Data processing method and device and communication equipment

Abstract

Provided in an embodiment of the present application are a data processing method and apparatus, and a communication device, the method comprising: a node processes data through a borne protocol entity, the bearer having at least one of the following characteristics: at least two protocol entities of the bearer are protocol entities of the same type having different modes; the function of the at least one protocol entity of the bearer can be dynamically changed or semi-statically changed; the borne protocol entity comprises a target entity, and the target entity has at least partial functions of a PDCP entity and / or an RLC entity.

Description

Method and device for processing data, and communication equipment Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a method and apparatus for processing data, and a communication device. Background Art

[0002] Compared to 5G, future communication standards (such as 6G) will have more diverse application scenarios. To meet these diverse application scenarios, access network resources need to be more flexible.

[0003] Bearer, as an access network resource, cannot meet the diverse application scenarios if defined according to current communication standards (such as 5G). The current definition of bearer in communication standards lacks flexibility and needs to be redefined.

[0004] Summary of the Invention

[0005] Embodiments of the present application provide a method and apparatus for processing data, a communication device, a chip, a computer-readable storage medium, a computer program product, and a computer program.

[0006] The data processing method provided in the embodiment of the present application includes:

[0007] The node processes data through a protocol entity of a bearer, where the bearer has at least one of the following characteristics:

[0008] The at least two protocol entities carried by the carrier are protocol entities of the same type with different modes;

[0009] The function of at least one protocol entity of the bearer may be changed dynamically or semi-statically;

[0010] The protocol entity of the bearer includes a target entity, and the target entity has at least part of the functions of a Packet Data Convergence Protocol (PDCP) entity and / or a Radio Link Control (RLC) entity.

[0011] The data processing method provided in the embodiment of the present application includes:

[0012] The node's Media Access Control (MAC) entity determines the Quality of Service (QoS) information corresponding to the data and multiplexes the data into a Transport Block (TB) based on the QoS information corresponding to the data.

[0013] The MAC entity of the node delivers the TB to a physical (PHY) entity for transmission.

[0014] The data processing device provided in the embodiment of the application is applied to a node, wherein the node has a bearer; the device includes:

[0015] A processing unit, configured to process data through a protocol entity of a bearer, wherein the bearer has at least one of the following characteristics:

[0016] The at least two protocol entities carried by the carrier are protocol entities of the same type with different modes;

[0017] The function of at least one protocol entity of the bearer may be changed dynamically or semi-statically;

[0018] The protocol entity of the bearer includes a target entity, and the target entity has at least part of the functions of a PDCP entity and / or an RLC entity.

[0019] The data processing device provided in the embodiment of the application is applied to a node, wherein the node has a MAC entity and a PHY entity; the device includes:

[0020] The processing unit is configured to determine the QoS information corresponding to the data through the MAC entity, multiplex the data into the TB based on the QoS information corresponding to the data, and deliver the TB to the PHY entity for transmission.

[0021] The communication device provided in an embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the above-mentioned method for processing data.

[0022] The chip provided in the embodiment of the present application is used to implement the above-mentioned method for processing data.

[0023] Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the above-mentioned method for processing data.

[0024] The computer-readable storage medium provided in an embodiment of the present application is used to store a computer program, which enables a computer to execute the above-mentioned method for processing data.

[0025] The computer program product provided in the embodiments of the present application includes computer program instructions, which enable a computer to execute the above-mentioned method for processing data.

[0026] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned method for processing data.

[0027] Through the above technical solution, the redefined bearer has at least one of the following characteristics: at least two protocol entities of the bearer are protocol entities of the same type with different modes; the function of at least one protocol entity of the bearer can be changed dynamically or semi-statically; the protocol entity of the bearer includes a target entity, and the target entity has at least part of the functions of the PDCP entity and / or RLC entity; the bearer with these characteristics is more flexible, and when processing data through the protocol entity of this bearer, it can flexibly adapt to more diversified application scenarios of future communication standards (such as 6G). BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

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

[0030] FIG2 is a flowchart of a method for processing data according to an embodiment of the present application;

[0031] FIG3 is a schematic diagram of a protocol stack according to an embodiment of the present application;

[0032] FIG4 is a schematic diagram of a PDCP header provided in an embodiment of the present application;

[0033] FIG5 is a second schematic diagram of a protocol stack provided in an embodiment of the present application;

[0034] FIG6 is a third schematic diagram of a protocol stack provided in an embodiment of the present application;

[0035] FIG7-1 is a first schematic diagram of a data processing process of a PPLC entity provided in an embodiment of the present application;

[0036] FIG7-2 is a second schematic diagram of the data processing process of the PPLC entity provided in an embodiment of the present application;

[0037] FIG8 is a fourth schematic diagram of a protocol stack provided in an embodiment of the present application;

[0038] FIG9 is a second flow chart of a method for processing data provided in an embodiment of the present application;

[0039] FIG10 is a fifth schematic diagram of a protocol stack provided in an embodiment of the present application;

[0040] FIG11 is a schematic diagram of the first structure of a device for processing data provided in an embodiment of the present application;

[0041] FIG12 is a second schematic diagram of the structure of the device for processing data provided in an embodiment of the present application;

[0042] FIG13 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0043] FIG14 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0044] FIG15 is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0046] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. As shown in Figure 1, communication system 100 may include network device 110, which may be a device that communicates with terminal device 120 (also referred to as a communication terminal or terminal). Network device 110 provides communication coverage for a specific geographic area and can communicate with terminal devices located within the coverage area.

[0047] Figure 1 exemplarily shows a network device and two terminal devices. In some embodiments of the present application, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0048] The terminal device in FIG1 may be any terminal device. For example, the terminal device may refer to an access terminal, user equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handheld terminal, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolution network, etc.

[0049] It should be noted that Figure 1 is merely an example of a system applicable to this application. Of course, the methods described in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein simply describes an association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the associated objects are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, "A indicates B" can mean that A directly indicates B, for example, B can obtain information through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can obtain information through C; or it can mean that A and B have an association relationship. It should also be understood that the "correspondence" mentioned in the embodiments of this application can mean that there is a direct or indirect correspondence between two objects, or that there is an association relationship between the two objects, or a relationship between an indicator and the indicated, a configuration and the configured, and so on. It should also be understood that the “predefined” or “predefined rules” mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit its specific implementation method. For example, predefined can refer to a definition in a protocol. It should also be understood that in the embodiments of the present application, the “protocol” can refer to a standard protocol in the field of communications, such as an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0050] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0051] In Long Term Evolution (LTE), a dedicated data radio bearer (DRB) is associated with the packet data convergence protocol (PDCP) configuration, radio link control (RLC) configuration, and logical channel configuration belonging to the DRB through the DRB identity. In LTE Dual Connectivity (LTE DC), the DRB identity is also associated with the RLC configuration and logical channel configuration on the secondary cell group (SCG) side belonging to the DRB.

[0052] In New Radio (NR), a dedicated DRB is associated with the DRB's PDCP configuration, RLC configuration, logical channel configuration, and Service Data Adaptation Protocol (SDAP) configuration through a DRB identifier. It should be noted that the SDAP entity is per PDU session.

[0053] Whether in LTE or NR, once a bearer (i.e., DRB) is established, the PDCP configuration and RLC configuration of the bearer remain unchanged.

[0054] On the one hand, the data in a bearer may have different Quality of Service (QoS) requirements, so the data in a bearer may require different processing methods. For example, for extended reality (XR) services, the data in a bearer may include I-frames, P-frames, and B-frames. I-frames, P-frames, and B-frames have different levels of importance. I-frames are more important than P-frames and B-frames. Therefore, the QoS requirements for I-frames and P / B-frames are different.

[0055] On the other hand, the security processing function of a bearer is enabled or disabled at the bearer level (per bearer). Security processing functions include encryption and integrity protection. Once the security processing function of a bearer is enabled, all data on the bearer must be securely processed. Once the security processing function of a bearer is disabled, no security processing is performed on all data on the bearer. If all data on a bearer is securely processed, the data transmission rate will be reduced due to limited data processing efficiency. Therefore, if selective security processing is performed on the data of a bearer, the purpose of protecting data security without affecting the data transmission rate can be achieved. In addition, in the current solution, enabling or disabling the security processing function of a bearer requires reconfiguration, that is, L2 reconstruction and reset are required to achieve it, and it is not possible to dynamically enable or disable the security processing function of a bearer.

[0056] Compared to 5G's three main application scenarios—enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), future communication standards (such as 6G) will feature more diverse application scenarios, requiring single or simultaneous support for multiple service QoS requirements, including high bandwidth, large connections, low latency, deterministic latency, and high-precision perception. Therefore, the network must be able to agilely and intelligently respond to emerging service demands. These requirements include not only bandwidth, latency, number of connections, and coverage, but also flexible orchestration of access network resources to enable intelligent and flexible management of network functions.

[0057] The currently defined bearer lacks flexibility and needs to be redefined based on new scenarios, new services, and new requirements of future communication standards (such as 6G). To this end, the following technical solutions of the embodiments of this application are proposed.

[0058] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0059] FIG2 is a flow chart of a method for processing data provided in an embodiment of the present application. As shown in FIG2 , the method for processing data includes the following steps:

[0060] Step 201: The node processes data through the protocol entity carried by the carrier, and the carrier has at least one of the following characteristics: at least two protocol entities carried by the carrier are protocol entities of the same type with different modes; the function of at least one protocol entity carried by the carrier can be changed dynamically or semi-statically; the protocol entity carried by the carrier includes a target entity, and the target entity has at least part of the functions of the PDCP entity and / or RLC entity.

[0061] The technical solution of the embodiment of the present application is applied to a node, which may be a network device or a terminal device.

[0062] In the embodiment of the present application, the protocol entity of the bearer has the following two implementation methods:

[0063] Method 1: The carried protocol entity includes at least one of the following: a PDCP entity and an RLC entity.

[0064] Here, the functions of the PDCP entity may refer to the definition of the target standard. For example, the functions of the PDCP entity include at least one of the following: header compression function, integrity protection function, encryption and decryption function, serial number (SN) and reordering function.

[0065] It should be noted that the SN and reordering functions of the PDCP entity refer to: the SN adding function and the SN-based reordering function of the PDCP entity. The SN of the PDCP entity refers to the PDCP SN.

[0066] Here, the functions of the RLC entity may refer to the definition of the target standard. For example, the functions of the RLC entity include at least one of the following: Automatic Repeat-reQuest (ARQ) function, segmentation function, SN and reordering function.

[0067] It should be noted that the SN and reordering function of the RLC entity refer to: the SN adding function and the SN-based reordering function of the RLC entity. The SN of the RLC entity refers to the RLC SN.

[0068] In some implementations, to support low-latency services, the RLC entity introduces a pre-processing function. This means that RLC entities operating in Unacknowledged Mode (UM) may not add a SN to data without segmenting it. RLC entities operating in Acknowledged Mode (AM) support ARQ, SN, and reordering.

[0069] In some embodiments, the carried protocol entity includes an RLC entity with a first mode and an RLC entity with a second mode; the RLC entity with the first mode is used to process data with first attribute information; and the RLC entity with the second mode is used to process data with second attribute information.

[0070] As an example: the first mode is AM mode, and the second mode is UM mode. Alternatively, the first mode is UM mode, and the second mode is AM mode.

[0071] In some embodiments, the first attribute information includes at least one of the following: a first QoS attribute; a first data type; a first importance; and a first data priority. The second attribute information includes at least one of the following: a second QoS attribute; a second data type; a second importance; and a second data priority. Here, the first QoS attribute may, for example, not allow packet loss or require ACK / NACK feedback. The second QoS attribute may, for example, allow packet loss or not require ACK / NACK feedback. Here, the first data type may, for example, be an I frame. The second data type may, for example, be a B frame and / or a P frame. The first importance may, for example, be a high importance. The second importance may, for example, be a low importance. The first data priority may, for example, be a high priority. The second data priority may, for example, be a low priority.

[0072] In one example, as shown in Figure 3, the carried protocol entity includes one PDCP entity and two RLC entities (i.e., RLC entity 1 and RLC entity 2), and the modes of the two RLC entities are different. That is, one PDCP entity is associated with two RLC entities with different modes. For example, the mode of RLC entity 1 is AM, and the mode of RLC entity 2 is UM, or the mode of RLC entity 1 is UM, and the mode of RLC entity 2 is AM. The data in a QoS flow has different attribute information, and the PDCP entity diverts the data to different RLC entities according to the attribute information of the data. For example: for data with the first attribute information, the PDCP entity diverts it to the RLC entity with the AM mode, and for data with the second attribute information, the PDCP entity diverts it to the RLC entity with the UM mode.

[0073] In some embodiments, the PDCP packet header corresponding to the data carries first indication information and / or second indication information, the first indication information is used to indicate whether the data has been encrypted, and the second indication information is used to indicate whether the data has been integrity protected, and the PDCP packet header is the packet header corresponding to the PDCP entity.

[0074] In one example, as shown in Figure 4, the PDCP header carries two indications. The CI field represents the first indication. Setting the CI field to 1 indicates that encryption is enabled for the data (i.e., the data is encrypted), while setting the CI field to 0 indicates that encryption is disabled for the data (i.e., the data is not encrypted). The II field represents the second indication. Setting the II field to 1 indicates that integrity protection is enabled for the data (i.e., the data is integrity protected), while setting the II field to 0 indicates that integrity protection is disabled for the data (i.e., the data is not integrity protected).

[0075] In some implementations, the node obtains a first index and determines whether a function of at least one protocol entity is enabled based on the first index. The first index is used to determine a pattern of whether the functions of each protocol entity in the at least one protocol entity are enabled. Specifically, the pattern corresponding to the first index is determined based on a first mapping relationship, and whether the function of the at least one protocol entity is enabled is determined based on the pattern corresponding to the first index; the first mapping relationship includes patterns corresponding to each index in a plurality of indexes. Here, the first index is carried in a packet header of the data.

[0076] Here, optionally, the functions of the at least one protocol entity include at least one of the following: QoS flow to bearer mapping function of the SDAP entity; encryption and decryption function of the PDCP entity; integrity protection function of the PDCP entity; and segmentation function of the RLC entity.

[0077] As an example: the first mapping relationship can be configured through RRC signaling. Specifically, a set of multiple L2 function on / off (i.e., patterns) is configured through RRC signaling. The indication of each L2 function on / off in the set is represented by an index. The following Table 1 gives a set of 4 L2 function on / off. The L2 function takes the integrity protection function and the encryption and decryption function as examples, but is not limited to this. The L2 function can also include other more or fewer functions.

[0078] Index index 1 Integrity protection function: On Encryption and decryption function: On

[0079] Index 2 Integrity Protection: Off Encryption and Decryption: On Index 3 Integrity Protection: On Encryption and Decryption: Off Index 4 Integrity Protection: Off Encryption and Decryption: Off

[0080] Table 1

[0081] The above index is carried in the PDCP header of the data to indicate whether the L2 function is on or off, so that the L2 function can be dynamically scheduled per data.

[0082] To better understand the L2 functions, the following Table 2 lists them.

[0083]

[0084] Table 2

[0085] The SN, whether it is a PDCP SN or an RLC SN, is used for data packet reordering, duplicate detection, and feedback. Therefore, the size of the SN cannot be changed dynamically or semi-statically at the per-data level.

[0086] The ARQ function of the RLC entity is used to indicate to the data receiver whether feedback is required for the data if it has not yet been received. If the ARQ function is enabled or disabled on a per-data basis, the receiver cannot determine whether feedback is required for the missing data if the data has not yet been received. Therefore, the ARQ function cannot be enabled or disabled dynamically or semi-statically on a per-data basis. Similarly, the RLC mode cannot be changed dynamically or semi-statically on a per-data basis.

[0087] The PDCP entity's header compression function requires that the data receiver receive the complete packet to establish a header compression context. This allows the receiver to receive the header-compressed data packet and decompress the headers based on the header compression context. Furthermore, there is no requirement to dynamically or semi-statically enable or disable header compression per data packet. Therefore, header compression cannot be enabled or disabled dynamically or semi-statically per data packet.

[0088] For the encryption and decryption function and integrity protection function of the PDCP entity, the function can be turned on or off dynamically or semi-statically per data indication.

[0089] Mode 2: The carried protocol entity includes a target entity, and the target entity has at least some functions of a PDCP entity and / or an RLC entity.

[0090] The SN and reordering functions of the PDCP and RLC entities are somewhat redundant. Considering that the PDCP SN is used for encryption, decryption, and integrity protection in addition to data reordering, the functions of the PDCP and RLC entities can be merged and implemented through a newly defined target entity.

[0091] Here, the target entity has at least some of the functions of a PDCP entity and / or an RLC entity. For example, the functions of the target entity are a combination of the functions of the PDCP entity and the functions of the RLC entity. The target entity may be called a Packet Process and Link Control (PPLC) entity. Of course, the target entity may also have other names, which are not limited in this application.

[0092] In one example, FIG5 shows a schematic diagram of the protocol stacks on the UE and base station sides, where the UE and base station have equivalent protocol stacks. The protocol stack before the PDCP entity and the RLC entity are merged is shown on the left side of FIG5 . An SDAP entity is located above the PDCP entity and the RLC entity, and a Media Access Control (MAC) entity and a physical (PHY) entity are located below the PDCP entity and the RLC entity. The protocol stack after the PDCP entity and the RLC entity are merged is shown on the right side of FIG5 . An SDAP entity is located above the PPLC entity, and a MAC entity and a PHY entity are located below the PPLC entity.

[0093] In some embodiments, the target entity has multiple modes, including at least a first mode, a second mode, and a third mode. Here, the first mode can be referred to as an acknowledgement mode (AM), the second mode can be referred to as an unacknowledgement mode (UM), and the third mode can be referred to as a transparent transmission mode (TM). Of course, the first mode, the second mode, and the third mode can also have other names, which are not limited in this application. The following describes the functions of the target entity in the first mode, the second mode, and the third mode, respectively.

[0094] Option 1) In some embodiments, the functions of the target entity having the first mode include at least one of the following: integrity protection function, encryption and decryption function, header compression function, ARQ function, sequence number (Serial Number, SN) and reordering function, and segmentation function; the functions of the target entity having the second mode include at least one of the following: integrity protection function, encryption and decryption function, header compression function, SN and reordering function, and segmentation function; the functions of the target entity having the third mode include at least one of the following: transparent transmission function.

[0095] Option 2) In some embodiments, the target entity's functionality in the first mode includes at least one of the following: integrity protection, encryption / decryption, ARQ, SN and reordering, and segmentation. The target entity's functionality in the second mode includes at least one of the following: integrity protection, encryption / decryption, SN and reordering, and segmentation. The target entity's functionality in the third mode includes at least one of the following: transparent transmission. Here, the target entity has an SDAP entity above it, and the SDAP entity has at least header compression.

[0096] Option 3) In some embodiments, the target entity in the first mode includes at least one of the following functions: ARQ, SN and reordering, and segmentation; the target entity in the second mode includes at least one of the following functions: SN and reordering, and segmentation; and the target entity in the third mode includes at least one of the following functions: transparent transmission. Here, the target entity includes an SDAP entity, which has at least one of the following functions: integrity protection, encryption and decryption, and header compression.

[0097] To more clearly understand the functions of the target entity in the three modes, the following Table 3 lists them.

[0098]

[0099] Table 3

[0100] In some embodiments, the carried protocol entity includes a target entity with a first mode and a target entity with a second mode; the target entity with the first mode is used to process data with first attribute information; the target entity with the second mode is used to process data with second attribute information.

[0101] As an example: the first mode is AM mode, and the second mode is UM mode. Alternatively, the first mode is UM mode, and the second mode is AM mode.

[0102] In some embodiments, the first attribute information includes at least one of the following: a first QoS attribute; a first data type; a first importance; and a first data priority. The second attribute information includes at least one of the following: a second QoS attribute; a second data type; a second importance; and a second data priority. Here, the first QoS attribute may, for example, not allow packet loss or require ACK / NACK feedback. The second QoS attribute may, for example, allow packet loss or not require ACK / NACK feedback. Here, the first data type may, for example, be an I frame. The second data type may, for example, be a B frame and / or a P frame. The first importance may, for example, be a high importance. The second importance may, for example, be a low importance. The first data priority may, for example, be a high priority. The second data priority may, for example, be a low priority.

[0103] In some embodiments, the node determines the bearer identifier corresponding to the QoS flow through the SDAP entity according to the first mapping rule, and determines the logical channel identifier and / or bearer identifier corresponding to the data according to the attribute information of each data in the QoS flow, and transfers the data to the corresponding target entity according to the bearer identifier and / or the logical channel identifier; the first mapping rule is a mapping rule from the QoS flow identifier to the bearer identifier; or, the node determines the bearer identifier and logical channel identifier corresponding to each data in the QoS flow through the SDAP entity according to the second mapping rule, and transfers the data to the corresponding target entity according to the bearer identifier and the logical channel identifier; the second mapping rule is a mapping rule from <QoS flow identifier, data attribute information> to <bearer identifier, logical channel identifier>.

[0104] In one example, as shown in FIG. 6, the protocol entities of the bearer include 2 PPLC entities (i.e., PPLC entity 1 and PPLC entity 2), and the modes of the 2 PPLC entities are different. For example, the mode of PPLC entity 1 is AM, and the mode of PPLC entity 2 is UM, or the mode of PPLC entity 1 is UM, and the mode of PPLC entity 2 is AM. The data in a QoS flow has different attribute information, and the SDAP entity distributes the data to different PPLC entities according to the attribute information of the data. For example: for the data with the first attribute information, the SDAP entity distributes it to the PPLC entity with the mode of AM, and for the data with the second attribute information, the SDAP entity distributes it to the PPLC entity with the mode of UM. As an implementation manner, the SDAP entity determines the bearer identifier corresponding to the QoS flow according to the first mapping rule, so as to map the QoS flow to the bearer; then, the SDAP entity determines the logical channel identifier and / or bearer identifier corresponding to the data according to the attribute information of each data in the QoS flow, so as to map the data to the corresponding PPLC entity. As another implementation manner, the second mapping rule configured by the RRC, the SDAP entity determines the bearer identifier and logical channel identifier corresponding to each data in the QoS flow according to the second mapping rule, so as to map the data to the corresponding PPLC entity.

[0105] In some embodiments, the target packet header corresponding to the data carries the first indication information and / or the second indication information, the first indication information is used to indicate whether the data has been encrypted, and the second indication information is used to indicate whether the data has been integrity protected, and the target packet header is the packet header corresponding to the target entity.

[0106] In one example, the PPLC header (i.e., the target header) carries two indications. The CI field represents the first indication. Setting the CI field to 1 indicates that encryption is enabled for the data (i.e., the data is encrypted), while setting the CI field to 0 indicates that encryption is disabled for the data (i.e., the data is not encrypted). The II field represents the second indication. Setting the II field to 1 indicates that integrity protection is enabled for the data (i.e., the data is integrity protected), while setting the II field to 0 indicates that integrity protection is disabled for the data (i.e., the data is not integrity protected).

[0107] In some implementations, the node obtains a first index and determines whether a function of at least one protocol entity is enabled based on the first index. The first index is used to determine a pattern of whether the functions of each protocol entity in the at least one protocol entity are enabled. Specifically, the pattern corresponding to the first index is determined based on a first mapping relationship, and whether the function of the at least one protocol entity is enabled is determined based on the pattern corresponding to the first index; the first mapping relationship includes patterns corresponding to each index in a plurality of indexes. Here, the first index is carried in a packet header of the data.

[0108] Here, optionally, the functions of the at least one protocol entity include at least one of the following: a mapping function of the SDAP entity's QoS flow to a bearer; an encryption and decryption function of the target entity; an integrity protection function of the target entity; or a segmentation function of the target entity.

[0109] As an example, the first mapping relationship can be configured via RRC signaling. Specifically, a set of multiple L2 function on / off modes (i.e., patterns) is configured via RRC signaling. Each L2 function on / off indication in the set is represented by an index. The index is carried in the PPLC packet header of the data to indicate whether the L2 function is on or off, thereby enabling dynamic per-data scheduling of L2 functions.

[0110] In some embodiments, the node performs at least one of the following processing on the data received from the upper layer through the target entity:

[0111] generating a first packet header for the data, and storing the data in a first buffer area;

[0112] Performing a first processing on the data in the first buffer area, the first processing comprising at least one of the following: header compression processing, encryption processing, and integrity protection processing;

[0113] storing the data after the first processing in a second buffer area;

[0114] performing a second process on the data in the second buffer area or the data after the first process, wherein the second process includes a segmentation process;

[0115] A first packet header is added to the data after the second processing or the data after the first processing.

[0116] Furthermore, optionally, the node further performs at least one of the following processes through the target entity:

[0117] storing the data after adding the first packet header in the third buffer area;

[0118] When it is determined that the data needs to be retransmitted, the data in the third buffer area is retransmitted, or the data in the third buffer area is processed by removing the first packet header and then segmenting and adding the second packet header before retransmitting.

[0119] In some embodiments, the node performs at least one of the following processing on the data received from the bottom layer through the target entity:

[0120] storing the data in a fourth buffer area;

[0121] removing the first packet header or the second packet header from the data in the fourth buffer area;

[0122] The data after the first packet header or the second packet header is removed is subjected to at least one of the following processing: reassembly processing, reordering processing, decryption processing, integrity protection verification processing, and header decompression processing.

[0123] In one example, Figure 7-1 illustrates the data processing process of a PPLC entity in a non-feedback retransmission mode. The processing on the transmitting side includes: after receiving data from the upper layer, generating a PPLC header for the data and storing the data in the transmission buffer; performing header compression, encryption, and integrity protection on the data in the transmission buffer; segmenting the data processed in the previous step; and adding a PPLC header to the data processed in the previous step. The processing on the receiving side includes: after receiving data from the lower layer, storing the data in the reception buffer; removing the PPLC header from the data; reassembling the data processed in the previous step; decrypting the data processed in the previous step; performing integrity protection verification on the data processed in the previous step; and decompressing the header of the data processed in the previous step.

[0124] In one example, Figure 7-2 illustrates the data processing process of a PPLC entity based on feedback retransmission mode. The processing on the transmitting side includes: after receiving data from the upper layer, generating a PPLC header for the data and storing the data in transmission buffer 1; performing header compression, encryption, and integrity protection on the data in transmission buffer 1; storing the processed data in transmission buffer 2; segmenting the processed data; adding a PPLC header to the processed data; and storing the data with the PPLC header added in the retransmission buffer. When data retransmission is required based on an indication from the receiving side, the data is retrieved from the retransmission buffer, the PPLC header is removed from the data, and a new PPLC header is added. Alternatively, the PPLC header is removed from the data, segmented, and a new PPLC header is added. The processing process on the receiving side includes: if a retransmission indication is received from the bottom layer, the sending side is instructed to retransmit the data; if data is received from the bottom layer, the data is stored in the reception buffer; the PPLC packet header is removed from the data; the data processed in the previous step is reassembled; the data processed in the previous step is reordered; the data processed in the previous step is decrypted; the data processed in the previous step is integrity verified; and the data processed in the previous step is decompressed.

[0125] It should be noted that when the L2 function is programmable, the function of the PPLC entity is changed dynamically or semi-statically, so the steps shown in Figures 7-1 and 7-2 above can also be executed only partially (that is, the part corresponding to the function of the PPLC entity).

[0126] In some implementations, the protocol stack of the node supports data duplication. The data duplication can be carrier aggregation (CA)-based data duplication (i.e., CA-based data duplication) or DC-based data duplication (i.e., DC-based data duplication). This is described below in conjunction with the target entity.

[0127] For CA based data duplication, the MAC entity of the node obtains first configuration information, and the first configuration information is used to configure at least one of the following: the data corresponding to the first logical channel needs to be copied and transmitted, the number of repetitions of the copied transmission, and the service cell list corresponding to each repetition; after the MAC entity of the node receives the data from the first logical channel from the target entity, it copies the data into multiple copies based on the number of repetitions of the copied transmission; based on the service cell list corresponding to each repetition, each copy of the data is multiplexed into a MAC PDU in the scheduling authorization of the corresponding service cell list, and the MAC PDU is transmitted on the authorization of the corresponding service cell list.

[0128] Here, the first configuration information may be configured by RRC. For CA-based data duplication, RRC configures a logical channel as CA-based data duplication and then configures the number of repetitions for the replicated transmission and the list of serving cells corresponding to each repetition for the MAC entity. Compared to traditional CA-based PDCP duplication, only one LCID is required to satisfy this function.

[0129] For DC based data duplication, after the target entity of the node receives the data from the SDAP entity, it copies the data; transmits the first copy of the data to the MAC entity on the Master Cell Group (MCG) side through the first MAC entity of the node, and transmits the second copy of the data to the MAC entity on the SCG side through the second MAC entity of the node; the first copy of the data received by the MAC entity on the MCG side and the second copy of the data received by the MAC entity on the SCG side are associated with the same bearer identifier and are associated with different logical channel identifiers; or, after the target entity of the node receives the data from the SDAP entity, it transmits the data to the MAC entity on the MCG side through the first MAC entity of the node, or transmits the data to the MAC entity on the SCG side through the second MAC entity of the node; the data received by the MAC entity on the MCG side and the data received by the MAC entity on the SCG side are associated with the same bearer identifier and are associated with different logical channel identifiers.

[0130] Here, the logical channel identifier associated with the second copy of the data is used by the MAC entity on the SCG side to determine the bearer identifier associated with the second copy of the data and forward the second copy of the data to the target entity on the MCG side based on the tunnel corresponding to the bearer identifier; or, the logical channel identifier associated with the data is used by the MAC entity on the SCG side to determine the bearer identifier associated with the data and forward the data to the target entity on the MCG side based on the tunnel corresponding to the bearer identifier; or, the logical channel identifier associated with the data is used by the MAC entity on the MCG side to determine the bearer identifier associated with the data and deliver the data to the target entity on the MCG side based on the bearer identifier.

[0131] In one example, Figure 8 illustrates the protocol stacks on the UE side and the network side. The protocol stack on the UE side includes the SDAP entity, the PPLC entity, the MAC entity 1, and the MAC entity 2. The protocol stack on the network side includes the SDAP entity, the PPLC entity, the MCG MAC entity on the MCG side, and the SCG MAC entity on the SCG side.

[0132] As an implementation method, for the UE side, after the PPLC entity receives data A from the SDAP entity, it copies the data, sends data A through MAC entity 1, and sends the copied data a through MAC entity 2. For the network side, the MCG MAC entity receives data A and delivers data A to the PPLC entity on the MCG side; the SCG MAC entity receives data a and delivers data a to the PPLC entity on the MCG side. Here, the MCG MAC entity receives the bearer identifier 1 and LCID 1 associated with data A, and the SCG MAC entity receives the bearer identifier 1 and LCID 2 associated with data a. The SCG MAC entity determines that data a is copied data on the MCG side and / or determines the bearer or PPLC entity to which data a belongs based on the bearer identifier 1 and LCID 2 associated with data a, and forwards data a to the PPLC entity on the MCG side through the GTP tunnel corresponding to bearer identifier 1.

[0133] As another way, for the UE side, after the PPLC entity receives data A from the SDAP entity, it sends data A through MAC entity 1, or sends data A through MAC entity 2. For the network side, if the MCG MAC entity receives data A, it delivers data A to the PPLC entity on the MCG side; if the SCG MAC entity receives data A, it delivers data A to the PPLC entity on the MCG side. Here, the MCG MAC entity receives the bearer identifier 1 and LCID 1 associated with data A, and the SCG MAC entity receives the bearer identifier 1 and LCID 2 associated with data A. The SCG MAC entity determines that data A is the assigned bearer or PPLC entity based on the bearer identifier 1 and LCID 2 associated with data A, and forwards data A to the PPLC entity on the MCG side through the GTP tunnel corresponding to bearer identifier 1.

[0134] It should be noted that the bearer in the embodiment of the present application refers to a data bearer, which may also be referred to as a radio data bearer (DRB).

[0135] The technical solution of the embodiment of the present application redefines the bearer to adapt to the more complex business requirements and application scenarios of future communication standards (such as 6G), thereby achieving the purpose of carrying flexible and adaptive business requirements and application scenarios.

[0136] FIG9 is a second flow chart of a method for processing data provided in an embodiment of the present application. As shown in FIG9 , the method for processing data includes the following steps:

[0137] Step 901: The MAC entity of the node determines the QoS information corresponding to the data, and multiplexes the data into the TB based on the QoS information corresponding to the data.

[0138] Step 902: The MAC entity of the node delivers the TB to the PHY entity for transmission.

[0139] The technical solution of the embodiment of the present application is applied to a node, which may be a network device or a terminal device.

[0140] In some implementations, the node is a network device, and the node receives data from a core network, and a packet header of the data carries QoS information corresponding to the data.

[0141] In some implementations, the node is a terminal device, and a MAC entity of the node receives data from an upper layer, and a packet header of the data carries QoS information corresponding to the data.

[0142] Here, the QoS information may be a QoS flow identifier (QoS flow id) or a QoS identifier (QoS id) and the like.

[0143] The QoS information is used to indicate QoS requirements; the MAC entity of the node multiplexes data with the same QoS requirements into the same TB; or, the MAC entity of the node multiplexes data whose similarity of QoS requirements meets specific conditions into the same TB.

[0144] Here, the purpose of the MAC entity multiplexing data whose QoS requirements meet specific conditions into the same TB is: the MAC entity multiplexes data with similar QoS requirements into the same TB. Here, the specific condition can be that the similarity is greater than or equal to the similarity threshold. This application does not limit the calculation method of similarity, and any similarity calculation method can be applied to the solution of this application.

[0145] In some embodiments, the TB or the QoS information is associated with first configuration information, where the first configuration information is used to configure at least one of the following: a maximum number of HARQ retransmissions corresponding to data, whether data supports cross-carrier retransmission, and a maximum number of cross-carrier retransmissions of data. Here, the first configuration information is configured by sending RRC signaling or is specified by a protocol.

[0146] Based on this, the MAC entity of the node determines at least one of the maximum HARQ retransmission times of the data in the TB or the data associated with the Qos information, whether cross-carrier retransmission is supported, and the maximum cross-carrier retransmission times based on the first configuration information.

[0147] In some embodiments, when the MAC entity of the node determines that the data in the TB or the data associated with the Qos information reaches the maximum number of cross-carrier retransmissions, the node declares a radio link failure, thereby triggering the RRC connection reestablishment process.

[0148] It should be noted that the cross-carrier retransmission in the above solution means that the initial transmission carrier and the retransmission carrier of the data belong to different carriers, or different spectrum ranges, or different center frequencies.

[0149] In one example, as shown in Figure 10, the MAC entity can perform data scheduling based on QoS. For the downlink, when a network device (such as a base station) receives data from the core network, the MAC entity of the network device can distinguish the data into different QoS flows. For example, each packet header of the data from the core network carries a QoS flow ID or QoS ID, which is used to indicate the QoS requirement of each data. The network device distinguishes the data into different QoS flows based on the QoS flow ID or QoS ID carried in the data header. For the uplink, the terminal device receives data from the upper layer. Similarly, the terminal device can also distinguish the data into different QoS flows. The MAC entity multiplexes data with the same or similar QoS requirements into a TB and delivers it to the PHY entity for transmission. On the one hand, to meet the requirement of zero packet loss rate, the network side configures or specifies the maximum number of HARQ retransmissions for the TB where such data is located. In addition, it is additionally specified that such data supports cross-carrier retransmission, and the maximum number of cross-carrier retransmissions is configured or specified. When the maximum number of cross-carrier retransmissions is reached, the terminal device declares a radio link failure, triggering the RRC connection reestablishment process. Alternatively, each QoS flow ID or QoS ID can be configured through RRC signaling to support cross-carrier retransmissions. The MAC entity determines which data can be retransmitted across carriers based on the RRC signaling configuration.

[0150] In some embodiments, the TB has at least one of the following characteristics: the packet header of each data multiplexed in the TB carries the Qos information corresponding to the data; the packet header of each data multiplexed in the TB carries the serial number (SN) corresponding to the data; the packet header of the TB carries the SN corresponding to the TB.

[0151] Here, the TB (i.e., MAC PDU) multiplexes multiple data. The header (or sub-header) of each data item carries the QoS information corresponding to the data item (such as the QoS flow ID, QoS ID). This QoS information is used to index the QoS flow to which it belongs. In addition, the header (or sub-header) of each data item may also carry a SN, which is used to indicate the number of the data item within the QoS flow.

[0152] Here, the header of the TB (ie, MAC PDU) carries an SN, which is used to indicate the number of the TB at the MAC layer.

[0153] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will no longer describe the various possible combinations separately. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in each embodiment described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the scope of protection of the present application.

[0154] It should also be understood that in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply a precedence in 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 the present application. In addition, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate the first direction of transmission of signals or data from a site to a user equipment in a cell, "uplink" is used to indicate the second direction of transmission of signals or data from a user equipment in a cell to a site, and "sidelink" is used to indicate the third direction of transmission of signals or data from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0155] FIG11 is a schematic diagram of the structure of a data processing device provided in an embodiment of the present application. The device is applied to a node, and the node has a bearer. As shown in FIG11 , the data processing device includes:

[0156] The processing unit 1101 is configured to process data through a protocol entity of a bearer, where the bearer has at least one of the following characteristics:

[0157] The at least two protocol entities carried by the carrier are protocol entities of the same type with different modes;

[0158] The function of at least one protocol entity of the bearer may be changed dynamically or semi-statically;

[0159] The protocol entity of the bearer includes a target entity, and the target entity has at least part of the functions of a PDCP entity and / or an RLC entity.

[0160] In some embodiments, the bearer protocol entity includes an RLC entity having a first mode and an RLC entity having a second mode;

[0161] The RLC entity having the first mode is used to process data having first attribute information;

[0162] The RLC entity with the second mode is used to process data with second attribute information.

[0163] In some embodiments, the bearer protocol entity further includes: a PDCP entity, and the PDCP entity is associated with the RLC entity with the first mode and the RLC entity with the second mode.

[0164] In some embodiments, the target entity has multiple modes, and the multiple modes include at least a first mode, a second mode, and a third mode.

[0165] In some embodiments, the functions of the target entity having the first mode include at least one of the following: integrity protection function, encryption and decryption function, header compression function, ARQ function, SN and reordering function, and segmentation function; the functions of the target entity having the second mode include at least one of the following: integrity protection function, encryption and decryption function, header compression function, SN and reordering function, and segmentation function; the functions of the target entity having the third mode include at least one of the following: transparent transmission function.

[0166] In some embodiments, the functions of the target entity having the first mode include at least one of the following: integrity protection function, encryption and decryption function, ARQ function, SN and reordering function, and segmentation function; the functions of the target entity having the second mode include at least one of the following: integrity protection function, encryption and decryption function, SN and reordering function, and segmentation function; the functions of the target entity having the third mode include at least one of the following: transparent transmission function.

[0167] In some implementations, an SDAP entity is provided on the target entity, and the SDAP entity has at least a header compression function.

[0168] In some embodiments, the functions of the target entity having the first mode include at least one of the following: ARQ function, SN and reordering function, and splitting function; the functions of the target entity having the second mode include at least one of the following: SN and reordering function, and splitting function; the functions of the target entity having the third mode include at least one of the following: transparent transmission function.

[0169] In some implementations, an SDAP entity is provided on the target entity, and the SDAP entity has at least one of the following functions: integrity protection function, encryption and decryption function, and header compression function.

[0170] In some implementation manners, when the bearer protocol entity includes a target entity, the processing unit 1101 is configured to perform at least one of the following processing on the data received from the upper layer through the target entity:

[0171] generating a first packet header for the data, and storing the data in a first buffer area;

[0172] Performing a first processing on the data in the first buffer area, the first processing comprising at least one of the following: header compression processing, encryption processing, and integrity protection processing;

[0173] storing the data after the first processing in a second buffer area;

[0174] performing a second process on the data in the second buffer area or the data after the first process, wherein the second process includes a segmentation process;

[0175] A first packet header is added to the data after the second processing or the data after the first processing.

[0176] In some embodiments, the processing unit 1101 is configured to further perform at least one of the following processes through the target entity:

[0177] storing the data after adding the first packet header in the third buffer area;

[0178] When it is determined that the data needs to be retransmitted, the data in the third buffer area is retransmitted, or the data in the third buffer area is processed by removing the first packet header and then segmenting and adding the second packet header before retransmitting.

[0179] In some implementations, when the carried protocol entity includes a target entity, the processing unit 1101 is configured to perform at least one of the following processing on the data received from the bottom layer through the target entity:

[0180] storing the data in a fourth buffer area;

[0181] Process the data in the fourth buffer area to remove the first packet header or the second packet header;

[0182] Perform at least one of the following processes on the data after removing the first packet header or the second packet header: recombination process, reordering process, decryption process, integrity protection verification process, packet header decompression process.

[0183] In some embodiments, the bearer protocol entity includes a target entity with a first mode and a target entity with a second mode; the target entity with the first mode is used to process data with first attribute information; the target entity with the second mode is used to process data with second attribute information.

[0184] In some embodiments, the processing unit 1101 is configured to determine, according to a first mapping rule, a bearer identifier corresponding to a QoS flow through an SDAP entity, and determine a logical channel identifier and / or a bearer identifier corresponding to the data according to the attribute information of each data in the QoS flow, and transfer the data to the corresponding target entity according to the bearer identifier and / or the logical channel identifier; the first mapping rule is a mapping rule from a QoS flow identifier to a bearer identifier; or, determine, according to a second mapping rule, a bearer identifier and a logical channel identifier corresponding to each data in the QoS flow through the SDAP entity, and transfer the data to the corresponding target entity according to the bearer identifier and the logical channel identifier; the second mapping rule is a mapping rule from <QoS flow identifier, data attribute information> to <bearer identifier, logical channel identifier>.

[0185] In some embodiments, when the bearer protocol entity includes the target entity, the method further includes: the processing unit 1101 is configured to obtain first configuration information through a MAC entity, and the first configuration information is used to configure at least one of the following: data corresponding to a first logical channel needs to be copied and transmitted, the number of repetitions of the copy transmission, and a serving cell list corresponding to each repetition; after receiving data from the first logical channel from the target entity through the MAC entity, copy the data into multiple copies based on the number of repetitions of the copy transmission; multiplex each copy of the data into a MAC protocol data unit (PDU) in the scheduling authorization of the corresponding serving cell list, and transmit the MAC PDU on the authorization of the corresponding serving cell list.

[0186] In some embodiments, when the protocol entity of the bearer includes the target entity, the method further includes: the processing unit 1101 is used to copy the data after receiving the data from the SDAP entity through the target entity; transmit the first copy of the data to the MAC entity on the main cell group MCG side through the first MAC entity of the node, and transmit the second copy of the data to the MAC entity on the secondary cell group SCG side through the second MAC entity of the node; the first copy of the data received by the MAC entity on the MCG side and the second copy of the data received by the MAC entity on the SCG side are associated with the same bearer identifier and are associated with different logical channel identifiers; or, after receiving the data from the SDAP entity through the target entity, transmit the data to the MAC entity on the MCG side through the first MAC entity of the node, or transmit it to the MAC entity on the SCG side through the second MAC entity of the node; the data received by the MAC entity on the MCG side and the data received by the MAC entity on the SCG side are associated with the same bearer identifier and are associated with different logical channel identifiers.

[0187] In some embodiments, the logical channel identifier associated with the second copy of the data is used by the MAC entity on the SCG side to determine the bearer identifier associated with the second copy of the data and forward the second copy of the data to the target entity on the MCG side based on the tunnel corresponding to the bearer identifier; or, the logical channel identifier associated with the data is used by the MAC entity on the SCG side to determine the bearer identifier associated with the data and forward the data to the target entity on the MCG side based on the tunnel corresponding to the bearer identifier; or,

[0188] The logical channel identifier associated with the data is used by the MAC entity on the MCG side to determine the bearer identifier associated with the data and deliver the data to the target entity on the MCG side based on the bearer identifier.

[0189] In some embodiments, the PDCP header or target header corresponding to the data carries first indication information and / or second indication information, the first indication information is used to indicate whether the data has been encrypted, and the second indication information is used to indicate whether the data has been integrity protected. The PDCP header is the header corresponding to the PDCP entity, and the target header is the header corresponding to the target entity.

[0190] In some embodiments, the processing unit 1101 is used to obtain a first index and determine whether a function of at least one protocol entity is enabled based on the first index, where the first index is a pattern for determining whether the functions of each protocol entity in the at least one protocol entity are enabled.

[0191] In some embodiments, the processing unit 1101 is used to determine the pattern corresponding to the first index based on a first mapping relationship, and determine whether the function of at least one protocol entity is enabled based on the pattern corresponding to the first index; the first mapping relationship includes patterns corresponding to each index in multiple indexes.

[0192] In some embodiments, the functions of the at least one protocol entity include at least one of the following: QoS flow to bearer mapping function of SDAP entity; encryption and decryption function of PDCP entity; integrity protection function of PDCP entity; segmentation function of RLC entity.

[0193] In some embodiments, the functions of the at least one protocol entity include at least one of the following: SDAP entity's QoS flow to bearer mapping function; target entity's encryption and decryption function; target entity's integrity protection function; target entity's segmentation function.

[0194] In some implementations, the first index is carried in a header of the data.

[0195] Those skilled in the art should understand that the relevant description of the above-mentioned data processing device in the embodiment of the present application can be understood with reference to the relevant description of the data processing method in the embodiment of the present application.

[0196] FIG12 is a second schematic diagram of the structure of a data processing device provided in an embodiment of the present application, which is applied to a node. The node has a MAC entity and a PHY entity. As shown in FIG12 , the data processing device includes:

[0197] The processing unit 1201 is configured to determine the QoS information corresponding to the data through the MAC entity, multiplex the data into a TB based on the QoS information corresponding to the data, and deliver the TB to the PHY entity for transmission.

[0198] In some embodiments, the node is a network device, and the apparatus further comprises:

[0199] The communication unit 1202 is configured to receive data from the core network, wherein the packet header of the data carries QoS information corresponding to the data.

[0200] In some implementations, the node is a terminal device, and a MAC entity of the node receives data from an upper layer, and a packet header of the data carries QoS information corresponding to the data.

[0201] In some embodiments, the QoS information is used to indicate QoS requirements; the processing unit 1201 is used to multiplex data with the same QoS requirements into the same TB through the MAC entity; or, multiplex data whose QoS requirements are similar and meet specific conditions into the same TB.

[0202] In some embodiments, the TB or the Qos information is associated with first configuration information, and the first configuration information is used to configure at least one of the following: the maximum number of HARQ retransmissions corresponding to the data, whether the data supports cross-carrier retransmission, and the maximum number of cross-carrier retransmissions of the data.

[0203] In some implementations, the first configuration information is configured through RRC signaling or specified by a protocol.

[0204] In some embodiments, the processing unit 1201 is used to determine at least one of the maximum HARQ retransmission times of the data in the TB or the data associated with the Qos information, whether cross-carrier retransmission is supported, and the maximum cross-carrier retransmission times based on the first configuration information.

[0205] In some embodiments, the processing unit 1201 is configured to, when determining that the data in the TB or the data associated with the Qos information reaches the maximum number of cross-carrier retransmissions, cause the node to declare a radio link failure, thereby triggering an RRC connection reestablishment process.

[0206] In the above solution, the cross-carrier retransmission means that the initial transmission carrier and the retransmission carrier of the data belong to different carriers, or different spectrum ranges, or different center frequency points.

[0207] In some embodiments, the TB has at least one of the following characteristics: the packet header of each data multiplexed in the TB carries the Qos information corresponding to the data; the packet header of each data multiplexed in the TB carries the SN corresponding to the data; the packet header of the TB carries the SN corresponding to the TB.

[0208] Those skilled in the art should understand that the relevant description of the above-mentioned data processing device in the embodiment of the present application can be understood with reference to the relevant description of the data processing method in the embodiment of the present application.

[0209] Figure 13 is a schematic diagram of a communication device 1300 provided in an embodiment of the present application. The communication device can be a terminal device or a network device. The communication device 1300 shown in Figure 13 includes a processor 1310, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0210] Optionally, as shown in FIG13 , the communication device 1300 may further include a memory 1320. The processor 1310 may call and execute a computer program from the memory 1320 to implement the method in the embodiment of the present application.

[0211] The memory 1320 may be a separate device independent of the processor 1310 , or may be integrated into the processor 1310 .

[0212] Optionally, as shown in FIG13 , the communication device 1300 may further include a transceiver 1330 , and the processor 1310 may control the transceiver 1330 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0213] The transceiver 1330 may include a transmitter and a receiver. The transceiver 1330 may further include an antenna, and the number of antennas may be one or more.

[0214] Optionally, the communication device 1300 may specifically be a network device in an embodiment of the present application, and the communication device 1300 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0215] Optionally, the communication device 1300 may specifically be a mobile terminal / terminal device of an embodiment of the present application, and the communication device 1300 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0216] Figure 14 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 1400 shown in Figure 14 includes a processor 1410, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0217] Optionally, as shown in FIG14 , the chip 1400 may further include a memory 1420 , wherein the processor 1410 may call and execute a computer program from the memory 1420 to implement the method in the embodiment of the present application.

[0218] The memory 1420 may be a separate device independent of the processor 1410 , or may be integrated into the processor 1410 .

[0219] Optionally, the chip 1400 may further include an input interface 1430. The processor 1410 may control the input interface 1430 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0220] Optionally, the chip 1400 may further include an output interface 1440. The processor 1410 may control the output interface 1440 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0221] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0222] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

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

[0224] FIG15 is a schematic block diagram of a communication system 1500 provided in an embodiment of the present application. As shown in FIG15 , the communication system 1500 includes a terminal device 1510 and a network device 1520 .

[0225] Among them, the terminal device 1510 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1520 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0226] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0227] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0228] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0229] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0230] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0231] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0232] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0233] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0234] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0235] The embodiment of the present application also provides a computer program.

[0236] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0237] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0238] Those skilled in the art will appreciate that the units and algorithm steps of each example 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 performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0239] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0240] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0241] The units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of the solution of this embodiment according to actual needs.

[0242] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0243] If the functions are implemented in the form of 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 technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0244] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for processing data, the method comprising: The node processes data through a protocol entity of a bearer, where the bearer has at least one of the following characteristics: The at least two protocol entities carried by the carrier are protocol entities of the same type with different modes; The function of at least one protocol entity of the bearer may be changed dynamically or semi-statically; The protocol entity of the bearer includes a target entity, and the target entity has at least part of the functions of a Packet Data Convergence Protocol PDCP entity and / or a Radio Link Control RLC entity.

2. The method according to claim 1, wherein The protocol entity of the bearer includes an RLC entity with a first mode and an RLC entity with a second mode; The RLC entity having the first mode is used to process data having first attribute information; The RLC entity with the second mode is used to process data with second attribute information.

3. The method according to claim 2, wherein: The carried protocol entity further includes: a PDCP entity, and the PDCP entity is associated with the RLC entity with the first mode and the RLC entity with the second mode.

4. The method according to any one of claims 1 to 3, wherein The target entity has multiple modes, and the multiple modes include at least a first mode, a second mode, and a third mode.

5. The method according to claim 4, wherein The functions of the target entity having the first mode include at least one of the following: integrity protection function, encryption and decryption function, header compression function, automatic repeat request ARQ function, sequence number SN and reordering function, and segmentation function; The function of the target entity having the second mode includes at least one of the following: integrity protection function, encryption and decryption function, header compression function, SN and reordering function, and segmentation function; The function of the target entity having the third mode includes at least one of the following: a transparent transmission function.

6. The method according to claim 4, wherein: The function of the target entity having the first mode includes at least one of the following: integrity protection function, encryption and decryption function, ARQ function, SN and reordering function, and segmentation function; The function of the target entity having the second mode includes at least one of the following: integrity protection function, encryption and decryption function, SN and reordering function, and segmentation function; The function of the target entity having the third mode includes at least one of the following: a transparent transmission function.

7. The method according to claim 6, wherein: An SDAP entity is located above the target entity, and the SDAP entity at least has a header compression function.

8. The method according to claim 4, wherein: The function of the target entity having the first mode includes at least one of the following: ARQ function, SN and reordering function, and segmentation function; The function of the target entity having the second mode includes at least one of the following: SN and reordering function, segmentation function; The function of the target entity having the third mode includes at least one of the following: a transparent transmission function.

9. The method according to claim 8, wherein An SDAP entity is provided on the target entity, and the SDAP entity has at least one of the following functions: integrity protection function, encryption and decryption function, and header compression function.

10. The method according to any one of claims 1 to 9, wherein When the carried protocol entity includes a target entity, the node processes the data through the carried protocol entity, including: The node processes the data received from the upper layer through the target entity to perform at least one of the following operations: Generate a first packet header for the data and store the data in a first buffer; Perform a first processing on the data in the first buffer, where the first processing includes at least one of the following processes: packet header compression processing, encryption processing, integrity protection processing; Store the data after the first processing in a second buffer; Perform a second processing on the data in the second buffer or the data after the first processing, where the second processing includes segmentation processing; Add a first packet header to the data after the second processing or the data after the first processing.

11. The method according to claim 10, wherein: The node also processes the data received from the upper layer through the target entity to perform at least one of the following operations: Store the data after adding the first packet header in a third buffer; In the case where it is determined that the data needs to be retransmitted, retransmit the data in the third buffer, or perform a first packet header removal processing on the data in the third buffer, then perform segmentation processing and add a second packet header before retransmitting.

12. The method according to any one of claims 1 to 11, wherein In the case where the bearer protocol entity includes the target entity, the node processes the data through the bearer protocol entity, including: The node processes the data received from the lower layer through the target entity to perform at least one of the following operations: Store the data in a fourth buffer; Perform a first packet header or second packet header removal processing on the data in the fourth buffer; Perform at least one of the following processes on the data after removing the first packet header or the second packet header: recombination processing, reordering processing, decryption processing, integrity protection verification processing, packet header decompression processing.

13. The method according to any one of claims 1 to 12, wherein The bearer protocol entity includes a target entity with a first mode and a target entity with a second mode; The target entity with the first mode is used to process data with first attribute information; The target entity with the second mode is used to process data with second attribute information.

14. The method according to claim 13, wherein The method further includes: The node determines the bearer identifier corresponding to the quality of service (QoS) flow according to a first mapping rule through the service data adaptation protocol (SDAP) entity, and determines the logical channel identifier and / or bearer identifier corresponding to the data according to the attribute information of each data in the QoS flow, and delivers the data to the corresponding target entity according to the bearer identifier and / or the logical channel identifier; the first mapping rule is a mapping rule from the QoS flow identifier to the bearer identifier; or The node determines the bearer identifier and logical channel identifier corresponding to each data in the QoS flow according to a second mapping rule through the SDAP entity, and delivers the data to the corresponding target entity according to the bearer identifier and the logical channel identifier; the second mapping rule is a mapping rule from <QoS flow identifier, data attribute information> to <bearer identifier, logical channel identifier>.

15. The method according to any one of claims 1 to 14, wherein In the case where the bearer protocol entity includes the target entity, the method further includes: A media access control (MAC) entity of the node obtains first configuration information, where the first configuration information is used to configure at least one of the following: data corresponding to the first logical channel needs to be replicated and transmitted, the number of repetitions of the replicated transmission, and a serving cell list corresponding to each repetition; After the MAC entity of the node receives the data from the first logical channel from the target entity, it copies the data into multiple copies based on the number of repetitions of the copy transmission; based on the service cell list corresponding to each repetition, it multiplexes each copy of the data into a MAC protocol data unit PDU in the scheduling authorization of the corresponding service cell list, and transmits the MAC PDU on the authorization of the corresponding service cell list.

16. The method according to any one of claims 1 to 14, wherein When the carried protocol entity includes the target entity, the method further includes: After receiving the data from the SDAP entity, the target entity of the node copies the data; transmits the first copy of the data to the MAC entity on the primary cell group MCG side through the first MAC entity of the node, and transmits the second copy of the data to the MAC entity on the secondary cell group SCG side through the second MAC entity of the node; the first copy of the data received by the MAC entity on the MCG side and the second copy of the data received by the MAC entity on the SCG side are associated with the same bearer identifier and are associated with different logical channel identifiers; or, After the target entity of the node receives data from the SDAP entity, it transmits the data to the MAC entity on the MCG side through the first MAC entity of the node, or transmits the data to the MAC entity on the SCG side through the second MAC entity of the node; the data received by the MAC entity on the MCG side and the data received by the MAC entity on the SCG side are associated with the same bearer identifier and are associated with different logical channel identifiers.

17. The method according to claim 16, wherein The logical channel identifier associated with the second data is used by the MAC entity on the SCG side to determine the bearer identifier associated with the second data and forward the second data to the target entity on the MCG side based on the tunnel corresponding to the bearer identifier; or The logical channel identifier associated with the data is used by the MAC entity on the SCG side to determine the bearer identifier associated with the data and forward the data to the target entity on the MCG side based on the tunnel corresponding to the bearer identifier; or, The logical channel identifier associated with the data is used by the MAC entity on the MCG side to determine the bearer identifier associated with the data and deliver the data to the target entity on the MCG side based on the bearer identifier.

18. The method according to any one of claims 1 to 17, wherein The PDCP packet header or target packet header corresponding to the data carries first indication information and / or second indication information, the first indication information is used to indicate whether the data has been encrypted, and the second indication information is used to indicate whether the data has been integrity protected. The PDCP packet header is the packet header corresponding to the PDCP entity, and the target packet header is the packet header corresponding to the target entity.

19. The method according to any one of claims 1 to 18, wherein The method further comprises: The node obtains a first index and determines whether a function of at least one protocol entity is enabled based on the first index, where the first index is a pattern for determining whether a function of each protocol entity in the at least one protocol entity is enabled.

20. The method according to claim 19, wherein The determining, based on the first index, whether a function of at least one protocol entity is enabled includes: The pattern corresponding to the first index is determined based on a first mapping relationship, and whether the function of at least one protocol entity is enabled is determined based on the pattern corresponding to the first index; the first mapping relationship includes patterns corresponding to each index in a plurality of indexes.

21. The method according to claim 19 or 20, wherein The functions of the at least one protocol entity include at least one of the following: Mapping function of SDAP entity's QoS flow to bearer; Encryption and decryption functions of the PDCP entity; PDCP entity integrity protection function; Segmentation functionality of the RLC entity.

22. The method according to claim 19 or 20, wherein The functions of the at least one protocol entity include at least one of the following: Mapping function of SDAP entity's QoS flow to bearer; The encryption and decryption functions of the target entity; Integrity protection function of the target entity; Segmentation function of the target entity.

23. The method according to any one of claims 19 to 22, wherein The first index is carried in the header of the data.

24. A method for processing data, the method comprising: The media access control (MAC) entity of the node determines the QoS information corresponding to the data, and multiplexes the data into a transport block (TB) based on the QoS information corresponding to the data; The MAC entity of the node delivers the TB to a physical PHY entity for transmission.

25. The method according to claim 24, wherein The node is a network device, and the method further includes: The node receives data from a core network, and a packet header of the data carries QoS information corresponding to the data.

26. The method according to claim 24, wherein The node is a terminal device, and the method further includes: The MAC entity of the node receives data from an upper layer, and the packet header of the data carries QoS information corresponding to the data.

27. The method according to any one of claims 24 to 26, wherein The QoS information is used to indicate QoS requirements; The multiplexing of the data into the TB based on the QoS information corresponding to the data includes: The MAC entity of the node multiplexes data with the same QoS requirement into the same TB; or, The MAC entity of the node multiplexes data whose similarity of QoS requirements meets specific conditions into the same TB.

28. The method according to any one of claims 24 to 27, wherein The TB or the Qos information is associated with first configuration information, and the first configuration information is used to configure at least one of the following: the maximum number of HARQ retransmissions corresponding to the data, whether the data supports cross-carrier retransmission, and the maximum number of cross-carrier retransmissions of the data.

29. The method according to claim 28, wherein The first configuration information is configured through radio resource control RRC signaling or specified by a protocol.

30. The method according to claim 28 or 29, wherein The method further comprises: The MAC entity of the node determines at least one of the maximum HARQ retransmission times of the data in the TB or the data associated with the Qos information, whether cross-carrier retransmission is supported, and the maximum cross-carrier retransmission times based on the first configuration information.

31. The method according to claim 30, wherein The method further comprises: When the MAC entity of the node determines that the data in the TB or the data associated with the Qos information reaches the maximum number of cross-carrier retransmissions, the node declares a radio link failure, thereby triggering the RRC connection reestablishment process.

32. The method according to any one of claims 28 to 31, wherein The cross-carrier retransmission means that the initial transmission carrier and the retransmission carrier of the data belong to different carriers, or different spectrum ranges, or different center frequency points.

33. The method according to any one of claims 24 to 32, wherein The TB has at least one of the following characteristics: The header of each data multiplexed in the TB carries the QoS information corresponding to the data; The header of each data multiplexed in the TB carries the sequence number SN corresponding to the data; The packet header of the TB carries the SN corresponding to the TB.

34. A data processing device, applied to a node, the node having a bearer; the device comprising: A processing unit, configured to process data through a protocol entity of a bearer, wherein the bearer has at least one of the following characteristics: The at least two protocol entities carried by the carrier are protocol entities of the same type with different modes; The function of at least one protocol entity of the bearer may be changed dynamically or semi-statically; The protocol entity of the bearer includes a target entity, and the target entity has at least part of the functions of a Packet Data Convergence Protocol PDCP entity and / or a Radio Link Control RLC entity.

35. A data processing device, applied to a node, wherein the node has a MAC entity and a PHY entity; the device comprising: a processing unit, configured to determine, through a MAC entity, QoS information corresponding to the data, and multiplex the data into a TB based on the QoS information corresponding to the data; The TB is delivered to the PHY entity for transmission.

36. A communication device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to perform the method according to any one of claims 1 to 23, or the method according to any one of claims 24 to 33.

37. A chip comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 23, or the method according to any one of claims 24 to 33.

38. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 23, or the method according to any one of claims 24 to 33.

39. A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 1 to 23, or any one of claims 24 to 33.

40. A computer program, the computer program causing a computer to perform the method of any one of claims 1 to 23, or any one of claims 24 to 33.

Images