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-references

[0002] This 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. Technical Field

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

[0004] Current R19 research on the Ambient Internet of Things (AIoT) considers using postambles in downlink / uplink channels to indicate the end of uplink / downlink transmission. Postambles can also be used for channel estimation, correction of sampling frequency offset (SFO), and better time synchronization.

[0005] Therefore, for those skilled in the art, how to transmit the tail code is a technical problem that needs to be solved urgently. Summary of the Invention

[0006] To address the problems in the related art, 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 the first information;

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

[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 the third information;

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

[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 device is provided, comprising:

[0016] A transmission module, configured to send or receive 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 the transmission format of the data part.

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

[0020] A transmission module, configured to send 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 the 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 a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the tail code transmission method as described in the first aspect are implemented.

[0024] In the sixth aspect, a first device is provided, comprising a processor and a communication interface, wherein the processor is used to send or receive the tail code based on first information; 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 the seventh aspect, a second device is provided, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the tail code transmission method as described in the second aspect are implemented.

[0026] In the eighth aspect, a second device is provided, comprising a processor and a communication interface, wherein the processor is used to send or receive the tail code based on third information; 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, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the tail code transmission method as described in the first aspect are implemented, or the steps of the tail code transmission method as described in the second aspect are implemented.

[0028] In the tenth aspect, a wireless communication system is provided, comprising: a first device and a second device, wherein the first device can be used to execute the steps of the tail code transmission method as described in the first aspect, and the second device can be used to execute the steps of the tail code transmission method as described in the second aspect.

[0029] In the eleventh aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the tail code transmission method as described in the first aspect, or to implement the tail code transmission method as described in the second aspect.

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

[0031] In an embodiment of the present application, the first device sends 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 the transmission format of the data part. The above scheme can realize the sending or receiving of the tail code based on the first information, has greater flexibility, and can improve the transmission performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] FIG1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application;

[0033] FIG2 is a schematic diagram of an A-IOT architecture provided in an embodiment of the present application;

[0034] FIG3 is a second schematic diagram of an A-IOT architecture diagram provided in an embodiment of the present application;

[0035] FIG4 is a schematic diagram of FMO encoding provided in an embodiment of the present application;

[0036] FIG5 is one of the schematic diagrams of the FMO encoding state provided in an embodiment of the present application;

[0037] FIG6 is a second schematic diagram of the FMO encoding state provided in an embodiment of the present application;

[0038] FIG7 is a state transition diagram of FM0 provided in an embodiment of the present application;

[0039] FIG8 is one of the schematic diagrams of the Preamble of the FMO code provided in an embodiment of the present application;

[0040] FIG9 is a second schematic diagram of the Preamble of the FMO code provided in an embodiment of the present application;

[0041] FIG10 is a schematic diagram of the end data of the FM0 code provided in an embodiment of the present application;

[0042] FIG11 is a schematic diagram of Miller coding provided in an embodiment of the present application;

[0043] FIG12 is one of the Miller encoding state diagrams provided in an embodiment of the present application;

[0044] FIG13 is a second schematic diagram of the Miller encoding state provided in an embodiment of the present application;

[0045] FIG14 is a Miller state transition diagram provided in an embodiment of the present application;

[0046] FIG15 is a schematic diagram of a preamble of Miller coding provided in an embodiment of the present application;

[0047] FIG16 is a second schematic diagram of a Miller-coded Preamble provided in an embodiment of the present application;

[0048] FIG17 is a waveform diagram of Miller coding provided in an embodiment of the present application;

[0049] FIG18 is a schematic diagram of the end data of Miller encoding provided in an embodiment of the present application;

[0050] FIG19 is a schematic diagram showing the relationship between chip rate and BLF provided in an embodiment of the present application;

[0051] FIG20 is a schematic diagram of PIE encoding provided in an embodiment of the present application;

[0052] FIG21 is a schematic diagram of Manchester encoding provided in an embodiment of the present application;

[0053] FIG22 is a flow chart of one of the tail code transmission methods provided in an embodiment of the present application;

[0054] FIG23 is a second flow chart of a tail code transmission method according to an embodiment of the present application;

[0055] FIG24 is a schematic diagram of a structure of a tail code transmission device according to an embodiment of the present application;

[0056] FIG25 is a second structural diagram of the tail code transmission device provided in an embodiment of the present application;

[0057] FIG26 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0058] FIG27 is a schematic diagram of the structure of the terminal of an embodiment of the present application

[0059] Figure 28 is a structural diagram of the network side device of an embodiment of the present application. DETAILED DESCRIPTION

[0060] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0061] The terms "first", "second", etc. in this 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 are interchangeable where appropriate, 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" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0062] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0063] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, 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 technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative 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) systems. th Generation, 6G) communication system.

[0064] FIG1 shows a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be an IoT device, an A-IoT device, a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer, a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device, an aircraft (flight vehicle), a vehicle user equipment (VUE), a ship-borne device, a pedestrian user equipment (PUE), a smart home (home appliance with wireless communication capabilities, such as a refrigerator, a television, a washing machine, or furniture), a game console, a personal computer (PC), a teller machine, or a self-service machine, or other terminal-side device. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called 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 embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0065] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, 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 this application are introduced:

[0067] 1. AIoT device types:

[0068] The 3GPP R19 A-IoT study characterizes ambient IoT devices based on their energy storage capacity and their ability to generate radio frequency signals for transmission. A-IoT devices are categorized into the following types:

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

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

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

[0072] Devices with different energy storage capabilities also affect their transmission quality. Generally, devices with higher energy storage capabilities also have higher receive sensitivity or higher transmit power, which can better ensure the reliability of the receive or transmit link.

[0073] 2. AIoT business types:

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

[0075] 1. DO: Device-originated

[0076] 2. DT: Device-terminated

[0077] DO data refers to data originating from an A-IoT device (similar to a radio frequency identification (RFID) tag), and DT data refers to data transmitted to an A-IoT device. DO data, which originates from an A-IoT device, can be further categorized as follows:

[0078] 1-1. DO-A: DO autonomous, meaning AIoT devices independently initiate data transmission;

[0079] For example: connecting a large number of various sensors that collect and, when necessary, actively report information about the environment, equipment, and organisms.

[0080] 1-2. DO-DTT, DO device-terminated triggered, that is, a reader device such as a base station triggers the AIoT device to initiate data transmission;

[0081] For example, in asset identification, status reporting, and tracking, the Reader collects data from the Tag by triggering an inventory process. Since the data is generated / initiated in the IoT device, this service should be considered as a DO service initiated by the Tag via a control command from the Reader.

[0082] 3. AIoT topology type (Topology):

[0083] As shown in Figure 2, Topology 1: Network devices (such as BS) communicate with A-IoT devices;

[0084] As shown in Figure 3, Topology 2: Network devices (such as BS) communicate with intermediate nodes and A-IoT devices.

[0085] 4. Introduction to common line codes:

[0086] For the tag to reader (uplink), RFID uses two encoding methods: FM0 and Miller code; for the reader to tag (downlink), RFID uses pulse interval encoding (PIE) encoding.

[0087] The following are introductions to FM0, Miller, PIE and the common Manchester encoding:

[0088] 1. FM0

[0089] FM0 coding (also known as Bi-Phase Space Coding) has memory, meaning that the timing selection of FM0 depends on the previous transmission form. FM0 coding works by using level changes within a bit window to represent logic. If the level flips at the beginning of the bit window, it represents a logical "1." If the level flips in the middle of the bit window in addition to the beginning of the bit window, it represents a logical "0." (That is, FM0 coding has a jump at the beginning of each bit of data. If there is also 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 coding, it can be found that regardless of whether the transmitted data is 0 or 1, a jump must occur at the beginning of the bit window, as shown in Figure 4.

[0090] FM0 encoding defines four states, where state S2 or state S3 represents data-0, as shown in FIG5 ; state S1 or state S4 represents data-1, as shown in FIG6 .

[0091] In addition, there is a transition relationship between the four states. For example, state S1 can be transformed into state S3 or S4, and state S2 can be transformed into S2 or S1. The specific state transition diagram is shown in Figure 7.

[0092] Two types of preambles are sent before data. The TRext value in the Query command determines which preamble is used. Figure 8 shows TRext = 0, while Figure 9 shows TRext = 1. "v" indicates an FM0 collision, meaning no phase flip occurs. This distinguishes the preamble from the data. FM0 signal encoding always ends data transmission with a 1-bit "dummy" data signal, as shown in Figure 10.

[0093] 2. Miller

[0094] Miller codes, also known as delay modulation codes, can be considered a variation of biphase codes. In Miller basic codes, signal edges transition only when the value is 0->0 (indicating that two adjacent bits are 0). For Miller-modulated subcarrier signals, each bit (Miller basic symbol) must consist of 2, 4, or 8 subcarrier periods, determined by the value of M in the query. Figure 11 shows a schematic diagram of the Miller basic code "000."

[0095] Similar to FM0 encoding, Miller encoding also has four states: state S1 or S4 represents data-0, as shown in Figure 12; state S2 or S3 represents data-1, as shown in Figure 13. The corresponding state transition relationships are shown in Figure 14.

[0096] The Miller subcarrier signal starts transmission through one of two preambles. The TRext value in the Query command that initiates the inventory determines which preamble is used. In Figure 15, it is Trext=0, and in Figure 16, it is Trext=1.

[0097] As shown in FIG15 , the encoding method of M=2 and TRext=0 is adopted; the Miller encoding rule is described as follows:

[0098] (1) If the current bit state is 1, the beginning of the signal is equal to the end of the previous signal, and the middle jumps;

[0099] (2) If the current bit state is 0 and the previous signal is 1, the beginning of the signal is equal to the end of the previous signal, and there is no jump in the middle;

[0100] (3) If the current bit state is 0 and the previous signal is 0, the beginning of the signal is equal to the transition at the end of the previous signal, and there is no transition in the middle.

[0101] Suppose there is a string of data to be encoded: "010111." The first data bit is '0'. According to the normal encoding method, the second data bit is '1', which meets the above rule 1. In this case, the beginning of the signal is equal to the end of the previous signal, with a transition in the middle. The third data bit is '0', which meets the above rule 2. In this case, the beginning of the signal is equal to the end of the previous signal, with no change in the middle. The fourth data bit is '1', which meets the above rule 1. In this case, the beginning of the signal is equal to the end of the previous signal, with a transition in the middle. The fifth data bit is '1', which meets the above rule 1. In this case, the beginning of the signal is equal to the end of the previous signal, with a transition in the middle. The sixth data bit is '1', which meets the above rule 1. In this case, the beginning of the signal is equal to the end of the previous signal, with a transition in the middle. The final encoded waveform is shown in Figure 17.

[0102] Miller coding also always ends data transmission with a 1-bit signal of "dummy" data 1, as shown in FIG18 .

[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 one cycle of BLF is shown in Figure 19. The time of one bit in FM0 is T cycle , each bit time in Miller-2 / 4 / 8 is 2*T cycle 、4*T cycle 、8*T cycle .

[0104] 3. PIE

[0105] In pulse interval encoding (PIE), data-0 and data-1 are shown in FIG20 , where Tari is the reference time interval, PW (Pulsewidth) is the pulse width, the duration of data-0 is Tari, and the duration of data-1 is 1.5-2Tari.

[0106] 4. Manchester

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

[0108] In the embodiment of the present application, the tail code may also be called Postamble, post-synchronization code, post-synchronization sequence, post-synchronization signal, etc., which is not limited in the embodiment of the present application.

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

[0110] The second device (such as a reading and writing device): a handheld or fixed device that reads (and sometimes writes) tag information. It can also be understood as a device that communicates with the tag. For example, it can be a terminal, a base station, or a device with reading and writing functions, such as a reader. The specific details are not limited here. The reading and writing device can send carrier excitation signals and control commands.

[0111] Optionally, the tail code transmission includes downlink transmission of a signal sent from the second device to the first device, and also includes uplink transmission of a signal sent from the first device to the second device, without limitation.

[0112] The tail code transmission method provided by the embodiment of the present application is described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0113] Referring to FIG. 22 , an embodiment of the present application provides a tail code transmission method. The embodiment is performed by a first device. The method includes:

[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 predefined information, the first configuration information, the first indication information and the transmission format of the data part.

[0117] In some embodiments, the tail code may be a sequence following the data portion, and the first device may send or receive the tail code based on at least one of the first predefined information, the first configuration information, the first indication information, and the transmission format of the data portion.

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

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

[0120] Optionally, the first device sends or receives the tail code via first configuration information, where the first configuration information is sent by the second device or forwarded by the network-side device via the second device. Optionally, when the second device is a network-side device, the first configuration information may be carried via control signaling.

[0121] Optionally, the tail code is sent or received via the first indication information. Optionally, the first indication information is indication information of a network-side device sent by the second device or forwarded by the second device. Optionally, in the case of forwarding (as in the scenario shown in FIG3 ), the second device may parse and re-encapsulate the information before sending it, or send it directly. For example, in the scenario shown in FIG2 , the second device dynamically or semi-statically indicates whether to transmit the tail code via downlink control signaling.

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

[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 send 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 one or some transmission types, the tail code can be transmitted, and for one or some transmission types, the tail code is not transmitted. For example, for a transmission type of a certain signaling transmission, the tail code may not be transmitted. For example, if the data length of the data part is less than or equal to a certain threshold, the tail code may not be transmitted, and if the data length of the data part is greater than a certain threshold, the tail code may be transmitted. The above-mentioned data part refers to what is transmitted before the tail code is sent, and can be data, signaling, or preamble, etc., without limitation.

[0124] In the tail code transmission method of this embodiment, the first device sends or receives the tail code based on first information; 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. In the above scheme, the tail code can be sent or received based on the first information, which is more flexible and can improve transmission performance.

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

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

[0127] In some embodiments, the association relationship 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 may 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 implementation, the correlation between the tail code and the data portion is determined in a variety of ways, which is relatively 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 portion;

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

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

[0135] (5) The tail code includes a check digit generated based on the data portion;

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

[0137] (7) The tail code and the data portion are connected with a separator.

[0138] For (1), for example, for uplink transmission from the Tag (first device) to the Reader (second device), the BLF used by the tail code is associated with the BLF of the data portion. For example, the BLF of the tail code is twice, half, or X times the BLF of the data portion. X can be determined by the Reader or based on preconfigured / predefined information or rules. For example, the Tag determines that the BLF used in the uplink data transmission portion is 80 kHz based on the Reader's downlink indication. If the BLF of the predefined tail code is twice the BLF of the data transmission portion, then the backscatter frequency used by the tail code is BLF = 160 kHz.

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

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

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

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

[0143] In the above embodiment, by allowing the tail code to use a frequency / chip rate / coding / number of subcarrier cycles different from that of the data part, it can be ensured that the same level pattern as the tail code cannot appear in the data transmission, thereby improving the accuracy of tail code monitoring and reducing the false detection rate of the tail code.

[0144] Optionally, in some embodiments, it is not necessary to additionally define a tail code sequence, and the tail code sequence can be obtained by using a check bit generated based on the data portion. For example, a cyclic redundancy check (CRC) check bit can be generated based on the data portion and a CRC generator polynomial, and the CRC check bit can be used as a postamble sequence to reduce the transmission load.

[0145] Optionally, the data portion and the tail code are connected with a delimiter (or the tail code starts with a delimiter);

[0146] In some embodiments, the delimiter is at least 1 bit, and the delimiter can be a violation, that is, the encoding rule used for the delimiter is opposite to or different from the encoding rule of the data portion. For example, in FM0 encoding, no level jump occurs between the delimiter and the previous bit (the previous bit is a bit in the data portion) (the normal encoding rule is that a level jump occurs); for another example, in Miller encoding, if the last bit of the data portion is 1 and the delimiter is bit 0, then the beginning of the tail code corresponding to the delimiter jumps with the end of the previous signal (i.e., the last bit of the data portion) (the normal encoding rule is that it is equal to the end of the previous signal); for another example, in Manchester, continuous high-level or low-level symbols are used as delimiters (the normal encoding rule is that there is a jump in the middle of the bit window), or in PIE encoding, the Tari value used for encoding is different from the Tari value of the data portion, for example, using X times the Tari value of the data portion to encode as the delimiter.

[0147] In the above implementation, the data portion and the tail code are separated by a delimiter, so that the starting position of the tail code can be determined, thereby reducing the complexity of tail code detection.

[0148] The above-mentioned (1)-(7) can be used together. For example, the CRC check sequence generated based on the data portion is used as the tail code sequence. The tail code and the data portion are connected by a delimiter, and the backscatter frequency and encoding method of the tail code are different from the backscatter frequency and encoding method of the data portion. Among them, for the same tail code, (5) and (6) are generally not used at the same time.

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

[0150] The frequency of the tail code is different from the frequency of the middle symbol;

[0151] The chip rate of the tail code 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 intermediate symbol may also be called Midamble, synchronization symbol, timing tracking symbol or intermediate identifier, etc.

[0155] Among them, intermediate symbols can be inserted in the data part.

[0156] Optionally, 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 of the data portion.

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

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

[0159] Wherein, uplink transmission refers to transmission from the first device to the second device;

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

[0161] The above-mentioned different transmission types include but are not limited to: uplink transmission, downlink transmission, data transmission, and signaling transmission; further, signaling transmission may also include transmission of different signaling types, such as read command / write command, etc.

[0162] In some embodiments, the tail code is determined by combining different rules according to different transmission types.

[0163] For example, for signaling transmission and data transmission, the transmission format of the tail code can be determined separately. For a signaling command without CRC (such as a Query command), the tail code can be based on violation + a predefined sequence, or only violation can be used as the tail code, or it can be considered that there is no tail code (for example, for a command with a fixed bit length, there is no need to transmit a tail code); for 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 may be determined based on the different data lengths of the data portion of the transmission (including signaling / data). For example, the transmission format of the tail code may be determined based on the data length (e.g., bit length) of the signaling / data. For example, when the bit length of the data portion is less than or equal to a predefined threshold, a CRC check bit is used as the tail code. When the bit length of the data portion is greater than the threshold, a predefined sequence (e.g., a sequence longer than the CRC check sequence) is used as the tail code.

[0166] Optionally, the first device sending or receiving the tail code based on the first information includes:

[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 the transmission format of the data part;

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

[0172] In some embodiments, the first device determines whether to send a tail code based on the first information. If it is determined to send a tail code, the first device determines the transmission format of the tail code based on the second information, and sends the tail code to the second device based on the transmission format of the tail code. This has greater reliability and can improve transmission performance.

[0173] Optionally, whether to transmit the tail code and the transmission format of the tail code (for example, at least one of the used frequency, chip rate, coding, number of subcarriers corresponding to each bit, and 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 obtains the format of the tail code received by the first device in the downlink and the format of the tail code sent in the uplink through the first configuration information. Then, the first device and the second device send and receive the tail code according to this format.

[0175] Optionally, whether to transmit the tail code and the transmission format of the tail code are determined by the first indication information sent by the second device. For example, the second device indicates the format of the downlink tail code through the first indication information, and indicates the format of the tail code to be transmitted uplink by the first device next.

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

[0177] Optionally, the above methods can be used in combination, that is, multiple combinations 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 portion.

[0179] Optionally, the first device receiving the tail code sent by the second device based on the first information includes:

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

[0181] In the case where it is determined that the second device sends the tail code, the first device determines a 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 a transmission format of a data portion;

[0182] The first device receives the tail code sent 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 sends a tail code based on the first information. If it is determined that the second device sends a tail code, the first device determines the transmission format of the tail code based on the second information, and receives the tail code sent by the second device based on the transmission format of the tail code, so as to correctly parse the tail code and improve the accuracy of signal detection.

[0184] Optionally, the first device determining, based on the second information, a transmission format of the tail code includes:

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

[0186] The first device determines a transmission format of the tail code based on the second information and 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 data length of the data part, that is, at least one information required to determine the transmission format of the tail code. Furthermore, it can also determine the transmission format ultimately adopted by the tail code based on the second information and at least one rule satisfied by the tail code.

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

[0189] Frequency, chip rate, coding, number of subcarrier cycles corresponding to each bit, sequence format used, delimiter, and data length.

[0190] It should be noted that the transmission format is only a summary of the information required to transmit the tail code. Other names may also be used in other embodiments, and the embodiments of the present application are not limited to this.

[0191] Referring to FIG. 23 , an embodiment of the present application provides a tail code transmission method. The embodiment is performed by a second device. The method includes:

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

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

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

[0195] In some embodiments, the second device may send 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 portion. For example, the second device may determine whether to transmit the tail code based on at least one of the first information.

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

[0197] Optionally, the third indication information is indication information of a network side device sent 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 portion, and the association is determined based on at least one of the following: second predefined information, second configuration information, and fourth indication information. The fourth indication information may be information sent by the first device to the second device, or may be indication information of a network-side device sent directly by the first device or forwarded by the first device. Optionally, the second configuration information may be configuration information pre-configured in the second device or sent 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 portion;

[0201] The chip rate of the tail code is different from the chip rate of the data portion;

[0202] The encoding of the tail code is different from the encoding of the data portion;

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

[0204] The tail code includes a check digit generated based on the data portion;

[0205] The tail code includes a predefined sequence;

[0206] The tail code and the data portion are connected with a separator.

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

[0208] The second device determines at least one rule satisfied by the tail code based on at least one of a transmission type and a data length of the data portion.

[0209] Optionally, the second device sending the tail code based on the third information includes:

[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 a transmission format of the tail code.

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

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

[0215] When 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 includes at least one of the following: first predefined information, first configuration information, third indication information, and a transmission format of a data portion;

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

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

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

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

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

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

[0222] The method provided in the embodiment of the present application is the same as the various processes implemented in the method embodiment shown in Figure 22, and achieves the same technical effect. To avoid repetition, it will not be repeated here.

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

[0224] FIG24 is a schematic diagram of a structure of a tail code transmission device provided in an embodiment of the present application. As shown in FIG24 , the tail code transmission device is applied to a first device, and the tail code transmission device includes:

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

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

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

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

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

[0230] The frequency of the tail code is different from the frequency of the data portion;

[0231] The chip rate of the tail code is different from the chip rate of the data portion;

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

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

[0234] The tail code includes a check digit generated based on the data portion;

[0235] The tail code includes a predefined sequence;

[0236] The tail code and the data portion are connected with a separator.

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

[0238] At least one rule satisfied by the tail code is determined based on at least one of a transmission type and a data length of the data portion.

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

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

[0241] In the case of determining to send the tail code, determining 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 the transmission format of the data part;

[0242] The tail code is sent to the second device based on a transmission format of the tail code.

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

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

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

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

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

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

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

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

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

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

[0253] The tail code transmission device provided in the embodiment of the present application can implement each process implemented by the method embodiment shown in Figure 22 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0254] FIG25 is a second structural diagram of a tail code transmission device provided in an embodiment of the present application. As shown in FIG25 , the tail code transmission device is applied to a second device, and the tail code transmission device includes:

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

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

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

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

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

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

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

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

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

[0264] The tail code includes a check digit generated based on the data portion;

[0265] The tail code includes a predefined sequence;

[0266] The tail code and the data portion are connected with a separator.

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

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

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

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

[0271] In the case of determining to send the tail code, determining 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;

[0272] The tail code is sent to the first device based on a transmission format of the tail code.

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

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

[0275] In the case where it is determined that the first device sends the tail code, determining a 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 a transmission format of a data portion;

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

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

[0278] Determining at least one rule satisfied by the tail code based on at least one of a transmission type and a data length of the data portion;

[0279] A transmission format of the tail code is determined based on the fourth information and at least one rule satisfied by the tail code.

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

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

[0282] The tail code transmission device provided in the embodiment of the present application can implement each process implemented by the method embodiment shown in Figure 23 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0283] The tail code transmission device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and the other device can be a server, a network attached storage (NAS), etc., which is not specifically limited in the embodiment of the present application.

[0284] The tail code transmission device provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 22 to 23 and achieve the same technical effects. To avoid repetition, they will not be described here.

[0285] As shown in Figure 26, an embodiment of the present application further provides a communication device 2600, including a processor 2601 and a memory 2602. The memory 2602 stores a program or instruction that can be run on the processor 2601. For example, when the communication device 2600 is a terminal, the program or instruction, when executed by the processor 2601, implements the various steps of the above-mentioned embodiment of the tail code transmission method and can achieve the same technical effect. When the communication device 2600 is a network-side device, the program or instruction, when executed by the processor 2601, implements the various steps of the above-mentioned embodiment of the tail code transmission method and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0286] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in Figure 22 or Figure 23. This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 27 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0287] The terminal 2700 includes but is not limited to: 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 at least some of the components of the processor 2710.

[0288] Those skilled in the art will appreciate that terminal 2700 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to processor 2710 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG27 does not limit the terminal. The terminal may include more or fewer components than shown, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0289] It should be understood that in an embodiment of the present application, the input unit 2704 may include a graphics processing unit (GPU) 27041 and a microphone 27042, and the graphics processor 27041 processes the image data of a static picture or 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 may include a display panel 27061, and the display panel 27061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 2707 includes a touch panel 27071 and at least one of other input devices 27072. The touch panel 27071 is also called a touch screen. The touch panel 27071 may include two parts: a touch detection device and a touch controller. Other input devices 27072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0290] In the embodiment of the present application, after receiving downlink data from the network-side device, the RF unit 2701 can transmit the data to the processor 2710 for processing. In addition, the RF unit 2701 can send uplink data to the network-side device. Generally, the RF unit 2701 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0291] Memory 2709 can be used to store software programs or instructions and various data. Memory 2709 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, memory 2709 may include volatile memory or non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 2709 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0292] Processor 2710 may include one or more processing units. Optionally, processor 2710 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 2710.

[0293] The radio frequency unit 2701 is configured to send 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 portion, and the association is determined based on at least one of the following: second predefined information, second configuration information, and 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 portion;

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

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

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

[0302] The tail code includes a check digit generated based on the data portion;

[0303] The tail code includes a predefined sequence;

[0304] The tail code and the data portion are connected with a separator.

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

[0306] At least one rule satisfied by the tail code is determined based on at least one of a transmission type and a data length of the data portion.

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

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

[0309] In the case of determining to send the tail code, determining the transmission format of the tail code based on second information; 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] The tail code is sent to the second device based on a transmission format of the tail code.

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

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

[0313] In a case where it is determined that the second device sends the tail code, determining a transmission format of the tail code based on second information, wherein the first information includes at least one of the following: first predefined information, first configuration information, first indication information, and a transmission format of a data portion;

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

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

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

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

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

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

[0320] The radio frequency unit 2701 is configured to send or receive the tail code based on the third information;

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

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

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

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

[0325] The frequency of the tail code is different from the frequency of the data portion;

[0326] The chip rate of the tail code is different from the chip rate of the data portion;

[0327] The encoding of the tail code is different from the encoding of the data portion;

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

[0329] The tail code includes a check digit generated based on the data portion;

[0330] The tail code includes a predefined sequence;

[0331] The tail code and the data portion are connected with a separator.

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

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

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

[0335] determining, based on the third information, whether to send the tail code;

[0336] In the case of determining to send the tail code, determining 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;

[0337] The tail code is sent to the first device based on a transmission format of the tail code.

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

[0339] determining, based on the third information, whether the first device sends the tail code;

[0340] In the case where it is determined that the first device sends the tail code, determining a 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 a transmission format of a data portion;

[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 configured to:

[0343] Determining at least one rule satisfied by the tail code based on at least one of a transmission type and a data length of the data portion;

[0344] A transmission format of the tail code is determined based on the fourth information and at least one rule satisfied by the tail code.

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

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

[0347] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment shown in Figure 22 or Figure 23, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0348] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG23 . This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this network-side device embodiment and can achieve the same technical effects.

[0349] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 28, network-side device 2800 includes an antenna 281, a radio frequency device 282, a baseband device 283, a processor 284, and a memory 288. Antenna 281 is connected to radio frequency device 282. In the uplink direction, radio frequency device 282 receives information via antenna 281 and sends the received information to baseband device 283 for processing. In the downlink direction, baseband device 283 processes the information to be transmitted and sends it to radio frequency device 282. Radio frequency device 282 processes the received information and then sends it through antenna 281.

[0350] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 283 , which includes a baseband processor.

[0351] The baseband device 283 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 28, one of the chips is, for example, a baseband processor, which is connected to the memory 288 through a bus interface to call the program in the memory 288 and execute the network device operations shown in the above method embodiment.

[0352] The network side device may further include 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 also includes: 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 execute the methods of the modules shown in FIG25 and achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0354] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned tail code transmission method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

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

[0356] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned tail code transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0357] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0358] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-mentioned tail code transmission method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0359] An embodiment of the present application further provides a communication system, including: a first device and a second device, wherein the first device can be used to execute the steps of the tail code transmission method described above, and the second device can be used to execute the steps of the tail code transmission method described above.

[0360] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0361] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0362] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A tail code transmission method, comprising: The first device sends or receives the tail code based on the first information; The first information includes at least one of the following: The first predefined information, the first configuration information, the first indication information and the transmission format of the data part.

2. The method according to claim 1, wherein The transmission format of the tail code is associated with the transmission format of the data portion, 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 according to claim 1 or 2, wherein: The tail code satisfies at least one of the following rules: The frequency of the tail code is different from the frequency of the data portion; The chip rate of the tail code is different from the chip rate of the data portion; The encoding of the tail code is different from the encoding of the data portion; The number of subcarrier cycles corresponding to each bit of the tail code is different from the number of subcarrier cycles corresponding to each bit of the data part; The tail code includes a check digit generated based on the data portion; The tail code includes a predefined sequence; The tail code and the data portion are connected with a separator.

4. The method according to claim 3, wherein: Before sending or receiving the tail code, the method further includes: 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 of the data portion.

5. The method according to any one of claims 1 to 3, wherein: The first device sending the tail code based on the first information includes: The first device determines whether to send the tail code based on the first information; 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 the transmission format of the data part; The first device sends the tail code to the second device based on the transmission format of the tail code.

6. The method according to any one of claims 1 to 3, wherein: The first device receiving the tail code based on the first information includes: The first device determines, based on the first information, whether the second device sends the tail code; In the case where it is determined that the second device sends 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 the transmission format of the data part; The first device receives the tail code sent by the second device based on the transmission format of the tail code.

7. The method according to claim 5 or 6, wherein: The first device determining, based on the second information, a transmission format of the tail code, including: The first device determines, based on at least one of a transmission type and a data length of the data portion, at least one rule satisfied by the tail code; The first device determines a transmission format of the tail code based on the second information and at least one rule satisfied by the tail code.

8. The method according to claim 4 or 7, wherein: The transmission type includes at least one of the following: Uplink transmission, downlink transmission, data transmission and signaling transmission, wherein the signaling transmission includes signaling transmission of at least one signaling type.

9. A tail code transmission method, comprising: The second device sends or receives the tail code based on the third information; The third information includes at least one of the following: The first predefined information, the first configuration information, the third indication information and the transmission format of the data part.

10. The method according to claim 9, wherein: The transmission format of the tail code is associated with the transmission format of the data portion, 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 according to claim 9 or 10, wherein: The tail code satisfies at least one of the following rules: The frequency of the tail code is different from the frequency of the data portion; The chip rate of the tail code is different from the chip rate of the data portion; The encoding of the tail code is different from the encoding of the data portion; The number of subcarrier cycles corresponding to each bit of the tail code is different from the number of subcarrier cycles corresponding to each bit of the data part; The tail code includes a check digit generated based on the data portion; The tail code includes a predefined sequence; The tail code and the data portion are connected with a separator.

12. The method according to claim 11, wherein Before sending or receiving the tail code, the method further includes: The second device determines at least one rule satisfied by the tail code based on at least one of a transmission type and a data length of the data portion.

13. The method according to any one of claims 9 to 12, wherein: The second device sending the tail code based on the third information includes: The second device determines whether to send the tail code based on the third information; 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; The second device sends the tail code to the first device based on the transmission format of the tail code.

14. The method according to any one of claims 9 to 12, wherein: The second device receives the tail code based on the third information, including: The second device determines, based on the third information, whether the first device sends the tail code; When 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 includes at least one of the following: first predefined information, first configuration information, third indication information, and a transmission format of a data portion; The second device receives the tail code sent by the first device based on the transmission format of the tail code.

15. The method according to claim 13 or 14, wherein: The second device determines, based on the fourth information, a transmission format of the tail code, including: The second device determines at least one rule satisfied by the tail code based on at least one of a transmission type and a data length of the data portion; The second device determines a transmission format of the tail code based on the fourth information and at least one rule satisfied by the tail code.

16. The method according to claim 12 or 15, wherein: The transmission type includes at least one of the following: Uplink transmission, downlink transmission, data transmission and signaling transmission, wherein the signaling transmission includes signaling transmission of at least one signaling type.

17. A tail code transmission device, comprising: A transmission module, configured to send or receive the tail code based on the first information; The first information includes at least one of the following: The first predefined information, the first configuration information, the first indication information and the transmission format of the data part.

18. The device according to claim 17, wherein The tail code satisfies at least one of the following rules: The frequency of the tail code is different from the frequency of the data portion; The chip rate of the tail code is different from the chip rate of the data portion; The encoding of the tail code is different from the encoding of the data portion; The number of subcarrier cycles corresponding to each bit of the tail code is different from the number of subcarrier cycles corresponding to each bit of the data part; The tail code includes a check digit generated based on the data portion; The tail code includes a predefined sequence; The tail code and the data portion are connected with a separator.

19. The device according to claim 17, wherein The transmission module is further configured to: At least one rule satisfied by the tail code is determined based on at least one of a transmission type and a data length of the data portion.

20. A tail code transmission device, comprising: A transmission module, configured to send or receive the tail code based on the third information; The third information includes at least one of the following: The first predefined information, the first configuration information, the third indication information and the transmission format of the data part.

21. The device according to claim 20, wherein The tail code satisfies at least one of the following rules: The frequency of the tail code is different from the frequency of the data portion; The chip rate of the tail code is different from the chip rate of the data portion; The encoding of the tail code is different from the encoding of the data portion; The number of subcarrier cycles corresponding to each bit of the tail code is different from the number of subcarrier cycles corresponding to each bit of the data part; The tail code includes a check digit generated based on the data portion; The tail code includes a predefined sequence; The tail code and the data portion are connected with a separator.

22. The device according to claim 21, wherein The transmission module is further configured to: At least one rule satisfied by the tail code is determined 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, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the tail code transmission method according to any one of claims 1 to 8 are implemented.

24. A second device comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the tail code transmission method according to any one of claims 9 to 16 are implemented.

25. A readable storage medium storing a program or instruction, wherein when the program or instruction is executed by a processor, the method for transmitting a tail code according to any one of claims 1 to 8 is implemented, or the steps of the method for transmitting a tail code according to any one of claims 9 to 16 are implemented.

Images