Communication method and apparatus
By using dedicated signaling radio bearers and data packet encryption, combined with the compression or removal of the non-access stratum header, the problem of excessively large voice data packet headers is solved, achieving resource savings and improved security.
Patent Information
- Application Number
- PCT/CN2025/145440
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2025-12-25
- Publication Date
- 2026-11-12
AI Technical Summary
In IP multimedia subsystems, voice data packets have large headers, resulting in a small proportion of effective data and wasting transmission resources.
By using dedicated signaling radio bearers or messages for transmitting voice data, the addition of a radio resource control header at the radio resource control layer is avoided. This is combined with packet encryption and compression or removal of non-access stratum headers to reduce header overhead.
It effectively reduces the proportion of packet headers in data packets, saves transmission resources, and improves transmission efficiency and security.
Smart Images

Figure CN2025145440_12112026_PF_FP_ABST
Abstract
Description
A communication method and apparatus
[0001] Cross-references to related applications
[0002] This application claims priority to Chinese Patent Application No. 202510602336.3, filed on May 9, 2025, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field
[0003] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology
[0004] For Internet Protocol (IP) Multimedia Subsystem (IMS) data packets, the header may be large, resulting in a smaller proportion of valid data being transmitted during packet transmission.
[0005] Take voice data packets as an example. After the voice data is encoded at the sending end, each protocol layer that the voice data passes through adds a corresponding header, resulting in a large header for the final voice data packet. If the amount of voice data is small, the header will occupy a larger proportion of the entire voice data packet. Consequently, when transmitting the voice data packet, the proportion of effective data transmitted is small, and more resources are used to transmit the header, resulting in a waste of transmission resources. Summary of the Invention
[0006] This application provides a communication method and apparatus for reducing the size of packet headers.
[0007] Firstly, a first communication method is provided. This method can be applied to a first device, such as a first communication device. Optionally, the first device may be, for example, a terminal-side device, also referred to as a terminal device or a terminal. The terminal device may be, for example, a terminal equipment, or other equipment including terminal equipment functions, or a circuit, or a system-on-a-chip (or, a chip, such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip) or other functional module, which is capable of implementing the functions of the terminal equipment, and which is, for example, disposed in the terminal equipment. The method includes: a first layer of the first communication device delivering a first data packet to a second layer of the first communication device, wherein the first data packet includes voice data, the first layer is a non-access layer, and the second layer is a radio resource control layer. The second layer transmits a second data packet via a first signaling radio bearer, the second data packet being determined based on the first data packet. Wherein, the first signaling radio bearer is a signaling radio bearer dedicated to transmitting voice data, and the second data packet does not include a radio resource control header, or the first signaling radio bearer adopts a radio resource control pass-through mode, which means that the second layer does not encode the data packets on the first signaling radio bearer; or, the second data packet is included in a first message on the first signaling radio bearer, and the first message is a dedicated control channel message dedicated to transmitting voice data. Optionally, the "deliver" data packet can also be understood or replaced as "send" or "transmit" data packet.
[0008] This application provides a signaling radio bearer or message specifically for transmitting voice data. When transmitting voice data, the signaling radio bearer or message can indicate that the data packet contains voice data. Therefore, it is not necessary to add a radio resource control header to the second data packet, or to increase the overhead of the second data packet at the radio resource control layer. This is beneficial for controlling the proportion of the second data packet header in the second data packet, and can save transmission resources or not increase transmission resources.
[0009] In one optional implementation, the first signaling radio bearer corresponds to a first logical channel, wherein the first signaling radio bearer is a signaling radio bearer dedicated to transmitting voice data, and the identifier of the first logical channel is different from the logical channel identifier corresponding to signaling radio bearer 1, and also different from the logical channel identifier corresponding to the repeating (bis) signaling radio bearer 1. The identifier of the first logical channel can be a newly defined identifier, so that the first logical channel can be determined to be used for transmitting voice data based on the identifier.
[0010] In one optional implementation, the first message is a dedicated control channel message for transmitting voice data. The first message includes at least one reserved bit to indicate that the first data packet includes voice data, or to indicate that the first message is a message dedicated to transmitting voice data. The first message may include at least one bit, which may be an existing bit in the first message. That is, in this embodiment, it is not necessary to add new bits to the first message, thus saving the overhead of the first message.
[0011] In an optional implementation, the method may further include: encrypting the first data packet at a first layer without performing integrity protection. Since voice data is not signaling, this embodiment of the application may not perform integrity protection on the voice data, thereby simplifying the voice data processing flow. However, this embodiment of the application may encrypt the voice data to improve the transmission security of the voice data.
[0012] In one optional implementation, the first data packet includes a first non-access layer header, and the method may further include: a second layer compressing the first non-access layer header to obtain a second non-access layer header. The second data packet may include the second non-access layer header. In this implementation, the second layer of the first communication device can compress the first non-access layer header, thereby saving header overhead on the second data packet. Optionally, the number of bits occupied by the second non-access layer header may be less than the number of bits occupied by the first non-access layer header.
[0013] In one optional implementation, the second non-access layer header includes a sequence number. Optionally, this sequence number may be, for example, a sequence number (SQN), or may have other names; hereinafter, SQN will be used as an example. For the receiving end of the second data packet, appropriate information is needed to decrypt the second data packet, and the SQN can be such decryption information. Therefore, the second non-access layer header may include an SQN, enabling the receiving end of the second data packet to decrypt the second data packet.
[0014] In one alternative implementation, the first data packet includes a first non-access stratum header, and the method may further include: a second layer removing the first non-access stratum header to obtain a second data packet. In this implementation, since the first communication device removes the first non-access stratum header, the second data packet does not include the non-access stratum header, thereby saving more of the header overhead of the second data packet.
[0015] In one optional implementation, the first non-access stratum header includes one or more of the following: SQN, length information, security header type field, first protocol discriminator field, message authentication code, bearer identifier, second protocol discriminator field, procedure processing identifier, or, ESM data transmission message identifier. Optionally, the first non-access stratum header can be a conventional non-access stratum header.
[0016] In one optional implementation, the first non-access stratum header includes a first field indicating that the NAS PDU within the first data packet is encrypted but not protected for integrity. Optionally, the first field may be, for example, a security header type field, or it may be other fields. The indication of the first field clearly shows that the NAS PDU within the first data packet is encrypted but not protected for integrity.
[0017] In one optional implementation, the first non-access stratum header includes a second field, which is either all 0s or all 1s; or, the first non-access stratum header does not include a second field; wherein the second field is used for integrity protection. Optionally, the second field may be, for example, a message authentication code, which can be used for integrity protection. However, in this embodiment, the NAS PDU in the first data packet is encrypted and not protected for integrity; therefore, the message authentication code can be set to a default value, such as all 0s or all 1s, or the message authentication code can be removed to save header overhead.
[0018] In an optional implementation, the method may further include: a first layer determining that the first data packet includes a first non-access layer header based on the fact that the first data packet includes voice data, wherein the first non-access layer header includes an SQN. For example, when the first layer receives or generates the first data packet, it can determine that the first data packet includes voice data, thereby determining that the first data packet includes the first non-access layer header, or determining to add the first non-access layer header to the first data packet.
[0019] In an optional implementation, the method may further include: a first layer determining that the first data packet does not include a non-access layer header based on the fact that the first data packet includes voice data. For example, the first layer may determine that the first data packet includes voice data upon receiving or generating the first data packet, thereby determining that the first data packet does not include a non-access layer header, or determining not to add a non-access layer header to the first data packet.
[0020] In an optional implementation, the method may further include: sending first information indicating an offset between the SQN and the RLC SN of the second data packet. For example, if the first data packet does not include a non-access stratum header, then the second data packet does not include the SQN of the second data packet. The receiving end of the second data packet may need to use the SQN to decrypt the second data packet. Therefore, optionally, the first communication device may send the first information to indicate the offset between the SQN and the RLC SN, so that the receiving end can deduce the SQN based on the offset and the RLC SN.
[0021] Secondly, a second communication method is provided. This method can be applied to a second device, such as a second communication device. Optionally, the second device may be, for example, a network-side device, also referred to as a network device. The network device may be, for example, a network equipment, or other equipment including network equipment functions, or a circuit, or a system-on-a-chip (or chip) or other functional module capable of implementing the functions of the network equipment, and may be, for example, disposed within the network equipment. The network equipment may include, for example, an access network device. The access network device may be, for example, a base station. The network device may be referred to as a first network device. The method includes: receiving a second data packet via a first signaling radio bearer; determining, based on the first signaling radio bearer being a signaling radio bearer dedicated to transmitting voice data, that the second data packet includes voice data, or determining, based on the second data packet being included in a dedicated control channel message dedicated to transmitting voice data.
[0022] In one optional implementation, the first signaling radio bearer corresponds to the first logical channel, wherein the first signaling radio bearer is a signaling radio bearer dedicated to transmitting voice data, and the identifier of the first logical channel is different from the logical channel identifier corresponding to signaling radio bearer 1, and also different from the logical channel identifier corresponding to signaling radio bearer 1bis.
[0023] In one alternative implementation, the first message is a dedicated control channel message for transmitting voice data, wherein at least one bit of reserved state included in the first message is used to indicate that the second data packet includes voice data, or to indicate that the first message is a message dedicated to transmitting voice data.
[0024] In one alternative implementation, the second data packet includes a second non-access stratum header, which is a compressed non-access stratum header; or, the second data packet does not include a non-access stratum header.
[0025] In an alternative implementation, the second data packet does not include a non-access stratum header, and the method may further include: receiving first information, the first information being used to indicate the offset between the SQN of the first data packet and the RLC SN of the first data packet.
[0026] In an optional implementation, the method may further include: the second communication device recovers the non-access layer header of the second data packet at its second layer to obtain a third data packet. The second layer is the Radio Resource Control (RRC) layer, and the third data packet includes a first non-access layer header. The first non-access layer header includes one or more of the following: SQN, length information, security header type field, first protocol discriminator field, message authentication code, bearer identifier, second protocol discriminator field, program processing identifier, or ESM data transmission message identifier; the second layer sends the third data packet. For example, the first communication device compresses the non-access layer header of the first data packet to obtain a second data packet. The second data packet may include the second non-access layer header or may not include it. The second communication device can then recover or decompress the non-access layer header of the second data packet. For example, the second data packet including the recovered or decompressed non-access layer header is referred to as the third data packet. The receiving end of the third data packet receives the third data packet and can then perform decryption or other processing on the third data packet based on the non-access layer header included in the third data packet.
[0027] In one alternative implementation, the security header type field indicates that the NAS PDU within the second data packet is encrypted and not protected for integrity.
[0028] In one alternative implementation, the first non-access stratum header includes a message authentication code, which is either all 0s or all 1s; or, the first non-access stratum header does not include a message authentication code.
[0029] In an optional embodiment, the method may further include: sending a second data packet and first indication information, the first indication information indicating one or more of the following: the second data packet carries voice data; the SQN included in the second data packet includes only the lower N bits; the identifier carried by the EPS corresponding to the second data packet; or, the SQN. Optionally, in this embodiment, the second communication device may not recover or decompress the non-access layer header of the second data packet. That is, if the second data packet includes a compressed non-access layer header (e.g., a second non-access layer header) or does not include a non-access layer header, then the second data packet sent by the second communication device also includes a compressed non-access layer header or does not include a non-access layer header. In this case, the second communication device may also send the first indication information, so that the receiving end of the second data packet can decrypt the second data packet accordingly.
[0030] In one optional implementation, the second data packet includes a first non-access layer header, which includes a SQN. For example, the first layer of the first communication device has already processed the second data packet. The first non-access layer header may be a compressed non-access layer header, or the number of bits occupied by the first non-access layer header may be less than the number of bits occupied by a conventional non-access layer header, thereby reducing the header overhead of the second data packet. The first non-access layer header may include an SQN, allowing the receiving end of the second data packet (e.g., a third communication device) to decrypt the second data packet accordingly.
[0031] Thirdly, a third communication method is provided. This method can be applied to a third device, such as a third communication device. Optionally, the third device is, for example, a network-side device, also referred to as a network device. The network device is, for example, a network equipment, or other equipment including network equipment functions, or a circuit, or a chip system (or chip) or other functional module capable of implementing the functions of the network equipment, and the chip system or functional module is, for example, disposed within the network equipment. The network equipment includes, for example, a core network device. The core network device is, for example, an MME, or other core network equipment. The method includes: receiving a third data packet; determining that the NAS PDU included in the third data packet is encrypted and not protected for integrity.
[0032] In one alternative implementation, the third data packet includes a first non-access stratum header, which includes one or more of the following: SQN, length information, security header type field, first protocol discriminator field, message authentication code, bearer identifier, second protocol discriminator field, program processing identifier, or ESM data transmission message identifier.
[0033] In one optional implementation, determining that the NAS PDU included in the third data packet is encrypted and not protected for integrity includes: determining that the NAS PDU in the third data packet is encrypted and not protected for integrity based on a first field within a first non-access stratum header included in the third data packet. If the third data packet includes, for example, a first non-access stratum header, then the first field can be used to determine that the NAS PDU in the third data packet is encrypted and not protected for integrity. Optionally, the first field may be, for example, a security header type field, or other fields.
[0034] In one alternative implementation, the third data packet includes a first non-access stratum header, which is a compressed non-access stratum header. For example, the first non-access stratum header occupies fewer bits than a conventional non-access stratum header (or an uncompressed non-access stratum header) to save header overhead on the third data packet.
[0035] In one optional implementation, determining that the NAS PDU included in the third data packet is encrypted and not protected for integrity includes: receiving first indication information; and determining, based on the first indication information, that the NAS PDU in the third data packet is encrypted and not protected for integrity. Through the first indication information, even if the third data packet does not include a non-access stratum header, the third communication device can determine that the NAS PDU in the third data packet is encrypted and not protected for integrity.
[0036] In one alternative implementation, the first indication information is used to indicate one or more of the following: the second data packet carries voice data, the SQN included in the second data packet includes only the lower N bits, the identifier of the EPS carried by the second data packet, or the SQN.
[0037] Regarding the technical effects of the second aspect or some of the optional embodiments, refer to the description of the technical effects of the first aspect or corresponding embodiments, and / or refer to the description of the technical effects of the second aspect or corresponding embodiments.
[0038] Fourthly, a fourth communication method is provided. This method can be applied to a third device, such as a third communication device. A description of the third device can be found in the third aspect. The method includes: receiving a fourth data packet, wherein the fourth data packet includes voice data; sending a fifth data packet and second indication information, wherein the fifth data packet is determined based on the fourth data packet, and the second indication information is used to indicate that the fifth data packet includes voice data, or to indicate that the non-access stratum header of the fifth data packet needs to be compressed.
[0039] The third communication device can indicate through the second indication information that the fifth data packet includes voice data, or indicate that the non-access stratum header of the fifth data packet needs to be compressed, so that the receiving end of the fifth data packet can determine that the fifth data packet includes voice data, that is, the receiving end can identify the data type.
[0040] In an optional implementation, the method may further include: the first layer of the second network device encrypts the fourth data packet without performing integrity protection; the first layer is a non-access stratum. Since voice data is not signaling, this embodiment of the application may not perform integrity protection on the voice data, thereby simplifying the voice data processing flow. However, this embodiment of the application may encrypt the voice data to improve the transmission security of the voice data.
[0041] In one optional implementation, the fifth data packet includes a third non-access stratum header, wherein the third non-access stratum header includes a second field, and the second field is all 0s or all 1s; or, the third non-access stratum header does not include a second field; wherein the second field is used for integrity protection. Optionally, the second field is, for example, a message authentication code, which can be used for integrity protection. However, in this embodiment, the NAS PDU in the fifth data packet is encrypted and not protected for integrity, so the message authentication code can be set to a default value, such as all 0s or all 1s, or the message authentication code can be removed to save header overhead.
[0042] Fifthly, a fifth communication method is provided. This method can be applied to a third device, such as a third communication device. For a description of the third device, please refer to the third aspect. The method includes: receiving a fourth data packet, wherein the fourth data packet includes voice data and a fourth non-access layer header, the fourth non-access layer header being a compressed non-access layer header, or the fourth data packet not including a non-access layer header; and transmitting a fifth data packet, the fifth data packet being determined based on the fourth data packet.
[0043] For example, the first layer of the third communication device may add a compressed Non-Access Stratum (NASS) header to the fourth data packet, or may not add a NASS header to the fourth data packet, in order to save on the header overhead of the fourth data packet. The fifth data packet may be, for example, the fourth data packet, or it may be another data packet determined based on the fourth data packet.
[0044] In an optional implementation, the method may further include: the first layer of the third communication device encrypting the fourth data packet without performing integrity protection. Since voice data is not signaling, this embodiment of the application may not perform integrity protection on the voice data, thereby simplifying the voice data processing flow. However, this embodiment of the application may encrypt the voice data to improve the transmission security of the voice data.
[0045] In an optional implementation, the method may further include: sending second indication information, the second indication information indicating one or more of the following: the fifth data packet carries voice data, the SQN included in the fifth data packet includes only the lower N bits, the identifier carried by the EPS corresponding to the fifth data packet, or the SQN. For example, if the fifth data packet does not include a non-access stratum header, the second indication information can enable the receiving end of the fifth data packet to decrypt the fifth data packet, etc.
[0046] A sixth aspect provides a sixth communication method. This method can be applied to a second device, such as a second communication device. A description of the second device is available in the second aspect. The method includes: receiving a fifth data packet; the second layer of the second communication device obtaining a sixth data packet based on the fifth data packet, the sixth data packet including a fourth non-access layer header, or the sixth data packet not including a non-access layer header, wherein the fourth non-access layer header is a compressed non-access layer header; and the second layer transmitting the sixth data packet via a second signaling radio bearer.
[0047] The second communication device can compress the non-access layer header of the fifth data packet to obtain a sixth data packet. The sixth data packet may include or may not include the compressed non-access layer header, thereby saving the header overhead of the sixth data packet.
[0048] In one alternative implementation, the second signaling radio bearer is a signaling radio bearer dedicated to transmitting voice data, and the sixth data packet does not include a radio resource control header, or the second signaling radio bearer is in radio resource control pass-through mode; or, the second signaling radio bearer is signaling radio bearer 1bis or signaling radio bearer 1, and the sixth data packet is included in a third message on the second signaling radio bearer, the third message being a dedicated control channel message dedicated to transmitting voice data.
[0049] In one optional implementation, the second signaling radio bearer corresponds to the second logical channel, wherein the second signaling radio bearer is a signaling radio bearer dedicated to transmitting voice data, and the identifier of the second logical channel is different from the logical channel identifier corresponding to signaling radio bearer 1, and also different from the logical channel identifier corresponding to signaling radio bearer 1bis.
[0050] In one alternative implementation, the dedicated control channel message is a dedicated control channel message for transmitting voice data, wherein the dedicated control channel message includes at least one bit of reserved state to indicate that the sixth data packet includes voice data, or to indicate that the dedicated control channel message is a message dedicated to transmitting voice data.
[0051] In an alternative implementation, the sixth data packet does not include a non-access stratum header, and the method may further include: sending second information indicating the offset between the SQN of the sixth data packet and the RLC SN of the sixth data packet.
[0052] In an alternative implementation, the method may further include: receiving second indication information; and determining, based on the second indication information, that the fifth data packet includes voice data.
[0053] In one alternative implementation, the second indication information is used to indicate that the fifth data packet includes voice data, or to indicate that the non-access layer header of the fifth data packet is compressed.
[0054] Regarding the technical effects of the sixth aspect or various alternative implementations, refer to the description of the technical effects of any of the first to fifth aspects or corresponding implementations.
[0055] A seventh aspect provides a seventh communication method. This method can be applied to a second device, such as a second communication device. A description of the second device can be found in the second aspect. The method includes: receiving a fifth data packet and second indication information; determining, based on the second indication information, that the fifth data packet includes voice data, wherein the second indication information indicates one or more of the following: the fifth data packet carries voice data; the SQN included in the fifth data packet includes only the lower N bits; an identifier carried by the EPS corresponding to the fifth data packet; or, the SQN.
[0056] In an alternative implementation, the method may further include: transmitting a fifth data packet via a second signaling radio bearer.
[0057] In one alternative implementation, the second signaling radio bearer is a signaling radio bearer dedicated to transmitting voice data, and the sixth data packet does not include a radio resource control header, or the second signaling radio bearer is in radio resource control pass-through mode; or, the second signaling radio bearer is signaling radio bearer 1bis or signaling radio bearer 1, and the sixth data packet is included in a third message on the second signaling radio bearer, the third message being a dedicated control channel message dedicated to transmitting voice data.
[0058] In one optional implementation, the second signaling radio bearer corresponds to the second logical channel, wherein the second signaling radio bearer is a signaling radio bearer dedicated to transmitting voice data, and the identifier of the second logical channel is different from the logical channel identifier corresponding to signaling radio bearer 1, and also different from the logical channel identifier corresponding to signaling radio bearer 1bis.
[0059] In one alternative implementation, the dedicated control channel message is a dedicated control channel message for transmitting voice data, wherein the dedicated control channel message includes at least one bit of reserved state to indicate that the sixth data packet includes voice data, or to indicate that the dedicated control channel message is a message dedicated to transmitting voice data.
[0060] In one alternative implementation, the fifth data packet includes a third non-access stratum header, which is a compressed non-access stratum header, or the fifth data packet does not include a non-access stratum header.
[0061] Regarding the technical effects of the seventh aspect or various alternative implementations, refer to the description of the technical effects of any of the first to sixth aspects or corresponding implementations.
[0062] Eighthly, an eighth communication method is provided. This method can be applied to a first device, such as a first communication device. For a description of the first device, please refer to the first aspect. The method includes: receiving a sixth data packet via a second signaling radio bearer; determining that the NAS PDU included in the sixth data packet is encrypted and not protected for integrity.
[0063] In one alternative implementation, the second signaling radio bearer is a signaling radio bearer dedicated to transmitting voice data, and the sixth data packet does not include a radio resource control header, or the second signaling radio bearer is in radio resource control pass-through mode; or, the second signaling radio bearer is signaling radio bearer 1bis or signaling radio bearer 1, and the sixth data packet is included in a third message on the second signaling radio bearer, the third message being a dedicated control channel message dedicated to transmitting voice data.
[0064] In one alternative implementation, determining that the NAS PDU included in the sixth data packet is encrypted and not protected for integrity includes: determining, based on the second signaling radio bearer or the third message, that the NAS PDU included in the sixth data packet is encrypted and not protected for integrity.
[0065] In one optional implementation, the sixth data packet includes a fourth non-access stratum header, or the sixth data packet does not include a non-access stratum header, wherein the fourth non-access stratum header includes an SQN. The method may further include: the second layer of the first communication device recovers the fourth non-access stratum header to obtain a third non-access stratum header, wherein the third non-access stratum header includes one or more of the following: SQN, length information, security header type field, first protocol discriminator field, message authentication code, bearer identifier, second protocol discriminator field, program processing identifier, or ESM data transmission message identifier.
[0066] In one alternative implementation, determining that the NAS PDU included in the sixth data packet is encrypted and not protected for integrity includes: determining that the NAS PDU included in the sixth data packet is encrypted and not protected for integrity based on a security header type field.
[0067] Regarding the technical effects of the eighth aspect or various alternative implementations, refer to the description of the technical effects of any of the first to seventh aspects or corresponding implementations.
[0068] A ninth aspect provides a ninth communication method. This method can be applied to a first apparatus, the description of which can be found in the first aspect. The method includes: transmitting a third MAC PDU, the third MAC PDU including a first RLC PDU, the first RLC PDU being determined according to a third rule, the third rule indicating that the first RLC PDU does not include segmented RLC SDUs.
[0069] In the embodiments of this application, the RLC layer of the first device may not segment the RLC SDU, so that the information used to indicate segmentation may not be included in the RLC header, thus saving the overhead of the RLC header.
[0070] In one alternative implementation, the third MAC PDU does not include the RLC header of the first RLC PDU. In this implementation, since the first RLC PDU does not have an RLC header, header overhead is further saved.
[0071] In one alternative implementation, the transmission mode of the RLC entity corresponding to the third MAC PDU is TM. For example, when the transmission mode of the RLC entity is TM, the first RLC PDU does not have an RLC header.
[0072] In one optional implementation, the number of HARQ processes corresponding to the RLC entity is 1. The RLC sequence number included in the RLC header can be used for RLC layer sorting at the receiver. If the number of HARQ processes is 1, the receiver does not need to sort according to the RLC sequence number. Therefore, when the number of HARQ processes is 1, the first RLC PDU may not have an RLC header to reduce header overhead.
[0073] In one alternative implementation, the third MAC PDU is used to transmit voice data.
[0074] A tenth aspect provides a tenth communication method. This method can be applied to a second device, the description of which can be found in the second aspect. The method includes: receiving a third MAC PDU, the third MAC PDU including a first RLC PDU, the first RLC PDU being determined according to a third rule, the third rule indicating that the first RLC PDU does not include segmented RLC SDUs.
[0075] In one alternative implementation, the third MAC PDU does not include the RLC header of the first RLC PDU.
[0076] In one alternative implementation, the transmission mode of the RLC entity corresponding to the third MAC PDU is TM.
[0077] In one alternative implementation, the number of HARQ processes corresponding to the RLC entity is 1.
[0078] In one alternative implementation, the third MAC PDU is used to transmit voice data.
[0079] For information on the technical effects of the tenth aspect or various alternative embodiments, please refer to the description of the technical effects of the ninth aspect or corresponding embodiments.
[0080] Eleventh aspect, an eleventh communication method is provided. This method can be applied to a first device, the description of which can be found in the first aspect. The method includes: transmitting a first RLC PDU, the first RLC PDU including at least two RLC SDUs, the RLC header of the first RLC PDU including at least one length field, the at least one length field being used to indicate the length of the at least two RLC SDUs, or to indicate the length of the RoHC header included in the at least two RLC SDUs, wherein the number of bits occupied by each length field in some or all of the at least one length field is less than a first threshold.
[0081] In this embodiment of the application, for an RLC PDU that includes cascaded (or aggregated; or set) RLC SDUs, the number of bits occupied by the length field in the RLC header of the RLC PDU can be reduced to save the overhead of the RLC header.
[0082] In one alternative implementation, the first threshold is 11. Alternatively, the first threshold can be any other value, without limitation.
[0083] In an optional implementation, the RLC header further includes first indication information, which indicates the number of bits occupied by each length field. In this implementation, the number of bits occupied by the length field can be variable; for example, in cases of good RoHC compression performance, the length field can be shorter, thereby further reducing header overhead. Since the number of bits occupied by the length field is variable, the RLC header can indicate the number of bits occupied by the length field through the first indication information, allowing the receiving end to determine the number of bits occupied by the length field based on the first indication information.
[0084] In one alternative implementation, each length field occupies fewer bits than the second threshold, and at least one length field is used to indicate the length of the RoHC header included in at least two RLC SDUs; or, each length field occupies more than or equal to the second threshold, and at least one length field is used to indicate the length of at least two RLC SDUs. The length field can indicate either the length of the RoHC header or the length of the RLC SDU, offering greater flexibility. The specific content indicated by the length field can be determined based on the number of bits it occupies, thus avoiding the need for additional information and saving signaling overhead.
[0085] In one optional implementation, the RLC header also includes the RLC sequence number of the first RLC PDU, wherein the number of bits occupied by the RLC sequence number is less than a second threshold. In addition to reducing the number of bits occupied by the length field, this embodiment of the application can also reduce the number of bits occupied by the RLC sequence number, thereby further reducing header overhead.
[0086] In one alternative implementation, the second threshold is 5. Alternatively, it can be any other value, without limitation.
[0087] In one alternative implementation, the RLC header does not include the RLC sequence number of the first RLC PDU. The RLC header may also exclude the RLC sequence number, thereby further reducing header overhead.
[0088] A twelfth aspect provides a twelfth communication method. This method can be applied to a second device, the details of which can be found in the second aspect. The method includes: receiving a first RLC PDU, the first RLC PDU comprising at least two RLC SDUs, the RLC header of the first RLC PDU comprising at least one length field, the at least one length field being used to indicate the length of the at least two RLC SDUs, or to indicate the length of the RoHC header included in the at least two RLC SDUs, wherein the number of bits occupied by each length field in part or all of the at least one length field is less than a first threshold.
[0089] In one alternative implementation, the first threshold is 11.
[0090] In one alternative implementation, the RLC header further includes first indication information for indicating the number of bits occupied by each length field.
[0091] In one alternative implementation, the number of bits occupied by each length field is less than the second threshold, and at least one length field is used to indicate the length of the RoHC header included in at least two RLC SDUs; or, the number of bits occupied by each length field is greater than or equal to the second threshold, and at least one length field is used to indicate the length of at least two RLC SDUs.
[0092] In one alternative implementation, the RLC header also includes the RLC sequence number of the first RLC PDU, wherein the number of bits occupied by the RLC sequence number is less than a second threshold.
[0093] In one alternative implementation, the second threshold is 5.
[0094] In one alternative implementation, the RLC header does not include the RLC serial number of the first RLC PDU.
[0095] For information on the technical effects of the twelfth aspect or various alternative embodiments, please refer to the description of the technical effects of the eleventh aspect or corresponding embodiments.
[0096] In a thirteenth aspect, a thirteenth communication method is provided. This method can be applied to a first apparatus, the description of which is provided in the first aspect. The method includes: transmitting a fifth MAC PDU, the fifth MAC PDU including a first MAC SDU, and the fifth MAC PDU not including the MAC subheader of the first MAC SDU.
[0097] The embodiments of this application do not require adding a MAC subheader to the MAC SDU, thereby significantly reducing the header overhead of the MAC PDU.
[0098] In one alternative implementation, the first MAC SDU is carried on a second resource, which corresponds to an LCID or a data radio bearer. The second resource, for example, corresponds to an LCID or a data radio bearer. The LCID can be the LCID corresponding to the RLC PDU included in the first MAC SDU, and the data radio bearer can be the data radio bearer corresponding to a first logical channel. The first logical channel can be the logical channel corresponding to the RLC PDU included in the first MAC SDU. For the receiving end, once the first MAC SDU is received through the second resource, it can be determined that the first MAC SDU corresponds to the LCID or the data radio bearer. Therefore, the MAC subheader of the first MAC SDU may not include the identifier of the LCID or the data radio bearer, or the MAC subheader of the first MAC SDU may not include any LCID or any data radio bearer identifier. This provides a premise that allows the first MAC SDU to not include a MAC subheader.
[0099] In one alternative implementation, the length of the first MAC SDU is equal to the time-domain length of the second resource. In this implementation, the length of the first MAC SDU can be determined by the receiver based on the time-domain length of the second resource. Therefore, the MAC subheader of the first MAC SDU does not necessarily need to indicate the length of the first MAC SDU, which provides another premise for allowing the first MAC SDU to not include a MAC subheader.
[0100] In one alternative implementation, the transmission mode of the first MAC SDU is TM. For example, when the transmission mode of the first MAC SDU is TM, the first MAC SDU does not include an RLC header.
[0101] In one alternative implementation, the first MAC SDU is carried on a second resource, the second resource having a coding rate less than or equal to 800 bps. Because the coding rate of the second resource is less than or equal to 800 bps, the first device can transmit the first MAC SDU without padding bits on that resource, allowing the length of the first MAC SDU to be equal to the time-domain length used for the second resource.
[0102] In one alternative implementation, the first MAC SDU or the fifth MAC PDU includes voice data.
[0103] The fourteenth aspect provides a fourteenth communication method. This method can be applied to a second device, the description of which can be found in the second aspect. The method includes: receiving a fifth MAC PDU, the fifth MAC PDU including a first MAC SDU, and the fifth MAC PDU not including the MAC subheader of the first MAC SDU.
[0104] In one alternative implementation, the first MAC SDU is carried on a second resource, which corresponds to an LCID or a data radio bearer.
[0105] In one alternative implementation, the length of the first MAC SDU is equal to the temporal length of the second resource.
[0106] In one alternative implementation, the transmission mode of the first MAC SDU is TM.
[0107] In one alternative implementation, the first MAC SDU is carried on a second resource, the second resource having an encoding rate of less than or equal to 800 bps.
[0108] In one alternative implementation, the first MAC SDU or the fifth MAC PDU includes voice data.
[0109] For information on the technical effects of the fourteenth aspect or various alternative embodiments, please refer to the description of the technical effects of the thirteenth aspect or corresponding embodiments.
[0110] The fifteenth aspect provides a fifteenth communication method. This method can be applied to a first device, and a description of the first device can be found in the first aspect. The method includes: transmitting a sixth MAC PDU, the sixth MAC PDU comprising K MAC SDUs, the sixth MAC PDU further comprising K MAC subheaders, the K MAC subheaders corresponding one-to-one with the K MAC SDUs, wherein the remaining MAC subheaders among the K MAC subheaders, excluding the third MAC subheader, do not include an LCID or identifier for a data radio bearer, the third MAC subheader is the MAC subheader of the first MAC SDU among the K MAC SDUs, and the K MAC SDUs all correspond to the same LCID or the same data radio bearer, where K is a positive integer.
[0111] In this embodiment of the application, since the transmission resources and the identifiers of LCID or data radio bearers can have a corresponding relationship, the identifiers of LCID or data radio bearers may not be included in the MAC subheader, so as to reduce the overhead of the MAC subheader.
[0112] In one optional implementation, each of the K MAC sub-headers further includes a length field, which indicates the length of the corresponding MAC SDU or the length of the RoHC header included in the corresponding MAC SDU. The length field in the MAC sub-header can indicate either the length of the MAC SDU or the length of the RoHC header, providing flexibility in indicating the target.
[0113] In one optional implementation, each MAC sub-header further includes first indication information, which indicates the number of bits occupied by the length field. In this implementation, the number of bits occupied by the length field can be variable; for example, in cases of good RoHC compression performance, the length field can be shorter, thereby further reducing header overhead. Since the number of bits occupied by the length field is variable, the MAC sub-header can indicate the number of bits occupied by the length field through the first indication information, allowing the receiving end to determine the number of bits occupied by the length field based on the first indication information.
[0114] In one optional implementation, the length field occupies fewer bits than the fourth threshold, and the length field is used to indicate the length of the RoHC header included in the corresponding MAC SDU; or, the length field occupies more than or equal to the fourth threshold, and the length field is used to indicate the length of the corresponding MAC SDU. The length field can indicate either the length of the RoHC header or the length of the MAC SDU, offering flexibility. The specific content indicated by the length field can be determined based on the number of bits it occupies, thus eliminating the need for additional information and saving signaling overhead.
[0115] In one optional implementation, the third MAC subheader includes an identifier for the LCID or data radio bearer; or, K MAC SDUs are carried on a third resource, the third resource corresponding to an LCID, and the third MAC subheader does not include the identifier for the LCID or data radio bearer. The third MAC subheader may include the identifier for the LCID or data radio bearer, enabling the receiving end to determine the LCID or data radio bearer corresponding to the respective MAC SDU. Alternatively, the third resource may correspond to an LCID or data radio bearer, and the receiving end can determine the LCID or data radio bearer based on the third resource; in this case, the third MAC subheader may not include the identifier for the LCID or data radio bearer to reduce the overhead of the MAC subheader.
[0116] In one optional implementation, in the sixth MAC PDU, K MAC sub-headers and K MAC SDUs form K MAC sub-PDUs, and the K MAC sub-PDUs are adjacent to each other.
[0117] In one optional implementation, any one of the K MAC sub-headers further includes a second field indicating whether a next concatenated MAC SDU with the same LCID or data radio bearer exists. The receiver can determine the existence of a next concatenated MAC SDU based on the second field, thereby improving the decoding accuracy of the receiver.
[0118] In one optional implementation, the bits occupied by the second field belong to the length field in any MAC subheader. The length field is used to indicate the length of the corresponding MAC SDU, or to indicate the length of the RoHC header included in the corresponding MAC SDU. In this implementation, existing bits in the MAC subheader can be reused as the second field, thus avoiding the need to add new bits to the MAC subheader, which is beneficial for compatibility with existing MAC subheader structures.
[0119] In one optional implementation, the sixth MAC PDU further includes a MAC CE and a fourth MAC subheader, wherein the fourth MAC subheader is the MAC subheader of the MAC CE. Both the third and fourth MAC subheaders include second indication information. The second indication information included in the third MAC subheader is a first value, indicating that the first MAC subheader is the MAC subheader of the MAC SDU; the second indication information included in the fourth MAC subheader is a second value, indicating that the second MAC subheader is the MAC subheader of the MAC CE. The sixth MAC PDU may include only the MAC SDU and not the MAC CE, or the sixth MAC PDU may include both the MAC SDU and the MAC CE. When the sixth MAC PDU includes the MAC CE, the third and fourth MAC subheaders may include the second indication information, allowing the receiving end to determine whether the current MAC subheader corresponds to the MAC SDU or the MAC CE based on the value of the second indication information.
[0120] In an alternative implementation, the method may further include receiving second information, the second information being used to indicate K. K may be configured by a network device, or predefined by a protocol, for example.
[0121] In one alternative implementation, the sixth MAC PDU includes voice data.
[0122] The sixteenth aspect provides a sixteenth communication method. This method can be applied to a second device, and a description of the second device can be found in the second aspect. The method includes: receiving a sixth MAC PDU, the sixth MAC PDU comprising K MAC SDUs, the sixth MAC PDU further comprising K MAC subheaders, the K MAC subheaders corresponding one-to-one with the K MAC SDUs, wherein the remaining MAC subheaders among the K MAC subheaders, except for the third MAC subheader, do not include the LCID or the identifier of the data radio bearer, the third MAC subheader is the MAC subheader of the first MAC SDU among the K MAC SDUs, and the K MAC SDUs all correspond to the same LCID or the same data radio bearer, where K is a positive integer.
[0123] In one optional implementation, each of the K MAC subheaders further includes a length field, which is used to indicate the length of the corresponding MAC SDU, or to indicate the length of the RoHC header included in the corresponding MAC SDU.
[0124] In one alternative implementation, each MAC subheader further includes first indication information, which indicates the number of bits occupied by the length field.
[0125] In one alternative implementation, the number of bits occupied by the length field is less than the fourth threshold, and the length field is used to indicate the length of the RoHC header included in the corresponding MAC SDU; or, the number of bits occupied by the length field is greater than or equal to the fourth threshold, and the length field is used to indicate the length of the corresponding MAC SDU.
[0126] In one alternative implementation, the third MAC subheader includes an LCID or an identifier of the data radio bearer; or, K MAC SDUs are carried on a third resource, the third resource corresponding to an LCID, and the third MAC subheader does not include an LCID or an identifier of the data radio bearer.
[0127] In one optional implementation, in the sixth MAC PDU, K MAC sub-headers and K MAC SDUs form K MAC sub-PDUs, and the K MAC sub-PDUs are adjacent to each other.
[0128] In one alternative implementation, any one of the K MAC subheaders further includes a second field indicating whether there is a next cascaded MAC SDU with the same LCID or data radio bearer.
[0129] In one alternative implementation, the bits occupied by the second field belong to the length field in any MAC subheader, the length field being used to indicate the length of the corresponding MAC SDU, or to indicate the length of the RoHC header included in the corresponding MAC SDU.
[0130] In one optional implementation, the sixth MAC PDU further includes a MAC CE and a fourth MAC subheader, the fourth MAC subheader being the MAC subheader of the MAC CE. Both the third MAC subheader and the fourth MAC subheader include second indication information, wherein the second indication information included in the third MAC subheader is a first value, the first value being used to indicate that the first MAC subheader is the MAC subheader of the MAC SDU; the second indication information included in the fourth MAC subheader is a second value, the second value being used to indicate that the second MAC subheader is the MAC subheader of the MAC CE.
[0131] In an alternative implementation, the method may further include: sending a second message, the second message being used to indicate K.
[0132] For information on the technical effects of the sixteenth aspect or various alternative embodiments, please refer to the description of the technical effects of the fifteenth aspect or corresponding embodiments.
[0133] In a seventeenth aspect, a communication device is provided. The communication device may be the first device described in the first, eighth, ninth, eleventh, thirteenth, or fifteenth aspects above. The communication device possesses the functions of the first device described above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the first, eighth, ninth, eleventh, thirteenth, or fifteenth aspects above. These modules, units, or means may be implemented in software, hardware, or a combination of software and hardware. The communication device may be, for example, a terminal device, or other device including terminal device functions, or a chip system (or chip or circuit) or other functional module capable of implementing the functions of a terminal device, and may be, for example, disposed in a terminal device. In an optional implementation, the communication device includes a baseband device and a radio frequency device. In another optional implementation, the communication device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a transceiver module). The transceiver unit is capable of both sending and receiving functions. When the transceiver unit performs the sending function, it can be called a sending unit (sometimes also called a sending module); when the transceiver unit performs the receiving function, it can be called a receiving unit (sometimes also called a receiving module). The sending unit and the receiving unit can be the same functional module, which is called the transceiver unit and can perform both sending and receiving functions; alternatively, the sending unit and the receiving unit can be different functional modules, and the transceiver unit is a collective term for these functional modules.
[0134] In one optional implementation, a processing unit is configured to deliver a first data packet to a second layer of the first device via a first layer of the first device, wherein the first data packet includes voice data, the first layer is a non-access stratum, and the second layer is a radio resource control (RRC) layer; a transceiver unit (or a sending unit) is configured to send a second data packet via a first signaling radio bearer via the second layer, wherein the second data packet is determined based on the first data packet; wherein the first signaling radio bearer is a signaling radio bearer dedicated to sending voice data, the second data packet does not include a RRC header, or the first signaling radio bearer adopts a RRC pass-through mode, the RRC pass-through mode meaning that the second layer does not encode the data packets on the first signaling radio bearer; or, the second data packet is included in a first message on the first signaling radio bearer, the first message being a dedicated control channel message dedicated to sending voice data.
[0135] In one alternative implementation, the transceiver unit (or receiving unit) is configured to receive the sixth data packet via a second signaling radio bearer; the processing unit is configured to determine that the NAS PDU included in the sixth data packet is encrypted and not protected for integrity.
[0136] In one alternative implementation, the transceiver unit (or, the transmitting unit) is configured to transmit a third MAC PDU, the third MAC PDU including a first RLC PDU, the first RLC PDU being determined according to a third rule indicating that the first RLC PDU does not include segmented RLC SDUs.
[0137] In one alternative implementation, the transceiver unit (or, the transmitting unit) is used to transmit a first RLC PDU, the first RLC PDU including at least two RLC SDUs, the RLC header of the first RLC PDU including at least one length field, the at least one length field being used to indicate the length of at least two RLC SDUs, or to indicate the length of the RoHC header included in at least two RLC SDUs, wherein the number of bits occupied by each length field in some or all of the at least one length field is less than a first threshold.
[0138] In one alternative implementation, the transceiver unit (or, the transmitting unit) is configured to transmit a fifth MAC PDU, the fifth MAC PDU including the first MAC SDU, and the fifth MAC PDU not including the MAC subheader of the first MAC SDU.
[0139] In one optional implementation, the transceiver unit (or, the transmitting unit) is used to transmit a sixth MAC PDU, which includes K MAC SDUs and K MAC subheaders. The K MAC subheaders correspond one-to-one with the K MAC SDUs. The remaining MAC subheaders among the K MAC subheaders, except for the third MAC subheader, do not include the LCID or the identifier of the data radio bearer. The third MAC subheader is the MAC subheader of the first MAC SDU among the K MAC SDUs. All K MAC SDUs correspond to the same LCID or the same data radio bearer, and K is a positive integer.
[0140] In an alternative embodiment, the communication device further includes a storage unit (sometimes also called a storage module), and a processing unit is configured to couple with the storage unit and execute programs or instructions in the storage unit to enable the communication device to perform the functions of the first device described in the first aspect, eighth aspect, ninth aspect, eleventh aspect, thirteenth aspect or fifteenth aspect.
[0141] Eighteenthly, a communication device is provided. The communication device may be a second device as described in the second, sixth, seventh, tenth, twelfth, fourteenth, or sixteenth aspects above. The communication device possesses the functions of the aforementioned second device. For example, the communication device may have the functions described in any one of the second, sixth, seventh, tenth, twelfth, fourteenth, or sixteenth aspects above. For example, the communication device includes modules, units, or means corresponding to the operations involved in any one of the second, sixth, seventh, tenth, twelfth, fourteenth, or sixteenth aspects above. These modules, units, or means may be implemented in software, hardware, or a combination of software and hardware. The communication device may be, for example, a network device, or other device including network device functions, or a chip system (or chip or circuit) or other functional module capable of implementing the functions of a network device, and may be, for example, disposed within a network device. In an optional implementation, the communication device includes a baseband device and a radio frequency device. In another alternative implementation, the communication device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a transceiver module). For details on the implementation of the transceiver unit, please refer to the description in aspect seventeen.
[0142] In one optional implementation, the transceiver unit (or receiving unit) is configured to receive the second data packet via a first signaling radio bearer; the processing unit is configured to determine, based on the first signaling radio bearer as a signaling radio bearer dedicated to transmitting voice data, that the second data packet includes voice data, or to determine, based on the fact that the second data packet is included in a dedicated control channel message dedicated to transmitting voice data.
[0143] In one optional implementation, the transceiver unit (or receiving unit) is configured to receive a fifth data packet; the processing unit is configured to obtain a sixth data packet based on the fifth data packet through the second layer of the second device, the sixth data packet including a fourth non-access layer header, or the sixth data packet not including a non-access layer header, wherein the fourth non-access layer header is a compressed non-access layer header; and the transceiver unit (or sending unit) is configured to send the sixth data packet through the second layer on the second signaling radio bearer.
[0144] In one optional implementation, the transceiver unit (or receiving unit) is configured to receive a fifth data packet and second indication information; the processing unit is configured to determine, based on the second indication information, that the fifth data packet includes voice data, wherein the second indication information indicates one or more of the following: the fifth data packet carries voice data, the SQN included in the fifth data packet includes only the lower N bits, the identifier carried by the EPS corresponding to the fifth data packet, or the SQN.
[0145] In one alternative implementation, the transceiver unit (or receiver unit) is configured to receive a third MAC PDU, the third MAC PDU including a first RLC PDU, the first RLC PDU being determined according to a third rule indicating that the first RLC PDU does not include segmented RLC SDUs.
[0146] In one alternative implementation, the transceiver unit (or receiver unit) is configured to receive a first RLC PDU, the first RLC PDU comprising at least two RLC SDUs, the RLC header of the first RLC PDU comprising at least one length field, the at least one length field being used to indicate the length of the at least two RLC SDUs, or to indicate the length of the RoHC header included in the at least two RLC SDUs, wherein the number of bits occupied by each length field in some or all of the at least one length field is less than a first threshold.
[0147] In one alternative implementation, the transceiver unit (or receiver unit) is configured to receive a fifth MAC PDU, the fifth MAC PDU including the first MAC SDU, and the fifth MAC PDU not including the MAC subheader of the first MAC SDU.
[0148] In one optional implementation, the transceiver unit (or receiver unit) is configured to receive a sixth MAC PDU, which includes K MAC SDUs and K MAC subheaders. The K MAC subheaders correspond one-to-one with the K MAC SDUs. The remaining MAC subheaders among the K MAC subheaders, except for the third MAC subheader, do not include the identifier of the LCID or the data radio bearer. The third MAC subheader is the MAC subheader of the first MAC SDU among the K MAC SDUs. All K MAC SDUs correspond to the same LCID or the same data radio bearer, where K is a positive integer.
[0149] In one alternative embodiment, the communication device further includes a storage unit (sometimes also called a storage module), and the processing unit is configured to couple with the storage unit and execute programs or instructions in the storage unit to enable the communication device to perform the functions of the second device described in any one of the second, sixth, seventh, tenth, twelfth, fourteenth, or sixteenth aspects.
[0150] Nineteenthly, a communication device is provided. The communication device may be the third device described in the third, fourth, or fifth aspects above. The communication device possesses the functions of the third device. For example, the communication device has the functions to implement any one of the third, fourth, or fifth aspects above. For example, the communication device includes modules, units, or means corresponding to performing the operations involved in any one of the third, fourth, or fifth aspects above. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware. The communication device may be, for example, a network device, or other device including network device functions, or a chip system (or chip or circuit) or other functional module capable of implementing the functions of a network device. This chip system or functional module may be, for example, disposed within a network device. In one optional implementation, the communication device includes a baseband device and a radio frequency device. In another optional implementation, the communication device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a transceiver module). For details on the implementation of the transceiver unit, please refer to the description in the ninth aspect.
[0151] In one alternative implementation, the transceiver unit (or receiving unit) is configured to receive a third data packet; the processing unit is configured to determine that the NAS PDU included in the third data packet is encrypted and not protected for integrity.
[0152] In one alternative implementation, the transceiver unit (or receiving unit) is configured to receive a fourth data packet, wherein the fourth data packet includes voice data; the transceiver unit (or sending unit) is configured to send a fifth data packet and second indication information, wherein the fifth data packet is determined based on the fourth data packet, and the second indication information is configured to indicate that the fifth data packet includes voice data, or to indicate that the non-access stratum header of the fifth data packet needs to be compressed.
[0153] In one optional implementation, the transceiver unit (or receiving unit) is configured to receive a fourth data packet, wherein the fourth data packet includes voice data and a fourth non-access layer header, the fourth non-access layer header being a compressed non-access layer header, or the fourth data packet not including a non-access layer header; the transceiver unit (or sending unit) is configured to send a fifth data packet, the fifth data packet being determined based on the fourth data packet.
[0154] In an alternative embodiment, the communication device further includes a storage unit (sometimes also called a storage module), and the processing unit is configured to couple with the storage unit and execute programs or instructions in the storage unit to enable the communication device to perform the functions of the third device described in any of the third, fourth, or fifth aspects above.
[0155] In a twentieth aspect, an apparatus is provided, the apparatus comprising a memory and one or more processors. The memory is used to store part or all of a computer program or instructions necessary for implementing the functions involved in any of the first, eighth, ninth, eleventh, thirteenth, or fifteenth aspects described above. The one or more processors are executable to carry out the computer program or instructions, such that, when executed, the apparatus implements the methods in any possible design or implementation of any of the first, eighth, ninth, eleventh, thirteenth, or fifteenth aspects described above.
[0156] In one possible design, the device may further include interface circuitry, through which the processor communicates with other devices or components.
[0157] In one possible design, the device may also include the memory.
[0158] The aforementioned device may be a terminal, or a communication module in the terminal, or a chip in the terminal responsible for communication functions such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module.
[0159] A twenty-first aspect provides an apparatus comprising a memory and one or more processors. The memory is used to store part or all of a computer program or instructions necessary for implementing the functions described in the second, third, fourth, fifth, sixth, seventh, tenth, twelfth, fourteenth, or sixteenth aspects. The one or more processors are executable to carry out the computer program or instructions, which, when executed, cause the apparatus to implement the methods in any possible design or implementation of the second, third, fourth, fifth, sixth, seventh, tenth, twelfth, fourteenth, or sixteenth aspects.
[0160] In one possible design, the device may further include interface circuitry, through which the processor communicates with other devices or components.
[0161] In one possible design, the device may also include the memory.
[0162] The aforementioned device may be a network device, a communication module in a network device, or a chip in a network device that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip that contains a modem module.
[0163] A twenty-second aspect provides a communication system comprising a second device and / or a third device. The second device is configured to perform the method described in any one of the second, third, fourth, fifth, sixth, seventh, tenth, twelfth, fourteenth, or sixteenth aspects; the third device is configured to perform the method described in any one of the third, fourth, or fifth aspects. For example, the second device may be implemented using the device described in the eighteenth or twenty-first aspect; the third device may be implemented using the device described in the nineteenth or twenty-first aspect.
[0164] Optionally, the communication system may further include a first device. The first device is used to perform the methods described in the first, eighth, ninth, eleventh, thirteenth, or fifteenth aspects. For example, the first device may be implemented using the device described in the seventeenth or twentieth aspect.
[0165] In a twenty-third aspect, a computer-readable storage medium is provided for storing a computer program or instructions that, when executed, cause the method performed by the first and / or second and / or third means in the foregoing aspects to be implemented.
[0166] In a twentieth aspect, a computer program product containing instructions is provided, which, when the computer program or instructions are run on a computer, causes the methods described in the above aspects to be implemented.
[0167] In a twenty-fifth aspect, a chip system is provided, including a processor and an interface, the processor being configured to call and execute instructions from the interface to enable the chip system to implement the methods of the above aspects. Attached Figure Description
[0168] Figure 1 is a schematic diagram of the control plane protocol stack;
[0169] Figure 2 shows an example of a voice data packet;
[0170] Figure 3 shows a structural example of a NAS header;
[0171] Figures 4 and 5A to 5C are schematic diagrams of several application scenarios of the embodiments of this application;
[0172] Figures 6-8, 10-14, and 17-18 are flowcharts of several communication methods provided in the embodiments of this application;
[0173] Figure 9 is a structural example of the first NAS head in an embodiment of this application;
[0174] Figure 15 is an example of an RLC header in an embodiment of this application;
[0175] Figure 16 shows another example of the RLC header in the embodiments of this application;
[0176] Figure 19 is an example of K MAC sub-PDUs in an embodiment of this application;
[0177] Figure 20 is an example of a MAC subheader in an embodiment of this application;
[0178] Figure 21 shows another example of the MAC subheader in an embodiment of this application;
[0179] Figure 22 is a schematic diagram of an apparatus provided in an embodiment of this application;
[0180] Figure 23 is a schematic diagram of another device provided in an embodiment of this application. Detailed Implementation
[0181] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings.
[0182] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.
[0183] The ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. Furthermore, the numbering of steps in the various embodiments described in this application is only to distinguish different steps and is not used to limit the order in which the steps are performed.
[0184] The following explanations of some terms or concepts used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.
[0185] In this embodiment of the application, the terminal device is a device with wireless transceiver function, which may be a fixed device, a mobile device, a handheld device (e.g., a mobile phone), a wearable device, an in-vehicle device, or a wireless device (e.g., a communication module, a modem, or a chip system, etc.) built into the above devices. The terminal devices are used to connect people, things, and machines, and can be widely used in various scenarios, including but not limited to the following: satellite communication scenarios, sensing scenarios, cellular communication, non-terrestrial networks (NTN), device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine / machine-type communications (M2M / MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, drones, robots, and terminal devices in indoor commercial scenarios (such as mobile phone screen mirroring, file sharing, and mobile phone to VR glasses). When the terminal equipment is applied to V2X, it can also be called a V2X device, such as a smart car, digital car, unmanned car, driverless car, pilotless car, or automobile, self-driving car, or autonomous car, pure electric vehicle (EV), hybrid electric vehicle (HEV), range-extended electric vehicle (REEV), plug-in hybrid electric vehicle (PHEV), new energy vehicle, or roadside unit (RSU). The terminal equipment can also be a device used in D2D communication, such as an electricity meter or water meter.
[0186] Furthermore, in this embodiment, the terminal device can also be a terminal device in an IoT system. IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.
[0187] The various terminal devices described above, if located in a vehicle (e.g., placed inside or installed inside a vehicle), can all be considered in-vehicle terminal devices, also known as on-board units (OBUs). The terminal device of this application can also be an in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit built into a vehicle as one or more components or units. The vehicle can implement the methods of this application through the built-in in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit.
[0188] The terminal equipment may sometimes be referred to as user equipment (UE), terminal, access station, UE station, remote station, wireless communication equipment, or user device, etc.
[0189] In this application embodiment, the communication device used to implement the terminal device function can be a terminal device, which can be a terminal device or a device capable of supporting the terminal device to implement the function, such as a communication module or chip system. This device can be installed in the terminal device. In the technical solutions provided in this application embodiment, the UE is used as an example to describe the technical solutions provided in this application embodiment.
[0190] The network devices in this application embodiment include, for example, access network devices (or access network elements) and / or core network devices (or core network elements). The access network devices are devices with wireless transceiver capabilities, used to communicate with the terminal devices. The access network devices include, but are not limited to, base stations (base transceiver stations, BTS, Node B, evolved Node B (eNodeB) / eNB, or the next generation Node B (gNodeB) / gNB), transmission reception points (TRPs), base stations evolved from the 3rd generation partnership project (3GPP), access nodes in wireless fidelity (Wi-Fi) systems, wireless relay nodes, wireless backhaul nodes, etc. The base stations can be: macro base stations, micro base stations, pico base stations, small cells, relay stations, etc. Multiple base stations can support networks using the same access technology or networks using different access technologies. A base station can contain one or more co-located or non-co-located transmission and reception points. The access network equipment can also be a radio controller, centralized unit (CU), and / or distributed unit (DU) in a cloud radio access network (CRAN) scenario. The access network equipment can also be a server, etc. In satellite communication systems, the access network equipment can be a satellite, a base station mounted on a satellite, or a gateway station (also called a ground station, earth station, signaling station, gateway, or gateway station). In some scenarios, the network equipment can also be a satellite communication terminal, such as a portable station, a fixed station, a vehicle-mounted or airborne satellite communication terminal. It should be understood that in these scenarios, the satellite communication terminal communicates with the satellite and can act as a micro base station or satellite data station to further provide data interfaces to user equipment accessing the satellite communication terminal. For example, the network equipment in V2X technology can be a roadside unit (RSU). The following explanation of the access network equipment uses a base station as an example. A base station can communicate with a terminal device, or it can communicate with a terminal device through a relay station. A terminal device can communicate with multiple base stations in different access technologies. The core network equipment is used to implement functions such as mobility management, data processing, session management, policy and accounting. The names of the equipment implementing core network functions may differ in systems using different access technologies; this application does not limit this.Taking a 5G system as an example, the core network equipment includes, for example, access and mobility management functions (AMF), session management functions (SMF), policy control functions (PCF), or user plane functions (UPF). Taking a 4G system as an example, the core network equipment includes, for example, a mobility management entity (MME).
[0191] In a CU-DU architecture, or in an open RAN (ORAN) system, access network equipment may include one or more logical network elements such as CU, DU, CU-control plane (CP), CU-user plane (UP), or radio unit (RU). CU and DU can be separate entities or included in the same network element, such as a baseband unit (BBU). RU may be included in radio equipment or radio units, such as remote radio units (RRU), active antenna units (AAU), or remote radio heads (RRH).
[0192] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called an open CU (O-CU), DU can also be called an open DU (O-DU), CU-CP can also be called an open CU-CP (O-CU-CP), CU-UP can also be called an open CU-UP (O-CU-CP), and RU can also be called an open RU (O-RU). For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples in its embodiments. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in the embodiments of this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.
[0193] The CU and DU can be configured according to the protocol layer functions of the wireless network they implement. For example, the CU can be configured to implement the functions of the Packet Data Convergence Protocol (PDCP) layer and above (such as the Radio Resource Control (RRC) layer and / or the Service Data Adaptation Protocol (SDAP) layer); the DU can be configured to implement the functions of protocol layers below the PDCP layer (such as one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, or Physical (PHY) layer). As another example, the CU can be configured to implement the functions of protocol layers above the PDCP layer (such as the RRC and / or SDAP layers), and the DU can be configured to implement the functions of protocol layers below the PDCP layer (such as one or more of the RLC, MAC, or PHY layers).
[0194] The above CU and DU configurations are merely examples; the functions of the CU and DU can be configured as needed. For instance, the CU or DU can be configured to have more protocol layer functions, or only some protocol layer processing functions. For example, some RLC layer functions and protocol layer functions above the RLC layer can be placed in the CU, while the remaining RLC layer functions and protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of the CU or DU can be divided according to service type or other system requirements, such as by latency. Functions that require low latency can be placed in the DU, while functions that do not require low latency can be placed in the CU.
[0195] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.
[0196] In this application embodiment, the communication device used to implement the functions of a network device can be called a network device. This network device can be a network element, a network device, or a device capable of supporting the network device or network element to implement the function, such as a chip system. This device can be installed in the network device. In the technical solutions provided in this application embodiment, the device used to implement the functions of a network device is described as a network device (for example, the device used to implement the functions of an access network device is an access network device, and the device used to implement the functions of a core network device is a core network device).
[0197] The technical features involved in the embodiments of this application are described below.
[0198] Currently, the industry hopes to leverage the modification of narrowband (NB) IoT chips to achieve voice data packet transmission. Current NB IoT transmission includes control plane (CP) and user plane (UP) schemes. For the CP scheme, the main idea is that data packets are transmitted through the control plane protocol stack, which can be seen in Figure 1. In the control plane protocol stack, the UE side includes the non-access stratum (NAS), radio resource control (RRC) layer, PDCP layer, RLC layer, MAC layer, and layer 1 (L1), which is, for example, the physical layer (PHY). The protocol layers for communication between the base station and the UE may include the RRC layer, PDCP layer, RLC layer, MAC layer, and L1; the protocol layers for communication between the base station and the core network (e.g., MME) may include the S1 application protocol (S1-AP), stream control transmission protocol (SCTP), IP, layer 2 (L2), and L1. The core network side may include S1-AP, SCTP, IP, L2, and L1. Before air interface security is activated, the NB-IoT UE does not establish a PDCP entity; messages are directly delivered from the UE's RRC layer to the RLC layer. That is, before air interface security is activated, the UE side in Figure 1 may not include a PDCP layer.
[0199] Figure 1 is merely an example of a control plane protocol stack; other implementations are possible. For instance, a control plane protocol stack may include protocol layers other than those shown in Figure 1, and / or it may not include some or all of the protocol layers shown in Figure 1, and / or it may have other protocol layer divisions and / or arrangement schemes besides those shown in Figure 1, and / or some or all of the protocol layers shown in Figure 1 may have other names. For example, the name of the NAS layer in Figure 1 may change, for example, it may be changed to Extended Non-Access Stratum (ENAS or XNAS), or it may be changed to another name. Besides the name, the functionality of the NAS layer may also change or be extended, without limitation.
[0200] For example, the name of the RRC layer in Figure 1 may be changed, for instance, to Extended Radio Resource Control (ERRC or XRRC), or it may be changed to another name. Besides the name, the function of this RRC layer may also be changed or expanded, without limitation.
[0201] The same applies to other protocol layers, so I won't give many examples.
[0202] For IMS voice packets, after the voice packet is voice encoded at the sending end, each protocol layer that the voice packet passes through adds a corresponding header to the voice packet. For example, refer to Figure 2, which shows an example of a voice packet. For instance, after voice encoding, voice data generates voice packet A, which includes an IP / User Datagram Protocol (UDP) / Real-Time Transport Protocol (RTP) header, with the voice data included as the payload. Voice packet A can be referred to as a NAS Service Data Unit (SDU).
[0203] When voice data packet A arrives at the NAS layer, the NAS layer performs robust header compression (RoHC) on the IP / UDP / RTP header within voice data packet A to obtain the RoHC header. Additionally, the NAS layer can add a NAS header to voice data packet A to obtain voice data packet B. Voice data packet B can be called a NAS protocol data unit (PDU) or an RRC SDU. The structure of the NAS header is shown in Figure 3. The NAS header may include an outer NAS header and an ESM data transport header. The outer NAS header may include the security header type, protocol discriminator, message authentication code, and sequence number (SQN); the ESM data transport header may include the evolved packet system (EPS) bearer identity (EPS bearer ID), protocol discriminator, procedure transaction identity, EPS session management (ESM) data transport message identity, and length of user data container contents.
[0204] The security header type can indicate the encryption and integrity protection status of the current message through different values. The protocol discriminator indicates the layer 3 (L3) message type. The message authentication code can be used for integrity protection. The sequence number can be used to determine the count (COUNT) value, which can be used as input information for encryption and integrity protection. The EPS bearer ID can also be used as input information for encryption and integrity protection. The NAS header occupies a total of 11 bytes.
[0205] When voice data packet B arrives at the RRC layer, the RRC layer processes it accordingly. It adds an RRC header to the data packet B (or encodes it using abstract syntax notation one (ASN.1)). The resulting voice data packet is called voice data packet C. Voice data packet C can be called an RRC PDU or an RLC SDU. The RRC header (or the overhead of the RRC layer) occupies at least one byte. This byte indicates that the message containing voice data packet C carries a dedicated information NAS (dedicatedInfoNAS) container, which includes voice data packet C.
[0206] When voice data packet C arrives at the RLC layer, the RLC layer performs appropriate processing (such as segmentation and concatenation of Long Term Evolution (LTE) RLC entities). The RLC layer then adds an RLC header to the voice data packet C, resulting in a voice data packet called voice data packet D. Voice data packet D can be called an RLC PDU or a MAC SDU.
[0207] When voice data packet D arrives at the MAC layer, the MAC layer performs appropriate processing (e.g., multiplexing resources for data packets from different logical channels, and assembling MAC PDUs). The MAC layer then adds a MAC header to voice data packet D, resulting in voice data packet E. Voice data packet E can be called a MAC PDU. This voice data packet E is then transmitted to the physical layer and sent by the physical layer.
[0208] As can be seen, each protocol layer adds a header before transmission. Since the payload of voice data packets is relatively small, the header occupies a larger proportion of the voice data packet D. For example, if we want to provide voice services via high-orbit satellites, the transmission rate is relatively low due to the long communication distance and significant path loss, such as 1–3 kilobits per second (kbps). To accommodate this transmission rate, the voice coding rate can be reduced, i.e., the coding rate of the original voice data packet payload can be reduced, for example, to 800 bits per second (bps). Refer to Table 1 for the possible transmission overhead of each layer's header in a voice data packet at a coding rate of 800 bps.
[0209] Table 1
[0210] As shown in Table 1, when the encoding rate is 800bps, the headers occupy a large number of bytes, while the payload is only 16 bits. This indicates that when transmitting voice data packets, the proportion of effective data (i.e., the payload) is relatively small, with more resources used for header transmission, resulting in a waste of transmission resources.
[0211] Therefore, in this embodiment of the application, the corresponding header of the first data packet can be reduced, for example, the RRC header and / or NAS header can be reduced, thereby reducing the proportion of the header of the first data packet in the first data packet and saving transmission resources.
[0212] The communication method provided in this application can be applied to 4G communication systems, such as LTE communication systems, and also to 5G communication systems, such as 5G NR communication systems, or to various communication systems evolved after 5G, such as future communication systems. The method provided in this application can also be applied to Bluetooth systems, wireless fidelity (Wi-Fi) systems, long-range radio (LoRa) systems, or vehicle-to-everything (V2X) systems. The method provided in this application can also be applied to sidelink (SL) communication. The method provided in this application can be applied to terrestrial networks (TN); or, the method provided in this application can also be applied to NTN, such as satellite communication systems, for example, transparent satellite architecture, backhaul satellite architecture, or regenerative satellite architecture, etc., without limitation. NTN can be a communication system integrated with other communication systems such as 4G, 5G mobile communication systems, or future communication systems, such as NR NTN, IoT NTN, etc.
[0213] Please refer to Figure 4, which is a schematic diagram of an application scenario according to an embodiment of this application. Figure 4 includes a UE and a network device, which may include access network equipment and / or core network equipment. For example, the UE camps on a cell provided by the network device. The UE may be located on the ground; the network device may be located on the ground or in the air, for example, it may be located on a satellite, a drone, or an aircraft, or the network device may be a satellite, a drone, or an aircraft, etc.
[0214] Please refer to Figures 5A to 5C, which are schematic diagrams of several network architectures of NTN, and also schematic diagrams of several application scenarios of the embodiments of this application. Among them, the architecture in which the UE connects to the terrestrial access network via satellite can be called a transparent satellite architecture (e.g., Figure 5A); the architecture in which the access network equipment is set on the satellite (or the satellite has the function of access network equipment) is called a regenerative satellite architecture or regenerative satellite architecture (e.g., Figure 5B); and the architecture in which the UE connects to the terrestrial access network and then connects to the terrestrial network via satellite can be called a satellite backhaul architecture (e.g., Figure 5C).
[0215] In Figure 5A, the network elements used for transmitting services (such as access network equipment and / or core network equipment) are all located on the ground. The UE accesses the network through the access network equipment located on the ground via satellite, and the satellite has a pass-through function.
[0216] In Figure 5B, the access network equipment is located on a satellite, or the underlying processing module of the access network element is located on a satellite, or the satellite has some or all of the functions of the access network equipment. Besides the access network equipment, other network elements used for service transmission (such as core network equipment) are located on the ground. Alternatively, some or all of the network elements in the core network can also be located on a satellite, or the satellite can have some or all of the functions of the network elements in the core network.
[0217] In Figure 5C, the access network equipment is located on the ground. The UE communicates with the satellite through the ground access network and then connects to the ground network through the satellite.
[0218] Alternatively, the satellites in Figures 5A, 5B, or 5C can be replaced with aerial equipment such as drones or high-altitude aircraft.
[0219] The methods provided in the embodiments of this application are described below with reference to the accompanying drawings. The various embodiments of this application can be applied to LTE systems, such as LTE NTN systems or IoT NTN systems, or other communication systems. In the various embodiments of this application, the "data packet" is, for example, an IoT NTN data packet, which includes, for example, voice data, and may also be referred to as a voice data packet or an IoT NTN voice data packet. In the flowcharts corresponding to the various embodiments of this application, unless otherwise specified, all steps indicated by dashed lines are optional steps.
[0220] The various embodiments described herein can be executed by a UE and a network device. The various embodiments described herein can be applied to the network architecture shown in any of Figures 4, 5A, and 5C. For example, the UE described in the various embodiments of this document can be any of the UEs in Figures 4, 5A, and 5C; the first network device described in the various embodiments of this document can be the network device in Figure 4, or it can be the access network device in any of Figures 5A and 5C; the second network device described in the various embodiments of this document can be a core network device not shown in Figure 4, or it can be the core network device in any of Figures 5A and 5C. Alternatively, the various embodiments of this document can also be executed between UEs, in which case “UE” can be replaced with “UE1”; “first network device” can be replaced with “UE2”; “second network device” can be replaced with “access network device”, or “second network device” can remain a core network device without replacement.
[0221] This application provides several communication methods. Among them, the embodiments shown in Figure 6 and Figure 7 can achieve packet header reduction by processing the Radio Resource Control (RRC) header of the data packet; other embodiments can achieve the same effect by processing the Non-Access Stratum (NAS) header of the data packet.
[0222] Optionally, the Radio Resource Control (RRC) header is, for example, a header added to data packets by the second layer of the protocol layer. Taking the second layer as an example, if it is the RRC layer, then the RRC header would be, for example, an RRC header. Alternatively, if the second layer is not the RRC layer, or if the name of the second layer is not "RRC", then the RRC header can have other names, and there is no limitation on this. The various embodiments of this application are described using the RRC header as an example; that is, "RRC header" in the following text can be replaced with "Radio Resource Control header".
[0223] Optionally, the non-access layer header (NAB) is, for example, the header added to the data packet by the first layer in the protocol layer. Taking the first layer as an example, if it is the NAS layer, then the NAB header would be, for example, the NAS header. Alternatively, if the first layer is not the NAS layer, or if the name of the first layer is not "NAS", then the NAB header can have other names, and there is no limitation on this. The various embodiments of this application are described using the NAS header as an example; that is, "NAS header" in the following text can be replaced with "non-access layer header".
[0224] This application provides a first communication method, please refer to Figure 6, which is a flowchart of the method.
[0225] S601. The first layer of the first communication device submits a first data packet to the second layer of the first communication device. The first data packet may include voice data, for example, the payload of the first data packet includes voice data. Optionally, "submit" can also be replaced or understood as "send" or "transmit". For example, submitting the first data packet to the second layer can also be replaced or understood as the first layer sending or transmitting data packets to the second layer.
[0226] In this embodiment, the first communication device is, for example, a UE or a chip in a UE, and the second communication device is, for example, a first network device or a chip in a first network device; or, the first communication device is, for example, a UE or a chip in a UE, and the second communication device is, for example, another UE or a chip in that other UE. The second communication device is the receiving end of the first data packet.
[0227] Layer 1 and Layer 2 are two protocol layers. Layer 1 can be, for example, a protocol layer corresponding to a first communication device and a third communication device, or a functional layer between the two devices, supporting signaling and / or data transmission. The third communication device can be, for example, a core network device or a chip within that device. Layer 2 can serve as a functional layer between the core network and the UE, supporting signaling and data transmission between them. For example, Layer 1 could be the NAS layer, or it could be another layer; the following explanation uses NAS as the first layer. For an introduction to the NAS layer (e.g., the name of the NAS layer may change), please refer to the previous text.
[0228] The second layer could be a protocol layer corresponding to the first and second communication devices, or a functional layer between them. The second communication device could be an access network device or a chip within that device. For example, the second layer could be the RRC layer, or it could be another protocol layer; the following text will use the RRC layer as an example. For an introduction to the RRC layer (e.g., the name of the RRC layer may change), please refer to the preceding text.
[0229] For example, the NAS layer can generate the first data packet, which can then be delivered to the RRC layer. The first data packet could be, for example, a NAS PDU.
[0230] S601 can be an optional step. Optionally, S601 can also be replaced by the first communication device obtaining or determining the first data packet; or, S601 can also be replaced by the second layer of the first communication device obtaining or determining the first data packet.
[0231] S602, the second layer of the first communication device transmits the second data packet through the first signaling radio bearer. Correspondingly, the second communication device receives the second data packet through the first signaling radio bearer. The second data packet may be determined based on the first data packet. The second data packet may include voice data; for example, the payload of the second data packet includes voice data. In this embodiment, the first data packet and the second data packet may be, for example, the same data packet. The signaling radio bearer in this embodiment may include a first signaling radio bearer on the first communication device side and a first signaling radio bearer on the second communication device side. Optionally, the first signaling radio bearer on the first communication device side and the first signaling radio bearer on the second communication device side may also be considered as the same data transmission channel between the first and second communication devices.
[0232] Signaling radio bearers can be used to transmit signaling between access network equipment and UE, and / or between core network equipment and UE. For example, the signaling radio bearer in the embodiments of this application is called a signaling radio bearer (SRB), or it may have other names. The following description uses an SRB as an example, for instance, the first signaling radio bearer is called the first SRB.
[0233] As a first optional implementation of S602, the first SRB of the first communication device may be an SRB dedicated to transmitting voice data, or a first SRB used to identify voice data, or a first SRB associated with or corresponding to voice data, or a first SRB set up for voice data. Optionally, the first SRB being a dedicated SRB for transmitting voice data can also be understood or replaced as the first SRB being a dedicated SRB for voice data, or an SRB of the first communication device that corresponds only to voice data and not to other data, or an SRB of the first communication device that is only used to transmit voice data and not to transmit other data. Continuing with the example of the second layer being the RRC layer. For example, if the RRC layer determines that the payload of the second data packet includes voice data based on the inter-layer information between the RRC layer and the NAS layer, the second data packet may be sent through the first SRB. Optionally, the RRC layer may determine that the payload of the second data packet includes voice data based on the inter-layer information between the RRC layer and the NAS layer. For example, in addition to submitting the second data packet to the second layer, the NAS layer may also send indication information to the RRC layer, such as indication information A, which indicates that the second data packet includes voice data. The RRC layer can then determine that the second data packet contains voice data based on indication information A. Alternatively, the RRC layer can also determine that the second data packet contains voice data through other means, without limitation on the specific method.
[0234] The first SRB dedicated to transmitting voice data is also called SRB5, or may have other names. The first communication device and the second communication device can each establish a first SRB, and the configuration of the first SRB established by the first communication device can be the same as that of the first SRB established by the second communication device. That is, this application embodiment provides a dedicated SRB for voice data (i.e., the first SRB), and all data transmitted through the first SRB is voice data. Therefore, for the second communication device, it can determine that the first data packet carries voice data based on the first SRB.
[0235] In the first optional implementation of S602, the second data packet may not include an RRC header, or the first SRB may adopt a first transparent transmission mode. The first transparent transmission mode means that the RRC layer does not perform encoding processing (e.g., ASN.1 encoding processing) on the data packet of a certain SRB (e.g., the first SRB), or the RRC layer does not add additional indication information through encoding (e.g., ASN.1 encoding) to enable the RRC layer on the network device side to distinguish different messages.
[0236] Optionally, the first pass-through mode may be, for example, a Radio Resource Control (RRC) pass-through mode. For instance, if the RRC pass-through mode is used at Layer 2, and Layer 2 is an RRC layer, then the RRC pass-through mode can also be called an RRC pass-through mode. Alternatively, if Layer 2 is not an RRC layer, or if the name of Layer 2 is not "RRC", then the RRC pass-through mode can have other names, and there is no limitation on this. The various embodiments of this application are described using the example of a RRC pass-through mode as the first pass-through mode.
[0237] Optionally, for different SRBs, it can be determined whether to adopt the RRC transparent transmission mode. If the second data packet includes an RRC header, or is understood that the RRC message carrying the second data packet is encoded with ASN.1, the RRC header can be used to indicate that the second data packet carries voice data (or the ASN.1 encoding information can indicate that the second data packet carries voice data). Since the first SRB used to transmit the second data packet can already indicate that the second data packet carries voice data, in the first optional implementation of S602, the second data packet may not include an RRC header, or may not be processed with ASN.1 encoding, or may not use ASN.1 encoding to add additional indication information to enable the RRC layer on the network device side to distinguish different messages, or the first SRB can adopt the RRC transparent transmission mode, thereby reducing the packet header overhead of the second data packet. Here, the RRC header can also be understood or replaced by the additional overhead brought by RRC encoding; not adding an RRC header can be replaced or understood as not performing ASN.1 encoding, or not using ASN.1 encoding to add additional indication information to enable the RRC layer on the network device side to distinguish different messages. The following description uses the RRC header as an example.
[0238] In a first optional implementation of S602, the first SRB may correspond to a first logical channel (LC). The logical channel identity (LCID) of the first logical channel may be different from the LCID of the logical channel corresponding to SRB 1, and also different from the LCID of the logical channel corresponding to SRB 1bis. For example, it can be understood that the first logical channel is a new logical channel, and a new LCID has been assigned to this new logical channel. Optionally, since the first SRB is an SRB dedicated to transmitting voice data, it can also be understood that the first logical channel is a logical channel dedicated to transmitting voice data.
[0239] In various embodiments of this application, SRB1 can be used to transmit signaling, for example, for NB IoT UE to transmit signaling under the control plane protocol stack (or under the CP scheme). SRB1bis can be used to transmit data, for example, SRB1bis can be used by NB IoT UE to transmit data under the control plane protocol stack (or under the CP scheme).
[0240] Taking a first data packet as an example, where the first communication device is a UE and the second communication device is a first network device. For instance, the UE's NAS layer can generate the first NAS PDU and submit it to the UE's RRC layer. If the RRC layer determines that the payload included in the first NAS PDU is voice data, it can omit adding an RRC header to the first NAS PDU. The RRC layer can then send the first NAS PDU without an RRC header through the first SRB.
[0241] As a second optional implementation of S602, the second data packet may be included in a first message on the first SRB. The first message may be a message dedicated to transmitting voice data, such as a dedicated control channel message for transmitting voice data. This dedicated control channel may be, for example, a dedicated control channel (DCCH), or it may be another channel. Continuing with the example where the second layer is the RRC layer, for instance, if the RRC layer determines that the second data packet includes voice data, it can send the second data packet through the first message on the first SRB.
[0242] The first message dedicated to transmitting voice data is, for example, an uplink DCCH message-narrowband (UL-DCCH-Message-NB) message. For instance, one possible UL-DCCH-Message-NB message for use as the first message is an IoT NTN Voice Data Transfer message, or it could be any other message. For example, the first message may include a dedicated infoNAS (Information Element, IE). For instance, if the first message only includes this dedicated infoNAS element, the overhead of the first information can be reduced. The second data packet may be included in this dedicated infoNAS element. That is, this application embodiment provides a dedicated message for voice data (i.e., the first message), and all data sent through the first message is voice data. Therefore, for the second communication device, the first message determines that the second data packet carries voice data.
[0243] In the first optional implementation of S602, the first SRB can be a conventional SRB, such as SRB1 or SRB1bis, without limitation.
[0244] In a first optional implementation of S602, the first message may include indication information that indicates the second data packet includes voice data, or indicates that the first message is a message dedicated to sending voice data.
[0245] As an optional implementation, the indication information may occupy at least one bit within the first message, or the indication information may be implemented using at least one bit within the first message. Optionally, the at least one bit may be a bit newly added to the first message, which is equivalent to adding a bit to the first message to indicate voice data in this embodiment, so that the indication does not affect the existing bits of the first message. Alternatively, the at least one bit may be a reserved bit in the first message. This means that this embodiment may use existing and unused bits (i.e., reserved bits) in the first message to indicate voice data, or may use existing and unused reserved states in the first message to indicate voice data, thereby avoiding the need to add new bits to the first message and saving the overhead of the first message. Optionally, the at least one bit may be included in the RRC header of the second data packet. If the at least one bit is a reserved bit in the RRC header, the effect of not increasing the overhead of the RRC header can be achieved.
[0246] Alternatively, the indication information may not be implemented through at least one bit, but in other forms, such as a flag bit within the first message. For example, if the first message includes the flag bit, it may indicate that the data packet included in the first message includes voice data; or, if the first message does not include the flag bit, it may indicate that the data packet included in the first message does not include voice data. This application does not limit the specific implementation of the indication information in its embodiments.
[0247] Taking a first data packet as an example, and the first communication device as a UE, and the second communication device as a first network device. For instance, the UE's NAS layer can generate the first NAS PDU and submit it to the UE's RRC layer. The RRC layer determines that the payload included in the first NAS PDU is voice data, and can then send the first NAS PDU through a first message. The first NAS PDU may include an RRC header, for example, the RRC header may include at least one bit, which may be a newly added bit in the RRC header, a reserved bit in the RRC header, or a reserved state in the ASN.1 encoding of the RRC message (e.g., the RRC message carrying the first data packet).
[0248] Optionally, the method may further include S603, whereby the second communication device determines, based on the first SRB or the first message, that the second data packet includes voice data.
[0249] The second communication device receives the second data packet via the first SRB. It can determine that the second data packet includes voice data based on the fact that the first SRB is dedicated to transmitting voice data, or based on the fact that the first logical channel is dedicated to transmitting voice data, or based on the fact that the first message is dedicated to transmitting voice data. Once the second communication device determines that the second data packet includes voice data, it can process the second data packet accordingly; the specific processing procedure is not limited.
[0250] This application provides an SRB or message specifically for transmitting voice data. When transmitting voice data, the SRB or message can indicate that the data packet contains voice data. Therefore, it is not necessary to add an RRC header to the second data packet, or to add extra overhead to the second data packet at the RRC layer. This is beneficial for controlling the proportion of the second data packet header in the second data packet, and can save transmission resources or not increase transmission resources.
[0251] This application provides a second communication method, please refer to Figure 7, which is a flowchart of the method.
[0252] S701, the third communication device sends a fifth data packet. Correspondingly, the second communication device receives the fifth data packet. The fifth data packet may include voice data; for example, the payload of the fifth data packet may include voice data.
[0253] In this embodiment, the third communication device is, for example, a second network device or a chip within a second network device; the second communication device is, for example, a first network device or a chip within a first network device; and the first communication device is, for example, a UE or a chip within a UE. Alternatively, the third communication device is, for example, a second network device or a chip within a second network device; the second communication device is, for example, a UE or a chip within a UE; and the first communication device is, for example, another UE or a chip within that other UE. The first communication device is the receiver of the first data packet, which is sent from the third communication device and can reach the first communication device via the second communication device. The embodiment shown in FIG6 can be understood as an uplink data transmission process, and the embodiment shown in FIG7 can be understood as a downlink data transmission process.
[0254] Taking the third communication device as an example, the fifth data packet can be generated by the MME, or it can be determined by the MME based on the fourth data packet received from other network elements, such as a serving gateway (SGW) or a packet data network (PDN) gateway (PGW).
[0255] The embodiment shown in Figure 6 can be understood as an uplink data transmission process, and the embodiment shown in Figure 7 can be understood as a downlink data transmission process.
[0256] S702, the second communication device transmits the sixth data packet via the second signaling radio bearer. Correspondingly, the first communication device receives the sixth data packet via the second signaling radio bearer. The sixth data packet may include voice data; for example, the payload of the sixth data packet includes voice data. The sixth data packet may be determined based on the fifth data packet; for example, in this embodiment, the sixth data packet and the fifth data packet may be the same data packet.
[0257] In S702, for example, the second layer of the second communication device can transmit the sixth data packet via the second signaling radio bearer. For a description of the second layer, please refer to the embodiment shown in FIG6. This embodiment also uses the RRC layer as an example of the second layer.
[0258] For an introduction to the signaling radio bearer, please refer to the embodiment shown in Figure 6. This embodiment also takes the signaling radio bearer as an SRB as an example, for example, the second signaling radio bearer is the second SRB.
[0259] As a first optional implementation of S702, the second SRB can be an SRB dedicated to transmitting voice data, or a second SRB used to identify voice data, or a second SRB associated with or corresponding to voice data, or a second SRB set up for voice data. Continuing with the example of the second layer being the RRC layer. For example, if the RRC layer determines that the sixth data packet includes voice data based on received indication information, it can send the sixth data packet via the second SRB. Optionally, the RRC layer can determine that the payload included in the sixth data packet is voice data based on received indication information. For example, in addition to sending the sixth data packet to the second communication device, the third communication device also sends indication information to the second communication device, for example, indicated information B. Indication information B can indicate that the sixth data packet includes voice data, and indication information B can be included in the S1-AP message. Then, the RRC layer of the second communication device can determine that the sixth data packet includes voice data based on indication information B. Alternatively, the second communication device can also determine that the sixth data packet includes voice data through other means; the specific method is not limited.
[0260] In the first optional implementation of S702, the second SRB may correspond to the fourth logical channel. The LCID of the fourth logical channel may be different from the LCID of the logical channel corresponding to SRB 1, and also different from the LCID of the logical channel corresponding to SRB 1bis. For example, it can be understood that the fourth logical channel is a new logical channel, and a new LCID has been assigned to this new logical channel. Optionally, since the second SRB is an SRB dedicated to transmitting voice data, it can also be understood that the fourth logical channel is a logical channel dedicated to transmitting voice data.
[0261] Taking the sixth data packet as the second NAS PDU, and the third communication device as the MME, the second communication device as the access network device, and the first communication device as the UE as an example. For instance, the MME can identify the second NAS PDU and send it to the access network device. If the RRC layer of the access network device determines that the payload included in the second NAS PDU is voice data, it can omit adding an RRC header to the second NAS PDU. The RRC layer can then send the second NAS PDU without an RRC header via the second SRB.
[0262] For more details on the first implementation of S702, please refer to the description of the first implementation of S602 in the embodiment shown in FIG6.
[0263] As a second optional implementation of S702, the sixth data packet may be included in a third message on the second SRB. The third message may be a message dedicated to transmitting voice data, such as a dedicated control channel message for transmitting voice data. This dedicated control channel may be, for example, a DCCH, or other channels. Continuing with the example where the second layer is the RRC layer, for instance, if the RRC layer determines that the sixth data packet includes voice data, it can transmit the sixth data packet via the third message on the second SRB.
[0264] The third message dedicated to transmitting voice data is, for example, a downlink DCCH message-narrowband (DL-DCCH-Message-NB) message. One example of a DL-DCCH-Message-NB message that can serve as the third message is the iotntnVoiceDataTransfer message. Alternatively, the first message can be any other message. For example, the first message may include a dedicatedinfoNAS element; for instance, if the first message only includes this dedicatedinfoNAS element, the overhead of the first message can be reduced. The sixth data packet may be included in this dedicatedinfoNAS element. That is, this application embodiment provides a dedicated message (i.e., the third message) for voice data, and all data sent through the third message is voice data. Therefore, for the first communication device, the sixth data packet carrying voice data can be determined based on the third message.
[0265] In a first optional implementation of S702, the third message may include at least one bit, which may indicate that the sixth data packet includes voice data, or indicate that the third message is a message dedicated to sending voice data. Optionally, the at least one bit may be a bit added to the third message, which is equivalent to adding a bit to the third message to indicate voice data in this embodiment, so that the indication does not affect the existing bits of the third message. Alternatively, the at least one bit may be a reserved bit in the third message. It can be understood that this embodiment can use existing and unused bits (i.e., reserved bits) in the third message to indicate voice data, or can use existing and unused reserved states in the third message to indicate voice data, thereby avoiding the need to add new bits to the third message and saving the overhead of the third message. Optionally, the at least one bit may be included in the RRC header of the sixth data packet. If the at least one bit is a reserved bit in the RRC header, the effect of not increasing the overhead of the RRC header can be achieved.
[0266] Taking the sixth data packet as the second NAS PDU, and the third communication device as the MME, the second communication device as the access network device, and the first communication device as the UE as an example. For instance, the MME can receive the second NAS PDU and send it to the access network device. If the RRC layer of the access network device determines that the payload included in the second NAS PDU is voice data, it can send the second NAS PDU through the third message. The second NAS PDU may include an RRC header, for example, the RRC header may include at least one bit, which may be a newly added bit in the RRC header or a reserved bit in the RRC header.
[0267] For more details on the second implementation of S702, please refer to the description of the second implementation of S602 in the embodiment shown in FIG6.
[0268] Optionally, the method may further include S703, whereby the first communication device determines, based on the second SRB or the third message, that the sixth data packet includes voice data.
[0269] The first communication device receives the sixth data packet via the second SRB. Based on the fact that the second SRB is dedicated to transmitting voice data, it can determine that the sixth data packet includes voice data; alternatively, based on the fact that the second logical channel is dedicated to transmitting voice data, it can determine that the second data packet includes voice data; or based on the fact that the first message is dedicated to transmitting voice data, it can determine that the second data packet includes voice data. Once the second communication device determines that the second data packet includes voice data, it can process the second data packet accordingly, without limiting the specific processing procedure.
[0270] This application provides an SRB or message specifically for transmitting voice data. When transmitting voice data, the SRB or message can indicate that the data packet contains voice data. Therefore, it is not necessary to add an RRC header to the sixth data packet, or to add extra overhead to the sixth data packet at the RRC layer. This is beneficial for controlling the proportion of the header in the sixth data packet, and can save transmission resources or not increase transmission resources.
[0271] This application provides a third communication method, please refer to Figure 8, which is a flowchart of the method.
[0272] S801, the first communication device sends a second data packet. Correspondingly, the second communication device receives the second data packet.
[0273] In this embodiment, the third communication device is, for example, a second network device or a chip within a second network device; the second communication device is, for example, a first network device or a chip within a first network device; and the first communication device is, for example, a UE or a chip within a UE. Alternatively, the third communication device is, for example, a second network device or a chip within a second network device; the second communication device is, for example, a UE or a chip within a UE; and the first communication device is, for example, another UE or a chip within that other UE. The third communication device serves as the receiver of the second data packet, which is sent from the first communication device and can reach the third communication device via the second communication device.
[0274] For example, the first layer of the first communication device can generate a first data packet, which can then deliver the first data packet to the second layer of the first communication device. A description of the first and second layers can be found in the embodiment shown in Figure 6. This embodiment uses a NAS layer as the first layer and an RRC layer as the example. The first data packet may include, for example, a NAS PDU or a NAS PDU. The first data packet may include a first NAS header. The first NAS header may include, for example, one or more of the following: security header type, protocol discriminator, SQN, message authentication code, EPS bearer ID, procedure transaction identity, ESM data transport message identity, or, length of user data container contents. For example, if the first NAS header is a traditional NAS header for data transmission, then the first NAS header may include the above items. A structure of a traditional NAS header can be found in Figure 3, which may occupy approximately 11 bytes.
[0275] Traditional solutions encrypt and protect the integrity of signaling and data transmitted via SRB at the NAS layer. However, this application considers voice data as not being signaling; therefore, optionally, this application may not protect the integrity of voice data. However, to improve data transmission security, voice data can still be encrypted. Therefore, optionally, in this application, the NAS layer may not protect the integrity of the NAS PDU included in the first data packet, but may encrypt the NAS PDU. Alternatively, it can be understood that the NAS PDU included in the first data packet is encrypted but not protected for integrity. Therefore, the transmission of the message authentication code used for integrity verification between the first and second communication devices is redundant, thereby reducing header overhead by saving the transmission of message authentication code information.
[0276] To enable the receiving end of the first data packet (e.g., a third communication device) to decrypt the NAS PDU and / or to know that the NAS PDU does not require integrity verification, the first communication device can indicate that the NAS PDU is encrypted and not protected for integrity in a corresponding manner. For example, one indication method is that the first field in the first NAS header can indicate that the NAS PDU in the first data packet is encrypted and not protected for integrity. The first field is, for example, a security header type, or it could be any other field in the first NAS header. Taking the security header type as an example, the reserved state of the security header type can be used to indicate that the NAS PDU is encrypted and not protected for integrity. For example, the security header type occupies 4 bits, and the reserved state can be any state or value from "1101" to "1111".
[0277] Optionally, the first NAS header may include a second field, which can be used for integrity protection. The second field, for example, is a message authentication code. Since the NAS PDU in the first data packet does not perform integrity protection, the second field can use a default or preset value, such as all 0s or all 1s, thus neither affecting the format of the first NAS header nor rendering the second field invalid. In this case, although the NAS header still contains the message authentication code, the information in the message authentication code does not need to be transmitted between the first and second communication devices. That is, the second communication device does not need to receive the content of this field to determine its information, thereby reducing the consumption of transmission resources.
[0278] Alternatively, the first NAS header may not include the second field. For example, the NAS layer may not add a second field to the first NAS header, or the NAS layer may remove the second field from the first NAS header. In this implementation, the structure of the first NAS header differs from that of a traditional NAS header, and the number of bits occupied by the first NAS header is less than that of a traditional NAS header. For example, refer to Figure 9, which shows an example structure of the first NAS header. Figure 9 uses the example where the second field is the message authentication code; in Figure 9, the first NAS header does not include the message authentication code.
[0279] This application embodiment does not perform integrity protection on the NAS PDU within the first data packet, which simplifies the processing of the NAS PDU by the first or third communication device. Furthermore, the first NAS header may not include the message authentication code, thereby saving the overhead of the first NAS header.
[0280] The RRC layer receives a first data packet from the NAS layer. Since the first data packet contains voice data, the first NAS header can be compressed, resulting in a second NAS header. The RRC layer can obtain a second data packet based on the second NAS header and the first data packet with the first NAS header removed. The second data packet may include the second NAS header. The second NAS header significantly reduces overhead compared to a traditional NAS header; therefore, this embodiment can achieve the effect of reducing the packet header size. For details on how the RRC layer determines that the first data packet contains voice data, please refer to the description of the embodiment shown in Figure 6.
[0281] The second NAS header can be a compressed NAS header. A compressed NAS header can be understood as the second NAS header occupying fewer bits than the traditional NAS header; or, the second NAS header may occupy fewer bits than the NAS header of the first data packet.
[0282] Optionally, in this embodiment, the RRC layer of the first communication device can compress the NAS header to reduce the resources occupied by the second data packet during transmission between the first and second communication devices. Currently, the first NAS header may contain a lot of redundant information, or it can be understood that the settings in the first NAS header are usually related to the transmitted data. The RRC layer can compress or remove this redundant information, thereby reducing the number of bits occupied by the second NAS header. Taking the compression of the message authentication code by the RRC layer as an example, if the first data packet includes voice data, and the NAS PDU in the first data packet is not protected for integrity, and the first NAS header includes a message authentication code, the message authentication code in the first NAS header can be set to a default value (e.g., set by the NAS layer of the first communication device), such as all 0s or all 1s. The RRC layer of the first communication device can compress the first NAS header into a second NAS header; for example, the RRC layer can remove the message authentication code from the first NAS header. When the RRC layer of the second communication device receives the second data packet, it can recover or decompress the second NAS header. For example, it can recover or decompress the header to obtain the message authentication code, which is either all 0s or all 1s. This saves air interface transmission resources and reduces header overhead without losing information. Similarly, one or more pieces of information in the first NAS header, such as the protocol discriminator, EPS bearer ID, and length of user data container contents, can be compressed on the first communication device side based on the current data packet (including voice data), and then recovered on the second or third communication device side, further reducing header overhead.
[0283] For example, if the first NAS header occupies 11 bytes, the second NAS header can occupy less than 11 bytes. For instance, the second NAS header might include the Security Header Type (SQN) but exclude the Security Header Type, Protocol Discriminator, Message Authentication Code, EPS Bearer ID, Procedure Transaction Identity, ESM Data Transport Message Identity, and the length of user data container contents. This can also be understood as the second NAS header only including the SQN. Alternatively, the second NAS header might include both the SQN and the EPS Bearer ID but exclude the Security Header Type, Protocol Discriminator, Message Authentication Code, EPS Bearer ID, Procedure Transaction Identity, ESM Data Transport Message Identity, and the length of user data container contents. This can also be understood as the second NAS header only including the SQN and the EPS Bearer ID. For example, the second NAS header may include the SQN, EPS bearer ID, and length information, but not the security header type, protocol discriminator, message authentication code, EPS bearer ID, procedure transaction identity, ESM data transport message identity, or length of user data container contents. This can also be understood as the second NAS header only including the SQN, EPS bearer ID, and length information. Optionally, this length information may be, for example, the length of user data container contents.
[0284] Alternatively, the second data packet may not include the NAS header. For example, the RRC layer compresses the first NAS header; another compression method is to remove the first NAS header entirely. This compression method can also be understood as the RRC layer removing the first NAS header from the first data packet to obtain the second data packet. This compression method can reduce header overhead to a greater extent.
[0285] If the second data packet includes a second NAS header, taking the second NAS header as an example where it only includes the SQN, then the second NAS header can occupy only one byte. Compared to the traditional solution where the NAS header occupies 11 bytes, the embodiments of this application significantly reduce the overhead of the NAS header. If the second data packet does not include a NAS header, the embodiments of this application further reduce the overhead of the NAS header.
[0286] Generally, the receiving end of the second data packet (e.g., a second or third communication device) can directly recover or decompress the information obtained from the second data packet, which is a voice data packet. This information can then be used as information that the first communication device can compress or delete, or it can be understood as redundant information. However, not all information in the first NAS header is redundant. Taking the SQN in the first NAS header as an example, the receiving end needs to infer the COUNT used to encrypt the second data packet based on the SQN carried in the second data packet, thereby decrypting the second data packet. If the receiving end cannot determine the SQN and other information, it may be unable to decrypt. Therefore, embodiments of this application enable the receiving end to obtain the SQN corresponding to the second data packet. One possible implementation includes that the first communication device can send corresponding information to the second communication device, and the second communication device can determine the SQN based on this information. For example, this information includes the offset between the RLC SN of the second data packet and the SQN.
[0287] Optionally, the first communication device may also send first information, which may indicate the offset between the SQN of the second data packet and the RLC SN of the second data packet. The first information may be included in the second data packet or may not be included in the second data packet, but may exist independently. Optionally, the first information and the second data packet may be included in the same message or in different messages. For example, the first information may be included in an RRC message, such as an RRC connection establishment request message, an RRC connection restoration message, or a UE assistance information (UAI) message. The receiving end of the second data packet (e.g., the second communication device or the third communication device) may deduce or determine the SQN of the second data packet based on the offset and the RLC SN of the second data packet (e.g., carried in the RLC header of the second data packet), so that the receiving end can determine the SQN even if the second NAS header does not include the SQN. The SQN determined by the receiving end may be the complete SQN or a portion of the SQN.
[0288] For example, if the second data packet does not include a NAS header, the second communication device cannot determine the SQN of the second data packet from the NAS header, which may affect the second communication device's ability to recover the NAS header. Furthermore, if the third communication device cannot obtain the SQN, it may be unable to decrypt the received data packet. Therefore, if the second data packet does not include a NAS header, the first communication device can also send first information, enabling the receiving end of the second data packet (e.g., the second communication device) to determine the SQN based on the RLC SN of the second data packet. The offset indicated by the first information can be the complete offset or an offset between a portion of the bits of the SQN and the RLC SN.
[0289] For example, if the RLC SN of the second data packet is "00000" and the corresponding SQN is "10101010", then the offset is "10101010", and the first information can indicate "10101010". For the second communication device, based on the RLC SN and the offset, the SQN can be determined to be "10101010".
[0290] Alternatively, the first information can indicate the offset between the RLC SN and the lower 5 bits of the SQN, for example, "01010". For the second communication device, based on the RLC SN and the offset, the SQN can be determined to be "01010". In this case, the second communication device may not need to recover the higher 3 bits of the SQN; that is, the second communication device determines the lower 5 bits of the SQN.
[0291] Alternatively, the first communication device may not send the first information. For example, even if the second data packet does not include a NAS header, if the lower 5 digits of the SQN have an offset of less than or equal to 10000 between them and the RLC SN, then the RLC SN can be used as the SQN. In this case, the first communication device may not send the first information, and the second communication device can determine the SQN based on the RLC SN, for example, determining that the RLC SN is the SQN.
[0292] Optionally, the first communication device can transmit the second data packet via the first signaling radio bearer. This application embodiment can be combined with the embodiment shown in FIG. 6; therefore, the content regarding the first communication device transmitting the second data packet via the first signaling radio bearer can be referred to S602 of the embodiment shown in FIG. 6. Alternatively, this application embodiment and the embodiment shown in FIG. 6 can be used independently, without combination; in this case, the first signaling radio bearer could be, for example, SRB1 or SRB 1bis. In the absence of a combination between this application embodiment and the embodiment shown in FIG. 6, optionally, existing SRB1 or SRB1bis messages can be extended so that the extended message indicates that the second data packet transmitted via the first signaling bearer includes voice data, thereby supporting NAS header compression.
[0293] Optionally, the method may further include S802, whereby the second communication device determines that the second data packet includes voice data.
[0294] For example, in combination with the embodiment shown in FIG6, the second communication device can determine that the second data packet includes voice data based on the first SRB or the first message. For instance, the second communication device receives the second data packet via the first SRB. It can determine that the second data packet includes voice data based on the fact that the first SRB is dedicated to transmitting voice data, or based on the fact that the first logical channel is dedicated to transmitting voice data, or based on the fact that the first message is dedicated to transmitting voice data. Once the second communication device determines that the second data packet includes voice data, it can process the second data packet accordingly; the specific processing procedure is not limited.
[0295] Optionally, the method may further include S803, whereby the second communication device determines a third data packet. The third data packet may include a third NAS header. Optionally, S803 may be executed by the RRC layer of the second communication device.
[0296] For example, the second communication device may execute S803 instead of S802. That is, if the second communication device receives the second data packet, it can determine the third data packet. Alternatively, if the second communication device receives the second data packet and determines the third data packet based on the fact that the second data packet includes voice data, it can do so.
[0297] Wherein, if the second data packet includes a second NAS header, the third NAS header can be the recovered second NAS header. For example, S803 can be understood as the second communication device recovering the second NAS header to obtain a third data packet, which may include the third NAS header (i.e., the recovered second NAS header). "Recovery" can also be understood as "decompression".
[0298] Alternatively, if the second data packet does not include the second NAS header, the third NAS header can also be understood as the recovered NAS header. For example, S803 can be understood as the second communication device recovering the NAS header of the second data packet to obtain the third data packet, which may include the third NAS header. "Recover" can also be understood as "generate" or "add".
[0299] The third NAS header may include one or more of the following: security header type, protocol discriminator, SQN, message authentication code, EPS bearer ID, procedure transaction identity, ESM data transport message identity, or length of user data container contents. The content of the third NAS header may be the same as that of the first NAS header; for more information on the third NAS header, please refer to the previous introduction to the first NAS header. Alternatively, it can be understood that if the second communication device recovers the header correctly, the third NAS header is the same as the first NAS header. In other words, the first data packet generated by the NAS layer of the first communication device includes the first NAS header; the RRC layer of the first communication device compresses the first NAS header to obtain the second NAS header, or removes the first NAS header; the second data packet sent by the RRC layer of the first communication device may or may not include the second NAS header; the second communication device then recovers the NAS header for the second data packet to obtain the third data packet, which may include the third NAS header, for example, the third NAS header may be the same as the first NAS header. Therefore, through the recovery by the second communication device, the second data packet can have a relatively complete NAS header. The compression by the RRC layer of the first communication device reduces the header overhead of the second data packet, which helps to reduce the air interface overhead of the second data packet.
[0300] Taking the second data packet including the second NAS header as an example, the optional recovery methods of the second communication device are introduced. Optionally, depending on whether the current second data packet includes voice data, some information in the NAS header of the second data packet can be determined in a standardized form. For example, since the NAS PDU in the second data packet includes an ESM transport message protected by NAS, the first protocol discriminator in the third NAS header can be set or restored to "0111" corresponding to EPS mobility management messages. The second protocol discriminator in the third NAS header can be set or restored to "0010" corresponding to EPS session management messages. The procedure transaction identity in the third NAS header can be set or restored to unsigned. The EPS bearer ID in the third NAS header can be restored according to the EPS bearer ID associated with the second SRB, for example, restored to the EPS bearer ID associated with the second SRB. The security header type in the third NAS header can be restored to the value corresponding to encryption without integrity protection, so that the security header type can indicate that the NAS PDU in the third data packet is encrypted and without integrity protection. The message authentication code in the third NAS header can be restored to a default or preset value, such as all 0s or all 1s; alternatively, the third NAS header may not include a message authentication code. For example, if the message authentication code in the first NAS header is a default or preset value, then the message authentication code in the third NAS header can be restored to a default or preset value; or, for another example, if the first NAS header does not include a message authentication code, then the third NAS header may also not include a message authentication code. The length of user data container contents in the third NAS header can indicate the length of the NAS PDU received by the second communication device (e.g., the length of the second data packet, or the length of the NAS PDU included in the second data packet). The SQN in the third NAS header can be equal to the SQN in the second NAS header.
[0301] If the second data packet does not include a NAS header, the recovery method for the second communication device regarding the protocol discriminator, procedure transaction identity, ESM data transport message identity, message authentication code, length of user data container contents, and security header type fields in the third NAS header can be found in the previous paragraph. For the SQN, it can be recovered based on the first information or the RLC SN of the second data packet. For example, if the second communication device receives the first information, it can recover the SQN based on the first information; the recovery method can be found in the relevant description above. If the second communication device does not receive the first information, it can recover the SQN based on the RLC SN of the second data packet. For example, the RLC SN can be used as the lower 5 bits of the SQN to obtain the SQN (actually, the lower 5 bits of the SQN are obtained).
[0302] Optionally, the method may further include S804, whereby the second communication device sends a third data packet, and correspondingly, the third communication device receives the third data packet.
[0303] Taking an access network device as the second communication device and an MME as the third communication device as an example, the second communication device sends a third data packet to the MME via an S1-application protocol (AP) message. Optionally, the third data packet may be included in the NAS-PDU IE within the S1-AP message. Optionally, the S1-AP message may be, for example, an initial UE message or an uplink NAS transport message.
[0304] Optionally, the S1-AP message may further include first indication information, which indicates that the third data packet includes voice data. The first indication information may be included in the S1-AP message but not in the third data packet; alternatively, the first indication information may also be included in the third data packet, for example, in the header of a protocol layer within the third data packet, without limitation. Thus, the third communication device receives the S1-AP message and, based on the first indication information, can determine that the third data packet includes voice data.
[0305] Alternatively, the S1-AP message may not include the first indication information. Since the third data packet carries a third NAS header, the third communication device can also determine that the third data packet includes voice data based on the third NAS header. For example, the third NAS header includes a first field that indicates that the NAS PDU included in the third data packet is encrypted and not protected for integrity. For example, if it is assumed that any encrypted data without integrity protection is voice data, the third communication device can determine that the third data packet includes voice data based on the first field.
[0306] Optionally, the method may also include S805, whereby the third communication device determines that the NAS PDU included in the third data packet is encrypted and not protected for integrity.
[0307] Optionally, the third communication device can determine from the third NAS header that the NAS PDU included in the third data packet is encrypted and not protected for integrity. For example, the third NAS header includes a first field that indicates that the NAS PDU included in the third data packet is encrypted and not protected for integrity, thereby allowing the third communication device to determine from the first field that the NAS PDU included in the third data packet is encrypted and not protected for integrity. The first field may be, for example, a security header type, or it may be another field within the third NAS header.
[0308] For example, a third communication device can determine the count value (COUNT) corresponding to the third data packet based on the SQN in the third NAS header, and decrypt the third data packet based on the COUNT and information such as the EPS bearer ID in the third NAS header, for example, decrypting the NAS PDU in the third data packet. The decrypted data packet can be called data packet A, and the third communication device can send data packet A to other core network elements. These other core network elements include, for example, SGW and / or PGW.
[0309] Optionally, the third communication device may also determine that the third data packet includes voice data based on the first instruction information and / or the first field in the third NAS header.
[0310] This application embodiment can compress the NAS header of the data packet, thereby significantly reducing the overhead of the NAS header and thus reducing the air interface transmission overhead of the data packet. Furthermore, this application embodiment can be combined with the embodiment shown in Figure 6, which can further reduce the RRC header overhead of the data packet to a certain extent. It is evident that this application embodiment can reduce the packet header overhead, which is beneficial for controlling the proportion of the packet header in the data packet. Since the second communication device recovers the NAS header, the processing of the third communication device can largely adopt the traditional NAS message processing method, which helps to reduce the implementation difficulty.
[0311] This application provides a fourth communication method. Please refer to Figure 10, which is a flowchart of the method.
[0312] S1001, the third communication device sends a fifth data packet. Correspondingly, the second communication device receives the fifth data packet. The fifth data packet may include voice data; for example, the payload of the fifth data packet may include voice data.
[0313] In this embodiment, the third communication device is, for example, a second network device or a chip within a second network device; the second communication device is, for example, a first network device or a chip within a first network device; and the first communication device is, for example, a UE or a chip within a UE. Alternatively, the third communication device is, for example, a second network device or a chip within a second network device; the second communication device is, for example, a UE or a chip within a UE; and the first communication device is, for example, another UE or a chip within that other UE. The first communication device is the receiver of the first data packet, which is sent from the third communication device and can reach the first communication device via the second communication device. The embodiment shown in FIG8 can be understood as an uplink data transmission process, and the embodiment shown in FIG10 can be understood as a downlink data transmission process.
[0314] Taking an MME as an example, the fifth data packet can be generated by the MME, or it can be determined by the MME based on the fourth data packet received from other network elements, such as an SGW or PGW. The fourth data packet may include voice data; for example, the payload of the fourth data packet may include voice data.
[0315] Taking the fifth data packet as an example, which is the data packet determined by the second communication device based on the fourth data packet. For example, the second communication device can encrypt the fourth data packet without performing integrity protection. For example, the second communication device can encrypt the NAS PDU within the fourth data packet without performing integrity protection to obtain the fifth data packet. Optionally, this processing can be performed by the first layer of the second communication device, such as the non-access layer, such as the NAS layer. For a description of the first layer, please refer to the embodiment shown in Figure 6.
[0316] The fifth data packet may include a third NAS header. The third NAS header may include, for example, one or more of the following: security header type, protocol discriminator, SQN, message authentication code, EPS bearer ID, procedure transaction identity, ESM data transport message identity, or length of user data container contents. For details regarding how the NAS layer of the second communication device determines the third NAS header, or regarding the content included in the third NAS header, please refer to the description of the first NAS header in the embodiment shown in Figure 8.
[0317] Taking an example where the third communication device is an MME and the second communication device is an access network device, optionally, the third communication device can send a fifth data packet to the access network device via an S1-AP message. Optionally, the fifth data packet can be included in the NAS-PDU IE within the S1-AP message. Optionally, the S1-AP message can be, for example, a downlink NAS transport message.
[0318] Optionally, the S1-AP message may further include second indication information, which may indicate that the fifth data packet includes voice data, or indicate that the NAS header of the fifth data packet needs to be compressed, or indicate that the NAS header of the fifth data packet needs to be compressed. The second indication information may be included in the S1-AP message but not in the fifth data packet; alternatively, the second indication information may also be included in the fifth data packet, for example, in the header of a protocol layer within the fifth data packet, without limitation. Upon receiving the S1-AP message, the second communication device can determine, based on the second indication information, that the fifth data packet includes voice data, or that the NAS header of the fifth data packet needs to be compressed, or that the NAS header of the fifth data packet needs to be compressed, or that the fifth data packet needs to be transmitted via a second signaling radio bearer. The second signaling radio bearer is, for example, a second SRB; for details regarding the second signaling radio bearer, please refer to the relevant description of the embodiment shown in Figure 7.
[0319] S1002, the second communication device determines the sixth data packet. The sixth data packet may include the fourth NAS header, or the sixth data packet may not include the NAS header. Optionally, S1002 may be executed by the second layer of the second communication device, such as the RRC layer. For more information about the second layer, please refer to the embodiment shown in Figure 6.
[0320] For example, the RRC layer of the second communication device receives the fifth data packet. Based on whether the fifth data packet contains voice data, or whether the NAS header of the fifth data packet needs to be compressed, or whether the fifth data packet is to be transmitted through the second SRB, the sixth data packet can be determined. Optionally, the RRC layer can determine whether the fifth data packet contains voice data, or whether the NAS header of the fifth data packet needs to be compressed, or whether the fifth data packet is to be transmitted through the second signaling radio bearer, based on the second indication information.
[0321] One way the RRC layer determines the sixth data packet is by compressing the third NAS header, one compression result being a fourth NAS header, from which the fifth data packet can be obtained. For example, the RRC layer can obtain the sixth data packet based on the fourth NAS header and the fifth data packet after removing the third NAS header; the sixth data packet may include the fourth NAS header. The fourth NAS header significantly reduces overhead compared to a traditional NAS header; therefore, embodiments of this application can achieve the effect of reducing the packet header size.
[0322] The fourth NAS header can be a compressed NAS header. A compressed NAS header can be understood as the fourth NAS header occupying fewer bits than a traditional NAS header; or, the fourth NAS header may occupy fewer bits than the third NAS header of the fifth data packet. For the fourth NAS header, refer to the description of the second NAS header in the embodiment shown in Figure 8.
[0323] Alternatively, the sixth data packet may not include the NAS header. For example, the RRC layer compresses the third NAS header; another compression result is the removal of the third NAS header. This compression method can also be understood as the RRC layer removing the third NAS header from the fifth data packet to obtain the sixth data packet. This compression method can reduce header overhead to a greater extent.
[0324] If the sixth data packet includes a fourth NAS header, taking the fourth NAS header as an example where it only includes the SQN, then the fourth NAS header can occupy only one byte. Compared to the traditional scheme where the NAS header occupies 11 bytes, the embodiments of this application significantly reduce the overhead of the NAS header. If the sixth data packet does not include a NAS header, the embodiments of this application further reduce the overhead of the NAS header.
[0325] S1002 can be an optional step. For example, S1002 can be omitted, and S1003 can be executed after S1001.
[0326] S1003, the second communication device transmits the sixth data packet via the second signaling radio bearer. Correspondingly, the first communication device receives the sixth data packet via the second signaling radio bearer.
[0327] This application embodiment can be combined with the embodiment shown in FIG7. For example, regarding the second communication device sending the sixth data packet via the second signaling radio bearer, please refer to S702 of the embodiment shown in FIG7. Alternatively, this application embodiment and the embodiment shown in FIG7 can be used independently, without combination. In this case, the second signaling radio bearer could be, for example, SRB1 or SRB 1bis.
[0328] Optionally, the second communication device may also send second information, which may indicate the offset between the SQN and RLC SN of the sixth data packet. The second information may be included in the sixth data packet, or it may exist independently instead of being included in the sixth data packet. Optionally, the second information and the sixth data packet may be included in the same message, or in different messages. For more information about the second information, please refer to the description of the first information in the embodiment shown in Figure 8.
[0329] Optionally, the method may further include S1004, whereby the first communication device determines that the NAS PDU included in the sixth data packet is encrypted and not protected for integrity.
[0330] Optionally, the first communication device can recover the NAS header of the sixth data packet, or the first communication device can decompress the NAS header of the sixth data packet. For example, the first communication device can obtain the third NAS header by recovering or decompressing. Wherein, if the sixth data packet includes a fourth NAS header, the third NAS header can be the recovered fourth NAS header. For example, the second communication device recovers the fourth NAS header to obtain the third data packet, and the third data packet may include the third NAS header (i.e., the recovered fourth NAS header). "Recovery" can also be understood as "decompression".
[0331] Alternatively, if the sixth data packet does not include the fourth NAS header, the third NAS header can also be understood as the recovered NAS header. For example, the second communication device recovers the NAS header for the sixth data packet, and the recovered NAS header is the third NAS header. "Recover" can also be understood as "generate" or "add".
[0332] The third NAS header may include one or more of the following: security header type, protocol discriminator, SQN, message authentication code, EPS bearer ID, procedure transaction identity, ESM data transport message identity, or length of user data container contents. This third NAS header may be the same as the third NAS header included in the fifth data packet. Alternatively, it can be understood that if the second communication device recovers the header correctly, the third NAS header recovered by the first communication device is the same as the third NAS header included in the fifth data packet. In other words, the fifth data packet sent by the third communication device includes the third NAS header; the RRC layer of the second communication device compresses the third NAS header to obtain the fourth NAS header, or removes the third NAS header; the sixth data packet sent by the RRC layer of the second communication device may include the fourth NAS header or not; the first communication device then recovers the NAS header for the sixth data packet, and the recovered NAS header is, for example, the third NAS header. It is evident that the recovery by the first communication device allows the sixth data packet to have a relatively complete NAS header. Furthermore, the compression by the RRC layer of the second communication device reduces the header overhead of the sixth data packet, which helps reduce the air interface transmission overhead of the sixth data packet.
[0333] Regarding the recovery method of the NAS header by the first communication device, please refer to the description of the recovery method of the NAS header by the second communication device in the embodiment shown in Figure 8.
[0334] Optionally, the first communication device can determine, based on the recovered third NAS header, that the NAS PDU included in the sixth data packet is encrypted and not protected for integrity.
[0335] For example, the third NAS header includes a first field that indicates that the NAS PDU included in the sixth data packet is encrypted but not protected for integrity. Thus, the first communication device can determine, based on the first field, that the NAS PDU included in the sixth data packet is encrypted but not protected for integrity. The first field could be, for example, a security header type, or it could be another field within the third NAS header.
[0336] For example, the first communication device can determine the COUNT corresponding to the sixth data packet based on the SQN in the third NAS header, and decrypt the sixth data packet based on the COUNT and information such as the EPS bearer ID in the third NAS header, for example, decrypting the NAS PDU in the sixth data packet. The data packet obtained after decryption can be called data packet B. The first communication device can also decompress the RoHC header in data packet B to obtain voice data.
[0337] This application embodiment can compress the NAS header of the data packet, thereby significantly reducing the overhead of the NAS header and thus reducing the air interface transmission overhead of the data packet. Furthermore, this application embodiment can be combined with the embodiment shown in Figure 7, which can also reduce the RRC header overhead of the data packet to a certain extent. Therefore, this application embodiment can reduce the header overhead of the data packet, which is beneficial for controlling the proportion of the header in the data packet.
[0338] This application provides a fifth communication method, please refer to Figure 11, which is a flowchart of the method.
[0339] S1101, the first communication device sends a second data packet. Correspondingly, the second communication device receives the second data packet.
[0340] In this embodiment, the third communication device is, for example, a second network device or a chip within a second network device; the second communication device is, for example, a first network device or a chip within a first network device; and the first communication device is, for example, a UE or a chip within a UE. Alternatively, the third communication device is, for example, a second network device or a chip within a second network device; the second communication device is, for example, a UE or a chip within a UE; and the first communication device is, for example, another UE or a chip within that other UE. The third communication device serves as the receiver of the second data packet, which is sent from the first communication device and can reach the third communication device via the second communication device.
[0341] For example, the first layer of the first communication device can generate a first data packet, which can then deliver the first data packet to the second layer of the first communication device. The second layer can execute S1101, whereby the second data packet can be determined based on the first data packet. For a description of the first and second layers, please refer to the embodiment shown in Figure 6. In this embodiment, the first layer is the NAS layer and the second layer is the RRC layer. The first data packet may include, for example, a NAS PDU or be a NAS PDU.
[0342] Traditional solutions encrypt and protect the integrity of signaling and data transmitted via SRB at the NAS layer. However, this application considers voice data as not being signaling; therefore, optionally, this application may not protect the integrity of voice data. But to improve data transmission security, voice data can still be encrypted. Therefore, optionally, in this application, the NAS layer may not protect the integrity of the NAS PDU included in the first data packet, but may encrypt the NAS PDU. Alternatively, it can be understood that the NAS PDU included in the first data packet is encrypted but not protected for integrity.
[0343] In this embodiment, the NAS layer can remove the NAS header of the first data packet, or the NAS layer can add a compressed NAS header to the first data packet, or not add a NAS header to the first data packet. For example, if the first data packet contains voice data, the NAS layer can add a compressed NAS header to the first data packet, or not add a NAS header to the first data packet.
[0344] As an optional implementation, the first data packet may include a first NAS header, which may be a compressed NAS header. For example, the number of bits occupied by the first NAS header may be less than the number of bits occupied by the NAS header in a conventional scheme. For example, a conventional NAS header occupies 11 bytes, while the first NAS header occupies less than 11 bytes. Compared to a conventional NAS header, the first NAS header significantly reduces overhead; therefore, the embodiments of this application can achieve the effect of reducing the packet header size.
[0345] Optionally, the NAS layer can directly generate the first NAS header; that is, the NAS layer obtains a compressed NAS header instead of a traditional NAS header. Alternatively, the NAS layer can generate a traditional NAS header and then compress or abridge it to obtain the first NAS header. In other words, in this embodiment, the NAS layer of the first communication device can compress or abridge the NAS header of the first data packet to reduce the resources occupied by the first data packet during transmission between the first and second communication devices.
[0346] Taking the compression of a traditional NAS header by the NAS layer to obtain a first NAS header as an example. Currently, traditional NAS headers may contain a lot of redundant information, or the settings in the traditional NAS header are usually related to the transmitted data. The NAS layer of the first communication device can compress or remove this redundant information, thereby reducing the number of bits occupied by the first NAS header. Taking the compression of the message authentication code by the NAS layer as an example, if the first data packet includes voice data, and the NAS PDU in the first data packet does not have integrity protection, and the traditional NAS header includes a message authentication code, the message authentication code in the traditional NAS header can be set to a default value (e.g., set by the NAS layer of the first communication device), such as all 0s or all 1s. The NAS layer can compress the traditional NAS header to obtain the first NAS header; for example, the NAS layer can remove the message authentication code from the traditional NAS header. When the NAS layer of the second or third communication device receives the second data packet, it can restore or decompress the first NAS header, for example, restoring or decompressing to obtain the message authentication code, which is either all 0s or all 1s. Therefore, without losing information, transmission resources can be saved and packet header overhead can be reduced. Similarly, one or more of the information in the traditional NAS header, such as protocol discriminator, EPS bearer ID, and length of user data container contents, can be compressed on the first communication device side and restored on the second or third communication device side, based on the current data packet, including voice data, thus reducing packet header overhead.
[0347] For example, the first NAS header may include the Security Quotas (SQN) but exclude the Security header type, protocol discriminator, message authentication code, EPS bearer ID, procedure transaction identity, ESM data transport message identity, and length of user data container contents. This can also be understood as the first NAS header only including the SQN. Alternatively, the first NAS header may include the SQN and EPS bearer ID but exclude the Security header type, protocol discriminator, message authentication code, EPS bearer ID, procedure transaction identity, ESM data transport message identity, and length of user data container contents. This can also be understood as the first NAS header only including the SQN and EPS bearer ID. Or, the first NAS header may include the SQN, EPS bearer ID, and length information but exclude the Security header type, protocol discriminator, message authentication code, EPS bearer ID, procedure transaction identity, ESM data transport message identity, and length of user data container contents. This can also be understood as the first NAS header only including the SQN, EPS bearer ID, and length information. Optionally, this length information may be, for example, the length of user data container contents.
[0348] Alternatively, the first data packet may not include a NAS header. For example, the NAS layer may not add a NAS header to the first data packet. This implementation can further reduce the header overhead of the first data packet.
[0349] If the first data packet includes a first NAS header, taking the first NAS header as an example where it only includes SQN, then the first NAS header can occupy only one byte. Compared to the traditional solution where the NAS header occupies 11 bytes, the embodiments of this application significantly reduce the overhead of the NAS header. If the first data packet does not include a NAS header, the embodiments of this application further reduce the overhead of the NAS header.
[0350] The NAS layer can deliver the first data packet to the RRC layer of the first communication device. The RRC layer can execute S1101. For example, the first communication device (e.g., the RRC layer) can send a second data packet via a first signaling radio bearer, the second data packet being derived from the first data packet. For example, the second data packet may include the first NAS header, or it may not include the NAS header. Another example is that the NAS PDU included in the second data packet is encrypted but not protected for integrity.
[0351] This application embodiment can be combined with the embodiment shown in FIG6. For example, regarding the first communication device sending the second data packet via the first signaling radio bearer, please refer to S602 of the embodiment shown in FIG6. Alternatively, this application embodiment and the embodiment shown in FIG6 can be used independently, without combination. In this case, the first signaling radio bearer could be, for example, SRB1 or SRB 1bis.
[0352] Optionally, the first communication device may also send first information, which may indicate the offset between the SQN of the second data packet and the RLC SN of the second data packet. Alternatively, the first communication device may not send the first information. Further details regarding the first information can be found in the embodiment shown in Figure 8.
[0353] Optionally, the method may further include S1102, whereby the second communication device determines that the second data packet includes voice data.
[0354] For example, in combination with the embodiment shown in FIG6, the second communication device can determine that the second data packet includes voice data based on the first SRB or the first message. For instance, the second communication device receives the second data packet via the first SRB. It can determine that the second data packet includes voice data based on the fact that the first SRB is dedicated to transmitting voice data, or based on the fact that the first logical channel is dedicated to transmitting voice data, or based on the fact that the first message is dedicated to transmitting voice data. Once the second communication device determines that the second data packet includes voice data, it can process the second data packet accordingly; the specific processing procedure is not limited.
[0355] Optionally, the method may further include S1103, whereby the second communication device determines the third data packet. Optionally, S1103 may be executed by the RRC layer of the second communication device. In the embodiments of this application, the third data packet and the second data packet are, for example, the same data packet.
[0356] For example, the second communication device may execute S1103 instead of S1102. That is, if the second communication device receives the second data packet, it can determine the third data packet. Alternatively, if the second communication device receives the second data packet and determines that the second data packet includes voice data, it can do so.
[0357] Optionally, the method may further include S1104, in which the second communication device sends a third data packet, and correspondingly, the third communication device receives the third data packet.
[0358] For example, the second communication device can execute S1102, S1103, and S1104. Alternatively, the second communication device can skip S1102 and execute S1103 and S1104 instead. Or, the second communication device can skip S1102 and S1103 and execute S1104 instead; for example, if the second communication device receives the second data packet, it can send the second data packet (the second data packet and the third data packet are the same data packet).
[0359] Taking an access network device as the second communication device and an MME as the third communication device as an example, the second communication device sends a third data packet to the MME via an S1-AP message. Optionally, the third data packet may be included in the NAS-PDU IE within the S1-AP message. Optionally, the S1-AP message may be, for example, an initial UE message or an uplink NAS transport message.
[0360] Optionally, the S1-AP message may further include first indication information, which may indicate one or more of the following: the NAS PDU in the third data packet is encrypted and not protected for integrity; the third data packet includes voice data; the SQN included in the third data packet only includes the lower N bits; the identifier of the EPS bearer corresponding to the third data packet; or, the SQN of the third data packet. The first indication information may be included in the S1-AP message but not in the third data packet; or, the first indication information may also be included in the third data packet, for example, in the header of a protocol layer within the third data packet, without limitation. Thus, when the third communication device receives the S1-AP message, it can determine one or more of the following based on the first indication information: the NAS PDU in the third data packet is encrypted and not protected for integrity; the third data packet includes voice data; the SQN included in the third data packet only includes the lower N bits; the identifier of the EPS bearer corresponding to the third data packet; or, the SQN of the third data packet.
[0361] Optionally, the method may further include S1105, whereby the third communication device determines that the NAS PDU included in the third data packet is encrypted and not protected for integrity.
[0362] Optionally, the third communication device can determine, based on the first indication information or the S1-AP message, that the NAS PDU included in the third data packet is encrypted and not protected for integrity. Optionally, if the first indication information indicates that the NAS PDU in the third data packet is encrypted and not protected for integrity, the third communication device can determine accordingly that the NAS PDU in the third data packet is encrypted and not protected for integrity. Alternatively, if the first indication information indicates other content (as described above), the third communication device can also determine accordingly that the NAS PDU in the third data packet is encrypted and not protected for integrity.
[0363] For example, a third communication device can determine the SQN based on the first indication information, determine the COUNT corresponding to the third data packet based on the SQN, and decrypt the third data packet based on the COUNT and EPS bearer ID, for example, decrypting the NAS PDU within the third data packet. The EPS bearer ID can also be the one indicated by the first indication information. The decrypted data packet can be called data packet A, and the third communication device can send data packet A to other core network elements. These other core network elements include, for example, SGW and / or PGW.
[0364] Optionally, the third communication device may also determine, based on the first instruction information and / or the S1-AP message, that the third data packet includes voice data.
[0365] This application embodiment can reduce the NAS header of data packets, thereby significantly reducing NAS header overhead and consequently reducing air interface transmission overhead. This application embodiment allows the NAS layer to process the NAS header, eliminating the need for processing by other protocol layers, thus reducing NAS header overhead at the source and decreasing the amount of information exchanged between layers. Furthermore, this application embodiment can be combined with the embodiment shown in Figure 6 to further reduce the RRC header overhead of data packets. Therefore, this application embodiment can reduce packet header overhead, which is beneficial for controlling the proportion of the packet header in the data packet.
[0366] This application provides a sixth communication method. Please refer to Figure 12, which is a flowchart of the method.
[0367] S1201, the third communication device sends a fifth data packet. Correspondingly, the second communication device receives the fifth data packet. The fifth data packet may include voice data; for example, the payload of the fifth data packet may include voice data.
[0368] In this embodiment, the third communication device is, for example, a second network device or a chip within a second network device; the second communication device is, for example, a first network device or a chip within a first network device; and the first communication device is, for example, a UE or a chip within a UE. Alternatively, the third communication device is, for example, a second network device or a chip within a second network device; the second communication device is, for example, a UE or a chip within a UE; and the first communication device is, for example, another UE or a chip within that other UE. The first communication device is the receiver of the first data packet, which is sent from the third communication device and can reach the first communication device via the second communication device. The embodiment shown in FIG11 can be understood as an uplink data transmission process, and the embodiment shown in FIG12 can be understood as a downlink data transmission process.
[0369] Taking an MME as an example, the fifth data packet can be generated by the MME, or it can be determined by the MME based on the fourth data packet received from other network elements, such as an SGW or PGW. The fourth data packet may include voice data; for example, the payload of the fourth data packet may include voice data.
[0370] Optionally, the process of generating the fifth data packet, or obtaining the fifth data packet based on the fourth data packet, can be executed by the first layer of the third communication device. The first layer is, for example, a non-access layer, such as a NAS layer. For a description of the first layer, please refer to the embodiment shown in Figure 6.
[0371] For example, the fifth data packet may include a fourth NAS header, which may be a compressed or abridged NAS header. Alternatively, the fifth data packet may not include a NAS header. This can be understood as the NAS layer either removing the NAS header from the fifth data packet, adding a compressed NAS header, or not adding a NAS header to the fifth data packet. For example, depending on whether the fifth data packet contains voice data, the NAS layer may add a compressed NAS header or not add a NAS header to the fifth data packet.
[0372] As an optional implementation, the fifth data packet may include a fourth NAS header, which may be a compressed NAS header. For example, the number of bits occupied by the fourth NAS header may be less than the number of bits occupied by the NAS header in a conventional scheme. For example, a conventional NAS header occupies 11 bytes, while the fourth NAS header occupies less than 11 bytes. The fourth NAS header significantly reduces overhead compared to a conventional NAS header; therefore, the embodiments of this application can achieve the effect of reducing the packet header size.
[0373] For example, the fourth NAS header may include the Security Quotient (SQN) but exclude the Security header type, protocol discriminator, message authentication code, EPS bearer ID, procedure transaction identity, ESM data transport message identity, and length of user data container contents. This can also be understood as the fourth NAS header only including the SQN. Alternatively, the fourth NAS header may include the SQN and EPS bearer ID but exclude the Security header type, protocol discriminator, message authentication code, EPS bearer ID, procedure transaction identity, ESM data transport message identity, and length of user data container contents. This can also be understood as the fourth NAS header only including the SQN and EPS bearer ID. Another example: the fourth NAS header may include the SQN, EPS bearer ID, and length information but exclude the Security header type, protocol discriminator, message authentication code, EPS bearer ID, procedure transaction identity, ESM data transport message identity, and length of user data container contents. This can also be understood as the fourth NAS header only including the SQN, EPS bearer ID, and length information. Optionally, this length information may be, for example, the length of user data container contents.
[0374] Alternatively, the fifth packet may not include a NAS header. For example, the NAS layer may not add a NAS header to the fifth packet. This implementation can further reduce the header overhead of the fifth packet.
[0375] If the fifth data packet includes the fourth NAS header, taking the fourth NAS header as an example where it only includes the SQN, then the fourth NAS header can occupy only one byte. Compared to the traditional scheme where the NAS header occupies 11 bytes, the embodiments of this application significantly reduce the overhead of the NAS header. If the fifth data packet does not include a NAS header, the embodiments of this application further reduce the overhead of the NAS header.
[0376] Optionally, the NAS layer can encrypt the fifth data packet without providing integrity protection. For example, if the second communication device can encrypt the NAS PDU within the fifth data packet without providing integrity protection, then the NAS PDU within the fifth data packet is encrypted but not protected for integrity.
[0377] Taking an MME as the third communication device and an access network device as the second communication device as an example, optionally, the third communication device can send a fifth data packet to the access network device via an S1-AP message. Optionally, the fifth data packet can be included in the NAS-PDU IE within the S1-AP message. Optionally, the S1-AP message can be, for example, a downlink NAS transport message.
[0378] Optionally, the S1-AP message may further include second indication information, which may indicate one or more of the following: the fifth data packet carries voice data; the SQN included in the fifth data packet includes only the lower N bits; the identifier of the EPS bearer corresponding to the fifth data packet; or, the SQN of the fifth data packet. The second indication information may be included in the S1-AP message but not in the fifth data packet; or, the second indication information may also be included in the fifth data packet, for example, in the header of a protocol layer within the fifth data packet, without limitation. Upon receiving the S1-AP message, the second communication device can determine, based on the second indication information, that the fifth data packet includes voice data, or that the NAS header of the fifth data packet needs to be compressed, or that the NAS header of the fifth data packet needs to be compressed, or that the fifth data packet needs to be transmitted via the second signaling radio bearer. The second signaling radio bearer is, for example, a second SRB; for details regarding the second signaling radio bearer, please refer to the relevant description of the embodiment shown in Figure 7.
[0379] Optionally, the method may further include S1202, in which the second communication device determines the sixth data packet. Optionally, S1202 may be executed by a second layer of the second communication device, such as the RRC layer. For more information about the second layer, please refer to the embodiment shown in FIG6. In the embodiments of this application, the sixth data packet and the fifth data packet are, for example, the same data packet.
[0380] For example, the RRC layer of the second communication device receives the fifth data packet. Based on whether the fifth data packet contains voice data, or whether the NAS header of the fifth data packet needs to be compressed, or whether the fifth data packet is to be transmitted through the second SRB, the sixth data packet can be determined. Optionally, the RRC layer can determine whether the fifth data packet contains voice data, or whether the NAS header of the fifth data packet needs to be compressed, or whether the fifth data packet is to be transmitted through the second signaling radio bearer, based on the second indication information.
[0381] Alternatively, S1202 can be replaced by the second communication device determining that the fifth data packet includes voice data. For example, the second communication device can determine that the fifth data packet includes voice data based on the second instruction information.
[0382] S1203, the second communication device transmits the sixth data packet via the second signaling radio bearer. Correspondingly, the first communication device receives the sixth data packet via the second signaling radio bearer.
[0383] For example, if S1202 includes the second communication device determining the sixth data packet, then the second communication device can further execute S1203. Alternatively, if S1202 includes the second communication device determining that the fifth data packet includes voice data, then the second communication device can execute S1203 based on the fact that the fifth data packet includes voice data.
[0384] This application embodiment can be combined with the embodiment shown in FIG7. For example, regarding the second communication device sending the sixth data packet via the second signaling radio bearer, please refer to S702 of the embodiment shown in FIG7. Alternatively, this application embodiment and the embodiment shown in FIG7 can be used independently, without combination. In this case, the second signaling radio bearer could be, for example, SRB1 or SRB 1bis.
[0385] Optionally, the second communication device may also send second information, which may indicate the offset between the SQN and RLC SN of the sixth data packet. The second information may be included in the sixth data packet, or it may exist independently instead of being included in the sixth data packet. Optionally, the second information and the sixth data packet may be included in the same message, or in different messages. For more information about the second information, please refer to the description of the first information in the embodiment shown in Figure 8.
[0386] Optionally, the method may further include S1204, whereby the first communication device determines that the NAS PDU included in the sixth data packet is encrypted and not protected for integrity.
[0387] For example, in combination with the embodiment shown in FIG7, the first communication device can determine that the NAS PDU included in the sixth data packet is encrypted and not protected for integrity based on the second SRB or the third message. If the sixth data packet includes a fourth NAS header, the first communication device can determine the SQN of the sixth data packet based on one or more of the fourth NAS header, the second indication information, or the second information; or, if the sixth data packet does not include a NAS header, the first communication device can determine the SQN of the sixth data packet based on the second indication information and / or the second information. The first communication device can determine the COUNT corresponding to the sixth data packet based on the SQN, and decrypt the sixth data packet based on the COUNT and information such as the EPS bearer ID of the sixth data packet, for example, decrypting the NAS PDU in the sixth data packet. The data packet obtained after decryption can be called data packet B. The first communication device can also decompress the RoHC header in data packet B to obtain voice data. The EPS bearer ID can also be determined based on the fourth NAS header and / or the second indication information.
[0388] The decryption of the sixth data packet can be performed by the NAS layer of the first communication device. For example, the RRC layer of the first communication device can determine the COUNT of the sixth data packet and submit it to the NAS layer. Alternatively, the RRC layer can submit information used to determine the COUNT to the NAS layer, which can then determine the COUNT based on this information. This information may include the RLC SN and / or second information of the sixth data packet. For example, if the sixth data packet does not include a NAS header, or if the NAS header does not include a SQN, the RRC layer can send the RLC SH and / or the second information to the NAS layer. The NAS layer can determine the COUNT and information such as the EPS bearer ID, and decrypt the sixth data packet based on the COUNT and the EPS bearer ID to obtain data packet B. It can also decompress the RoHC header within data packet B.
[0389] This application embodiment can compress the NAS header of the data packet, thereby significantly reducing the overhead of the NAS header and thus reducing the air interface transmission overhead of the data packet. Furthermore, this application embodiment can be combined with the embodiment shown in Figure 7, which can also reduce the RRC header overhead of the data packet to a certain extent. Therefore, this application embodiment can reduce the header overhead of the data packet, which is beneficial for controlling the proportion of the header in the data packet.
[0390] The embodiments shown in any two or more of the figures in Figures 6 to 8 and Figures 10 to 12 as described above can be used in combination, or these embodiments can be used separately without combination.
[0391] For example, the embodiments shown in Figure 11 and Figure 8 can be used in combination. For instance, the RRC layer of the first communication device can compress the NAS header of the data packet according to the embodiment shown in Figure 8. The RRC layer of the second communication device does not restore the NAS header of the data packet, and the NAS layer of the third communication device decrypts the data packet. For example, the NAS layer of the third communication device can decrypt the data packet according to the embodiment shown in Figure 11. Alternatively, the NAS layer of the first communication device can shorten the NAS header of the data packet according to the embodiment shown in Figure 11. The RRC layer of the second communication device can restore the NAS header of the data packet according to the embodiment shown in Figure 8 and send the data packet with the restored NAS header to the third communication device, whereby the third communication device can decrypt the data packet.
[0392] For example, the embodiments shown in Figure 12 and Figure 10 can be used in combination. For instance, the NAS layer of the third communication device can shorten the NAS header of the data packet according to the embodiment shown in Figure 12, and the RRC layer of the second communication device can restore the NAS header of the data packet according to the embodiment shown in Figure 10, and send the data packet with the restored NAS header to the first communication device, which can then decrypt the data packet. Alternatively, the RRC layer of the second communication device can compress the NAS header of the data packet according to the embodiment shown in Figure 10, and the RRC layer of the first communication device may not need to restore the NAS header; the NAS layer of the first communication device can simply decrypt the data packet. For example, the NAS layer of the third communication device can decrypt the data packet according to the embodiment shown in Figure 12.
[0393] Other embodiments of this application will be described below. In the various method embodiments described below, the first communication device is a UE and the second communication device is a first network device, as an example.
[0394] This application provides a seventh communication method. Please refer to Figure 13, which is a flowchart of the method. Optionally, the embodiment shown in Figure 13 can be used in NR systems, or it can also be used in other communication systems, such as future communication systems.
[0395] S1301, the UE sends a third MAC PDU. Correspondingly, the first network device receives the third MAC PDU.
[0396] Optionally, the third MAC PDU can carry voice data, or it can carry other types of data. The encoding rate of the data (e.g., voice data) carried by the third MAC PDU can be 800bps, or it can be greater or less than 800bps, and this application embodiment does not impose any limitations.
[0397] Optionally, the UE can send the third MAC PDU on the TN or on the NTN. If the UE sends the third MAC PDU on the NTN, the first network device can be located in the air, as shown in Figure 5B, and the first network device can be a satellite or a functional module located on a satellite; or, the first network device can be located on the ground, as shown in Figure 5C; or, the first network device can include functional modules located in the air and functional modules located on the ground, as shown in Figure 5A, and the first network device can include a satellite (or a functional module on a satellite) and a ground gateway station.
[0398] The third MAC PDU may include the first RLC PDU. The first RLC PDU may not include segmented RLC SDUs. For example, the RLC SDUs included in the first RLC PDU may be determined according to a third rule, which may indicate that the RLC PDU does not include segmented RLC SDUs. The third rule may be predefined by the protocol, configured by the first network device, or determined through negotiation between the UE and the first network device.
[0399] The RLC layer has a segmentation function. For example, if the data volume of an RLC SDU is large, it can be divided into multiple RLC SDUs for transmission. If an RLC PDU includes segmented RLC SDUs, the RLC header of that RLC PDU needs to include information indicating the segmentation, resulting in a longer RLC header. Therefore, this application proposes not to perform segmentation at the RLC layer, for example, not to divide an RLC SDU into multiple RLC SDUs, so that the RLC header does not need to carry information indicating segmentation. For example, if the first RLC PDU is not segmented at the RLC layer, that is, the first RLC PDU does not include segmented RLC SDUs, then the RLC header of the first RLC PDU does not need to include information indicating segmentation, thereby reducing the length of the RLC header.
[0400] For example, when the MAC layer performs logical channel priority (LCP) packetization on data on the logical channel (LCH), the corresponding RLC layer does not segment the RLC SDU. This eliminates the need to include information indicating segmented RLC SDUs in the RLC header, thus reducing its length. Optionally, the RLC layer can match the data size provided by the MAC layer. For example, if the RLC needs to store 50 bits of data for the current TB, and an RLC SDU is 35 bits in size, then the RLC will only store one RLC SDU in that TB, without splitting the second RLC SDU to provide 50 bits of data.
[0401] Optionally, the first RLC PDU may not include an RLC header. For example, the first RLC SDU may not include a segmented RLC SDU, and the third MAC PDU may not include the RLC header of the first RLC PDU, thereby further reducing header overhead. For example, the RLC entity (or RLC layer) corresponding to the third MAC PDU may adopt transparent mode (TM). In TM, the RLC PDU included in the third MAC PDU may not include an RLC header. The transmission mode of the RLC entity can be configured by the first network device. For example, the first network device may configure the transmission mode of the RLC entity of the DRB used for transmitting voice data to TM, thereby reducing the RLC header of the RLC PDU processed by the RLC entity. Optionally, the aforementioned LCP packet assembly scheme may also be used for the RLC entity, that is, the RLC entity does not perform segmentation.
[0402] As an optional implementation, the number of hybrid automatic repeat request (HARQ) processes corresponding to the RLC entity can be 1. Alternatively, if the number of HARQ processes corresponding to the RLC entity is 1, then the RLC entity can use a TM (Transfer Module), in which case the RLC PDU may not include an RLC header.
[0403] The RLC layer in this embodiment may not segment the RLC SDU, thus omitting information indicating segmentation from the RLC header and saving RLC header overhead. Optionally, the RLC PDU may also omit the RLC header, further saving header overhead.
[0404] This application provides an eighth communication method, as shown in Figure 14, which is a flowchart of the method. Optionally, the embodiment shown in Figure 14 can be used in an LTE system, or it can also be used in other communication systems.
[0405] S1401, the UE sends a first RLC PDU. Correspondingly, the first network device receives the first RLC PDU.
[0406] The UE can further process the first RLC PDU before sending it. For example, the first RLC PDU can also be processed by protocol layers such as the MAC layer before being sent, and there is no limitation on this. Optionally, the first RLC PDU can carry voice data, or it can carry other types of data. The encoding rate of the data (e.g., voice data) carried by the first RLC PDU can be 800bps, or it can be greater than or less than 800bps, and this application embodiment does not impose any limitations.
[0407] Optionally, the UE can send the first RLC PDU on the TN or on the NTN. If the UE sends the first RLC PDU on the NTN, the first network device can be located in the air, as shown in Figure 5B, and the first network device can be a satellite or a functional module located on a satellite; or, the first network device can be located on the ground, as shown in Figure 5C; or, the first network device can include functional modules located in the air and functional modules located on the ground, as shown in Figure 5A, and the first network device can include a satellite (or a functional module on a satellite) and a ground gateway station.
[0408] The first RLC PDU may include at least two RLC SDUs, which can also be understood as the first RLC PDU being a cascaded RLC PDU. The first RLC PDU may also include an RLC header. This RLC header may include at least one length field, which may indicate the length of the at least two RLC SDUs, or indicate the length of the RoHC header included in the at least two RLC SDUs. For any one of the at least two RLC SDUs, it may include a PDCP header, a RoHC header, and a payload; the lengths of the RoHC headers included in different RLC SDUs may be the same or different.
[0409] When an RLC PDU includes multiple cascaded RLC SDUs, the RLC PDU may include a field indicating the length of the cascaded RLC SDUs, such as a length field, which can be represented as an LI field. In conventional schemes, the LI field occupies 11 bits, and the maximum length it can indicate is 2048 bytes. However, for voice data, the length of the RLC SDU carrying the voice data is shorter. For example, with an encoding rate of 800bps, the payload length can be 8 bytes, the IP / UDP / RTP header length is 40 bytes, and the PDCP header length is 1 byte, then the total length of the RLC SDU is 49 bytes, and 11 bits are not needed for indication. Based on the actual size of the voice data packet under low bitrate encoding, embodiments of this application propose that the number of bits occupied by each length field in at least one of the length fields included in the first RLC PDU can be less than a first threshold to reduce the overhead of the RLC header. Optionally, the first threshold is 11, or it can be other values. Optionally, the number of bits occupied by different length fields in the at least one length field can be the same. For example, different length fields in the at least one length field occupy the same number of bits, and this number of bits can be less than a first threshold. For instance, this number of bits could be 7 bits, which can indicate a maximum RLC SDU length of 128 bytes. Since the RLC header can be byte-aligned, using 7 bits for the RLC SDU length indication, combined with the extended indication field E, allows the length of the RLC SDU to be indicated using only one byte, making implementation easier. Alternatively, when the length of the RLC SDU can be further shortened, this number of bits can also be other values, such as 3 or 4, without restriction.
[0410] The number of at least one length field can be less than or equal to the number of at least two RLC SDUs. The value of the at least one length field can indicate the length of the corresponding RLC SDU, or the value of the at least one length field can be used by the receiver to determine the length of the RLC SDU. Optionally, the receiver can transmit only variable quantities based on information known to both the receiver and the transmitter, such as transmitting RoHC header length information or RoHC header length information superimposed with PDCP header length information. For example, the number of the at least one length field is equal to the number of the at least two RLC SDUs. The value of the first length field in the at least one length field can directly indicate the length of the first RLC SDU among the at least two RLC SDUs, or the value of the first length field can indicate the length of the RoHC header included in the first RLC SDU. The receiving end can determine the length of the RLC SDU based on information such as the coding rate and / or the PDCP header length. The value of the second length field in the at least one length field can directly indicate the length of the second RLC SDU among the at least two RLC SDUs, or the value of the second length field can indicate the length of the RoHC header included in the second RLC SDU. The receiving end can determine the length of the RLC SDU based on information such as the coding rate and / or the PDCP header length, and so on.
[0411] For example, the number of the at least one length field is less than the number of the at least two RLC SDUs. The value of the at least one length field can indicate the length of the corresponding RLC SDU, or the value of the at least one length field can be used by the receiver to determine the length of the corresponding RLC SDU. Optionally, the receiver can transmit only variable quantities based on information known to both the receiver and the transmitter, such as transmitting RoHC header length information or RoHC header length information superimposed with PDCP header length information. The value of the first length field in the at least one length field can indicate the length of the first RLC SDU among the at least two RLC SDUs, or the value of the first length field can indicate the length of the RoHC header included in the first RLC SDU. The receiver can determine the length of the RLC SDU based on information such as the coding rate and / or PDCP header length. The value of the second length field in the at least one length field can indicate the length of the second RLC SDU among the at least two RLC SDUs, or the value of the second length field can indicate the length of the RoHC header included in the second RLC SDU. The receiver can determine the length of the RLC SDU based on information such as the coding rate and / or PDCP header length, and so on. However, for the last RLC SDU among the at least two RLC SDUs, the length of the RLC SDU may not be indicated by the length field, nor may the length of the RoHC header included in the RLC SDU be indicated by the length field. For example, the receiver can estimate the length of the last RLC SDU based on the length of the RLC PDU and the lengths of the other RLC SDUs.
[0412] Referring to Figure 15, an example of an RLC header is shown. The left side of Figure 15 shows a traditional RLC header, and the right side shows an RLC header provided in this embodiment. Taking a first RLC PDU comprising three cascaded RLC SDUs as an example, namely RLC SDU1 to RLC SDU3. The RLC header of the first RLC SDU includes two length fields (which can also be represented by "length"), namely length field 1 and length field 2. In the left figure of Figure 15, length field 1 can indicate the length of RLC SDU1, and length field 2 can indicate the length of RLC SDU2. In the right figure of Figure 15, length field 1 can indicate the length of RLC SDU1, or the length of the RoHC header included in RLC SDU1; length field 2 can indicate the length of RLC SDU2, or the length of the RoHC header included in RLC SDU2. As can be seen from the right figure, this embodiment of the application adaptively reduces the length fields based on the characteristics of low voice coding rate when voice data packets are transmitted on non-terrestrial networks. For example, each length field occupies 7 bits, so the length field and field E occupy exactly one byte. Furthermore, by reducing the length field, the length of the RLC header is reduced from 4 bytes to 3 bytes.
[0413] Optionally, the number of bits occupied by the length field in the RLC header can be variable. The length field in the RLC header can indicate the length of the RLC SDU or the length of the RoHC header included in the RLC SDU. Regardless of which indication, it includes the length of the RoHC header. The length of the RoHC header is related to RoHC compression. If the compression performance is good, the RoHC header length can be shorter, such as 1 byte or 3 bytes; if the compression performance is poor, the RoHC header length will be longer. That is, the length of the RoHC header is variable. It is evident that the length difference of multiple RLC SDUs transmitted by an RLC entity corresponding to one RB is mainly due to RoHC header compression. Therefore, this application proposes that the number of bits occupied by the length field can also be variable. For example, if the RoHC header is short or the compression performance is good, the number of bits occupied by each length field in some or all of the length fields included in the first RLC PDU can be less, for example, less than the second threshold, thereby further reducing the header overhead; or, if the RoHC header is long or the compression performance is poor, the number of bits occupied by each length field in some or all of the length fields included in the first RLC PDU can be more, for example, greater than or equal to the second threshold, so that the length field can indicate the length of the RLC SDU or the length of the RoHC header.
[0414] For the length fields included in the RLC header of the RLC PDU generated by the UE, the number of bits occupied by different length fields can be the same or different. As a possible implementation, using several possible header lengths after RoHC header compression, for example, the number of bits occupied by each length field in a partial length field can be less, while the number of bits occupied by each length field in the remaining length fields can be more. For example, the RoHC header corresponding to the partial length field has better compression performance, while the RoHC header corresponding to the remaining length fields has poorer compression performance. Optionally, the number of bits occupied by each length field can be less than 11 bits. Optionally, RLC SDUs corresponding to length fields with different bit counts can not be included in the same RLC PDU; for example, the length fields in the same RLC PDU may occupy the same number of bits, while the length fields in different RLC PDUs may occupy the same or different numbers of bits. Alternatively, RLC SDUs corresponding to length fields with different bit counts can also be included in the same RLC PDU; for example, the length fields in the same RLC PDU may occupy the same or different numbers of bits.
[0415] For example, with an encoding rate of 800 bps, a payload length of 8 bytes, a RoHC header length of 3 bytes, and a PDCP header length of 1 byte, the total length of the RLC SDU does not exceed 12 bytes. In this case, if the at least one length field indicates the length of at least two RLC SDUs, then each length field in the at least one length field can occupy 4 bits; or, since the payload is fixed, the length of the RLC SDU varies from 10 bytes to 12 bytes. If the at least one length field indicates the length range of at least two RLC SDUs, such as indicating the length of the RoHC header included in the RLC SDU, then each length field in the at least one length field can occupy 2 bits. The length of the RLC SDU can be determined based on the value indicated by these 2 bits. For example, a length field of "00" indicates that the RoHC header length is 1 byte, and the corresponding RLC SDU length is 10 bytes.
[0416] Optionally, the RLC header may include first indication information, which may indicate the number of bits occupied by each length field in some or all of the at least one length field. This first indication information may be represented as a length scale (LS), or other forms. Since the number of bits occupied by each length field is variable, it can be indicated by the first indication information, allowing the receiving end to clearly specify the number of bits occupied by each length field. The first indication information may occupy one or more bits, which may be newly added bits in the RLC header or existing bits in the RLC header. For example, if the first indication information occupies one bit, a "1" indicates that the number of bits occupied by each length field is less than a second threshold or that each length field is short, for example, occupying 3 bits; a "0" indicates that the number of bits occupied by each length field is greater than or equal to the second threshold or that the length field is long, for example, occupying 7 bits.
[0417] As mentioned earlier, the at least one length field can indicate the length of the RLC SDU, or the length of the RoHC header included in the RLC SDU. The content indicated by the length field can be predefined by the protocol, pre-configured by the first network device, determined through negotiation between the UE and the first network device, or determined based on the first indication information. Taking the determination of the content indicated by the length field based on the first indication information as an example: For instance, if the first indication information indicates that the number of bits occupied by each length field is less than a second threshold or indicates that each length field is short, then each length field can indicate the length of the RoHC header; or, if the first indication information indicates that the number of bits occupied by each length field is greater than or equal to the second threshold or indicates that the length field is long, then each length field can indicate the length of the RLC SDU. It is evident that there are multiple and flexible methods for determining the content indicated by the length field.
[0418] If the at least one length field indicates the length of at least two RLC SDUs, the receiving end of the first RLC PDU (e.g., the first network device) can determine the length of the at least two RLC SDUs based on the value of the at least one length field. Alternatively, if the at least one length field indicates the length of the RoHC header included in the at least two RLC SDUs, the first network device can determine the length of the at least two RLC SDUs based on the at least one length field and an offset. For example, for any one of the at least two RLC SDUs, the first network device can determine the length of the RLC SDU based on the value of the length field indicating the RLC SDU and the offset corresponding to the RLC SDU, such as including the length of the PDCP header and the length of the RoHC header included in the RLC SDU.
[0419] Referring to Figure 16, another example of an RLC header can be seen. The left side of Figure 16 shows a traditional RLC header, and the right side shows an RLC header provided in the embodiments of this application. Taking a first RLC PDU comprising three cascaded RLC SDUs as an example, namely RLC SDU1 to RLC SDU3. The RLC header of the first RLC SDU includes two length fields (which can also be represented by length), namely length field 1 and length field 2. In the left figure of Figure 16, length field 1 indicates the length of RLC SDU1, and length field 2 indicates the length of RLC SDU2. In the right figure of Figure 16, length field 1 indicates the length of the RoHC header included in RLC SDU1; length field 2 indicates the length of the RoHC header included in RLC SDU2. For example, if these three RLC SDUs are carried through the same TB, and all three RLC SDUs have good compression performance, then each of the two length fields included in the first RLC PDU can be relatively short, for example, occupying 3 bits. As shown in the right figure of Figure 16, the two length fields and the two fields E2 occupy exactly one byte. For example, the payload length of the first RLC PDU is 8 bytes. The PDCP headers of these three RLC SDUs are each 1 byte long, and the RoHC headers of these three RLC SDUs are 1 byte, 3 bytes, and 3 bytes long, respectively. Then, length field 1, for example, "001" indicates 1 byte; length field 2, for example, "010" indicates 3 bytes. For the first network device, the length of RLC SDU1 can be determined to be 1+8+1=10 bytes, the length of RLC SDU2 to be 3+8+1=12 bytes, and the remainder to be the length of RLC SDU3. It can be seen that when three RLC SDUs are cascaded, by reducing the length fields, the length of the RLC header of the first RLC PDU can be reduced from 4 bytes to 2 bytes.
[0420] Optionally, the RLC header of the first RLC PDU may include the RLC SN of the first RLC PDU. The number of bits occupied by this RLC SN may be less than, for example, a second threshold. Alternatively, the number of bits occupied by the RLC SN can be reduced. For example, when the number of HARQ processes is limited, the maximum value of the RLC SN can be smaller, or the number of RLC SNs is limited, so fewer bits are needed to indicate the RLC SN, and the number of bits occupied by the RLC SN can be reduced. The second threshold may be, for example, 5, or it may be another value.
[0421] For example, in the case of only one HARQ process, the RLC layer of the receiving end (e.g., the first network device) does not need to perform sorting based on the RLC SN, so the RLC header of the first RLC PDU may not include the RLC SN.
[0422] If the number of bits occupied by the RLC SN is reduced, or if the RLC header excludes the RLC SN, then the reduced bit can be omitted from the RLC header. For example, if the RLC SN originally occupies 5 bits, and it is reduced to 4 bits, resulting in 1 bit, the RLC header can exclude this 1 bit. Or, if the RLC SN originally occupies 5 bits, and it is removed from the RLC header, resulting in 5 bits, the RLC header can exclude these 5 bits. This effectively reduces the size of the RLC header, thereby decreasing its overhead.
[0423] Alternatively, even if the number of bits occupied by the RLC SN is reduced or the RLC header does not include the RLC SN, the RLC header can still include the reduced bits, which can be used as reserved bits or for other purposes.
[0424] For example, the right side of Figure 16 shows an RLC header excluding the RLC SN. In the right side of Figure 16, some of the bits originally occupied by the RLC SN are used to carry the first indication information (represented by LS in the right side of Figure 16), and the remaining bits are reserved bits (represented by R in the right side of Figure 16).
[0425] Optionally, the RLC header may also include a third field, which may indicate whether a next length field exists. For example, in the right-hand diagram of Figure 16, the third field is represented by E2. Alternatively, the third field may use an existing field in the RLC header, such as field E (i.e., E2 in the right-hand diagram of Figure 16 can also be replaced with E), without restriction. For example, in the right-hand diagram of Figure 16, the first E2 indicates whether a length field 2 exists, and the second E2 indicates whether a next length field exists after length field 2.
[0426] In this embodiment of the application, for an RLC PDU that includes a cascaded RLC SDU, the number of bits occupied by the length field in the RLC header of the RLC PDU can be reduced to save RLC header overhead. Optionally, the number of bits occupied by the length field can be variable; if the number of bits occupied by the length field is small, the RLC header overhead can be further reduced.
[0427] This application provides a ninth communication method, as shown in Figure 17, which is a flowchart of the method. Optionally, the embodiment shown in Figure 17 can be used in an LTE system, or it can also be used in other communication systems.
[0428] S1701, the UE sends the fifth MAC PDU. Correspondingly, the first network device receives the fifth MAC PDU.
[0429] Optionally, the fifth MAC PDU can carry voice data, or it can carry other types of data. The encoding rate of the data (e.g., voice data) carried by the fifth MAC PDU can be 800bps, or it can be greater than or less than 800bps, and this application embodiment does not impose any limitations.
[0430] Optionally, the UE can send the fifth MAC PDU on the TN or on the NTN. If the UE sends the fifth MAC PDU on the NTN, the first network device can be located in the air, as shown in Figure 5B, and the first network device can be a satellite or a functional module located on a satellite; or, the first network device can be located on the ground, as shown in Figure 5C; or, the first network device can include functional modules located in the air and functional modules located on the ground, as shown in Figure 5A, and the first network device can include a satellite (or a functional module on a satellite) and a ground gateway station.
[0431] The fifth MAC PDU may include the first MAC SDU, and the fifth MAC PDU may not include the MAC subheader of the first MAC SDU. In other words, the first MAC SDU may not have a MAC subheader, or may not need to add a MAC subheader to the first MAC SDU, thereby reducing the packet header overhead of the first MAC PDU.
[0432] Optionally, the UE can transmit the first MAC SDU on the second resource, and the first network device can receive the first MAC SDU on the second resource; that is, the first MAC SDU can be carried on the second resource. The second resource, for example, corresponds to an LCID, which can be the LCID corresponding to the RLC PDU included in the first MAC SDU. For the receiving end, as long as the first MAC SDU is received through the second resource, it can be determined that the first MAC SDU corresponds to the LCID. Therefore, the MAC subheader of the first MAC SDU may not include the LCID, or the MAC subheader of the first MAC SDU may not include any LCID.
[0433] Alternatively, the second resource may correspond to a DRB, which could be the DRB corresponding to a first logical channel, and the first logical channel could be the logical channel corresponding to the RLC PDU included in the first MAC SDU. For the receiving end, as long as the first MAC SDU is received through the second resource, it can be determined that the first MAC SDU corresponds to the DRB. Therefore, the MAC subheader of the first MAC SDU may not include the DRB identifier, or the MAC subheader of the first MAC SDU may not include any DRB identifier. It is evident that, since the embodiments of this application correspond transmission resources to LCIDs or DRBs, the MAC subheader of the first MAC SDU may not include the LCID or DRB identifier, thereby reducing the overhead of the MAC subheader of the first MAC SDU.
[0434] Optionally, the length of the first MAC SDU can be equal to the time-domain length of the second resource, or it can be understood that the first MAC SDU exactly occupies the time-domain space of the second resource without any padding bits. Therefore, for the receiving end, the length of the first MAC SDU can be determined based on the time-domain length of the second resource. Thus, the MAC sub-header of the first MAC SDU does not necessarily need to indicate its length. Optionally, the coding rate of the second resource can be less than or equal to 800 bps. For example, when the first network device schedules resources for the UE, it can schedule resources with a coding rate less than or equal to 800 bps, so that the UE does not need to pad bits on the resource when sending the first MAC SDU, making the length of the first MAC SDU equal to the time-domain length of the resource.
[0435] In summary, since the MAC subheader of the first MAC SDU may not include the LCID (or DRB identifier) or the length information of the first MAC SDU, a MAC subheader may not be added to the first MAC SDU, thereby reducing the packet header overhead of the first MAC PDU.
[0436] Optionally, the transmission mode of the first MAC SDU can be a transparent transmission mode, such as TM. In transparent transmission mode, the first MAC SDU can be made to not have a corresponding MAC sub-header.
[0437] The first MAC SDU can carry voice data, or it can carry other types of data. Taking the first MAC SDU carrying voice data as an example, in this embodiment of the application, a dedicated transmission resource (e.g., a second resource) can be configured for the voice data. This transmission resource can correspond to the LCID used for voice data transmission, thereby reducing the MAC subheader; and / or, in this embodiment of the application, a dedicated logical channel can be configured for the voice data. This logical channel can correspond to the DRB used for voice data transmission, thereby reducing the MAC subheader.
[0438] The embodiments of this application do not require adding a MAC subheader to the MAC SDU, thereby significantly reducing the header overhead of the MAC PDU.
[0439] This application provides a tenth communication method, as shown in Figure 18, which is a flowchart of the method. Optionally, the embodiment shown in Figure 18 can be used in an LTE system, or it can also be used in other communication systems.
[0440] S1801, the UE sends the sixth MAC PDU. Correspondingly, the first network device receives the sixth MAC PDU.
[0441] Optionally, the sixth MAC PDU can carry voice data, or it can carry other types of data. The encoding rate of the data (e.g., voice data) carried by the sixth MAC PDU can be 800bps, or it can be greater or less than 800bps, and this application embodiment does not impose any limitations.
[0442] Optionally, the UE can send the sixth MAC PDU on the TN or on the NTN. If the UE sends the sixth MAC PDU on the NTN, the first network device can be located in the air, as shown in Figure 5B, and the first network device can be a satellite or a functional module located on a satellite; or, the first network device can be located on the ground, as shown in Figure 5C; or, the first network device can include functional modules located in the air and functional modules located on the ground, as shown in Figure 5A, and the first network device can include a satellite (or a functional module on a satellite) and a ground gateway station.
[0443] The sixth MAC PDU may include K MAC SDUs, where K is a positive integer. The sixth MAC PDU may also include K MAC subheaders, which are the MAC subheaders of the K MAC SDUs, and these K MAC subheaders can correspond one-to-one with the K MAC SDUs. Optionally, the K MAC subheaders and the K MAC SDUs can form K MAC subPDUs. For example, one of the K MAC subheaders can form a MAC subPDU with the MAC SDU corresponding to that subheader, resulting in a total of K MAC subPDUs. Optionally, the K MAC subPDUs can be adjacent. For example, refer to Figure 19 for an example of such K MAC subPDUs.
[0444] Optionally, K can be predefined by the protocol or configured by the first network device. For example, if configured by the first network device, the first network device can send second information to the UE, which can indicate K, and the UE can then execute S1801 according to the second information.
[0445] In this embodiment of the application, of the K MAC sub-headers, except for the third MAC sub-header, the remaining K-1 MAC sub-headers may not include the LCID or the DRB identifier. The third MAC sub-header is, for example, the MAC sub-header of the first MAC SDU among the K MAC SDUs. All K MAC SDUs correspond to the same LCID or the same DRB.
[0446] In the traditional approach, each of the K MAC sub-headers includes a corresponding LCID. Since the LCIDs corresponding to the K MAC SDUs are the same, the LCIDs included in the K MAC sub-headers are identical. Therefore, in this embodiment, the K-1 MAC sub-headers can be made to exclude either the LCID or the DRB identifier. For the receiving end, based on the LCID or DRB identifier in the third MAC sub-header, it can be determined that each of the K MAC SDUs corresponds to the corresponding LCID or DRB.
[0447] The third MAC subheader may include the LCID corresponding to the K MAC SDUs, or the identifier of the DRB corresponding to the K MAC SDUs.
[0448] Alternatively, the third MAC subheader may not include the LCID or DRB identifier. For example, the UE can transmit the K MAC SDUs on the third resource, and the first network device can receive the K MAC SDUs on the third resource; that is, the K MAC SDUs can be carried on the second resource. The third resource, for example, corresponds to an LCID, which can be the LCID corresponding to the RLC PDU included in the K MAC SDUs. For the receiving end, as long as the K MAC SDUs are received through the third resource, it can be determined that the K MAC SDUs correspond to the LCID. Therefore, the third MAC subheader may not include the LCID, or the third MAC subheader may not include any LCID.
[0449] Alternatively, the third resource may correspond to a DRB, which could be a DRB corresponding to at least one logical channel, and the at least one logical channel could be a logical channel corresponding to the RLC PDU included in the K MAC SDUs. For the receiving end, as long as the K MAC SDUs are received through the third resource, it can be determined that the K MAC SDUs correspond to the DRB. Therefore, the third MAC subheader may not include the DRB identifier, or the third MAC subheader may not include any DRB identifier. It is evident that, since the embodiments of this application correspond the transmission resources to LCIDs or DRBs, the MAC subheaders of the K MAC SDUs may all omit the LCID or DRB identifiers, thereby reducing the overhead of the MAC subheaders.
[0450] Optionally, each of the K MAC sub-headers may also include a length field, such as represented as "length," or may have other representations. This length field may indicate the length of the corresponding MAC SDU, or the length of the RoHC header included in the corresponding MAC SDU. For example, for any one of the K MAC sub-headers, the length field included in the MAC sub-header may indicate the length of the MAC SDU corresponding to that MAC sub-header, or the length of the RoHC header included in the MAC SDU corresponding to that MAC sub-header.
[0451] In traditional schemes, the length field within a MAC subheader can occupy one or two bytes. However, for voice data, the length of the MAC SDU carrying the voice data is relatively short, for example, no more than 128 bytes, and does not require many bits for indication. Based on the actual size of the voice data packet under low bitrate encoding, this application proposes that the number of bits occupied by the length field in any of the K MAC subheaders can be less than a third threshold to reduce the overhead of the MAC subheader. Optionally, the third threshold is 8 or 16, or it can be other values. Optionally, the number of bits occupied by different length fields in the K MAC subheaders can be the same. For example, if the number of bits occupied by different length fields in the K MAC subheaders is the same, this number of bits can be less than the third threshold. For example, this number of bits is, for instance, 7 bits, which can indicate a MAC SDU of up to 128 bytes. Since MAC subheaders can be byte-aligned, using 7 bits for the MAC SDU length indication, combined with the extended indication field E, allows one byte to be used to indicate the length of the MAC SDU, which is more convenient to implement. Alternatively, when the length of the MAC SDU can be further shortened, the number of bits can also be other values, such as 3, 4, etc., without restriction.
[0452] Optionally, the number of bits occupied by the length field in the MAC sub-header can be variable. The length field in the MAC sub-header can indicate the length of the MAC SDU or the length of the RoHC header included in the MAC SDU. Regardless of which it indicates, it includes the length of the RoHC header. The length of the RoHC header is related to RoHC compression. If the compression performance is good, the length of the RoHC header can be shorter, such as 1 byte or 3 bytes; if the compression performance is poor, the length of the RoHC header will be longer. That is, the length of the RoHC header is variable. It is evident that the length difference among multiple MAC SDUs transmitted by the MAC entity is mainly caused by RoHC header compression. Therefore, this application proposes that the number of bits occupied by the length field can also be variable. For example, if the RoHC header is short or the compression performance is good, the number of bits occupied by the length field in any of the K MAC SDUs can be less, for example, less than the fourth threshold, thereby further reducing the packet header overhead; or, if the RoHC header is long or the compression performance is poor, the number of bits occupied by the length field in any of the K MAC SDUs can be more, for example, greater than or equal to the fourth threshold, so that the length field can indicate the length of the MAC SDU or the length of the RoHC header.
[0453] For the length fields included in the MAC subheader of the MAC PDU generated by the UE, the number of bits occupied by different length fields can be the same or different. As a possible implementation, using several possible header lengths compressed from the RoHC header, for example, the number of bits occupied by each length field in a partial length field can be less, while the number of bits occupied by each length field in the remaining length fields can be more. For example, the RoHC header corresponding to the partial length field has better compression performance, while the RoHC header corresponding to the remaining length fields has poorer compression performance. Optionally, the number of bits occupied by each length field can be less than 11 bits. Optionally, MAC SDUs corresponding to length fields with different bit counts can not be included in the same MAC PDU; for example, the length fields in the same MAC PDU may occupy the same number of bits, and the length fields in different MAC PDUs may occupy the same or different numbers of bits. Alternatively, MAC SDUs corresponding to length fields with different bit counts can also be included in the same MAC PDU; for example, the length fields in the same MAC PDU may occupy the same or different numbers of bits.
[0454] Optionally, the MAC subheader may include first indication information, which indicates the number of bits occupied by the length field included in the MAC subheader. This first indication information may be represented as LS, or it may have other representations. Since the number of bits occupied by the length field is variable, it can be indicated by the first indication information, allowing the receiving end to clearly specify the number of bits occupied by the length field. The first indication information may occupy one or more bits, which may be newly added bits in the MAC subheader or existing bits in the MAC subheader. For example, if the first indication information occupies one bit, a "1" indicates that the number of bits occupied by the length field is less than the fourth threshold or that the length field is short, such as occupying 3 bits; a "0" indicates that the number of bits occupied by the length field is greater than or equal to the fourth threshold or that the length field is long, such as occupying 7 bits.
[0455] As mentioned earlier, the length field can indicate the length of the MAC SDU, or it can indicate the length of the RoHC header included in the MAC SDU. The content indicated by the length field can be predefined by the protocol, pre-configured by the first network device, determined through negotiation between the UE and the first network device, or it can be determined based on the first indication information. Taking the determination of the length field content based on the first indication information as an example: For instance, if the first indication information indicates that the number of bits occupied by the length field is less than the fourth threshold or that the length field is short, then the length field can indicate the length of the RoHC header; or, if the first indication information indicates that the number of bits occupied by the length field is greater than or equal to the fourth threshold or that the length field is long, then the length field can indicate the length of the RLC SDU. It is evident that there are many ways to determine the content indicated by the length field, making it quite flexible.
[0456] If the length field indicates the length of the MAC SDU, the receiving end (e.g., the first network device) of the K MAC SDUs can determine the length of the K MAC SDUs based on the length fields included in the K MAC subheaders. Alternatively, if the length field indicates the length of the RoHC header included in the MAC SDU, the first network device can determine the length of the K MAC SDUs based on the length fields included in the K MAC subheaders and the offset. For example, for any one of the K MAC SDUs, the first network device can determine the length of the MAC SDU based on the length fields included in the MAC subheaders of the MAC SDU and the offset corresponding to the MAC SDU. The offset corresponding to the MAC SDU may include, for example, the length of the PDCP header, the length of the RLC header, and the length of the RoHC header included in the MAC SDU.
[0457] Referring to Figure 20, an example of a MAC subheader is shown. The left side of Figure 20 shows a traditional MAC subheader, and the right side shows a MAC subheader provided in this embodiment. Taking the sixth MAC PDU as an example, which includes two MAC SDUs, namely MAC SDU1 and MAC SDU2. The MAC subheader of MAC SDU1 includes a length field 1, and the MAC subheader of MAC SDU2 includes a length field 2. As shown in the right image of Figure 20, the MAC subheader of MAC SDU2 does not include the LCID or the DRB identifier, thus saving the overhead of the MAC subheader. In addition, Figure 20 shows an example where the MAC subheader of MAC SDU1 includes the LCID. As shown in the left and right images of Figure 20, the length fields 1 and 2 in this embodiment are shorter, while the length fields 1 and 2 in the traditional scheme are longer; moreover, some MAC subheaders in this embodiment may not include the LCID and DRB identifiers, while in the traditional scheme, each MAC subheader includes the LCID. Through the technical solution of this embodiment, the overhead of the MAC subheader is reduced.
[0458] Referring again to Figure 21, another example of a MAC subheader is shown. The left side of Figure 21 shows a traditional MAC subheader, and the right side shows a MAC subheader provided in this embodiment. Taking the sixth MAC PDU as an example, which includes two MAC SDUs, namely MAC SDU1 and MAC SDU2. The MAC subheader of MAC SDU1 includes a length field 1, and the MAC subheader of MAC SDU2 includes a length field 2. As shown in the right image of Figure 21, the MAC subheader of MAC SDU2 does not include the LCID or DRB identifier, thus saving the overhead of the MAC subheader. In addition, Figure 21 shows that the MAC subheader of MAC SDU1 does not include the LCID or DRB identifier. As shown in the left and right images of Figure 21, the length fields 1 and 2 in this embodiment are shorter, while the length fields 1 and 2 in the traditional scheme are longer; moreover, all MAC subheaders in this embodiment can omit the LCID and DRB identifiers, while each MAC subheader in the traditional scheme includes the LCID. Through the technical solution of this embodiment, the overhead of the MAC subheader is reduced.
[0459] Optionally, any one of the K MAC subheaders may also include a second field, which indicates whether there is a next cascaded MAC SDU with the same LCID or DRB. For example, in Figure 20 or Figure 21, "E" represents the second field. A cascaded MAC SDU can be understood as a MAC SDU included within the same MAC PDU.
[0460] The second field can occupy one or more bits. These bits can be newly added to the MAC header or reused bits already present in the MAC header. In the scheme of reusing existing bits, for any one of the K MAC headers, the one or more bits occupied by the second field of that MAC header can optionally belong to the length field of that MAC header. This can also be understood as reducing the length field of the MAC header, and the resulting portion or all of the bits can be used as the second field. For example, for any MAC SDU, the length field of its MAC header originally occupies one byte, i.e., 8 bits. This length field can be reduced, for example, by one bit, so that the length field occupies 7 bits, resulting in one bit. This one bit can then be used as the second field; that is, the second field can occupy one bit. Figures 20 and 21 use this as an example. Reusing existing bits in the MAC header for the second field, thus avoiding the need to add new bits to the MAC header, is beneficial for compatibility with existing technologies.
[0461] Optionally, the third resource can transmit MAC CEs in addition to MAC SDUs. The MAC CE and the K MAC SDUs are, for example, included in the sixth MAC PDU. The MAC CE also has a MAC subheader, for example called the fourth MAC subheader, and the fourth MAC subheader is not shortened; for example, the fourth MAC subheader may include MAC CE LCID, etc. Optionally, on the third resource, the MAC subheader of the MAC CE can be placed before the MAC subheader of the MAC SDU; for example, the fourth MAC subheader can be placed before the K MAC subheaders.
[0462] Optionally, each of the K MAC subheaders and the fourth MAC subheader may include second indication information. This second indication information may indicate that the MAC subheader containing the second indication information corresponds to a MAC CE or a MAC SDU. The second indication information may occupy one or more bits. Optionally, the second indication information may occupy one or more bits at the beginning of the MAC subheader, for example, the first bit within the MAC subheader.
[0463] Optionally, the second indication information included in any of the K MAC subheaders can be a first value, and the value of the second indication information included in the fourth MAC subheader can be a second value. The first value can indicate that the MAC subheader is a MAC subheader of a MAC SDU; the second value can indicate that the fourth MAC subheader is a MAC subheader of a MAC CE.
[0464] Taking the second indication information occupying one bit as an example, for instance, the first value is "1" and the second value is "0". Then, if the bit is "1", it indicates that the MAC subheader where the second indication information is currently located corresponds to the MAC SDU, or indicates that the MAC subheader where the second indication information is currently located is the MAC subheader of the MAC SDU; or, if the bit is "0", it indicates that the MAC subheader where the second indication information is currently located corresponds to the MAC CE, or indicates that the MAC subheader where the second indication information is currently located is the MAC subheader of the MAC CE.
[0465] In this embodiment, since the transmission resource can correspond to the identifier of LCID or DRB, the MAC subheader can be made to exclude the identifier of LCID or DRB, thereby reducing the overhead of the MAC subheader. Furthermore, if MAC CE and MAC SDU are transmitted on the same resource, the second indication information can be used to distinguish the MAC subheaders of these two types, thereby reducing the probability of incorrect identification by the receiver.
[0466] The embodiments shown in any of the figures 6-8, 10-14, and 17-18 can be applied individually, or any two or more embodiments can be applied in combination. For example, one combination includes the first communication device using one or more of the following to generate data packets or MAC PDUs: the RRC layer of the first communication device can reduce the packet header using the embodiment shown in Figure 8; the NAS layer of the first communication device can reduce the packet header using the embodiment shown in Figure 11; the RLC layer of the first communication device can reduce the packet header using the embodiment shown in Figure 13 or Figure 14; or the MAC layer of the first communication device can reduce the packet header using the embodiment shown in Figure 17 or Figure 18.
[0467] Figure 22 shows a schematic diagram of the structure of an apparatus provided in an embodiment of this application. The communication device 2200 can be a first communication device or its circuit system as described in any one of the embodiments shown in Figures 6-8, 10-14, and 17-18, used to implement the method corresponding to the first communication device in the above method embodiments. Alternatively, the communication device 2200 can be a second communication device or its circuit system as described in any one of the embodiments shown in Figures 6-8, 10-14, and 17-18, used to implement the method corresponding to the second communication device in the above method embodiments. Alternatively, the communication device 2200 can be a third communication device or its circuit system as described in any one of the embodiments shown in Figures 6-8, 10-14, and 17-18, used to implement the method corresponding to the third communication device in the above method embodiments. For example, one type of circuit system is a chip system.
[0468] The communication device 2200 includes at least one processor 2201. The processor 2201 can be used for internal processing within the device to implement certain control processing functions. Optionally, the processor 2201 includes instructions. Optionally, the processor 2201 can store data. Optionally, different processors can be independent devices, located in different physical locations, or located on different integrated circuits. Optionally, different processors can be integrated into one or more processors, for example, integrated on one or more integrated circuits.
[0469] Optionally, the communication device 2200 includes one or more memories 2203 for storing instructions. Optionally, the memories 2203 may also store data. The processor and the memories may be separate or integrated together.
[0470] Optionally, the communication device 2200 includes a communication line 2202 and at least one communication interface 2204. Since the memory 2203, communication line 2202, and communication interface 2204 are all optional, they are all represented by dashed lines in Figure 22.
[0471] Optionally, the communication device 2200 may further include a transceiver and / or an antenna. The transceiver can be used to send information to or receive information from other devices. The transceiver may be referred to as a transceiver unit, transceiver circuit, input / output interface, etc., and is used to realize the transmission and reception functions of the communication device 2200 via the antenna. Optionally, the transceiver includes a transmitter and a receiver. For example, the transmitter can be used to generate a radio frequency (RF) signal from a baseband signal, and the receiver can be used to convert the RF signal back into a baseband signal.
[0472] Processor 2201 may include a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs according to the present application.
[0473] Communication line 2202 may include a path for transmitting information between the aforementioned components.
[0474] Communication interface 2204 uses any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), wired access network, etc.
[0475] Memory 2203 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. Memory 2203 may exist independently and be connected to processor 2201 via communication line 2202. Alternatively, memory 2203 may be integrated with processor 2201.
[0476] The memory 2203 stores computer execution instructions for implementing the present application scheme, and its execution is controlled by the processor 2201. The processor 2201 executes the computer execution instructions stored in the memory 2203, thereby implementing the steps performed by the first, second, or third communication device as described in any of the embodiments shown in Figures 6-8, 10-14, and 17-18.
[0477] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.
[0478] In a specific implementation, as one example, processor 2201 may include one or more CPUs, such as CPU0 and CPU1 in FIG22.
[0479] In a specific implementation, as one embodiment, the communication device 2200 may include multiple processors, such as processors 2201 and 2205 in FIG. 22. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. Here, a processor may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).
[0480] When the device shown in Figure 22 is a chip, such as the chip of the first communication device, the chip of the second communication device, or the chip of the third communication device, the chip includes a processor 2201 (which may also include a processor 2205), a communication line 2202, and a communication interface 2204. Optionally, it may include a memory 2203. Specifically, the communication interface 2204 may be an input interface, pins, or circuits, etc. The memory 2203 may be a register, a cache, etc. The processor 2201 and the processor 2205 may be a general-purpose CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of a program that controls the communication method of any of the above embodiments.
[0481] This application embodiment can divide the device into functional modules according to the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or software functional modules. The module division in this application embodiment is illustrative and only represents one logical functional division; in actual implementation, there may be other division methods. For example, when dividing the device into functional modules according to each function, Figure 23 is a schematic diagram of a device. This device 2300 can be the first, second, or third communication device involved in the above method embodiments, or a chip in the first, second, or third communication device. The device 2300 includes a processing unit 2302 and a transceiver unit 2301.
[0482] It should be understood that the device 2300 can be used to implement the steps performed by the first communication device, the second communication device, or the third communication device in the communication method of the embodiments of this application. The relevant features can be referred to the embodiments shown in any one of the above figures 6 to 8, 10 to 14, and 17 to 18, which will not be repeated here.
[0483] Optionally, the functions / implementation processes of the transceiver unit 2301 and processing unit 2302 in Figure 23 can be implemented by the processor 2201 in Figure 22 calling computer execution instructions stored in memory 2203. Alternatively, the functions / implementation processes of the processing unit 2302 in Figure 23 can be implemented by the processor 2201 in Figure 22 calling computer execution instructions stored in memory 2203, and the functions / implementation processes of the transceiver unit 2301 in Figure 23 can be implemented by the communication interface 2204 in Figure 22.
[0484] Optionally, when the device 2300 is a chip or circuit, the function / implementation process of the transceiver unit 2301 can also be implemented through pins or circuits. Optionally, the transceiver unit 2301 may include a transmitting unit and / or a receiving unit, whereby the transmitting unit implements the transmitting function and the receiving unit implements the receiving function; or, the transceiver unit 2301 may be an integral module capable of implementing both transmitting and / or receiving functions. Optionally, the transceiver unit 2301 can be implemented using a transceiver.
[0485] This application also provides a computer-readable storage medium storing a computer program or instructions that, when executed, implement the methods performed by the first and / or second and / or third communication devices in the aforementioned method embodiments. Thus, the functions described in the above embodiments can be implemented as software functional units and sold or used as independent products. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to it, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.
[0486] This application also provides a computer program product comprising: computer program code, which, when run on a computer, causes the computer to perform the method executed by the first communication device and / or the second communication device and / or the third communication device in any of the foregoing method embodiments.
[0487] This application also provides a processing apparatus, including a processor and an interface; the processor is used to execute the methods performed by the first communication device and / or the second communication device and / or the third communication device involved in any of the above method embodiments.
[0488] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).
[0489] The various illustrative logic units and circuits described in the embodiments of this application can be implemented or operate the described functions using a general-purpose processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor can be a microprocessor; alternatively, it can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented using a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration.
[0490] The steps of the methods or algorithms described in the embodiments of this application can be directly embedded in hardware, software units executed by a processor, or a combination of both. The software units can be stored in RAM, flash memory, ROM, erasable programmable read-only memory (EPROM), EEPROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from the storage medium and write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and storage medium can be disposed in an ASIC, which can be disposed in the terminal device. Optionally, the processor and storage medium can also be disposed in different components of the terminal device.
[0491] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.
[0492] The contents of the various embodiments of this application can be referenced to each other. Unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.
[0493] It is understood that in the embodiments of this application, the first communication device and / or the second communication device and / or the third communication device may execute some or all of the steps in the embodiments of this application. These steps or operations are merely examples. In the embodiments of this application, other operations or variations of various operations may also be performed. Furthermore, the steps may be performed in different orders as presented in the embodiments of this application, and it is not necessary to perform all the operations in the embodiments of this application.
Claims
1. A communication method characterized by comprising: The method includes: The first layer of the first communication device delivers a first data packet to the second layer of the first communication device, wherein the first data packet includes voice data, the first layer is a non-access layer, and the second layer is a radio resource control layer; The second layer transmits the second data packet via the first signaling radio bearer, and the second data packet is determined based on the first data packet; Wherein, the first signaling radio bearer is a signaling radio bearer dedicated to transmitting voice data, the second data packet does not include a radio resource control header, or the first signaling radio bearer adopts a radio resource control pass-through mode, wherein the radio resource control pass-through mode means that the second layer does not encode the data packets on the first signaling radio bearer; or... The second data packet is included in a first message on the first signaling radio bearer, the first message being a dedicated control channel message used for transmitting voice data.
2. The method of claim 1, wherein, The first signaling radio bearer corresponds to the first logical channel, wherein the first signaling radio bearer is a signaling radio bearer dedicated to transmitting voice data, and the identifier of the first logical channel is different from the logical channel identifier corresponding to signaling radio bearer 1, and is different from the logical channel identifier corresponding to signaling radio bearer 1 (repeated bis).
3. The method of claim 1, wherein, The first message is a dedicated control channel message used specifically for transmitting voice data, wherein, The first message includes at least one reserved bit for indicating that the first data packet includes the voice data, or for indicating that the first message is a message dedicated to sending voice data.
4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The first layer encrypts the first data packet but does not provide integrity protection.
5. The method according to any one of claims 1 to 3, characterized in that, The first data packet includes a first non-access layer header, and the method further includes: The second layer compresses the first non-access layer header to obtain a second non-access layer header, which includes a sequence number SQN. The second data packet includes the second non-access layer header.
6. The method according to any one of claims 1 to 3, characterized in that, The first data packet includes a first non-access layer header, and the method further includes: The second layer removes the first non-access layer header to obtain the second data packet.
7. The method according to claim 5 or 6, characterized in that, The first non-access layer header includes a first field, which indicates that the NAS protocol data unit (PDU) in the first data packet is encrypted and not protected for integrity.
8. The method according to any one of claims 5 to 7, characterized in that, The first non-access layer header includes a second field, and the second field is either all 0s or all 1s; or, The first non-access layer header does not include the second field; The second field is used for integrity protection.
9. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The first layer determines that the first data packet includes a first non-access layer header based on the fact that the first data packet includes the voice data, and the first non-access layer header includes SQN.
10. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The first layer determines that the first data packet does not include the non-access layer header based on the fact that the first data packet includes the voice data.
11. The method according to any one of claims 6 to 8, 10, characterized in that, The method further includes: Send a first message, which indicates the offset between the SQN and the Radio Link Control (RLC) Sequence Number (SN) of the second data packet.
12. A communication method characterized by comprising: The method is applied to a first communication device, and the method includes: The sixth data packet is received via the second signaling radio bearer; It is determined that the NAS PDU included in the sixth data packet is encrypted and not protected for integrity (this feature may be optional in the embodiment).
13. The method according to claim 12, characterized in that, The second signaling radio bearer is a signaling radio bearer dedicated to transmitting voice data, and the sixth data packet does not include a radio resource control header, or the second signaling radio bearer is in radio resource control pass-through mode; or, The second signaling radio bearer is signaling radio bearer 1bis or signaling radio bearer 1, and the sixth data packet is included in the third message on the second signaling radio bearer. The third message is a dedicated control channel message used for transmitting voice data.
14. The method of claim 13, wherein, Determining that the NAS PDU included in the sixth data packet was encrypted and not protected for integrity includes: Based on the second signaling radio bearer or the third message, it is determined that the NAS PDU included in the sixth data packet is encrypted and not protected for integrity.
15. The method according to claim 12 or 13, characterized in that, The sixth data packet may include a fourth non-access layer header, or the sixth data packet may not include a non-access layer header, wherein the fourth non-access layer header includes SQN, and the method further includes: The second layer of the first communication device recovers the fourth non-access layer header to obtain a third non-access layer header, which includes one or more of the following: the SQN, length information, security header type field, first protocol discriminator field, message authentication code, bearer identifier, second protocol discriminator field, program processing identifier, or, ESM data transmission message identifier.
16. The method according to claim 15, characterized in that, Determining that the NAS PDU included in the sixth data packet was encrypted and not protected for integrity includes: Based on the security header type field, it is determined that the NAS PDU included in the sixth data packet is encrypted and not protected for integrity.
17. A method of communication, comprising: The method is applied to a second communication device, and the method includes: The second data packet is received via the first signaling wireless bearer; The second data packet is determined to include voice data based on the fact that the first signaling radio bearer is a signaling radio bearer dedicated to transmitting voice data, or the second data packet is determined to include voice data based on the fact that the second data packet is included in a dedicated control channel message dedicated to transmitting voice data.
18. The method of claim 17, wherein, The first signaling radio bearer corresponds to the first logical channel, wherein the first signaling radio bearer is a signaling radio bearer dedicated to transmitting voice data, and the identifier of the first logical channel is different from the logical channel identifier corresponding to signaling radio bearer 1, and also different from the logical channel identifier corresponding to signaling radio bearer 1bis.
19. The method according to claim 17, characterized in that, The first message is a dedicated control channel message used specifically for transmitting voice data, wherein, The first message includes at least one reserved bit for indicating that the second data packet includes the voice data, or for indicating that the first message is a message dedicated to sending voice data.
20. The method according to any one of claims 17 to 19, characterized in that, The second data packet includes a second non-access stratum header, which is a compressed non-access stratum header; or, The second data packet does not include a non-access stratum header.
21. The method according to claim 20, characterized in that, The second data packet does not include a non-access stratum header, and the method further includes: Receive first information, which indicates the offset between the SQN of the first data packet and the RLC SN of the first data packet.
22. The method according to any one of claims 17 to 21, characterized in that, The method further includes: The second layer of the second communication device recovers the non-access layer header of the second data packet to obtain a third data packet. The second layer is the radio resource control layer. The third data packet includes a first non-access layer header, which includes one or more of the following: SQN, length information, security header type field, first protocol discriminator field, message authentication code, bearer identifier, second protocol discriminator field, program processing identifier, or ESM data transmission message identifier. The second layer sends the third data packet.
23. The method according to claim 22, characterized in that, The security header type field indicates that the NAS PDU in the second data packet is encrypted and not protected for integrity.
24. The method according to claim 22 or 23, characterized in that, The first non-access layer header includes the message authentication code, and the message authentication code is either all 0s or all 1s; or, The first non-access layer header does not include the message authentication code.
25. The method according to any one of claims 17 to 21, characterized in that, The method further includes: Send the second data packet and the first indication information, the first indication information being used to indicate one or more of the following: the second data packet carries voice data, the SQN included in the second data packet includes only the lower N bits, the identifier carried by the Evolved Packet System (EPS) corresponding to the second data packet, or the SQN.
26. The method according to claim 25, characterized in that, The second data packet includes a first non-access stratum header, which includes an SQN.
27. A communication device, characterized in that, The communication device includes a module for performing the method as described in any one of claims 1 to 11, or includes a module for performing the method as described in any one of claims 12 to 16, or includes a module for performing the method as described in any one of claims 17 to 26.
28. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when the computer program is run on the first communication device or on a chip in the first communication device, causes the method as described in any one of claims 1 to 11 to be executed, or causes the method as described in any one of claims 12 to 16 to be executed.
29. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when run on the second communication device or a chip in the second communication device, causes the method as described in any one of claims 17 to 26 to be executed.
30. A computer program product, characterized in that, The computer program product includes a computer program that, when run on a first communication device or a chip in the first communication device, causes the method as described in any one of claims 1 to 11 to be executed, or causes the method as described in any one of claims 12 to 16 to be executed.
31. A computer program product, characterized in that, The computer program product includes a computer program that, when run on a second communication device or a chip in the second communication device, causes the method as described in any one of claims 17 to 26 to be executed.
32. A communication system, characterized in that, The communication system includes a first communication device and a second communication device, wherein... The first communication device is configured to perform the method as described in any one of claims 1 to 11; The second communication device is used to perform the method as described in any one of claims 17 to 26.
