A communication method and apparatus

Abstract

The application discloses a communication method and device. The method comprises the following steps: a terminal device receives first data, wherein the first data is data of a first service, the first service is a service allowing data error transmission or submission, and the first data is not subjected to CRC; and the terminal device submits the first data of a first logical channel. In the method, the first data is not subjected to CRC before being submitted. According to the method, even if the first data is erroneous during transmission, the erroneous submission of the first data is still performed. Compared with the CRC of the first data before submission, the first data cannot be submitted due to the error of the first data, so that the tolerance transmission gain of the data is obtained.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] Currently, when data is transmitted between the sending and receiving devices, the sending device needs to perform a cyclic redundancy check (CRC) on the data to be sent to ensure correct transmission. After receiving the data from the sending device, the receiving device performs a CRC check on the data. If the check fails, the data is discarded or the device waits for retransmission.

[0003] In scenarios where data transmission is crucial, such as semantic communication, the focus is on the meaning conveyed by the data. Even if errors occur during data transmission, it doesn't prevent the meaning of the data packet from being inferred from the received data. In such cases, how to transmit the data becomes a pressing issue. Summary of the Invention

[0004] This application provides a communication method and apparatus that performs error delivery of data when errors are permissible, thereby obtaining the error-tolerant transmission gain of the data.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] In a first aspect, embodiments of this application provide a first communication method, which can be executed by a first communication device. The first communication device can be a communication equipment or a communication device capable of supporting the functions required by the communication equipment to implement the method, such as a chip system. The first communication device can be a receiving end among the two ends of communication. Taking an example where the two ends of communication include an access network device and a terminal device, and the sending end is the access network device and the receiving end is the terminal device, the first communication device can be the terminal device or a unit or functional module inside the terminal device. For example, the first communication device can be a chip disposed in the terminal device, or the first communication device can be other components used to implement the functions of the terminal device. The method provided in the first aspect is described below with the example of the first communication device being the terminal device itself.

[0007] The communication method includes: a terminal device receiving first data, the first data being data of a first service, the first service being a service that allows data to be transmitted or delivered incorrectly, and the first data not undergoing CRC; and the terminal device delivering the first data carried by a first logical channel.

[0008] In this method, CRC is not performed on the first data before submission. This ensures that even if an error occurs during the transmission of the first data, the erroneous submission of the first data will still proceed. Compared to performing CRC on the first data before submission, this avoids the first data failing to be submitted due to errors, thus achieving a fault-tolerant transmission gain.

[0009] In a possible implementation, after delivering the first data carried by the first logical channel, the method further includes: the terminal device mapping the quality of service (QoS) stream containing the first data only to the first packet data convergence protocol (PDCP) layer entity through a service data adaptation protocol (SDAP) layer entity.

[0010] The first type of business can be considered a category of business. For this type of business, it can be predefined or agreed that the PDCP layer can only map data of this type of business.

[0011] In possible implementations, the integrity verification function of the first PDCP layer entity is not enabled, or the integrity verification function of the first PDCP layer entity is not allowed, or the first PDCP layer entity does not support / does not have the integrity verification function. When the first data is the data of the first service, the first PDCP layer entity will not perform integrity verification. Optionally, when the integrity verification function of the PDCP layer entity is not enabled, SDAP can only map the data of the first service.

[0012] In a possible implementation, the method further includes: the terminal device receiving second data, which is CRC-processed; before submitting the first data carried by the first logical channel, the method further includes: the terminal device receiving a MAC protocol data unit (PDU) through a medium access control (MAC) layer entity. The MAC PDU includes the first data but does not include the second data.

[0013] For the second data that has undergone CRC and the first data that has not undergone CRC, the MAC layer entity will not encapsulate the first and second data into a single PDU to avoid fault tolerance conflicts.

[0014] In a possible implementation, the method further includes: the terminal device receiving a configuration message, which indicates that the first data does not require CRC at the physical (PHY) layer.

[0015] The configuration message can indicate to the terminal device that the first data does not need to be CRC-tested at the PHY layer, so that the terminal device can execute the delivery without CRC-testing at the PHY layer after clearly obtaining the first data.

[0016] In possible implementations, the configuration message may be one of the following: information about a first search space, a first scrambling parameter, semi-persistent scheduling (SPS) information, or information included in the first downlink control information (DCI). Specifically, the DCI for scheduling the first data is located in the first search space; or, the DCI for scheduling the first data is scrambled by the first scrambling parameter; or, the first data is transmitted on the time-frequency resources configured in the SPS information; and the first DCI schedules the first data.

[0017] One or more of the above configurations can be used to explicitly or implicitly indicate that the first data does not need to undergo CRC at the PHY layer, thus eliminating the need for additional resources to indicate that the first data does not need to undergo CRC at the PHY layer and effectively saving transmission resources.

[0018] In possible implementations, the first service is a service that allows data to be transmitted or delivered incorrectly, including: the first service allows the data error transmission rate to be higher than a first threshold and / or lower than a second threshold.

[0019] In possible implementations, the first logical channel is also used to carry data for the second service, where the error transmission rate of the second service is lower than that of the first service; or, the first logical channel is a logical channel dedicated to carrying data for the first service.

[0020] Logical channels can be used to distinguish whether data carried on a logical channel has been erroneously delivered. For example, a logical channel can be configured specifically for carrying data for the first service, such as a first logical channel; and a logical channel can be configured specifically for carrying data for the second service, such as a second logical channel. Data carried on the first logical channel does not require CRC at the PHY layer, while data carried on the second logical channel does require CRC at the PHY layer. Logical information implicitly indicates which data does not require CRC at the PHY layer, thus eliminating the need for additional resources to indicate this, effectively saving transmission resources.

[0021] In a possible implementation, the method further includes: a terminal device receiving indication information, which can be used to indicate a first verification method; and the terminal device verifying the first data according to the first verification method.

[0022] The first verification method can be a predefined verification method or an agreed-upon verification method. The first verification method can be a CRC verification method distinct from that of the PHY layer. For example, the first verification method can be a verification method for checking the transmission error rate of the first data. The terminal device verifies the first data according to the first verification method, thereby determining the error transmission rate of the first data, which is beneficial for interpreting the meaning represented by the first data.

[0023] Secondly, embodiments of this application provide a second communication method, which can be executed by a second communication device. The second communication device can be a communication equipment or a communication device capable of supporting the functions required for the method to be implemented, such as a chip system. The second communication device can be a transmitting end in one of the two communication ends. Taking an example where the two communication ends include an access network device and a terminal device, and the transmitting end is the access network device, the second communication device can be the access network device or a unit or functional module within the access network device. For example, the second communication device can be a chip disposed in the access network device, or the first communication device can be other components used to implement the functions of the access network device. The method provided in the second aspect is described below with the example of the access network device itself as the second communication device.

[0024] The communication method includes: an access network device sending a configuration message, receiving first data carried by a first logical channel, and sending the first data. The configuration message indicates that the first data does not require CRC at the PHY layer, the first data is data of a first service, the first service is a service that allows data error transmission or delivery, and the first data has not undergone CRC.

[0025] In a possible implementation, before receiving the first data carried by the first logical channel, the method further includes: the access network device mapping the QoS flow containing the first data to only the first PDCP layer entity through the SDAP layer entity.

[0026] In the possible implementations, the integrity verification function of the first PDCP layer entity is not enabled.

[0027] In a possible implementation, the method further includes: the access network device receiving second data carried by the second logical channel, the second data being processed by CRC, and then transmitting the second data.

[0028] In a possible implementation, before sending the first data, the method further includes: the access network device sending a PHY PDU to the PHY layer through a MAC layer entity, the PHY PDU including the first data but not including the second data.

[0029] In possible implementations, the configuration message is one or more of the following: information of the first search space, first scrambling parameters, SPS information, or information included in the first DCI. Specifically, the DCI for scheduling the first data is located in the first search space; or, the DCI for scheduling the first data is scrambled by the first scrambling parameters; or, the first data is transmitted on the time-frequency resources configured by the SPS information; and the first DCI schedules the first data.

[0030] In possible implementations, the first service is a service that allows data to be transmitted or delivered incorrectly, including: the first service allows the data error transmission rate to be higher than a first threshold and / or lower than a second threshold.

[0031] In possible implementations, the first logical channel is also used to carry data for the second service, where the error transmission rate of the second service is lower than that of the first service; or, the first logical channel is a logical channel dedicated to carrying data for the first service.

[0032] In a possible implementation, the method further includes: the access network device receiving indication information, which indicates that the first data is data of the first service.

[0033] In this method, the access network device can be instructed whether the first data to be sent needs to undergo CRC at the PHY layer, which helps the access network device configure the terminal device with information for transmitting the first data.

[0034] In possible implementations, the indication information is information sent by the core network, and / or the indication information is contained in the QFI.

[0035] For the technical effects of the second aspect and its possible methods, please refer to the description of the technical effects of the corresponding implementation of the first aspect.

[0036] Thirdly, embodiments of this application provide a third communication method, which can be executed by both communication ends. The two communication ends can be a sending end and a receiving end, or internal units of the sending end and the receiving end, or internal units of the sending end and internal units of the receiving end. The internal unit of the sending end can be a chip or functional module disposed in the sending end. The internal unit of the receiving end can be a chip or functional module disposed in the receiving end. For ease of description, the method provided in the third aspect will be described below using the example of the sending end being the access network device itself and the receiving end being a terminal device.

[0037] The communication method includes: an access network device sending a configuration message, the configuration message indicating that first data does not require CRC at the PHY layer, the first data being data of a first service, and the first service being a service that allows data error transmission or delivery; the access network device receiving the first data carried by a first logical channel and sending the first data, the first data not being CRC-processed; and a terminal device receiving the first data and delivering the first data carried by the first logical channel.

[0038] For the technical effects of the third aspect and its possible methods, please refer to the introduction of the technical effects of the first aspect and its possible methods.

[0039] Fourthly, embodiments of this application provide a communication device that has the functionality to implement the behavior in the method examples of any of the first to second aspects described above. The beneficial effects can be found in the descriptions of the first and second aspects and will not be repeated here. For example, the communication device may be the first communication device in the first aspect; for example, the communication device may be a terminal device or a chip or chip system within a terminal device. Alternatively, the communication device may be a device capable of supporting the terminal device in the first aspect to implement the functions required by the method provided in the first aspect; for example, the communication device may be a terminal device. As another example, the communication device may also be the second communication device in the second aspect; for example, the communication device may be an access network device or a chip or chip system within an access network device. Alternatively, the communication device may be a device capable of supporting the access network device in the second aspect to implement the functions required by the method provided in the first aspect; for example, the communication device may be an access network device.

[0040] In one possible design, the communication device includes corresponding means or modules for performing the methods of any of the first to second aspects. For example, the communication device includes a processing unit (sometimes also called a processing module or processor) and / or a transceiver unit (sometimes also called a transceiver module or transceiver). The transceiver unit is capable of both transmitting and receiving functions. When the transceiver unit performs the transmitting function, it may be called a transmitting unit (sometimes also called a transmitting module), and when it performs the receiving function, it may be called a receiving unit (sometimes also called a receiving module). The transmitting unit and the receiving unit may be the same functional unit, referred to as the transceiver unit, which performs both transmitting and receiving functions; or, the transmitting unit and the receiving unit may be different functional units, with "transceiver unit" being a collective term for these functional units. These units (modules) can perform the corresponding functions in the method examples of any of the first to second aspects described above, as detailed in the method examples, and will not be repeated here.

[0041] Fifthly, embodiments of this application provide a communication device, which can be the communication device described in the fourth aspect of the above embodiments, or a chip or chip system disposed in the communication device described in the fourth aspect. The communication device includes a communication interface and a processor, and optionally, a memory. The memory stores computer programs, instructions, or data. The processor is coupled to the memory and the communication interface. When the processor reads the computer program, instructions, or data, it causes the communication device to execute the method performed by the access network device or the terminal device in the above method embodiments. For example, the communication device can be an access network device or a functional module within an access network device, such as a baseband chip and a radio frequency chip. As another example, the communication device can be a terminal device or a functional module within a terminal device, such as a baseband chip and a radio frequency chip.

[0042] Sixthly, embodiments of this application provide a chip system including a processor, and may further include a memory and / or a communication interface for implementing the methods described in any of the first to second aspects. Optionally, the chip system further includes a memory. The memory is used to store computer programs (also referred to as code or instructions). The processor is used to call and run the computer program from the memory, causing a device equipped with the chip system to perform any of the first to second aspects, and the methods in any possible implementation of any of the first to second aspects. The chip system may be composed of chips or may include chips and other discrete devices.

[0043] In a seventh aspect, embodiments of this application provide a communication device including an input / output interface and logic circuitry. The input / output interface is used for inputting and / or outputting information. The input / output interface may be an interface circuit, an output circuit, an input circuit, a pin, or related circuitry, etc. The logic circuitry is used to execute the methods described in any one of the first to second aspects.

[0044] In practical implementation, the aforementioned communication device can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the logic circuit can be a transistor, gate circuit, flip-flop, and various other logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the input / output interface and the logic circuit.

[0045] In one implementation, the communication device is a wireless communication device, which can be a terminal such as a smartphone or an access network device such as a base station. The interface circuit can be a radio frequency processing chip in the wireless communication device, and the processing circuit can be a baseband processing chip in the wireless communication device.

[0046] Eighthly, embodiments of this application provide a communication system, which includes the communication device for implementing the functions of the first aspect as described in the fourth aspect, and the communication device for implementing the functions of the second aspect as described in the fourth aspect. Optionally, the communication system further includes a core network device, which can be used to send indication information to the communication device implementing the functions of the second aspect, the indication information indicating that the first data is data of a first service.

[0047] In a ninth aspect, embodiments of this application provide a communication system, which includes a core network device and a communication apparatus as described in the fourth aspect for implementing the functions of the second aspect. The core network device can be used to send indication information to the communication apparatus for implementing the functions of the second aspect, the indication information indicating that the first data is data of a first service. Optionally, the communication system further includes the communication apparatus as described in the fourth aspect for implementing the functions of the first aspect.

[0048] In a tenth aspect, this application provides a computer-readable storage medium storing a computer program that, when executed, implements the methods described in any of the first to second aspects.

[0049] Eleventhly, a computer program product is provided, the computer program product comprising: computer program code, which, when the computer program code is run, causes the methods of any one of the first to second aspects to be executed.

[0050] The beneficial effects of the above-mentioned fourth to eleventh aspects and their implementation methods can be referred to the description of the beneficial effects of the first to second aspects, or the first to second aspects and their implementation methods. Attached Figure Description

[0051] Figure 1 This is an exemplary structural diagram of a communication system to which the embodiments of this application are applicable;

[0052] Figure 2 A schematic diagram illustrating the data transmission between layers from network devices to terminal devices.

[0053] Figure 3 A schematic diagram illustrating the specific functions of the MAC layer and PHY layer;

[0054] Figure 4This is a schematic diagram of the structure during the first data transmission process provided in an embodiment of this application;

[0055] Figure 5 A flowchart illustrating the first communication method provided in an embodiment of this application;

[0056] Figure 6 A flowchart illustrating the second communication method provided in this application embodiment;

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

[0058] Figure 8 This is another schematic diagram of the communication device provided in the embodiments of this application. Detailed Implementation

[0059] The technical solutions provided in the embodiments of this application can be applied to fifth-generation (5G) mobile communication systems, or to long-term evolution (LTE) systems, or to next-generation mobile communication systems, such as 6G mobile communication systems or other similar communication systems. Other similar communication systems include vehicle-to-everything (V2X), internet of things (IoT) systems, and narrowband internet of things (NB-IoT) systems. IoT can be understood as IoT or wearable WiFi networks based on wireless fidelity (WiFi). Wearable WiFi networks refer to WiFi networks composed of terminal devices (e.g., mobile phones) as virtual access points and associated wearable devices. This application describes embodiments using a 5G mobile communication system as an example. When applying the technical solutions of this application to other communication systems, the devices, components, and modules in the embodiments can be replaced with corresponding devices, components, and modules in other communication systems without limitation.

[0060] Please see Figure 1 This paper illustrates a network architecture for a 5G communication system, which may include network devices and at least one terminal device. Figure 1 Taking at least one terminal device as an example, which consists of two terminal devices. Figure 1The network architecture shown is for illustrative purposes only. For example, the network device may include access network devices. Alternatively, the network device may include both access network devices and a core network. Terminal devices access the core network through the access network devices and can communicate with data networks (DNs) through the core network.

[0061] Access network equipment is a network-side device with wireless transceiver capabilities. Access network equipment can be a device in a radio access network (RAN) that provides wireless communication functions for terminal devices; it is called RAN equipment. For example, access network equipment can be a base station, such as an evolved Node B (eNB) in a Long Term Evolution (LTE) system or Long Term Evolution-Advanced (LTE-A) system (which can be abbreviated as eNB or e-NodeB). An eNB is a device deployed in a radio access network that meets 4G standards and provides wireless communication functions for terminal devices. The network device can also be a new radio controller (NR controller), a gNode B (gNB) in a 5G system, a centralized unit, a new wireless base station, a remote radio module, a micro base station (also known as a small cell), a relay, a distributed unit, a macro base station of various forms, a transmission reception point (TRP), a transmission measurement function (TMF), a transmission point (TP), or any other wireless access device. The embodiments in this application are not limited to these. Network devices can also be radio network controllers (RNCs), Node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved Node Bs, or home Node Bs, HNBs), base band units (BBUs), remote radio units (RRUs), Wi-Fi access points (APs), or base band pools (BBU pools) and RRUs in cloud radio access networks (CRANs), etc. The embodiments of this application do not limit the specific technologies or device forms used in the network devices. In 4G systems, network devices can correspond to eNBs, and in 5G systems, they can correspond to gNBs.

[0062] Furthermore, the access network equipment in this application embodiment may include centralized units (CUs) and distributed units (DUs), and multiple DUs can be centrally controlled by a single CU. CUs and DUs can be divided according to their respective wireless network protocol layer functions. For example, PDCP layer and higher protocol layer functions are located in the CU, while lower protocol layers such as radio link control (RLC) and MAC layers are located in the DU. It should be noted that this protocol layer division is merely an example, and other protocol layer divisions are also possible. Radio frequency devices can be remotely located, not placed in the DU, or integrated into the DU, or partially remote and partially integrated into the DU; this application embodiment does not impose any limitations. Additionally, in some embodiments, the control plane (CP) and user plane (UP) of the CU can be separated into different entities, namely the control plane CU entity (CU-CP entity) and the user plane CU entity (CU-UP entity). In this network architecture, signaling generated by the CU can be sent to the terminal device through the DU, or signaling generated by the UE can be sent to the CU through the DU. The DU can directly encapsulate the signaling through the protocol layer and transmit it to the terminal device or CU without parsing it. In this network architecture, the CU is classified as a network device on the RAN side. Alternatively, the CU can also be classified as a network device on the core network (CN) side. This application does not impose any restrictions on this.

[0063] In this application embodiment, "access network device" refers to a device that can be used to implement the functions of an access network device, or it can be a device that supports the access network device in implementing those functions, such as a chip system, which can be installed in the access network device. The chip system can be composed of chips or may include chips and other discrete components. In this application embodiment, the technical solution provided by this application embodiment is described using the access network device itself as an example of the device used to implement the functions of the access network device.

[0064] A terminal device, possessing wireless transceiver capabilities, can send signals to or receive signals from network devices. For example, a terminal device, also called a terminal, includes user equipment (UE), access station, UE station, remote station, wireless communication equipment, user device, chip, etc. In this application embodiment, unless otherwise specified, "terminal device" and "terminal equipment" have the same meaning below. The terminal device is used to connect people, objects, machines, etc., and can be widely used in various scenarios, including but not limited to the following: cellular communication, device-to-device (D2D) communication, V2X, machine-to-machine / machine-type communications (M2M / MTC), IoT, virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, drones, robots, and other scenarios.

[0065] For example, the terminal device described in the embodiments of this application may be a mobile phone, tablet computer, computer with wireless transceiver function, VR terminal, AR terminal, wireless terminal in industrial control, complete vehicle, wireless communication module in a complete vehicle, vehicle-mounted T-box (Telematics BOX), RSU, wireless terminal in autonomous driving, smart speaker in IoT network, wireless terminal device in telemedicine, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, or wireless terminal device in smart home, etc. As an example and not a limitation, in the embodiments of this application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices or smart wearable devices, etc., and are a general term for devices that apply wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes.

[0066] Terminal devices may also include relays. Alternatively, any device capable of data communication with a base station can be considered a terminal device. The various terminal devices described above, if located in a vehicle (e.g., placed inside or installed inside a vehicle), can be considered vehicle-mounted terminal devices, also known as on-board units (OBUs). The terminal devices of this application can also be vehicle-mounted modules, vehicle-mounted components, vehicle-mounted chips, or vehicle-mounted units built into a vehicle as one or more components or units. The vehicle can implement the methods of this application through the built-in vehicle-mounted modules, vehicle-mounted components, vehicle-mounted chips, or vehicle-mounted units.

[0067] In this application embodiment, "terminal device" refers to a device that can be used to implement the functions of a terminal device, or a device that supports the terminal device in implementing those functions, such as a chip system. This device can be installed in the terminal device. For example, the terminal device can also be a vehicle detector. A chip system can be composed of chips or include chips and other discrete components. Unless otherwise specified, "terminal device," "terminal equipment," and "terminal" have the same meaning and can be used interchangeably. In this application embodiment, the technical solution provided by the embodiments of this application is described using the terminal device itself as an example of the device used to implement the functions of the terminal device.

[0068] The core network (CN) serves as the interface to the DN (Digital Network) as the bearer network, providing communication connections, authentication, management, policy control, and data service delivery for terminal devices. The CN may include at least one core network device, such as user plane function network elements (referred to as user plane network elements) and control plane function network elements (referred to as control plane network elements). Control plane function network elements may include access management network elements, session management network elements, unified data management network elements, and policy control network elements. It should be noted that the aforementioned CN may include one or more CN devices. A CN device may be a network element used to perform a single network function or a network element used to perform multiple network functions. When a single CN device is used to perform multiple network functions, the CN device may include one or more functional modules for performing these multiple network functions. These functional modules may be software modules or hardware / software modules; this application embodiment does not limit this.

[0069] The network architecture / system and service scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will understand that with the evolution of network architecture and the emergence of new service scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems. The apparatus in the following embodiments of this application, depending on the functions it implements, can be located in a terminal device or a network device. When the above CU-DU structure is adopted, the network device can be a CU, or a DU, or a RAN device including a CU and a DU.

[0070] Communication between access network devices and terminal devices follows a specific protocol layer structure. For example, data sent from an access network device to a terminal device needs to pass through the user plane protocol layer. The user plane protocol layer structure includes the SDAP layer, PDCP layer, RLC layer, MAC layer, and physical layer (PHY) / PHY layer. The functions of one or more of these protocol layers can be implemented by one or more nodes of the access network device or terminal device. For example, if the access network device includes a CU and a DU, the functions of the PDCP layer and above are located in the CU, while the functions of protocol layers below the PDCP layer, such as the RLC layer and MAC layer, are located in the DU. This division of protocol layers is just one example; it can also be done at other protocol layers. For example, at the RLC layer, the functions of the RLC layer and above are located in the CU, and the functions of protocol layers below the RLC layer are located in the DU; or, within a certain protocol layer, for example, some functions of the RLC layer and the functions of protocol layers above the RLC layer are located in the CU, and the remaining functions of the RLC layer and the functions of protocol layers below the RLC layer are located in the DU. Alternatively, functions can be divided in other ways, such as by latency, where functions whose processing time needs to meet latency requirements are set in DU, and functions that do not need to meet the latency requirements are set in CU.

[0071] The SDAP layer, PDCP layer, RLC layer, MAC layer, and physical layer can all be collectively referred to as the access layer. Based on the direction of data transmission, they are divided into transmitting and receiving layers, and each of these layers is further divided into a transmitting section and a receiving section. The following data transmission example is shown below. Figure 2 This is a schematic diagram illustrating the data transmission between layers from access network devices to terminal devices. Figure 2 The downward arrow indicates data transmission, and the upward arrow indicates data reception. In this embodiment, the data sent from the access network device to the terminal device is also referred to as downlink data.

[0072] During downlink data transmission, after the PDCP layer receives data from the upper layer, it transmits the data to the RLC and MAC layers. The MAC layer then generates a transport block (TB), which is then wirelessly transmitted through the physical layer. Data is encapsulated at each layer. Data received by a layer from its upper layer is considered a service data unit (SDU) for that layer. After layer encapsulation, it becomes a PHYPDU and is then passed to the next layer. For example, data received by the PDCP layer from its upper layer is called a PDCP SDU, and data sent by the PDCP layer to its lower layer is called a PDCP PDU; data received by the RLC layer from its upper layer is called an RLC SDU, and data sent by the RLC layer to its lower layer is called an RLC PDU; data received by the MAC layer from its upper layer is called a MAC SDU, and data sent by the MAC layer to its lower layer is called a MAC PDU. A MAC PDU can also be called a transport block. In the protocol, inter-layer communication is mostly represented by channels. The RLC layer and MAC layer correspond via a logical channel (LCH), while the MAC layer and physical layer correspond via a transport channel. Below the physical layer is the physical channel, which is used to map to the physical layer at the other end.

[0073] Similar to access network equipment, terminal equipment also has an access layer comprising SDAP, PDCP, RLC, MAC, and physical layers. Terminal equipment also has an application layer and a non-access layer. The application layer provides services to applications installed on the terminal equipment. For example, downlink data received by the terminal equipment can be sequentially transmitted from the physical layer to the application layer, and then provided to the application by the application layer. Alternatively, the application layer can acquire data generated by applications (such as videos recorded by users using the application) and sequentially transmit the data to the physical layer for transmission to other communication devices. The non-access layer forwards user data, such as forwarding uplink data received from the application layer to the SDAP layer or forwarding downlink data received from the SDAP layer to the application layer.

[0074] During downlink data transmission, the specific functions of the MAC layer and PHY layer are as follows: Figure 3As shown. The MAC layer may include one or more sub-functional entities or modules, such as multiplexing or demultiplexing entities, hybrid automatic repeat request (HARQ) entities, encoding or decoding entities. The PHY layer may also include one or more sub-functional entities or modules, such as a CRC check module. The following describes these sub-functional entities or modules from the perspectives of the transmitting and receiving devices. The transmitting device can be a terminal device, and the receiving device can be an access network device; alternatively, the transmitting device can be an access network device, and the receiving device can be a terminal device.

[0075] For the transmitting device, the MAC layer can include a multiplexing entity, a HARQ entity, and an encoding entity. The multiplexing entity can multiplex RLC PDUs received from the RLC layer to obtain a MAC PDU and deliver it to the HARQ entity. One RLC layer entity corresponds to one logical channel, and the RLC PDU can also be called a MAC SDU. Multiplexing can be performed in various ways, such as segmentation and concatenation. For example, the multiplexing entity can segment the RLC PDU received from logical channel 1, such as into two RLCPDU segments, RLC PDU segment 1 and RLC PDU segment 2, and then obtain MAC PDU1 from RLC PDU segment 1 and MAC PDU2 from RLC PDU segment 2. As another example, the multiplexing entity can concatenate RLC PDU1 received from logical channel 1 and RLC PDU2 received from logical channel 2, and then obtain a single MAC PDU from the concatenated RLC PDU1 and RLC PDU2. RLC PDUs from different logical channels can be distinguished by the Logical Channel Identifier (LCH ID) in the MAC PDU header. Figure 3 Taking multiplexing as an example of cascading, the HARQ entity can pass the MAC PDU received from the multiplexing entity to the encoding entity, which then encodes it and transmits the encoded MAC PDU to the physical layer. The CRC check module of the PHY layer performs CRC check processing on the MAC PDU received from the MAC layer and transmits it to the receiving device.

[0076] For the receiving device, after receiving data, the CRC check module in the PHY layer performs a CRC check on the data. If the check passes, the data is then passed to the MAC layer. The MAC layer's decoding entity receives the MAC PDU from the PHY layer and decodes it. If the decoding is correct, the MAC layer passes the MAC PDU to the HARQ entity, which then passes it to the demultiplexing entity. The HARQ entity can also send HARQ feedback information. After receiving the MAC PDU, the demultiplexing entity demultiplexes it to obtain the MAC SDU and passes it to the RLC layer through the corresponding logical channel.

[0077] As mentioned earlier, during downlink data transmission, the CRC check module of the PHY layer of the transmitting device performs CRC check processing on the MAC PDU received from the MAC layer and transmits it to the receiving device. After receiving the data, the CRC check module of the PHY layer of the receiving device can perform CRC check on the data. If the check passes, the data can be submitted to the MAC layer. If the check fails, the PHY layer can discard the data or wait for retransmission.

[0078] In some scenarios, even if errors occur during data transmission, the interpretation of the data remains unaffected. In such cases, a certain degree of fault tolerance is allowed, eliminating the need for the sending device's PHY layer CRC check module to perform CRC verification on the MAC PDU received from the MAC layer. Correspondingly, the receiving device's PHY layer CRC check module also does not need to perform CRC verification on the received data and can directly submit it to the MAC layer.

[0079] For example, in semantic communication scenarios, the focus is on the meaning conveyed by data. Even if a receiving device receives erroneous data, it can still infer the meaning of the data packet from the received data. In this case, errors during data transmission are permissible, as long as the meaning can be determined from the received data; bit-level or symbol-level accuracy in data transmission is not required. The sending device's PHY layer does not perform CRC checks on the data to be transmitted, and the receiving device's PHY layer does not perform CRC checks on the received data before delivery. This avoids the potential for poor user experience due to discarding or waiting for retransmission of erroneous data packets. For instance, in high-definition video services, if erroneous data packets are discarded or wait for retransmission, video stuttering may occur, resulting in a poor user experience. Furthermore, even if the data is erroneous, it does not affect the meaning it conveys; waiting for retransmission would waste resources.

[0080] Based on this, the technical solution of the embodiments of this application is provided. In the embodiments of this application, for error-tolerant service data, the CRC verification module of the PHY layer of the transmitting device does not need to perform CRC verification processing on the MAC PDU received from the MAC layer. Correspondingly, after receiving the data, the CRC verification module of the PHY layer of the receiving device also does not need to perform CRC verification on the data and can directly submit it to the MAC layer. Compared with performing CRC on the first data before submission, it can avoid the first data from failing to be submitted due to errors, thus obtaining the error-tolerant transmission gain of the data. In addition, it can also reduce the latency of service data transmission or save resource overhead.

[0081] This application's embodiments involve two types of services, such as a first type of service and a second type of service. Compared to the second type of service, the first type of service allows more errors during data transmission. For example, the first type of service allows a certain number of errors during data transmission; the second type of service does not allow errors during data transmission. Alternatively, the first type of service allows the proportion of errors during data transmission to be higher than a certain threshold (e.g., a first threshold); the second type of service allows the proportion of errors during data transmission to be lower than a certain threshold (e.g., a second threshold), where the first threshold is greater than the second threshold. Alternatively, the first type of service allows the data error transmission rate / decoding error rate to be higher than a certain threshold (e.g., a third threshold); the second type of service allows the data error transmission rate / decoding error rate to be lower than a certain threshold (e.g., a fourth threshold), where the third threshold is greater than the fourth threshold. Alternatively, the first type of service does not require the data decoding accuracy to be higher than a certain threshold (e.g., a fifth threshold); the second type of service requires the data decoding accuracy to be higher than a certain threshold (e.g., a sixth threshold), where the fifth threshold is less than the sixth threshold. Alternatively, the data for the first type of service has (application layer) pre-error correction capability, tolerating bit transmission errors within a first threshold; the data for the second type of service does not have pre-error correction capability, tolerating bit transmission errors within a second threshold, where the first threshold is greater than the second threshold. Alternatively, the data for the first type of service does not require CRC verification at the PHY layer, while the data for the second type of service requires CRC verification at the PHY layer.

[0082] For example, the second type of service could be a traditional (legacy) communication service, which requires accurate transmission at the bit or symbol level during data transmission; the first type of service could be a semantic communication service, which allows for certain errors during data transmission without affecting the semantic meaning expressed by the data.

[0083] In this embodiment, the first service can be a first-class service, and the second service can be a second-class service. Alternatively, the first service can be a first-class service, and the second service can be a second-class service. The first data is the data of the first service, and the second data is the data of the second service. During downlink data transmission, the first service is a service that allows data to be transmitted or delivered incorrectly, or the data of the first service (i.e., the first data) has not undergone CRC verification at the PHY layer. The data of the second service (i.e., the second data) has undergone CRC verification at the PHY layer.

[0084] It should be noted that in this embodiment, the first data refers to the data generated by application layer source encoding, also known as application data or payload, which has fault tolerance capabilities. Data that does not require CRC verification at the PHY layer is the data generated by application layer source encoding. At the PHY layer, the first data is the data included in the transport block (TB). During transmission, if some bit information of the first data is lost or corrupted, the application layer can still recover the meaning expressed by the original first data. Taking image data as an example, if the image data is partially lost or corrupted during transmission, the receiving end can rely on source decoding methods to recover image data that meets certain service requirements from the received image data. This service requirement may be, for example, an image quality requirement. The service requirement can be understood as a threshold value used by the receiving end to determine whether the received first data has been successfully transmitted or failed. This service requirement can also be called a PDU set content criterion.

[0085] It is understandable that the first piece of data will undergo processing / encapsulation at various protocol layers during transmission. For example, after receiving an SDU from the layer above, a layer adds the header of its current layer's protocol stack to the SDU, encapsulates it to generate a PDU, and then sends the PDU to the next layer. For example, please see [link to example]. Figure 4 The diagram illustrates the structure of the first data transmission process. The first data can be raw user data plus an added application (APP) header. The first data is transmitted from the application layer to the transport layer. The transport layer processes the first data, adding a TCP header. The first data with the added TCP header is transmitted from the transport layer to the network layer. The network layer adds an IP header to the first data with the added TCP header and transmits the first data with both the IP and TCP headers to the physical layer. The physical layer receives the first data with the added IP and TCP headers from the network layer and can then add an NR header. (The diagram is repeated in the original text.) Figure 4 As shown in the embodiments of this application, CRC verification is not required. Figure 4The application data in the header, but other parts such as the APP header, TCP header, IP header and NR header still need to be checked by CRC.

[0086] In this application embodiment, the first data carried by a certain protocol layer is actually the SDU or PDU carrying the first data carried by that protocol layer. For ease of description, this application embodiment also refers to the PDU generated after each protocol layer encapsulates the first data as the first data. The first data carried by different protocol layers is actually different. Figure 4 For example, the TCP header and application data in the transport layer can be referred to as the first data, as can the IP header, TCP header, and application data in the network layer. Figure 2 For example, the first data in the PDCP layer is called a PDCP SDU or PDCP PDU. The first data in the RLC layer is called an RLC SDU or RLC PDU. The first data in the MAC layer is called a MAC SDU or MAC PDU. The first data in the PHY layer is called a PHY SDU or PHY PDU.

[0087] In this embodiment, the PHY layer does not need to perform CRC verification. This can be due to: the PHY layer not performing CRC operation, or the PHY layer not generating CRC codes, or the PHY layer's CRC verification module being disabled, or the PHY layer's CRC verification module not being enabled, or the PHY layer's CRC verification module not performing CRC verification, or whether the data packets received by the PHY layer support error delivery. During downlink data transmission, for the access network device, the PHY layer does not need to perform CRC verification to indicate whether the MAC PDU supports error delivery. For the terminal device, the PHY layer does not need to perform CRC verification to indicate whether the PHY SDU supports error delivery. If the MAC PDU supports error delivery, but one or more MAC SDUs in the MAC PDU do not support error delivery, the terminal device can submit the MAC SDUs that support error delivery to the upper layer after decoding failure; for MAC SDUs that do not support error delivery, they can be left unsubmitted to the upper layer and submitted only after successful retransmission.

[0088] Alternatively, the CRC check result of the PHY layer does not affect the PHY layer's submission of the PHY PDU to the MAC layer. This means that even if the CRC check result of the PHY layer is incorrect, the PHY layer still submits the PHY PDU to the MAC layer.

[0089] The PHY layer does not need to perform CRC checks and can be replaced by supporting error delivery. For example, the first data does not need CRC checks at the PHY layer and can be replaced by supporting error delivery. Supporting error delivery for the first data can include at least one of the following: the service to which the first data belongs supports error delivery; the cell transmitting the first data supports error delivery; or at least some or all of the at least one logical channel carrying the first data supports error delivery. For example, if the service to which the first data belongs is service A, and service A supports error delivery, then the first data supports error delivery. Another example: if the service to which the first data belongs is service A, and service A supports error delivery, and the cell transmitting the first data also supports error delivery, then the first data supports error delivery. Yet another example: if the first data includes data from at least one logical channel, and all at least one logical channel supports error delivery, then the first data supports error delivery. Yet another example: if the first data includes data from at least one logical channel, and some of the at least one logical channel supports error delivery, then the first data supports error delivery. In other possible examples, the first data includes data from at least one logical channel, and the first data may not support error delivery if some of the logical channels of at least one logical channel do not support error delivery.

[0090] In the embodiments of this application, "system" and "network" can be used interchangeably. "Multiple" refers to two or more. Therefore, in the embodiments of this application, "multiple" can also be understood as "at least two". "At least one" can be one or more, for example, at least one is one, two or more. For example, including at least one means including one, two or more, and is not limited to which ones are included. For example, including at least one of A, B and C, then it can include A, B, C, A and B, A and C, B and C, or A and B and C. Similarly, the understanding of descriptions such as "at least one" is similar. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single items or multiple items. For example, "at least one of A, B and C" includes A, B, C, AB, AC, BC or ABC. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, unless otherwise specified, the character " / " generally indicates that the objects before and after it are in an "or" relationship.

[0091] Unless otherwise specified, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects, but are not used to limit the order, sequence, priority, or importance of multiple objects, and the descriptions of "first" and "second" do not limit the objects to necessarily being different. For example, "first data" and "second data" indicate that there are two data, without limiting the priority or importance of these two data. In the embodiments of this application, "if" and "if" are interchangeable, and unless otherwise specified, "when..." and "in the case of..." are interchangeable. "CRC check" and "CRC" are interchangeable.

[0092] The communication method provided in this application involves the interaction between two communication devices, such as a first communication device and a second communication device. The first communication device can be a transmitting end device, and the second communication device can be a receiving end device. For example, the first communication device can be an access network device, and the second communication device can be a terminal device. The steps performed by the access network device can be implemented by the access network device itself, or by components (such as chips, processing units, or processor modules) within the access network device. For example, the access network device can be... Figure 1 Access network equipment in, or it could be Figure 1 The chip (system) in the access network equipment. The steps executed by the terminal device can be implemented by the terminal device itself, or by components within the terminal device (such as chips, processing units, or processor modules). The terminal device can be, for example... Figure 1 The terminal device shown, or it could be Figure 1 The chip (system) in the terminal device.

[0093] It should be noted that the method provided in this application is applicable to data interaction between two communicating ends. This application does not limit the specific implementation of the two communicating ends. For example, the sending end can be a first terminal device, and the receiving end can be a second terminal device. In this case, the first terminal device can send data that supports error delivery and send data packets to the second terminal device. If a data transmission error occurs, the second terminal device can perform an error delivery.

[0094] When an access network device sends first data to a terminal device, the access network device can encapsulate the first data, which supports error delivery. The access network device does not perform CRC on the first data at the PHY layer. The access network device sends a PDU containing the first data to the terminal device. If the first data transmission fails, the terminal device can perform error delivery. The terminal device does not know in advance whether CRC is required for the first data at the PHY layer. If error delivery is allowed for the first data, but the terminal device still performs CRC on the first data at the PHY layer, the first data may fail to be delivered, and the fault-tolerant transmission gain of the first data may not be obtained. Therefore, embodiments of this application propose a scheme to indicate to the terminal device that CRC is not required for the first data at the PHY layer.

[0095] The following describes, with reference to Embodiment 1, how to indicate to the terminal device that the first data does not require CRC at the PHY layer, and with reference to Embodiment 2, provides a detailed description of the behavior of the access network device at each protocol layer, the behavior of the terminal device at each protocol layer, and the interaction between the access network device and the terminal device.

[0096] Example 1 describes how an access network device indicates to a terminal device that first data does not require CRC at the PHY layer.

[0097] Please see Figure 5 This is a flowchart illustrating the first communication method provided in an embodiment of this application. Figure 5 This method is introduced from the perspective of the interaction between access network devices and terminal devices. For example... Figure 5 As shown, the process of this first communication method includes the following steps.

[0098] S501, The access network device determines that the first data is the data of the first service.

[0099] Since one or more data streams mapped to the first service do not require CRC at the PHY layer, while the data streams mapped to the second service do require CRC at the PHY layer, the access network device can determine whether the first data belongs to the first service before sending the first data. If the first data belongs to the first service, the access network device does not perform CRC on the first data at the PHY layer.

[0100] There are several ways for the access network device to determine that the first data is data for the first service. For example, some terminal devices support the first service, while others do not. After the terminal device accesses the network, it registers information with the core network. If the terminal device supports the first service, its registration information with the core network can include information about the first service. When the access network device needs to exchange the first data with the terminal device, the core network can indicate to the access network device that the first data is data for the first service.

[0101] For example, S501 includes S501a, in which the access network device receives indication information indicating that the first data is data for the first service. This indication information may originate from the core network, meaning it is sent by the access network device on the core network. The indication information may be included in the QFI. For example, the QFI may include a first field carrying the indication information. Alternatively, the indication information may be a QoS indication, which includes the QFI.

[0102] The instruction information can explicitly indicate that the first data is data for the first service, or it can implicitly indicate that the first data is data for the first service. The instruction indicating that the first data is data for the first service can also be replaced with an instruction indicating that the current service is the first service or the first type of service.

[0103] For example, the indication information may include type information of the service corresponding to one or more data streams. If the type information of the service corresponding to a certain data stream indicates that the type of the service corresponding to the data stream is a first type, then it can be determined that the data of that data stream does not need to undergo CRC at the PHY layer. For example, taking data stream A as an example, data stream A is a data stream of service A. The indication information includes the type information of service A corresponding to data stream A. If the type of service A is a first type, it can be determined that the data of data stream A does not need to undergo CRC at the PHY layer.

[0104] Alternatively, the indication information may include error delivery indications for one or more data streams. If an error delivery indication for a data stream supports error delivery, then it can be determined that the data in that data stream does not require CRC at the PHY layer. For example, the indication information may include service information for one or more services. Taking service A as an example, the service information for service A includes error delivery indications for one or more data streams corresponding to service A (such as data stream A1 and data stream A2). For instance, the error delivery indication for data stream A1 is used to indicate whether data stream A1 supports error delivery.

[0105] Alternatively, the indication information may include service information corresponding to one or more data flows, implicitly indicating that the first data does not require CRC at the PHY layer. Taking data flow A as an example, data flow A is the data flow for service A. The service information may include the allowable fault tolerance rate / transmission error rate for service A. If this fault tolerance rate / transmission error rate is greater than or equal to the allowable error submission threshold, the access network device can determine that the data in data flow A does not require CRC at the PHY layer.

[0106] It should be noted that the above-mentioned business A can be understood as a type of business, or a specific business, without being limited to any particular one.

[0107] S502, the access network device sends a configuration message to the terminal device.

[0108] Accordingly, the terminal device receives a configuration message from the access network device. When the access network device determines that the first data is data for the first service, the configuration message can also be used to indicate that the first data does not require CRC at the PHY layer. In some possible examples, it can be predefined or preconfigured that data received by the terminal device does not require CRC at the PHY layer, thus the access network device may no longer need to indicate to the terminal device that the first data packet does not require CRC at the PHY layer.

[0109] There are several ways for access network devices to indicate whether the first data does not need to undergo CRC at the PHY layer through configuration messages, which will be introduced in turn below.

[0110] Instruction method 1 can associate the DCI of the first data with a specific control-resource set (CORESET) and / or search space (SS), implicitly indicating whether the first data needs to undergo CRC at the PHY layer by configuring the specific control-resource set and / or search space.

[0111] For example, the configuration message may include information about the first CORESET and / or the first SS. If the DCI scheduling the first data is located in the first control resource set and / or the first search space, then the configuration message may indicate that the first data does not require CRC at the PHY layer. If the DCI scheduling the first data is not received in the first control resource set and / or the first search space, then the configuration message may indicate that the first data requires CRC at the PHY layer. Alternatively, the requirement for CRC at the PHY layer can be indicated by specifying the resource scheduled by the DCI scheduling the first data. For example, if the resource scheduled by the DCI in the first control resource set and / or the first search space carries data that does not require CRC at the PHY layer.

[0112] Indication method 2 can associate the DCI of the first data with specific scrambling parameters, implicitly indicating whether the first data needs to undergo CRC at the PHY layer by configuring specific scrambling parameters.

[0113] For example, the configuration message may include information about a first scrambling parameter. If the DCI for scheduling the first data is scrambled by the first scrambling parameter, then the configuration message may indicate that the first data does not require CRC at the PHY layer. If the DCI for scheduling the first data is not scrambled by the first scrambling parameter, then the configuration message may indicate that the first data requires CRC at the PHY layer. The first scrambling parameter may be predefined or (pre)configured; for example, the first scrambling parameter may be a predefined radio network temporary identifier (RNTI) or a specific ScramblingID.

[0114] Instruction method 3 can explicitly indicate whether the first data needs to undergo CRC in the PHY by scheduling the DCI of the first data.

[0115] For example, the configuration message may include a first DCI for scheduling the first data. If the first DCI carries indication information 1, it indicates whether the first data needs to undergo CRC in the PHY; conversely, if the first DCI does not carry indication information 1, it indicates that the first data needs to undergo CRC in the PHY. Alternatively, if the first DCI carries indication information 2, which occupies 1 bit, if the value of this 1 bit is the first value, it indicates whether the first data needs to undergo CRC in the PHY; conversely, if the value of this 1 bit is the second value, it indicates that the first data needs to undergo CRC in the PHY.

[0116] Indication information 1 or indication information 2 can be carried in one or more fields of the first DCI, such as one or more of the following: HARQ process number indication field, modulation and coding scheme (MCS) indication field, frequency domain resource assignment indication field, time domain resource assignment indication field, and reserved fields carried in DCI-2. Taking the MCS indication field of the DCI carried by indication information 1 or indication information 2 as an example, for instance, the MCS indication field includes 5 bits, totaling 32 (2 5 There are 25 code points, of which 25 code points have been defined with specific meanings, and the remaining 7 code points are reserved code points. One or more of the remaining 7 code points can be used to indicate whether the first data needs to be CRC-tested at the PHY layer.

[0117] Indication method 4 implicitly indicates whether the first data needs to undergo CRC at the PHY layer by configuring specific resources.

[0118] For example, it can be agreed that DCI-scheduled data received on specific resources does not require CRC at the PHY layer. For instance, the configuration message may include information about a first time-domain resource and / or a first frequency-domain resource. If the DCI scheduling the first data is received on the first time-domain resource and / or the first frequency-domain resource, then the first data scheduled by that DCI does not require CRC at the PHY layer; conversely, if the DCI scheduling the first data is not received on the first time-domain resource and / or the first frequency-domain resource, then the first data scheduled by that DCI requires CRC at the PHY layer.

[0119] For example, it can be agreed that data carried on a specific resource does not require CRC at the PHY layer. For instance, a configuration message may include SPS information, where data carried on the time-frequency resource indicated by the SPS information does not require CRC at the PHY layer. If the first data is carried on the time-frequency resource indicated by the SPS information, then the first data does not require CRC at the PHY layer.

[0120] It should be noted that, for SPS, DCI can be used to indicate whether the data carried by the SPS resources needs to undergo CRC at the PHY layer. Alternatively, the RRC message used for configuration periods can also be used to indicate whether the data carried by the SPS resources needs to undergo CRC at the PHY layer.

[0121] For example, up to eight SPS resources can be configured on a bandwidth part (BWP). When indicating whether the data carried by the SPS resources needs CRC at the PHY layer via RRC messages, it can be done individually for each SPS resource. For instance, if the RRC message indicates that the data carried by a certain SPS resource does not need CRC at the PHY layer, then no further indication is needed in the DCI for activating the resources of that SPS. Once the resources of that SPS are activated, the data transmitted on those SPS resources does not need CRC at the PHY layer. Alternatively, it can be configured uniformly to determine whether the data carried by all SPS resources needs CRC at the PHY layer. For example, if the RRC message indicates that the data carried by the SPS resource does not need CRC at the PHY layer, then no further indication is needed in the DCI for activating the resources of that SPS. Once the resources of any SPS are activated, the data transmitted on that SPS does not need CRC at the PHY layer.

[0122] The configuration message may include one or more of the information from indication methods 1 to indication methods 4 described above. The configuration message may explicitly or implicitly indicate that the first data does not require CRC at the PHY layer, thereby eliminating the need for additional resources to indicate that the first data does not require CRC at the PHY layer and effectively saving transmission resources.

[0123] Understandably, configuration messages can also be used to configure the data radiobearer (DRB) of the first data. For example, the configuration message includes DRB information and cell group information. The DRB mainly consists of PDCP layer entities and RLC layer entities. A cell group may include a MAC layer entity and a set of logical channels with associated RLC layer entities.

[0124] Because there is a correspondence between data streams and logical channels, access network devices can also implicitly indicate through logical channels whether the first data does not require CRC at the PHY layer.

[0125] For the first type of service, a dedicated logical channel can be configured. For example, the configuration message includes information about a first logical channel used to carry the first data. If the first logical channel is dedicated to carrying data streams for the first type of service, then it cannot be used to carry data streams for the second type of service. If the logical channel configured in the configuration message is dedicated to carrying data streams for the first type of service, the terminal device can determine, based on the configuration message, that data carried on the configured logical channel does not require CRC at the PHY layer. Conversely, data carried on logical channels other than those dedicated to carrying data streams for the first type of service requires CRC at the PHY layer. For example, data for service A does not require CRC at the PHY layer, while data for service B requires CRC at the PHY layer. Logical channel 1 is dedicated to carrying data streams for the first type of service, and logical channel 2 is dedicated to carrying data streams for the second type of service. If the data sent from the access network device to the terminal device is data for service A, then the configuration message can include information about logical channel 1.

[0126] Alternatively, a logical channel used to carry data streams for the first type of service can be a subset of logical channels used to carry data streams for the second type of service. Or, a logical channel can be used to carry both first and second data. For example, the IDs of logical channels used to carry data streams for the second type of service form a first set. The IDs of logical channels used to carry data streams for the first type of service form a second set, which is a subset of the first set. Data carried on one or more logical channels corresponding to the second set does not require CRC at the PHY layer. Conversely, data carried on one or more logical channels corresponding to IDs in the first set (excluding those in the second set) requires CRC at the PHY layer.

[0127] It's important to note that data for each service can be mapped to one or more data flows. For the same service, some data flows may not require CRC at the PHY layer, while others require it. In this case, configuration messages can configure whether one or more data flows require CRC at the PHY layer. Since there's a correspondence between data flows and logical channels, configuration messages can also be used to configure whether data flows carried by one or more logical channels require CRC at the PHY layer. For example, data for service A can be mapped to data flows A1 and A2. Data flow A1 does not require CRC at the PHY layer, while data flow A2 does. Data carried on logical channel 1 does not require CRC at the PHY layer, while data carried on logical channel 2 does. In this case, logical channel 1 can be configured for data flow A.

[0128] In Example 2, the access network device sends first data to the terminal device, and correspondingly, the terminal device receives the first data from the access network device.

[0129] Please see Figure 6 This is a flowchart illustrating the second communication method provided in the embodiments of this application. Figure 6 This method is introduced from the perspective of the interaction between access network devices and terminal devices. For example... Figure 6 As shown, the process of this second communication method includes the following steps.

[0130] S601, The access network device receives the first data carried by the first logical channel.

[0131] The access network device receives the first data carried by the first logical channel. In reality, the MAC layer entity of the access network device receives the first data carried by the first logical channel. The first data carried by the first logical channel is actually an RLC PDU including the first data carried by the first logical channel. It can be understood that after obtaining the original first data, the access network device can then... Figure 5 The configuration messages in the relevant embodiments are based on Figure 2 The protocol layer structure shown processes / encapsulates the first data at each protocol layer, and then sends the PHY PDU obtained at the PHY layer to the PHY layer entity of the terminal device.

[0132] S601 can include S601a-S601c, and S601a-S601c will be introduced separately below.

[0133] S601a, The access network device maps the first data to the SDAP layer entity.

[0134] After receiving the first data, the SDAP layer entity adds an SDAP header to the first data and then generates an SDAP PDU, which is sent to the PDCP layer entity, such as the first PDCP entity.

[0135] S601b: The SDAP layer entity of the access network device sends an SDAP PDU to the first PDCP entity.

[0136] The access network device can map the QoS flow containing the first data to the first PDCP layer entity through the SDAP layer entity. The first PDCP entity adds a PDCP header to the SDAP PDU, generates a PDCP PDU, and sends it to the RLC layer entity. It is understood that the PDCP PDU includes the first data, the SDAP header, and the PDCP header.

[0137] Since the first service allows for erroneous data transmission or delivery, the first data does not require CRC verification. Accordingly, the first PDCP layer entity does not need to perform integrity verification on the first data. The first PDCP layer entity's failure to perform integrity verification on the first data includes the following two aspects.

[0138] On one hand, the first PDCP layer entity has integrity verification functionality. In this case, the integrity verification functionality of the first PDCP layer entity can be either not enabled or not activated, meaning the integrity verification functionality of the first PDCP layer entity is either not enabled or not activated. Alternatively, for the first data / first type of service, the integrity verification functionality of the first PDCP layer entity may be disabled. When the first PDCP layer entity has integrity verification functionality, it can determine whether to perform integrity verification on the first data based on the first data. On the other hand, for the first data / first type of service, the first PDCP layer entity may not support integrity verification functionality, or the first PDCP layer entity may not have integrity verification functionality. Alternatively, for the first data / first type of service, the integrity verification functionality of the first PDCP layer entity may be disabled.

[0139] When the integrity verification function of the PDCP layer entity of the access network device is not enabled or is not allowed, or when the PDCP layer entity does not support the integrity verification function, the SDAP layer entity of the access network device can only map data of the first type of service and cannot map data of the second type of service. Taking the first data as an example, the SDAP layer entity of the access network device will map the QoS flow containing the first data only to the first PDCP layer entity.

[0140] S601c, The first PDCP layer entity of the access network device sends a PDCP PDU to the RLC layer entity.

[0141] After receiving the PDCP PDU, the RLC layer entity maps the PDCP PDU to the first logical channel and adds an RLC header to the PDCP PDU to generate an RLC PDU. The RLC layer entity mapping the PDCP PDU to the first logical channel can also be considered as the RLC layer entity mapping the first data to the first logical channel. The RLC layer entity then sends the generated RLC PDU to the MAC layer entity.

[0142] S602, The access network device sends the first data.

[0143] The access network device sends the first data; in fact, the MAC layer entity of the access network device sends the first data to the PHY layer entity, and the PHY layer of the access network device sends the first data to the PHY layer entity of the terminal device. S602 includes S602a-S602b.

[0144] S602a, The MAC layer entity of the access network device sends a MAC PDU to the PHY layer entity.

[0145] After receiving the RLC PDU, the MAC layer entity of the access network device adds a MAC header to the RLC PDU, generates a MAC PDU, and then sends the generated MAC PDU to the PHY layer of the access network device. The multiplexing entity within the MAC layer entity of the access network device can multiplex data received from at least one logical channel. Since the access network device may also send data that requires CRC at the PHY layer, such as second data, to the terminal device, it is understood that the second data undergoes CRC at the PHY layer. In this case, if the MAC layer entity multiplexes the first data and the second data, it may cause fault tolerance conflicts. Therefore, in this embodiment, if the MAC layer entity receives both the first data and the second data, then the MAC PDU includes the first data but does not include the second data. Alternatively, the MAC layer entity of the access network device will not combine data that does not require CRC at the PHY layer and data that requires CRC at the PHY layer into a single MAC SDU.

[0146] The MAC layer entity of the access network device can combine multiple data sets that do not require CRC at the PHY layer into a single MACSDU, or it can combine multiple data sets that require CRC at the PHY layer into a single MAC SDU. For example, if, in addition to the first data, the access network device also receives third data of the first service, the third data also does not require CRC at the PHY layer. The MAC layer entity of the access network device receives an RLC PDU including the first data and an RLCPDU including the third data from at least one logical channel. The MAC layer entity of the access network device can multiplex the first data and the third data. For example, the MAC layer entity of the access network device can combine the RLC PDU of the first data and the RLC PDU including the third data into a single MAC SDU.

[0147] S602b: The PHY layer of the access network device sends a PHY PDU to the PHY layer of the terminal device.

[0148] Since the first data does not require CRC checking at the PHY layer, the PHY layer entity of the access network device does not perform CRC checking on the first data in the MAC PDU, or the first data included in the MAC SDU is not CRC checked. Alternatively, the PHY layer entity of the access network device sends the PHY PDU to the PHY layer of the terminal device regardless of the CRC check result. Or, the PHY PDU sent by the PHY layer of the access network device to the PHY layer of the terminal device does not include the CRC code for the first data. The PHY layer of the access network device adds a PHY header to the MAC PDU and sends it to the PHY layer of the terminal device.

[0149] S603, The terminal device submits the first data carried by the first logical channel.

[0150] When a terminal device delivers the first data carried by the first logical channel, it actually involves the terminal device's PHY layer entity receiving a PHY PDU from the access network device's PHY layer, followed by sequential transmission through the MAC layer entity, RLC layer entity, PDCP layer entity, SDAP layer entity, and then the non-access layer and application layer. For example, based on configuration information, the terminal device may determine that the first data in the PHY PDU does not require CRC verification at the PHY layer, and the terminal device's PHY layer entity can directly deliver the first data to the MAC layer entity. Alternatively, the terminal device's PHY layer entity may send the PHY PDU to the network device's PHY layer regardless of the CRC verification module's result. Or, the PHY PDU sent by the terminal device's PHY layer to the access network device's PHY layer may not include the CRC code for the first data.

[0151] Alternatively, the terminal device may not perform CRC on the first data at the PHY layer, but may also perform error delivery on the first data at other layers. Error delivery of the first data by the terminal device includes at least one of the following: (1) the HARQ entity of the terminal device performs error delivery on the first data; (2) the demultiplexing entity of the terminal device performs error delivery on the first data; (3) the RLC layer entity of the terminal device performs error delivery on the first data packet; (4) the PDCP layer entity of the terminal device performs error delivery on the first data. It is understood that error delivery of the first data by the terminal device may also include error delivery of the first data packet by other layer entities, such as the SDAP layer entity performing error delivery on the first data. For example, when each of the entities described above performs error delivery on the first data, it can notify the upper layer of a first data transmission error.

[0152] The following provides a detailed explanation of the different entities that performed the erroneous submission of the first data.

[0153] (1) The HARQ entity performs an error submission on the first data.

[0154] The HARQ entity can deliver the first data to the demultiplexing entity without needing the result from the decoding entity. Even if the decoding result indicates an error in the first data transmission, the HARQ entity will still deliver the first data to the demultiplexing entity. Alternatively, the HARQ entity can deliver the first data and the decoding result together to the demultiplexing entity. The decoding result can indicate an error in the first data transmission. For example, the decoding result might indicate the decoding accuracy of the first data, such as 30% or 50%. Or, for example, the decoding result might indicate the error transmission rate of the first data, such as 70% or 50%.

[0155] For example, even if the decoding error rate of the first data exceeds a certain threshold, such as a first threshold, the HARQ entity still delivers the first data to the demultiplexing entity for decoding. For instance, the first threshold could be 20%. After receiving the first data, if the terminal device determines that the decoding error rate reaches 30% (greater than the first threshold), it delivers the first data to the demultiplexing entity. After receiving the first data (which is the first retransmission of some data), the terminal device can merge the first data with the data in the HARQ buffer for decoding. If the decoding error rate reaches 25% (greater than the first threshold), it delivers the data to the demultiplexing entity and updates the data in the HARQ buffer to the previous merging result. The first threshold can be specified by a protocol; or it can be determined by the access network device. Furthermore, the access network device can also send the first threshold to the terminal device.

[0156] It should be noted that after the HARQ entity delivers the first data with a transmission error to the demultiplexing entity, if it receives a retransmission of the first data, it does not need to deliver the retransmission to the demultiplexing entity again. This is understandable because when the latency requirements of the service are high, retransmission may not meet those requirements. Therefore, by not delivering the retransmission of the first data with a transmission error to the demultiplexing entity, the processing burden on the upper layer can be reduced. Alternatively, after the HARQ entity delivers the first data with a transmission error to the demultiplexing entity, if the HARQ entity receives a retransmission of the first data and the retransmission is successful, it can deliver the retransmission to the demultiplexing entity. Or, if the HARQ entity delivers the first data with a transmission error to the demultiplexing entity and receives a retransmission of the first data, regardless of whether the retransmission is successful, it does not need to deliver the retransmission to the demultiplexing entity again.

[0157] For erroneously submitted first data, the HARQ entity can provide appropriate feedback based on whether it submitted the first data to the demultiplexing entity. For example, if the HARQ entity submits the erroneously transmitted first data to the demultiplexing entity, it may not need to provide an acknowledgment (ACK) or a negative acknowledgment (NACK), i.e., it will not provide feedback. Alternatively, if the HARQ entity submits the erroneously transmitted first data to the demultiplexing entity, it may provide an ACK; if it did not submit the data, it may provide a NACK or not provide feedback at all. Or, if the HARQ entity submits the erroneously transmitted first data to the demultiplexing entity, it will not provide feedback; if it did not submit the data, it may provide a NACK. Alternatively, the HARQ entity can also provide appropriate feedback based on whether the first data was transmitted correctly. For example, if the HARQ entity determines that the first data was transmitted correctly, it will provide an ACK; if it determines that the first data was transmitted incorrectly, it will provide a NACK or not provide feedback. For example, if the HARQ entity determines that the first data transmission is correct, it will not provide feedback; if it determines that the first data transmission is incorrect, it will provide NACK feedback.

[0158] (2) De-reuse entity performs erroneous delivery on the first data.

[0159] The demultiplexing entity can deliver the first data to the RLC layer entity. If the first data transmission fails, the demultiplexing entity can also inform the RLC entity of the error. For example, the demultiplexing entity can deliver the first data and error indication information to the RLC layer entity; this error indication information indicates a data transmission error. Here, if the first data is a MAC PDU delivered by the HARQ entity, the demultiplexing entity, upon receiving the MAC PDU from the HARQ entity, can demultiplex the MAC PDU into one or more MAC SDUs and deliver them to the RLC layer entity.

[0160] For example, taking a MAC PDU that includes MAC SDU1, and MAC SDU1 that includes first data as an example, even if the logical channel corresponding to MAC SDU1 is a logical channel dedicated to carrying data of the first type of service, the demultiplexing entity still delivers MAC SDU1 to the RLC layer entity.

[0161] There are several ways for the demultiplexing entity to determine the logical channel corresponding to MAC SDU1. For example, the demultiplexing entity can parse the logical channel identifier corresponding to MAC SDU1 from the MAC subheader of the MAC SDU. Alternatively, the demultiplexing entity can obtain the logical channel identifier corresponding to MAC SDU1 from the DCI or from the upper-layer configuration message. In this embodiment, the method by which the demultiplexing entity obtains the logical channel identifier is not limited; the following description uses the example of the demultiplexing entity parsing the logical channel identifier from the MAC subheader of the first data packet.

[0162] When the demultiplexing entity delivers MAC SDU1 to the RLC layer entity, it can also indicate to the RLC entity that the first data in MAC SDU1 was transmitted incorrectly.

[0163] For example, if MAC SDU1 corresponds to logical channel 1 and logical channel 1 supports error delivery, then the demultiplexing entity resolves the logical channel corresponding to MAC SDU1 to logical channel 1. Then, MAC SDU1 and error indication information can be delivered to RLC layer entity 1 through logical channel 1. The error indication information indicates that the first data in MAC SDU1 was transmitted incorrectly.

[0164] For example, the demultiplexing entity parses the MAC SDU to obtain at least one logical channel, which includes a logical channel supporting error delivery, such as logical channel 1. In this case, the demultiplexing entity can deliver MAC SDU1 and error indication information to RLC layer entity 1 through logical channel 1, the error indication information indicating a first data error transmission in MAC SDU1.

[0165] (3) The RLC layer entity and the PDCP layer entity perform an error delivery on the first data.

[0166] Similar to the PDCP layer entity of the access network device, the integrity verification function of the PDCP layer entity of the terminal device is not enabled or is not allowed. Alternatively, the PDCP layer entity does not support the integrity verification function.

[0167] When an RLC layer entity or a PDCP layer entity receives a MAC SDU (e.g., MAC SDU1) from the MAC layer, and the MAC layer indicates that MAC SDU1 is a data packet with a transmission error, the RLC layer entity or the PDCP layer entity can move the window of their respective layer according to the RLC sequence number (SN) and the PDCP SN. That is, the RLC layer entity can move the window of the RLC SN, and the PDCP layer entity can move the window of the PDCP SN.

[0168] When an RLC layer entity or PDCP layer entity receives MAC SDU1 from the MAC layer, and the MAC layer indicates that MAC SDU1 is a data packet with a transmission error, if the RLC layer entity or PDCP layer entity determines that this is the first time MAC SDU1 has been received, it can move its respective layer's window according to the RLC sequence number (SN) and PDCP SN. If it determines that this is not the first time MAC SDU1 has been received (for example, it may be the second or third time MAC SDU1 has been received), it can stop moving its respective layer's window according to the RLC SN and PDCP SN, thereby avoiding errors caused by moving the window multiple times for the same MAC SDU. For example, even if the second or third MAC SDU1 received is transmitted correctly, the RLC layer entity or PDCP layer entity may not need to move its respective layer's window according to the RLC SN and PDCP SN.

[0169] In addition, regarding the incorrect submission of the first data, it should be noted that:

[0170] (1) When the RLC layer entity receives a MAC SDU (e.g., MAC SDU1) from the MAC layer and the MAC layer indicates that MACSDU1 is a data packet with a transmission error (or decoding failure), the RLC layer entity can submit the first data to the upper-layer PDCP layer entity.

[0171] (2) If the RLC layer entity receives the same MAC SDU from the MAC layer multiple times, and the MAC layer indicates a transmission error (or decoding failure) each time, the RLC layer entity may submit the MAC SDU to the PDCP layer entity each time; or, it may submit the MAC SDU to the PDCP layer entity for the first N times, and then not submit it again. The value of N can be determined by the access network device. Furthermore, the access network device may also indicate the value of N to the terminal device; or, the RLC layer entity may submit the MAC SDU to the PDCP layer entity when it receives an indication from the MAC layer that the decoding error rate is greater than a certain threshold (this threshold may be agreed upon by the protocol, or it may be determined by the access network device; furthermore, the access network device may also send the value of the threshold to the terminal device).

[0172] (3) The PDCP layer entity receives the SDU from the RLC and submits the PDU to the SDPA layer. The PDCP layer entity does not perform integrity verification on the first data included in the RLC SDU. For example, the integrity verification function of the PDCP layer entity in the terminal device may not be enabled or may not be active. Optionally, the PDCP layer entity may also indicate to the SDPA layer that the first data it submitted is data with a transmission error.

[0173] When an SDAP layer entity receives an SDU from PDCP, it may submit the PDU to an upper layer (such as the application layer). Optionally, it may also indicate to the upper layer that the first data it submitted was data with a transmission error.

[0174] In possible implementations, a verification method distinct from the CRC checkpoint of the PHY layer can be predefined or agreed upon. For example, a first verification method can be predefined or agreed upon. This first verification method can be a method for verifying the transmission error rate of the first data. The terminal device verifies the first data according to the first verification method, thereby determining the error transmission rate of the first data, which is beneficial for interpreting the meaning represented by the first data. If the terminal device needs to determine the error transmission rate of the first data, the access network device can send indication information to the terminal device, which can be used to indicate the first verification method.

[0175] The above-described Embodiment 1 and Embodiment 2 can be implemented separately or in combination. That is, the access network device in Embodiment 1 and the access network device in Embodiment 2 can be different access network devices, and the terminal device in Embodiment 1 and the terminal device in Embodiment 2 can be different terminal devices; or, the access network device in Embodiment 1 and the access network device in Embodiment 2 can be the same access network device, and the terminal device in Embodiment 1 and the terminal device in Embodiment 2 can be the same terminal device.

[0176] The configuration messages involved in this application embodiment can be sent to the terminal device in a variety of ways, such as through RRC signaling, without being limited to any specific method.

[0177] The embodiments provided in this application describe the method from the perspective of interaction between the terminal device and the access network device. The steps executed by the access network device can also be implemented by different communication devices. For example, a first device generates a configuration message, and a second device sends the configuration message. Alternatively, the first and second devices jointly complete the steps executed by the access network device in the embodiments of this application; this application does not limit the specific division method. When the network architecture includes one or more DUs, one or more CUs, and one or more radio units (RUs), the steps executed by the access network device can be implemented by the DUs, CUs, and RUs respectively. To implement the functions in the methods provided in the embodiments of this application, the terminal device and the access network device can include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0178] Figure 7 This is a schematic block diagram of a communication device 700 provided in an embodiment of this application. The communication device 700 can correspondingly implement the functions or steps implemented by the terminal device or access network device in the various method embodiments described above. The communication device 700 may include a processing module 710 and a transceiver module 720. Optionally, it may also include a storage unit, which can be used to store instructions (code or program) and / or data. The processing module 710 and the transceiver module 720 may be coupled to the storage unit. For example, the processing module 710 can read instructions (code or program) and / or data from the storage unit to implement the corresponding method. The above-mentioned units can be set independently, or partially or completely integrated.

[0179] It should be understood that the processing module 710 may be a processor or controller, such as a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing unit (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc. The transceiver module 720 is an interface circuit of the device for receiving signals from other devices. For example, when the device is implemented as a chip, the transceiver module 720 is an interface circuit of the chip for receiving signals from other chips or devices, or an interface circuit of the chip for sending signals to other chips or devices.

[0180] The communication device 700 can be an access network device or a terminal device as described in the above embodiments, or it can be a functional module within an access network device or a terminal device. For example, the communication device can be a chip (system) within an access network device or a terminal device. When the communication device 700 is an access network device or a terminal device, the processing module 710 can be, for example, a processor, and the transceiver module 720 can be, for example, a transceiver. Optionally, the transceiver can include radio frequency circuitry, and the storage unit can be, for example, a memory. For example, when the communication device 700 is a chip used in an access network device or a terminal device, the processing module 710 can be, for example, a processor, and the transceiver module 720 can be, for example, an input / output interface, pins, or circuits. The processing module 710 can execute computer execution instructions stored in the storage unit. Optionally, the storage unit is a storage unit inside the chip, such as a register or cache. The storage unit can also be a storage unit located outside the chip in the access network device or terminal device, such as a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, such as random access memory (RAM).

[0181] In some possible implementations, the communication device 700 can correspondingly implement the behavior and functions of the access network device in the above method embodiments, for example, implementing... Figure 5 and / or Figure 6The method executed by the access network device in the embodiment. The communication device 700 can be an access network device, a component (e.g., a chip or circuit) applied in the access network device, or a chip or chipset in the access network device, or a part of a chip for performing the relevant method function. For example, the transceiver module 720 can be used to perform Figure 5 S502 in the illustrated embodiment, and / or other processes used to support the techniques described herein; processing module 710 is used to perform, for example Figure 5 In the illustrated embodiment, S501, and / or other processes used to support the techniques described herein. For example, the transceiver module 720 can be used to perform... Figure 6 S601, S602 in the illustrated embodiments, and / or other processes used to support the technology described herein; processing module 710 is used to perform, for example Figure 6 Other processes used to support the techniques described herein are shown in the embodiments.

[0182] For example, the transceiver module 720 is used to send a configuration message, receive first data carried by the first logical channel, and send the first data. The configuration message is used to indicate that the first data does not need to undergo CRC at the PHY layer, the first data is data of the first service, the first service is a service that allows data error transmission or delivery, and the first data has not undergone CRC.

[0183] In a possible implementation, before the transceiver module 720 receives the first data carried by the first logical channel, the processing module 710 is used to map the QoS stream containing the first data only to the first PDCP layer entity through the SDAP layer entity.

[0184] In the possible implementations, the integrity verification function of the first PDCP layer entity is not enabled.

[0185] In a possible implementation, the transceiver module 720 is also used to receive second data carried by the second logical channel, which is then processed by CRC and then transmitted.

[0186] In a possible implementation, before sending the first data, the transceiver module 720 is also used to send a PHY PDU to the PHY layer through the MAC layer entity. The PHY PDU includes the first data but does not include the second data.

[0187] In possible implementations, the configuration message is one or more of the following: information of the first search space, first scrambling parameters, SPS information, or information included in the first DCI. Specifically, the DCI for scheduling the first data is located in the first search space; or, the DCI for scheduling the first data is scrambled by the first scrambling parameters; or, the first data is transmitted on the time-frequency resources configured by the SPS information; and the first DCI schedules the first data.

[0188] In possible implementations, the first service is a service that allows data to be transmitted or delivered incorrectly, including: the first service allows the data error transmission rate to be higher than a first threshold and / or lower than a second threshold.

[0189] In possible implementations, the first logical channel is also used to carry data for the second service, where the error transmission rate of the second service is lower than that of the first service; or, the first logical channel is a logical channel dedicated to carrying data for the first service.

[0190] In a possible implementation, the transceiver module 720 is also used to receive indication information, which indicates that the first data is data of the first service.

[0191] In possible implementations, the indication information is information sent by the core network, and / or the indication information is contained in the QFI.

[0192] In some possible implementations, the communication device 700 can correspondingly implement the behavior and functions of the terminal device in the above method embodiments, for example, implementing... Figure 5 and / or Figure 6 The method executed by the terminal device in the embodiments is described. The communication device 700 can be a terminal device, a component (e.g., a chip or circuit) applied in the terminal device, or a chip or chipset in the terminal device, or a part of a chip used to perform the relevant method function. For example, the transceiver module 720 can be used to execute... Figure 5 S502 in the illustrated embodiment, and / or other processes used to support the techniques described herein; processing module 710 is used to perform, for example Figure 5 Other processes are shown in the illustrated embodiments to support the techniques described herein. For example, the transceiver module 720 can be used to perform... Figure 6 S602, S603 in the illustrated embodiments, and / or other processes used to support the technology described herein; processing module 710 is used to perform, for example Figure 6 Other processes used to support the techniques described herein are shown in the embodiments.

[0193] For example, the transceiver module 720 is used to receive first data, which is data of a first service. The first service is a service that allows data to be transmitted or delivered incorrectly, and the first data has not undergone CRC. The transceiver module 720 is also used to deliver the first data carried by the first logical channel.

[0194] In a possible implementation, after the first data carried by the first logical channel is delivered, the processing module 710 is used to map the QoS stream containing the first data only to the first PDCP layer entity through the SDAP layer entity.

[0195] In the possible implementations, the integrity verification function of the first PDCP layer entity is not enabled.

[0196] In a possible implementation, the transceiver module 720 is further configured to receive second data, which is CRC-processed; before delivering the first data carried by the first logical channel, the transceiver module 720 is further configured to receive a MAC PDU through a MAC layer entity. This MAC PDU includes the first data but does not include the second data.

[0197] In a possible implementation, the transceiver module 720 is also used to receive a configuration message that indicates that the first data does not require CRC at the PHY layer.

[0198] In possible implementations, the configuration message is one of the following: information of the first search space, first scrambling parameters, SPS information, or information included in the first DCI. Specifically, the DCI for scheduling the first data is located in the first search space; or, the DCI for scheduling the first data is scrambled by the first scrambling parameters; or, the first data is transmitted on the time-frequency resources configured by the SPS information; and the first DCI schedules the first data.

[0199] In possible implementations, the first service is a service that allows data to be transmitted or delivered incorrectly, including: the first service allows the data error transmission rate to be higher than a first threshold and / or lower than a second threshold.

[0200] In possible implementations, the first logical channel is also used to carry data for the second service, where the error transmission rate of the second service is lower than that of the first service; or, the first logical channel is a logical channel dedicated to carrying data for the first service.

[0201] In a possible implementation, the transceiver module 720 is further configured to receive indication information, which can be used to indicate a first verification method. The terminal device verifies the first data according to the first verification method.

[0202] When the communication device 700 is a chip-based device or circuit, the transceiver module can be an input / output circuit and / or a communication interface; the processing module is an integrated processor, microprocessor, or integrated circuit.

[0203] Figure 8This is a schematic block diagram of a communication device 800 provided in an embodiment of this application. The communication device 800 can be a terminal device, capable of implementing the functions of the terminal device in the method provided in this application. Alternatively, the communication device 800 can be a device that supports the terminal device in implementing the corresponding functions in the method provided in this application. Alternatively, the communication device 800 can be an access network device, capable of implementing the functions of the access network device in the method provided in this application. Alternatively, the communication device 800 can be a device that supports the access network device in implementing the corresponding functions in the method provided in this application. The communication device 800 can be a chip system. In this embodiment, the chip system can be composed of chips or may include chips and other discrete devices. Specific functions can be found in the descriptions of the above method embodiments.

[0204] The communication device 800 includes one or more processors 801, used to implement or support the communication device 800 in implementing the functions of the terminal device or access network device in the methods provided in the embodiments of this application. For details, please refer to the detailed description in the method examples, which will not be repeated here. The processor 801 can also be called a processing unit or processing module, and can implement certain control functions. The processor 801 can be a general-purpose processor or a dedicated processor, etc. For example, it includes: a baseband processor, a central processing unit, an application processor, a modem processor, a graphics processor, an image signal processor, a digital signal processor, a video codec processor, a controller, a memory, and / or a neural network processor, etc. The baseband processor can be used to process communication protocols and communication data. The central processing unit can be used to control the communication device 800, execute software programs, and / or process data. Different processors can be independent devices or integrated into one or more processors, for example, integrated on one or more application-specific integrated circuits.

[0205] Optionally, the communication device 800 includes one or more memories 802 for storing instructions 804, which can be executed on the processor 801 to cause the communication device 800 to perform the method described in the above method embodiments. The memories 802 and the processor 801 are coupled. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. The processor 801 may operate in conjunction with the memories 802. At least one of the at least one memories may be included in the processor. It should be noted that the memory 802 is not mandatory, so in... Figure 8 The image is indicated by a dashed line.

[0206] Optionally, the memory 802 may also store data. The processor and memory may be configured separately or integrated together. In this embodiment, the memory 802 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it may be volatile memory, such as RAM. Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited thereto. The memory in this embodiment may also be a circuit or any other device capable of implementing storage functions for storing program instructions and / or data.

[0207] Optionally, the communication device 800 may include instructions 803 (sometimes referred to as code or program), which can be executed on the processor to cause the communication device 800 to perform the methods described in the above embodiments. Data may be stored in the processor 801.

[0208] Optionally, the communication device 800 may also include a transceiver 805 and an antenna 806. The transceiver 805 may be referred to as a transceiver unit, transceiver module, transceiver, transceiver circuit, transceiver, input / output interface, etc., and is used to realize the transmission and reception functions of the communication device 800 through the antenna 806.

[0209] The processor 801 and transceiver 805 described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency identification (RFID) integrated circuits, mixed-signal ICs, ASICs, printed circuit boards (PCBs), or electronic devices. The communication device described herein can be a standalone device (e.g., a standalone integrated circuit, a mobile phone, etc.) or a part of a larger device (e.g., a module embedded in other devices), as detailed in the foregoing description of terminal devices or terminal apparatuses, which will not be repeated here.

[0210] Optionally, the communication device 800 may further include one or more of the following components: a wireless communication module, an audio module, an external memory interface, internal memory, a universal serial bus (USB) interface, a power management module, an antenna, a speaker, a microphone, an input / output module, a sensor module, a motor, a camera, or a display screen, etc. It is understood that in some embodiments, the communication device 800 may include more or fewer components, or some components may be integrated, or some components may be separated. These components may be implemented in hardware, software, or a combination of software and hardware.

[0211] It should be noted that the communication device in the above embodiments can be a terminal device (or access network device), a circuit, a chip applied in a terminal device (or access network device), or other combined devices or components having the aforementioned terminal device (or access network device). When the communication device is a terminal device (or access network device), the transceiver module can be a transceiver, which may include an antenna and radio frequency circuits, etc., and the processing module can be a processor, such as a CPU. When the communication device is a component with the aforementioned terminal device (or access network device) functions, the transceiver module can be a radio frequency unit, and the processing module can be a processor. When the communication device is a chip system, the communication device can be an FPGA, a dedicated ASIC, a system-on-chip (SoC), a CPU, a network processor (NP), a DSP, a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips. The processing module can be the processor of the chip system. The transceiver module or communication interface can be the input / output interface or interface circuit of the chip system. For example, the interface circuit can be a code / data read / write interface circuit. The interface circuit can be used to receive code instructions (the code instructions are stored in memory and can be read directly from memory or through other devices) and transmit them to the processor; the processor can then execute the code instructions to perform the methods described in the above method embodiments. Alternatively, the interface circuit can also be a signal transmission interface circuit between a communication processor and a transceiver.

[0212] This application also provides a communication system, specifically, the communication system includes at least one terminal device, and may further include at least one access network device. Exemplarily, the communication system includes components for implementing the above... Figure 5 and / or Figure 6 Terminal devices for related functions and devices for implementing the above Figure 5 and / or Figure 6 An access network device for related functions. Alternatively, the communication system includes at least one terminal device and at least one access network device. Exemplarily, the communication system includes devices for implementing the above. Figure 5 and / or Figure 6 Terminal devices and terminal equipment for implementing the above-mentioned functions Figure 5 and / or Figure 6 The access network equipment includes access network devices with related functions. Optionally, the communication system may also include core network equipment. Please refer to the relevant descriptions in the above method embodiments for details, which will not be repeated here.

[0213] Alternatively, the communication system may include at least one access network device, and may also include core network equipment. For example, the communication system includes devices for implementing the above. Figure 5 and / or Figure 6 Access network devices and core network equipment with related functions. Optionally, the communication system may also include at least one device for implementing the above-mentioned functions. Figure 5 and / or Figure 6 A terminal device with related functions. Please refer to the relevant descriptions in the above method embodiments for details, which will not be repeated here. Alternatively, the communication system includes at least one access network device and a core network device. For example, the communication system includes devices for implementing the above... Figure 5 and / or Figure 6 Access network equipment that performs the functions related to the access network device. Optionally, the communication system may further include at least one device for implementing the above-mentioned functions. Figure 5 and / or Figure 6 Terminal devices for related functions. Please refer to the relevant descriptions in the above method embodiments for details, which will not be repeated here.

[0214] This application also provides a computer-readable storage medium, including instructions that, when executed on a computer, cause the computer to perform... Figure 5 and / or Figure 6 The method executed by the terminal device or access network device.

[0215] This application also provides a computer program product, including instructions that, when run on a computer, cause the computer to perform... Figure 5 and / or Figure 6 The method executed by the terminal device or access network device.

[0216] This application provides a chip system including a processor and potentially a memory, for implementing the functions of the terminal device or access network device described in the aforementioned methods. The chip system can be composed of chips or may include chips and other discrete components.

[0217] To achieve the above Figures 7-8In addition to the functions of the communication device, this application also provides a chip, including a processor, for supporting the communication device in implementing the functions involved in the terminal device or access network device in the above method embodiments. In one possible design, the chip is connected to a memory or the chip includes a memory for storing the computer programs or instructions and data necessary for the communication device.

[0218] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0219] Those skilled in the art will recognize that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0220] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0221] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0222] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0223] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the essential contributing part of the technical solution of this application, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), RAM, magnetic disks, or optical disks.

[0224] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method, characterized in that, Applied to terminal devices, including: Receive a configuration message, the configuration message being used to indicate that the first data does not require cyclic redundancy check (CRC) at the physical PHY layer; The first data is received, the first data has not undergone CRC, the first data is the data of the first service, and the first service is a service that allows data to be transmitted or delivered incorrectly. The first data carried by the first logical channel is delivered, and no CRC is performed on the first data before delivery; The method further includes, after delivering the first data carried by the first logical channel: The Service Quality of Service (QoS) stream containing the first data is mapped only to the First Packet Data Convergence Protocol (PDCP) layer entity through the Service Data Adaptation Protocol (SDAP) layer entity. The integrity verification function of the first PDCP layer entity is not enabled, and the SDAP layer entity can only map the data of the first service. The method further includes, before delivering the first data carried by the first logical channel: The MAC protocol data unit (PDU) is received through the Media Access Control (MAC) layer entity. The MAC PDU includes the first data but does not include the second data, which is CRC-processed.

2. The method as described in claim 1, characterized in that, The configuration message is one of the following: Information from the first search space, including downlink control information for scheduling the first data, is located within the first search space; or... The first scrambling parameter is used to scramble the downlink control information that schedules the first data; or... Semi-persistent scheduling (SPS) information, wherein the first data is transmitted on the time-frequency resources configured in the SPS information; The first downlink control information includes information that schedules the first data.

3. A communication method, characterized in that, Applied to access network devices, including: Send a configuration message, the configuration message being used to indicate that the first data does not need to undergo cyclic redundancy check (CRC) at the physical PHY layer, the first data being the data of the first service, the first service being a service that allows data to be transmitted or delivered incorrectly; Receive the first data carried by the first logical channel; The first data is sent without undergoing a CRC check. The method further includes, prior to receiving the first data carried by the first logical channel: The Service Data Adaptation Protocol (SDAP) layer entity maps the QoS (Quality of Service) flow containing the first data only to the First Packet Data Convergence Protocol (PDCP) layer entity, and the integrity verification function of the first PDCP layer entity is not enabled. The method further includes: before sending the first data, sending a PHY layer protocol data unit (PDU) to the PHY layer through a media access control (MAC) layer entity, wherein the PHY layer PDU includes the first data but does not include the second data, and the second data is CRC-processed.

4. The method as described in claim 3, characterized in that, The configuration message is one or more of the following: Information from the first search space, including downlink control information for scheduling the first data, is located within the first search space; or... The first scrambling parameter is used to scramble the downlink control information that schedules the first data; or... Semi-persistent scheduling (SPS) information, wherein the first data is transmitted on the time-frequency resources configured in the SPS information; The first downlink control information includes information that schedules the first data.

5. The method as described in claim 3 or 4, characterized in that, The method further includes: Receive indication information, the indication information being used to indicate that the first data is data of the first service.

6. The method as described in claim 5, characterized in that, The indication information is information sent by the core network, and / or the indication information is included in the Quality of Service Flow Indication (QFI).

7. A communication device, characterized in that, It includes a processing module and a transceiver module; The transceiver module is used to receive a receiving configuration message, first data, and to deliver the first data carried by the first logical channel. The configuration message is used to indicate that the first data does not need to be subjected to cyclic redundancy check (CRC) at the physical PHY layer, the first data has not undergone CRC, the first data is the data of the first service, the first service is a service that allows data to be transmitted or delivered incorrectly, and the first data is not subjected to CRC before being delivered. The processing module is used to process the first data; Wherein, after the transceiver module delivers the first data carried by the first logical channel, the processing module is further configured to: map the QoS stream where the first data is located only to the first packet data aggregation layer protocol PDCP layer entity through the Service Data Adaptation Protocol (SDAP) layer entity, wherein the integrity verification function of the first PDCP layer entity is not enabled, and the SDAP layer entity can only map the data of the first service; Before delivering the first data carried by the first logical channel, the transceiver module is further configured to: receive a MAC protocol data unit (PDU) through a media access control (MAC) layer entity, wherein the MAC PDU includes the first data but does not include the second data, and the second data is CRC-processed.

8. The apparatus as claimed in claim 7, characterized in that, The configuration message is one of the following: Information from the first search space, including downlink control information for scheduling the first data, is located within the first search space; or... The first scrambling parameter is used to scramble the downlink control information that schedules the first data; or... Semi-persistent scheduling (SPS) information, wherein the first data is transmitted on the time-frequency resources configured in the SPS information; The first downlink control information includes information that schedules the first data.

9. A communication device, characterized in that, It includes a processing module and a transceiver module; The processing module is used to determine a configuration message, which indicates that the first data does not need to undergo cyclic redundancy check (CRC) at the physical PHY layer, the first data being the data of the first service, and the first service being a service that allows data to be transmitted or delivered incorrectly. The transceiver module is used to send configuration messages, receive the first data carried by the first logical channel, and send the first data, wherein the first data has not undergone CRC. Before the transceiver module receives the first data carried by the first logical channel, the transceiver module is further configured to: The Service Data Adaptation Protocol (SDAP) layer entity maps the QoS (Quality of Service) flow containing the first data only to the First Packet Data Convergence Protocol (PDCP) layer entity, and the integrity verification function of the first PDCP layer entity is not enabled. Before sending the first data, the transceiver module is further configured to: send a PHY layer protocol data unit (PDU) to the physical PHY layer through a media access control (MAC) layer entity, wherein the PHY layer PDU includes the first data but does not include the second data, and the second data is CRC-processed.

10. The apparatus as claimed in claim 9, characterized in that, The configuration message is one or more of the following: Information from the first search space, including downlink control information for scheduling the first data, is located within the first search space; or... The first scrambling parameter is used to scramble the downlink control information that schedules the first data; or... Semi-persistent scheduling (SPS) information, wherein the first data is transmitted on the time-frequency resources configured in the SPS information; The first downlink control information includes information that schedules the first data.

11. The apparatus as claimed in claim 9 or 10, characterized in that, The transceiver module is also used for: Receive indication information, the indication information being used to indicate that the first data is data of the first service.

12. A communication device, characterized in that, The communication device includes a processor and a communication interface. The communication interface is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device. The processor is used to implement the method as described in claim 1 or 2 through logic circuits or executable code instructions, or the processor is used to implement the method as described in any one of claims 3-6 through logic circuits or executable code instructions.

13. A communication system, characterized in that, The communication system includes a terminal device and a network device, wherein the terminal device is used to implement the method as described in claim 1 or 2, and the network device is used to implement the method as described in any one of claims 3-6.

14. The system as described in claim 13, characterized in that, The system also includes core network equipment, which is used to send indication information, the indication information being used to indicate that the first data is data of a first service, the first service being a service that allows data to be transmitted or delivered incorrectly.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed, implements the method as described in claim 1 or 2, or the method as described in any one of claims 3-6.

Images