CN116801253A

CN116801253A - Communication method and device

Info

Publication number: CN116801253A
Application number: CN202210266127.2A
Authority: CN
Inventors: 刘南南; 李娇娇; 常俊仁; 娄崇; 酉春华
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-03-17
Filing date: 2022-03-17
Publication date: 2023-09-22
Also published as: WO2023174044A1

Abstract

Provided are a communication method and apparatus, the method including: acquiring first data, wherein the first data is data which is not subjected to integrity protection, is associated with a first MAC PDU and is associated with a first PDCP entity; the first condition is satisfied, the first data is discarded, and the first condition includes an integrity check result of data associated with the first data. The integrity check result of the data which is subjected to the integrity protection is used for further determining whether the data which is not subjected to the integrity protection is discarded, and a processing method of the data which is not subjected to the integrity protection is provided. In addition, the method is beneficial to improving the accuracy of data receiving or the accuracy of data submitted to an upper layer, and is also beneficial to improving the communication quality/efficiency. For example, the first data is discarded when the first condition is satisfied, and the first condition is more, that is, the requirement on the reserved data is more strict, so that the accuracy of data receiving or the accuracy of data submitted to an upper layer is improved.

Description

Communication method and device

Technical Field

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

Background

With the rapid development of communication technology, information security problems of mobile communication systems are receiving increasing attention. The integrity protection (integrity protection, IP) function is a function that prevents user data from being tampered with. The integrity protection function includes integrity protection as well as integrity verification, and is generally performed by a packet data convergence protocol (packet data convergence protocol, PDCP) layer. For example, the sender performs integrity protection on the header (header) and the data portion of the PDCP protocol data unit (protocol data unit, PDU), and the receiver performs integrity check on the PDCP PDU.

Currently, for each Radio Bearer (RB), if the RB is configured with an integrity protection function, all data (data) (e.g., all PDCP data PDUs) on the RB are integrity protected so that the receiving end performs integrity checking on the RB and discards the RB if the checking fails. In some cases, only a portion of the data (e.g., a portion of PDCP data PDU) on the RB may be integrity protected (hereinafter referred to as a partial full protection).

Note that "all data on RB" does not include PDCP control PDU.

Therefore, how to process data that is not integrity protected is a technical problem that needs to be solved under the condition of partial protection.

Disclosure of Invention

The application provides a communication method and a communication device, which are convenient for processing data which are not subjected to integrity protection under the condition of partial protection.

In a first aspect, the present application provides a communication method, which may be performed by a first communication device, or may also be performed by a component (such as a chip, a system on a chip, etc.) configured in the first communication device, or may also be implemented by a logic module or software capable of implementing all or part of the functions of the first communication device, which is not limited in this aspect.

Illustratively, the method includes: acquiring first data, the first data being data that is not integrity protected, the first data being associated with a first media access control (medium access control, MAC) PDU and with a first PDCP entity; the first condition is satisfied, the first data is discarded, the first condition includes one or more of: the second data integrity check fails, the second data being associated with the first MAC PDU and with the first PDCP entity; the third data integrity check fails, the third data being associated with the first MAC PDU and with the second PDCP entity; a fourth data integrity check failure, the fourth data associated with the second MAC PDU and with the first PDCP entity; the fifth data integrity check fails, the fifth data being associated with a second MAC PDU and with a second PDCP entity; alternatively, the sixth data integrity check fails, the sixth data is associated with the second MAC PDU and with the third PDCP entity.

Based on the above technical solution, after the first communication device obtains the data (i.e., the first data) which is not integrity protected, the first data may be discarded if the data associated with the first communication device fails to perform integrity protection, where the data associated with the first communication device fails to perform integrity protection may be a second data integrity verification, where the second data and the first data are associated with the same MAC PDU and are associated with the same PDCP entity; alternatively, it may be that the third data integrity check fails, the third data and the first data being associated with the same MAC PDU and being associated with different PDCP entities; alternatively, the fourth data integrity check may fail, the fourth data and the first data being associated with different MAC PDUs and being associated with the same PDCP entity; alternatively, it may be that the fifth data integrity check fails, the fifth data and the first data are associated with different MAC PDUs and with different PDCP entities, but the fifth data and the third data are associated with the same PDCP entity; alternatively, the sixth data may fail the integrity check, the sixth data and the first data may be associated with different MAC PDUs and different PDCP entities, and the sixth data and the third data may be associated with different PDCP entities. Based on the checking result of the data subjected to the integrity protection, whether the data which is not subjected to the integrity protection is discarded or not is further determined, and a processing method of the data which is not subjected to the integrity protection is provided for the first communication equipment. In addition, the method is beneficial to improving the accuracy of data receiving or the accuracy of data submitted to an upper layer, and is also beneficial to improving the communication quality/efficiency. For example, there are many cases where data not subjected to integrity protection is discarded, in other words, conditions for delivering data not subjected to integrity protection to an upper layer are strict, so that it is advantageous to improve accuracy of data reception or accuracy of data delivered to the upper layer.

With reference to the first aspect, in certain 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 associated with a different MAC PDU.

The first communication device considers the case where at least one data in the MAC PDU is segmented data before performing the integrity check. In other words, the second communication device transmits via a different MAC PDU after segmenting a certain data. In the case of such presence segmentation, 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 a different MAC PDU. 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 associated with the first MAC PDU and the second MAC PDU.

With reference to the first aspect, in certain possible implementation manners of the first aspect, the method further includes: one or more of the second data, the third data, the fourth data, the fifth data, or the sixth data is discarded.

One possible implementation is that if a certain data integrity check in the data associated with the same MAC PDU fails, all the data in the MAC PDU may be discarded, thereby facilitating an improvement in the accuracy of data reception or the accuracy of data submitted to an upper layer. The first communication device may also discard the second data and the third data, for example, in case the second data integrity check fails and/or the third data integrity check fails; in case the fourth data integrity check fails, the fourth data, the fifth data and the sixth data may also be discarded; likewise, in case the fifth data and/or the sixth data fails the integrity check, the fourth data, the fifth data and the sixth data may also be discarded.

Another possible implementation manner is that, when integrity check of a certain data in the data associated with the same MAC PDU fails, the data with failed integrity check and the data without integrity protection in the MAC PDU can be discarded, which is beneficial to reducing the possibility of tampering the data without integrity protection, thereby being beneficial to improving the accuracy of data reception or the accuracy of data submitted to an upper layer.

With reference to the first aspect, in certain possible implementation manners of the first aspect, the method further includes: in the case that the second condition is satisfied, the first data is not discarded; wherein the second condition comprises one or more of: 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; alternatively, the sixth data integrity check is successful.

With reference to the first aspect, in certain possible implementation manners of the first aspect, the method further includes: determining that at least one of the first data, the second data, or the third data is associated with the first MAC PDU according to the first indication information; and/or, based on the second indication information, determining that at least one of the fourth data, the fifth data, or the sixth data is associated with the second MAC PDU.

It may be appreciated that when the first communication device acquires a plurality of MAC PDUs, it is required to determine which data are associated with the same MAC PDU, so as to determine whether to discard data that is not integrity protected based on a verification result of integrity protected data in the data associated with the same MAC PDU, which is beneficial to improving accuracy of data reception or accuracy of data submitted to an upper layer. One possible implementation manner is that the first communication device determines that at least one data of the first data, the second data and the third data is associated with the first MAC PDU according to the first indication information; and/or determining 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, wherein the first indication information and the second indication information may be received separately or together. The first indication information and the second indication information may be received simultaneously or may not be received simultaneously.

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

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

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

With reference to the first aspect, in some possible implementation manners of the first aspect, the first indication information includes numbering information corresponding to at least one of the first data, the second data, or the third data; and/or the second indication information comprises number information corresponding to at least one of fourth data, fifth data or sixth data.

The number information may be a custom number, and the data associated with the same MAC PDU will obtain the same number, for example, the data associated with the first MAC PDU will obtain the same number, and the data associated with the second MAC PDU will obtain a number different from the first MAC PDU. In addition, the number information may be a PDCP sequence number indicated by the MAC layer in the first communication device to the PDCP layer directly, or an RLC sequence number indicated by the MAC layer in the first communication device to the RLC layer, and further, a PDCP sequence number indicated by the RLC layer to the PDCP layer. The first communication device is advantageously configured to determine data associated with the same MAC PDU based on the indication information by giving an indication of the first indication information and the second indication information.

With reference to the first aspect, in certain possible implementation manners of the first aspect, 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 associated with a different MAC PDU.

In the case that there is a segment in the data in the plurality of MAC PDUs acquired by the first communication device, it may be 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 associated with a different MAC PDU, 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 associated with the first MAC PDU and the second MAC PDU, which is further advantageous for further determining the integrity check result of at least one of the first data to the sixth data.

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

With reference to the first aspect, in certain possible implementation manners of the first aspect, the method further includes one or more of: determining that the third data integrity check fails or succeeds based on the fourth indication information; determining that the fifth data integrity check fails or succeeds based on the fifth indication information; or, based on the sixth indication information, determining that the sixth data integrity check fails or succeeds.

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

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

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

When the data in the MAC PDU acquired by the first communication device is associated with different PDCP entities, the integrity check result of the data associated with the different PDCP entities may be obtained based on the indication information from the different PDCP entities, so as to facilitate processing of the data that is not integrity protected. For example, a third data integrity check failure is determined based on fourth indication information from the second PDCP entity.

In a second aspect, the present application provides a communication method, which may be performed by the first communication device, or may also be performed by a component (such as a chip, a system on a chip, etc.) configured in the first communication device, or may also be implemented by a logic module or software capable of implementing all or part of the functions of the first communication device, which is not limited in this aspect.

Illustratively, the method includes: generating seventh indication information for indicating a proportion of data for adjusting the integrity protection; and transmitting seventh indication information to the second communication device.

Based on the above technical solution, the first communication device may generate and send seventh indication information to the second communication device to indicate the second communication device to adjust the proportion of the integrity protected data, where the adjustment may be to adjust the proportion of the integrity protected data up or down, or to turn on or off the partial full protection function. The first communication device sends the seventh indication information, which is beneficial for the second communication device to reasonably adjust the proportion of the integrity-protected data based on the seventh indication information.

In a third aspect, the present application provides a communication method, which may be performed by the second communication device, or may be performed by a component (such as a chip, a system on a chip, etc.) configured in the second communication device, or may be implemented by a logic module or software capable of implementing all or part of the functions of the second communication device, which is not limited in this aspect.

Illustratively, the method includes: receiving seventh indication information, wherein the seventh indication information is used for indicating the proportion of the data for adjusting the integrity protection; based on the seventh indication information, the proportion of the integrity-protected data is adjusted.

Based on the above technical solution, the second communication device may receive the seventh indication information, so as to adjust the proportion of the integrity protected data based on the seventh indication information, where the adjustment may be to adjust the proportion of the integrity protected data up or down, or to turn on or off the partial full protection function. The second communication device adjusts the proportion of the integrity-protected data according to the seventh indication information, which is beneficial to improving the rationality of the proportion of the integrity-protected data in the second communication device.

With reference to the second aspect or the third aspect, in some possible implementations, the seventh indication information indicates that the proportion of the integrity-protected data is to be turned up if a third condition is satisfied, where the third condition includes one or more of: the number of failed integrity checks is greater than or equal to a first threshold; or, the number of received MAC PDUs that do not contain integrity-protected data is greater than or equal to a second threshold; and/or, in case the fourth condition is met, the seventh indication information indicates a proportion of the data of the reduced integrity protection, wherein the fourth condition comprises one or more of: the number of times of successful integrity check is greater than or equal to a third threshold; the number of received MAC PDUs containing integrity-protected data is greater than or equal to a fourth threshold; or, the number of the received MAC PDUs is greater than or equal to the fifth threshold, where the received MAC PDUs include data that is integrity protected.

In the above technical solution, a possible condition that the seventh indication information indicates to increase the proportion of the integrity protected data is given, and/or a possible condition that the seventh indication information indicates to decrease the proportion of the integrity protected data is given, so that the first communication device may send different indication information to the second communication device under different conditions, so that the second communication device adjusts the proportion of the integrity protected data, which is beneficial to improving the rationality of the second communication device adjusting the proportion of the integrity protected data.

With reference to the second aspect or the third aspect, in some possible implementations, the number of failed integrity checks is determined according to any one of the following: the number of PDCP PDUs failing the integrity check; or, the number of MAC PDUs including PDCP PDUs for which the integrity check fails.

The number of failed integrity check PDCP PDUs may be determined according to the number of failed integrity check PDCP PDUs, which is granularity for the first communication device, e.g., the first communication device may maintain a counter, and the number of failed integrity check PDCP PDUs is increased by 1, and the number of failed integrity check indicated by the counter is increased by 1. The number of integrity check failures may also be determined according to the number of MAC PDUs including PDCP PDUs for which the integrity check fails, where the number of MAC PDUs is granularity for the first communication device, e.g. the first communication device may maintain a counter, the number of MAC PDUs including PDCP PDUs for which the integrity check fails is increased by 1, the number of integrity check failures indicated by the counter is increased by 1, wherein for a certain MAC PDU, if the number of PDCP PDUs for which the integrity check fails in the MAC PDU is 2, the counter is increased by 1.

With reference to the second aspect or the third aspect, in some possible implementations, the number of PDCP PDUs for which the integrity check fails is associated with one PDCP entity; alternatively, the PDCP PDU for which the integrity check fails from among the number of MAC PDUs including the PDCP PDU for which the integrity check fails is associated with one PDCP entity.

The number of PDCP PDUs for which the integrity check fails is associated with one PDCP entity, indicating that the number of PDCP PDUs for which the integrity check fails is granularity for one PDCP entity. For example, each PDCP entity maintains a counter, and when the number of PDCP PDUs for which the integrity check associated with the PDCP entity fails increases by 1, the number of integrity check failures indicated by the counter corresponding to the PDCP entity increases by 1. Likewise, the PDCP PDUs for which the integrity check fails, among the number of MAC PDUs containing the PDCP PDUs for which the integrity check fails, are associated with one PDCP entity, are also granularity for one PDCP entity. For example, each PDCP entity maintains a counter, and if the number of PDCP PDUs for which the integrity check fails in a MAC PDU is 2 and the two PDCP PDUs are associated with different PDCP entities, the counter corresponding to each PDCP entity is incremented by 1.

With reference to the second aspect or the third aspect, in some possible implementations, the number of successful integrity checks is determined according to any one of the following: the number of PDCP PDUs for which the integrity check is successful; or, the number of MAC PDUs including PDCP PDUs for which the integrity check was successful.

With reference to the second aspect or the third aspect, in some possible implementations, the number of PDCP PDUs for which the integrity check is successful is associated with one PDCP entity; alternatively, the successfully-checked PDCP PDUs of the number of MAC PDUs including the successfully-checked PDCP PDUs are associated with one PDCP entity.

With reference to the second aspect or the third aspect, in some possible implementations, the seventh indication information is associated with one PDCP entity.

Wherein the seventh indication information is associated with one PDCP entity, which means that the seventh indication information is specific to a granularity of a PDCP entity, in other words, the seventh indication information may indicate to adjust a proportion of integrity-protected data in data associated with the PDCP entity, so as to facilitate the second communication device to reasonably adjust the proportion of the integrity-protected data in the PDCP entity.

In a fourth aspect, the present application provides a communication method, which may be performed by the second communication device, or may also be performed by a component (such as a chip, a system on a chip, etc.) configured in the second communication device, or may also be implemented by a logic module or software capable of implementing all or part of the functions of the second communication device, which is not limited in this aspect.

Illustratively, the method includes: acquiring a first resource; a fifth condition is met, allocating resources for a first Logical Channel (LCH) associated with partial full protection, wherein the fifth condition comprises one or more of: 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 data set comprises seventh data, or the first data set comprises seventh data and second data set, wherein the seventh data is integrity protected data and the second data set comprises at least one data, and the at least one data is not integrity protected data.

Based on the above technical solution, the second communication device allocates resources for the first LCH associated with the partial full protection 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 when the variable corresponding to the first LCH is greater than or equal to the size of the first data set, where the association of the first LCH with the partial full protection means that the PDCP entity corresponding to the first LCH is configured with the partial full protection, so that it can be ensured that each PDCP entity in the MAC PDU contains at least one data for integrity protection, and that the MAC PDU contains at least one data for integrity protection, which is beneficial to reducing the possibility of tampering of the data, thereby being beneficial to improving the security of the data.

With reference to the fourth aspect, in some possible implementations of the fourth aspect, the second data set includes all data preceding the seventh data; alternatively, the second data set includes all data between the seventh data and the eighth data, wherein the eighth data is integrity-protected data.

All data preceding the seventh data refer to all data preceding the seventh data among the data issued by the RLC layer. A possible situation is that the second data set includes all data before the seventh data, in other words, there may be one or more data before the seventh data that is not integrity protected, and there may be no other data after the seventh data that is integrity protected or not, i.e. during the MAC multiplexing, for the first LCH, if the variable Bj maintained by the first LCH 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), it is multiplexed in the MAC PDU, so that it may be ensured that each PDCP entity in the MAC PDU contains at least one integrity protected data. Another possibility is that the second data set includes all data between the seventh data and the eighth data, in other words, in the MAC multiplexing process, if Bj is greater than or equal to the first integrity-protected data (i.e. the seventh data) and the data between the first integrity-protected data and the second integrity-protected data (i.e. the second data set), the first data set and the second data set are multiplexed in the MAC PDU, so that it can be ensured that each PDCP entity in the MAC PDU contains at least one integrity-protected data.

With reference to the fourth aspect, in some possible implementations of the fourth aspect, the eighth data is data that is integrity-protected after the seventh data.

That is, 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, so that it can be ensured that the first data for each PDCP entity in the MAC PDU is the integrity-protected data after MAC multiplexing.

With reference to 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 data that is integrity-protected one before the seventh data.

That is, the seventh data may further include integrity-protected data (e.g., ninth data), and the remaining resources of the first resource need to accommodate the following data: the seventh data, the eighth data, and the data between the seventh data, so that it can be ensured that at least one integrity-protected data is included for each PDCP entity in the MAC PDU.

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

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

In a fifth aspect, the present application provides a communication method, which may be performed by a terminal device, or may also be performed by a component (such as a chip, a chip system, etc.) configured in the terminal device, or may also be implemented by a logic module or software capable of implementing all or part of the functions of the terminal device, which is not limited in this aspect.

Illustratively, 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 may be used to indicate RLM measurement relaxation rules and the BFD measurement relaxation configuration information may be used to indicate BFD measurement relaxation rules; RLM measurement relaxation rules and/or BFD measurement relaxation rules are determined. Relaxing RLM measurements and/or BFD measurements, or determining relaxing or not relaxing RLM measurements and/or BFD measurements based on the indication information.

In the application, the terminal equipment determines the RLM/BFD measurement relaxation rule according to the configuration of the network equipment, and automatically performs measurement relaxation (after meeting the RLM/BFD measurement relaxation criterion), or determines whether to perform measurement relaxation according to the indication information of the network equipment, so that the network equipment can adjust the strategy of the terminal equipment for relaxing the RLM measurement and/or BFD measurement according to the condition of the terminal equipment, thereby reducing the probability of failure of the terminal equipment during relaxation measurement as much as possible. For example, in the case that the service area signal quality of the terminal device is not good enough or the terminal device has a service with a higher service quality requirement, the network device may configure the terminal device to determine whether to perform measurement relaxation according to the indication of the network setting, but not to perform measurement relaxation by itself, so that the network device controls the measurement behavior of the terminal device, thereby avoiding adverse effects caused by autonomous measurement relaxation of the terminal device.

In one possible design, determining the RLM measurement relaxation rule and/or the BFD measurement relaxation rule may be that the terminal device determines (after meeting the RLM/BFD measurement relaxation criterion) whether measurement relaxation is possible or that the terminal device determines (after meeting the RLM/BFD measurement relaxation criterion) whether measurement relaxation is possible based on indication information of the network device.

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

In a sixth aspect, the present application provides a communication device, which may implement the communication method in any one of the possible implementation manners of the first aspect and the first aspect, or may implement the communication method in any one of the possible implementation manners of the second aspect and the second aspect. The apparatus comprises corresponding means for performing the above-described method. The units comprised by the device may be implemented in software and/or hardware.

In a seventh aspect, the present application provides a communication device, which may implement the communication method in any one of the possible implementation manners of the third aspect and the third aspect, or may implement the communication method in any one of the possible implementation manners of the fourth aspect and the fourth aspect. The apparatus comprises corresponding means for performing the above-described method. The units comprised by the device may be implemented in software and/or hardware.

In an eighth aspect, the present application provides a communications apparatus comprising a processor. The processor is coupled to the memory and operable to execute a computer program in the memory to implement the communication method of any one of the possible implementations of the first aspect and the first aspect, or to implement the communication method of any one of the possible implementations of the second aspect and the second aspect.

In a ninth aspect, the present application provides a communications apparatus comprising a processor. The processor is coupled to the memory and operable to execute a computer program in the memory to implement the communication method in any one of the possible implementations of the third aspect and the third aspect, or to implement the communication method in any one of the possible implementations of the fourth aspect and the fourth aspect.

In a tenth aspect, the present application provides a communication apparatus, which can implement the communication method described in the fifth aspect. The apparatus comprises corresponding means for performing the above-described method. The units comprised by the device may be implemented in software and/or hardware.

In an eleventh aspect, the present application provides a communication device comprising a processor. The processor is coupled to the memory and is operable to execute the computer program in the memory to implement the communication method of the fifth aspect.

In a twelfth aspect, the present application provides a computer readable storage medium having stored therein a computer program or instructions which, when executed, implement the communication method in any one of the possible implementations of the first aspect and the first aspect, or implement the communication method in any one of the possible implementations of the second aspect and the second aspect, or implement the communication method in any one of the possible implementations of the third aspect and the third aspect, or implement the communication method in any one of the possible implementations of the fourth aspect and the fourth aspect, or implement the communication method in any one of the possible implementations of the fifth aspect.

In a thirteenth aspect, the present application provides a computer program product comprising instructions which, when executed, implement the communication method of any one of the possible implementations of the first aspect and the first aspect, or the communication method of any one of the possible implementations of the second aspect and the second aspect, or the communication method of any one of the possible implementations of the third aspect and the third aspect, or the communication method of any one of the possible implementations of the fourth aspect and the fourth aspect, or the communication method of the fifth aspect.

In a fourteenth aspect, the present application provides a chip system, which includes a processor, and may further include a memory, for implementing the communication method in any one of the possible implementations of the first aspect and the first aspect, or implementing the communication method in any one of the possible implementations of the second aspect and the second aspect, or implementing the communication method in any one of the possible implementations of the third aspect and the third aspect, or implementing the communication method in any one of the possible implementations of the fourth aspect and the fourth aspect, or implementing the communication method in any one of the possible implementations of the fifth aspect. The chip system may be formed of a chip or may include a chip and other discrete devices.

In a fifteenth aspect, an embodiment of the present application provides a communication system, which includes the communication apparatus of the sixth aspect or the eighth aspect, and the communication apparatus of the seventh aspect or the ninth aspect.

Drawings

Fig. 1 is a schematic structural diagram of a protocol stack according to an embodiment of the present application;

fig. 2 is a schematic diagram of a data PDU structure according to an embodiment of the present application;

fig. 3 is a schematic diagram of a relationship between PDUs and service data units (service data unit, SDUs) of each protocol layer provided by an embodiment of the present application;

fig. 4 is a schematic diagram of a relationship between PDCP PDUs and PDCP SDUs provided by an embodiment of the present application;

FIG. 5 is a schematic illustration of a partial end of life provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of a system architecture suitable for use in the method provided by embodiments of the present application;

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

fig. 8 to 12 are schematic diagrams of several MAC PDUs provided by embodiments of the present application;

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

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

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

Fig. 16 to 19 are schematic structural diagrams of possible communication devices according to an embodiment of the present application.

Detailed Description

The technical scheme of the application will be described below with reference to the accompanying drawings.

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

first, in order to clearly describe the technical solution of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", etc. are used to distinguish identical items or similar items having substantially identical functions and actions. For example, the first indication information and the second indication information are merely for distinguishing different indication information, and the order of the different indication information is not limited. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ.

Second, in the embodiment of the present application, "and/or" describes the association relationship of the association object, which means that three relationships may exist, for example, a and/or B may mean: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the front-to-rear associated object is an "or" relationship, but does not exclude the case where the front-to-rear associated object is an "and" relationship, and the meaning of the specific representation may be understood in conjunction with the context. "the following item(s)" or "items(s)" or the like, refer to any combination of these item(s), including any combination of single item(s) or plural item(s). For example, one or more of a, b, or c(s) may represent: a, b, c; a and b; a and c; b and c; or a and b and c. Wherein a, b and c can be single or multiple.

In the present application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

The technical scheme provided by the application can be applied to various communication systems, such as: global system for mobile communications (global system for mobile communications, GSM), code division multiple access (code division multiple access, CDMA) system, wideband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (general packet radio service, GPRS), wireless local area network (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 (time division duplex, TDD), side-chain (sidelink) communication system, general mobile communication system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX) communication system, fifth generation (5th generation,5G) mobile communication system, or new wireless access technology (new radio access technology, NR). The 5G mobile communication system may include a non-independent Networking (NSA) and/or an independent networking (SA), among others.

The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation (6th Generation,6G) mobile communication system and the like. The application is not limited in this regard.

In the 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 may be any device having a wireless transceiver function. Network devices include, but are not limited to: an evolved Node B (eNB), a radio network controller (radio network controller, RNC), a Node B (Node B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (home evolved Node B, or home Node B, HNB, for example), a Base Band Unit (BBU), an Access Point (AP) in a Wi-Fi (wireless fidelity, wi-Fi) system, a radio relay Node, a radio backhaul Node, a transmission point (transmission point, TP), or a transmission reception point (transmission and reception point, TRP), etc., may also be a gNB or a transmission point (TRP or TP) in a 5G (such as NR) system, or one or a group (including a plurality of antenna panels) of base stations in a 5G system, or may also be a network Node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a Distributed Unit (DU), etc.

In some deployments, the gNB may include a Centralized Unit (CU) and DUs. Illustratively, a CU implements part of the functionality of the gNB, and a DU implements part of the functionality of the gNB, e.g., the CU is responsible for handling non-real time protocols and services, implementing radio resource control (radio resource control, RRC), packet data convergence layer protocol (packet data convergence protocol, PDCP) layer functions; the DUs may include functions of a radio link control (radio link control, RLC) layer, functions of a medium access control (media access control, MAC) layer, and partial functions of a Physical (PHY) layer.

Illustratively, the DU may include functionality of higher layers in the PHY layer. Among other things, the functions of the higher layers in the PHY layer may include cyclic redundancy check (cyclic redundancy check, CRC) functions, channel coding, rate matching, scrambling, modulation, and layer mapping; alternatively, the functions of higher layers in the PHY layer may include cyclic redundancy check, channel coding, rate matching, scrambling, modulation, layer mapping, and precoding. The functions of the lower layer in the PHY layer may be implemented by another network entity independent of the DUs, where the functions of the lower layer in the PHY layer may include precoding, resource mapping, physical antenna mapping, and radio frequency functions; alternatively, the functions of lower layers in the PHY layer may include resource mapping, physical antenna mapping, and radio frequency functions. The embodiment of the application does not limit the functional division of the upper layer and the bottom layer in the PHY layer. When the functions of the lower layers in the PHY layer can be implemented in another network entity independent of the DU, the DU transmits data or information to other communication devices (e.g., terminal equipment, core network equipment), it can be understood that: the DU performs functions of the RLC layer, the MAC layer, and part of functions of the PHY layer. For example, after the functions of the RLC layer and the MAC layer are completed, and cyclic redundancy check, channel coding, rate matching, scrambling, modulation, layer mapping, the remaining functions of mapping and transmitting on physical resources are performed by the network entity independent of the DUs, which performs the functions of the lower layer in the PHY layer.

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

In the embodiment of the present application, the terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment.

The terminal device may be a device providing voice/data connectivity to a user, e.g., a handheld device with wireless connectivity, an in-vehicle device, etc. Currently, some examples of terminal devices may be: a mobile phone (mobile phone), a tablet (pad), a computer with wireless transceiver function (e.g., a notebook, a palm, etc.), a mobile internet device (mobile internet device, MID), a Virtual Reality (VR) device, an augmented reality (augmented reality, AR) device, a wireless terminal in an industrial control (industrial control), a wireless terminal in an unmanned (self-driving) device, an unmanned aerial vehicle, a wireless terminal in a remote medical (remote medium), a wireless terminal in a smart grid (smart grid), a wireless terminal in a transportation security (transportation safety), a wireless terminal in a smart city (smart city), a wireless terminal in a smart home (smart home), a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a wireless terminal in a vehicle-mounted device, a future evolution land-based terminal (PLMN) device, a mobile terminal in a mobile phone (35G) or a future-developed network (public land mobile network) device, etc.

The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wearing and developing wearable devices by applying a wearable technology, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

Furthermore, the terminal device may also be a terminal device in an internet of things (internet of things, ioT) system. IoT is an important component of future information technology development, and its main technical feature is to connect an item with a network through a communication technology, so as to implement man-machine interconnection and an intelligent network for object interconnection. IoT technology may enable massive connectivity, deep coverage, and terminal power saving through, for example, narrowband (NB) technology.

In addition, the terminal device may further include sensors such as an intelligent printer, a train detector, and a gas station, and the main functions include collecting data (part of the terminal device), receiving control information and downlink data of the network device, and transmitting electromagnetic waves to transmit uplink data to the network device.

It should be understood that the present application is not limited to any particular form of network device or terminal device.

In order to better understand the communication method provided by the embodiment of the present application, the terms related in the present application will be briefly described first.

1. NR protocol architecture: the user plane protocol stack and the control plane protocol stack can be classified according to purposes. The two protocol stacks described above will be described in detail below in connection with fig. 1. A) in fig. 1 shows a user plane protocol stack and b) in fig. 1 shows a control plane protocol stack. As shown in a) of fig. 1, the user plane protocol stack mainly includes five layers of PHY layer, MAC layer, RLC layer, PDCP layer, and service data adaptation protocol (service data adaptation protocol, SDAP) layer. The PHY layer may be responsible for processing one or more of coding, modulation and demodulation, multi-antenna mapping, and other physical layer functions, among others. The MAC layer is responsible for handling one or more of hybrid automatic repeat request (hybrid automatic repeat request, HARQ) retransmissions and uplink and downlink scheduling. The RLC layer may be responsible for segmentation, reassembly, and retransmission processes. The PDCP layer may be responsible for performing one or more of header compression, security (ciphering, integrity protection), retransmission, sequential transmission of higher layer data, and the like.

As shown in b) of fig. 1, the control plane protocol stack mainly includes non-access stratum (NAS), RRC, PDCP, RLC, MAC, PHY layers. Wherein the PDCP layer provides ciphering and integrity protection functions, and the functions performed by control planes in the RLC layer and the MAC layer coincide with the user plane. The RRC layer is mainly responsible for functions such as broadcasting, paging, RRC connection management, radio bearer control, mobility management, measurement reporting and control of terminal equipment, and the like. The NAS layer handles the transfer of information between the terminal device and the access and mobility management function (access and mobility management function, AMF) entities, the transferred content may be user information or control information, for example, the transferred content includes session management, user management, security management, etc. It should be appreciated that for the user plane protocol stack, the NR protocol stack is more SDAP layer than the LTE protocol stack, and for the control plane protocol stack, the NR protocol stack is similar to the LTE protocol stack.

2. Integrity protection: the integrity of data is one of three basic points of information security, namely ensuring that the data is not tampered or can be quickly found after tampering in the process of transmission or storage. The integrity protection function includes integrity protection and integrity check for preventing data from being tampered with, and is performed at the PDCP layer. Wherein the PDCP layer of the transmitting side 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, and the PDCP layer of the receiving side performs integrity check according to the MAC-I. The integrity-protected data unit is the PDU header and the data portion of the PDU prior to ciphering. Integrity protection may be applied to PDCP data PDUs of a signaling radio bearer (signalling radio bearer, SRB) (SRB carrying control plane data) carrying control plane data. Integrity protection may also be applied to PDCP data PDUs of a data radio bearer (data radio bearer, DRB) (DRB carrying user plane data) carrying user plane data that is configured with the integrity protection. Wherein the data PDU is used to convey data of the user plane and the control plane and the MAC-I generated by the integrity protection.

Fig. 2 shows two examples of data PDUs, a) in fig. 2 shows a format of PDCP data PDUs corresponding to SRBs, and b) in fig. 2 shows a format of PDCP data PDUs corresponding to DRBs. The formats of the above two PDCP data PDUs will be described in detail with reference to fig. 2.

As shown in a) of fig. 2, the PDCP Data PDU corresponding to the SRB includes an R field, a PDCP Sequence Number (SN), data (Data), and a MAC-I. Where R represents reserved bits, for example, 4 reserved bits may be included. In addition, the length of PDCP SN is 12 bits.

As shown in b) of fig. 2, the PDCP Data PDU corresponding to the DRB includes D/C field, R field, PDCP SN, data, and MAC-I. Wherein the D/C field is used to identify the type of PDU, e.g., D/C field 0 represents a control PDU and D/C field 1 represents a data PDU. R represents a reserved bit. In addition, the PDCP SN may have a length of 12 bits. In other embodiments, the PDCP SN may also have a length of 18 bits, which is not limited in this embodiment of the present application.

Note that "MAC-I (continuous)" in fig. 2 indicates that the MAC-I may occupy a plurality of lines. "PDCP SN (continue)" means that PDCP SN may occupy a plurality of lines.

3. PDU and SDU: the SDUs of the N layer and the PDUs of the upper layer are in one-to-one correspondence. In other words, the PDU of the present layer is the SDU of the lower layer, and the SDU of the present layer is the PDU of the upper layer.

The relationship of the PDU and the SDU will be described in detail below in connection with fig. 3 and 4.

Fig. 3 is a schematic diagram of a relationship between PDU and SDU of each protocol layer according to an embodiment of the present application. As shown in fig. 3, for the access network device, after the RRC layer generates signaling (e.g., RRC message or RRC PDU) to be transmitted, it may be submitted to the corresponding PDCP entity, and for convenience of description, we will hereinafter refer to/replace the signaling with data; for data (e.g., PDCP SDUs) received from the RRC layer, the PDCP entity may or may not obtain PDCP PDUs after a certain processing, and then deliver the PDCP PDUs to the RLC entity corresponding to the PDCP entity; for data (e.g., RLC SDUs) received from the PDCP layer, the RLC entity may or may not obtain RLC PDUs with some processing, and then submit the RLC PDUs to the corresponding MAC entities; for data received from the RLC layer (e.g., MAC SDUs), the MAC entity may or may not have some processing to obtain MAC PDUs, and then deliver the MAC PDUs to the PHY layer; the PHY layer performs air interface transmission.

Accordingly, for the terminal device, after the PHY layer receives data (e.g., transport Block (TB)), the TB is submitted to the MAC layer; for data (e.g., TB or MAC PDU) received from PHY, the MAC entity may or may not process to obtain a MAC SDU, which is then delivered to the corresponding RLC layer; for data (e.g., RLC PDU) received from the MAC layer, the RLC entity may or may not obtain RLC SDU with a certain process, and then deliver the RLC SDU to the corresponding PDCP entity; for data (e.g., PDCP PDUs) received from the RLC layer, the PDCP entity may or may not receive PDCP SDUs with some processing, and then deliver the PDCP SDUs to the RRC layer; for data (e.g., RRC message or RRC PDU) received from the PDCP layer, which may also be referred to as signaling, the RRC layer performs RRC decoding or asn.1 decoding to determine the meaning of the received data.

For the transmission and reception of data (or signaling), the data may be encapsulated/processed correspondingly in the respective layers or may be transparent. For example, for the transmitting end, data received from an upper layer of the layer is called SDU, data submitted to a lower layer by the layer is called PDU, and for the layer, data received from the upper layer and data submitted to the lower layer may be the same (e.g., transparent) or different (e.g., data received from the upper layer is encapsulated/processed by the layer to obtain data submitted to the lower layer). For example, data received by the PDCP entity from the upper layer is called PDCP SDU, and data transmitted by the PDCP entity to the lower layer is called PDCP PDU; data received by the RLC entity from the upper layer is called RLC SDU, and data transmitted 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 a MAC SDU, and the data transmitted by the MAC entity to the lower layer is called a MAC PDU. For example, for reception, data received by a layer from a lower layer of the layer is referred to as a PDU, data submitted by the layer to an upper layer is referred to as an SDU, and for the layer, data received by the layer from the lower layer and data submitted to the upper layer may be the same (e.g., transparent) or different (e.g., data received from the lower layer is processed by the layer to obtain data submitted to the upper layer). For example, data received by the PDCP entity from the lower layer is called PDCP PDU, and data transmitted 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 transmitted 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 transmitted by the MAC entity to the upper layer is called MAC SDU.

The upper layer and the lower layer in the embodiment of the present application are a relative concept, for example, the RLC layer is taken as an example, and the RLC layer may be a lower layer of the RRC layer for the RRC layer, but may be an upper layer of the MAC layer for the MAC layer. As another example, the lower layers of the RRC layer may include any one or more of the following: PHY layer, MAC layer, RLC layer, PDCP layer.

Fig. 4 is a schematic diagram of a relationship between PDCP PDUs and PDCP SDUs provided by an embodiment of the present application. As shown in fig. 4, for the access network device, the PDCP entity may or may not process the PDCP PDU for the data (e.g., PDCP SDU) received from the RRC layer, e.g., the PDCP entity may add the PDCP SDU to the PDCP header to obtain the PDCP PDU.

4. MAC multiplexing: refers to the MAC layer multiplexing data (e.g., MAC SDUs, or RLC PDUs) and/or MAC CEs of one or more logical channels onto one resource or MAC PDU. That is, the uplink resource allocated to a certain terminal device by the base station is determined, and the terminal device decides which logical channels to place data and how much data to place for each logical channel based on the configuration of the base station and rules specified by the protocol.

It will be appreciated that during MAC multiplexing, there is only one resource or MAC PDU, but there are a plurality of logical channels to be multiplexed, and that resources may be allocated for each logical channel according to the rules of logical channel priority (Logical Channel Prioritization, LCP). Wherein the logical channels have corresponding priorities.

One possible way is: the data of the highest priority logical channel is preferentially included in the MAC PDU, followed by the data of the next highest priority logical channel, and so on until the allocated resources or MAC PDU is full or no more data is to be transmitted. However, this allocation may cause the high priority logical channels to always occupy the radio resources allocated to the terminal device by the base station, so that the low priority logical channels cannot obtain the radio resources. To avoid this, LTE introduced the concept of prioritized bit rates (prioritised bit rate, PBR).

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

The MAC layer implements MAC multiplexing using algorithms similar to token bucket (token bucket). The basic idea of the algorithm is to determine whether to send data of a logical channel based on whether there are tokens in the token bucket and how many tokens are, and to control the amount of data of the logical channel assembled in the MAC PDU. The algorithm of the token bucket will be described in detail below.

The bucket size duration (bucket size duration, BSD) determines the "depth" of the token bucket. It determines together with the PBR that the maximum capacity of the token bucket is PBR x BSD. The maximum capacity of the token bucket limits the amount of data that each logical channel can suspend (pending), i.e., the total amount of data buffered in a buffer.

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

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

for LCH's selected according to LCP restrictions (and Bj of LCH's greater than 0), resources are allocated in descending order of priority. If the PBR of the logical channel is set to "infinity", the MAC entity will allocate resources for all data available for transmission on the lower priority logical channel before the PBR of that logical channel is met, and subtract Bj from the total size of the MAC SDUs provided by the logical channel j. If there are remaining resources, the data is provided in a strictly decreasing priority order (regardless of the value of Bj) for the logical channels selected according to the LCP restrictions. It should be noted that logical channels of the same priority should be treated equally.

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

For details of LCP or MAC multiplexing reference may be made to the specifications (technical specification, TS) 38.321 of the third generation partnership project (3rd generation partnership project,3GPP) for relevant details of MAC, see in particular "3rd Generation Partnership Project; technical Specification Group Radio Access Network; NR; medium Access Control (MAC) protocol specification).

5. Partial finish protection: for a certain RB, part of the data (e.g., PDCP data PDU) associated with the RB is integrity-protected. As can be seen from the foregoing, the MAC layer may multiplex a plurality of RLC PDUs, or a plurality of RLC SDUs, or a plurality of MAC SDUs, and thus, there may be two cases of MAC PDUs:

at least one integrity protected MAC SDU is contained for each RB in the MAC PDU; or, the MAC PDU contains at least one integrity-protected MAC SDU. Fig. 5 shows an example of the above two cases, which will be described in detail below in conjunction with fig. 5.

The integrity-protected MAC SDU can be understood as: the method comprises the steps of carrying out integrity protection on a MAC SDU corresponding to the PDCP PDU/SDU, or carrying out integrity protection on an RLC PDU corresponding to the PDCP PDU/SDU, or carrying out integrity protection on an RLC SDU corresponding to the PDCP PDU/SDU.

For each RB in a MAC PDU, at least one integrity-protected MAC SDU is contained:

as shown in a) in fig. 5, three PDCP SDUs associated with RB 1 are PDCP SDUs 1 to 3, PDCP SDU1 is integrity protected, three PDCP SDUs associated with RB 2 are PDCP SDUs a to c, PDCP SDU a is integrity protected, the PDCP layer issues it to the RLC layer, the RLC layer is not segmented, and further issues it to the MAC layer, and the MAC layer can multiplex it in one MAC PDU, and then the MAC PDU contains one integrity protected MAC SDU for each RB, namely MAC SDU1 and MAC SDU a.

For the case that at least one integrity protected MAC SDU is contained in a MAC PDU:

as shown in b) of fig. 5, three PDCP SDUs associated with RB 1 are PDCP SDUs 1 to 3, PDCP SDU1 is integrity protected, three PDCP SDUs associated with RB 2 are PDCP SDUs a to c, all of which are not integrity protected, the PDCP layer issues them to the RLC layer, the RLC layer is not segmented, and further issues them to the MAC layer, which can multiplex them in one MAC PDU, and the MAC PDU contains one integrity protected MAC SDU, i.e. MAC SDU1.

Wherein, the PDCP SDUs described in fig. 5 may be replaced with PDCP PDUs, it is understood that PDCP SDUs correspond to PDCP PDUs. In addition, the MAC SDU described in fig. 5 corresponds to the PDCP PDU, in other words, the MAC PDU includes an integrity-protected MAC SDU, or alternatively, the MAC PDU includes an integrity-protected PDCP PDU.

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

Fig. 6 is a schematic diagram of a system architecture suitable for use in the method provided by the embodiment of the present application. As shown in fig. 6, the communication system 600 includes communication devices 610 to 650, where the communication device 610 and the communication device 620 may be, for example, network devices, for example, micro base stations, TRP, or other types of network devices, which are not limited by the embodiments of the present application. The communication devices 630 to 650 may be, for example, terminal devices. Wherein the terminal device may be mobile or stationary. It will be appreciated that each network device may provide communication coverage for a particular geographic area and may communicate over a wireless link with terminal devices located within that coverage area (cell). For example, network device 610 may communicate with terminal device 630 and network device 620 may communicate with terminal devices 640, 650. In addition, wireless link communication can also be performed between the terminal devices. For example, terminal device 630 may communicate with terminal device 640, or with terminal device 650, and terminal device 640 may communicate with terminal device 650.

Alternatively, the communication system shown in the communication system 600 may include more or fewer communication devices, and the connection relationship between any two communication devices may be other connection relationships, which is not limited in this embodiment of the present application.

In the system architecture shown in fig. 6, when any two communication devices communicate, the integrity of the data sent by the communication devices can be protected by the PDCP layer to prevent the data from being tampered with. As can be seen from the foregoing, if a certain PDCP entity is configured with integrity protection, a PDCP PDU (e.g., PDCP data PDU) associated with the PDCP entity is integrity protected, and the receiving end may determine whether to discard the PDCP PDU based on whether the PDCP PDU passes the integrity check. However, in the case that a certain PDCP entity is configured with partial integrity protection, how to process PDCP PDUs (e.g., PDCP data PDUs) that are not integrity protected is a technical problem that needs to be solved.

In order to solve the above problems, the present application provides a communication method, where after a first communication device obtains data that is not integrity protected, in case that the data associated with the first communication device fails to verify the integrity protected data, the data that is not integrity protected is discarded, where the data associated with the first communication device and the data that is not integrity protected may be associated with the same MAC PDU and the same PDCP entity, or the same MAC PDU and different PDCP entities, or the different MAC PDUs and the same PDCP entity, or the different MAC PDUs and the different PDCP entities. And determining whether to discard the data which is not subjected to the integrity protection according to the integrity check result of the data subjected to the integrity protection, and providing a processing method of the data which is not subjected to the integrity protection for the first communication equipment. In addition, the method is beneficial to improving the accuracy of data receiving or the accuracy of data submitted to an upper layer, and is also beneficial to improving the communication quality/efficiency. For example, there are many cases where data not subjected to integrity protection is discarded, in other words, conditions under which data not subjected to integrity protection is submitted to an upper layer are strict, so that accuracy of data reception or accuracy of data submitted to the upper layer is improved.

It should be noted that, in the embodiment of the present application, the first communication device may be, for example, a receiving end of data, and the second communication device may be, for example, a sending end of data. 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 by the present application may be applicable to both interaction between a network device and a terminal device and interaction between a terminal device and a terminal device, which is not limited by the embodiments of the present application.

In the embodiment of the present application, any two or more of the first PDCP entity, the first RB, the first RLC entity, the first LCH, and the first logical channel identity (logical channel identifier, LCID) are associated, which is not limited in the embodiment of the present application.

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

In the 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, which is not limited in the embodiment of the present application.

In the embodiment of the present application, the second PDCP entity may be replaced with: any one or more of a second RB, a second RLC entity, a second LCH, and a 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, which is not limited in the embodiment of the present application.

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

In the embodiment of the present application, the PDCP entity may also be described/replaced with an RB, or LCH, or LCID, or RLC entity.

The communication method provided by the embodiment of the application will be described in detail below with reference to the accompanying drawings. It should be appreciated that the embodiment shown in fig. 7 describes the method from the perspective of the first communication device interacting with the second communication device.

It should be understood that the embodiments shown below are described by way of example in which a first communication device interacts with a second communication device, but should not constitute any limitation as to the subject matter of execution of the method. The method provided by the embodiment of the present application can be executed as long as the program recorded with the code of the method provided by the embodiment of the present application can be executed. For example, the first communication device may be replaced with a component (e.g., a chip system, etc.) provided in the first communication device, or other functional modules capable of calling and executing a program, and the second communication device may be replaced with a component (e.g., a chip system, etc.) provided in the network device, or other functional modules capable of calling and executing a program. The embodiment of the present application is not limited thereto.

Fig. 7 is a schematic flow chart of a communication method 700 provided by an embodiment of the present application. The communication method 700 shown in fig. 7 may include S710 and S720. The various steps in method 700 are described in detail below.

S710, the first communication device acquires first data.

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

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

Wherein the first data is associated with the first MAC PDU, it may be included/understood that all or part of the first data is from the first MAC PDU; and/or all or part of the first data belongs to the first MAC PDU.

For example, the first data is data that is not segmented, in other words, the second communication device does not segment in the process of transmitting the first data, i.e., all 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 segments the first data in the process of transmitting the first data, i.e., transmits the first data through different MAC PDUs, such as through the first MAC PDU and the second MAC PDU, in other words, a part of the first data is from the first MAC PDU and another part of the first data is from the second MAC PDU.

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

Optionally, the first PDCP entity is associated with a partial full hold.

For example, the first data may include/be understood as: a first PDCP PDU or a first PDCP data PDU.

The first communication device obtaining the first data may comprise/be understood as:

(one), the first communication device receives the first data from the second communication device. Accordingly, the second communication device transmits the first data to the first communication device; or alternatively, the first and second heat exchangers may be,

(II), the higher layer of the first communication device (e.g., the PDCP layer of the first communication device) acquires the first data from the lower layer of the first communication device. For example, with a first PDCP entity of a first communication device, the first PDCP entity obtains first data from an RLC layer of the first communication device; alternatively, the first PDCP entity obtains the first data from the MAC layer of the first communication device.

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

Wherein the first condition comprises one or more of:

the second data integrity check fails;

the third data integrity check fails;

The fourth data integrity check fails;

fifth data integrity check fails; or,

the sixth data integrity check fails.

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 with the first PDCP entity.

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

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

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

Optionally, the sixth data is associated with the second MAC PDU and/or 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 an understanding of at least one of the sixth data is associated with the second MAC PDU may refer to an understanding of the first data associated with 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 an understanding of at least one of the sixth data and the third PDCP entity may refer to an understanding of the first data associated with the first PDCP entity, and for brevity, will not be described in detail herein.

Optionally, 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 a different MAC PDU. 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 associated with the first MAC PDU and the second MAC PDU. "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 a different MAC PDU" may include/be understood as: at least one of the first data, the second data, the third data, the fourth data, the fifth data, or the sixth data is reassembled from segmented data (e.g., MAC SDUs or RLC PDUs) from different MAC PDUs. The first communication device receives the segment data 1 and the segment data 2, and then reassembles the segment data 1 and the segment data 2 through an RLC layer to obtain all data of the first data.

It should also be appreciated that in the case of determining whether to discard the first data based on the integrity check result of the second data, the first communication device is considered to have acquired the second data. Likewise, the third data to the sixth data are similar to the second data, and will not be described here.

It should also be appreciated that the following description is made from the perspective that the first communication device discards the first data satisfying the first condition, wherein the steps performed by the first communication device (e.g., discarding the first data) may be performed by the PDCP entity or other layer, and the present application is not limited. For example, the first condition is satisfied and the first PDCP entity discards the first data.

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

Note that, the hatched portions in fig. 8 to 12 indicate data subjected to integrity protection, and the blank portions indicate data not subjected to integrity protection. In the following, a few possible cases of discarding the first data will be described in detail taking any one of the one or more data that is not integrity protected, such as the first data, as an example.

First, several cases of discarding the first data for one MAC PDU are shown.

The first possibility is to discard the first data in case the second data integrity check fails. It can be appreciated that if the integrity check of the integrity-protected data associated with the first MAC PDU (i.e., the same MAC PDU as the first data) and the first PDCP entity (i.e., the same PDCP entity as the first data) fails, the first data may be considered to be possibly tampered with, and discarded, thereby facilitating improvement of accuracy of data reception or accuracy of data submitted to an upper layer. As shown in fig. 8, the data in the MAC PDU that is not integrity protected includes data 2 and/or data b, the second data may be data 1 or data a, and the second data and the first data are both associated with the first MAC PDU and the first PDCP entity. In case the second data integrity check fails, the first communication device discards the first data, i.e. data 2 and/or data b.

A second possibility is to discard the first data in case the third data integrity check fails. It can be appreciated that if the integrity-protected data integrity check associated with the first MAC PDU (i.e., the same MAC PDU as the first data) and the second PDCP entity (i.e., different from the PDCP entity associated with the first data) fails, the first data may be considered to be possibly tampered with, and discarded, thereby facilitating an improvement in accuracy of data reception or accuracy of data submitted to an upper layer. As shown in fig. 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 case the third data integrity check fails, the first communication device discards the first data, i.e. at least one of data 1, data 2 or data b.

A third possible scenario is to discard the first data in case the second data integrity check fails and the third data integrity check fails. It can be appreciated that if the integrity check of the integrity-protected data associated with the first MAC PDU (i.e., the same MAC PDU as the first data) fails, the first data may be considered to be possibly tampered with, and the first data is discarded, thereby facilitating improvement of accuracy of data reception or accuracy of data submitted to an upper layer. As shown in fig. 10, the data that is not integrity protected in the MAC PDU includes data 2 and data b, the second data includes data 1, the third data includes data a, and the first data to the third data are all associated with the first MAC PDU. In case the integrity check of both the second data and the third data fails, the first communication device discards the first data, i.e. discards data 2 and/or data b.

It may be seen that the second data integrity check fails and/or the third data integrity check fails, and the first data is discarded, which may be understood as discarding the first data in case one or more of the integrity-protected data of the same MAC PDU associated with the first data fails. It should be noted that, in the embodiment of the present application, it may be determined whether to discard the first data according to one or more data integrity check results in the integrity-protected data associated with the same MAC PDU as the first data, that is, whether to consider the PDCP entity corresponding to the MAC PDU, or not.

Next, several cases of discarding the first data for a plurality of MAC PDUs are shown.

It should be understood that, as already mentioned above, there may be a case of segmentation of at least one of the first data to the sixth data, i.e. a certain data is transmitted via different MAC PDUs, how to discard the first data will be described in detail below.

The first possibility is to discard the first data in case the fourth data integrity check fails. 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, a part of the fourth data is from the first MAC PDU, another part of the fourth data is from the second MAC PDU, and after being reassembled by the RLC layer of the first communication device, the PDCP layer further performs integrity checking on the fourth data, so that the fourth data integrity checking failure may be that a part of the fourth data in the first MAC PDU may be tampered with, or that another part of the fourth data in the second MAC PDU may be tampered with, so that the data in the first MAC PDU that is not integrity protected may also be tampered with, and therefore, the first communication device discards the first data. For example, as shown in fig. 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 data that is not segmented; or data 2 and/or data b may also be data that is segmented), the fourth data is data that is segmented, a portion of the fourth data may be data 3, and another portion of the fourth data may be data 1. The first communication device reassembles the data 1 and the data 3 to form fourth data, if the integrity check of the fourth data fails, any one of the data 1 and the data 3 has a possibility of being tampered, so that the data which is not subjected to integrity protection in the first MAC PDU, namely, the first data, also has a possibility of being tampered, and therefore, the data 2 and/or the data b are discarded, namely, the first data is discarded.

Another possible design is that the first data may be data that is segmented and the fourth data is data that is not segmented, e.g. part of the first data is from a first MAC PDU and another part of the first data is from a second MAC PDU, in case the fourth data integrity check fails, there is a possibility that part of the first data in the second MAC PDU is tampered with, and thus the first communication device discards the first data.

It should be understood that the above-described case of discarding the first data is merely an example, and should not be construed as limiting the embodiments of the present application in any way. For example, in the event that the fifth data integrity check fails, discarding the first data; or, in case the sixth data integrity check fails, discarding the first data. In addition, in the case that any two or more of the second data to the sixth data fail in the integrity check, the first data may be discarded, for example, the second data and the fourth data fail in the integrity check, and the first data may be discarded. For brevity, details are not provided here.

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

It should also be appreciated that the descriptions of fig. 8-11 only exemplarily describe a case of discarding data without integrity protection, and other data without integrity protection may be discarded by a similar method, which is not described in detail herein.

Alternatively, in an embodiment of the present application, the discard data may be discarded in the form of a group. In an example, a certain MAC PDU contains data associated with one PDCP entity. In the case that the integrity check of the integrity-protected data in the MAC PDU fails, all the data (i.e., a set of data) in the MAC PDU that is not integrity-protected is discarded. For example, the MAC PDU 1 includes data 1, data 2, and data 3, where data 1 is data with integrity protection, data 2 and data 3 are data without integrity protection, and data 1, data 2, and data 3 are associated with the same PDCP entity, and if the integrity check of data 1 fails, both data 2 and data 3 need to be discarded.

As yet another example, a certain MAC PDU contains data associated with a plurality of PDCP entities. In the case that the integrity check of the integrity-protected data in the MAC PDU fails, all the data (i.e., a set of data) in the MAC PDU that is not integrity-protected is discarded. For example, the MAC PDU 1 includes data 1, data 2, data 3, and data 4, where data 1 and data 3 are data that are not integrity protected, data 2 and data 4 are data that are not integrity protected, and data 1 and data 2 are associated with PDCP entity 1, and data 3 and data 4 are associated with PDCP entity 2, so that in case that the integrity check of data 1 fails, both data 2 and data 4 that are not integrity protected need to be discarded.

For another example, regarding the plurality of MAC PDUs, taking MAC PDU 1 and MAC PDU 2 as an example, a certain data in MAC PDU 1 and a certain data in MAC PDU 2 are segmented from the same data and are integrity-protected data, and after the data are reassembled, integrity check is performed, and if the integrity check fails, all the data that are not integrity-protected in MAC PDU 1 and MAC PDU 2 are discarded. For example, the MAC PDU 1 includes data 1, data 2, and data 3, the MAC PDU 2 includes data 4 and data 5, the data 1 and data 4 are data subjected to integrity protection, the data 1 and data 4 are data segmented by a certain data (denoted as data 6), the data 2, data 3, and data 5 are data not subjected to integrity protection, the data 1 and data 4 are reassembled and then subjected to integrity verification, and if the integrity verification fails, the data 2, data 3, and data 5 not subjected to integrity protection need to be discarded.

It is further 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 associated with a different MAC PDU based on the third indication information.

Alternatively, the third indication information may be from the RLC layer or the 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 a different MAC PDU (e.g., a first MAC PDU and a second MAC PDU), and the third indication information may be from the first RLC entity.

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

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

Optionally, the method further comprises: one or more of the second data, the third data, the fourth data, the fifth data, or the sixth data is discarded.

That is, for the second to sixth data subjected to the integrity protection, it is also necessary to consider whether to discard or not. Several possible scenarios are exemplarily shown below.

A first possibility is that the first communication device discards the second data in addition to the first data. As shown in fig. 8, the data that is not integrity protected in the MAC PDU includes data 2 and data b, the second data may be data 1 or data a, the second data and the first data are both associated with the first MAC PDU and are both associated with the first PDCP entity, and in case of failure of the integrity check of data 1, the data 2, the data 1 and the data b are discarded, i.e. the first data and the second data are discarded. In addition, whether or not the data a is successfully checked for integrity, the data a will be further discarded, in other words, when one of the MAC PDUs fails in the data integrity check, all the data on the MAC PDU (e.g., MAC SDU or RLC PDU) will be discarded, or the data on the MAC PDU associated with the PDCP entity associated with the partial reservation (e.g., MAC SDU or RLC PDU) will be discarded. Alternatively, if the integrity check of data 1 fails, the integrity check of data a is successful, discarding data 2, data b and data 1. In other words, when one or more data integrity checks fail in a certain MAC PDU, the data with failed integrity protection and the data without integrity protection (e.g., MAC SDU or RLC PDU) on the MAC PDU will be discarded, or the data with failed integrity protection and the data associated with the PDCP entity associated with partial integrity protection (e.g., MAC SDU or RLC PDU) will be discarded. It should be understood that, for data 2 and data b that are not integrity-protected, in an 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, and thus, each time one data is received that is not integrity-protected, 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 therewith.

A second possibility is that the first communication device discards the second data and the third data in addition to the first data. As shown in fig. 12, the first data includes data 1, the second data includes data 2, the third data may be data a or data b, and when one or more of data 2, data a and data b fails to check the integrity of the data, data 1, data 2, data a and data b are discarded, i.e., the first data, the second data and the third data are discarded. Or when the integrity check of the data 2 fails, discarding the data 1 and the data 2 under the condition that the integrity check of the data a and the data b is successful.

It should be understood that the two cases shown above are merely examples and should not be construed as limiting the embodiments of the present application in any way. For example, the second data and the fourth data may also be discarded; alternatively, the second data and the fifth data may also be discarded, etc. For brevity, details are not provided here.

It will be appreciated that the above description is made in terms of in which case the first communication device discards the first data, and accordingly, it may also be considered in terms of in which case the first communication device does not discard the first data.

Optionally, the method may further include: s730, the first communication device does not discard the first data.

The first communication device not discarding the first data may include/be understood as one or more of the following: the first communication device stores the first data, the first communication device delivers/stores the first data to/in the reception buffer, the first communication device performs reordering, or the first communication device processes the first data.

Wherein the second condition comprises one or more of:

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 cases for one MAC PDU are shown without discarding the first data.

A first possibility is that the first communication device does not discard the first data in case the second data integrity check is successful. If the integrity-protected data integrity check associated with the first MAC PDU (i.e., the same MAC PDU as the first data) and the first PDCP entity (i.e., the same PDCP entity as the first data) is successful, the first data may be considered to be unlikely to be tampered with and discarded. For example, the first MAC PDU includes only data associated with one PDCP entity, and when the second data integrity check is successful, that is, the integrity-protected data integrity check in the first MAC PDU is successful, it is considered that the possibility that the data not integrity-protected is tampered may be ignored, so the first communication device does not discard the first data.

A second possibility is that the first communication device does not discard the first data in case the third data integrity check is successful. If the integrity-protected data integrity check associated with the first MAC PDU (i.e., the same MAC PDU as the first data) and associated with the second PDCP entity (i.e., different from the PDCP entity associated with the first data) is successful, the first data may be considered to be unlikely to be tampered with and discarded. For example, the first MAC PDU includes data associated with the first PDCP entity and the second PDCP entity, and if the third data integrity check is successful, it is considered that the possibility that the data that is not integrity-protected is tampered may be ignored, so the first communication device does not discard the first data.

A third possibility is that the first communication device does not discard the first data in case the second data integrity check is successful and the third data integrity check is successful. If the integrity-protected data integrity check associated with the first MAC PDU (i.e., the same MAC PDU as the first data) and with the second PDCP entity (i.e., different from the PDCP entity associated with the first data) and with the first PDCP entity (the same PDCP entity as the first data) is successful, the first data may be considered to be unlikely to be tampered with and not discarded. For example, the first MAC PDU includes data associated with the first PDCP entity and the second PDCP entity, and if the second data integrity check is successful and the third data integrity check is successful, the first data is not discarded.

From the above, it can be seen that one possible implementation is that one or more data integrity checks of the integrity-protected data associated with the same MAC PDU as the first data are successful, and the first communication device may not discard the first data.

It should be understood that, as already mentioned above, there may be a case of segmentation of at least one of the first data to the sixth data, that is, a case where a certain data is transmitted via a different MAC PDU, a condition that the first data is not discarded will be described in detail below.

The first possibility is that the first data is not discarded in case the fourth data integrity check is successful. The fourth data integrity check is successful with two possible designs:

one possible design is that the fourth data may be segmented data, e.g. a part of the fourth data is from the first MAC PDU, another part of the fourth data is from the second MAC PDU, after being reassembled by the RLC layer of the first communication device, the PDCP layer further performs an integrity check on the fourth data, so that a successful integrity check of the fourth data may be understood that there is no possibility of tampering by a part of the fourth data in the first MAC PDU and another part of the fourth data in the second MAC PDU, so that there is no possibility of tampering of data in the first MAC PDU that is not integrity protected, and therefore the first communication device does not discard the first data.

Another possible design is that the first data may be data that is segmented and the fourth data is data that is not segmented, e.g. part of the first data is from a first MAC PDU and another part of the first data is from a second MAC PDU, and in case the fourth data integrity check is successful, there may be no possibility that part of the first data in the second MAC PDU is tampered with, and therefore the first communication device does not discard the first data.

A second possibility is that the first communication device does not discard the first data in case the second data integrity check is successful and the fourth data integrity check is successful. For example, the first MAC PDU includes only data associated with the first PDCP entity, the second MAC PDU includes only data associated with the first PDCP entity, and the first data is associated with the first MAC PDU and the second MAC PDU, and the first communication device does not discard the first data in case that the second data integrity check is successful and the fourth data integrity check is successful.

It should be understood that the above-described cases are merely examples and should not be construed as limiting the embodiments of the present application in any way. For example, the first data may not be discarded if the fifth data integrity check is successful. For brevity, details are not provided here.

It should also be appreciated that the case of successful fifth data integrity check and/or successful sixth data integrity check is similar to the fourth data and will not be described in detail herein for brevity.

It should also be understood that the above condition of discarding the first data and the condition of not discarding the first data may be used separately or may be used in combination, which is not limited by the embodiment of the present application.

It can be appreciated 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 indication information across RB/PDCP entities. For example, the first PDCP entity receives indication information of other PDCP entities to determine its associated data integrity check result.

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

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

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

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

For example, the first PDCP entity receives eighth indication information from the second PDCP entity, the eighth indication information indicating that the third data integrity check is successful, and the first PDCP entity may determine that the data integrity check associated with the same MAC PDU associated with the first data is successful, and may not discard the first data.

It should be noted that S730 may be implemented as a separate embodiment or may be used as a step in this embodiment in combination with other steps in this embodiment, for example, as an optional step in combination with S710, S720 and one or more of i to v mentioned below. The application is not limited in this regard.

Optionally, the above method may further comprise 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 data of the first data, the second data and the third data is associated with the first MAC PDU according to the first indication information; or (b)

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

It will be appreciated that the first communication device obtains one or more PDCP PDUs and needs to determine which MAC PDU or PDUs these PDCP PDUs are associated with.

Alternatively, the first indication information and/or the second indication information may be from a MAC layer or an RLC layer of the first communication device.

The first indication information and the second indication information may be acquired simultaneously, may not be acquired simultaneously, may be acquired separately, or may be acquired together, which is not limited by the embodiment of the present application.

The process by which the first communication device determines data associated with the same MAC PDU will be described below from the perspective of the respective protocol layers of the first communication device.

In an example, when there is only one MAC PDU (e.g., a first MAC PDU) and the first MAC PDU contains only data associated with one PDCP entity, the MAC or RLC layer transmits first indication information to the PDCP layer to indicate to the PDCP layer that the first data and/or the second data are associated with the first MAC PDU.

In yet another example, when there is only one MAC PDU (e.g., a first MAC PDU) and the first MAC PDU includes data associated with a plurality of PDCP entities (e.g., a first PDCP entity and a second PDCP entity), the MAC or RLC layer transmits first indication information to the PDCP layer to indicate that at least one of first data, second data, or third data of the PDCP layer is associated with the first MAC PDU.

Optionally, the first indication information also needs to indicate with which PDCP entities the data contained in the first MAC PDU is associated. For example, only one MAC PDU, such as MAC PDU 1, including data 1, data 2, and data 3 in the MAC PDU 1, the data 1 being associated with the PDCP entity 1, the data 2 and the data 3 being associated with the PDCP entity 2, i.e., the MAC PDU 1 contains data associated with 2 PDCP entities, the MAC or RLC layer transmits first indication information to the PDCP layer, the first indication information may indicate: information of data associated with MAC PDU 1 (e.g., number information corresponding to at least one of data 1, data 2, or data 3) may also indicate: information of the PDCP entity associated with the MAC PDU 1 (e.g., data 1 associated with PDCP entity 1 and/or data 2 and/or data 3 associated with PDCP entity 2).

In yet another example, when there are a plurality of MAC PDUs (e.g., a first MAC PDU and a second MAC PDU), the MAC or RLC layer transmits first indication information to the PDCP layer to indicate that at least one of first data, second data, or third data of the PDCP layer is associated with the first MAC PDU. The MAC or RLC layer transmits second indication information to the PDCP layer to indicate that at least one of fourth data, fifth data, or sixth data is associated with the second MAC PDU.

Alternatively, if the data contained in a certain MAC PDU is associated with a plurality of PDCP entities, the indication information also needs to indicate with which PDCP entities the data contained in the MAC PDU is associated. For example, there are a plurality of MAC PDUs, such as MAC PDU1 and MAC PDU2, where the MAC PDU1 includes data 1 and data 2, where the data 1 is associated with PDCP entity 1, and where the data 2 is associated with PDCP entity 2, that is, where the MAC PDU1 includes data 3 and data 4, where the data 3 is associated with PDCP entity 1, and where the data 4 is associated with PDCP entity 2, the MAC or RLC layer sends a first indication information to the PDCP layer, where the first indication information may indicate information of the data associated with MAC PDU1 (e.g., number information corresponding to at least one of data 1 and data 2, where the data 1 and data 2 are associated with MAC PDU 1), and may also indicate information of the PDCP entity associated with MAC PDU1 (e.g., data 1 is associated with PDCP entity 1, data 2 is associated with PDCP entity 2), and where the MAC or RLC layer may also send a second indication information to the PDCP layer, where the second indication information may indicate information of the data associated with MAC PDU2 (e.g., data 3, or at least one of data 3, data 2 and data 4 is associated with PDCP entity 2, and number information corresponding to at least one of data 3, and data 2 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 the present application.

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

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

The above numbering information may be of the following two possible designs:

one possible design is that the numbering information may be a newly defined number, and that data associated with the same MAC PDU will get the same number. For example, data associated with a first MAC PDU will get the same number, e.g., number 1, and data associated with a second MAC PDU will get a different number, e.g., number 2, than the first MAC PDU. In an example, the first MAC PDU includes data 1, data 2, and data 3, the second MAC PDU includes data 4 and data 5, and numbers of data 1, data 2, and data 3 may be number 1, numbers of data 4 and data 5 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, and the second indication information may include numbers corresponding to data 4 and data 5, such as number 2.

Another possible design is that the number may be a PDCP sequence number indicated by the MAC layer in the first communication device to the PDCP layer directly, or an RLC sequence number indicated by the MAC layer in the first communication device to the RLC layer, and further 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 corresponds to the PDCP sequence number associated with the first MAC PDU and which data corresponds to the PDCP sequence number associated with the second MAC PDU, and 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 above, the data acquired 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, the third data, the fifth data are associated with the second PDCP entity, the sixth data are associated with the third PDCP entity, and the integrity check for a certain data is performed by its corresponding PDCP entity, so it is necessary for the first PDCP entity to receive the integrity check results for its associated data from other PDCP entities. It should be noted that, in the embodiment of the present application, 2 PDCP entities (such as the first PDCP entity and the second PDCP entity) are described herein as an example for one MAC PDU, and 3 PDCP entities (such as the first PDCP entity, the second PDCP entity and the third PDCP entity) are described herein for 2 MAC PDUs, and in other embodiments, the first communication device may also correspond to a larger number of PDCP entities, that is, the number of PDCP entities that need to perform interaction will be larger, which is not limited in the embodiment of the present application.

Optionally, the above method may further comprise at least one of the following iii to v:

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 fails or succeeds based on the fifth indication information; or (b)

And v, the first communication equipment determines that the sixth data integrity check fails or succeeds based on the sixth indication information.

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

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

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

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

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

Based on the above technical solution, after the first communication device obtains the data (for example, the first data) which is not subjected to the integrity protection, the first data may be discarded in the case that the verification of the data which is associated with the first communication device and is subjected to the integrity protection fails. And determining whether to discard the data which is not subjected to the integrity protection according to the checking result of the data subjected to the integrity protection, and providing a processing method of the data which is not subjected to the integrity protection for the first communication equipment. And the accuracy of data receiving or the accuracy of data submitted to an upper layer is also improved. Which is advantageous for improving communication quality/efficiency. For example, the situation that data which is not subjected to integrity protection is discarded is more, that is, conditions for submitting the data which is not subjected to integrity protection to an upper layer are more strict, so that the accuracy of data receiving or the accuracy of data submitted to the upper layer is improved.

Another communication method provided by the embodiment of the present application will be described below with reference to fig. 13. Fig. 13 is a schematic flow chart diagram 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. The steps in method 1300 are described in detail below.

S1310, the first communication device generates seventh indication information for indicating a proportion of data for adjusting (or suggesting adjusting) the integrity protection.

Wherein adjusting or suggesting adjusting the proportion of integrity-protected data includes/is understood as any one of: to turn up (or suggest to turn up) the proportion of integrity-protected data, to turn down (or suggest to turn down) the proportion of integrity-protected data, to increase (or suggest to increase) the integrity-protected data, to decrease (or suggest to decrease) the integrity-protected data, to turn on (or suggest to turn on) the partial full protection function, or to turn off (or suggest to turn off) the partial full protection function.

The heightening may include/be understood as: and (3) increasing.

The throttling down may include/be understood as: and (3) reducing.

Opening may include/be understood as: enabling.

Closing may include/be understood as: disabling.

Optionally, the seventh indication information may also be used to indicate the adjusted proportion, or suggest the adjusted proportion.

In other words, the seventh indication information may indicate that the second communication device adjusts (or suggests adjusting) the proportion of the integrity protection, and may also indicate a value of the proportion of the integrity protection data specifically adjusted (or suggested adjusting). For example, the seventh indication information may indicate a proportion of data of the integrity protection to be turned up (or suggested to be turned up), and may also indicate how much to specifically turn up (or suggested to be turned up). For another example, the seventh indication information may indicate a proportion of the data of the integrity protection to be turned down (or suggested to be turned down), and may also indicate how much to specifically turn down (or suggested to be turned down).

Optionally, the method may further include: the third condition is satisfied and the seventh indication information indicates that the proportion of the integrity-protected data is turned up (or suggested to be turned up), or that the integrity-protected data is increased (or suggested to be increased), or that the partial protection function is turned off (or suggested to be turned off).

Wherein the third condition comprises one or more of:

the number of failed integrity checks is greater than or equal to a first threshold; or alternatively, the first and second heat exchangers may be,

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

The MAC PDU may further include a MAC Control Element (CE), and the like. It should be noted that, the data described above may refer to a MAC SDU or a PDCP PDU corresponding to the MAC SDU.

The number of integrity check failures greater than or equal to the first threshold may include/be replaced with: the number of times the integrity check is successful is less than or equal to a first threshold.

The integrity-protected data may be replaced with an integrity-protected MAC SDU or PDCP PDU corresponding to the MAC SDU.

Optionally, the method may further include: the fourth condition is satisfied and the seventh indication information indicates that the proportion of the integrity-protected data is turned down (or recommended to be turned down), the integrity-protected data is reduced (or recommended to be reduced), or the partial protection function is turned on (or recommended to be turned on).

Wherein the fourth condition comprises one or more of:

the number of times of successful integrity check is greater than or equal to a third threshold;

the number of received MAC PDUs containing integrity-protected data is greater than or equal to a fourth threshold; or alternatively, the first and second heat exchangers may be,

the number of the received MAC PDUs is greater than or equal to a fifth threshold, wherein the received MAC PDUs contain data that is integrity protected.

The MAC PDU may further include a MAC CE, and it should be noted that, the data described herein refers to a MAC SDU or a PDCP PDU corresponding to the MAC SDU. For example, the received MAC PDU may include data that is integrity protected instead of: the received MAC PDU contains MAC SDUs that are integrity protected.

The received MAC PDU contains data that is integrity protected and may include/be understood as one or more of the following: the received MAC PDU contains data (e.g., MAC SDU or RLC PDU) that is integrity protected; or, the received MAC PDU contains data (e.g., MAC SDU or RLC PDU) associated with the PDCP entity associated with the partial hold, which is integrity-protected data.

The number of successful integrity checks greater than or equal to the third threshold may include/be replaced with: the number of integrity check failures is less than or equal to a third threshold.

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

The number of integrity check failures is determined according to any one of the following: the number of PDCP PDUs failing the integrity check; or, the number of MAC PDUs including PDCP PDUs for which the integrity check fails.

Alternatively, 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, the continuous integrity check failure refers to a case where the continuous integrity check fails and the intermediate integrity check is not successful in performing the integrity check. Discontinuous integrity check failure refers to multiple integrity checks, some of which are successful and others of which are discontinuous. For example, 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 two.

One possible design is that the number of integrity check failures may be determined based on the number of PDCP PDUs that failed the integrity check. The number of PDCP PDUs failing in the integrity check may be the number of PDCP PDUs failing in the continuous integrity check or the number of PDCP PDUs failing in the discontinuous integrity check, which is not limited in the embodiment of the present application.

Alternatively, the number of PDCP PDUs for which the integrity check fails may be granularity for the first communication device or may be granularity for one PDCP entity. Wherein, PDCP entity granularity may also be described/replaced by RB granularity, or LCH granularity, or LCID granularity, or RLC entity granularity.

Optionally, if the number of PDCP PDUs with failed integrity check is granularity for one PDCP entity, 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, the consecutive integrity check failure refers to a case where the consecutive integrity check fails for one PDCP entity and there is no successful integrity check in between. Discontinuous integrity check failure refers to that multiple integrity checks are performed on one PDCP entity, some are successful and some are failed, wherein the integrity check failure is discontinuous. For example, 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 two.

For example, the first communication device may maintain a counter, and the number of PDCP PDUs for which the integrity check fails is increased by 1, and the number of times the integrity check fails is increased by 1.

Optionally, the number of PDCP PDUs for which the integrity check fails is the number of PDCP PDUs for which the integrity check fails within the first preset time period.

For example, a duration may be set, and in the case that the first preset duration is reached and the number of PDCP PDUs for which the integrity check fails is greater than or equal to the first threshold, the seventh indication information indicates to turn up (or suggest to turn up) the proportion of the integrity-protected data, or to increase (or suggest to increase) the integrity-protected data, or to turn off (or suggest to turn off) the partial full-protection function.

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

The number of MAC PDUs including PDCP PDUs for which the integrity check fails may be granularity for the first communication device or may be granularity for one PDCP entity.

For example, the first communication device may maintain a counter, the number of MAC PDUs including PDCP PDUs with failed integrity checks is increased by 1, and the counter integrity check is increased by 1, wherein for a certain MAC PDU, if the number of PDCP PDUs with failed integrity checks in the MAC PDU is 2, the counter is increased by 1.

Optionally, the number of MAC PDUs including PDCP PDUs failing the integrity check is the number of MAC PDUs including PDCP PDUs failing the integrity check within the second preset time period.

For example, a duration may be set, and in the case that the second preset duration is reached and the number of MAC PDUs including PDCP PDUs for which the integrity check fails is greater than or equal to the second threshold, the seventh indication information indicates to increase (or suggest to increase) the proportion of the integrity-protected data, or increase (or suggest to increase) the integrity-protected data, or close (or suggest to close) the partial full-protection function.

Optionally, the number of PDCP PDUs for which the integrity check fails is associated with one PDCP entity; alternatively, the PDCP PDU for which the integrity check fails from among the number of MAC PDUs including the PDCP PDU for which the integrity check fails is associated with one PDCP entity.

Wherein the number of PDCP PDUs for which the integrity check fails is associated with one PDCP entity, indicating that the number of PDCP PDUs for which the integrity check fails is granularity for one PDCP entity. For example, one PDCP entity maintains a counter, and the number of PDCP PDUs for which the integrity check associated with the PDCP entity fails is increased by 1, and the counter integrity check corresponding to the PDCP entity is increased by 1.

The association of the PDCP PDUs with which the integrity check fails in the number of MAC PDUs containing the PDCP PDUs with which the integrity check fails with one PDCP entity is also granularity for one PDCP entity. For example, one PDCP entity maintains one counter, and if the number of PDCP PDUs for which the integrity check fails in a certain MAC PDU is 2 and the two PDCP PDUs are associated with different PDCP entities, the counter corresponding to each PDCP entity is incremented by 1.

The number of successful integrity checks is determined according to any one of the following: the number of PDCP PDUs for which the integrity check is successful; or, the number of MAC PDUs including PDCP PDUs for which the integrity check was successful.

Alternatively, the number of successful integrity checks may be the number of successful continuous integrity checks or the number of unsuccessful integrity checks. For example, the continuous integrity check is successful when the continuous integrity check is successful and the integrity check fails in the middle. Discontinuous integrity check success refers to performing multiple integrity checks, some of which are successful and others of which are failed, wherein the integrity check success is discontinuous. For example, the integrity check is performed five times, the first integrity check is successful, the second to fourth integrity checks fail, and the fifth integrity check is successful, and the number of times of the integrity check is two.

The number of successful integrity checks may be determined based on the number of PDCP PDUs for which the integrity checks were successful.

Optionally, the number of PDCP PDUs for which the integrity check is successful is granularity for the first communication device, or may be granularity for one PDCP entity. Wherein, PDCP entity granularity may also be described/replaced by RB granularity, or LCH granularity, or LCID granularity, or RLC entity granularity.

Optionally, if the number of PDCP PDUs for which the integrity check is successful may be granularity for one PDCP entity, the number of successful integrity checks may be the number of successful continuous integrity checks or the number of unsuccessful integrity checks. For example, the continuous integrity check success refers to a case where continuous integrity check is successful for one PDCP entity, and there is no integrity check failure in between. Discontinuous integrity check success refers to that multiple integrity checks are performed on one PDCP entity, some are successful and some are failed, wherein the integrity check success is discontinuous. For example, four integrity checks are performed, the first integrity check is successful, the second and third integrity checks fail, and the fourth integrity check is successful, then the number of integrity checks is two.

For example, the first communication device may maintain a counter, and the number of PDCP PDUs for which the integrity check is successful is increased by 1, and the number of times the integrity check indicated by the counter is successful is increased by 1.

Optionally, the number of PDCP PDUs for which the integrity check is successful is the number of PDCP PDUs for which the integrity check is successful within the third preset time period.

For example, a duration may be set, and in the case that the third preset duration is reached and the number of PDCP PDUs for which the integrity check is successful is greater than or equal to the third threshold, the seventh indication information indicates to turn down (or suggest to turn down) the proportion of the integrity-protected data, or to decrease (or suggest to decrease) the integrity-protected data, or to turn on (or suggest to turn on) the partial full-protection function.

The number of successful integrity checks may also be determined based on the number of MAC PDUs including PDCP PDUs for which the integrity check was successful.

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

For example, the first communication device may maintain a counter, the number of MAC PDUs including PDCP PDUs for which the integrity check is successful is increased by 1, and the number of integrity check successes indicated by the counter is increased by 1, wherein for a certain MAC PDU, if the number of PDCP PDUs for which the integrity check is successful in the MAC PDU is 2, the counter is increased by 1.

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

For example, a duration may be set, and in the case that the fourth preset duration is reached and the number of MAC PDUs including PDCP PDUs for which the integrity check is successful is greater than or equal to the fourth threshold, the seventh indication information indicates to turn down (or suggest to turn down) the proportion of the integrity-protected data, or to decrease (or suggest to decrease) the integrity-protected data, or to turn on (or suggest to turn on) the partial full-protection function.

Optionally, the number of PDCP PDUs for which the integrity check is successful is associated with one PDCP entity; alternatively, the successfully-checked PDCP PDUs of the number of MAC PDUs including the successfully-checked PDCP PDUs are associated with one PDCP entity.

Wherein the number of PDCP PDUs for which the integrity check is successful is associated with one PDCP entity, indicating that the number of PDCP PDUs for which the integrity check is successful is granularity for one PDCP entity. For example, one PDCP entity maintains a counter, and the number of PDCP PDUs for which the integrity check associated with the PDCP entity is successful is increased by 1, and the counter integrity check corresponding to the PDCP entity is increased by 1.

The association of the successfully-integrity-checked PDCP PDUs with one PDCP entity in the number of MAC PDUs containing the successfully-integrity-checked PDCP PDUs is also granularity for one PDCP entity. For example, one PDCP entity maintains a counter, and if the number of PDCP PDUs for which the integrity check is successful is 2 in a certain MAC PDU and the two PDCP PDUs are associated with different PDCP entities, the counter corresponding to each PDCP entity is incremented by 1.

It should be appreciated that the above-described adjustment or recommendation to adjust the proportion of integrity-protected data may be communication device granularity or PDCP entity granularity. For example, the seventh indication information indicates adjusting or suggesting 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, the proportion of data that adjusts or suggests to adjust the integrity protection is for PDCP entity granularity. For example, the seventh indication information may be used to indicate a proportion of data to adjust or suggest to adjust the integrity protection 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 for which the integrity check associated with the first PDCP entity fails reaches a first threshold, the seventh indication information indicates to turn up or suggest to turn up the proportion of integrity-protected data associated with the first PDCP entity, or to turn off or suggest to turn off the partial full hold function for the first PDCP entity. In other words, the proportion of integrity-protected data associated with other PDCP entities of the second communication device need not be adjusted.

S1320, the first communication device sends seventh indication information to the second communication device. Accordingly, the second communication device receives the seventh indication information.

After the first communication device generates the seventh indication information, the seventh indication information is sent to the second communication device, so that the second communication device can adjust the proportion of the integrity-protected data.

For example, the seventh indication information occupies 1 bit. This value of 1 represents a proportion of data of the turnup (or proposed turnup) integrity protection, and this value of 0 represents a proportion of data of the turndown (or proposed turndown) integrity protection. The particular adjusted value may be determined by the second communication device.

For another example, a value of 1 indicates that the partial full protection function is on (or recommended to be on), and a value of 0 indicates that the partial full protection function is off (or recommended to be off).

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

For example, the proportion of the integrity-protected data may be adjusted for the PDCP entity granularity, and the seventh indication information indicates to adjust (or suggest to adjust) the proportion of the integrity-protected data associated with a certain PDCP entity, where the seventh indication information further needs to indicate information of the corresponding PDCP entity. The seventh indication information may also indicate information of the corresponding RB, or LCH, or LCID. The embodiment of the present application is not limited thereto.

Optionally, the method further comprises: and S1330, the second communication device adjusts the proportion of the integrity-protected data based on the seventh indication information.

And after the second communication equipment receives the seventh indication information, adjusting the proportion of the integrity-protected data based on the seventh indication information.

For example, if the seventh indication information indicates to raise (or suggests to raise) the proportion of the integrity-protected data in the second communication device, the second communication device may raise the proportion of the integrity-protected data after receiving the seventh indication information, and the specific raised value may be determined by the second communication device, for example, may be determined based on the function of the second communication device itself.

For another example, when the seventh indication information indicates to raise (or suggests to raise) the proportion of the integrity-protected data associated with the first PDCP entity in the second communication device, the second communication device receives the seventh indication information and then raises the proportion of the integrity-protected data associated with the first PDCP entity, and the other PDCP entities may perform integrity protection on the data according to the original proportion.

Based on the technical scheme, the first communication device can generate the seventh indication information based on the verification result of the integrity-protected data and send the seventh indication information to the second communication device, so that the second communication device can adjust the proportion of the integrity-protected data based on the seventh indication information, thereby being beneficial to improving the rationality of the proportion of the integrity-protected data in the second communication device and improving the communication quality/efficiency.

It should be noted that the embodiments shown in fig. 7 and 13 may be used in combination or may be used alone, and the comparison of the embodiments of the present application is not limited.

As can be seen from the foregoing, in the case of partial handover, one MAC PDU contains at least one integrity-protected MAC SDU for each PDCP entity, and how the second communication device guarantees that one MAC PDU contains at least one integrity-protected MAC SDU for one PDCP entity (e.g., one PDCP entity associated with partial handover) during MAC multiplexing will be described in detail below with reference to specific embodiments.

Fig. 14 is a schematic flow chart diagram 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. The various steps in method 1400 are described in detail below.

S1410, acquiring a first resource.

S1420, the second communication device allocates resources for the first LCH, satisfying the fifth condition.

Optionally, the first LCH is associated with partial full protection.

The first LCH is associated with a partial full reservation, which may include/be understood as one or more of a first RLC entity corresponding to the first LCH is associated with a partial full reservation, or a first RB corresponding to the first LCH is associated with a partial full reservation, or a first LCID corresponding to the first LCH is associated with a partial full reservation, or a first PDCP entity corresponding to the first LCH is associated with a partial full reservation, which embodiments of the present application are not limited.

The fifth condition includes one or more of:

the remaining resources of the first resource or the first resource is 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 is capable of hosting a first data set.

The MAC subheader refers to a subheader of MAC SDUs, each of which includes a subheader.

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

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

It will also be appreciated that the second communication device first performs LCH selection in accordance with LCP restrictions and then allocates resources to LCHs in descending order of LCH priority.

One possible implementation is to perform according to the embodiment shown in fig. 14 if the PDCP entity corresponding to the LCH is partially associated. If the PDCP entity corresponding to the LCH is not associated with partial full reservation, it may be performed according to existing MAC multiplexing or other procedures, which is not limited by the present application.

The second communication device allocates resources for the first LCH, and one possible implementation manner is that the remaining resources of the first resources 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 for the first LCH, in other words, multiplexes the first data set in the first MAC PDU, and at least one data corresponding to the first LCH in the first MAC PDU is integrity-protected data, that is, seventh data.

Another possible implementation manner is that, in a case where the variable corresponding to the first LCH, i.e. the Bj described above is greater than or equal to the size of the first data set, the second communication device allocates resources for the first LCH. Optionally, the variable corresponding to the first LCH is greater than 0.

In another possible implementation manner, the second communication device allocates resources for the first LCH 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 the variable corresponding to the first LCH, that is, the Bj is greater than or equal to the size of the first data set.

Optionally, the second data set includes all data preceding the seventh data; alternatively, the second data set includes all data between the seventh data and the eighth data, wherein the eighth data is integrity-protected data.

It should be noted that, in the embodiment of the present application, the foregoing or the following may be understood in the order in which the RLC layer issues data, for example, all data before the seventh data refers to all data before the seventh data in the data issued by the RLC layer.

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

one possibility is that the second data set comprises all data preceding the seventh data. One or more data which is not subjected to integrity protection may exist before the seventh data, no other data subjected to integrity protection exists, and the seventh data may exist after the seventh data which is subjected to integrity protection or is not subjected to integrity protection, namely, if Bj is greater than or equal to the first data subjected to integrity protection (namely, the seventh data) and the previous data (namely, the second data set) of the first LCH in the MAC multiplexing process, the first LCH is multiplexed in the MAC PDU, so that the MAC PDU can be ensured to contain at least one data subjected to integrity protection for each PDCP entity.

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

That is, the seventh data may further include integrity-protected data (e.g., ninth data), and the remaining resources of the first resource need to accommodate the following data: the seventh data, the ninth data, and the data between the seventh data, so that it can be ensured that at least one integrity-protected data (i.e., the seventh data) is included for each PDCP entity in the MAC PDU. Wherein the data between the ninth data and the seventh data does not include the seventh data and the ninth data.

Another possibility is that the second data set includes all data between the seventh data and the eighth data, in other words, in the MAC multiplexing process, if Bj is greater than or equal to the first integrity-protected data (i.e. the seventh data) and the data between the first integrity-protected data and the second integrity-protected data (i.e. the second data set), the first data set and the second data set are multiplexed in the MAC PDU, so that it can be ensured that each PDCP entity in the MAC PDU contains at least one integrity-protected data.

Optionally, the eighth data is the data after the seventh data for which integrity protection is performed.

The process by which the second communication device allocates resources is described in detail below in connection with specific examples.

One possible design is for the second communication device to allocate resources to ensure that each MAC PDU contains the first MAC SDU for each RB with integrity protection by:

taking a first LCH of the plurality of LCHs as an example, the first LCH is the LCH with the highest priority among the plurality of LCHs, and if Bj is greater than or equal to the data between the first integrity-protected data and the data from the first integrity-protected data to the second integrity-protected data, allocating resources for the first LCH.

Conversely, if Bj is less than the data between the first integrity-protected data and the first integrity-protected data to the second integrity-protected data in the LCH, then the next LCH is determined.

It should be noted that whether the remaining resources can accommodate the data between the first integrity-protected data and the first integrity-protected data to the second integrity-protected data in the first LCH may also be comprehensively considered, in other words, if Bj is greater than or equal to the data between the first integrity-protected data and the first integrity-protected data to the second integrity-protected data in the first LCH, and the remaining resources can accommodate the data between the first integrity-protected data and the first integrity-protected data to the second integrity-protected data in the first LCH, then the resources are allocated to the first LCH.

It should be appreciated that each LCH may be determined sequentially from higher to lower LCH priority according to the above method.

It should also be appreciated that after all LCHs satisfying the condition are determined, if there are remaining resources, the determination is made according to whether the remaining resources can accommodate a set of data (e.g., data preceding the data to be integrity-protected next) in descending order of LCH priorities, without considering Bj.

Another possible design is for the second communication device to allocate resources in such a way that it is guaranteed that each MAC PDU contains one MAC SDU for each RB that is integrity protected (the first one is not required).

Taking a first LCH of the plurality of LCHs as an example, the first LCH is the LCH with the highest priority among the plurality of LCHs, and if Bj is greater than or equal to the first data and the data before the first data in the first LCH, and the remaining resources can accommodate the part of data, allocating resources for the first LCH.

Conversely, if Bj is smaller than the first data and the previous data in the first LCH, then the next LCH is determined.

It should be noted that, whether the remaining resources can accommodate the first completely-protected data and the data before the first completely-protected data in the first LCH may also be comprehensively considered, in other words, if Bj is greater than or equal to the first completely-protected data and the data before the first completely-protected data in the first LCH, and the remaining resources can accommodate the first completely-protected data and the data before the first completely-protected data in the first LCH, then the resources are allocated to the first LCH.

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 in the first data set, the eighth data, and the ninth data are associated with one LCH, i.e., one RB.

Optionally, the method further comprises: the second communication device transmits the MAC PDU.

After the second communication device allocates resources according to the above method, the multiplexed MAC PDU may be sent out.

It should be noted that, in the embodiments described in the present application (for example, the embodiments corresponding to fig. 7, 13, and 14) may be the steps at the same time or may be sequential. For example, S720 and S730 in fig. 7 may be performed simultaneously, or may be sequential, e.g., the first communication device may perform S720 first and then S730; or vice versa, embodiments of the present application are not limited thereto. In addition, the step numbers of the embodiments described in the embodiments of the present application (for example, the embodiments corresponding to fig. 7, 13, and 14) are only an example of the execution flow, and do not limit the execution sequence of the steps, and in the embodiments of the present application, there is no strict execution sequence between the steps that have no time sequence dependency relationship with each other.

It should be noted that, the embodiments described in the present application (for example, the embodiments corresponding to fig. 7, 13, and 14) may be implemented alone or may be implemented in combination (for example, all or part of the schemes referred to in fig. 7 may be combined with the embodiments corresponding to fig. 13), which is not limited in particular.

In addition, currently, the network device may configure the terminal device to perform RLM measurements and/or BFD measurements to monitor the quality of the communication link and/or the communication beam, ensuring communication information. The terminal device may relax RLM measurements and/or BFD measurements in case a certain relaxation criterion is fulfilled, e.g. the terminal device performs RLM measurements and/or BFD measurements with a longer period. However, in the case of releasing RLM measurement and/or BFD measurement, since the terminal device may not monitor the communication link and/or beam quality timely, the terminal device may fail in radio link (radio link failure, RLF) and/or Beam Failure (BF), so how to avoid or reduce the failure of the terminal device due to releasing RLM measurement and/or BFD measurement is a problem to be solved.

In order to solve the problem, the embodiment of the application provides a communication method, which controls the RLM/BFD measurement relaxation behavior of the terminal equipment through the network equipment, so that the network can adjust the strategy of the RLM measurement and/or BFD measurement relaxed by the UE according to the condition of the UE, so as to reduce the probability of failure of the UE in relaxation measurement as much as possible. The above communication method will be described in detail below with reference to fig. 15. As shown in fig. 15, the method includes S1510 to S1550, and each step of fig. 15 will be described in detail below.

It should be understood that the steps shown in fig. 15 are only examples, and should not be construed as limiting the embodiments of the present application in any way. For example, in further embodiments, the communication method may include more or fewer steps than fig. 15, such as not including S1520.

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

The RLM/BFD measurement relaxation configuration information may be used to indicate RLM/BFD measurement relaxation criteria configuration. Wherein the RLM/BFD measurement relaxation criterion is configured for the terminal device to determine whether a condition for relaxing RLM/BFD measurement is fulfilled, the configuration may comprise a quality threshold and/or a duration threshold of the reference signal. In particular, the RLM/BFD measurement relaxation configuration information may include a low mobility criterion (low mobility criterion) configuration and/or a serving cell quality criterion (serving cell quality criterion) configuration.

RLM/BFD measurement relaxation configuration information may also be used to indicate rules for RLM/BFD measurement relaxation. The rule of RLM/BFD measurement relaxation may specifically be that the terminal device (after meeting the RLM/BFD measurement relaxation criterion) may decide whether to perform measurement relaxation or not by itself, or the terminal device (after meeting the RLM/BFD measurement relaxation criterion) needs to determine whether to perform measurement relaxation or not according to the indication information of the network.

For example, if the RLM/BFD measurement relaxation configuration information sent by the network device includes a first field, it indicates that the terminal device (after meeting the RLM/BFD measurement relaxation criterion) needs to determine whether measurement relaxation can be performed according to the indication information of the network. The RLM/BFD measurement relaxation configuration information sent by the network device does not include the first field, which indicates that the terminal device can decide whether to perform measurement relaxation or not by itself after the RLM/BFD measurement relaxation criterion is satisfied.

For another example, the RLM/BFD measurement relaxation configuration information sent by the network device includes a first field, where the first field has at least two values, and if the first field is set to 1, it indicates that the terminal device (after meeting the RLM/BFD measurement relaxation criterion) needs to determine whether measurement relaxation can be performed according to the indication information of the network device; if the first field is set to a value of 2, the terminal device can decide whether to perform measurement relaxation or not by itself after meeting the RLM/BFD measurement relaxation criterion.

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

S1520, the terminal equipment determines that the relaxation criterion is satisfied according to the RLM/BFD measurement relaxation configuration information.

And the terminal equipment evaluates the RLM/BFD measurement relaxation criterion according to the RLM/BFD measurement relaxation configuration information sent by the access network equipment, and determines that the relaxation criterion is met.

Wherein S1520 may be an optional step.

S1530, the terminal equipment determines a measurement relaxation rule according to the RLM/BFD measurement relaxation configuration information.

And the terminal equipment determines the rule of the RLM/BFD measurement relaxation according to the RLM/BFD measurement relaxation configuration information sent by the access network equipment.

The measurement relaxation rule may be that the terminal device (after meeting the RLM/BFD measurement relaxation criterion) may decide whether to perform measurement relaxation or not by itself, or the terminal device (after meeting the RLM/BFD measurement relaxation criterion) needs to determine whether to perform measurement relaxation or not according to the indication information of the network.

S1540a, if the measurement relaxation rule is that the terminal device (after meeting the RLM/BFD measurement relaxation criterion) can decide by itself whether to perform measurement relaxation or not, the terminal device relaxes the RLM/BFD measurement.

In particular, the terminal device may relax the RLM measurement and/or the BFD measurement if a relaxation criterion is met. The specific manner of relaxing the RLM measurement and/or the BFD measurement may be that the terminal device increases a measurement period of the RLM measurement and/or the BFD measurement, increases an indication and/or a reporting period of the RLM measurement and/or the BFD measurement, or decreases the number of reference signals of the RLM measurement and/or the BFD measurement, and so on.

S1540b, if the measurement relaxation rule is that the terminal device (after meeting the RLM/BFD measurement relaxation criterion) needs to determine whether measurement relaxation can be performed according to the indication information of the network, the terminal device determines to relax or not relax the RLM/BFD measurement.

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

In particular, the network device indicates that relaxation is allowed, or the network device does not (within a certain time) indicate that relaxation is not allowed, and the terminal device may perform measurement relaxation. The network device indicates that relaxation is not allowed, or the network device does not indicate that relaxation is allowed, the terminal device does not make measurement relaxation.

S1550, the network equipment sends indication information to the terminal equipment.

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

In particular, the indication information may be an indication that the terminal device is allowed to make measurement relaxation or an indication that the terminal device is not allowed to make 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 the embodiments. These steps or operations are merely examples, and embodiments of the present application may perform other operations or variations of the various operations. Furthermore, the various steps may be performed in a different order than presented in the various embodiments, and it is possible that not all of the operations in the embodiments of the application may be performed. The sequence number of each step does not mean the sequence of execution sequence, and the execution sequence of each process should be determined by its function and internal logic, and should not be limited in any way to the implementation process of the embodiment of the present application.

It should be appreciated that embodiments of the present application may also be applied to other types of measurement relaxation. For example, radio resource management (Radio Resource Management, RRM) measurements. Logic conforming to the above embodiments is also within the scope of the present application.

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

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

The apparatus 1600 may be configured to implement the functionality of the first communication device in the method embodiment illustrated in fig. 7, or the apparatus 1600 may include a module configured to implement any of the functionality or operation of the first communication device in the method embodiment illustrated in fig. 7, which may be implemented in whole or in part in software, hardware, firmware, or any combination thereof. The apparatus 1600 may be configured to implement the functionality of the first communication device in the method embodiment illustrated in fig. 13, or the apparatus 1600 may include modules configured to implement any of the functionality or operations of the first communication device in the method embodiment illustrated in fig. 13, which may be implemented in whole or in part in software, hardware, firmware, or any combination thereof. The apparatus 1600 may be used to implement the functionality of the second communication device in the method embodiment shown in fig. 13, or the apparatus 1600 may include modules for implementing any of the functionality or operations of the second communication device in the method embodiment shown in fig. 13, which may be implemented in whole or in part in software, hardware, firmware, or any combination thereof. The apparatus 1600 may be used to implement the functionality of the second communication device in the method embodiment shown in fig. 14, or the apparatus 1600 may include modules for implementing any of the functionality or operations of the second communication device in the method embodiment shown in fig. 14, which may be implemented in whole or in part in software, hardware, firmware, or any combination thereof.

Illustratively, when the apparatus 1600 is configured to implement the functionality of the first communication device in the method embodiment shown in fig. 7, the transceiver unit 1620 may be configured to obtain first data, where the first data is data that is not integrity protected, and the first data is associated with the first MAC PDU and is associated with the first PDCP entity; the processing unit 1610 may be configured to satisfy a first condition, discard the first data, the first condition comprising one or more of: a second data integrity check failure, the second data associated with the first MAC PDU and with the first PDCP entity; a third data integrity check failure, the third data associated with the first MAC PDU and with a second PDCP entity; a fourth data integrity check failure, the fourth data associated with the second MAC PDU and with the first PDCP entity; the fifth data integrity check fails, the fifth data being associated with a second MAC PDU and with a second PDCP entity; alternatively, the sixth data integrity check fails, the sixth data is associated with the second MAC PDU and with the third PDCP entity.

Illustratively, when the apparatus 1600 is configured to implement the function of the first communications device in the method embodiment shown in fig. 13, the processing unit 1610 may be configured to generate seventh indication information, where the seventh indication information is used to indicate a proportion of data for adjusting the integrity protection, and the transceiver unit 1620 may be configured to send the seventh indication information.

Illustratively, when the apparatus 1600 is configured to implement the function of the second communications device in the method embodiment shown in fig. 13, the transceiver unit 1620 may be configured to receive the seventh indication information, and the processing unit 1610 may be configured to adjust the proportion of the integrity-protected data based on the seventh indication information.

Illustratively, when the apparatus 1600 is configured to implement the functionality of the second communications device in the method embodiment shown in fig. 14, the processing unit 1610 may be configured to obtain the first resource; a fifth condition is satisfied, allocating resources for a first logical channel, the first LCH being associated with partial full protection, wherein the fifth condition comprises one or more of: 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 data set comprises seventh data, or the first data set comprises seventh data and second data set, wherein the seventh data is integrity protected data and the second data set comprises at least one data, and the at least one data is not integrity protected data.

Alternatively, the apparatus 1600 may be used to implement the functions of the terminal device in the method embodiment shown in fig. 15, or the apparatus 1600 may include modules for implementing any functions or operations of the terminal device in the method embodiment shown in fig. 15, which may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. The apparatus 1600 may also be used to implement the functionality of the network device in the method embodiment shown in fig. 15, or the apparatus 1600 may include modules for implementing any of the functions or operations of the network device in the method embodiment shown in fig. 15, which may be implemented in whole or in part in software, hardware, firmware, or any combination thereof.

The above-mentioned processing unit 1610 and the transceiver unit 1620 may be directly described with reference to the related descriptions in the method embodiments shown in fig. 7, 13, 14 or 15, which are not described herein.

It should be understood that the division of the units in the embodiment of the present application is schematic, only one logic function is divided, and another division manner may be implemented in practice. In addition, each functional unit in the embodiments of the present application may be integrated in one processor, or may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

Fig. 17 is another schematic block diagram of a communication apparatus 1700 provided by an embodiment of the present application. The apparatus 1700 may be a chip system or may be an apparatus configured with a chip system for implementing the communication function in the above-described method embodiment. In the embodiment of the application, the chip system can be formed by a chip, and can also comprise the chip and other discrete devices.

As shown in fig. 17, the apparatus 1700 may include a processor 1710 and a communication interface 1720. Wherein communication interface 1720 may be used to communicate with other devices via a transmission medium such that apparatus 1700 may 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 performing a transceiving function. The processor 1710 can input and output data using the communication interface 1720 and can be used to implement the methods described in the corresponding embodiments of fig. 7, 13, 14, or 15. For example, the apparatus 1700 may be configured to implement the functionality of the first communication device or the second communication device of the method embodiment described above.

When the apparatus 1700 is used to implement the method shown in fig. 7, 13, 14 or 15, the processor 1610 is used to implement the functions of the processing unit 1610, and the communication interface 1720 is used to implement the functions of the transceiver unit 1620.

Optionally, the apparatus 1700 further comprises at least one memory 1730 for storing program instructions and/or data. Memory 1730 is coupled to processor 1710. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which may be in electrical, mechanical, or other forms for information interaction between the devices, units, or modules. Processor 1710 may operate in conjunction 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 specific connection medium between the processor 1710, the communication interface 1720, and the memory 1730 is not limited in the embodiment of the present application. In fig. 17, the processor 1710, the communication interface 1720, and the memory 1730 are connected to each other by a bus 1740 according to an embodiment of the present application. Bus 1740 is shown in bold lines in fig. 17, and the manner in which the other components are connected is illustrated only schematically and not by way of limitation. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 17, but not only one bus or one type of bus.

Fig. 18 is a schematic structural diagram of a network device provided in an embodiment of the present application, for example, may be a schematic structural diagram of a base station. As shown in fig. 18, the base station 1800 may include one or more radio frequency units, such as a remote radio frequency unit (remote radio unit, RRU) 1810 and one or more baseband units (BBU) (also referred to as a Distributed Unit (DU)) 1820. The RRU1810 may be referred to as a transceiver unit, and corresponds to the transceiver unit 1620 in fig. 16. Alternatively, the RRU1810 may also be referred to as a transceiver, transceiving circuitry, or transceiver, etc., which may include at least one antenna 1811 and a radio frequency unit 1812. Alternatively, the RRU1810 may include a receiving unit, which may correspond to a receiver (or receiver, receiving circuit), and a transmitting unit, which may correspond to a transmitter (or transmitter, transmitting circuit). The RRU1810 is mainly used for receiving and transmitting radio frequency signals and converting radio frequency signals into baseband signals, for example, for transmitting configuration information to a terminal device. The BBU1820 portion is mainly configured to perform baseband processing, control a base station, and the like. The RRU1810 and BBU1820 may be physically located together or physically separate, i.e., distributed base stations.

The BBU 1820 is a control center of the base station, and may also be referred to as a processing unit, and may correspond to the processing unit 1610 in fig. 16, and is mainly configured to perform baseband processing functions, such as channel coding, multiplexing, modulation, spreading, and so on. For example, the BBU (processing unit) may be configured to control the base station to perform the operation procedures described in the above method embodiments with respect to the network device.

In one example, the BBU 1820 may be configured by one or more boards, where the multiple boards may support a single access radio access network (such as an LTE network) together, or may support different access radio access networks (such as an LTE network, a 5G network, or other networks) respectively. 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 configured to control the base station to perform necessary actions, for example, to control the base station to perform the operational procedures described above with respect to the network device in the method embodiments. The memory 1821 and processor 1822 may serve one or more boards. That is, the memory and the processor may be separately provided on each board. It is also possible that multiple boards share the same memory and processor. In addition, each single board can be provided with necessary circuits.

It should be appreciated that the base station 1800 shown in fig. 18 is capable of implementing the methods described in the embodiments shown in fig. 7, 13, 14 or 15. The operations and/or functions of the various modules in the base station 1800 are respectively for implementing the respective flows in the method embodiments described above. Reference is specifically made to the description in the above method embodiments, and detailed descriptions are omitted here as appropriate to avoid repetition.

Fig. 19 is a schematic structural diagram of a terminal device according to an embodiment of the present application. The terminal device 1900 may be used to implement the methods described in the embodiments shown in fig. 7, 13, 14 or 15, and the terminal device 1900 may be applied in the communication system 600 shown in fig. 6. As shown in fig. 19, the terminal device 1900 includes a processor 1901 and a transceiver 1902. Optionally, the terminal device 1900 further comprises a memory 1903. The processor 1901, the transceiver 1902 and the memory 1903 may communicate with each other via an internal connection path to transmit control and/or data signals, the memory 1903 is used for storing a computer program, and the processor 1901 is used for calling and running the computer program from the memory 1903 to control the transceiver 1902 to transmit and receive signals. Optionally, the terminal device 1900 may further include an antenna 1904 for transmitting uplink data or uplink control signaling output by the transceiver 1902 through a wireless signal. Optionally, the terminal device 1900 further comprises a Wi-Fi module 1911 for accessing the wireless network.

The processor 1901 and the memory 1903 may be combined into one processing device, and the processor 1901 is configured to execute program codes stored in the memory 1903 to realize the functions. In particular, the memory 1903 may also be integrated into the processor 1901 or separate from the processor 1901. The processor 1901 may correspond to the processing unit 1610 in fig. 16 or the processor 1710 in fig. 17.

The 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 circuitry) and a transmitter (or transmitter, transmitting circuitry). Wherein the receiver is for receiving signals and the transmitter is for transmitting signals.

Optionally, the terminal device 1900 may also include a power supply 1905 for providing 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 further include one or more of an input unit 1906, a display unit 1907, an audio circuit 1908, a camera 1909, a sensor 1910, and the like, and the audio circuit may further include a speaker 1908a, a microphone 1908b, and the like.

It should be appreciated that the terminal device 1900 shown in fig. 19 is capable of implementing the various processes involving the terminal device in the method embodiments shown in fig. 7, 13, 14, or 15. The operations and/or functions of the respective modules in the terminal device 1900 are respectively for implementing the corresponding flows in the above-described method embodiment. Reference is specifically made to the description in the above method embodiments, and detailed descriptions are omitted here as appropriate to avoid repetition.

When terminal device 1900 is used to perform the operational flow described in the method embodiments above involving the terminal device, processor 1901 may be used to perform the actions described in the method embodiments above as being performed internally by the terminal device, while transceiver 1902 may be used to perform the actions described in the method embodiments above as being transmitted to or received from the network device by the terminal device. Please refer to the description of the foregoing method embodiments, and details are not repeated herein.

The present application also provides a computer program product comprising: a computer program (also referred to as code, or instructions), when executed, causes a computer to perform the method of any of the embodiments shown in fig. 7, 13, 14 or 15.

The present application also provides a computer-readable storage medium storing a computer program (which may also be referred to as code, or instructions). The computer program, when executed, causes a computer to implement the method of any of the embodiments shown in fig. 7, 13, 14 or 15.

The embodiment of the application provides a communication system, which comprises a first communication device and a second communication device.

It should be appreciated that the processor in embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It should also be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

The terms "unit," "module," and the like as used in this specification may be used to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. The units and the modules in the embodiment of the application have the same meaning and can be used in a crossed way.

Those of ordinary skill in the art will appreciate that the various illustrative logical blocks (illustrative logical block) and steps (steps) described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application. In the several embodiments provided by the present application, it should be understood that the disclosed apparatus, device and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

In the above-described embodiments, the functions of the respective functional units may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, 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 according to the embodiments of the present application are fully or partially produced. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). 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 an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital versatile disk (digital video disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A communication method applied to a first communication device, the method comprising:

acquiring first data, which is data without integrity protection, the first data being associated with a first media access control, MAC, protocol data unit, PDU, and with a first packet data convergence protocol, PDCP, entity;

discarding the first data if a first condition is satisfied, the first condition comprising one or more of:

a second data integrity check failure, the second data associated with the first MAC PDU and with the first PDCP entity;

a third data integrity check failure, the third data associated with the first MAC PDU and with a second PDCP entity;

a fourth data integrity check failure, the fourth data associated with a second MAC PDU and with the first PDCP entity;

a fifth data integrity check failure, the fifth data associated with the second MAC PDU and with the second PDCP entity; or,

a sixth data integrity check fails, the sixth data being associated with the second MAC PDU and with a third PDCP entity.

2. The method of claim 1, wherein 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 a different MAC PDU.

3. The method of claim 1 or 2, wherein the method further comprises:

discarding one or more of the second data, the third data, the fourth data, the fifth data, or the sixth data.

4. A method according to any one of claims 1 to 3, wherein the method further comprises:

in the case that the second condition is satisfied, not discarding the first data; wherein,

the second condition includes one or more of:

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 of any one of claims 1 to 4, wherein the method further comprises:

determining that at least one of the first data, the second data, or the third data is associated with the first MAC PDU according to first indication information from a MAC layer of the first communication device; and/or the number of the groups of groups,

Determining 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 from a MAC layer of the first communication device.

6. The method of claim 5, wherein the first indication information includes numbering information corresponding to at least one of the first data, the second data, or the third data; and/or the second indication information comprises number information corresponding to at least one of the fourth data, the fifth data or the sixth data.

7. The method of any one of claims 1 to 6, wherein the method further comprises:

determining 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 associated with a different MAC PDU based on third indication information from a radio link control RLC layer of the first communication device.

8. The method of any one of claims 1 to 7, further comprising one or more of:

Determining that the third data integrity check fails or succeeds based on fourth indication information from the second PDCP entity;

determining that the fifth data integrity check fails or succeeds based on fifth indication information from the second PDCP entity; or,

and determining that the sixth data integrity check fails or succeeds based on sixth indication information from the third PDCP entity.

9. The method of any one of claims 1 to 8, wherein the method further comprises:

and sending seventh indication information to the second communication device, wherein the seventh indication information is used for indicating the proportion of the data for adjusting the integrity protection.

10. The method of claim 9, wherein the seventh indication information indicates a proportion of data to tune up the integrity protection if a third condition is satisfied, wherein the third condition includes one or more of:

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

And/or the number of the groups of groups,

the seventh indication information indicates a proportion of the data of the reduced integrity protection if a fourth condition is satisfied, wherein the fourth condition includes one or more of:

the number of the received MAC PDUs is greater than or equal to a fifth threshold, where the received MAC PDUs include data that is integrity protected.

11. The method of claim 10, wherein the number of integrity check failures is determined according to any one of:

the number of PDCP PDUs failing the integrity check; or,

the number of MAC PDUs including PDCP PDUs for which the integrity check failed.

12. The method of claim 11, wherein the number of PDCP PDUs for which the integrity check failed is associated with one PDCP entity; or,

the PDCP PDUs for which the integrity check fails in the number of MAC PDUs including the PDCP PDUs for which the integrity check fails are associated with one PDCP entity.

13. The method according to any of claims 10 to 12, wherein the number of successful integrity checks is determined according to any of the following:

The number of PDCP PDUs for which the integrity check is successful; or,

the number of MAC PDUs including PDCP PDUs for which the integrity check was successful.

14. The method of claim 13, wherein the number of PDCP PDUs for which the integrity check was successful is associated with one PDCP entity; or,

the successfully-checked PDCP PDUs of the number of MAC PDUs including the successfully-checked PDCP PDUs are associated with one PDCP entity.

15. The method of any of claims 9 to 14, wherein the seventh indication information is associated with one PDCP entity.

16. A communication device, comprising:

a transceiver unit, configured to obtain first data, where the first data is data that is not integrity protected, and the first data is associated with a first media access control MAC protocol data unit PDU and is associated with a first packet data convergence protocol PDCP entity;

a processing unit configured to satisfy a first condition, and discard the first data, where the first condition includes one or more of:

17. The apparatus of claim 16, wherein 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 a different MAC PDU.

18. The apparatus of claim 16 or 17, wherein the processing unit is further to discard one or more of the second data, the third data, the fourth data, the fifth data, or the sixth data.

19. The apparatus of any one of claims 16 to 18, wherein the processing unit is further configured to not discard the first data if a second condition is met; wherein,

The second condition includes one or more of:

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 apparatus of any one of claims 16 to 19, wherein the processing unit is further configured to determine that at least one of the first data, the second data, or the third data is associated with the first MAC PDU based on first indication information from a MAC layer of the apparatus; and/or the number of the groups of groups,

determining 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 from a MAC layer of the apparatus.

21. The apparatus of claim 20, wherein the first indication information comprises numbering information corresponding to at least one of the first data, the second data, or the third data; and/or the second indication information comprises number information corresponding to at least one of the fourth data, the fifth data or the sixth data.

22. The apparatus of any of claims 16-21, wherein the processing unit is further configured to 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 associated with a different MAC PDU based on third indication information from a radio link control, RLC, layer of the apparatus.

23. The apparatus of any one of claims 16 to 22, wherein the processing unit is further to perform one or more of:

24. The apparatus according to any of claims 16 to 23, wherein the processing unit is further configured to send seventh indication information, the seventh indication information being configured to indicate a proportion of data for adjusting the integrity protection.

25. The apparatus of claim 24, wherein the device comprises,

the seventh indication information indicates a proportion of data of the integrity protection is turned up if a third condition is satisfied, wherein the third condition includes one or more of:

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

26. The apparatus of claim 25, wherein the number of integrity check failures is determined according to any one of:

the number of PDCP PDUs failing the integrity check; or,

27. The apparatus of claim 26, wherein the number of PDCP PDUs for which the integrity check failed is associated with one PDCP entity; or,

28. The apparatus of any of claims 25 to 27, wherein the number of successful integrity checks is determined according to any of:

the number of PDCP PDUs for which the integrity check is successful; or,

29. The apparatus of claim 28, wherein the number of PDCP PDUs for which the integrity check was successful is associated with one PDCP entity; or,

30. The apparatus of any of claims 24 to 29, wherein the seventh indication information is associated with one PDCP entity.

31. A communications device comprising a processor and a memory, the processor and the memory being coupled, the processor being configured to control the device to implement the method of any one of claims 1 to 15.

32. A computer readable storage medium, characterized in that the storage medium has stored therein a computer program or instructions which, when executed by a computer, implement the method of any of claims 1 to 15.

33. A computer program product comprising instructions which, when executed by a computer, implement the method of any one of claims 1 to 15.