Postamble transmission method and device

Abstract

A postamble transmission method and a device, which belong to the technical field of communication. The postamble transmission method in the embodiments of the present application comprises: on the basis of first information, a first device sending or receiving a postamble, wherein the first information comprises at least one of the following: first predefined information, first configuration information, first indication information, and a transmission format of a data portion.

Description

Tail code transmission method and device

[0001] Cross-reference to related applications

[0002] The present disclosure claims priority to Chinese Patent Application No. 202410403739.0, filed on April 3, 2024, the entire contents of which are incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] The present application belongs to the technical field of communication, and specifically relates to a tail code transmission method and device. BACKGROUND

[0004] In the current R19-ambient Internet of Things (AIoT) research, a postamble is considered to be used in a downlink / uplink channel, and the postamble is used to indicate the end of uplink / downlink transmission. The postamble can also be used for channel estimation / sample frequency offset (SFO) correction / better time synchronization, etc.

[0005] Therefore, for those skilled in the art, how to perform tail code transmission is a technical problem to be solved. SUMMARY

[0006] To solve the problems in the related art, the embodiments of the present application provide a tail code transmission method and device.

[0007] In a first aspect, a tail code transmission method is provided, comprising:

[0008] The first device sends or receives the tail code based on first information;

[0009] The first information comprises at least one of:

[0010] The first predefined information, the first configuration information, the first indication information, and the transmission format of the data part.

[0011] In a second aspect, a tail code transmission method is provided, comprising:

[0012] The second device sends or receives the tail code based on third information;

[0013] The third information comprises at least one of:

[0014] The first predefined information, the first configuration information, the third indication information, and the transmission format of the data part.

[0015] In a third aspect, a tail code transmission apparatus is provided, comprising:

[0016] transmitting or receiving the tail code based on the first information;

[0017] The first information includes at least one of the following:

[0018] The first predefined information, the first configuration information, the first indication information, and a transmission format of the data part.

[0019] In a fourth aspect, a tail code transmission apparatus is provided, comprising:

[0020] The transmission module is configured to transmit or receive the tail code based on the third information.

[0021] The third information includes at least one of the following:

[0022] The first predefined information, the first configuration information, the third indication information, and a transmission format of the data part.

[0023] In a fifth aspect, a first device is provided, comprising a processor and a memory, wherein the memory stores programs or instructions executable on the processor, and the programs or instructions, when executed by the processor, implement the steps of the tail code transmission method according to the first aspect.

[0024] In a sixth aspect, a first device is provided, comprising a processor and a communication interface, wherein the processor is configured to transmit or receive the tail code based on the first information, and the first information includes at least one of the following: first predefined information, first configuration information, first indication information, and a transmission format of the data part.

[0025] In a seventh aspect, a second device is provided, comprising a processor and a memory, wherein the memory stores programs or instructions executable on the processor, and the programs or instructions, when executed by the processor, implement the steps of the tail code transmission method according to the second aspect.

[0026] In an eighth aspect, a second device is provided, comprising a processor and a communication interface, wherein the processor is configured to transmit or receive the tail code based on the third information, and the third information includes at least one of the following: first predefined information, first configuration information, third indication information, and a transmission format of the data part.

[0027] In a ninth aspect, a readable storage medium is provided, wherein the readable storage medium stores programs or instructions, and the programs or instructions, when executed by a processor, implement the steps of the tail code transmission method according to the first aspect, or implement the steps of the tail code transmission method according to the second aspect.

[0028] In a tenth aspect, a wireless communication system is provided, comprising: a first device configured to perform the steps of the tail code transmission method according to the first aspect, and a second device configured to perform the steps of the tail code transmission method according to the second aspect.

[0029] In an eleventh aspect, a chip is provided, comprising a processor and a communication interface, the communication interface being coupled to the processor, the processor being configured to execute a program or instructions to implement the tail code transmission method according to the first aspect or the tail code transmission method according to the second aspect.

[0030] In a twelfth aspect, a computer program / program product is provided, stored in a storage medium, the program / program product being executed by at least one processor to implement the steps of the tail code transmission method according to the first aspect or the tail code transmission method according to the second aspect.

[0031] In the embodiments of the present application, the first device transmits or receives the tail code based on the first information, and the first information comprises at least one of the following: first predefined information, first configuration information, first indication information and a transmission format of the data part. In the above scheme, the transmission or reception of the tail code can be implemented based on the first information, which has greater flexibility and can improve the transmission performance. BRIEF DESCRIPTION OF DRAWINGS

[0032] FIG. 1 is a schematic diagram of an architecture of a wireless communication system according to an embodiment of the present application;

[0033] FIG. 2 is a schematic diagram of an A-IOT architecture according to an embodiment of the present application;

[0034] FIG. 3 is a schematic diagram of an A-IOT architecture according to an embodiment of the present application;

[0035] FIG. 4 is a schematic diagram of FM0 encoding according to an embodiment of the present application;

[0036] FIG. 5 is a schematic diagram of FM0 encoding states according to an embodiment of the present application;

[0037] FIG. 6 is a schematic diagram of FM0 encoding states according to an embodiment of the present application;

[0038] FIG. 7 is a state transition diagram of FM0 according to an embodiment of the present application;

[0039] FIG. 8 is a schematic diagram of a preamble of FM0 encoding according to an embodiment of the present application;

[0040] FIG. 9 is a schematic diagram of a preamble of FM0 encoding according to an embodiment of the present application;

[0041] Figure 10 is a schematic diagram of the end data of FM0 encoding provided in an embodiment of this application;

[0042] Figure 11 is a schematic diagram of Miller encoding provided in an embodiment of this application;

[0043] Figure 12 is one of the schematic diagrams of Miller encoding states provided in the embodiments of this application;

[0044] Figure 13 is a second schematic diagram of the Miller encoding state provided in the embodiment of this application;

[0045] Figure 14 is a Miller state transition diagram provided in an embodiment of this application;

[0046] Figure 15 is one of the schematic diagrams of Miller-encoded Preamble provided in the embodiments of this application;

[0047] Figure 16 is a second schematic diagram of the Miller-encoded Preamble provided in the embodiments of this application;

[0048] Figure 17 is a waveform diagram of Miller encoding provided in an embodiment of this application;

[0049] Figure 18 is a schematic diagram of the end data of Miller encoding provided in the embodiments of this application;

[0050] Figure 19 is a schematic diagram showing the relationship between chip rate and BLF provided in the embodiments of this application;

[0051] Figure 20 is a schematic diagram of PIE encoding provided in an embodiment of this application;

[0052] Figure 21 is a schematic diagram of Manchester encoding provided in an embodiment of this application;

[0053] Figure 22 is one of the flowcharts of the tail code transmission method provided in the embodiments of this application;

[0054] Figure 23 is a second schematic flowchart of the tail code transmission method provided in the embodiments of this application;

[0055] Figure 24 is one of the structural schematic diagrams of the tail code transmission device provided in the embodiments of this application;

[0056] Figure 25 is a second schematic diagram of the tail code transmission device provided in an embodiment of this application;

[0057] Figure 26 is a schematic diagram of the structure of the communication device provided in an embodiment of this application;

[0058] Figure 27 is a schematic diagram of the terminal structure according to an embodiment of this application.

[0059] Figure 28 is a schematic diagram of the network-side device according to an embodiment of this application. DETAILED DESCRIPTION

[0060] The technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all the other embodiments obtained by those of ordinary skill in the art are within the scope of protection of the present application.

[0061] The terms "first", "second", and the like in the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second" are generally a category and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in the present application means at least one of the connected objects. For example, "A or B" covers three schemes, namely, scheme one: including A and not including B; scheme two: including B and not including A; scheme three: including A and including B. The character " / " generally represents that the associated objects before and after are in an "or" relationship.

[0062] The term "indicate" in the present application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). Among them, the direct indication can be understood as that the sender explicitly informs the receiver of the specific information, the operation to be performed or the request result, etc. in the sent indication; the indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or judges and determines the operation to be performed or the request result, etc. according to the judgment result.

[0063] It is worth noting that the technology described in the embodiments of the present application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems. th

[0064] ​FIG. 1 shows a block diagram of a wireless communication system to which embodiments of the present application can be applied. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be an Internet of Things (IOT) device, an A-IOT device, a mobile phone, a Tablet Personal Computer, a Laptop Computer, a notebook computer, a Personal Digital Assistant (PDA), a palm computer, a netbook, an Ultra-mobile Personal Computer (UMPC), a Mobile Internet Device (MID), an Augmented Reality (AR) device, a Virtual Reality (VR) device, a robot, a wearable device, a flight vehicle, a Vehicle User Equipment (VUE), a shipboard device, a Pedestrian User Equipment (PUE), a smart home (a home device with a wireless communication function, such as a refrigerator, a television, a washing machine, or furniture, etc.), a game console, a Personal Computer (PC), a kiosk, or a self-service machine, etc. The wearable device includes a smart watch, a smart bracelet, a smart earphone, smart glasses, smart jewelry (a smart bracelet, a smart necklace, a smart ring, a smart necklace, a smart anklet, a smart necklace, etc.), a smart wristband, smart clothing, etc. The vehicle-mounted device can also be referred to as a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip, or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network-side device 12 can include an access network device or a core network device. The access network device can also be referred to as a Radio Access Network (RAN) device, a radio access network function, or a radio access network unit. The access network device can include a base station, a Wireless Local Area Network (WLAN) Access Point (AP), or a Wireless Fidelity (WiFi) node, etc.The base station can be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a relay station (RBS), a serving base station (SBS), a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home Node B (HNB), a home evolved Node B, a transmission reception point (TRP), or some other suitable terminology in the art, and is not limited to a particular technical terminology, provided that the same technical effect is achieved. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0065] The core network device can include, but is not limited to, at least one of the following: a core network node, a core network function, a mobility management entity (MME), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), a policy and charging rules function (PCRF), an edge application server discovery function (EASDF), a unified data management (UDM), a unified data repository (UDR), a home subscriber server (HSS), a centralized network configuration (CNC), a network repository function (NRF), a network exposure function (NEF), a local NEF (L-NEF), a binding support function (BSF), an application function (AF), and the like. It should be noted that only the core network device in the NR system is taken as an example for introduction in the embodiments of the present application, and the specific type of the core network device is not limited.

[0066] First, the technical terms and application scenarios involved in the embodiments of the present application are introduced:

[0067] I. AIoT device type:

[0068] In 3GPP R19 A-IoT research, the energy storage capacity of environmental Internet of Things devices and the ability to generate radio frequency signals for transmission are used to represent environmental Internet of Things devices. A-IoT devices have the following types:

[0069] (1) Device A: has energy storage, no independent signal generation / amplification, that is, can send signals using backscatter transmission.

[0070] (2) Device B: with energy storage, no independent signal generation, i.e. signals can be sent using backscatter transmission. The use of stored energy can include amplification of reflected signals.

[0071] (3) Device C: with energy storage, with independent signal generation, i.e. active RF components for transmission.

[0072] Different energy storage capabilities of devices also affect the transmission quality of the devices. In general, devices with higher energy storage also mean higher reception sensitivity or higher transmission power, and the reliability of the reception or transmission link can be better guaranteed.

[0073] II. AIoT service types:

[0074] Main data / service types of A-IoT:

[0075] 1. DO: Device-originated

[0076] 2. DT: Device-terminated

[0077] Among them, DO means that the data flow originates from the A-IoT device (similar to the Radio Frequency Identification (RFID) tag Tag), and DT data means that the data flow is transmitted to the A-IoT device. For data flow originating from A-IoT device, i.e. DO data, it can be further classified as:

[0078] 1-1, DO-A: DO autonomous, i.e. AIoT device initiates data transmission autonomously;

[0079] For example: Connect a large number of various sensors, which collect and actively report information about the environment, equipment and living things when necessary.

[0080] 1-2, DO-DTT, DO device-terminated triggered, i.e. base station and other reader devices (Reader) trigger AIoT device to initiate data transmission;

[0081] For example: Asset identification, status reporting and tracking, Reader collects data from Tag by triggering inventory program. Since the data is generated / initiated in the IoT device, this service should be considered as a DO service initiated by the Tag triggered by the Reader-side control command.

[0082] III. AIoT topology types:

[0083] Topology 1: Network device (e.g. BS) communicates with A-IoT device, as shown in Figure 2.

[0084] Topology 2: Network device (e.g. BS) communicates with intermediate node and A-IoT device, as shown in Figure 3.

[0085] Four, Introduction of Common Line Code:

[0086] For Tag to Reader (uplink), FM0 and Miller are used in RFID; for Reader to Tag (downlink), Pulse Interval Encoding (PIE) is used in RFID.

[0087] The following will introduce FM0, Miller, PIE and common Manchester encoding respectively:

[0088] 1. FM0

[0089] FM0 encoding (also known as Bi-Phase Space Coding) has memory, that is, the timing of FM0 depends on the previous transmission form. The working principle of FM0 encoding is to use level change within a bit window to represent logic. If the level flips from the start of the bit window, it represents logic "1". If the level flips in the middle of the bit window in addition to the start of the bit window, it represents logic "0". (That is, FM0 encoding has a jump at the beginning of each bit of data, and if there is a jump in the center of the data, it represents 0, and if there is no jump in the center of the data, it represents 1). According to the rules of FM0 encoding, it can be found that whether the transmitted data is 0 or 1, a jump needs to occur at the start of the bit window, as shown in Figure 4.

[0090] FM0 encoding defines four states, in which state S2 or state S3 represents data-0, as shown in Figure 5; state S1 or state S4 represents data-1, as shown in Figure 6.

[0091] And there is a transition relationship between the four states, for example, state S1 can be converted to state S3 or S4, and state S2 can be converted to S2 or S1, as shown in Figure 7.

[0092] There are two preambles sent before the data, which preamble is used is determined by the value of TRext in the Query command, as shown in Figure 8 for Trext = 0, and Figure 9 for Trext = 1. The "v" indicates an FM0 conflict, i.e. no corresponding phase flip occurs, and is used to distinguish the preambles from the data code. The transmission of data is always ended by a 1-bit signal of a "dummy" data 1, as shown in Figure 10.

[0093] 2. Miller

[0094] Miller code is also known as delay modulation code, and can be regarded as a variant of bi-phase code. In Miller basic encoding, only when 0 -> 0 (indicating that the two adjacent bits are both 0), the signal edge will be changed. For Miller-modulated subcarrier, each bit (Miller basic code) must include 2 / 4 / 8 subcarrier periods, and is determined by the value of M in the Query command. A schematic diagram of a Miller basic code "000" is shown in Figure 11.

[0095] Similar to FM0 encoding, Miller encoding also has four states, and states S1 or S4 represent data-0, as shown in Figure 12; states S2 or S3 represent data-1, as shown in Figure 13. There is also a corresponding state transition relationship, as shown in Figure 14.

[0096] Miller subcarrier signal starts transmission by one of the two preambles, which preamble is used is determined by the value of TRext in the Query command initiating the inventory, as shown in Figure 15 for Trext = 0, and Figure 16 for Trext = 1.

[0097] As shown in Figure 15, the encoding mode of M = 2 and TRext = 0 is used; the Miller encoding rules are as follows:

[0098] (1) If the current bit state is 1, the signal start is equal to the tail of the previous signal, with a jump in the middle;

[0099] (2) If the current bit state is 0, and the previous signal is 1, the signal start is equal to the tail of the previous signal, without a jump in the middle;

[0100] (3) If the current bit state is 0, and the previous signal is 0, the signal start is equal to the tail of the previous signal with a jump, without a jump in the middle.

[0101] Suppose there is a string of data to be encoded "010111". The first data bit is '0', the second data bit is '1' according to the normal encoding mode, which meets the above rule 1, so the signal starts with the tail of the previous signal and jumps in the middle. The third data bit is '0', which meets the above rule 2, so the signal starts with the tail of the previous signal and does not change in the middle. The fourth data bit is '1', which meets the above rule 1, so the signal starts with the tail of the previous signal and jumps in the middle. The fifth data bit is '1', which meets the above rule 1, so the signal starts with the tail of the previous signal and jumps in the middle. The sixth data bit is '1', which meets the above rule 1, so the signal starts with the tail of the previous signal and jumps in the middle. The final encoded waveform is shown in Figure 17.

[0102] While the Miller encoding also always ends the transmission of data with a "dummy" data 1 of 1 bit signal, as shown in Figure 18.

[0103] In RFID, the Tag sends the bit data encoded by FM0 / Miller to the Reader using the Backscatter Link Frequency (BLF). The relationship between the chip rate and a period corresponding to the BLF is shown in Figure 19, where the bit time in FM0 is T cycle , and the bit time in Miller-2 / 4 / 8 is 2*T cycle , 4*T cycle , and 8*T cycle , respectively.

[0104] 3、PIE

[0105] Pulse Interval Encoding (PIE) (in which data-0 and data-1 are shown in Figure 20, where Tari is the reference time interval, PW (Pulse width) is the pulse width, and the duration of data-0 is Tari, and the duration of data-1 is 1.5-2Tari.

[0106] 4、Manchester

[0107] Manchester encoding represents data-0 and data-1 by a level jump in the middle of the bit window, where data-0 is represented as a jump from high to low, and data-0 is represented as a jump from low to high. An example of Manchester encoding is shown in Figure 21.

[0108] In the embodiments of the present application, the tail code can also be referred to as a postamble, a postamble code, a postamble sequence, a postamble signal, etc. The embodiments of the present application do not limit this.

[0109] Optionally, the first device (such as the responding device) can be a tag or an electronic tag (Tag), that is, an RFID tag, which is a common name of RFID. Radio frequency identification technology can be divided into active, passive and semi-active three kinds. For passive tags, it can also be referred to as passive IOT, that is, passive Internet of Things device. The communication mode of the responding device can be backscattering RF signal for signal transmission, or some active tags have the ability to generate active signals. Because the energy of the responding device can come from the environment, such as environmental RF energy, thermal energy, wind energy, kinetic energy, etc., it can also be referred to as an A-IoT device. Therefore, the first device can also be regarded as a terminal, and can also be referred to as a terminal device.

[0110] The second device (such as the reading and writing device): a handheld or fixed reading (sometimes also writing) tag information device, which can also be understood as a device communicating with the tag, such as a terminal, a base station, or a device with reading and writing functions, for example, a reader (Reader), which is not limited here. The reading and writing device can send a carrier excitation signal or a control command.

[0111] Optionally, the tail code transmission includes downlink transmission of the second device to the first device, and also includes uplink transmission of the first device to the second device, which is not limited.

[0112] The tail code transmission method provided by the embodiments of the present application will be described in detail in combination with the drawings and some embodiments and application scenarios.

[0113] Please refer to FIG. 22, the present application embodiment provides a tail code transmission method, the execution subject of the present embodiment is the first device, and the method comprises:

[0114] Step 101, the first device sends or receives the tail code based on the first information;

[0115] The first information includes at least one of the following:

[0116] The first pre-defined information, the first configuration information, the first indication information, and the transmission format of the data part.

[0117] In some embodiments, the tail code can be a sequence after the data part, and the first device can send or receive the tail code based on at least one of the first pre-defined information, the first configuration information, the first indication information, and the transmission format of the data part.

[0118] Optionally, whether to transmit the tail code is determined based on at least one of the first information, and the tail code is transmitted or received.

[0119] Optionally, whether to transmit the tail code can be determined by the first predefined information, that is, the first device can transmit the tail code or receive the tail code transmitted by the second device through the first predefined information. The first predefined information can be information or rules agreed in advance by the protocol, and the first predefined information can be information of the first device itself or information transmitted by the second device to the first device.

[0120] Optionally, the first device transmits or receives the tail code through the first configuration information, which is transmitted by the second device or forwarded by the network side device through the second device. Optionally, when the second device is the network side device, the first configuration information can be carried through control signaling.

[0121] Optionally, the tail code is transmitted or received through the first indication information. Optionally, the first indication information is indication information of the network side device transmitted by the second device or forwarded by the second device. Optionally, in the forwarding case (as shown in FIG. 3), the second device can parse and re-encapsulate and then transmit, or directly transmit. For example, in the scenario shown in FIG. 2, the second device dynamically or semi-statically indicates whether to transmit the tail code through downlink control signaling.

[0122] Optionally, the transmission format includes at least one of frequency, chip rate, coding, subcarrier data corresponding to each bit, sequence format, transmission type, and data length used for transmission.

[0123] Optionally, whether to transmit the tail code can be implicitly determined based on the transmission format of the data part, that is, the first device can transmit or receive the tail code based on the transmission format of the data part. Optionally, the tail code is associated with the data length, transmission type, etc. of the data part. For example, for certain transmission type or types, the tail code can be transmitted, and for certain transmission type or types, the tail code is not transmitted, for example, for signaling transmission of a certain type, the tail code can not be transmitted. For example, for a data part with a data length less than or equal to a certain threshold, the tail code can not be transmitted, and for a data part with a data length greater than a certain threshold, the tail code can be transmitted. The above-mentioned data part refers to the data transmitted before the tail code, which can be data or signaling or a preamble, without limitation.

[0124] The tail code transmission method of the embodiment, the first device transmits or receives the tail code based on the first information; the first information includes at least one of the following: first predefined information, first configuration information, first indication information, and transmission format of the data part. In the above-mentioned scheme, the transmission or reception of the tail code can be realized based on the first information, which has greater flexibility and can improve transmission performance.

[0125] Optionally, the transmission format of the tail code is associated with the transmission format of the data part, and the association is determined based on at least one of the following: second predefined information, second configuration information, and the second indication information.

[0126] Optionally, the second indication information is indication information of a network side device sent by or forwarded by the second device.

[0127] In some embodiments, the association can be determined based on second predefined information (such as protocol predefined information, predefined rules), second configuration information (such as configuration information sent by the second device to the first device), or second indication information dynamically indicated by the second device to the first device.

[0128] The second configuration information can be information configured by the second device to the first device, or configuration information of a network side device forwarded by the second device.

[0129] In the above embodiments, the association between the tail code and the data part is determined in multiple ways, which is more flexible.

[0130] Optionally, the tail code satisfies at least one of the following:

[0131] (1) the frequency of the tail code is different from the frequency of the data part;

[0132] (2) the chip rate of the tail code is different from the chip rate of the data part;

[0133] (3) the encoding of the tail code is different from the encoding of the data part;

[0134] (4) the number of subcarrier periods corresponding to each bit of the tail code is different from the number of subcarrier periods corresponding to each bit of the data part;

[0135] (5) the tail code includes check bits generated based on the data part;

[0136] (6) the tail code includes a predefined sequence;

[0137] (7) the tail code and the data part are connected by a delimiter.

[0138] For (1), for example, for uplink transmission from Tag (first device) to Reader (second device), the BLF used by the postamble is associated with the BLF of the data part, for example, the BLF of the postamble is 2 times or 1 / 2 or X times of the BLF of the data part, X can be indicated by the Reader to determine or determined based on pre-configuration / pre-defined information or rules, etc. For example, the Tag determines the BLF used by the uplink data transmission part to be 80 kHz based on the downlink indication of the Reader, if the pre-defined BLF of the postamble is 2 times of the BLF of the data transmission part, then the backscatter frequency used by the postamble is BLF = 160 kHz.

[0139] For (2), for example, for downlink transmission from Reader (second device) to Tag (first device), PIE encoding is used, the postamble uses a different Tari value from the data part, for example, the Tari value used by the postamble is 2 times or 1 / 2 of the Tari value used by the data part, etc.

[0140] For (3), for example, for uplink transmission from Tag (first device) to Reader (second device), there are two encoding methods to choose from, respectively FM0 and Miller, if the data part uses FM0 encoding, then the postamble can use Miller encoding by default (for example, Miller-2 is used by default); if the data part uses Miller encoding, the postamble uses FM0 encoding by default.

[0141] For example, for downlink transmission from Reader (second device) to Tag (first device), if the data part uses PIE encoding, then the postamble uses Manchester encoding by default; if the data part uses Manchester encoding, then the postamble uses PIE encoding by default.

[0142] For (4), for example, for uplink transmission from Tag (first device) to Reader (second device), the data part uses Miller-2, i.e. each bit includes 2 subcarrier periods / subcarrier periods, then the postamble uses Miller-4, i.e. each bit includes 4 subcarrier periods / subcarrier periods.

[0143] In the above embodiments, by letting the postamble use a different frequency / chip rate / encoding / subcarrier period number from the data part, it can be ensured that the same level pattern as the postamble cannot appear in the data transmission, thereby improving the accuracy of postamble monitoring and reducing the false detection rate of the postamble.

[0144] Optionally, in some embodiments, the postamble sequence can be generated based on the data part and the check bits, and the additional definition of the postamble sequence can not be needed. For example, the CRC check bits can be generated based on the data part and a CRC generation polynomial, and the CRC check bits can be used as the postamble sequence, so that the transmission load can be reduced.

[0145] Optionally, the data part and the postamble are connected by a delimiter (or the postamble is connected as a starting part of the delimiter).

[0146] In some embodiments, the delimiter is at least 1 bit, and the delimiter can be a violation, i.e., the encoding rule used by the delimiter is opposite or different from the encoding rule of the data part. For example, for FM0 encoding, no level jump occurs between the delimiter and the previous bit (i.e., the bit in the data part) (the normal encoding rule is to have a level jump) ; for example, for Miller encoding, the last bit of the data part is 1, and the delimiter is bit 0, so that the start of the postamble corresponding to the delimiter has a jump from the previous signal tail (i.e., the last bit of the data part) (the normal encoding rule is equal to the previous signal tail) ; for example, for Manchester, consecutive high or low level symbols are used as delimiters (the normal encoding rule is to have a jump in the middle of the bit window), or for PIE encoding, the Tari value used for encoding is different from the Tari value of the data part, e.g., the Tari value of the data part is used as X times to encode as the delimiter.

[0147] In the above embodiments, the data part and the postamble are separated by the delimiter, so that the start position of the postamble can be determined, and the detection complexity of the postamble can be reduced.

[0148] The above (1) - (7) can be combined for use, e.g., the CRC check sequence generated based on the data part is used as the postamble sequence, the postamble and the data part are connected by the delimiter, and the backscatter frequency and the encoding manner of the postamble are different from the backscatter frequency and the encoding manner of the data part, respectively. Among them, the same postamble (5) and (6) are generally not used at the same time.

[0149] Optionally, the postamble further satisfies at least one of the following rules:

[0150] The frequency of the postamble is different from the frequency of the middle symbol.

[0151] The chip rate of the postamble is different from the chip rate of the middle symbol.

[0152] The encoding of the tail code is different from the encoding of the middle symbol.

[0153] The number of subcarrier periods corresponding to each bit of the tail code is different from the number of subcarrier periods corresponding to each bit of the middle symbol.

[0154] The middle symbol can also be referred to as a Midamble, a synchronization symbol, a timing tracking symbol, or a middle identifier, etc.

[0155] The middle symbol can be inserted in the data part.

[0156] Optionally, the first device determines that the tail code satisfies at least one rule based on at least one of a transmission type and a data length of the data part.

[0157] Optionally, the transmission type includes at least one of the following:

[0158] The uplink transmission, the downlink transmission, the data transmission, and the signaling transmission, wherein the signaling transmission includes at least one signaling type of signaling transmission.

[0159] The uplink transmission refers to the transmission from the first device to the second device.

[0160] The downlink transmission refers to the transmission from the second device to the first device.

[0161] The different transmission types include but are not limited to the uplink transmission, the downlink transmission, the data transmission, and the signaling transmission. Further, the signaling transmission can also include different signaling type transmissions, such as read commands / write commands, etc.

[0162] In some embodiments, different rules are combined to determine the tail code according to different transmission types.

[0163] For example, for the signaling transmission and the data transmission, the transmission format of the tail code can be determined respectively. For the signaling Command (such as the Query command) without CRC, the violation+predefined sequence can be used as the tail code, or only the violation is used as the tail code, or it is considered that there is no tail code (for example, for the Command with a determined bit length, the tail code does not need to be transmitted); for the data transmission, the predefined sequence can be used as the tail code.

[0164] The predefined sequence is, for example, a specific 01 bit sequence.

[0165] Optionally, the tail code can also be determined according to different data lengths of the data part of the transmission (including signaling / data). For example, the transmission format of the tail code is determined according to the data length (such as bit length) of the signaling / data. For example, when the bit length of the data part is less than or equal to a certain predefined threshold, the CRC check bit is used as the tail code; when the bit length of the data part is greater than the threshold, a predefined sequence (such as a longer CRC check sequence) is used as the tail code.

[0166] Optionally, the first device sends or receives the tail code based on the first information, including:

[0167] The first device sends the tail code to the second device based on the first information, or

[0168] The first device receives the tail code sent by the second device based on the first information.

[0169] Optionally, the first device determines whether to send the tail code based on the first information;

[0170] In the case of determining to send the tail code, the first device determines the transmission format of the tail code based on second information; the second information includes at least one of the following: first predefined information, first configuration information, first indication information, and transmission format of the data part;

[0171] The first device sends the tail code to the second device based on the transmission format of the tail code.

[0172] In some embodiments, the first device determines whether to send the tail code based on the first information, determines the transmission format of the tail code based on the second information in the case of determining to send the tail code, and sends the tail code to the second device based on the transmission format of the tail code, which has greater reliability and can improve transmission performance.

[0173] Optionally, whether to transmit the tail code, the transmission format of the tail code (such as at least one of the frequency used, the chip rate, the coding, the number of subcarriers corresponding to each bit, and the sequence format) can be determined by the first predefined information.

[0174] Optionally, the first device sends or receives the tail code through the first configuration information, for example, the first device learns the format of the tail code received by the first device in downlink and the format of the tail code sent by the first device in uplink through the first configuration information, and then the first device and the second device send and receive the tail code according to this format.

[0175] Optionally, the first indication information sent by the second device is used to determine whether to transmit the tail code and the transmission format of the tail code. For example, the second device indicates the format of the downlink tail code and the format of the uplink tail code sent by the first device through the first indication information.

[0176] Optionally, whether to transmit the tail code and the transmission format of the tail code (e.g. frequency used, chip rate, coding, number of subcarriers corresponding to each bit, sequence format, etc.) can be determined implicitly based on the transmission format of the data part, e.g. the tail code is associated with the frequency, chip rate, coding, number of subcarriers used by the data part, and the frequency, chip rate, coding, number of subcarriers used by the tail code are determined implicitly based on the frequency, chip rate, coding, number of subcarriers used by the data part.

[0177] Optionally, the above several manners can be used in combination, i.e. a combination of multiple of the first predefined information, the first configuration information, the first indication information and the transmission format of the data part can determine whether to transmit the tail code and the transmission format of the tail code.

[0178] For example, the first device determines whether to transmit the tail code based on the first indication information or the first configuration information, and determines the transmission format of the tail code based on the transmission format of the data part.

[0179] Optionally, the first device receives the tail code transmitted by the second device based on the first information, including:

[0180] The first device determines whether the second device transmits the tail code based on the first information;

[0181] In a case where it is determined that the second device transmits the tail code, the first device determines the transmission format of the tail code based on second information, and the second information includes at least one of the first predefined information, the first configuration information, the first indication information and the transmission format of the data part;

[0182] The first device receives the tail code transmitted by the second device based on the transmission format of the tail code.

[0183] In some embodiments, the first device determines whether the second device transmits the tail code based on the first information, in a case where it is determined that the second device transmits the tail code, determines the transmission format of the tail code based on the second information, and receives the tail code transmitted by the second device based on the transmission format of the tail code, which can correctly parse the tail code and improve the accuracy of signal detection.

[0184] Optionally, the first device determines the transmission format of the tail code based on the second information, including:

[0185] The first device determines at least one rule satisfied by the tail code based on at least one of the transmission type and the data length of the data part;

[0186] The first device determines the transmission format of the tail code based on the second information and the at least one rule satisfied by the tail code.

[0187] In some embodiments, the first device can determine at least one rule satisfied by the tail code based on at least one of the transmission type and the data length of the data part, i.e., determine at least one information required by the transmission format of the tail code, and further determine the transmission format finally adopted by the tail code based on the second information and the at least one rule satisfied by the tail code.

[0188] Optionally, the transmission format of the tail code comprises at least one of the following:

[0189] frequency, chip rate, coding, number of subcarrier periods corresponding to each bit, sequence format adopted, delimiter, data length.

[0190] It should be noted that the transmission format is only a summary of the information required for transmitting the tail code, and other names can be used in other embodiments, which are not limited in the embodiments of the present application.

[0191] Referring to FIG. 23, the embodiments of the present application provide a tail code transmission method, and the execution subject of the embodiments is a second device, which comprises the following steps:

[0192] Step 201: The second device transmits or receives the tail code based on third information.

[0193] The third information comprises at least one of the following:

[0194] first predefined information, first configuration information, third indication information, and transmission format of the data part.

[0195] In some embodiments, the second device can transmit or receive the tail code based on at least one of the first predefined information, the first configuration information, the third indication information, and the transmission format of the data part. For example, whether to transmit the tail code is determined based on at least one of the above first information.

[0196] Optionally, the first configuration information can be pre-configured in the second device or configuration information transmitted by a network side device.

[0197] Optionally, the third indication information is indication information of the network side device transmitted by the first device or forwarded by the first device.

[0198] Optionally, the transmission format of the tail code is associated with the transmission format of the data part, and the association relationship is determined based on at least one of the following: second predefined information, second configuration information, and fourth indication information. The fourth indication information can be information transmitted by the first device to the second device, and can be indication information of the network side device transmitted directly by the first device or forwarded by the first device. Optionally, the second configuration information can be pre-configured in the second device or configuration information transmitted by a network side device.

[0199] Optionally, the tail code satisfies at least one of the following rules:

[0200] The frequency of the tail code is different from the frequency of the data part.

[0201] The chip rate of the tail code is different from the chip rate of the data part.

[0202] The encoding of the tail code is different from the encoding of the data part.

[0203] The number of subcarrier periods corresponding to each bit of the tail code is different from the number of subcarrier periods corresponding to each bit of the data part.

[0204] The tail code includes check bits generated based on the data part.

[0205] The tail code includes a predefined sequence.

[0206] The tail code and the data part are connected by a delimiter.

[0207] Optionally, before the sending or receiving the tail code, further comprising:

[0208] The second device determines that the tail code satisfies at least one of the rules based on at least one of the transmission type and the data length of the data part.

[0209] Optionally, the second device sends the tail code based on the third information, comprising:

[0210] The second device determines whether to send the tail code based on the third information.

[0211] In the case of determining to send the tail code, the second device determines the transmission format of the tail code based on fourth information; the fourth information includes at least one of the following: first predefined information, first configuration information, third indication information, and the transmission format of the data part.

[0212] The second device sends the tail code to the first device based on the transmission format of the tail code.

[0213] Optionally, the second device receives the tail code based on the first information, comprising:

[0214] The second device determines whether the first device sends the tail code based on the third information.

[0215] In the case of determining that the first device sends the tail code, the second device determines the transmission format of the tail code based on fourth information; the fourth information includes at least one of the following: first predefined information, first configuration information, third indication information, and the transmission format of the data part.

[0216] The second device receives the trailer code sent by the first device based on a transmission format of the trailer code.

[0217] Optionally, the second device determines the transmission format of the trailer code based on fourth information, including:

[0218] The second device determines at least one rule that the trailer code satisfies based on at least one of a transmission type and a data length of the data part;

[0219] The second device determines the transmission format of the trailer code based on the fourth information and at least one rule that the trailer code satisfies.

[0220] Optionally, the transmission type includes at least one of:

[0221] Uplink transmission, downlink transmission, data transmission, and signaling transmission, the signaling transmission including signaling transmission of at least one signaling type.

[0222] The method provided in the embodiments of the present application has the same processes and achieves the same technical effects as the method embodiment shown in FIG. 22, and thus details are not repeated here.

[0223] The trailer code transmission method provided in the embodiments of the present application can be executed by a trailer code transmission device. In the embodiments of the present application, the trailer code transmission method is executed by a trailer code transmission device as an example, and the trailer code transmission device provided in the embodiments of the present application is described.

[0224] FIG. 24 is a structural schematic diagram of a trailer code transmission device provided in the embodiments of the present application, as shown in FIG. 24, the trailer code transmission device is applied to a first device, and the trailer code transmission device includes:

[0225] The transmission module 110 is configured to send or receive the trailer code based on first information.

[0226] The first information includes at least one of:

[0227] First predefined information, first configuration information, first indication information, and a transmission format of the data part.

[0228] Optionally, the transmission format of the trailer code is associated with the transmission format of the data part, and the association relationship is determined based on at least one of second predefined information, second configuration information, and the second indication information.

[0229] Optionally, the trailer code satisfies at least one rule, including:

[0230] The frequency of the trailer code is different from the frequency of the data part;

[0231] The chip rate of the trailer code is different from the chip rate of the data part.

[0232] The encoding of the tail code is different from the encoding of the data part;

[0233] The number of subcarrier periods corresponding to each bit of the tail code is different from the number of subcarrier periods corresponding to each bit of the data part;

[0234] The tail code includes check bits generated based on the data part;

[0235] The tail code includes a predefined sequence;

[0236] The tail code and the data part are connected by a delimiter.

[0237] Optionally, the transmission module 110 is further configured to:

[0238] Determine at least one rule that the tail code satisfies based on at least one of a transmission type and a data length of the data part.

[0239] Optionally, the transmission module 110 is specifically configured to:

[0240] Determine whether to send the tail code based on the first information;

[0241] In a case where it is determined to send the tail code, determine a transmission format of the tail code based on second information; the second information includes at least one of first predefined information, first configuration information, first indication information, and a transmission format of the data part.

[0242] Send the tail code to the second device based on the transmission format of the tail code.

[0243] Optionally, the transmission module 110 is specifically configured to:

[0244] Determine whether the second device sends the tail code based on the first information;

[0245] In a case where it is determined that the second device sends the tail code, determine a transmission format of the tail code based on second information; the second information includes at least one of first predefined information, first configuration information, first indication information, and a transmission format of the data part.

[0246] Receive the tail code sent by the second device based on the transmission format of the tail code.

[0247] Optionally, the transmission module 110 is specifically configured to:

[0248] The first device determines at least one rule that the tail code satisfies based on at least one of a transmission type and a data length of the data part;

[0249] The first device determines a transmission format of the tail code based on at least one rule satisfied by the tail code and the second information.

[0250] The first device determines at least one rule satisfied by the tail code based on at least one of a transmission type and a data length;

[0251] Optionally, the transmission type includes at least one of:

[0252] An uplink transmission, a downlink transmission, a data transmission, and a signaling transmission, the signaling transmission including at least one signaling type of signaling transmission.

[0253] The tail code transmission apparatus provided in the embodiments of the present application can implement each process achieved by the method embodiment shown in FIG. 22 and achieve the same technical effects. To avoid repetition, details are not described herein.

[0254] FIG. 25 is a structural schematic diagram of a tail code transmission apparatus provided in the embodiments of the present application, as shown in FIG. 25, the tail code transmission apparatus is applied to a second device, and the tail code transmission apparatus includes:

[0255] The transmission module 210 is configured to transmit or receive the tail code based on third information.

[0256] The first information includes at least one of:

[0257] First predefined information, first configuration information, third indication information, and a transmission format of a data part.

[0258] Optionally, the transmission format of the tail code is associated with the transmission format of the data part, and the association relationship is determined based on at least one of second predefined information, second configuration information, and the fourth indication information.

[0259] Optionally, the tail code satisfies at least one rule:

[0260] The frequency of the tail code is different from the frequency of the data part;

[0261] The chip rate of the tail code is different from the chip rate of the data part;

[0262] The encoding of the tail code is different from the encoding of the data part;

[0263] The number of subcarrier periods corresponding to each bit of the tail code is different from the number of subcarrier periods corresponding to each bit of the data part;

[0264] The tail code includes a check bit generated based on the data part;

[0265] The tail code includes a predefined sequence;

[0266] The tail code and the data part are connected by a delimiter.

[0267] Optionally, the transmission module 210 is further configured to:

[0268] The second device determines at least one rule that the tail code satisfies based on at least one of a transmission type and a data length of the data part.

[0269] Optionally, the transmission module 210 is specifically configured to:

[0270] Determine whether to send the tail code based on the third information;

[0271] In a case where it is determined to send the tail code, determine a transmission format of the tail code based on fourth information; the fourth information includes at least one of first predefined information, first configuration information, third indication information, and a transmission format of the data part.

[0272] Send the tail code to the first device based on the transmission format of the tail code.

[0273] Optionally, the transmission module 210 is specifically configured to:

[0274] Determine whether the first device sends the tail code based on the third information;

[0275] In a case where it is determined that the first device sends the tail code, determine a transmission format of the tail code based on fourth information; the fourth information includes at least one of first predefined information, first configuration information, third indication information, and a transmission format of the data part.

[0276] Receive the tail code sent by the first device based on the transmission format of the tail code.

[0277] Optionally, the transmission module 210 is specifically configured to:

[0278] Determine at least one rule that the tail code satisfies based on at least one of a transmission type and a data length of the data part.

[0279] Determine a transmission format of the tail code based on the fourth information and the at least one rule that the tail code satisfies.

[0280] Optionally, the transmission type includes at least one of:

[0281] Uplink transmission, downlink transmission, data transmission, and signaling transmission, and the signaling transmission includes signaling transmission of at least one signaling type.

[0282] The tail code transmission apparatus provided in the embodiments of the present application can implement each process of the method embodiments shown in FIG. 23 and achieve the same technical effects. To avoid repetition, details are not described herein.

[0283] The tail code transmission apparatus in the embodiments of the present application can be an electronic device, for example, an electronic device with an operating system, or a component in the electronic device, for example, an integrated circuit or a chip. The electronic device can be a terminal or other device. For example, the terminal can include, but is not limited to, the types of the terminal 11 listed above, and the other device can be a server, a network attached storage (NAS), etc. The embodiments of the present application are not limited in this regard.

[0284] The tail code transmission apparatus provided in the embodiments of the present application can implement each process of the method embodiments shown in FIG. 22 to FIG. 23 and achieve the same technical effects. To avoid repetition, details are not described herein.

[0285] As shown in FIG. 26, the embodiments of the present application further provide a communication device 2600, which includes a processor 2601 and a memory 2602. The memory 2602 stores programs or instructions executable on the processor 2601. For example, when the communication device 2600 is a terminal, the programs or instructions are executed by the processor 2601 to implement each step of the tail code transmission method embodiments described above and achieve the same technical effects. When the communication device 2600 is a network side device, the programs or instructions are executed by the processor 2601 to implement each step of the tail code transmission method embodiments described above and achieve the same technical effects. To avoid repetition, details are not described herein.

[0286] The embodiments of the present application further provide a terminal, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to execute programs or instructions to implement the steps in the method embodiments shown in FIG. 22 or FIG. 23. The terminal embodiments correspond to the terminal side method embodiments described above. Each implementation process and implementation manner of the method embodiments can be applied to the terminal embodiments and achieve the same technical effects. Specifically, FIG. 27 is a schematic diagram of a hardware structure of a terminal implementing the embodiments of the present application.

[0287] The terminal 2700 includes, but is not limited to, at least part of the following components: a radio frequency unit 2701, a network module 2702, an audio output unit 2703, an input unit 2704, a sensor 2705, a display unit 2706, a user input unit 2707, an interface unit 2708, a memory 2709, and a processor 2710.

[0288] Those skilled in the art can understand that the terminal 2700 can also include a power supply (such as a battery) for supplying power to each component, and the power supply can be logically connected to the processor 2710 through a power management system, so that the power management system can realize the functions of managing charging, discharging, power consumption management and the like. The terminal structure shown in FIG. 27 does not constitute a limitation on the terminal, and the terminal can include more or fewer components than those shown, or combine certain components, or different component arrangements, which are not described here.

[0289] It should be understood that in the embodiments of the present application, the input unit 2704 can include a graphics processor (GPU) 27041 and a microphone 27042. The graphics processor 27041 processes image data of a still picture or a video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 2706 can include a display panel 27061, which can be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 2707 includes at least one of a touch panel 27071 and other input devices 27072. The touch panel 27071 is also called a touch screen. The touch panel 27071 can include two parts of a touch detection device and a touch controller. The other input devices 27072 can include, but are not limited to, a physical keyboard, function keys (such as volume control keys, on-off keys, etc.), trackballs, mice, joysticks, which are not described here.

[0290] In the embodiments of the present application, after the radio frequency unit 2701 receives the downlink data from the network side device, it can be transmitted to the processor 2710 for processing. In addition, the radio frequency unit 2701 can send uplink data to the network side device. Generally, the radio frequency unit 2701 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0291] The memory 2709 can be used to store software programs or instructions and various data. The memory 2709 can mainly include a first storage area storing programs or instructions and a second storage area storing data, wherein the first storage area can store an operating system, application programs or instructions required by at least one function (such as a sound playing function, an image playing function, etc.), and the like. In addition, the memory 2709 can include a volatile memory or a non-volatile memory. The non-volatile memory can be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. The volatile memory can be a Random Access Memory (RAM), a Static RAM (SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double Data Rate SDRAM (DDR SDRAM), an Enhanced SDRAM (ESDRAM), a Synch link DRAM (SLDRAM), and a Direct Rambus RAM (DRRAM). The memory 2709 in the embodiments of the present application includes but is not limited to these and any other suitable types of memory.

[0292] The processor 2710 can include one or more processing units; optionally, the processor 2710 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and an application program, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 2710.

[0293] The radio frequency unit 2701 is configured to transmit or receive the tail code based on the first information.

[0294] The first information includes at least one of the following:

[0295] The first predefined information, the first configuration information, the first indication information, and the transmission format of the data part.

[0296] Optionally, the transmission format of the tail code is associated with the transmission format of the data part, and the association is determined based on at least one of the following: second predefined information, second configuration information, and the second indication information.

[0297] Optionally, the tail code satisfies at least one of the following rules:

[0298] The frequency of the tail code is different from the frequency of the data part;

[0299] The chip rate of the tail code is different from the chip rate of the data part;

[0300] The encoding of the tail code is different from the encoding of the data part;

[0301] The number of subcarrier periods corresponding to each bit of the tail code is different from the number of subcarrier periods corresponding to each bit of the data part;

[0302] The tail code includes check bits generated based on the data part;

[0303] The tail code includes a predefined sequence;

[0304] The tail code and the data part are connected by a delimiter.

[0305] Optionally, the radio frequency unit 2701 is further configured to:

[0306] Determine, based on at least one of the transmission type and the data length of the data part, at least one rule that the tail code satisfies.

[0307] Optionally, the radio frequency unit 2701 is specifically configured to:

[0308] Determine, based on the first information, whether to send the tail code;

[0309] In a case where it is determined to send the tail code, determine, based on second information, the transmission format of the tail code; the first information includes at least one of the following: first predefined information, first configuration information, first indication information, and the transmission format of the data part;

[0310] Send the tail code to the second device based on the transmission format of the tail code.

[0311] Optionally, the radio frequency unit 2701 is specifically configured to:

[0312] Determine, based on the first information, whether the second device sends the tail code;

[0313] In a case that it is determined that the second device transmits the trailer code, determining a transmission format of the trailer code based on second information; the first information comprises at least one of the following: first predefined information, first configuration information, first indication information and a transmission format of the data part;

[0314] Receiving the trailer code transmitted by the second device based on the transmission format of the trailer code.

[0315] Optionally, the radio frequency unit 2701 is specifically used for:

[0316] The first device determines that the trailer code satisfies at least one rule based on at least one of a transmission type and a data length of the data part;

[0317] The first device determines the transmission format of the trailer code based on the second information and at least one rule satisfied by the trailer code.

[0318] Optionally, the transmission type comprises at least one of the following:

[0319] Uplink transmission, downlink transmission, data transmission and signaling transmission, and the signaling transmission comprises at least one signaling type of signaling transmission. Or,

[0320] The radio frequency unit 2701 is used for transmitting or receiving the trailer code based on third information;

[0321] The third information comprises at least one of the following:

[0322] First predefined information, first configuration information, third indication information and a transmission format of the data part.

[0323] Optionally, the transmission format of the trailer code is associated with the transmission format of the data part, and the association relationship is determined based on at least one of the following: second predefined information, second configuration information and the fourth indication information.

[0324] Optionally, the trailer code satisfies at least one rule:

[0325] The frequency of the trailer code is different from the frequency of the data part;

[0326] The chip rate of the trailer code is different from the chip rate of the data part;

[0327] The encoding of the trailer code is different from the encoding of the data part;

[0328] The number of subcarrier periods corresponding to each bit of the trailer code is different from the number of subcarrier periods corresponding to each bit of the data part;

[0329] The trailer code comprises a check bit generated based on the data part;

[0330] The tail code includes a predefined sequence.

[0331] The tail code and the data part are connected by a delimiter.

[0332] Optionally, the radio frequency unit 2701 is further used for:

[0333] The second device determines at least one rule that the tail code satisfies based on at least one of a transmission type and a data length of the data part.

[0334] Optionally, the radio frequency unit 2701 is specifically used for:

[0335] Based on the third information, it is determined whether to send the tail code.

[0336] In a case where it is determined to send the tail code, a transmission format of the tail code is determined based on fourth information; the fourth information includes at least one of first predefined information, first configuration information, third indication information, and a transmission format of the data part.

[0337] Based on the transmission format of the tail code, the tail code is sent to the first device.

[0338] Optionally, the radio frequency unit 2701 is specifically used for:

[0339] Based on the third information, it is determined whether the first device sends the tail code.

[0340] In a case where it is determined that the first device sends the tail code, a transmission format of the tail code is determined based on fourth information; the fourth information includes at least one of first predefined information, first configuration information, third indication information, and a transmission format of the data part.

[0341] Based on the transmission format of the tail code, the tail code sent by the first device is received.

[0342] Optionally, the radio frequency unit 2701 is specifically used for:

[0343] Based on at least one of a transmission type and a data length of the data part, at least one rule that the tail code satisfies is determined.

[0344] Based on the fourth information and at least one rule that the tail code satisfies, a transmission format of the tail code is determined.

[0345] Optionally, the transmission type includes at least one of:

[0346] Uplink transmission, downlink transmission, data transmission, and signaling transmission, the signaling transmission includes signaling transmission of at least one signaling type.

[0347] It can be understood that the implementation process of each implementation manner mentioned in the embodiment can refer to the related description of the method embodiment shown in FIG. 22 or FIG. 23, and achieve the same or corresponding technical effects. To avoid repetition, details are not described herein.

[0348] The embodiment of the present application further provides a network side device, comprising a processor and a communication interface, wherein the communication interface is coupled with the processor, and the processor is configured to run programs or instructions to implement the steps of the method embodiment shown in FIG. 23. The network side device embodiment corresponds to the network side device method embodiment described above, and each implementation process and implementation manner of the method embodiment described above can be applied to the network side device embodiment and achieve the same technical effects.

[0349] Specifically, the embodiment of the present application further provides a network side device. As shown in FIG. 28, the network side device 2800 comprises an antenna 281, a radio frequency device 282, a baseband device 283, a processor 284 and a memory 288. The antenna 281 is connected with the radio frequency device 282. In the uplink direction, the radio frequency device 282 receives information through the antenna 281 and sends the received information to the baseband device 283 for processing. In the downlink direction, the baseband device 283 processes the information to be sent and sends it to the radio frequency device 282. The radio frequency device 282 processes the received information and sends it out through the antenna 281.

[0350] The method performed by the network side device in the above embodiment can be implemented in the baseband device 283, which comprises a baseband processor.

[0351] The baseband device 283 may, for example, comprise at least one baseband board, and a plurality of chips are arranged on the baseband board, as shown in FIG. 28. One of the chips is, for example, a baseband processor, which is connected with the memory 288 through a bus interface to call programs in the memory 288 and perform the network device operations shown in the above method embodiment.

[0352] The network side device may, for example, further comprise a network interface 286, which is, for example, a Common Public Radio Interface (CPRI).

[0353] Specifically, the network side device 2800 of the embodiment of the present application further comprises instructions or programs stored in the memory 288 and executable on the processor 284. The processor 284 calls the instructions or programs in the memory 288 to perform the method executed by each module shown in FIG. 25 and achieve the same technical effects. To avoid repetition, details are not described herein.

[0354] The embodiment of the present application further provides a readable storage medium, and the readable storage medium stores programs or instructions, which are executed by a processor to implement the processes of the tail code transmission method embodiment and achieve the same technical effects. To avoid repetition, details are not described herein.

[0355] The processor is the processor in the terminal in the above embodiments. The readable storage medium includes a computer readable storage medium, such as a computer readable only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc. In some examples, the readable storage medium can be a non-transitory readable storage medium.

[0356] The embodiment of the present application further provides a chip, which includes a processor and a communication interface. The communication interface is coupled with the processor. The processor is configured to run programs or instructions to implement the processes of the tail code transmission method embodiment and achieve the same technical effects. To avoid repetition, details are not described herein.

[0357] It should be understood that the chip mentioned in the embodiment of the present application can also be referred to as a system chip, a system chip, a chip system or a system on chip, etc.

[0358] The embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the processes of the tail code transmission method embodiment and achieve the same technical effects. To avoid repetition, details are not described herein.

[0359] The embodiment of the present application further provides a communication system, which includes a first device and a second device. The first device can be used to execute the steps of the tail code transmission method. The second device can be used to execute the steps of the tail code transmission method.

[0360] It should be noted that, in the present document, the terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can also include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises a", "comprising", or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element. Furthermore, it is to be understood that the methods and apparatuses of the present application can be carried out by specific hardware, by software, or by a combination of hardware and software. It is therefore, contemplated to this patent to cover any and all modifications, variations, or equivalents that fall within the scope of the present application. Accordingly, where a concept can have been illustrated in only one of the exemplary embodiments, various aspects of the concept can be modified and / or combined to produce a variety of other embodiments that are not specifically illustrated. Thus, for purposes of describing particular embodiments, reference has been made to orientations. However, it is to be understood that the teachings of this patent are not limited in their application to any one of the mentioned orientations, but are applicable to any assembly having the features currently described or hereinafter ascertained.

[0361] From the above description of the embodiments, it is apparent that the method of the above embodiments can be realized by means of a computer software product and general hardware platform, of course, it can also be realized by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disc, optical disc, etc.), and includes a plurality of instructions for making the terminal or network side device execute the method described in each embodiment of the present application.

[0362] The embodiments of the present application are described above in combination with the drawings, but the present application is not limited to the above specific embodiments, and the above specific embodiments are only illustrative, but not restrictive. Those skilled in the art can make many forms of embodiments under the inspiration of the present application without departing from the scope of the present application and the protection scope of the claims, and these embodiments all belong to the protection scope of the present application.

Claims

1. A tail code transmission method, comprising: a first device sending or receiving the tail code based on first information; the first information comprising at least one of the following: first predefined information, first configuration information, first indication information, and a transmission format of a data part. 2.The method of claim 1, wherein a transmission format of the tail code is associated with the transmission format of the data part, and the association is determined based on at least one of the following: second predefined information, second configuration information, and second indication information. 3.The method of claim 1 or 2, wherein the tail code satisfies at least one of the following rules: a frequency of the tail code is different from a frequency of the data part; a chip rate of the tail code is different from a chip rate of the data part; an encoding of the tail code is different from an encoding of the data part; a number of subcarrier periods corresponding to each bit of the tail code is different from a number of subcarrier periods corresponding to each bit of the data part; the tail code comprises check bits generated based on the data part; the tail code comprises a predefined sequence; 4. The method of claim 3, wherein, the tail code and the data part are connected by a delimiter. Before the sending or receiving the tail code, the method further comprises:

5. The method according to any one of claims 1-3, wherein, the first device determining at least one rule that the tail code satisfies based on at least one of a transmission type and a data length of the data part. The first device sending the tail code based on the first information comprises: the first device determining whether to send the tail code based on the first information; in a case where it is determined to send the tail code, the first device determining a transmission format of the tail code based on second information; the second information comprising at least one of the following:

6. The method according to any one of claims 1-3, wherein, first predefined information, first configuration information, first indication information, and the transmission format of the data part; the first device sending the tail code to a second device based on the transmission format of the tail code. The first device receiving the tail code based on the first information comprises: the first device determining whether the tail code is sent by a second device based on the first information; 7. The method of claim 5 or 6, wherein, in a case where it is determined that the tail code is sent by the second device, the first device determining a transmission format of the tail code based on second information; the second information comprising at least one of the following: first predefined information, first configuration information, first indication information, and the transmission format of the data part; the first device receiving the tail code sent by the second device based on the transmission format of the tail code. The first device determining the transmission format of the tail code based on the second information comprises: the first device determining at least one rule that the tail code satisfies based on at least one of a transmission type and a data length of the data part; the first device determining the transmission format of the tail code based on the second information and the at least one rule that the tail code satisfies. 8.The method of claim 4 or 7, wherein the transmission type comprises at least one of the following: uplink transmission, downlink transmission, data transmission, and signaling transmission, the signaling transmission comprising at least one signaling type of signaling transmission. 9.A tail code transmission method, comprising: a second device sending or receiving the tail code based on third information; the third information comprising at least one of the following: a transmission format of the first predefined information, the first configuration information, the third indication information and the data part. 10.The method of claim 9, wherein, a transmission format of the tail code is associated with a transmission format of the data part, and the association is determined based on at least one of the following: second predefined information, second configuration information and fourth indication information. 11.The method of claim 9 or 10, wherein, the tail code satisfies at least one of the following rules: a frequency of the tail code is different from a frequency of the data part; a chip rate of the tail code is different from a chip rate of the data part; an encoding of the tail code is different from an encoding of the data part; a number of subcarrier periods corresponding to each bit of the tail code is different from a number of subcarrier periods corresponding to each bit of the data part; the tail code comprises check bits generated based on the data part; the tail code comprises a predefined sequence; the tail code and the data part are connected by a delimiter.

12. The method of claim 11, wherein, Before the sending or receiving the tail code, the method further comprises: the second device determines at least one rule that the tail code satisfies based on at least one of a transmission type and a data length of the data part.

13. The method according to any one of claims 9-12, wherein, the second device sends the tail code based on the third information, comprising: the second device determines whether to send the tail code based on the third information; in a case where it is determined to send the tail code, the second device determines a transmission format of the tail code based on fourth information; the fourth information comprises at least one of the following: first predefined information, first configuration information, third indication information and a transmission format of the data part; the second device sends the tail code to the first device based on the transmission format of the tail code.

14. The method of any one of claims 9-12, wherein, the second device receives the tail code based on the third information, comprising: the second device determines whether the first device sends the tail code based on the third information; in a case where it is determined that the first device sends the tail code, the second device determines a transmission format of the tail code based on fourth information; the fourth information comprises at least one of the following: first predefined information, first configuration information, third indication information and a transmission format of the data part; the second device receives the tail code sent by the first device based on the transmission format of the tail code.

15. The method of claim 13 or 14, wherein, the second device determines the transmission format of the tail code based on the fourth information, comprising: the second device determines at least one rule that the tail code satisfies based on at least one of a transmission type and a data length of the data part; the second device determines the transmission format of the tail code based on the fourth information and the at least one rule that the tail code satisfies. 16.The method of claim 12 or 15, wherein, the transmission type comprises at least one of the following: uplink transmission, downlink transmission, data transmission and signaling transmission, and the signaling transmission comprises at least one signaling type of signaling transmission. 17.An apparatus for tail code transmission, comprising: a transmission module configured to send or receive the tail code based on first information; the first information comprises at least one of the following: first predefined information, first configuration information, first indication information and a transmission format of the data part.

18. The apparatus of claim 17, wherein, the trailer code satisfies at least one of the following rules: a frequency of the trailer code is different from a frequency of the data portion; a chip rate of the trailer code is different from a chip rate of the data portion; an encoding of the trailer code is different from an encoding of the data portion; a number of subcarrier periods corresponding to each bit of the trailer code is different from a number of subcarrier periods corresponding to each bit of the data portion; the trailer code comprises check bits generated based on the data portion; the trailer code comprises a predefined sequence; the trailer code and the data portion are connected with a delimiter.

19. The apparatus of claim 17, wherein, The transmission module is further configured to: determine the at least one rule satisfied by the trailer code based on at least one of a transmission type and a data length of the data portion.

20. An apparatus for trailer code transmission, comprising: a transmission module configured to transmit or receive the trailer code based on third information; the third information comprises at least one of the following: first predefined information, first configuration information, third indication information, and a transmission format of the data portion.

21. The apparatus of claim 20, wherein, the trailer code satisfies at least one of the following rules: a frequency of the trailer code is different from a frequency of the data portion; a chip rate of the trailer code is different from a chip rate of the data portion; an encoding of the trailer code is different from an encoding of the data portion; a number of subcarrier periods corresponding to each bit of the trailer code is different from a number of subcarrier periods corresponding to each bit of the data portion; the trailer code comprises check bits generated based on the data portion; the trailer code comprises a predefined sequence; the trailer code and the data portion are connected with a delimiter.

22. The apparatus of claim 21, wherein, The transmission module is further configured to: determine the at least one rule satisfied by the trailer code based on at least one of a transmission type and a data length of the data portion.

23. A first device comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implement the steps of the trailer code transmission method according to any one of claims 1 to 8.

24. A second device comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implement the steps of the trailer code transmission method according to any one of claims 9 to 16.

25. A readable storage medium, the readable storage medium storing programs or instructions, the programs or instructions, when executed by a processor, implement the trailer code transmission method according to any one of claims 1 to 8, or implement the steps of the trailer code transmission method according to any one of claims 9 to 16.

Images