WO2023174044A1 - Communication method and apparatus - Google Patents

Abstract

Provided are a communication method and apparatus. The method comprises: obtaining first data, the first data being data that is not subjected to integrity protection, being associated with a first MAC PDU, and being associated with a first PDCP entity; and if a first condition is satisfied, discarding the first data, the first condition comprising an integrity verification result of data associated with the first data. Whether the data that is not subjected to integrity protection is discarded is further determined by means of the integrity verification result of the data subjected to integrity protection, and a method for processing the data that is not subjected to integrity protection is provided. In addition, the accuracy of data reception or the accuracy of data submitted to an upper layer can be improved, and the communication quality/efficiency can also be improved. For example, if the first condition is satisfied, the first data is discarded, and the more cases the first condition comprises, the higher the requirement for reserved data is, so that the accuracy of data reception or the accuracy of the data submitted to the upper layer can be improved.

Description

A communication method and device

This application claims priority to the Chinese patent application submitted to the State Intellectual Property Office of China on March 17, 2022, with application number 202210266127.2 and application title "A communication method and device", the entire content of which is incorporated into this application by reference. middle.

Technical field

The present application relates to the field of communication, and in particular, to a communication method and device.

Background technique

With the rapid development of communication technology, the information security issues of mobile communication systems have received more and more attention. The integrity protection (IP) function is a function that prevents user data from being tampered with. The integrity protection function includes integrity protection and integrity verification. Generally speaking, the integrity protection function is performed through the packet data convergence protocol (PDCP) layer. For example, the sending end performs integrity protection on the header and data part of the PDCP protocol data unit (PDU), and the receiving end performs integrity verification on the PDCP PDU.

Currently, for each radio bearer (RB), if the RB is configured with the integrity protection function, then all data (data) on the RB (for example, all PDCP data PDUs) will be integrity protected. Protection, so that the receiving end can check its integrity and discard it if the verification fails. In some cases, only part of the data on the RB (for example, part of the PDCP data PDU) may be integrity protected (hereinafter referred to as partial integrity protection).

It should be noted that "all data on the RB" does not include PDCP control PDU.

Therefore, in the case of partial integrity protection, how to deal with data that is not integrity protected has become an urgent technical issue that needs to be solved.

Contents of the invention

This application provides a communication method and device to facilitate processing of data without integrity protection in the case of partial integrity protection.

In a first aspect, this application provides a communication method, which can be executed by a first communication device, or can also be executed by a component (such as a chip, chip system, etc.) configured in the first communication device, or also It can be implemented by a logic module or software that can realize all or part of the functions of the first communication device, and this application does not limit this.

Exemplarily, the method includes: obtaining first data, the first data is data without integrity protection, the first data is associated with a first medium access control (medium access control, MAC) PDU, and is associated with a first medium access control (MAC) PDU. A PDCP entity is associated; the first condition is met and the first data is discarded. The first condition includes one or more of the following: the second data integrity check fails, the second data is associated with the first MAC PDU, and The first PDCP entity is associated; the third data integrity check fails, and the third data is associated with the first MAC PDU and is associated with the second PDCP entity; the fourth data integrity check fails, and the fourth data is associated with the second PDCP entity. Two MAC PDUs are associated and related to the first PDCP entity associated; the fifth data integrity check fails, the fifth data is associated with the second MAC PDU, and is associated with the second PDCP entity; or the sixth data integrity check fails, the sixth data is associated with the second MAC PDU associated, and associated with the third PDCP entity.

Based on the above technical solution, after the first communication device obtains the data that is not integrity protected (i.e., the first data), it can discard the second data if the integrity-protected data associated with it fails to be verified. One data, wherein the integrity-protected data verification failure associated with it may be a second data integrity verification failure, and the second data and the first data are associated with the same MAC PDU and are associated with the same PDCP entities are associated; or, the third data integrity check may fail, and the third data and the first data are associated with the same MAC PDU and are associated with different PDCP entities; or, it may be the fourth data. The integrity check fails, and the fourth data and the first data are associated with different MAC PDUs and are associated with the same PDCP entity; alternatively, the integrity check of the fifth data fails, and the fifth data and the first data The data is associated with different MAC PDUs and different PDCP entities, but the fifth data and the third data are associated with the same PDCP entity; alternatively, the sixth data integrity check may fail and the sixth data The first data is associated with different MAC PDUs and different PDCP entities. In addition, the sixth data and the third data are associated with different PDCP entities. Based on the verification results of the integrity-protected data, it is then determined whether to discard the data that is not integrity-protected, thereby providing the first communication device with a method for processing the data that is not integrity-protected. In addition, it is helpful to improve the accuracy of data reception or the accuracy of data submitted to the upper layer, and is also beneficial to improving communication quality/efficiency. For example, there are many cases where data without integrity protection is discarded. In other words, the conditions for submitting data without integrity protection to the upper layer are stricter, which is beneficial to improving the accuracy of data reception or the accuracy of data submitted to the upper layer. sex.

In conjunction with the first aspect, in some possible implementations of the first aspect, at least one of the first data, the second data, the third data, the fourth data, the fifth data, or the sixth data is different from MAC PDU associated.

Before performing the integrity check, the first communication device considers the situation that at least one data in the MAC PDU is fragmented data. In other words, the second communication device segments certain data and sends it through different MAC PDUs. In this case where segmentation exists, at least one of the first data, the second data, the third data, the fourth data, the fifth data, or the sixth data is associated with different MAC PDUs. For example, at least one of first data, second data, third data, fourth data, fifth data, or sixth data is associated with the first MAC PDU and the second MAC PDU.

In conjunction with the first aspect, in some possible implementations of the first aspect, the above method further includes: discarding one or more of the second data, the third data, the fourth data, the fifth data, or the sixth data. item.

One possible implementation is that if a certain data integrity check in the data associated with the same MAC PDU fails, all data in the MAC PDU can be discarded, which will help improve the accuracy of data reception or send data to the upper layer. Accuracy of data submitted. For example, when the second data integrity check fails and/or the third data integrity check fails, the first communication device may also discard the second data and the third data; when the fourth data integrity check fails, When the integrity check of the fifth data and/or the sixth data fails, the fourth data, the fifth data and the sixth data can also be discarded; similarly, when the integrity check of the fifth data and/or the sixth data fails, the fourth data, the fifth data and the sixth data can also be discarded. The fifth data and the sixth data.

Another possible implementation is that when a certain data integrity check in the data associated with the same MAC PDU fails, the data in the MAC PDU that fails the integrity check and the data that is not integrity protected can be discarded. Data will help reduce the possibility of data tampering without integrity protection, thereby helping to improve the accuracy of data reception or the accuracy of data submitted to the upper level.

In conjunction with the first aspect, in some possible implementations of the first aspect, the above method further includes: not discarding the first data when the second condition is met; wherein the second condition includes one or more of the following : The second data integrity check is successful; the third data integrity check is successful; the fourth data integrity check is successful; the fifth data integrity check is successful; or the sixth data integrity check is successful.

In conjunction with the first aspect, in some possible implementations of the first aspect, the above method further includes: determining, according to the first indication information, that at least one of the first data, the second data, or the third data is consistent with the first data. The MAC PDU is associated; and/or, based on the second indication information, it is determined that at least one of the fourth data, the fifth data, or the sixth data is associated with the second MAC PDU.

It can be understood that when the first communication device obtains multiple MAC PDUs, it needs to determine which data is associated with the same MAC PDU, so as to facilitate integrity-protected data verification based on the data associated with the same MAC PDU. Check the results to determine whether to discard data without integrity protection, which will help improve the accuracy of data reception or the accuracy of data submitted to the upper layer. One possible implementation is that the first communication device determines that at least one of the first data, the second data, and the third data is associated with the first MAC PDU based on the first indication information; and/or, based on the second The indication information determines that at least one of the fourth data, the fifth data, and the sixth data is associated with the second MAC PDU, wherein the first indication information and the second indication information can be received separately or together. The first indication information and the second indication information may be received at the same time or not at the same time.

Optionally, the first indication information comes from the MAC layer of the first communication device.

Optionally, the second indication information comes from the MAC layer of the first communication device.

The first indication information and/or the second indication information comes from the MAC layer of the first communication device. In other words, the MAC layer of the first communication device can send indication information to the PDCP layer to indicate which data comes from the same MAC PDU.

In conjunction with the first aspect, in some possible implementations of the first aspect, the first indication information includes number information corresponding to at least one of the first data, the second data, or the third data; and/or, The second indication information includes number information corresponding to at least one of the fourth data, the fifth data, or the sixth data.

Among them, the above numbering information can be a customized number, and the data associated with the same MAC PDU will get the same number. For example, the data associated with the first MAC PDU will get the same number, and the data associated with the second MAC PDU will get the same number. The associated data will receive a different number than the first MAC PDU. In addition, the above numbering information may also be a PDCP sequence number that the MAC layer in the first communication device directly indicates to the PDCP layer, or an RLC sequence number that the MAC layer in the first communication device indicates to the RLC layer, and then the RLC layer indicates to the PDCP The PDCP sequence number indicated by the layer. By giving indications of the first indication information and the second indication information, it is beneficial for the first communication device to determine the data associated with the same MAC PDU based on the above indication information.

In conjunction with the first aspect, in some possible implementations of the first aspect, the above method further includes: based on the third indication information, determining the first data, the second data, the third data, the fourth data, the fifth data, Or at least one data in the sixth data is associated with a different MAC PDU.

When the data in the multiple MAC PDUs obtained by the first communication device is fragmented, the first data, the second data, the third data, the fourth data, the fifth data may be determined according to the third indication information from the RLC layer. The data, or at least one of the sixth data, is associated with different MAC PDUs, for example, at least one of the first data, the second data, the third data, the fourth data, the fifth data, or the sixth data. Being associated with the first MAC PDU and the second MAC PDU is beneficial to further determining the integrity check result of at least one of the above-mentioned first data to sixth data.

Optionally, the third indication information comes from a radio link control (radio link control, RLC) layer of the first communication device.

In conjunction with the first aspect, in some possible implementations of the first aspect, the above method further includes one or more of the following: determining whether the third data integrity check fails or succeeds based on the fourth indication information; based on the fifth The indication information determines that the fifth data integrity check fails or succeeds; or based on the sixth indication information, it determines that the sixth data integrity check fails or succeeds.

Optionally, the fourth indication information comes from the second PDCP entity.

Optionally, the fifth indication information comes from the second PDCP entity.

Optionally, the sixth indication information comes from the third PDCP entity.

When the data in the MAC PDU obtained by the first communication device is associated with different PDCP entities, it can obtain the integrity check results of the data associated with different PDCP entities based on the instruction information from the different PDCP entities, and then have Facilitates processing of data that is not integrity protected. For example, based on the fourth indication information from the second PDCP entity, it is determined that the third data integrity check fails.

In a second aspect, the present application provides a communication method, which can be executed by a first communication device, or can also be executed by a component (such as a chip, chip system, etc.) configured in the first communication device, or also It can be implemented by a logic module or software that can realize all or part of the functions of the first communication device, and this application does not limit this.

Exemplarily, the method includes: generating seventh indication information, the seventh indication information being used to indicate adjusting the proportion of integrity protected data; and sending the seventh indication information to the second communication device.

Based on the above technical solution, the first communication device may generate and send seventh instruction information to the second communication device to instruct the second communication device to adjust the proportion of the integrity-protected data, where the adjustment may be to increase the proportion of the integrity-protected data. The ratio can be adjusted up or down, or part of the full protection function can be turned on or off. The first communication device sends the seventh indication information, which is helpful for the second communication device to reasonably adjust the proportion of integrity protected data based on the seventh indication information.

In a third aspect, the present application provides a communication method, which can be executed by a second communication device, or can also be executed by a component (such as a chip, chip system, etc.) configured in the second communication device, or also It can be implemented by a logic module or software that can realize all or part of the functions of the second communication device, and this application does not limit this.

Exemplarily, the method includes: receiving seventh indication information, the seventh indication information being used to instruct adjusting the proportion of integrity-protected data; and adjusting the proportion of integrity-protected data based on the above-mentioned seventh indication information.

Based on the above technical solution, the second communication device may receive seventh indication information, so as to adjust the proportion of integrity-protected data based on the seventh indication information, where the adjustment may be to increase or decrease the proportion of integrity-protected data. Low, it can also turn on or off some full protection functions. The second communication device adjusts the proportion of integrity-protected data according to the seventh instruction information, which is beneficial to improving the rationality of the proportion of integrity-protected data in the second communication device.

In combination with the second aspect or the third aspect, in some possible implementations, when the third condition is met, the seventh instruction information indicates to increase the proportion of integrity protected data, where the third condition includes one of the following: One or more items: the number of integrity check failures is greater than or equal to the first threshold; or, the number of received MAC PDUs that do not contain integrity protected data is greater than or equal to the second threshold; and/or, in If the fourth condition is met, the seventh instruction information indicates to reduce the proportion of integrity protected data, where the fourth condition includes one or more of the following: the number of successful integrity checks is greater than or equal to the third threshold; The number of received MAC PDUs containing integrity protected data is greater than or equal to the fourth threshold; or the number of received MAC PDUs is greater than or equal to the fifth threshold, wherein the received MAC PDUs contain data All are integrity protected.

In the above technical solution, possible conditions for the seventh instruction information to indicate an increase in the proportion of integrity-protected data are given, and/or possible conditions for the seventh instruction information to indicate a decrease in the proportion of integrity-protected data. , furthermore, under different circumstances, the first communication device can send different instruction information to the second communication device, so that the second communication device can adjust the proportion of integrity protected data, which is beneficial to improving the second communication device's adjustment of integrity protection. The rationality of the proportion of the data.

Combined with the second aspect or the third aspect, in some possible implementations, the number of integrity check failures is determined according to any of the following: the number of PDCP PDUs that fail the integrity check; or, including the number of PDCP PDUs that fail the integrity check. The number of MAC PDUs for PDCP PDUs that failed verification.

The number of integrity check failures can be determined based on the number of PDCP PDUs that fail the integrity check. The number of PDCP PDUs that fail the integrity check is based on the granularity of the first communication device. For example, the first communication device can Maintain a counter. The number of PDCP PDUs that fail integrity check increases by 1, and the number of integrity check failures indicated by the counter increases by 1. The number of integrity check failures can also be determined based on the number of MAC PDUs containing PDCP PDUs that failed integrity check. The number of MAC PDUs is for the first communication device granularity. For example, the first communication device can maintain A counter. The number of MAC PDUs containing PDCP PDUs that failed integrity check increases by 1. Then the number of integrity check failures indicated by the counter increases by 1. Among them, for a certain MAC PDU, if the MAC PDU contains The number of PDCP PDUs that failed the integrity check is 2, and the counter is increased by 1.

Combined with the second aspect or the third aspect, in some possible implementations, the number of PDCP PDUs that fail integrity check is associated with a PDCP entity; or, the MAC PDU containing the PDCP PDU that fails integrity check The number of PDCP PDUs that failed the integrity check are associated with a PDCP entity.

The number of PDCP PDUs that failed the integrity check is associated with a PDCP entity. It means that the number of PDCP PDUs that failed the integrity check is based on one PDCP entity granularity. For example, each PDCP entity maintains a counter. If the number of PDCP PDUs associated with the PDCP entity that fail the integrity check increases by 1, then the number of integrity check failures indicated by the counter corresponding to the PDCP entity increases by 1. Similarly, the PDCP PDU that fails the integrity check and is associated with a PDCP entity in the number of MAC PDUs that contain the PDCP PDU that fails the integrity check is also based on the granularity of a PDCP entity. For example, each PDCP entity maintains a counter. For a certain MAC PDU, if the number of PDCP PDUs that fail integrity check in the MAC PDU is 2, and these two PDCP PDUs are related to different PDCP entities connection, the counter corresponding to each PDCP entity increases by 1.

Combined with the second aspect or the third aspect, in some possible implementations, the number of successful integrity checks is determined according to any of the following: the number of PDCP PDUs with successful integrity checks; or, including the number of PDCP PDUs with successful integrity checks; The number of MAC PDUs of successfully verified PDCP PDUs.

Combined with the second aspect or the third aspect, in some possible implementations, the number of PDCP PDUs with successful integrity verification is associated with a PDCP entity; or, a MAC PDU containing the PDCP PDU with successful integrity verification A number of PDCP PDUs with successful integrity checks are associated with a PDCP entity.

Combined with the second aspect or the third aspect, in some possible implementations, the seventh indication information is associated with a PDCP entity.

Wherein, the seventh indication information is associated with a PDCP entity means that the seventh indication information is for a certain PDCP entity granularity. In other words, the seventh indication information can indicate adjusting the integrity protection data in the data associated with a certain PDCP entity. proportion, thereby helping the second communication device to reasonably adjust the proportion of integrity-protected data in a certain PDCP entity.

In the fourth aspect, the present application provides a communication method, which can be executed by a second communication device, or can also be executed by a component (such as a chip, chip system, etc.) configured in the second communication device, or also It can be implemented by a logic module or software that can realize all or part of the functions of the second communication device, and this application does not limit this.

Exemplarily, the method includes: obtaining a first resource; satisfying a fifth condition, allocating resources to a first logical channel (logical channel, LCH), the first LCH being associated with partial security, where the fifth condition includes the following One or more items: the remaining resources of the first resource are greater than or equal to the size of the first data set and the size of the MAC subheader; or the variable corresponding to the first LCH is greater than or equal to the size of the first data set; wherein, the first The data set includes seventh data, or the first data set includes seventh data and a second data set, wherein the seventh data is integrity protected data, the second data set includes at least one data, and the at least one data is Data that is not integrity protected.

Based on the above technical solution, when the remaining resources of the first resource are greater than or equal to the size of the first data set and the size of the MAC subheader, and/or the variable corresponding to the first LCH is greater than or equal to the first data set, the second communication device If the size of Ensure that the MAC PDU contains at least one integrity-protected data for each PDCP entity. Compared with the MAC PDU containing at least one integrity-protected data, it will help reduce the possibility of data being tampered with, thereby helping to improve the security of the data. safety.

Combined with the fourth aspect, in some possible implementations of the fourth aspect, the second data set includes all data before the seventh data; or, the second data set includes all data between the seventh data and the eighth data. , among which, the eighth data is integrity-protected data.

All data before the seventh data refers to all data before the seventh data in the data sent by the RLC layer. One possible situation is that the second data set includes all the data before the seventh data. In other words, there may be one or more data that are not integrity protected before the seventh data, and there is no other data that is integrity protected. Yes, there may be integrity-protected or non-integrity-protected data after the seventh data. That is, during the MAC multiplexing process, for the first LCH, if the variable Bj maintained by the first LCH is greater than or equal to the first The integrity-protected data (i.e., the seventh data) and its previous data (i.e., the second data set) are multiplexed in the MAC PDU, thereby ensuring that the MAC PDU contains at least one for each PDCP entity. Integrity protected data. Another possible situation is that the second data set includes all data between the seventh data and the eighth data. In other words, during the MAC multiplexing process, for the first LCH, if Bj is greater than or equal to the first one, complete The data with integrity protection (i.e., the seventh data) and the data between the first data with integrity protection and the second data with integrity protection (i.e., the second data set) are multiplexed in the MAC PDU , thus ensuring that the MAC PDU contains at least one integrity-protected data for each PDCP entity.

Combined with the fourth aspect, in some possible implementations of the fourth aspect, the eighth data is integrity-protected data after the seventh data.

In other words, the seventh data is the first data in the first data set, that is, the integrity-protected data is the first data in the first data set, thus ensuring that after MAC multiplexing, the MAC PDU The first data for each PDCP entity is the data for integrity protection.

Combined with the fourth aspect, in some possible implementations of the fourth aspect, the second data set includes all data before the seventh data, including: the second data set includes all data between the ninth data and the seventh data. . The ninth data may be integrity-protected data before the seventh data.

That is to say, the seventh data may also include integrity-protected data (such as the ninth data). The remaining resources of the first resource need to accommodate the following data: between the seventh data, the eighth data and the seventh data. data, thus ensuring that the MAC PDU contains at least one integrity-protected data for each PDCP entity.

Combined with the fourth aspect, in some possible implementations of the fourth aspect, the above method further includes: the first data set, the eighth data, and the ninth data are associated with one PDCP entity.

Combined with the fourth aspect, in some possible implementations of the fourth aspect, the variable corresponding to the first LCH is greater than 0.

In the fifth aspect, this application provides a communication method, which can be executed by a terminal device, or can be executed by a component (such as a chip, chip system, etc.) configured in the terminal device, or can be implemented by Logic modules or software implementations of all or part of the terminal equipment functions are not limited in this application.

Exemplarily, the method includes: receiving radio link monitoring (radio link monitoring, RLM) measurement relaxation configuration information and/or beam failure detection (beam failure detection, BFD) measurement relaxation configuration information, wherein the RLM measurement relaxation configuration information can Used to indicate RLM measurement relaxation rules, BFD measurement relaxation configuration information can be used to indicate BFD measurement relaxation rules; determine RLM measurement relaxation rules and/or BFD measurement relaxation rules. Relax the RLM measurement and/or BFD measurement, or determine whether to relax or not relax the RLM measurement and/or BFD measurement according to the instruction information.

In this application, the terminal device determines the RLM/BFD measurement relaxation rules according to the configuration of the network device, and (after meeting the RLM/BFD measurement relaxation criteria) performs measurement relaxation on its own, or determines whether to perform measurement relaxation according to the instruction information of the network device, so that The network device can adjust the strategy for the terminal device to relax RLM measurement and/or BFD measurement according to the conditions of the terminal device to minimize the probability of failure of the terminal device when relaxing the measurement. For example, when the signal quality in the service area of the terminal device is not good enough or the terminal device has services with higher service quality requirements, the network device can configure the terminal device to determine whether to perform measurement relaxation according to the instructions of the network settings, rather than doing it on its own. Measurement relaxation allows the network device to control the measurement behavior of the terminal device, thereby avoiding the adverse effects of the terminal device's autonomous measurement relaxation.

In a possible design, determining the RLM measurement relaxation rules and/or BFD measurement relaxation rules may be that the terminal equipment determines (after meeting the RLM/BFD measurement relaxation criteria) that it can decide whether to perform measurement relaxation on its own, or the terminal equipment determines (after meeting the RLM/BFD measurement relaxation criteria) After BFD measurement relaxation criteria), it is necessary to determine whether measurement relaxation can be performed based on the instruction information of the network device.

In one possible design, relaxing RLM measurement and/or BFD measurement includes: increasing the measurement period of RLM measurement and/or BFD measurement, increasing the indication and/or reporting period of RLM measurement and/or BFD measurement, or reducing The number of reference signals for RLM measurement and/or BFD measurement, etc.

In a sixth aspect, the present application provides a communication device that can implement the first aspect and the communication method in any possible implementation of the first aspect, or can implement the second aspect and any possible implementation of the second aspect. Communication methods in the implementation. The device includes corresponding units for performing the above method. The units included in the device can be implemented by software and/or hardware.

In a seventh aspect, the present application provides a communication device that can implement the third aspect and the communication method in any possible implementation of the third aspect, or can implement any of the fourth aspect and any possible implementation of the fourth aspect. Communication methods in the implementation. The device includes corresponding units for performing the above method. The units included in the device can be implemented by software and/or hardware.

In an eighth aspect, the present application provides a communication device, which includes a processor. The processor is coupled to a memory and can be used to execute a computer program in the memory to implement the first aspect and the communication method in any possible implementation of the first aspect, or to implement the second aspect and any possible implementation of the second aspect. Communication methods in the implementation.

In a ninth aspect, the present application provides a communication device, which includes a processor. The processor is coupled to a memory and can be used to execute a computer program in the memory to implement the communication method in the third aspect and any possible implementation of the third aspect, or to implement any one of the fourth aspect and the fourth possible implementation. Communication methods in the implementation.

In a tenth aspect, the present application provides a communication device that can implement the communication method described in the fifth aspect. The device includes corresponding units for performing the above method. The units included in the device can be implemented by software and/or hardware.

In an eleventh aspect, the present application provides a communication device, which includes a processor. The processor is coupled to the memory and can be used to execute the computer program in the memory to implement the communication method described in the fifth aspect.

In a twelfth aspect, the present application provides a computer-readable storage medium in which a computer program or instructions are stored. When the computer program or instructions are executed, the first aspect and the first aspect are implemented. The communication method in any possible implementation manner, or the communication method in any possible implementation manner of implementing the second aspect and the second aspect, or the communication method in any possible implementation manner of implementing the third aspect and the third aspect The communication method, or implement the communication method in the fourth aspect and any possible implementation manner of the fourth aspect, or implement the communication method described in the fifth aspect.

In a thirteenth aspect, the present application provides a computer program product that includes instructions that, when executed, implement the communication method in the first aspect and any possible implementation of the first aspect, Or implement the second aspect and the communication method in any possible implementation of the second aspect, or implement the third aspect and the communication method in any possible implementation of the third aspect, or implement the fourth aspect and the fourth aspect The communication method in any possible implementation of the aspect, or the communication method described in the fifth aspect.

In a fourteenth aspect, the present application provides a chip system, which includes a processor and may also include a memory, for implementing the communication method in the first aspect and any possible implementation of the first aspect, or implementing The communication method in the second aspect and any possible implementation of the second aspect, or the communication method in any possible implementation of the third aspect and the third aspect, or the communication method in any of the fourth aspect and the fourth aspect. A communication method in a possible implementation, or the communication method described in the fifth aspect. The chip system can be composed of chips or include chips and other discrete devices.

In a fifteenth aspect, embodiments of the present application provide a communication system, which includes the communication device described in the sixth or eighth aspect, and the communication device described in the seventh or ninth aspect.

Description of the drawings

Figure 1 is a schematic structural diagram of a protocol stack provided by an embodiment of the present application;

Figure 2 is a schematic structural diagram of a data PDU provided by an embodiment of the present application;

Figure 3 is a schematic diagram of the relationship between PDU and service data unit (service data unit, SDU) of each protocol layer provided by the embodiment of this application;

Figure 4 is a schematic diagram of the relationship between PDCP PDU and PDCP SDU provided by the embodiment of the present application;

Figure 5 is a schematic diagram of partially complete protection provided by the embodiment of the present application;

Figure 6 is a schematic diagram of the system architecture suitable for the method provided by the embodiment of the present application;

Figure 7 is a schematic flow chart of the communication method provided by the embodiment of the present application;

Figures 8 to 12 are schematic diagrams of several MAC PDUs provided by embodiments of this application;

Figure 13 is a schematic flow chart of another communication method provided by an embodiment of the present application;

Figure 14 is a schematic flow chart of yet another communication method provided by an embodiment of the present application;

Figure 15 is a schematic flow chart of yet another communication method provided by an embodiment of the present application;

Figures 16 to 19 are schematic structural diagrams of possible communication devices provided by embodiments of the present application.

Detailed ways

The technical solutions in this application will be described below with reference to the accompanying drawings.

In order to facilitate understanding of the embodiments of this application, the following description is first made:

First, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same or similar items with basically the same functions and effects. . For example, the first indication information and the second indication information are only used to distinguish different indication information, and their order is not limited. Those skilled in the art can understand that words such as "first" and "second" do not limit the number and execution order, and words such as "first" and "second" do not limit the number and execution order.

Second, in the embodiment of this application, "and/or" describes the association of associated objects, indicating that there can be three relationships. For example, A and/or B can mean: A exists alone, and A and B exist simultaneously. When B exists alone, A and B can be singular or plural. The character "/" generally indicates that the related objects are in an "or" relationship, but it does not exclude the situation that the related objects are in an "and" relationship. The specific meaning can be understood based on the context. "The following one or more items" or similar expressions refer to any combination of these items, including any combination of single items or plural items. For example, one or more of a, b, or c can mean: a, b, c; a and b; a and c; b and c; or a and b and c. Among them, a, b, c can be single or multiple.

In this application, the words "exemplary" or "such as" are used to mean examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" or "such as" is not intended to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.

The technical solution provided by this application can be applied to various communication systems, such as: global system for mobile communications (GSM) system, code division multiple access (code division multiple access, CDMA) system, broadband code division multiple access (CDMA) system wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), wireless local area network (WLAN), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (TDD), sidelink communication system, universal mobile telecommunication system (UMTS), global interconnection microwave access (worldwide interoperability for microwave access, WiMAX) communication system, fifth generation (5th generation, 5G) mobile communication system or new radio access technology (new radio access technology, NR). Among them, the 5G mobile communication system may include non-standalone networking (non-standalone, NSA) and/or independent networking (standalone, SA).

The technical solution provided by this application can also be applied to future communication systems, such as the sixth generation (6th Generation, 6G) mobile communication system, etc. This application does not limit this.

In this embodiment of the present application, the first communication device and/or the second communication device may be a network device or a terminal device.

The network device can be any device with wireless transceiver functions. Network equipment includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (Node B, NB), base station controller (BSC) , base transceiver station station (BTS), home base station (e.g., home evolved Node B, or home Node B, HNB), baseband unit (BBU), access point in a wireless fidelity (Wi-Fi) system ( access point (AP), wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc. It can also be a gNB in a 5G (such as NR) system. or transmission point (TRP or TP), or one or a group (including multiple antenna panels) of antenna panels of a base station in a 5G system, or it can also be a network node that constitutes a gNB or transmission point, such as a baseband unit (BBU) ), or distributed unit (DU), etc.

In some deployments, gNB may include centralized units (CUs) and DUs. For example, CU implements some functions of gNB, and DU implements some functions of gNB. For example, CU is responsible for processing non-real-time protocols and services, implementing radio resource control (RRC), and packet data convergence layer protocol (packet data convergence). protocol, PDCP) layer functions; DU can include the functions of the radio link control (RLC) layer, the functions of the media access control (media access control, MAC) layer, and the physical (physical, PHY) layer some functions.

For example, the DU may include functions of higher layers in the PHY layer. Among them, the functions of the higher layers in the PHY layer may include cyclic redundancy check (CRC) functions, channel coding, rate matching, scrambling, modulation, and layer mapping; or, the functions of the upper layers of the PHY layer may include cyclic Redundancy check, channel coding, rate matching, scrambling, modulation, layer mapping and precoding. The functions of the middle and lower layers of the PHY layer can be implemented through another network entity independent of the DU. Among them, the functions of the middle and lower layers of the PHY layer can include precoding, resource mapping, physical antenna mapping and radio frequency functions; alternatively, the functions of the middle and lower layers of the PHY layer can Includes resource mapping, physical antenna mapping and radio frequency capabilities. The embodiments of the present application do not limit the functional division of the upper layer and the lower layer in the PHY layer. When the functions of the lower layers in the PHY layer can be implemented by another network entity independent of DU, DU sends data or information to other communication devices (such as terminal equipment, core network equipment), which can be understood as: DU executes the RLC layer and MAC layer functions, and, part of the functions of the PHY layer. For example, after DU completes the functions of the RLC layer and MAC layer, as well as cyclic redundancy check, channel coding, rate matching, scrambling, modulation, and layer mapping, a network independent of the DU performs the functions of the middle and lower layers of the PHY layer. The entity performs the remaining functions of mapping and sending on physical resources.

The network equipment provides services for the cell, and the terminal equipment communicates with the cell through the transmission resources (for example, frequency domain resources, or spectrum resources) allocated by the network equipment. The cell may belong to a macro base station (for example, macro eNB or macro gNB, etc.) , or it can belong to the base station corresponding to a small cell. The small cell here can include: metro cell, micro cell, pico cell, femto cell, etc. , these small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-rate data transmission services.

In the embodiment of this application, the terminal equipment may also be called user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, Terminal, wireless communication equipment, user agent or user device.

The terminal device may be a device that provides voice/data connectivity to the user, such as a handheld device, a vehicle-mounted device, etc. with wireless connectivity capabilities. At present, some examples of terminal devices can be: mobile phones, tablets, computers with wireless transceiver functions (such as laptops, handheld computers, etc.), mobile internet devices (MID), virtual Reality (VR) equipment, augmented reality (AR) equipment, wireless terminals in industrial control (industrial control), wireless terminals in self-driving (self driving), drones, remote medicine (remote) Wireless terminals and smart grid in medical Wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocols protocol (SIP) telephone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, Vehicle-mounted equipment, wearable devices, terminal equipment in 5G networks or terminal equipment in the future evolved public land mobile communication network (public land mobile network, PLMN), etc.

Among them, wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones. Use, such as various types of smart bracelets, smart jewelry, etc. for physical sign monitoring.

In addition, the terminal device can also be a terminal device in an Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-computer interconnection and object interconnection. IoT technology can achieve massive connections, deep coverage, and terminal power saving through narrowband (NB) technology, for example.

In addition, terminal equipment can also include sensors such as smart printers, train detectors, and gas stations. Its main functions include collecting data (some terminal equipment), receiving control information and downlink data from network equipment, and sending electromagnetic waves to transmit uplink data to network equipment. .

It should be understood that this application does not limit the specific forms of network equipment and terminal equipment.

In order to better understand the communication method provided by the embodiments of this application, first a brief explanation of the terms involved in this application will be given.

1. NR protocol architecture: It can be divided into user plane protocol stack and control plane protocol stack according to the purpose. The above two protocol stacks will be described in detail below in conjunction with Figure 1. a) in Figure 1 shows the user plane protocol stack, and b) in Figure 1 shows the control plane protocol stack. As shown in a) in Figure 1, the user plane protocol stack mainly includes five layers: PHY layer, MAC layer, RLC layer, PDCP layer and service data adaptation protocol (service data adaptation protocol, SDAP) layer. Among them, the PHY layer can be responsible for processing one or more of encoding and decoding, modulation and demodulation, multi-antenna mapping and other physical layer functions. The MAC layer is responsible for processing one or more of hybrid automatic repeat request (HARQ) retransmission and uplink and downlink scheduling. The RLC layer can be responsible for segmentation, reassembly and retransmission processing. The PDCP layer can be responsible for performing one or more of header compression, security (encryption function, integrity protection function), retransmission, and sequential transmission of high-level data.

As shown in b) in Figure 1, the control plane protocol stack mainly includes the non-access stratum (NAS), RRC, PDCP, RLC, MAC, and PHY layers. Among them, the PDCP layer provides encryption and integrity protection functions, and the control plane in the RLC layer and MAC layer performs the same functions as the user plane. The RRC layer is mainly responsible for functions such as broadcast, paging, RRC connection management, wireless bearer control, mobility management, terminal equipment measurement reporting and control. The NAS layer handles the transmission of information between the terminal device and the access and mobility management function (AMF) entity. The transmitted content can be user information or control information. For example, the transmitted content includes session management. User management, security management, etc. It should be understood that for the user plane protocol stack, the NR protocol stack has an additional SDAP layer compared to the LTE protocol stack. For the control plane protocol stack, the NR protocol stack is similar to the LTE protocol stack.

2. Integrity protection: Data integrity is one of the three basic points of information security. It refers to ensuring that the data is not tampered with or can be quickly discovered after tampering during the transmission or storage process. The integrity protection function includes integrity protection and integrity verification, which are used to prevent data from being tampered with. The integrity protection function is performed at the PDCP layer. Among them, the PDCP layer at the sending end performs integrity protection and generates an integrity message authentication code (message authentication code for integrity, MAC-I) to be placed at the end of the PDCP PDU. The PDCP layer at the receiving end performs integrity verification based on MAC-I. test. The data unit of integrity protection is the PDU header and the data part of the PDU before encryption. Integrity protection can be applied to PDCP data PDUs of the signaling radio bearer (SRB) carrying control plane data. Integrity protection can also be applied to PDCP data PDUs of data radio bearer (DRB) (DRB carrying user plane data) configured with integrity protection that carry user plane data. Among them, the data PDU is used to transmit user plane and control plane data as well as MAC-I generated by integrity protection.

Figure 2 shows two examples of data PDUs. a) in Figure 2 shows the format of the PDCP data PDU corresponding to the SRB, and b) in Figure 2 shows the format of the PDCP data PDU corresponding to the DRB. The formats of the above two PDCP data PDUs will be described in detail below with reference to Figure 2.

As shown in a) in Figure 2, the PDCP data PDU corresponding to the SRB includes the R field, PDCP sequence number (SN), data (Data) and MAC-I. Among them, R represents reserved bits, which may include 4 reserved bits, for example. In addition, the length of PDCP SN is 12 bits.

As shown in b) in Figure 2, the PDCP data PDU corresponding to the DRB includes the D/C field, R field, PDCP SN, Data and MAC-I. The D/C field is used to identify the type of PDU. For example, a D/C field of 0 represents a control PDU, and a D/C field of 1 represents a data PDU. R represents reserved bits. In addition, the length of PDCP SN can be 12 bits. In other embodiments, the length of the PDCP SN may also be 18 bits, which is not limited in the embodiments of this application.

It should be noted that “MAC-I (continue)” in Figure 2 indicates that MAC-I can occupy multiple lines. "PDCP SN (Continue)" indicates that the PDCP SN can occupy multiple lines.

3. PDU and SDU: The SDU of the Nth layer has a one-to-one correspondence with the PDU of the upper layer. In other words, the PDU of this layer is the SDU of the lower layer, and the SDU of this layer is the PDU of the upper layer.

The relationship between PDU and SDU will be described in detail below with reference to Figures 3 and 4.

Figure 3 is a schematic diagram of the relationship between PDU and SDU of each protocol layer provided by the embodiment of the present application. As shown in Figure 3, for access network equipment, after the RRC layer generates the signaling to be transmitted (for example, RRC message or RRC PDU), it can submit it to the corresponding PDCP entity. For the convenience of description, next we Call/replace signaling with data; for data received from the RRC layer (for example, PDCP SDU), the PDCP entity may obtain the PDCP PDU after certain processing or no processing, and then submit the PDCP PDU to the corresponding PDCP entity. RLC entity; for data received from the PDCP layer (for example, RLC SDU), the RLC entity may obtain the RLC PDU through certain processing or no processing, and then submit the RLC PDU to the corresponding MAC entity; for data received from the RLC layer Data (for example, MAC SDU), the MAC entity may obtain the MAC PDU through certain processing or not, and then submit the MAC PDU to the PHY layer; the PHY layer will perform air interface transmission.

Correspondingly, for the terminal device, after the PHY layer receives the data (for example, transport block (TB)), it will submit the TB to the MAC layer; for the data received from the PHY (for example, TB or MAC PDU ), The MAC entity may obtain the MAC SDU through certain processing or not, and then submit the MAC SDU to the corresponding RLC layer; for the data received from the MAC layer (for example, RLC PDU), the RLC entity may or may not process the data received from the MAC layer. Obtain the RLC SDU, and then submit the RLC SDU to the corresponding PDCP entity; for the data received from the RLC layer (for example, PDCP PDU), the PDCP entity may obtain the PDCP SDU after certain processing or no processing, and then submit the PDCP SDU to RRC layer; for data received from the PDCP layer (for example, RRC message or RRC PDU), which can also be called signaling, the RRC layer will perform RRC decoding or ASN.1 decoding to determine the identity of the received data. meaning.

For the sending and receiving of data (or signaling), the data may be encapsulated/processed accordingly in each layer, or may be transparently transmitted. For example, for the sender, the data received by a certain layer from the upper layer of this layer is called SDU, and the data submitted by this layer to the lower layer is called PDU. For this layer, the data received from the upper layer and the data submitted to The data in the lower layer may be the same (for example, transparent transmission), or they may be different (for example, the data received from the upper layer is encapsulated/processed by this layer and then the data is submitted to the lower layer). For example, the data received by the PDCP entity from the upper layer is called PDCP SDU, and the data sent by the PDCP entity to the lower layer is called PDCP PDU; the data received by the RLC entity from the upper layer is called RLC SDU, and the data sent by the RLC entity to the lower layer is called RLC. PDU; the data received by the MAC entity from the upper layer is called MAC SDU, and the data sent by the MAC entity to the lower layer is called MAC PDU. For example, for reception, the data received by a certain layer from the lower layer of the layer is called PDU, and the data submitted by this layer to the upper layer is called SDU. For this layer, the data received from the lower layer and the data submitted to the upper layer are The data may be the same (for example, transparent transmission), or they may be different (for example, the data received from the lower layer is processed by this layer and then the data is submitted to the upper layer). For example, the data received by the PDCP entity from the lower layer is called PDCP PDU, and the data sent by the PDCP entity to the upper layer is called PDCP SDU; the data received by the RLC entity from the lower layer is called RLC PDU, and the data sent by the RLC entity to the upper layer is called RLC. SDU; the data received by the MAC entity from the lower layer is called MAC PDU, and the data sent by the MAC entity to the upper layer is called MAC SDU.

Among them, the upper layer and lower layer involved in the embodiments of this application are a relative concept. For example, taking the RLC layer as an example, for the RRC layer, the RLC layer can be the lower layer of the RRC layer, but for the MAC layer, the RLC layer Can be the upper layer of the MAC layer. For another example, the lower layer of the RRC layer may include any one or more of the following: PHY layer, MAC layer, RLC layer, and PDCP layer.

Figure 4 is a schematic diagram of the relationship between PDCP PDU and PDCP SDU provided by the embodiment of the present application. As shown in Figure 4, for the access network equipment, for the data (for example, PDCP SDU) received from the RRC layer, the PDCP entity may obtain the PDCP PDU after certain processing or no processing. For example, the PDCP entity may obtain the PDCP PDU. Add the PDCP header to the SDU to get the PDCP PDU.

4. MAC multiplexing: refers to the MAC layer multiplexing the data of one or more logical channels (for example, MAC SDU, or RLC SDU, or RLC PDU) and/or MAC CE into one resource or MAC PDU. That is to say, the uplink resources allocated by the base station to a certain terminal device are determined. The terminal device decides which logical channel data to place and how much data to place in each logical channel based on the configuration of the base station and the rules specified by the protocol.

It can be understood that in the process of MAC multiplexing, there is only one resource or MAC PDU, but there are multiple logical channels to be multiplexed. Each logical channel can be configured according to the rules of Logical Channel Prioritization (LCP). Allocating resources. Among them, logical channels have corresponding priorities.

One possible way is: the data of the highest priority logical channel is included in the MAC PDU first, followed by the data of the second highest priority logical channel, and so on until the allocated resources or MAC PDU are full or there is no update. There is a lot of data to send. However, this allocation method may cause the high-priority logical channel to always occupy the terminal allocated by the base station. The wireless resources of the end device are blocked, resulting in low-priority logical channels being unable to obtain wireless resources. To avoid this situation, LTE introduces the concept of prioritized bit rate (PBR).

The specific process of MAC multiplexing is described in detail below.

The MAC layer uses an algorithm similar to the token bucket to implement MAC reuse. The basic idea of this algorithm is to determine whether to send the data of a certain logical channel based on whether there are tokens in the token bucket and the number of tokens, and to control the amount of data of the logical channel assembled in the MAC PDU. The token bucket algorithm will be described in detail below.

Bucket size duration (BSD) determines the "depth" of the token bucket. It and PBR jointly determine the maximum capacity of the token bucket as PBR × BSD. The maximum capacity of the token bucket limits the amount of data that can be pending for each logical channel, that is, the total amount of data cached in the buffer.

The terminal device maintains a variable Bj for each logical channel j. The variable Bj indicates the number of tokens currently available in the token bucket. Logical channel j is established, and the MAC entity initializes the variable Bj corresponding to the logical channel j to zero.

To perform a new transmission, the MAC layer should allocate resources to logical channels as follows:

For the LCH selected according to LCP restrictions (and the Bj of the LCH is greater than 0), resources are allocated in descending order of priority. If the PBR of a logical channel is set to "infinity", the MAC entity will allocate resources for all data available for transmission on that logical channel before the PBR of the lower priority logical channel is met, and Bj minus the above logical channel jThe total size of the provided MAC SDU. If resources remain, data is provided in strictly decreasing priority order (regardless of the value of Bj) for logical channels selected according to LCP restrictions. It should be noted that logical channels with the same priority should be processed equally.

In the above process, LCP restrictions may include any one or more of the following: subcarrier spacing, physical downlink shared channel (PUSCH) duration, resources (grant), cells, etc.

For the specific content of LCP or MAC reuse, please refer to the relevant content on MAC in the technical specification (TS) 38.321 of the 3rd generation partnership project (3GPP). For details, please refer to the "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification".

5. Partial integrity protection: For a certain RB, part of the multiple data (for example, PDCP data PDU) associated with the RB is integrity protected. As can be seen from the above, the MAC layer can multiplex multiple RLC PDUs, or multiple RLC SDUs, or multiple MAC SDUs. Therefore, the MAC PDU may have the following two situations:

The MAC PDU contains at least one integrity-protected MAC SDU for each RB; or, the MAC PDU contains at least one integrity-protected MAC SDU. Figure 5 gives an example of the above two situations. The above two situations will be described in detail below with reference to Figure 5.

The integrity protected MAC SDU can be understood as: the MAC SDU corresponding to the integrity protected PDCP PDU/SDU, or the RLC PDU corresponding to the integrity protected PDCP PDU/SDU, or the RLC SDU corresponding to the integrity protected PDCP PDU/SDU. .

Contain at least one integrity-protected MAC SDU for each RB in the MAC PDU:

As shown in a) in Figure 5, the three PDCP SDUs associated with RB 1 are PDCP SDU 1 to 3 respectively. PDCP SDU 1 is integrity protected. The three PDCP SDUs associated with RB 2 are PDCP SDU a to c. , PDCP SDU a is integrity protected, and the PDCP layer delivers it to the RLC layer. The RLC layer does not segment it and further delivers it to the MAC layer. The MAC layer can multiplex it in a MAC PDU, then the MAC The PDU contains an integrity-protected MAC SDU for each RB, namely MAC SDU 1 and MAC SDU a.

For the case where the MAC PDU contains at least one integrity-protected MAC SDU:

As shown in b) in Figure 5, the three PDCP SDUs associated with RB 1 are PDCP SDU 1 to 3. PDCP SDU 1 is integrity protected. The three PDCP SDUs associated with RB 2 are PDCP SDU a to c. , none of them are integrity protected. The PDCP layer delivers it to the RLC layer. The RLC layer does not segment it and further delivers it to the MAC layer. The MAC layer can multiplex it in a MAC PDU. Then in the MAC PDU Contains an integrity-protected MAC SDU, MAC SDU 1.

Among them, the PDCP SDU described in Figure 5 can be replaced by PDCP PDU. It can be understood that PDCP SDU corresponds to PDCP PDU. In addition, the MAC SDU depicted in Figure 5 corresponds to the PDCP PDU. In other words, the MAC PDU contains an integrity-protected MAC SDU, which can also be replaced by the MAC PDU containing an integrity-protected PDCP PDU.

In order to facilitate understanding of the communication method provided by the embodiment of the present application, the system architecture of the communication method provided by the embodiment of the present application will be described below. It can be understood that the system architecture described in the embodiments of this application is to more clearly illustrate the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided by the embodiments of this application.

Figure 6 is a schematic diagram of the system architecture suitable for the method provided by the embodiment of the present application. As shown in Figure 6, the communication system 600 includes communication devices 610 to 650, wherein the communication device 610 and the communication device 620 may be network devices, such as micro base stations, or TRP or other devices. Type of network equipment, this is not limited in the embodiments of this application. The communication devices 630 to 650 may be terminal devices, for example. Among them, the terminal equipment can be mobile or fixed. It can be understood that each network device can provide communication coverage for a specific geographical area and can perform wireless link communication with terminal devices located within the coverage area (cell). For example, the network device 610 can communicate with the terminal device 630, and the network device 620 can communicate with the terminal device 640 and the terminal device 650. In addition, wireless link communication can also be performed between terminal devices. For example, the terminal device 630 can communicate with the terminal device 640 or with the terminal device 650, and the terminal device 640 can communicate with the terminal device 650.

Optionally, the communication system shown in the communication system 600 may include more or less communication devices, and the connection relationship between any two communication devices may also be other connection relationships. This is not the case in the embodiment of the present application. Make limitations.

In the system architecture shown in Figure 6, when any two communication devices communicate, the data sent by the communication devices can be integrity protected by the PDCP layer to prevent data from being tampered with. As can be seen from the above, if a certain PDCP entity is configured with integrity protection, the PDCP PDU (for example, PDCP data PDU) associated with the PDCP entity is integrity protected, and the receiving end can determine whether the PDCP PDU passes the integrity check. Determine whether to discard this PDCP PDU. However, when a certain PDCP entity is configured with partial integrity protection, how to handle PDCP PDU (for example, PDCP data PDU) without integrity protection is a technical problem that needs to be solved urgently.

In order to solve the above problem, this application provides a communication method. After the first communication device obtains the data without integrity protection, if the integrity protection data associated with it fails to be verified, the first communication device discards the data. For the above-mentioned data without integrity protection, the associated data with integrity protection can be associated with the same MAC PDU and the same PDCP entity as the data without integrity protection, or , associated with the same MAC PDU and associated with different PDCP entities, or associated with different MAC PDU and associated with the same PDCP entity, or associated with different MAC PDU and different PDCP entities are associated. Through the integrity check result of the integrity-protected data, it is determined whether to discard the data that is not integrity-protected, thereby providing the first communication device with a method for processing the data that is not integrity-protected. In addition, it is helpful to improve the accuracy of data reception or the accuracy of data submitted to the upper layer, and is also beneficial to improving communication quality/efficiency. For example, data without integrity protection is often discarded. In other words, the conditions for submitting data without integrity protection to the upper layer are stricter, which is beneficial to improving the accuracy of data reception or the accuracy of data submitted to the upper layer. .

It should be noted that in this embodiment of the present application, the first communication device may be, for example, a data receiving end, and the second communication device may be, for example, a data sending end. The type of the first communication device may be a terminal device or a network device, and the type of the second communication device may be a network device or a terminal device. In other words, the embodiments provided in this application may be applicable to the interaction between a network device and a terminal device, or may be It is suitable for interaction between terminal devices and is not limited in the embodiments of this application.

In this embodiment of the present application, any two or more items among the first PDCP entity, the first RB, the first RLC entity, the first LCH, and the first logical channel identifier (LCID) are related. The embodiments of this application do not limit this.

In this embodiment of the present application, the first PDCP entity may be replaced by any one or more of the first RB, the first RLC entity, the first LCH, and the first LCID.

In this embodiment of the present application, any two or more of the second PDCP entity, the second RB, the second RLC entity, the second LCH, and the second LCID are associated. In this embodiment of the present application, Not limited.

In this embodiment of the present application, the second PDCP entity may be replaced by any one or more of the second RB, the second RLC entity, the second LCH, and the second LCID.

In the embodiment of the present application, any two or more of the third PDCP entity, the third RB, the third RLC entity, the third LCH, and the third LCID are associated. In this embodiment of the present application, Not limited.

In this embodiment of the present application, the third PDCP entity may be replaced by any one or more of the third RB, the third RLC entity, the third LCH, and the third LCID.

In the embodiment of this application, the PDCP entity can also be described/replaced as an RB, or LCH, or LCID, or RLC entity.

The communication method provided by the embodiment of the present application will be described in detail below with reference to the accompanying drawings. It should be understood that the embodiment shown in FIG. 7 describes the method from the perspective of interaction between the first communication device and the second communication device.

It should be understood that although the embodiments shown below are described by taking the interaction between the first communication device and the second communication device as an example, this should not constitute any limitation on the execution subject of the method. As long as the program recording the code of the method provided by the embodiment of the present application can be run, the method provided by the embodiment of the present application can be executed. For example, the first communication device can also be replaced by components (such as chips, chip systems, etc.) configured in the first communication device, or other functional modules capable of calling and executing programs, and the second communication device can also be replaced by components configured in the first communication device. Components in network equipment (such as chips, chip systems, etc.), or other functional modules that can call and execute programs. The embodiments of the present application do not limit this.

Figure 7 is a schematic flow chart of the communication method 700 provided by the embodiment of the present application. The communication method 700 shown in Figure 7 may include S710 and S720. Each step in method 700 is described in detail below.

S710. The first communication device obtains the first data.

The first data may be data that is not integrity protected.

Optionally, the first data is associated with the first MAC PDU, and/or is associated with the first PDCP entity.

Wherein, the first data is associated with the first MAC PDU, which may include/understand that all or part of the first data comes from the first MAC PDU; and/or all or part of the first data belongs to the first MAC PDU. One MAC PDU.

For example, the first data is data that has not been segmented. In other words, when the second communication device sends the first data, No segmentation is performed in the process, that is, all the data of the first data comes from the first MAC PDU.

For another example, the first data is segmented data. In other words, the second communication device performs segmentation in the process of sending the first data, that is, the first data is sent through different MAC PDUs, such as through The first MAC PDU and the second MAC PDU are sent, in other words, part of the first data comes from the first MAC PDU, and the other part of the first data comes from the second MAC PDU.

Wherein, the first data is associated with the first PDCP entity, which may include/be understood to mean that the first data is processed by the first PDCP entity, and/or the first data belongs to the first PDCP entity.

Optionally, the first PDCP entity is associated with partial coverage.

For example, the first data may include/understand as: the first PDCP PDU or the first PDCP data PDU.

Obtaining the first data by the first communication device may include/understood as:

(1) The first communication device receives the first data from the second communication device. Correspondingly, the second communication device sends the first data to the first communication device; or,

(2) The high layer of the first communication device (for example, the PDCP layer of the first communication device) obtains the first data from the bottom layer of the first communication device. For example, taking the first PDCP entity of the first communication device, the first PDCP entity obtains the first data from the RLC layer of the first communication device; or, the first PDCP entity obtains the first data from the MAC layer of the first communication device. .

S720. When the first condition is met, the first communication device discards the first data.

Among them, the first condition includes one or more of the following:

The second data integrity check failed;

The third data integrity check failed;

The fourth data integrity check failed;

The fifth data integrity check failed; or,

The sixth data integrity check failed.

It should be understood that the second data to the sixth data are integrity protected data.

Optionally, the second data is associated with the first MAC PDU, and/or is associated with the first PDCP entity.

Optionally, the third data is associated with the first MAC PDU, and/or is associated with the second PDCP entity.

Optionally, the fourth data is associated with the second MAC PDU, and/or is associated with the first PDCP entity.

Optionally, the fifth data is associated with the second MAC PDU, and/or is associated with the second PDCP entity.

Optionally, the sixth data is associated with the second MAC PDU, and/or is associated with the third PDCP entity.

Wherein, the second data is associated with the first MAC PDU, the third data is associated with the first MAC PDU, the fourth data is associated with the second MAC PDU, the fifth data is associated with the second MAC PDU, or, the sixth data The understanding of at least one item in the association between the data and the second MAC PDU may refer to the understanding of the association between the first data and the first MAC PDU. The second data is associated with the first PDCP entity, the third data is associated with the second PDCP entity, the fourth data is associated with the first PDCP entity, the fifth data is associated with the second PDCP entity, and the sixth data is associated with the third The understanding of at least one item in the PDCP entity association may refer to the understanding of the association between the first data and the first PDCP entity. For the sake of brevity, the details will not be described one by one here.

Optionally, at least one of the first data, second data, third data, fourth data, fifth data, or sixth data is associated with different MAC PDUs. For example, at least one of the first data, the second data, the third data, the fourth data, the fifth data, or the sixth data is consistent with the first MAC PDU and the second MAC PDU. association. "At least one of the first data, the second data, the third data, the fourth data, the fifth data, or the sixth data is associated with different MAC PDUs" may include/understood as: the first data, the second data, or the sixth data. At least one of the data, the third data, the fourth data, the fifth data, or the sixth data is reassembled from segmented data in different MAC PDUs (eg, MAC SDU or RLC PDU). The segmented data is data that is segmented from the same data. For example, for the first data, the second communication device performs segmentation during the process of sending the first data, that is, the first data passes through a different MAC. PDU transmission, taking the first data into two pieces of data as an example, that is, the first data is divided into segment data 1 and segment data 2. Segment data 1 is sent by the first MAC PDU, and segment data 2 is sent by the second MAC PDU. When the MAC PDU is sent, after receiving segment data 1 and segment data 2, the first communication device reassembles them through the RLC layer to obtain all the data of the first data.

It should also be understood that when it is determined whether to discard the first data based on the integrity check result of the second data, it is considered that the first communication device has acquired the second data. Likewise, the third to sixth data are similar to the second data and will not be described here.

It should also be understood that the following description is from the perspective that the first communication device discards the first data when the first condition is met, wherein the steps performed by the first communication device (for example, discarding the first data) may be performed by the PDCP entity or other layers. There are no restrictions on application. For example, if the first condition is met, the first PDCP entity discards the first data.

Several cases of discarding the first data will be exemplarily shown below.

It should be noted that the shaded portions in Figures 8 to 12 represent data with integrity protection, and the blank portions represent data without integrity protection. Taking any one of one or more pieces of data that is not integrity protected (such as the first data) as an example, several possible situations of discarding the first data are described in detail below.

First, several situations of discarding the first data for a MAC PDU are shown.

The first possible situation is to discard the first data if the integrity check of the second data fails. It can be understood that if it is associated with the first MAC PDU (that is, the MAC PDU associated with the first data is the same), and is associated with the first PDCP entity (that is, the PDCP entity associated with the first data is the same) If the integrity check of the data with integrity protection fails, it can be considered that the first data may have been tampered with and the first data will be discarded, which will help improve the accuracy of data reception or the accuracy of data submitted to the upper layer. As shown in Figure 8, the data that is not integrity protected in the MAC PDU includes data 2 and/or data b. The second data can be data 1 or data a. Both the second data and the first data are the same as the first MAC PDU. associated, and both are associated with the first PDCP entity. In the event that the second data integrity check fails, the first communication device discards the first data, that is, discards data 2 and/or data b.

The second possible situation is to discard the first data when the integrity check of the third data fails. It can be understood that if it is associated with the first MAC PDU (that is, the MAC PDU associated with the first data is the same), and is associated with the second PDCP entity (that is, the PDCP entity associated with the first data is different) If the integrity check of the data with integrity protection fails, it can be considered that the first data may have been tampered with and the first data will be discarded, which will help improve the accuracy of data reception or the accuracy of data submitted to the upper layer. As shown in Figure 9, the data that is not integrity protected in the MAC PDU includes data 1, data 2 and data b. The third data includes data a. The first data and the third data are both associated with the first MAC PDU. The first data is associated with the first PDCP entity, and the third data is associated with the second PDCP entity. In the event that the third data integrity check fails, the first communication device discards the first data, that is, discards at least one of data 1, data 2, or data b.

The third possible situation is to discard the first data when the second data integrity check fails and the third data integrity check fails. It can be understood that if associated with the first MAC PDU (ie, associated with the first data (the same MAC PDU), if the integrity check of the data with integrity protection fails, it can be considered that the first data may have been tampered with, and the first data will be discarded, which will help improve the accuracy of data reception or data submitted to the upper layer. accuracy. As shown in Figure 10, the data without integrity protection in the MAC PDU includes data 2 and data b, the second data includes data 1, and the third data includes data a. The first data to the third data are all the same as the first MAC PDU associated. When both the second data and the third data fail the integrity check, the first communication device discards the first data, that is, discards data 2 and/or data b.

It can be seen that the second data integrity check fails and/or the third data integrity check fails, and the first data is discarded. It can be understood that the integrity-protected data associated with the same MAC PDU as the first data In the event that one or more data integrity checks fail, the first data is discarded. It should be noted that in this embodiment of the present application, it can be determined whether to discard the first data based on one or more data integrity check results in the integrity-protected data associated with the same MAC PDU as the first data, or That is, the corresponding PDCP entity on the MAC PDU may not be considered, and the PDCP entity may also be considered, which is not limited in the embodiments of this application.

Next, several situations of discarding the first data for multiple MAC PDUs are shown.

It should be understood that, as mentioned above, at least one of the first data to the sixth data may be fragmented, that is, a certain data is sent through different MAC PDUs. The fragmentation situation will be described in detail below. How to discard the first data.

The first possible situation is that when the fourth data integrity check fails, the first data is discarded. There are two possible designs for the fourth data integrity check failure:

One possible design is that the fourth data may be segmented data. For example, part of the fourth data comes from the first MAC PDU, and another part of the fourth data comes from the second MAC PDU, passing through the first communication device. After the RLC layer is reorganized, the PDCP layer further performs an integrity check on the fourth data. Therefore, the failure of the fourth data integrity check may be due to the possibility that part of the fourth data in the first MAC PDU has been tampered with. , it is also possible that another part of the fourth data in the second MAC PDU may be tampered with, so the data that is not integrity protected in the first MAC PDU may also be tampered with. Therefore, the first communication device discards the first data. For example, as shown in Figure 11, the data that is not integrity protected in the first MAC PDU includes data 2 and data b (data 2 and/or data b may be unsegmented data; or, data 2 and/or Data b may also be segmented data), the fourth data may be segmented data, a part of the fourth data may be data 3, and the other part of the data may be data 1. The first communication device reassembles data 1 and data 3 to form fourth data. If the integrity check of the fourth data fails, either data 1 or data 3 may be tampered with. Therefore, in the first MAC PDU Data without integrity protection, that is, the first data, may also be tampered with, so data 2 and/or data b, that is, the first data, are discarded.

Another possible design is that the first data may be segmented data, and the fourth data may be unsegmented data. For example, part of the first data comes from the first MAC PDU, and another part of the first data The data comes from the second MAC PDU. When the fourth data integrity check fails, part of the first data in the second MAC PDU may be tampered with. Therefore, the first communication device discards the first data.

It should be understood that the situation of discarding the first data shown above is only an example and should not constitute any limitation on the embodiment of the present application. For example, if the fifth data integrity check fails, the first data is discarded; or if the sixth data integrity check fails, the first data is discarded. In addition, when any two or more data from the second to sixth data fail the integrity check, the first data can also be discarded. For example, if the integrity check of the second data and the fourth data fails, Discard the first data. For the sake of brevity, they will not be described in detail here.

It should also be understood that the failure of the fifth data integrity check and/or the failure of the sixth data integrity check is similar to that of the fourth data, and will not be described in detail here for the sake of brevity.

It should also be understood that the description of Figures 8 to 11 only exemplarily describes a situation of discarding data that is not integrity protected. Other data that is not integrity protected can be discarded through similar methods. This is not the case here. Elaborate again.

Optionally, in this embodiment of the present application, the discarded data may be discarded in the form of groups. As an example, a certain MAC PDU contains data associated with a PDCP entity. If the integrity check of the integrity-protected data in the MAC PDU fails, all data (i.e. a set of data) in the MAC PDU that is not integrity-protected will be discarded. For example, MAC PDU 1 contains data 1, data 2, and data 3. Data 1 is integrity protected data, data 2 and data 3 are data that are not integrity protected, and data 1, data 2, and data 3 is associated with the same PDCP entity, if the integrity check of data 1 fails, both data 2 and data 3 need to be discarded.

Another example is the case where a certain MAC PDU contains data associated with multiple PDCP entities. If the integrity check of the integrity-protected data in the MAC PDU fails, all data (i.e. a set of data) in the MAC PDU that is not integrity-protected will be discarded. For example, MAC PDU 1 contains data 1, data 2, data 3 and data 4. Data 1 and data 3 are integrity protected data, data 2 and data 4 are data that are not integrity protected, and data 1 and data 3 are integrity protected data. Data 2 is associated with PDCP entity 1, and data 3 and 4 are associated with PDCP entity 2. If the integrity check of data 1 fails, data 2 and data 4 that are not integrity protected need to be discarded.

As another example, for multiple MAC PDUs, taking MAC PDU 1 and MAC PDU 2 as an example, certain data in MAC PDU1 and certain data in MAC PDU 2 are segmented from the same data, and If the data is integrity protected, the above data will be reorganized and then integrity checked. If the integrity check fails, all data in MAC PDU 1 and MAC PDU 2 that are not integrity protected will be discarded. For example, MAC PDU 1 contains data 1, data 2, and data 3, MAC PDU 2 contains data 4 and data 5, data 1 and data 4 are integrity protected data, and data 1 and data 4 are protected by a certain After the data (recorded as data 6) is segmented, data 2, data 3 and data 5 are data that have not been integrity protected. Then data 1 and data 4 will be reorganized and then integrity checked. If the integrity check If it fails, data 2, data 3 and data 5 that are not integrity protected need to be discarded.

It should also be understood that the first communication device may determine that at least one of the first data, the second data, the third data, the fourth data, the fifth data, or the sixth data is different from the MAC PDU based on the third indication information. Associated.

Optionally, the third indication information may come from the RLC layer or MAC layer of the first communication device.

For example, at least one of the first data, the second data, or the fourth data is associated with different MAC PDUs (e.g., the first MAC PDU and the second MAC PDU), and the third indication information may come from the first RLC entity .

For example, the third data and/or the fifth data are associated with different MAC PDUs (eg, the first MAC PDU and the second MAC PDU), and the third indication information may come from the second RLC entity.

For example, the sixth data is associated with different MAC PDUs (eg, the first MAC PDU and the second MAC PDU), and the third indication information may come from the third RLC entity.

Optionally, the above method further includes: discarding one or more items of the second data, the third data, the fourth data, the fifth data, or the sixth data.

In other words, it is also necessary to consider whether to discard the second to sixth data that have been integrity protected. Several possible situations are exemplarily shown below.

A first possible situation is that the first communication device discards the second data in addition to the first data. As shown in Figure 8, the data that is not integrity protected in this MAC PDU includes data 2 and data b. The second data can be data 1 or data a. Both the second data and the first data are associated with the first MAC PDU. , and are all associated with the first PDCP entity. If the integrity check of data 1 fails, data 2, data 1 and data b are discarded, that is, the first data and the second data are discarded. In addition, regardless of whether the integrity check of data a is successful, data a will be further discarded. In other words, when one data integrity check fails in a certain MAC PDU, all data on the MAC PDU will be discarded (for example, MAC SDU or RLC SDU or RLC PDU), or the data on that MAC PDU associated with the PDCP entity associated with partial integrity will be discarded (e.g., MAC SDU or RLC SDU or RLC PDU). Another method is to discard data 2, data b and data 1 if the integrity check of data 1 fails and the integrity check of data a succeeds. In other words, when one or more data integrity checks fail in a certain MAC PDU, the data that fails integrity protection and the data that is not integrity protected on the MAC PDU will be discarded (for example, MAC SDU or RLC SDU or RLC PDU), or data on that MAC PDU that fails integrity protection and data associated with a partially intact PDCP entity that is not integrity protected will be discarded (e.g., MAC SDU or RLC SDU or RLC PDU ). It should be understood that for data 2 and data b that are not integrity protected, in the actual process, the first PDCP entity may receive data 2 and data b one by one or may receive data 2 and data b together. Therefore, every time it receives an unprotected In the case of integrity-protected data, it may be determined whether to discard the data that is not integrity-protected based on the integrity check result of the integrity-protected data associated with it.

The second possible situation is that the first communication device discards the second data and the third data in addition to the first data. As shown in Figure 12, the first data includes data 1, the second data includes data 2, and the third data can be data a or data b. When one or more data integrity checks among data 2, data a, and data b In the case of failure, data 1, data 2, data a and data b are discarded, that is, the first data, the second data and the third data are discarded. Or, when the integrity check of data 2 fails and the integrity check of data a and data b succeeds, data 1 and data 2 are discarded.

It should be understood that the two situations shown above are only examples and should not constitute any limitation on the embodiments of the present application. For example, the second data and the fourth data may also be discarded; or the second data, the fifth data, etc. may also be discarded. For the sake of brevity, they will not be described in detail here.

It can be understood that the above description is from the perspective of the circumstances under which the first communication device discards the first data. Correspondingly, the description can also be considered from the perspective of the circumstances under which the first communication device does not discard the first data.

Optionally, the above method may also include: S730: The first communication device does not discard the first data when the second condition is met.

The first communication device not discarding the first data may include/understood as one or more of the following: the first communication device stores the first data, the first communication device submits/stores the first data to the receiving buffer, the first communication device Reordering is performed, or the first communication device processes the first data.

Among them, the second condition includes one or more of the following:

The second data integrity check is successful;

The third data integrity check is successful;

The fourth data integrity check is successful;

The fifth data integrity check is successful; or,

The sixth data integrity check is successful.

First, several situations in which the first data is not discarded for a MAC PDU are shown.

The first possible situation is that the first communication device does not discard the first data when the second data integrity check is successful. If associated with the first MAC PDU (i.e., the same MAC PDU associated with the first data), and associated with the first PDCP entity (i.e., the same PDCP entity associated with the first data), the complete If the data integrity check of sexual protection is successful, it can be considered that there is no possibility of the first data being tampered with, and the first data will not be discarded. For example, the first MAC PDU only contains data associated with one PDCP entity. When the integrity check of the second data is successful, that is, the integrity check of the integrity-protected data in the first MAC PDU is successful, it is considered that the incomplete data can be ignored. There is a possibility that the integrity-protected data may be tampered with, so the first communication device does not discard the first data.

The second possible situation is that the first communication device does not discard the first data when the third data integrity check is successful. If associated with the first MAC PDU (i.e., the same MAC PDU associated with the first data), and associated with the second PDCP entity (i.e., different PDCP entity associated with the first data), the complete If the data integrity check of sexual protection is successful, it can be considered that there is no possibility of the first data being tampered with, and the first data will not be discarded. For example, the first MAC PDU contains data associated with the first PDCP entity and the second PDCP entity. If the integrity check of the third data succeeds, it is considered that the possibility of tampering with unprotected data can be ignored. Therefore the first communication device does not discard the first data.

The third possible situation is that the first communication device does not discard the first data when the second data integrity check is successful and the third data integrity check is successful. If associated with a first MAC PDU (i.e., the same MAC PDU associated with the first data), and associated with a second PDCP entity (i.e., a different PDCP entity associated with the first data) and with the first PDCP If the integrity check of the integrity-protected data associated with the entity (the same as the PDCP entity associated with the first data) is successful, it can be considered that there is no possibility of tampering with the first data, and the first data will not be discarded. For example, the first MAC PDU contains data associated with the first PDCP entity and the second PDCP entity. If the integrity check of the second data is successful and the integrity check of the third data is successful, the first data is not discarded.

It can be seen from the above situation that one possible implementation method is that if one or more integrity-protected data associated with the same MAC PDU as the first data is successfully verified, the first communication device may not Discard the first data.

Next, several situations of discarding the first data for multiple MAC PDUs are shown.

It should be understood that, as mentioned above, at least one of the first data to the sixth data may be fragmented, that is, a certain data is sent through different MAC PDUs. The fragmentation situation will be described in detail below. Conditions for not discarding the first data.

The first possible situation is that when the fourth data integrity check is successful, the first data is not discarded. There are two possible designs for the fourth successful data integrity check:

One possible design is that the fourth data may be segmented data. For example, part of the fourth data comes from the first MAC PDU, and another part of the fourth data comes from the second MAC PDU, passing through the first communication device. After the RLC layer is reorganized, the PDCP layer further performs an integrity check on the fourth data. Therefore, the success of the fourth data integrity check can be understood as consisting of a part of the fourth data in the first MAC PDU and the second MAC The other part of the fourth data in the PDU has no possibility of being tampered with, so the data in the first MAC PDU that is not integrity protected may not have the possibility of being tampered with. Therefore, the first communication device does not discard the first data.

Another possible design is that the first data may be segmented data, and the fourth data may be unsegmented data. For example, part of the first data comes from the first MAC PDU, and another part of the first data Data comes from the second MAC PDU, if the fourth data integrity check is successful, part of the first data in the second MAC PDU may not be tampered with, and therefore, the first communication device does not discard the first data.

The second possible situation is that the first communication device does not discard the first data when the second data integrity check is successful and the fourth data integrity check is successful. For example, the first MAC PDU only contains data associated with the first PDCP entity, the second MAC PDU only contains data associated with the first PDCP entity, and the first data is associated with the first MAC PDU and the second MAC PDU, then when When the second data integrity check is successful and the fourth data integrity check is successful, the first communication device does not discard the first data.

It should be understood that the situations shown above are only examples and should not constitute any limitation on the embodiments of the present application. For example, if the fifth data integrity check succeeds, the first data may not be discarded. For the sake of brevity, they will not be described in detail here.

It should also be understood that the success of the fifth data integrity check and/or the success of the sixth data integrity check are similar to the fourth data, and for the sake of brevity, they will not be described in detail here.

It should also be understood that the above-mentioned condition for discarding the first data and the condition for not discarding the first data can be used separately or in combination, and this is not limited in the embodiments of the present application.

It can be understood that the first communication device determines whether to discard the first data based on the integrity check result of one or more of the third data, the fifth data, or the sixth data, and the first communication device also needs to receive the cross-RB/ PDCP entity indication information. For example, the first PDCP entity receives indication information from other PDCP entities to determine its associated data integrity check results.

Exemplarily, the first communication device performs one or more of the following: based on the eighth indication information, determining that the third data integrity check is successful; based on the ninth indication information, determining that the fifth data integrity check is successful; or, Based on the tenth indication information, it is determined that the sixth data integrity check is successful.

Optionally, the eighth indication information comes from the second PDCP entity.

Optionally, the ninth indication information comes from the second PDCP entity.

Optionally, the tenth indication information comes from the third PDCP entity.

Exemplarily, the first PDCP entity receives the eighth indication information from the second PDCP entity, and the eighth indication information indicates that the third data integrity check is successful, then the first PDCP entity can determine the same MAC associated with the first data. The data integrity check associated with the PDU is successful, and the first data does not need to be discarded.

It should be noted that S730 can be implemented as an independent embodiment, or can be used as a step in this embodiment in combination with other steps in this embodiment, for example, as an optional step together with S710, S720 and A combination of one or more of the items i to v mentioned below. This application does not limit this.

Optionally, the above method may also include at least one of the following i and ii:

i. The first communication device or the PDCP layer/entity of the first communication device determines that at least one of the first data, the second data, and the third data is associated with the first MAC PDU based on the first indication information; or

ii. The first communication device or the PDCP layer/entity of the first communication device determines that at least one of the fourth data, the fifth data, and the sixth data is associated with the second MAC PDU based on the second indication information.

It can be understood that the first communication device obtains one or more PDCP PDUs and needs to determine which MAC PDU(s) these PDCP PDUs are associated with.

Optionally, the first indication information and/or the second indication information may come from the MAC layer or RLC layer of the first communication device.

Wherein, the first communication device or the PDCP layer/entity of the first communication device obtains the first indication information and the second indication information. Information, the first indication information and the second indication information may be obtained at the same time, or may not be obtained at the same time, may be obtained separately, or may be obtained together, which is not limited in the embodiment of the present application.

The process of the first communication device determining data associated with the same MAC PDU will be described below from the perspective of each protocol layer of the first communication device.

For example, when there is only one MAC PDU (such as the first MAC PDU), and the first MAC PDU only contains data associated with one PDCP entity, the MAC or RLC layer sends the first indication information to the PDCP layer to indicate the first data of the PDCP layer. and/or the second data is associated with the first MAC PDU.

In another example, when there is only one MAC PDU (such as the first MAC PDU), and the first MAC PDU contains data associated with multiple PDCP entities (such as the first PDCP entity and the second PDCP entity), the MAC or RLC layer transmits data to the PDCP layer. First indication information is sent to indicate that at least one of the first data, the second data or the third data of the PDCP layer is associated with the first MAC PDU.

Optionally, the first indication information also needs to indicate which PDCP entities the data contained in the first MAC PDU is associated with. For example, there is only one MAC PDU, such as MAC PDU 1. The MAC PDU 1 includes data 1, data 2 and data 3. Data 1 is associated with PDCP entity 1, and data 2 and data 3 are associated with PDCP entity 2, that is, The MAC PDU 1 contains data associated with two PDCP entities, then the MAC or RLC layer sends the first indication information to the PDCP layer. The first indication information can indicate: the information of the data associated with the MAC PDU 1 (for example, data 1 , the number information corresponding to at least one data in data 2 or data 3), and can also indicate: the information of the PDCP entity associated with MAC PDU 1 (for example, data 1 is associated with PDCP entity 1, and/or, data 2 and /or data 3 is associated with PDCP entity 2).

In another example, when there are multiple MAC PDUs (such as the first MAC PDU and the second MAC PDU), the MAC or RLC layer sends first indication information to the PDCP layer to indicate the first data, second data or third data of the PDCP layer. At least one of the data is associated with the first MAC PDU. The MAC or RLC layer sends second indication information to the PDCP layer to indicate that at least one of the fourth data, the fifth data, or the sixth data is associated with the second MAC PDU.

Optionally, if the data contained in a certain MAC PDU is associated with multiple PDCP entities, the indication information also needs to indicate which PDCP entities the data contained in the MAC PDU is associated with. For example, there are multiple MAC PDUs, such as MAC PDU 1 and MAC PDU 2. The MAC PDU 1 includes data 1 and data 2. Data 1 is associated with PDCP entity 1, and data 2 is associated with PDCP entity 2. That is, the MAC PDU 1 contains data associated with 2 PDCP entities. The above MAC PDU 2 includes data 3 and data 4. Data 3 is associated with PDCP entity 1, and data 4 is associated with PDCP entity 2. Then the MAC or RLC layer communicates with the PDCP layer. Send first indication information, which may indicate information about the data associated with MAC PDU 1 (for example, data 1, or number information corresponding to at least one data in data 2. For example, data 1 and data 2 are associated with MAC PDU 1 associated), can also indicate the information of the PDCP entity associated with MAC PDU 1 (for example, data 1 is associated with PDCP entity 1, data 2 is associated with PDCP entity 2), in addition, the MAC or RLC layer can also Send second indication information to the PDCP layer. The second indication information may indicate information about the data associated with MAC PDU 2 (for example, data 3, or number information corresponding to at least one data in data 4. For example, data 3 and data 4 associated with MAC PDU 2), and may also indicate information about the PDCP entity associated with MAC PDU 2 (for example, data 3 is associated with PDCP entity 1, data 4 is associated with PDCP entity 2). The first indication information and the second indication information may be carried in the same signaling, or may be carried in different signaling, which is not limited in this application.

The indication methods of the first indication information and the second indication information will be described in detail below.

One possible implementation is that the first indication information includes number information corresponding to at least one of the first data, the second data, or the third data; and/or the second indication information includes the fourth data, Number information corresponding to at least one of the fifth data or the sixth data.

The above numbering information can have the following two possible designs:

One possible design is that the above numbering information can be a newly defined number, and data associated with the same MAC PDU will receive the same number. For example, the data associated with the first MAC PDU will get the same number, such as number 1, and the data associated with the second MAC PDU will get a different number than the first MAC PDU, such as number 2. As an example, the first MAC PDU includes data 1, data 2 and data 3, and the second MAC PDU includes data 4 and data 5. Then the numbers of data 1, data 2 and data 3 can be number 1, and the numbers of data 4 and data 5. The number may be number 2. The first indication information may include number information corresponding to data 1, data 2 and data 3, such as number 1. The second indication information may include number information corresponding to data 4 and data 5, such as number 2.

Another possible design is that the above number can be a PDCP sequence number directly indicated to the PDCP layer by the MAC layer in the first communication device, or an RLC sequence number indicated by the MAC layer in the first communication device to the RLC layer, and then The PDCP sequence number indicated by the RLC layer to the PDCP layer. For example, the MAC layer directly indicates to the PDCP layer which data corresponding to the PDCP sequence number is associated with the first MAC PDU, and which data corresponding to the PDCP sequence number is associated with the second MAC PDU. After the PDCP layer reads the PDCP sequence number , the data associated with the first MAC PDU and the data associated with the second MAC PDU can be determined.

As mentioned before, the data obtained by the first communication device may be associated with different PDCP entities. For example, the first data, the second data and the fourth data are associated with the first PDCP entity, and the third data and the fifth data are associated with the first PDCP entity. The second PDCP entity is associated, the sixth data is associated with the third PDCP entity, and the integrity check of a certain data is performed by its corresponding PDCP entity. Therefore, for the first PDCP entity, it is necessary to Receive the integrity check results of its associated data from other PDCP entities. It should be noted that in the embodiment of this application, for the case of one MAC PDU, this article takes two PDCP entities (such as the first PDCP entity and the second PDCP entity) as an example to illustrate. For the case of two MAC PDUs, This article uses three PDCP entities (such as the first PDCP entity, the second PDCP entity, and the third PDCP entity) for description. In other embodiments, the first communication device may also correspond to a larger number of PDCP entities, that is, it is necessary to perform The number of interactive PDCPs will be greater, which is not limited in the embodiments of this application.

Optionally, the above method may also include at least one of the following iii to v:

iii. The first communication device determines that the third data integrity check fails or succeeds based on the fourth indication information;

iv. The first communication device determines that the fifth data integrity check failed or succeeded based on the fifth indication information; or

v. The first communication device determines that the sixth data integrity check fails or succeeds based on the sixth indication information.

Optionally, the fourth indication information comes from the second PDCP entity.

Optionally, the fifth indication information comes from the second PDCP entity.

Optionally, the sixth indication information comes from the third PDCP entity.

For example, the first PDCP entity receives the fourth indication information from the second PDCP entity, and the fourth indication information indicates that the third data integrity check fails, then the first PDCP entity may determine that the third data integrity check fails, That is, if the integrity check of the integrity-protected data associated with the first MAC PDU and associated with the second PDCP entity fails, the first PDCP entity can discard the first data.

For example, the first PDCP entity receives the fourth indication information from the second PDCP entity, and the fourth indication information indicates that the third data integrity check is successful, then the first PDCP entity can determine that the third data integrity check is successful, also That is, if the integrity check of the integrity-protected data associated with the first MAC PDU and associated with the second PDCP entity is successful, the first PDCP entity may not discard the first data.

Based on the above technical solution, after the first communication device obtains the data that is not integrity protected (for example, the first data), it can discard the second data if the verification of the integrity protected data associated with it fails. One data. By checking the results of the integrity-protected data and then determining whether to discard the data that is not integrity-protected, a method for processing the data that is not integrity-protected is provided for the first communication device. It is also helpful to improve the accuracy of data reception or the accuracy of data submitted to the upper level. Helps improve communication quality/efficiency. For example, there are many cases where data without integrity protection is discarded, that is, the conditions for submitting data without integrity protection to the upper layer are stricter, which is helpful to improve the accuracy of data reception or the accuracy of data submitted to the upper layer.

Another communication method provided by the embodiment of the present application will be described below with reference to FIG. 13 . Figure 13 is a schematic flowchart of another communication method 1300 provided by an embodiment of the present application. The communication method 1300 shown in FIG. 13 may include S1310 to S1330. Each step in method 1300 is described in detail below.

S1310. The first communication device generates seventh indication information, where the seventh indication information is used to indicate adjusting (or recommending adjusting) the proportion of integrity protected data.

Among them, adjusting or recommending to adjust the proportion of integrity-protected data includes/is understood to mean any of the following: increasing (or recommending to increase) the proportion of integrity-protected data, lowering (or recommending to lower) the proportion of integrity-protected data. The proportion of data, increasing (or recommending to increase) the data for integrity protection, reducing (or recommending to reduce) the data for integrity protection, turning on (or recommending turning on) the partial full protection function, or turning off (or recommending turning off) the partial full protection function. .

Turning up can include/understand as: increase.

Turning down can include/understand as: reduce.

Turning on can include/understand as: enabling.

Shutdown can include/be understood as: disabling.

Optionally, the seventh indication information may also be used to indicate the adjustment ratio, or to recommend the adjustment ratio.

In other words, the seventh indication information may instruct the second communication device to adjust (or recommend adjusting) the proportion of integrity protection, and may also indicate a numerical value of the proportion of integrity protection data that is specifically adjusted (or recommended to be adjusted). For example, the seventh instruction information may indicate increasing (or recommending increasing) the proportion of integrity protected data, and may also indicate a specific amount of increasing (or recommending increasing). For another example, the seventh instruction information may indicate to reduce (or recommend to reduce) the proportion of integrity protected data, and may also indicate how much to specifically reduce (or recommend to reduce).

Optionally, the above method may also include: when the third condition is met, the seventh instruction information indicates to increase (or recommend to increase) the proportion of integrity protected data, or to increase (or recommend to increase) the integrity protected data, or Turn off (or recommend turning off) some full protection functions.

Among them, the third condition includes one or more of the following:

The number of integrity check failures is greater than or equal to the first threshold; or,

The number of received MAC PDUs that do not contain integrity-protected data is greater than or equal to the second threshold.

Among them, the MAC PDU may also contain a MAC control element (control element, CE), etc. It should be noted that the data mentioned above may refer to the MAC SDU or the PDCP PDU corresponding to the MAC SDU.

The number of integrity check failures being greater than or equal to the first threshold may include/replaced by: the number of integrity check successes being less than or equal to the first threshold.

Integrity-protected data can be replaced with integrity-protected MAC SDU or the PDCP corresponding to the MAC SDU. PDU.

Optionally, the above method may also include: meeting the fourth condition, the seventh instruction information indicating to reduce (or recommend reducing) the proportion of integrity protected data or, reducing (or recommending reducing) the integrity protected data, or Turn on (or recommend turning on) some full protection functions.

Among them, the fourth condition includes one or more of the following:

The number of successful integrity checks is greater than or equal to the third threshold;

The number of received MAC PDUs containing integrity protected data is greater than or equal to the fourth threshold; or,

The number of received MAC PDUs is greater than or equal to the fifth threshold, in which the data contained in the received MAC PDUs is integrity protected.

Among them, the MAC PDU may also contain MAC CE. It should be noted that the data described here refers to the MAC SDU or the PDCP PDU corresponding to the MAC SDU. For example, the data contained in the received MAC PDU is integrity protected, which can be replaced by: the MAC SDU contained in the received MAC PDU is integrity protected.

The data contained in the received MAC PDU is integrity protected, which can include/understand as one or more of the following: The data contained in the received MAC PDU (for example, MAC SDU or RLC SDU or RLC PDU) is complete Integrity-protected data; or, the data contained in the received MAC PDU and associated with the PDCP entity associated with partial integrity protection (for example, MAC SDU or RLC SDU or RLC PDU) is integrity-protected data.

The number of times of integrity check successes being greater than or equal to the third threshold may include/replaced by: the number of times of integrity check failures being less than or equal to the third threshold.

The third condition and the fourth condition are explained in detail below respectively.

The number of integrity check failures is determined by either of the following: the number of PDCP PDUs that fail the integrity check; or the number of MAC PDUs that contain the PDCP PDUs that fail the integrity check.

Optionally, the number of integrity check failures may be the number of consecutive integrity check failures or the number of discontinuous integrity check failures. For example, continuous integrity check failure means that during the integrity check, consecutive integrity checks fail, and no integrity check succeeds in the middle. Discontinuous integrity check failures refer to multiple integrity checks being performed, some of which are successful and some of which are failed. Among them, the integrity check failures are discontinuous. For example, if four integrity checks are performed, the first integrity check fails, the second and third integrity checks succeed, and the fourth integrity check fails, then the number of integrity check failures is for twice.

One possible design is that the number of integrity check failures can be determined based on the number of PDCP PDUs that fail the integrity check. The number of PDCP PDUs that fail the integrity check may be the number of PDCP PDUs that fail the continuous integrity check, or the number of PDCP PDUs that fail the discontinuous integrity check. This is not the case in the embodiment of this application. limited.

Optionally, the number of PDCP PDUs that fail the integrity check may be at the granularity of the first communication device or at the granularity of a PDCP entity. The PDCP entity granularity can also be described/replaced as RB granularity, or LCH granularity, or LCID granularity, or RLC entity granularity.

Optionally, if the number of PDCP PDUs that fail integrity check can be granular for one PDCP entity, the number of integrity check failures can be the number of consecutive integrity check failures, or it can be discontinuous complete The number of failed sex checks. For example, continuous integrity check failure refers to the situation where continuous integrity checks fail for a PDCP entity, and no integrity check succeeds in the middle. Discontinuous integrity check failures refer to multiple integrity checks being performed on a PDCP entity. Some integrity checks are successful, and some integrity checks fail. Among them, the integrity check Verification failures are discontinuous. For example, if four integrity checks are performed, the first integrity check fails, the second and third integrity checks succeed, and the fourth integrity check fails, then the number of integrity check failures is for twice.

As an example, the first communication device can maintain a counter. The number of PDCP PDUs that fail integrity check increases by 1, and the number of times that the counter integrity check fails increases by 1.

Optionally, the number of PDCP PDUs that fail the integrity check is the number of PDCP PDUs that fail the integrity check within the first preset time period.

For example, the duration can be set. When the first preset duration is reached and the number of PDCP PDUs that fail integrity check is greater than or equal to the first threshold, the seventh instruction information indicates to increase (or recommend to increase) the integrity The proportion of data with integrity protection, or increasing (or recommending to increase) the data with integrity protection, or turning off (or recommending turning off) some of the integrity protection functions.

Another possible design is that the number of integrity check failures can be determined based on the number of MAC PDUs containing PDCP PDUs that failed integrity check.

The number of MAC PDUs containing PDCP PDUs that failed integrity check may be at the granularity of the first communication device or at the granularity of a PDCP entity.

As an example, the first communication device can maintain a counter. The number of MAC PDUs containing PDCP PDUs that fail integrity check increases by 1, and the integrity check of the counter increases by 1. Wherein, for a certain MAC PDU, if The number of PDCP PDUs that failed integrity check in this MAC PDU is 2, and the counter is increased by 1.

Optionally, the number of MAC PDUs containing PDCP PDUs that fail integrity check is the number of MAC PDUs that contain PDCP PDUs that fail integrity check within the second preset time period.

For example, the duration can be set. When the second preset duration is reached and the number of MAC PDUs containing PDCP PDUs that failed integrity check is greater than or equal to the second threshold, the seventh instruction information indicates to increase the value (or recommend Increase) the proportion of integrity-protected data, or increase (or recommend adding) integrity-protected data, or close (or recommend closing) some of the complete protection functions.

Optionally, the number of PDCP PDUs that failed the integrity check is associated with a PDCP entity; or, the number of MAC PDUs that contain the PDCP PDU that failed the integrity check is associated with the PDCP PDU that failed the integrity check. A PDCP entity is associated.

Among them, the number of PDCP PDUs that failed integrity check is associated with one PDCP entity, indicating that the number of PDCP PDUs that failed integrity check is based on one PDCP entity granularity. For example, a PDCP entity maintains a counter. If the number of PDCP PDUs associated with the PDCP entity that fail the integrity check increases by 1, then the integrity check of the counter corresponding to the PDCP entity increases by 1.

The PDCP PDU that fails the integrity check and is associated with a PDCP entity in the number of MAC PDUs that contain the PDCP PDU that fails the integrity check is also based on the granularity of a PDCP entity. For example, a PDCP entity maintains a counter. For a certain MAC PDU, if the number of PDCP PDUs that fail integrity check in the MAC PDU is 2, and these two PDCP PDUs are associated with different PDCP entities , then the counter corresponding to each PDCP entity increases by 1.

The number of successful integrity checks is determined by either of the following: the number of PDCP PDUs with successful integrity checks; or the number of MAC PDUs containing PDCP PDUs with successful integrity checks.

Optionally, the number of successful integrity checks may be the number of successful continuous integrity checks, or the number of successful discontinuous integrity checks. For example, continuous integrity check success means that during the integrity check, consecutive integrity checks are successful, and there is no integrity check failure in the middle. Discontinuous integrity check success means that multiple During the integrity check, some are successful and some are failed. Among them, the success of integrity check is discontinuous. For example, if five integrity checks are performed, the first integrity check succeeds, the second to fourth integrity checks fail, and the fifth integrity check succeeds, then the number of successful integrity checks for twice.

The number of successful integrity checks can be determined based on the number of PDCP PDUs with successful integrity checks.

Optionally, the number of PDCP PDUs with successful integrity check is based on the granularity of the first communication device, or may be based on the granularity of a PDCP entity. The PDCP entity granularity can also be described/replaced as RB granularity, or LCH granularity, or LCID granularity, or RLC entity granularity.

Optionally, if the number of PDCP PDUs with successful integrity check can be based on one PDCP entity granularity, the number of successful integrity checks can be the number of consecutive successful integrity checks, or it can be discontinuous complete The number of successful sex checks. For example, continuous integrity check success means that for a PDCP entity, continuous integrity checks are successful, and there is no integrity check failure in the middle. Discontinuous integrity check success means that multiple integrity checks have been performed on a PDCP entity. Some integrity checks are successful, and some integrity checks fail. Among them, the integrity check successes are discontinuous. For example, if four integrity checks are performed, the first integrity check succeeds, the second and third integrity checks fail, and the fourth integrity check succeeds, then the number of successful integrity checks for twice.

For example, the first communication device may maintain a counter. The number of PDCP PDUs with successful integrity checks increases by 1, and the number of successful integrity checks indicated by the counter increases by 1.

Optionally, the number of PDCP PDUs whose integrity verification is successful is the number of PDCP PDUs whose integrity verification is successful within the third preset time period.

For example, the duration can be set. When the third preset duration is reached and the number of PDCP PDUs with successful integrity verification is greater than or equal to the third threshold, the seventh instruction information indicates to lower (or recommends lowering) the integrity The proportion of integrity-protected data may be reduced (or it is recommended to reduce) the integrity-protected data, or the partial integrity protection function may be enabled (or it is recommended to be enabled).

The number of successful integrity checks can also be determined based on the number of MAC PDUs containing PDCP PDUs with successful integrity checks.

The number of MAC PDUs is for the granularity of the first communication device, or it may be for the granularity of a PDCP entity.

For example, the first communication device can maintain a counter, and the number of MAC PDUs containing PDCP PDUs with successful integrity checks increases by 1, and then the number of successful integrity checks indicated by the counter increases by 1, where, for a certain MAC PDU For example, if the number of PDCP PDUs with successful integrity check in this MAC PDU is 2, the counter increases by 1.

Optionally, the number of MAC PDUs containing PDCP PDUs with successful integrity verification is the number of MAC PDUs containing PDCP PDUs with successful integrity verification within the fourth preset time period.

For example, the duration can be set. When the fourth preset duration is reached and the number of MAC PDUs containing PDCP PDUs with successful integrity verification is greater than or equal to the fourth threshold, the seventh indication information indicates to lower (or recommend Reduce) the proportion of integrity-protected data, or reduce (or recommend reducing) the integrity-protected data, or turn on (or turn on) part of the complete protection function.

Optionally, the number of PDCP PDUs with successful integrity verification is associated with a PDCP entity; or, the number of MAC PDUs containing PDCP PDUs with successful integrity verification is associated with the PDCP PDU with successful integrity verification. A PDCP entity is associated.

Among them, the number of PDCP PDUs whose integrity check is successful is associated with a PDCP entity to indicate the integrity check. The number of successful PDCP PDUs is based on one PDCP entity granularity. For example, a PDCP entity maintains a counter. If the number of PDCP PDUs associated with the PDCP entity with successful integrity check increases by 1, then the integrity check of the counter corresponding to the PDCP entity increases by 1.

The number of MAC PDUs containing PDCP PDUs with successful integrity checks. The PDCP PDUs with successful integrity checks are associated with a PDCP entity and are also granular for a PDCP entity. For example, a PDCP entity maintains a counter. For a certain MAC PDU, if the number of PDCP PDUs with successful integrity check in the MAC PDU is 2, and these two PDCP PDUs are associated with different PDCP entities , then the counter corresponding to each PDCP entity increases by 1.

It should be understood that the adjustment or recommendation to adjust the proportion of integrity protected data described above may be at the communication device granularity or at the PDCP entity granularity. For example, the seventh instruction information indicates adjusting or recommending adjusting the proportion of integrity-protected data in the second communication device.

Optionally, the seventh indication information is associated with one PDCP entity. In other words, adjusting or recommending adjusting the proportion of integrity protected data is based on the PDCP entity granularity. For example, the seventh indication information may be used to instruct or recommend adjusting the proportion of integrity protected data associated with a certain PDCP entity in the second communication device.

Illustratively, taking the first PDCP entity as an example, the number of PDCP PDUs that fail the integrity check associated with the first PDCP entity reaches the first threshold, and the seventh instruction information indicates or recommends increasing the association of the first PDCP entity. The proportion of integrity protected data, or the first PDCP entity is turned off or it is recommended to turn off the partial integrity protection function. In other words, the proportion of integrity-protected data associated with other PDCP entities of the second communication device does not need to be adjusted.

S1320. The first communication device sends seventh instruction information to the second communication device. Correspondingly, the second communication device receives the seventh indication information.

After the first communication device generates the seventh indication information, it sends it to the second communication device, so that the second communication device adjusts the proportion of integrity protected data.

For example, the seventh indication information occupies 1 bit. A value of 1 indicates that the proportion of data for integrity protection is increased (or recommended to be increased), and a value of 0 indicates that the proportion of data for integrity protection is decreased (or recommended to be increased). The specific adjusted value may be determined by the second communication device.

For another example, a value of 1 means turning on (or recommending turning on) the partial full protection function, and a value of 0 means turning off (or recommending turning off) the partial full protection function.

Optionally, the seventh indication information indicates information on at least one of the corresponding PDCP entity, RB, LCH, or LCID.

For example, adjusting the proportion of integrity protected data can also be based on PDCP entity granularity. The seventh instruction information indicates adjusting (or recommending adjustment) the proportion of integrity protected data associated with a certain PDCP entity. The seventh instruction information also needs to Information indicating the corresponding PDCP entity. The seventh indication information may also indicate the corresponding RB, or LCH, or LCID information. The embodiments of the present application do not limit this.

Optionally, the above method further includes: S1330: The second communication device adjusts the proportion of integrity protected data based on the seventh indication information.

After receiving the seventh indication information, the second communication device adjusts the proportion of integrity protected data based on the seventh indication information.

For example, the seventh instruction information indicates to increase (or recommend to increase) the proportion of integrity-protected data in the second communication device. After receiving the seventh instruction information, the second communication device adjusts the proportion of integrity-protected data. High, specifically increase The value of may be determined by the second communication device, for example, may be determined based on the functions of the second communication device itself.

For another example, the seventh instruction information indicates to increase (or recommend to increase) the proportion of integrity protected data associated with the first PDCP entity in the second communication device. Then, after receiving the seventh instruction information, the second communication device will If the proportion of integrity-protected data associated with one PDCP entity is increased, other PDCP entities can integrity-protect data according to the original proportion.

Based on the above technical solution, the first communication device can generate the seventh indication information based on the verification result of the integrity protected data, and send it to the second communication device, so that the second communication device adjusts the completeness based on the seventh indication information. The proportion of integrity-protected data is conducive to improving the rationality of the proportion of integrity-protected data in the second communication device and improving communication quality/efficiency.

It should be noted that the embodiments shown in Fig. 7 and Fig. 13 can be used in combination or alone. The comparison of the embodiments of this application is not limited.

As can be seen from the above, in the case of partial integrity protection, a MAC PDU contains at least one integrity-protected MAC SDU for each PDCP entity. The following will describe in detail the process of MAC multiplexing by the second communication device in conjunction with specific embodiments. How to ensure that a MAC PDU contains at least one integrity-protected MAC SDU for a PDCP entity (for example, a PDCP entity associated with partial integrity).

Figure 14 is a schematic flow chart of yet another communication method 1400 provided by an embodiment of the present application. The communication method 1400 shown in FIG. 14 may include S1410 and S1420. Each step in method 1400 is described in detail below.

S1410. Obtain the first resource.

S1420. When the fifth condition is met, the second communication device allocates resources to the first LCH.

Optionally, the first LCH is associated with partial coverage.

The first LCH is associated with partially completed protection, which may include/understood as one or more of the following: the first RLC entity corresponding to the first LCH is associated with partially completed protection, or the first RB corresponding to the first LCH is associated with partially completed protection Full coverage is associated, or the first LCID corresponding to the first LCH is associated with partial full coverage, or the first PDCP entity corresponding to the first LCH is associated with partial full coverage. This is not limited in the embodiment of the present application.

The fifth condition includes one or more of the following:

The remaining resources of the first resource or the first resource are greater than or equal to the size of the first data set and the size of the MAC subheader; or,

The variable corresponding to the first LCH is greater than or equal to the size of the first data set.

The remaining resources of the first resource or the first resource being greater than or equal to the size of the first data set and the size of the MAC subheader may include: the first resource can accommodate the first data set.

The MAC subheader refers to the subheader of the MAC SDU, and each MAC SDU includes the subheader.

The first data set includes seventh data, or the first data set includes seventh data and the second data set.

Among them, the seventh data is integrity-protected data. The second data set includes at least one data, and at least one data is data that is not integrity protected.

It should also be understood that the second communication device first performs LCH selection according to LCP restrictions, and then allocates resources to the LCH in descending order of LCH priority.

One possible implementation method is that if the PDCP entity part corresponding to the LCH is fully associated, execution is performed according to the embodiment shown in Figure 14. If the PDCP entity corresponding to the LCH is not associated with partial integrity, it can be performed according to the existing MAC multiplexing or other processes, which is not limited by this application.

The second communication device allocates resources to the first LCH. One possible implementation is that the remaining resources of the first resource are greater than or equal to the size of the first data set and the size of the MAC subheader, and the second communication device allocates resources to the first LCH. Resources, in other words, the first data set is multiplexed in the first MAC PDU, then at least one data corresponding to the first LCH in the first MAC PDU is integrity protected data, that is, the seventh data.

Another possible implementation is that when the variable corresponding to the first LCH, that is, the aforementioned Bj is greater than or equal to the size of the first data set, the second communication device allocates resources to the first LCH. Optionally, the variable corresponding to the first LCH is greater than 0.

Another possible implementation is that the remaining resources of the first resource are greater than or equal to the size of the first data set and the size of the MAC subheader, and the variable corresponding to the first LCH, that is, the aforementioned Bj is greater than or equal to the first If the size of the data set is determined, the second communication device allocates resources to the first LCH.

Optionally, the second data set includes all data before the seventh data; or, the second data set includes all data between the seventh data and the eighth data, where the eighth data is integrity protected data. .

It should be noted that in the embodiment of the present application, before or after can be understood according to the order in the process of data being delivered by the RLC layer. For example, all data before the seventh data refers to the data delivered by the RLC layer. , all data before the seventh data.

Two possible situations for the above second data set will be described in detail below:

One possible situation is that the second data set includes all data before the seventh data. There may be one or more data that are not integrity protected before the seventh data, and there is no other data that is integrity protected. After the seventh data, there may be data that are integrity protected or not. That is, during the MAC multiplexing process, for the first LCH, if Bj is greater than or equal to the first integrity-protected data (i.e., the seventh data) and the data before it (i.e., the second data set), then it will Multiplexed in the MAC PDU, thereby ensuring that the MAC PDU contains at least one integrity-protected data for each PDCP entity.

Optionally, the second data set includes all data before the seventh data, including: the second data set includes all data between the ninth data and the seventh data. The ninth data may be integrity-protected data before the seventh data.

That is to say, the seventh data may also include integrity-protected data (such as ninth data). The remaining resources of the first resource need to accommodate the following data: between the seventh data, the ninth data and the seventh data. data, thereby ensuring that the MAC PDU contains at least one integrity-protected data (ie, the seventh data) for each PDCP entity. Among them, the data between the ninth data and the seventh data does not include the seventh data and the ninth data.

Another possible situation is that the second data set includes all data between the seventh data and the eighth data. In other words, during the MAC multiplexing process, for the first LCH, if Bj is greater than or equal to the first one, complete The data with integrity protection (i.e., the seventh data) and the data between the first data with integrity protection and the second data with integrity protection (i.e., the second data set) are multiplexed in the MAC PDU , thus ensuring that the MAC PDU contains at least one integrity-protected data for each PDCP entity.

Optionally, the eighth data is integrity-protected data after the seventh data.

In other words, the seventh data is the first data in the first data set, that is, the integrity-protected data is the first data in the first data set, thus ensuring that after MAC multiplexing, the MAC PDU The first data for each PDCP entity is the data for integrity protection.

The process of allocating resources by the second communication device is described in detail below with reference to specific examples.

One possible design is that the second communication device allocates resources in the following manner to ensure that the first MAC SDU for each RB contained in each MAC PDU is integrity protected:

Taking the first LCH among multiple LCHs as an example, the first LCH is the LCH with the highest priority among the multiple LCHs. If Bj is greater than or equal to the first integrity-protected data in the first LCH and the first For data between the integrity-protected data and the second integrity-protected data, resources are allocated to the first LCH.

On the contrary, if Bj is smaller than the data between the first integrity-protected data in the LCH and the first integrity-protected data to the second integrity-protected data, then the next one is judged. LCH.

It should be noted that it is also possible to comprehensively consider whether the remaining resources can accommodate the first integrity-protected data in the first LCH and the first integrity-protected data to the second integrity-protected data. In other words, if Bj is greater than or equal to the first integrity-protected data in the first LCH and the first integrity-protected data to the second integrity-protected data. data between, and the remaining resources can accommodate the data between the first integrity-protected data in the first LCH and the first integrity-protected data to the second integrity-protected data, Then allocate resources to the first LCH.

It should be understood that according to the above method, each LCH can be judged in order from high to low LCH priority.

It should also be understood that after judging all LCHs that meet the conditions, if there are remaining resources, the LCH priority will be in descending order, regardless of Bj, and integrity protection will be performed based on whether the remaining resources can accommodate a set of data (such as the next one). data before the data) to make a judgment.

Another possible design is that the second communication device allocates resources in the following manner to ensure that each MAC PDU contains one MAC SDU for each RB that is integrity protected (the first one is not required).

Taking the first LCH among multiple LCHs as an example, the first LCH is the LCH with the highest priority among the multiple LCHs. If Bj is greater than or equal to the first fully protected data in the first LCH and its previous data, and If the remaining resources can accommodate this part of data, resources will be allocated to the first LCH.

On the contrary, if Bj is smaller than the first intact data in the first LCH and its previous data, the next LCH is determined.

It should be noted that whether the remaining resources can accommodate the first fully guaranteed data in the first LCH and its previous data can also be comprehensively considered. In other words, if Bj is greater than or equal to the first fully guaranteed data in the first LCH and the data before it, and the remaining resources can accommodate the first intact data in the first LCH and the data before it, then allocate resources to the first LCH.

It should be understood that according to the above method, each LCH can be judged in order from high to low LCH priority.

It should also be understood that after judging all LCHs that meet the conditions, if there are remaining resources, the LCH priority will be in descending order, regardless of Bj, and integrity protection will be performed based on whether the remaining resources can accommodate a set of data (such as the next one). data before the data) to make a judgment.

Optionally, the data in the first data set, the eighth data, and the ninth data are associated with one PDCP entity. In other words, the data, the eighth data, and the ninth data in the first data set are associated with one LCH, that is, with one RB.

Optionally, the above method also includes: the second communication device sends a MAC PDU.

After allocating resources according to the above method, the second communication device can send the multiplexed MAC PDU.

Based on the above technical solution, when the remaining resources of the first resource are greater than or equal to the size of the first data set and the size of the MAC subheader, and/or the variable corresponding to the first LCH is greater than or equal to the first data set, the second communication device of If the size is large, allocate resources to the first LCH associated with partial security, where the first LCH associated with partial security means that the PDCP entity corresponding to the first LCH is configured with partial security, thus ensuring The MAC PDU contains at least one integrity-protected data for each PDCP entity. Compared with the MAC PDU, which contains at least one integrity-protected data, it is helpful to reduce the possibility of data tampering, thereby helping to improve data security. sex.

It should be noted that the various steps in the various embodiments described in this application (such as the embodiments corresponding to FIG. 7, FIG. 13, and FIG. 14) may be simultaneous or sequential. For example, S720 and S730 in Figure 7 can be executed at the same time or in sequence. For example, the first communication device can execute S720 first and then S730; or vice versa. This is not limited in the embodiment of the present application. In addition, the step numbers of the various embodiments described in the embodiments of this application (such as the embodiments corresponding to Figures 7, 13, and 14) are only an example of the execution process, and do not constitute an indication of the order of execution of the steps. Limitation: There is no strict execution order between steps that have no temporal dependence on each other in the embodiments of this application.

It should be noted that each of the embodiments described in this application (such as the embodiments corresponding to Figures 7, 13, and 14) can be implemented individually or in combination (for example, all or part of the solutions involved in Figure 7 can be implemented Combined with the embodiment corresponding to Figure 13), the details are not limited.

In addition, currently, network equipment can configure terminal equipment to perform RLM measurement and/or BFD measurement to monitor the quality of communication links and/or communication beams to ensure communication information. The terminal device can relax the RLM measurement and/or BFD measurement when certain relaxation criteria are met. For example, the terminal device performs the RLM measurement and/or BFD measurement in a longer period. However, when the RLM measurement and/or BFD measurement is relaxed, the terminal equipment may suffer from radio link failure (RLF) and/or due to the terminal equipment not monitoring the communication link and/or beam quality in a timely manner. Or beam failure (BF), therefore how to avoid or reduce the failure of terminal equipment due to relaxing RLM measurement and/or BFD measurement is an urgent problem to be solved.

To address this problem, embodiments of the present application provide a communication method that controls the RLM/BFD measurement relaxation behavior of the terminal device through the network device, so that the network can adjust the UE's strategy for relaxing RLM measurement and/or BFD measurement according to the UE's situation. , to minimize the probability of UE failure when relaxing measurements. The above communication method will be described in detail below with reference to Figure 15. As shown in Figure 15, the method includes S1510 to S1550. Each step of Figure 15 will be described in detail below.

It should be understood that the steps shown in Figure 15 are only examples and should not constitute any limitation on the embodiments of the present application. For example, in other embodiments, the communication method may include more or fewer steps than in FIG. 15 , such as not including S1520.

S1510. The network device sends RLM/BFD measurement relaxation configuration information to the terminal device.

RLM/BFD measurement relaxation configuration information may be used to indicate RLM/BFD measurement relaxation criterion configuration. The RLM/BFD measurement relaxation criterion configuration is used by the terminal device to determine whether the conditions for relaxing RLM/BFD measurement are met. The configuration may include a quality threshold and/or a duration threshold of the reference signal. Specifically, the RLM/BFD measurement relaxation configuration information may include low mobility criterion (low mobility criterion) configuration and/or serving cell quality criterion (serving cell quality criterion) configuration.

The RLM/BFD measurement relaxation configuration information may also be used to indicate rules for RLM/BFD measurement relaxation. The specific rules for RLM/BFD measurement relaxation can be that the terminal device (after meeting the RLM/BFD measurement relaxation criteria) can decide whether to perform measurement relaxation on its own, or the terminal device (after meeting the RLM/BFD measurement relaxation criteria) needs to determine according to the instruction information of the network. Is it possible to measure relaxation.

For example, if the RLM/BFD measurement relaxation configuration information sent by the network device contains the first field, it means that the terminal device (after meeting the RLM/BFD measurement relaxation criteria) needs to determine whether measurement relaxation can be performed based on the network's instruction information. If the RLM/BFD measurement relaxation configuration information sent by the network device does not contain the first field, it means that the terminal device can decide whether to perform measurement relaxation after meeting the RLM/BFD measurement relaxation criteria.

For another example, the RLM/BFD measurement relaxation configuration information sent by the network device includes a first field. The first field has at least two values. If the first field is set to a value of 1, it means that the terminal device (satisfies the RLM/BFD measurement requirements) After relaxing the criteria), it is necessary to determine whether measurement relaxation can be performed based on the instruction information of the network device; if the first field is set to the value 2, it means that the terminal device can decide whether to perform measurement relaxation after meeting the RLM/BFD measurement relaxation criteria.

It should be noted that the network device can indicate the RLM/BFD measurement relaxation criterion configuration and the RLM/BFD measurement relaxation rule in the same message, or in different messages. In other words, the RLM measurement relaxation rules and the BFD measurement relaxation rules can be indicated separately or together, which is not limited in the embodiments of the present application.

S1520: The terminal device measures the relaxation configuration information according to the RLM/BFD and determines that the relaxation criteria are met.

The terminal device evaluates the RLM/BFD measurement relaxation criteria based on the RLM/BFD measurement relaxation configuration information sent by the access network device, and determines that the relaxation criteria are met.

Among them, S1520 may be an optional step.

S1530: The terminal device determines the measurement relaxation rules according to the RLM/BFD measurement relaxation configuration information.

The terminal device determines the rules for RLM/BFD measurement relaxation based on the RLM/BFD measurement relaxation configuration information sent by the access network device.

Among them, the measurement relaxation rule may be that the terminal device (after meeting the RLM/BFD measurement relaxation criteria) can decide whether to perform measurement relaxation on its own, or the terminal device (after meeting the RLM/BFD measurement relaxation criteria) needs to determine whether it can be performed based on the instruction information of the network. Measure relaxation.

S1540a. If the measurement relaxation rule is that the terminal device (after meeting the RLM/BFD measurement relaxation criteria) can decide on its own whether to perform measurement relaxation, the terminal device relaxes the RLM/BFD measurement.

Specifically, the terminal device may relax the RLM measurement and/or the BFD measurement if the relaxation criteria are met. The specific way to relax the RLM measurement and/or BFD measurement may be that the terminal device increases the measurement period of the RLM measurement and/or BFD measurement, increases the indication and/or reporting period of the RLM measurement and/or BFD measurement, or reduces the RLM The number of reference signals for measurement and/or BFD measurement, etc.

S1540b. If the measurement relaxation rule is that the terminal device (after meeting the RLM/BFD measurement relaxation criteria) needs to determine whether measurement relaxation can be performed based on the instruction information of the network, the terminal device determines whether to relax the RLM/BFD measurement.

The terminal device determines whether to relax or not to relax the measurement according to the instruction information sent by the network device.

Specifically, if the network device indicates that relaxation is allowed, or if the network device does not indicate (within a certain period of time) that relaxation is not allowed, the terminal device may perform measurement relaxation. If the network device indicates that relaxation is not allowed, or the network device does not indicate that relaxation is allowed, the terminal device will not perform measurement relaxation.

S1550. The network device sends instruction information to the terminal device.

The indication information is used to indicate whether the terminal device can perform RLM/BFD measurement relaxation.

Specifically, the indication information may be an indication that the terminal device is allowed to perform measurement relaxation, or an indication that the terminal device is not allowed to perform measurement relaxation.

It should be understood that in the above embodiments, the terminal device and/or the network device may perform some or all of the steps in each embodiment. These steps or operations are only examples, and embodiments of the present application may also perform other operations or variations of various operations. In addition, various steps may be performed in a different order presented in each embodiment, and it is possible that not all operations in the embodiments of the present application are performed. Moreover, the size of the serial number of each step does not mean 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 embodiment of the present application.

It should be understood that the embodiments of the present application can also be applied to other types of measurement relaxation. For example, Radio Resource Management (RRM) measurement. Anything that conforms to the logic of the above embodiments should also be within the scope of this application.

16 to 19 are schematic structural diagrams of possible communication devices provided by embodiments of the present application.

Figure 16 is a schematic block diagram of a communication device 1600 provided by an embodiment of the present application.

As shown in Figure 16, the communication device 1600 includes a processing unit 1610 and a transceiver unit 1620.

The above-mentioned device 1600 may be used to implement the functions of the first communication device in the above-mentioned method embodiment shown in Figure 7, or the above-mentioned device 1600 may include any means for implementing the first communication device in the above-mentioned method embodiment shown in Figure 7. A functional or operational module that may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. The above-mentioned device 1600 may be used to implement the functions of the first communication device in the above-mentioned method embodiment shown in Figure 13, or the device 1600 may include any of the first communication devices used in the above-mentioned method embodiment shown in Figure 13. A module of function or operation, which may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. The above-mentioned device 1600 may be used to implement the functions of the second communication device in the above-mentioned method embodiment shown in FIG. 13, or the device 1600 may include any one of the functions of the second communication device in the above-mentioned method embodiment shown in FIG. 13. A module of function or operation, which may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. The above-mentioned device 1600 may be used to implement the functions of the second communication device in the above-mentioned method embodiment shown in FIG. 14, or the device 1600 may include any one of the functions of the second communication device in the above-mentioned method embodiment shown in FIG. 14. A module of function or operation, which may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.

For example, when the device 1600 is used to implement the functions of the first communication device in the method embodiment shown in Figure 7, the transceiver unit 1620 can be used to obtain the first data, and the first data is data without integrity protection, The first data is associated with the first MAC PDU and is associated with the first PDCP entity; the processing unit 1610 can be used to satisfy the first condition and discard the first data, where the first condition includes one or more of the following: second data The integrity check fails, the second data is associated with the first MAC PDU, and is associated with the first PDCP entity; the third data integrity check fails, the third data is associated with the first MAC PDU, and Associated with the second PDCP entity; the fourth data integrity check fails, the fourth data is associated with the second MAC PDU, and associated with the first PDCP entity; the fifth data integrity check fails, the fifth data is associated with The second MAC PDU is associated with the second PDCP entity; or, the sixth data integrity check fails, and the sixth data is associated with the second MAC PDU and is associated with the third PDCP entity.

Exemplarily, when the apparatus 1600 is used to implement the functions of the first communication device in the method embodiment shown in Figure 13, the processing unit 1610 can be used to generate seventh indication information, the seventh indication information being used to indicate adjusting the integrity According to the proportion of protected data, the transceiver unit 1620 may be used to send seventh indication information.

For example, when the apparatus 1600 is used to implement the functions of the second communication device in the method embodiment shown in Figure 13, the transceiver unit 1620 can be used to receive the seventh indication information, and the processing unit 1610 can be used to receive the seventh indication information based on the seventh indication information. , adjust the proportion of integrity-protected data.

For example, when the device 1600 is used to implement the functions of the second communication device in the method embodiment shown in Figure 14, the processing unit 1610 can be used to obtain the first resource; and when the fifth condition is met, allocate resources to the first logical channel , the first LCH is associated with a partial guarantee, where the fifth condition includes one or more of the following: remaining resources of the first resource Greater than or equal to the size of the first data set and the size of the MAC subheader; or, the variable corresponding to the first LCH is greater than or equal to the size of the first data set; wherein the first data set includes seventh data, or, the first data The set includes seventh data and a second data set, wherein the seventh data is integrity-protected data, and the second data set includes at least one data, and at least one data is data that is not integrity-protected.

Optionally, the above-mentioned device 1600 can also be used to implement the functions of the terminal device in the above-mentioned method embodiment shown in Figure 15, or the above-mentioned device 1600 can include a function for implementing the terminal device in the above-mentioned method embodiment shown in Figure 15. Any function or operation module that can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. The above-mentioned device 1600 can also be used to implement the functions of the network device in the above-mentioned method embodiment shown in Figure 15, or the above-mentioned device 1600 can be used to implement any function of the network device in the above-mentioned method embodiment shown in Figure 15 or A module of operation, which may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.

More detailed descriptions about the processing unit 1610 and the transceiver unit 1620 can be obtained directly by referring to the relevant descriptions in the method embodiments shown in Figure 7, Figure 13, Figure 14 or Figure 15, and will not be described again here.

It should be understood that the division of units in the embodiment of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods. In addition, each functional unit in various embodiments of the present application may be integrated into one processor, may exist independently, or may have two or more units integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

Figure 17 is another schematic block diagram of a communication device 1700 provided by an embodiment of the present application. The device 1700 may be a chip system, or may be a device configured with a chip system to implement the communication function in the above method embodiment. In the embodiment of the present application, the chip system may be composed of chips, or may include chips and other discrete devices.

As shown in Figure 17, the device 1700 may include a processor 1710 and a communication interface 1720. The communication interface 1720 can be used to communicate with other devices through a transmission medium, so that the device 1700 can communicate with other devices. The communication interface 1720 may be, for example, a transceiver, an interface, a bus, a circuit, or a device capable of implementing transceiver functions. The processor 1710 can use the communication interface 1720 to input and output data, and is used to implement the method described in the corresponding embodiment of FIG. 7, FIG. 13, FIG. 14 or FIG. 15. For example, the device 1700 can be used to implement the functions of the first communication device or the second communication device in the above method embodiment.

When the device 1700 is used to implement the method shown in Figure 7, Figure 13, Figure 14 or Figure 15, the processor 1610 is used to implement the function of the above-mentioned processing unit 1610, and the communication interface 1720 is used to implement the function of the above-mentioned transceiver unit 1620.

Optionally, the apparatus 1700 further includes at least one memory 1730 for storing program instructions and/or data. Memory 1730 and processor 1710 are coupled. The coupling in the embodiment of this application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information interaction between devices, units or modules. Processor 1710 may cooperate with memory 1730. Processor 1710 may execute program instructions stored in memory 1730 . At least one of the at least one memory may be included in the processor.

The embodiment of the present application does not limit the specific connection medium between the processor 1710, the communication interface 1720, and the memory 1730. In the embodiment of the present application, in Figure 17, the processor 1710, the communication interface 1720, and the memory 1730 are connected through a bus 1740. The bus 1740 is represented by a thick line in FIG. 17 , and the connection methods between other components are only schematically illustrated and not limited thereto. The bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one thick line is used in Figure 17, but it does not mean that there is only one bus or one type of bus.

Figure 18 is a schematic structural diagram of a network device provided by an embodiment of the present application, which may be a schematic structural diagram of a base station, for example. As shown in Figure 18, the base station 1800 may include one or more radio frequency units, such as a remote radio unit (remote radio unit). unit (RRU) 1810 and one or more baseband units (BBUs) (also called distributed units (DU)) 1820. The RRU 1810 may be called a transceiver unit, corresponding to the transceiver unit 1620 in Figure 16 . Optionally, the RRU 1810 may also be called a transceiver, a transceiver circuit, a transceiver, or the like, and may include at least one antenna 1811 and a radio frequency unit 1812. Optionally, the RRU 1810 may include a receiving unit and a transmitting unit, the receiving unit may correspond to a receiver (or receiver, receiving circuit), and the transmitting unit may correspond to a transmitter (or transmitter, transmitting circuit). The RRU 1810 part is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals and baseband signals, for example, for sending configuration information to terminal equipment. The BBU 1820 part is mainly used for baseband processing, base station control, etc. The RRU 1810 and the BBU 1820 may be physically installed together or physically separated, that is, a distributed base station.

The BBU 1820 is the control center of the base station and can also be called a processing unit. It can correspond to the processing unit 1610 in Figure 16 and is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, spread spectrum, etc. For example, the BBU (processing unit) can be used to control the base station to execute the operation process related to the network device in the above method embodiment.

In one example, the BBU 1820 may be composed of one or more single boards. Multiple single boards may jointly support a single access standard wireless access network (such as an LTE network), or may support different access standard wireless access networks respectively. Wireless access network (such as LTE network, 5G network or other networks). The BBU 1820 also includes a memory 1821 and a processor 1822. The memory 1821 is used to store necessary instructions and data. The processor 1822 is used to control the base station to perform necessary actions, for example, to control the base station to perform the operation process of the network equipment in the above method embodiment. The memory 1821 and processor 1822 may serve one or more single boards. In other words, the memory and processor can be set independently on each board. It is also possible for multiple boards to share the same memory and processor. In addition, necessary circuits can also be installed on each board.

It should be understood that the base station 1800 shown in Figure 18 can implement the method described in the embodiment shown in Figure 7, Figure 13, Figure 14 or Figure 15. The operations and/or functions of each module in the base station 1800 are respectively intended to implement the corresponding processes in the above method embodiments. For details, please refer to the description in the above method embodiment. To avoid repetition, the detailed description is appropriately omitted here.

Figure 19 is a schematic structural diagram of a terminal device provided by an embodiment of the present application. The terminal device 1900 can be used to implement the method described in the embodiment shown in Figure 7, Figure 13, Figure 14 or Figure 15. The terminal device 1900 can be applied in the communication system 600 shown in Figure 6. As shown in Figure 19, the terminal device 1900 includes a processor 1901 and a transceiver 1902. Optionally, the terminal device 1900 also includes a memory 1903. Among them, the processor 1901, the transceiver 1902 and the memory 1903 can communicate with each other through internal connection channels and transmit control and/or data signals. The memory 1903 is used to store computer programs, and the processor 1901 is used to retrieve data from the memory 1903. The computer program is called and run to control the transceiver 1902 to send and receive signals. Optionally, the terminal device 1900 may also include an antenna 1904 for sending uplink data or uplink control signaling output by the transceiver 1902 through wireless signals. Optionally, the terminal device 1900 also includes a Wi-Fi module 1911 for accessing a wireless network.

The above-mentioned processor 1901 and the memory 1903 can be combined into one processing device, and the processor 1901 is used to execute the program code stored in the memory 1903 to implement the above functions. During specific implementation, the memory 1903 may also be integrated in the processor 1901 or independent of the processor 1901. The processor 1901 may correspond to the processing unit 1610 in FIG. 16 or the processor 1710 in FIG. 17 .

The above-mentioned transceiver 1902 may correspond to the transceiver unit 1620 in FIG. 16 or the communication interface 1720 in FIG. 17 . The transceiver 1902 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Among them, the receiver is used to receive signals, and the transmitter is used to transmit signals.

Optionally, the above terminal device 1900 may also include a power supply 1905, which is used to provide power to various devices or circuits in the terminal device 1900.

In addition, in order to make the functions of the terminal device more complete, the terminal device 1900 may also include one or more of an input unit 1906, a display unit 1907, an audio circuit 1908, a camera 1909, a sensor 1910, etc., the audio The circuitry may also include a speaker 1908a, a microphone 1908b, etc.

It should be understood that the terminal device 1900 shown in Figure 19 can implement various processes involving the terminal device in the method embodiments shown in Figure 7, Figure 13, Figure 14 or Figure 15. The operations and/or functions of each module in the terminal device 1900 are respectively to implement the corresponding processes in the above method embodiment. For details, please refer to the description in the above method embodiment. To avoid repetition, the detailed description is appropriately omitted here.

When the terminal device 1900 is used to perform the operation process involving the terminal device in the above method embodiment, the processor 1901 can be used to perform the actions implemented internally by the terminal device described in the previous method embodiment, and the transceiver 1902 can be used to Execute the actions of the terminal device sending to or receiving from the network device described in the previous method embodiments. For details, please refer to the description in the previous method embodiments and will not be described again here.

This application also provides a computer program product. The computer program product includes: a computer program (which can also be called a code, or an instruction). When the computer program is run, it causes the computer to implement Figures 7, 13, and 14. Or the method described in any one of the embodiments shown in Figure 15.

This application also provides a computer-readable storage medium that stores a computer program (which may also be called a code, or an instruction). When the computer program is run, the computer is caused to implement the method described in any one of the embodiments shown in Figure 7, Figure 13, Figure 14 or Figure 15.

An embodiment of the present application provides a communication system, which includes a first communication device and a second communication device as described above.

It should be understood that the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. During the implementation process, each step of the above method embodiment can be completed through an integrated logic circuit of hardware in the processor or instructions in the form of software. The above-mentioned processor can be a general processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (field programmable gate array, FPGA), or other available processors. Programmed logic devices, discrete gate or transistor logic devices, discrete hardware components. Each method, step and logical block diagram disclosed in the embodiment of this application can be implemented or executed. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field. 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.

It should also be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory may be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static Random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, 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.

The terms "unit", "module", etc. used in this specification may be used to refer to computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. The units and modules in the embodiments of this application have the same meaning and can be used interchangeably.

Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or a combination of computer software and electronic hardware. accomplish. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application. In the several embodiments provided in this application, it should be understood that the disclosed devices, equipment and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

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

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.

In the above embodiments, the functions of each functional unit may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (program) are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVD)), or semiconductor media (e.g., solid state disks (SSD) )wait.

If the functions described are implemented in the form of software functional units and sold or used as independent products, they can be stored on a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the existing technology 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, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk and other media that can store program codes.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application. should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (33)

1. A communication method, characterized in that it is applied to a first communication device, and the method includes:

   Obtain first data, the first data is data without integrity protection, the first data is associated with the first media access control MAC protocol data unit PDU, and is associated with the first packet data convergence protocol PDCP entity couplet;

   If the first condition is met, the first data is discarded. The first condition includes one or more of the following:

   The second data integrity check failed, the second data is associated with the first MAC PDU and is associated with the first PDCP entity;

   The integrity check of the third data failed, and the third data is associated with the first MAC PDU and associated with the second PDCP entity;

   The fourth data integrity check fails, the fourth data is associated with the second MAC PDU and is associated with the first PDCP entity;

   The fifth data integrity check fails, the fifth data is associated with the second MAC PDU and is associated with the second PDCP entity; or,

   The sixth data integrity check fails, and the sixth data is associated with the second MAC PDU and associated with the third PDCP entity.
2. The method of claim 1, wherein: among the first data, the second data, the third data, the fourth data, the fifth data, or the sixth data At least one piece of data is associated with a different MAC PDU.
3. The method according to claim 1 or 2, characterized in that the method further includes:

   One or more of the second data, the third data, the fourth data, the fifth data, or the sixth data are discarded.
4. The method according to any one of claims 1 to 3, characterized in that the method further includes:

   When the second condition is met, the first data is not discarded; wherein,

   The second condition includes one or more of the following:

   The second data integrity check is successful;

   The third data integrity check is successful;

   The fourth data integrity check is successful;

   The fifth data integrity check is successful; or,

   The sixth data integrity check is successful.
5. The method according to any one of claims 1 to 4, characterized in that the method further includes:

   According to first indication information, it is determined that at least one of the first data, the second data, or the third data is associated with the first MAC PDU, and the first indication information is from the third data. The MAC layer of a communications device; and/or,

   Based on second indication information, it is determined that at least one of the fourth data, the fifth data, or the sixth data is associated with the second MAC PDU, the second indication information being from the first The MAC layer of a communication device.
6. The method of claim 5, wherein the first indication information includes number information corresponding to at least one of the first data, the second data, or the third data; and /Or, the second indication information includes data corresponding to at least one of the fourth data, the fifth data, or the sixth data. Number information.
7. The method according to any one of claims 1 to 6, characterized in that the method further includes:

   Based on the third indication information, it is determined that at least one of the first data, the second data, the third data, the fourth data, the fifth data, or the sixth data is different from associated with the MAC PDU, and the third indication information comes from the radio link control RLC layer of the first communication device.
8. The method according to any one of claims 1 to 7, characterized in that the method further includes one or more of the following:

   Determine whether the third data integrity check fails or succeeds based on fourth indication information, the fourth indication information coming from the second PDCP entity;

   Determine that the fifth data integrity check failed or succeeded based on fifth indication information, the fifth indication information coming from the second PDCP entity; or,

   Based on sixth indication information, it is determined that the sixth data integrity check fails or succeeds, and the sixth indication information comes from the third PDCP entity.
9. The method according to any one of claims 1 to 8, characterized in that the method further includes:

   Seventh indication information is sent to the second communication device, where the seventh indication information is used to indicate adjusting the proportion of integrity protected data.
10. The method of claim 9, wherein when a third condition is met, the seventh instruction information indicates increasing the proportion of integrity protected data, wherein the third condition includes one of the following or more than one:

    The number of integrity check failures is greater than or equal to the first threshold; or,

    The number of received MAC PDUs that do not contain integrity-protected data is greater than or equal to the second threshold;

    and / or,

    If the fourth condition is met, the seventh indication information indicates to reduce the proportion of integrity protected data, wherein the fourth condition includes one or more of the following:

    The number of successful integrity checks is greater than or equal to the third threshold;

    The number of received MAC PDUs containing integrity protected data is greater than or equal to the fourth threshold; or,

    The number of received MAC PDUs is greater than or equal to the fifth threshold, wherein the data contained in the received MAC PDUs is integrity protected.
11. The method of claim 10, wherein the number of integrity check failures is determined according to any of the following:

    The number of PDCP PDUs that failed integrity check; or,

    The number of MAC PDUs containing PDCP PDUs that failed integrity check.
12. The method of claim 11, wherein the number of PDCP PDUs that fail the integrity check is associated with one PDCP entity; or,

    The PDCP PDU that fails the integrity check in the number of MAC PDUs containing the PDCP PDU that fails the integrity check is associated with a PDCP entity.
13. The method according to any one of claims 10 to 12, characterized in that the number of successful integrity checks is determined according to any one of the following:

    The number of PDCP PDUs with successful integrity check; or,

    The number of MAC PDUs containing PDCP PDUs with successful integrity check.
14. The method of claim 13, wherein the number of PDCP PDUs with successful integrity verification is associated with one PDCP entity; or,

    The PDCP PDU with successful integrity check among the number of MAC PDUs containing the PDCP PDU with successful integrity check is associated with one PDCP entity.
15. The method according to any one of claims 9 to 14, characterized in that the seventh indication information is associated with a PDCP entity.
16. A communication device, characterized by including:

    A transceiver unit, configured to obtain first data, which is data without integrity protection, where the first data is associated with the first media access control MAC protocol data unit PDU and is associated with the first packet data The convergence protocol PDCP entity is associated;

    A processing unit configured to discard the first data when a first condition is met, where the first condition includes one or more of the following:

    The second data integrity check failed, the second data is associated with the first MAC PDU and is associated with the first PDCP entity;

    The integrity check of the third data failed, and the third data is associated with the first MAC PDU and associated with the second PDCP entity;

    The fourth data integrity check fails, the fourth data is associated with the second MAC PDU and is associated with the first PDCP entity;

    The fifth data integrity check fails, the fifth data is associated with the second MAC PDU and is associated with the second PDCP entity; or,

    The sixth data integrity check fails, and the sixth data is associated with the second MAC PDU and associated with the third PDCP entity.
17. The device of claim 16, wherein: one of the first data, the second data, the third data, the fourth data, the fifth data, or the sixth data At least one piece of data is associated with a different MAC PDU.
18. The device of claim 16 or 17, wherein the processing unit is further configured to discard the second data, the third data, the fourth data, the fifth data, or the One or more items in the sixth data.
19. The device according to any one of claims 16 to 18, wherein the processing unit is further configured not to discard the first data when the second condition is met; wherein,

    The second condition includes one or more of the following:

    The second data integrity check is successful;

    The third data integrity check is successful;

    The fourth data integrity check is successful;

    The fifth data integrity check is successful; or,

    The sixth data integrity check is successful.
20. The device according to any one of claims 16 to 19, wherein the processing unit is further configured to determine the first data, the second data, or the third data according to the first indication information. At least one of the data is associated with the first MAC PDU, and the first indication information comes from the MAC layer of the device; and/or,

    Determine that at least one of the fourth data, the fifth data, or the sixth data is associated with the second MAC PDU based on second indication information, the second indication information coming from the device MAC layer.
21. The device of claim 20, wherein the first indication information includes number information corresponding to at least one of the first data, the second data, or the third data; and /Or, the second indication information includes number information corresponding to at least one of the fourth data, the fifth data, or the sixth data.
22. The device according to any one of claims 16 to 21, wherein the processing unit is further configured to determine the first data, the second data, and the third data based on third indication information. , at least one of the fourth data, the fifth data, or the sixth data is associated with different MAC PDUs, and the third indication information comes from the radio link control RLC layer of the device.
23. The device according to any one of claims 16 to 22, wherein the processing unit is further configured to perform one or more of the following:

    Determine whether the third data integrity check fails or succeeds based on fourth indication information, the fourth indication information coming from the second PDCP entity;

    Determine that the fifth data integrity check failed or succeeded based on fifth indication information, the fifth indication information coming from the second PDCP entity; or,

    Based on sixth indication information, it is determined that the sixth data integrity check fails or succeeds, and the sixth indication information comes from the third PDCP entity.
24. The device according to any one of claims 16 to 23, characterized in that the processing unit is further configured to send seventh indication information, and the seventh indication information is used to indicate adjusting the proportion of integrity protected data.
25. The device according to claim 24, characterized in that:

    If the third condition is met, the seventh indication information indicates increasing the proportion of integrity protected data, wherein the third condition includes one or more of the following:

    The number of integrity check failures is greater than or equal to the first threshold; or,

    The number of received MAC PDUs that do not contain integrity protected data is greater than or equal to the second threshold; and/or,

    If the fourth condition is met, the seventh indication information indicates to reduce the proportion of integrity protected data, wherein the fourth condition includes one or more of the following:

    The number of successful integrity checks is greater than or equal to the third threshold;

    The number of received MAC PDUs containing integrity protected data is greater than or equal to the fourth threshold; or,

    The number of received MAC PDUs is greater than or equal to the fifth threshold, wherein the data contained in the received MAC PDUs is integrity protected.
26. The device of claim 25, wherein the number of integrity check failures is determined according to any one of the following:

    The number of PDCP PDUs that failed integrity check; or,

    The number of MAC PDUs containing PDCP PDUs that failed integrity check.
27. The device of claim 26, wherein the number of PDCP PDUs that fail the integrity check is associated with one PDCP entity; or,

    Among the number of MAC PDUs containing PDCP PDUs that failed the integrity check, the integrity check failed. PDCP PDU is associated with a PDCP entity.
28. The device according to any one of claims 25 to 27, characterized in that the number of successful integrity checks is determined according to any one of the following:

    The number of PDCP PDUs with successful integrity check; or,

    The number of MAC PDUs containing PDCP PDUs with successful integrity check.
29. The device of claim 28, wherein the number of PDCP PDUs with successful integrity verification is associated with one PDCP entity; or,

    The PDCP PDU with successful integrity check among the number of MAC PDUs containing the PDCP PDU with successful integrity check is associated with one PDCP entity.
30. The apparatus according to any one of claims 24 to 29, wherein the seventh indication information is associated with a PDCP entity.
31. A communication device, characterized in that it includes a processor and a memory, the processor is coupled to the memory, and the processor is used to control the device to implement the method according to any one of claims 1 to 15.
32. A computer-readable storage medium, characterized in that a computer program or instructions are stored in the storage medium. When the computer program or instructions are executed by a computer, the implementation of any one of claims 1 to 15 is achieved. method described.
33. A computer program product, characterized in that the computer program product includes instructions, and when the instructions are run by a computer, the method according to any one of claims 1 to 15 is implemented.