Communication method and apparatus

Abstract

Embodiments of the present application relate to the field of communications, and provide a communication method and apparatus, for use in preventing transmission of service data from being affected due to misalignment of data compression formats between network devices and terminal devices. In the method, a network device may send, to a terminal device, a first message comprising configuration information and first information, wherein the first information may be used to indicate to the terminal device a time for applying the configuration information; the terminal device may quickly determine, on the basis of the first information, the time for applying the configuration information, and at the time for applying the configuration information, apply the configuration information, i.e., using a compression format corresponding to the configuration information to perform transmission with the network device. In this way, alignment of data compression formats between terminal devices and network devices can be achieved, thereby preventing transmission of service data from being affected due to misalignment of data compression formats between network devices and terminal devices.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202411038812.5, filed with the State Intellectual Property Office of China on July 30, 2024, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a communication method and apparatus. Background Technology

[0003] Currently, network devices can send Radio Resource Control (RRC) reconfiguration messages to terminal devices as needed. These RRC reconfiguration messages can include compressed configuration information or compressed reconfiguration information to change the data compression format. For example, the data format can be changed from compressed to uncompressed, from uncompressed to compressed, or the compression algorithm can be changed. When a terminal device receives an RRC reconfiguration message, it can apply the compressed configuration information or compressed reconfiguration information and send an RRC reconfiguration completion message back to the network device.

[0004] However, when the terminal device sends an RRC reconfiguration completion message to the network device, the compressed configuration information or compressed reconfiguration information may not have taken effect or been completed yet. At this time, the data compression formats between the network device and the terminal device may be misaligned, which may prevent the terminal device and the network device from using the correct decompression format to decompress the received data, thus affecting the transmission of service data. Summary of the Invention

[0005] This application provides a communication method and apparatus to avoid affecting the transmission of business data due to misalignment of data compression formats between network devices and terminal devices.

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

[0007] Firstly, a communication method is provided. This method can be executed by a terminal device, by a module applied to the terminal device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the terminal device's functions. For ease of description, the following description assumes the method is executed by a terminal device. The method includes: receiving a first message from a network device and applying configuration information based on first information. The first message includes configuration information and first information; the configuration information includes relevant configurations for data compression formats; and the first information indicates the time of applying the configuration information.

[0008] As can be seen from the method described in the first aspect, the network device can send a first message containing configuration information and first information to the terminal device. The first information can be used to indicate the time when the terminal device applies the configuration information. The terminal device can quickly determine the time to apply the configuration information based on the first information, and apply the configuration information at the time of application. That is, it uses the compression format corresponding to the configuration information to transmit with the network device. In this way, the data compression formats between the terminal device and the network device can be aligned to avoid the transmission of business data and the user experience being affected by the misalignment of data compression formats between the network device and the terminal device.

[0009] In one possible design, the first information includes at least one of the following: a first application time, a first timestamp, a first timestamp and a first duration, a first data packet number, or a second data packet number and a first value. The specific information can be flexibly selected according to actual circumstances to meet the needs of different scenarios, and this application embodiment does not limit this. Furthermore, the first information may also include any other possible parameters, without limitation.

[0010] In one possible design scheme, the application configuration information, based on the first information, includes at least one of the following: applying the configuration information at a first application time; or, obtaining a first duration and applying the configuration information at a second time, wherein the second time is determined based on a first timestamp and a first duration; or, applying the configuration information at a second time, wherein the second time is determined based on a first timestamp and a first duration; or, applying the configuration information when processing a first data packet based on its number; or, applying the configuration information when processing a third data packet based on its number, wherein the number of the third data packet is determined based on the number of a second data packet and a first value, where the first value is the number of data packets. The specific number can be flexibly selected according to the actual situation and is not limited thereto. Other implementations are also possible and are not limited thereto. In this way, the terminal device can accurately determine the time for applying the configuration information based on the first information, achieving flexibility.

[0011] In one possible design, the first timestamp is the time the first message is sent, and the first duration is greater than or equal to the transmission delay between the terminal device and the network device. That is, the time the network device sends the first message plus the first duration is the time the terminal device applies the configuration information. If the configuration time required for the configuration information or the time required for the Packet Data Convergence Protocol (PDCP) entity re-establishment process is short and can be ignored, then it can be considered equal to the time the network device sends the first message plus the transmission delay between the terminal device and the network device, which is the time the terminal device applies the configuration information. If the configuration time required for the configuration information or the time required for the PDCP entity re-establishment process is long (e.g., greater than a preset duration), then it can be considered equal to the time the network device sends the first message plus the first duration (greater than the transmission delay between the terminal device and the network device), which is the time the terminal device applies the configuration information. It can be understood that when the terminal device applies the configuration information, the configuration of the configuration information or the PDCP entity re-establishment has been completed.

[0012] In one possible design, the application configuration information includes: re-establishing the Packet Data Convergence Protocol (PDCP) entity according to the configuration information; processing the first data to be transmitted using the re-established PDCP entity to obtain the first data; and sending the first data to the network device. In this way, the terminal device can send the first data to the network device using the data compression format indicated by the configuration information, so as to ensure that the network device can decompress the first data using the correct decompression format, thereby ensuring the normal transmission of service data.

[0013] In one possible design, the method described in the first aspect may further include: sending indication information to the network device. The indication information indicates that the first data was obtained from application configuration information. Thus, the network device can explicitly determine, based on the indication information, that the first data was obtained by the terminal device using the data compression format indicated by the configuration information, i.e., displaying an indication, thereby achieving flexibility.

[0014] In one possible design, the method described in the first aspect may further include: receiving second data from a network device. The second data is generated by the network device using a data compression format when the configuration information is applied. That is, the network device can send the second data to the terminal device using the data compression format when the terminal device applies the configuration information. This ensures that the terminal device can use the correct decompression format to decompress the second data, thereby guaranteeing the normal transmission of service data.

[0015] Secondly, a communication method is provided. This method can be executed by a network device, by a module applied to the network device (such as a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the network device. For ease of description, the following description uses the execution of the method by a network device as an example. The method includes: generating a first message and sending the first message to a terminal device. The first message includes configuration information and first information. The configuration information includes relevant configurations for data compression formats, and the first information indicates the time when the configuration information is applied.

[0016] In one possible design, the first information includes at least one of the following: a first application time, a first timestamp, a first timestamp and a first duration, a first data packet number, or a second data packet number and a first value.

[0017] In one possible design, the method described in the second aspect may further include: receiving first data from the terminal device. The first data is obtained from the application configuration information at the time of application configuration information.

[0018] In one possible design, the method described in the second aspect may further include: receiving indication information from a terminal device. The indication information is used to indicate that the first data was obtained from application configuration information.

[0019] In one possible design, the method described in the second aspect may further include: sending second data to the terminal device using a data compression format when the configuration information is applied.

[0020] Furthermore, the technical effects of the method described in the second aspect can be found in the description of the method described in the first aspect, and will not be repeated here.

[0021] Thirdly, a communication method is provided. This method can be executed by a terminal device, by a module applied to the terminal device (such as a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the terminal device's functions. For ease of description, the following description uses the method executed by a terminal device as an example. The method includes: receiving configuration information from a network device, and sending first information to the network device according to the configuration information. The configuration information includes relevant configurations for data compression formats; the first information indicates the time when the terminal device applies the configuration information.

[0022] Based on the method described in the third aspect, when the terminal device receives configuration information including data compression format configuration sent by the network device, the terminal device can send the time when it applied the configuration information to the network device through the first information. The network device can quickly determine the time when the terminal device applied the configuration information based on the first information. In this way, the data compression format between the terminal device and the network device can be aligned to avoid affecting the transmission of business data and the user experience due to the misalignment of data compression formats between the network device and the terminal device.

[0023] In one possible design, the first information includes at least one of the following: a first application time, a first timestamp, a first timestamp and a first duration, a first data packet number, or a second data packet number and a first value. The specific information can be flexibly selected according to actual circumstances to meet the needs of different scenarios, and this application embodiment does not limit this. Furthermore, the first information may also include any other possible parameters, without limitation.

[0024] In one possible design, the method described in the third aspect may further include: receiving second data from a network device. The second data is generated by the network device using a data compression format at the time the configuration information is applied. That is, the network device can send the second data to the terminal device using the data compression format at the time the terminal device applies the configuration information, as determined by the first information. This ensures that the terminal device can use the correct decompression format to decompress the second data, thereby guaranteeing the normal transmission of service data.

[0025] In one possible design, the method described in the third aspect may further include: applying configuration information at the time of application. Optionally, applying the configuration information includes: re-establishing the Packet Data Convergence Protocol (PDCP) entity according to the configuration information, processing the first data to be transmitted using the re-established PDCP entity to obtain the first data, and sending the first data to the network device. Thus, at the time of application of the configuration information, the terminal device can send the first data to the network device using the data compression format indicated by the configuration information, ensuring that the network device can decompress the first data using the correct decompression format, thereby ensuring the normal transmission of service data.

[0026] In one possible design, the method described in the third aspect may further include: sending indication information to the network device. The indication information indicates that the first data was obtained from application configuration information. Thus, the network device can explicitly determine, based on the indication information, that the first data was obtained by the terminal device using the data compression format indicated by the configuration information, i.e., displaying an indication, thereby achieving flexibility.

[0027] Fourthly, a communication method is provided. This method can be executed by a network device, by a module applied to the network device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the network device. For ease of description, the following description uses the execution of the method by a network device as an example. The method includes: sending configuration information to a terminal device and receiving first information from the terminal device. The configuration information includes relevant configurations for data compression formats, and the first information indicates the time of application of the configuration information.

[0028] In one possible design, the first information includes at least one of the following: a first application time, a first timestamp, a first timestamp and a first duration, a first data packet number, or a second data packet number and a first value.

[0029] In one possible design, the method described in the fourth aspect may further include: sending second data to the terminal device using a data compression format based on the first information.

[0030] In one possible design scheme, based on the first information, second data is sent to the terminal device using a data compression format, including at least one of the following: sending the second data to the terminal device using a data compression format at a first application time; or, obtaining a first duration and sending the second data to the terminal device using a modified data compression format at a second time, wherein the second time is determined based on a first timestamp and a first duration; or, sending the second data to the terminal device using a data compression format at a second time, wherein the second time is determined based on a first timestamp and a first duration; or, sending the second data to the terminal device using a data compression format when receiving data corresponding to the number of a first data packet; or, sending the second data to the terminal device using a data compression format when receiving data corresponding to the number of a third data packet, wherein the number of the third data packet is determined based on the number of the second data packet and a first value, the first value being the number of data packets, which can be flexibly selected according to the actual situation and is not limited thereto. Other implementations are also possible and are not limited thereto. In this way, the network device can accurately determine the time when the terminal device applies the configuration information based on the first information, so that it can subsequently use this data compression format to send the second data to the terminal device, achieving flexibility.

[0031] In one possible design, the first timestamp is the time when the first information is sent, and the first duration is greater than or equal to the transmission delay between the terminal device and the network device. That is, the time when the terminal device sends the first information plus the first duration is the time when the terminal device applies the configuration information. If the configuration time required for the configuration information or the time required for the PDCP entity re-establishment process is short and can be ignored, then it can be considered equal to the time when the terminal device sends the first information plus the transmission delay between the terminal device and the network device, which is the time when the terminal device applies the configuration information. If the configuration time required for the configuration information or the time required for the PDCP entity re-establishment process is long (e.g., greater than a preset duration), then it can be considered equal to the time when the terminal device sends the first information plus the first duration (greater than the transmission delay between the terminal device and the network device), which is the time when the terminal device applies the configuration information. It can be understood that when the terminal device applies the configuration information, the configuration of the configuration information or the PDCP entity re-establishment has been completed.

[0032] In one possible design, the method described in the fourth aspect may further include: receiving first data from the terminal device. The first data is obtained from the application configuration information at the time of application configuration information.

[0033] In one possible design, the method described in the fourth aspect may further include: receiving indication information from a terminal device; wherein the indication information is used to indicate that the first data is obtained from application configuration information.

[0034] Furthermore, the technical effects of the method described in the fourth aspect can be found in the description of the method described in the third aspect, and will not be repeated here.

[0035] Fifthly, a communication method is provided. This method can be executed by a terminal device, a module applied to the terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the terminal device's functions. For ease of description, the following description assumes the method is executed by a terminal device. The method includes: receiving configuration information from a network device; processing first data to be transmitted according to compression configuration information to obtain first data; releasing a first logical channel and adding a second logical channel according to RLC configuration information; and sending the first data to the network device through the second logical channel. The configuration information includes Radio Link Control (RLC) configuration information and compression configuration information. The RLC configuration information includes relevant configurations for changing the RLC bearer, and the compression configuration information includes relevant configurations for data compression formats. The first logical channel is the logical channel used before applying the compression configuration information.

[0036] Based on the method described in the fifth aspect, the network device can send configuration information containing compression configuration information and RLC configuration information to the terminal device. The terminal device can perform logical channel changes based on the RLC configuration information, such as releasing the first logical channel used by the terminal device before applying the compression configuration information and adding a new second logical channel. The terminal device can use the second logical channel to send the first data obtained by processing the first data to be transmitted according to the data compression format indicated by the compression configuration information to the network device. That is, the terminal device can carry the first data obtained by applying the configuration information through the new second logical channel. In this way, the data obtained by the terminal device before applying the compression configuration information and the data obtained after applying the compression configuration information (the two data formats are different, i.e., a change has occurred) can be carried in different logical channels. The terminal device can directly release the first logical channel to avoid the MAC layer being reset due to the PDCP entity re-establishment, which would clear other service data and reduce the impact on the cached data on other radio bearers.

[0037] In one possible design, processing the first data to be transmitted according to compression configuration information to obtain the first data includes: the Packet Data Convergence Protocol (PDCP) layer of the terminal device performs PDCP entity re-establishment according to the compression configuration information, and uses the re-established PDCP entity to process the first data to be transmitted to obtain the first data. That is, the terminal device compresses the data at the PDCP layer. After receiving the compression configuration information, the terminal device can perform PDCP entity re-establishment. Thus, the terminal device can send the first data to the network device using the data compression format indicated by the compression configuration information, thereby ensuring the normal transmission of service data.

[0038] In one possible design, the first data to be transmitted is processed according to the compression configuration information to obtain the first data. This includes: the Radio Resource Control (RRC) layer of the terminal device processes the first data to be transmitted according to the compression configuration information to obtain the first data. That is, the terminal device compresses the data at the RRC layer. Thus, the terminal device can send the first data to the network device using the data compression format indicated by the compression configuration information, ensuring the normal transmission of service data and meeting the needs of different scenarios.

[0039] In one possible design, the method described in the fifth aspect may further include: the Radio Resource Control (RRC) layer of the terminal device sending a PDCP re-establishment request message to the Packet Data Convergence Protocol (PDCP) layer of the terminal device according to compressed configuration information; and the PDCP layer of the terminal device re-establishing the PDCP entity according to the PDCP re-establishment request message. The PDCP re-establishment request message is used to request the re-establishment of the PDCP entity. That is, after receiving the compressed configuration information, the RRC layer of the terminal device can trigger the sending of a PDCP re-establishment request message to the PDCP layer to achieve on-demand instruction and flexibility.

[0040] In one possible design, releasing the first logical channel includes: clearing the data cached in the first logical channel to save overhead.

[0041] Sixthly, a communication method is provided. This method can be executed by a network device, by a module applied to the network device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the network device. For ease of description, the following description uses the execution of the method by a network device as an example. The method includes: sending configuration information to a terminal device and receiving first data from the terminal device. The configuration information includes Radio Link Control (RLC) configuration information and compression configuration information. The RLC configuration information includes relevant configurations for changing the RLC bearer, and the compression configuration information includes relevant configurations for the data compression format.

[0042] Other technical effects of the communication method described in the sixth aspect can be referred to the technical effects of the communication method described in the fifth aspect, and will not be repeated here.

[0043] A seventh aspect provides a communication device. The communication device includes: a module for performing the method described in the first aspect, such as a transceiver module and a processing module. The transceiver module is used to instruct the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0044] For example, a transceiver module is used to receive a first message from a network device. A processing module is used to apply configuration information based on the first message. The first message includes configuration information and the first information itself; the configuration information includes relevant configurations for data compression formats, and the first information indicates the time at which the configuration information is applied.

[0045] In one possible design, the first information includes at least one of the following: a first application time, a first timestamp, a first timestamp and a first duration, a first data packet number, or a second data packet number and a first value.

[0046] In one possible design, the processing module is further configured to perform at least one of the following: applying configuration information at a first application time; or, obtaining a first duration and applying configuration information at a second time, wherein the second time is determined based on a first timestamp and a first duration; or, applying configuration information at a second time, wherein the second time is determined based on a first timestamp and a first duration; or, applying configuration information when processing a first data packet based on the number of the first data packet; or, applying configuration information when processing a third data packet based on the number of the third data packet, wherein the number of the third data packet is determined based on the number of the second data packet and a first value, the first value being the number of data packets.

[0047] In one possible design, the first timestamp is the time when the first message is sent, and the first duration is greater than or equal to the transmission delay between the communication device and the network device as described in the seventh aspect.

[0048] In one possible design, the processing module is further configured to re-establish the Packet Data Convergence Protocol (PDCP) entity according to configuration information, and use the re-established PDCP entity to process the first data to be transmitted to obtain the first data. The transceiver module is further configured to send the first data to the network device.

[0049] In one possible design, the transceiver module is also used to send indication information to the network device. This indication information indicates that the first data was obtained from application configuration information.

[0050] In one possible design, the transceiver module is also used to receive second data from the network device, wherein the second data is generated by the network device using a data compression format when applying configuration information.

[0051] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the seventh aspect, and the receiving module implements the receiving function of the communication device described in the seventh aspect.

[0052] Optionally, the communication device described in the seventh aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the first aspect.

[0053] It is understood that the communication device described in the seventh aspect may be a terminal device, or a chip (system) or other component or assembly that can be disposed in the terminal device, or a device that includes the terminal device; this application does not limit this.

[0054] Furthermore, the technical effects of the communication device described in the seventh aspect can be referred to the technical effects of the method described in the first aspect, and will not be repeated here.

[0055] Eighthly, a communication device is provided. The communication device includes: a module for performing the method described in the second aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0056] For example, a processing module is used to generate a first message. A transceiver module is used to send the first message to the terminal device. The first message includes configuration information and first information; the configuration information includes relevant configurations for the data compression format, and the first information indicates the time of application configuration.

[0057] In one possible design, the first information includes at least one of the following: a first application time, a first timestamp, a first timestamp and a first duration, a first data packet number, or a second data packet number and a first value.

[0058] In one possible design, the transceiver module is further configured to receive first data from the terminal device. This first data is obtained from the application configuration information at the time specified in the application configuration information.

[0059] In one possible design, the transceiver module is further configured to receive indication information from the terminal device. This indication information indicates that the first data was obtained from application configuration information.

[0060] In one possible design, the transceiver module is also used to send second data to the terminal device using a data compression format when the application configuration information is being applied.

[0061] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the eighth aspect, and the receiving module implements the receiving function of the communication device described in the eighth aspect.

[0062] Optionally, the communication device described in the eighth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the second aspect.

[0063] It is understood that the communication device described in the eighth aspect may be a network device, or a chip (system) or other component or assembly that can be disposed in a network device, or a device that includes a network device; this application does not limit this.

[0064] Furthermore, the technical effects of the communication device described in the eighth aspect can be referred to the technical effects of the method described in the second aspect, and will not be repeated here.

[0065] A ninth aspect provides a communication device. The communication device includes: a module for performing the method described in the third aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0066] For example, a transceiver module is used to receive configuration information from network devices. A processing module is used to send first information to the network devices based on the configuration information. The configuration information includes settings related to data compression formats; the first information indicates when the terminal device should apply the configuration information.

[0067] In one possible design, the first information includes at least one of the following: a first application time, a first timestamp, a first timestamp and a first duration, a first data packet number, or a second data packet number and a first value.

[0068] In one possible design, the transceiver module is further configured to receive second data from the network device. This second data is generated by the network device using a data compression format when applying configuration information.

[0069] In one possible design, the processing module is also used to apply configuration information at the time of application configuration information.

[0070] In one possible design, the processing module is further configured to re-establish the Packet Data Convergence Protocol (PDCP) entity according to configuration information, and use the re-established PDCP entity to process the first data to be transmitted to obtain the first data. The transceiver module is further configured to send the first data to the network device.

[0071] In one possible design, the transceiver module is also used to send indication information to the network device, wherein the indication information is used to indicate that the first data is obtained from application configuration information.

[0072] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the ninth aspect, and the receiving module implements the receiving function of the communication device described in the ninth aspect.

[0073] Optionally, the communication device described in the ninth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the third aspect.

[0074] It is understood that the communication device described in the ninth aspect may be a terminal device, or a chip (system) or other component or assembly that can be disposed in the terminal device, or a device that includes the terminal device, and this application does not limit it in this regard.

[0075] Furthermore, the technical effects of the communication device described in the ninth aspect can be referred to the technical effects of the method described in the third aspect, and will not be repeated here.

[0076] A tenth aspect provides a communication device. The communication device includes: a module for performing the method described in the fourth aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0077] For example, the transceiver module is used to send configuration information to the terminal device and receive first information from the terminal device. The configuration information includes settings related to the data compression format, and the first information indicates the time at which the configuration information is applied.

[0078] In one possible design, the first information includes at least one of the following: a first application time, a first timestamp, a first timestamp and a first duration, a first data packet number, or a second data packet number and a first value.

[0079] In one possible design, the transceiver module is also used to send second data to the terminal device using a data compression format based on the first information.

[0080] In one possible design, the processing module is configured to perform at least one of the following: at a first application moment, sending second data to the terminal device using a data compression format; or, obtaining a first duration and sending the second data to the terminal device using a modified data compression format at a second time, wherein the second time is determined based on a first timestamp and the first duration; or, sending the second data to the terminal device using a data compression format at a second time, wherein the second time is determined based on a first timestamp and the first duration; or, sending the second data to the terminal device using a data compression format upon receiving data corresponding to the number of a first data packet; or, sending the second data to the terminal device using a data compression format upon receiving data corresponding to the number of a third data packet, wherein the number of the third data packet is determined based on the number of the second data packet and a first value, the first value being the number of data packets.

[0081] In one possible design, the first timestamp is the time when the first information is sent, and the first duration is greater than or equal to the transmission delay between the terminal device and the network device.

[0082] In one possible design, the transceiver module is further configured to receive first data from the terminal device. This first data is obtained from the application configuration information at the time specified in the application configuration information.

[0083] In one possible design, the transceiver module is further configured to receive indication information from the terminal device. This indication information indicates that the first data was obtained from application configuration information.

[0084] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the tenth aspect, and the receiving module implements the receiving function of the communication device described in the tenth aspect.

[0085] Optionally, the communication device according to the tenth aspect may further include a storage module storing a program or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the fourth aspect.

[0086] It is understood that the communication device described in the tenth aspect may be a network device, or a chip (system) or other component or assembly that can be disposed in a network device, or a device that includes a network device, and this application does not limit it in this regard.

[0087] Furthermore, the technical effects of the communication device described in the tenth aspect can be referred to the technical effects of the method described in the fourth aspect, and will not be repeated here.

[0088] Eleventhly, a communication device is provided. The communication device includes: modules for performing the method described in the fifth aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0089] For example, the transceiver module is used to receive configuration information from the network device. The processing module is used to process the first data to be transmitted according to the compression configuration information to obtain the first data, and to process the first data to be transmitted according to the compression configuration information to obtain the first data. The transceiver module is also used to send the first data to the network device through a second logical channel. The configuration information includes Radio Link Control (RLC) configuration information and compression configuration information. The RLC configuration information includes relevant configurations for changing the RLC bearer, and the compression configuration information includes relevant configurations for the data compression format. The first logical channel is the logical channel used before applying the compression configuration information.

[0090] In one possible design, the processing module is further configured to, according to the compression configuration information, perform PDCP entity re-establishment at the Packet Data Convergence Protocol (PDCP) layer of the communication device described in the eleventh aspect, and use the re-established PDCP entity to process the first data to be transmitted to obtain the first data.

[0091] In one possible design, the processing module is further configured to, in the radio resource control (RRC) layer of the communication device described in the eleventh aspect, process the first data to be transmitted according to the compression configuration information to obtain the first data.

[0092] In one possible design, the transceiver module is used to send a PDCP re-establishment request message to the Packet Data Convergence Protocol (PDCP) layer of the communication device described in the eleventh aspect, based on compressed configuration information. The processing module is further configured to allow the PDCP layer of the communication device to re-establish the PDCP entity based on the PDCP re-establishment request message. The PDCP re-establishment request message is used to request the re-establishment of the PDCP entity.

[0093] In one possible design, a processing module is used to clear the data cached in the first logical channel.

[0094] Optionally, the transceiver module may include a sending module and a receiving module. The sending module implements the sending function of the communication device described in the eleventh aspect, and the receiving module implements the receiving function of the communication device described in the eleventh aspect.

[0095] Optionally, the communication device described in the eleventh aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the fifth aspect.

[0096] It is understood that the communication device described in the eleventh aspect may be a terminal device, or a chip (system) or other component or assembly that can be disposed in a terminal device, or a device that includes a terminal device, and this application does not limit it in this regard.

[0097] Furthermore, the technical effects of the communication device described in the eleventh aspect can be referred to the technical effects of the method described in the fifth aspect, and will not be repeated here.

[0098] In a twelfth aspect, a communication device is provided. The communication device includes: a module for performing the method described in the sixth aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0099] For example, the processing module controls the transceiver module to send configuration information to the terminal device. The transceiver module receives the first data from the terminal device. The configuration information includes Radio Link Control (RLC) configuration information and compression configuration information. The RLC configuration information includes relevant configurations for changing the RLC bearer, and the compression configuration information includes relevant configurations for the data compression format.

[0100] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the twelfth aspect, and the receiving module implements the receiving function of the communication device described in the twelfth aspect.

[0101] Optionally, the communication device described in the twelfth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the sixth aspect.

[0102] It is understood that the communication device described in the twelfth aspect may be a network device, or a chip (system) or other component or assembly that can be disposed in a network device, or a device that includes a network device, and this application does not limit it in this regard.

[0103] Furthermore, the technical effects of the communication device described in the twelfth aspect can be referred to the technical effects of the method described in the sixth aspect, and will not be repeated here.

[0104] In a thirteenth aspect, a communication device is provided. The communication device includes a processor configured to execute the method described in any one of the possible implementations of the first to sixth aspects.

[0105] In one possible design, the communication device described in aspect thirteen may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in aspect thirteen and other communication devices.

[0106] In one possible design, the communication device described in aspect thirteen may further include a memory. This memory may be integrated with the processor or disposed separately. The memory may be used to store computer programs and / or data relating to the methods described in any of aspects one through six.

[0107] In the embodiments of this application, the communication device described in the thirteenth aspect may be a terminal device described in any one of the first, third, or fifth aspects, or a chip (system) or other component or assembly disposed in the terminal device, or a device comprising the terminal device; or, the communication device described in the thirteenth aspect may be a network device described in any one of the second, fourth, or sixth aspects, or a chip (system) or other component or assembly disposed in the network device, or a device comprising the network device.

[0108] Furthermore, the technical effects of the communication device described in aspect thirteen can be referred to the technical effects of the method described in any of the implementations of aspects one through six, and will not be repeated here.

[0109] Fourteenth aspect, a communication device is provided. The communication device includes: a processor coupled to a memory, the processor being configured to execute a computer program stored in the memory, such that the communication device performs the method described in any one of the possible implementations of the first to sixth aspects.

[0110] In one possible design, the communication device described in aspect fourteen may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in aspect fourteen and other communication devices.

[0111] In the embodiments of this application, the communication device described in the fourteenth aspect may be a terminal device described in any one of the first, third, or fifth aspects, or a chip (system) or other component or assembly disposed in the terminal device, or a device comprising the terminal device; or, the communication device described in the fourteenth aspect may be a network device described in any one of the second, fourth, or sixth aspects, or a chip (system) or other component or assembly disposed in the network device, or a device comprising the network device.

[0112] Furthermore, the technical effects of the communication device described in the fourteenth aspect can be referred to the technical effects of the method described in any of the implementations of the first to sixth aspects, and will not be repeated here.

[0113] In a fifteenth aspect, a communication device is provided, comprising: a processor and a memory; the memory being configured to store a computer program, which, when executed by the processor, causes the communication device to perform the method described in any one of the first to sixth aspects.

[0114] In one possible design, the communication device described in aspect fifteen may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in aspect fifteen and other communication devices.

[0115] In the embodiments of this application, the communication device described in the fifteenth aspect may be a terminal device described in any one of the first, third, or fifth aspects, or a chip (system) or other component or assembly disposed in the terminal device, or a device comprising the terminal device; or, the communication device described in the fifteenth aspect may be a network device described in any one of the second, fourth, or sixth aspects, or a chip (system) or other component or assembly disposed in the network device, or a device comprising the network device.

[0116] Furthermore, the technical effects of the communication device described in aspect fifteen can be referred to the technical effects of the method described in any of the implementations of aspects one through six, and will not be repeated here.

[0117] In a sixteenth aspect, a communication device is provided, comprising: a processor; the processor being configured to be coupled to a memory, and after reading a computer program from the memory, to execute, according to the computer program, the method as described in any one of the first to sixth aspects.

[0118] In one possible design, the communication device described in the sixteenth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the sixteenth aspect and other communication devices.

[0119] In the embodiments of this application, the communication device described in the sixteenth aspect may be a terminal device described in any one of the first, third, or fifth aspects, or a chip (system) or other component or assembly disposed in the terminal device, or a device comprising the terminal device; or, the communication device described in the sixteenth aspect may be a network device described in any one of the second, fourth, or sixth aspects, or a chip (system) or other component or assembly disposed in the network device, or a device comprising the network device.

[0120] Furthermore, the technical effects of the communication device described in the sixteenth aspect can be referred to the technical effects of the method described in any of the implementations of the first to sixth aspects, and will not be repeated here.

[0121] In a seventeenth aspect, a communication system is provided. The communication system includes: the terminal device described in the first aspect and the network device described in the second aspect.

[0122] Eighteenthly, a communication system is provided. The communication system includes: the terminal device described in the third aspect and the network device described in the fourth aspect.

[0123] Nineteenthly, a communication system is provided. The communication system includes: the terminal device described in the fifth aspect and the network device described in the sixth aspect.

[0124] In a twentieth aspect, a communication chip is provided, wherein instructions are stored that, when the chip is operated on a communication device, cause the communication method described in any one of the first to sixth aspects to be implemented.

[0125] A twenty-first aspect provides a computer-readable storage medium comprising: a computer program or instructions; wherein, when the computer program or instructions are executed on a computer, the computer causes the computer to perform the method described in any one of the possible implementations of the first to sixth aspects.

[0126] In a twenty-second aspect, a computer program product is provided, comprising a computer program or instructions that, when executed on a computer, cause the computer to perform the method described in any one of the possible implementations of the first to sixth aspects. Attached Figure Description

[0127] Figure 1 is a schematic diagram of the AI ​​application framework in NR;

[0128] Figure 2 is a schematic diagram of the user plane protocol stack;

[0129] Figure 3 is a schematic diagram of the process by which a network device sends an RRC reconfiguration message to a terminal device;

[0130] Figure 4 is a schematic diagram of different compression formats used on different RBs;

[0131] Figure 5 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0132] Figure 6 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0133] Figure 7 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0134] Figure 8 is a schematic flowchart of a communication method provided in an embodiment of this application;

[0135] Figure 9 is a time-based schematic diagram of terminal device application configuration information provided in an embodiment of this application;

[0136] Figure 10 is a schematic diagram of a communication method provided in an embodiment of this application;

[0137] Figure 11 is a schematic flowchart of a communication method provided in an embodiment of this application;

[0138] Figure 12 is a schematic flowchart of a communication method provided in an embodiment of this application;

[0139] Figure 13 is a schematic flowchart of a communication method provided in an embodiment of this application;

[0140] Figure 14 is a flowchart illustrating a communication method applied to an O-RAN architecture according to an embodiment of this application;

[0141] Figure 15 is a schematic diagram of the communication device provided in an embodiment of this application;

[0142] Figure 16 is a schematic diagram of the structure of the communication device provided in the embodiment of this application. Detailed Implementation

[0143] For ease of understanding, the technical terms involved in the embodiments of this application will be introduced below.

[0144] 1. Artificial intelligence (AI)

[0145] AI, a technology proposed in the 1950s, simulates complex calculations by mimicking the human brain. With advancements in data storage and computing power, AI has found increasing applications. The 3rd Generation Partnership Project (3GPP) release R17 approved a Study Item (SI) proposing the application of AI in New Radio (NR) to improve network performance and user experience through intelligent data collection and analysis.

[0146] Based on discussions within the 3GPP Radio Access Network (RAN) 3 working group, a preliminary framework for AI applications in NR has been defined, as shown in Figure 1. This AI application framework mainly includes: a data collection entity, a model training entity, a model inference entity, and an actor entity. The data collection entity stores data inputs from various sources, including next-generation NodeBs (gNBs), gNB-central units (CUs), gNB-distributed units (DUs), user equipment (UEs), and other management entities, serving as a database for AI model training and data analysis inference. The model training entity analyzes the training data provided by the data collection entity, outputs the optimal AI model, and sends the model deployment / update results to the model inference entity. The model inference entity can use (model scheduling or updated) AI models, based on inference data provided by the data collection entity, to make reasonable AI-based predictions about network operation or guide the network to make policy adjustments. The inference results are then sent as output to the execution entity. Simultaneously, the model inference entity can send model performance feedback to the model training entity. Related policy adjustments can be planned uniformly by the execution entity and sent to multiple network entities for execution. Furthermore, the network's specific performance after applying the relevant policies is again input into the database as feedback and stored.

[0147] Currently, 3GPP, through working groups such as RAN3 and RAN1, has designed several basic application scenarios / use cases (UCs) for AI on the RAN side. RAN3 includes energy saving, load balancing, and mobility optimization, while RAN1 includes channel state information-reference signal (CSI-RS) feedback enhancement, beam management enhancement, and positioning accuracy enhancement. The basic principles of each use case are briefly introduced below.

[0148] Energy saving involves collecting load, energy consumption, and energy efficiency information from the base station and neighboring cells, as well as UE trajectory information and measurement results, to predict the load trend. This prediction, combined with cell usage and key performance indicators (KPIs) requirements, allows for timely and appropriate energy-saving measures without affecting network coverage or user access. The simplest energy-saving strategy involves directly deactivating the cell. Other strategies include carrier shutdown, channel shutdown, time slot shutdown, and reduced transmit power. More complex strategies combine these measures. When network coverage is affected or cannot meet UE access and service requirements, the current energy-saving strategy needs to be modified, or the system needs to revert to normal operation. In such cases, load re-prediction or a change in the AI ​​model used for re-inference should be considered.

[0149] Load balancing: By collecting load, energy consumption, and energy efficiency information from its own and neighboring cells, as well as UE trajectory information and measurement results, base stations predict their own load trends. Combined with cell usage and KPI requirements, they rationally select some UEs to hand over to neighboring cells or receive UEs from neighboring cells, ensuring that the load levels among base stations across the entire network are similar, reducing situations where some base stations are overloaded and affecting normal services while others are idle. However, because the accuracy of prediction is not 100%, unreasonable UE selection or handover target cells may occur, leading to handover failures or impact on UE services. Inaccurate load prediction may result in poor load balancing, or temporary abnormal load changes may render the original load balancing strategy inapplicable. In such cases, it is necessary to exit or modify the current load balancing strategy and consider re-predicting the load or changing the AI ​​model used for re-inference.

[0150] Mobility optimization: By collecting historical trajectory information of the UE from the base station and combining it with the UE's measurement information, the future trajectory of the UE is predicted. Based on the predicted trajectory, it is determined in advance whether the UE needs to handover, and handover configuration is sent in advance, and the target cell is notified to prepare access resources, reducing the latency of the UE during the handover process and lowering the probability of handover and access failures. However, since the accuracy of trajectory prediction is not 100%, when the predicted trajectory is incorrect, it will lead to UE handover failure and service interruption. In this case, it is necessary to consider retraining the model and inference based on the abnormal situation, or consider replacing the model, to avoid similar abnormal situations from occurring again in subsequent UEs.

[0151] CSI-RS feedback enhancement: The main process of current CSI-RS feedback enhancement can be as follows: (1) The base station and UE first exchange a dictionary. Usually, the base station trains a model in advance according to the UE's capabilities and its own requirements, and then sends an encoder and quantizer tool to the UE; (2) The UE compresses and quantizes the matrix to be fed back according to the measured channel matrix results and the existing dictionary, and sends the result B to the base station; (3) The base station recovers the original channel matrix in reverse according to the dictionary and the data reported by the UE.

[0152] Beam management enhancement: The main process of beam management enhancement can be as follows: (1) Initial model generation: The base station reports the full beam scanning results of the synchronization signaling block (SSB) by a certain number of UEs to train a sparse scanning matrix. This matrix is ​​usually unique to each cell; (2) The base station sends the sparse model to the UE (which can be done through system information block (SIB) messages, etc.), and the UE performs beam scanning in the P1 stage based on this matrix; (3) Based on the sparse scanning results of the UE, the base station infers the optimal CSI-RS beam and starts to perform P2 scanning on the UE. The UE feeds back the optimal CSI-RS beam identifier (ID).

[0153] Positioning accuracy enhancement: The main process of current positioning accuracy enhancement can be as follows: (1) The base station uses the reference UE controlled by the operator to collect raw data; the location management function (LMF) (non-RAN side node) and gNB train models respectively. The LMF model can infer the final positioning (such as latitude and longitude), and the gNB model can infer the line of sight (LOS) and non-line of sight (NLOS) judgment results.

[0154] Based on the above introduction, the application environment of the model will be described below.

[0155] For different AI-based UC applications, the UE can be configured to perform different functions. For example, in a CSI feedback enhancement case, the UE can be configured to perform CSI channel prediction. Regarding how to implement a specific function, the UE can choose from multiple models with the same function (meaning all can provide the required output). The selection can be configured on the network side or the UE can choose based on its internal implementation. The selection is usually based on the model's application environment. In current standard discussions, there are many classifications of model application environments, which typically include the following aspects:

[0156] (1) Macroscopic physical attributes of the UE, such as the UE's speed, direction of movement, geographical location, altitude, etc.; (2) Hardware and software attributes of the UE, such as the UE's effective power, computing power, storage space, compilation environment of the supported AI models, etc.; (3) Channel environment in which the UE is located, such as urban macro (UMa), urban micro (UMi), indoor hotspot (InH), etc.; (4) Communication configuration between the UE and gNB, such as the number of receiving antennas of the UE and the number of transmitting ports of the gNB, etc.; (5) Time and frequency domain resources of air interface communication, such as carrier frequency, subcarrier spacing, bandwidth, etc.

[0157] Even models that can achieve the same function may have different performance in different application environments. Therefore, it is usually necessary to select the most suitable model based on the actual application environment of the UE.

[0158] 2. Radio bearer (RB)

[0159] RB is the collective term for the different layer protocol entities and configurations allocated by the base station to the UE. Figure 2 shows a schematic diagram of the user plane protocol stack of a 5th generation (5G) mobile communication system. As shown in Figure 2, the user plane protocol stack includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, the Medium Access Control (MAC) layer, and the Physical Layer (PHY). Among them, the SDAP layer is mainly responsible for mapping the Quality of Service (QoS) flow to the Data Radio Bearer (DRB); the PDCP layer is mainly responsible for header compression, encryption, and integrity protection; the RLC layer is mainly responsible for data segmentation and reassembly; the MAC layer is mainly responsible for logical channel (LC) multiplexing, hybrid automatic repeat request (HARQ) retransmission, and scheduling-related functions; and the PHY layer is mainly responsible for encoding, decoding, modulation, demodulation, and multi-antenna mapping functions.

[0160] For each layer in the protocol stack, data received from (or sent to) the layer above can be called a service data unit (SDU), and data sent to (or received from) the layer below can be called a protocol data unit (PDU). For example, data received from the PDCP layer by the RLC layer can be called an RLC SDU (or PDCP PDU), and the data output by the RLC layer after processing is called an RLC PDU (or MAC SDU). The channel between the RLC layer and the MAC layer is called a logical channel. The MAC layer can perform logical multiplexing, that is, it can multiplex one or more RLC PDUs from the RLC layer into a single MAC PDU and pass it to the PHY. For the PHY, a MAC PDU is also called a transport block (TB).

[0161] As shown in Figure 3, a terminal device can include an RRC layer, SDAP layer, PDCP layer, RLC layer, and MAC layer. The RRC layer can be a higher layer of the control plane, mainly responsible for the air interface resource transmission between control layer (L1) and L2, and providing information transmission services for the non-access stratum (NAS). Currently, network devices can send radio resource control (RRC) reconfiguration messages to terminal devices as needed. These RRC reconfiguration messages can include compressed configuration information or compressed reconfiguration information to change the data compression format, such as changing the data format from compressed to uncompressed, from uncompressed to compressed, or changing the compression algorithm. When the terminal device receives the RRC reconfiguration message, it can apply the compressed configuration information or compressed reconfiguration information and send an RRC reconfiguration completion message back to the network device.

[0162] However, in this scenario, the following problems may exist:

[0163] Problem A: When the terminal device sends an RRC reconfiguration completion message to the network device, the compressed configuration information or compressed reconfiguration information may not have taken effect or been completed yet. At this time, the data compression formats between the network device and the terminal device may not be aligned. For example, PDCP re-establishment may not be completed yet, which will prevent the terminal device and the network device from using the correct decompression format to decompress the received data. For example, if the network device sends data to the terminal device using a new compression format, the terminal device may not be able to decompress the data. At the same time, the network device will also consider the data sent by the terminal device to be obtained using the new compression format, which will also prevent the network device from decompressing the data, affecting the transmission of service data.

[0164] Question B: Within the same RB, if the compression format changes (e.g., from compressed to uncompressed, from uncompressed to compressed, or the compression algorithm is changed; network devices can indicate the change in compression format through compression configuration information or compression reconfiguration information), the MAC layer needs to be reset. At this time, in addition to the cached data on the RB whose compression format has changed being cleared, the cached data on other service RBs will also be cleared.

[0165] For example, current standards discuss AI data collection, as training AI models requires a large amount of data. Existing technologies consider compressing the data collected by AI, such as using uplink data compression (UDC) algorithms to compress user plane data. UDC is based on a lossless data compression protocol, a lossless compression algorithm primarily based on the LZ77 algorithm and Huffman coding, to compress data.

[0166] As shown in Figure 4, taking RBx and RBy as examples, RBx carries Internet Protocol (IP) data packets #n and #n+1, while RBy carries IP data packets #m. IP packets #n and #n+1 pass through the SDAP layer (header (H) + SDAP SDU), PDCP layer (H + PDCP SDU), and RLC layer (H + RLC SDU), respectively; IP packet #m passes through the SDAP layer (H + SDAP SDU), PDCP layer (H + PDCP SDU), and RLC layer ((H + SDU segment #1) + (H + SDU segment #2)). Then, the MAC layer combines the H + SDAP SDUs corresponding to IP packets #n and #n+1, and the H + SDU segment #1 corresponding to IP packet #m, and adds a MAC subheader to encapsulate it into a MAC PDU. This MAC PDU can be carried by a TB. The PHY no longer segments the data delivered by the MAC layer, but matches it with the actual physical channel resource size through rate matching.

[0167] In this scenario, assuming that at time t, the data compression format on RBx changes, such as from compressed to uncompressed, meaning that the same RBx contains different compression formats (including compressed and uncompressed data), the MAC layer needs to perform a reset. In addition to the RB that compresses the data, i.e., the cached data on RBx will be cleared, and the cached data on other service RBs, i.e., RBy (where the data compression format has not changed), such as H+SDU segment #1, will also be cleared.

[0168] Therefore, how to prevent business data on other RBs from being cleared in order to reduce the impact on cached data on other RBs is an urgent problem to be solved.

[0169] In summary, to address the aforementioned technical problems, this application proposes the following technical solutions to avoid affecting the transmission of business data due to misalignment of data compression formats between network devices and terminal devices.

[0170] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0171] The technical solutions of this application embodiment can be applied to various communication systems, such as wireless fidelity (WiFi) systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, 4G such as long term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, 5G such as new radio (NR) systems, and future communication systems, etc.

[0172] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0173] Furthermore, in the embodiments of this application, the words "exemplary," "for example," etc., are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the term "exemplary" is intended to present the concept in a concrete manner.

[0174] In the embodiments of this application, the terms "information," "signal," "message," "channel," and "signaling" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, their intended meanings are consistent. Similarly, "of," "corresponding (relevant)," and "corresponding" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, their intended meanings are consistent. Furthermore, the " / " mentioned in this application can be used to indicate an "or" relationship. It is understood that in this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing an instruction information used to indicate A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A.

[0175] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to instruct the information to be instructed, such as, but not limited to, directly instructing the information to be instructed, such as the information to be instructed itself or its index; indirectly instructing the information to be instructed by instructing other information, where there is a relationship between the other information and the information to be instructed; or instructing only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent.

[0176] The information to be instructed can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device.

[0177] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0178] To facilitate understanding of the embodiments of this application, the communication system applicable to the embodiments of this application will be described in detail first using the communication system shown in FIG5 as an example. For example, FIG5 is a schematic diagram of the architecture of a communication system to which the communication method provided in the embodiments of this application applies.

[0179] As shown in Figure 5, the communication system mainly includes network equipment and terminal equipment.

[0180] There can be multiple network devices, such as a first network device, a second network device, a third network device, etc. A network device can be a device with wireless transceiver capabilities, or it can be a chip or chip system located in the access network (AN) of the communication system to provide access services to the terminal. For example, a network device can be called an RAN device, specifically an access network device in a future mobile communication system, such as a base station in a future mobile communication system. Alternatively, network devices may have other naming conventions in future mobile communication systems, all of which are covered within the protection scope of the embodiments of this application, and this application does not impose any limitations on them. Alternatively, network equipment can also include 5G, such as a gNB in ​​a new radio (NR) system, or one or a group of antenna panels (including multiple antenna panels) of a 5G base station. It can also be network nodes constituting a gNB, transmission and reception point (TRP) or transmission point (TP), or transmission measurement function (TMF), such as CU, DU, CU-control plane (CP), CU-user plane (UP), or radio unit (RU), roadside unit (RSU) with base station functionality, or wired access gateway, or 5G core network elements, etc. Alternatively, network equipment can also include: access points (APs) in wireless fidelity (WiFi) systems, wireless relay nodes, wireless backhaul nodes, various forms of macro base stations, micro base stations (also called small cells), relay stations, access points, wearable devices, vehicle-mounted equipment, etc.

[0181] In this network, CU and DU can be configured separately or included in the same network element, such as a baseband unit (BBU). RU can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). It is understood that network equipment can be CU nodes, DU nodes, or a combination of CU and DU nodes. Furthermore, CUs can be classified as network equipment in the access network (RAN) or in the core network (CN); there are no restrictions on this classification.

[0182] 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 radio unit (O-CU), DU can also be called an open distributed unit (O-DU), CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0183] In this embodiment, the form of the network device is not limited. The device used to implement the function of the network device can be the network device itself, or it can be a device that supports the network device in implementing the function, such as a chip system. The device can be installed in the network device or used in conjunction with the network device.

[0184] There can be one or more terminal devices, such as a first terminal device, a second terminal device, a third terminal device, etc. A terminal device can be a terminal device with transceiver capabilities, or it can be a chip or chip system installed in that terminal device. This terminal device can also be referred to as user equipment (UE), access terminal equipment, subscriber unit, user station, mobile station (MS), mobile station, remote station, remote terminal equipment, mobile device, user terminal equipment, terminal equipment, wireless communication equipment, user agent, or user apparatus. The terminal devices in the embodiments of this application may be mobile phones, cellular phones, smartphones, tablets, wireless data cards, personal digital assistants (PDAs), wireless modems, handsets, laptop computers, machine-type communication (MTC) terminal devices, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminal devices in autonomous driving, wireless terminal devices in industrial control, wireless terminal devices in self-driving, wireless terminal devices in remote medical care, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, and smart homes. The terminal equipment in this application can be a wireless terminal device (e.g., a vehicle-mounted terminal device), an RSU with terminal device functions, or a flight device (e.g., an intelligent robot, a hot air balloon, a drone, or an airplane). The terminal equipment in this application can also be a vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip, or vehicle-mounted unit that is built into a vehicle as one or more components or units. The terminal equipment can also be other devices with terminal device functions; for example, the terminal equipment can also be a device that performs terminal device functions in D2D communication.

[0185] The embodiments of this application do not limit the form of the terminal device. The device used to implement the function of the terminal device can be the terminal device itself; it can also be a device that supports the terminal device in implementing the function, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete components.

[0186] In this communication system, the network device can send a first message containing configuration information and first information to the terminal device. The first information can be used to indicate when the terminal device should apply the configuration information. Based on the first information, the terminal device can quickly determine the time to apply the configuration information and apply it at that time. That is, it uses the compression format corresponding to the configuration information to transmit with the network device. In this way, the data compression formats between the terminal device and the network device can be aligned to avoid the transmission of business data and the user experience being affected by the misalignment of data compression formats between the network device and the terminal device.

[0187] It is understandable that the communication system shown in Figure 5 above can be applied to the sub-scenario of data collection in the AI ​​scenario. That is, the terminal device can have AI function and can collect AI data; the access network device, such as the base station, can manage the access and handover of the terminal device and communicate with the core network (CN) device (such as the core network element, which can manage the access network device and has AI function) and has AI function.

[0188] The communication system shown in Figure 5 can be used in different communication system architectures. For example, it can be applied to the communication system shown in Figure 6. As shown in Figure 6, the network device can be RAN, the terminal device can be UE, and the AI ​​data can be obtained by CN or RAN from UE, or by UE from RAN or CN.

[0189] For example, the communication system shown in Figure 5 can be applied to the communication system shown in Figure 7, namely the open-radio access network (O-RAN) architecture. As shown in Figure 7, the O-DU has baseband processing capabilities and complete protocol layer functions, mainly responsible for higher-level protocol functions such as data encryption and integrity protection, and can also have physical layer high-level processing functions; the O-RU has physical layer low-level signal processing functions, mainly responsible for the transmission and reception of radio frequency signals. AI data can be collected by the O-DU or CN, and the terminal device reports the collected data.

[0190] It is understood that Figures 5-7 are simplified schematic diagrams for ease of understanding only. The communication system may also include other network devices and / or other terminal devices, which are not shown in Figures 5-7.

[0191] For ease of understanding, the communication method provided in the embodiments of this application will be described in detail below with reference to Figures 8-14.

[0192] To address problem A above, Figure 8 is, for example, a flowchart illustrating a communication method provided in an embodiment of this application. This method can be applied to communication between terminal devices and network devices in the aforementioned communication system.

[0193] Specifically, as shown in Figure 8, the flow of this communication method is as follows:

[0194] S801, the network device generates the first message.

[0195] The first message may include configuration information and first information.

[0196] The configuration information is described below.

[0197] Configuration information may include settings related to data compression formats. This configuration information can be determined by the network device based on the compression capability information reported by the terminal device. After the terminal device connects to the network device, it begins interacting with the network device. For example, the compression capability information reported by the terminal may include: the compression algorithms supported by the terminal device, the terminal device's data caching capability, and supported service categories. The terminal device can support multiple compression algorithms, such as UDC, AI compression, fast compression, LZW (lempel-ziv-welch encoding), and LZMA (lempel-ziv-markov chain-algorithm) compression algorithms. If the network device and the terminal device agree to use only one compression algorithm for data compression, the terminal device only needs to report whether it supports compression. The terminal device's data caching capability is related to the compression algorithms it supports. For compression algorithms that require caching, the terminal device reports its supported caching capability. Generally speaking, the terminal device's data caching capability represents the size of the lookup dictionary it supports; the larger the cache, the more strings can be stored, and the higher the corresponding compression ratio.

[0198] Network devices can determine configuration information based on the compression capability information reported by terminal devices. This configuration information may include at least one of the following: the compression algorithm used for compression, data caching capability, compression format (such as zip, rar, 7z, tgz, etc.), the number of compressed packets N (e.g., compressing the first N data packets, where N is an integer greater than or equal to 0), the types of services that can be compressed (e.g., Hypertext Transfer Protocol (HTTP) services, IP services, etc.), the dictionary used for compression, the fields that can be compressed, and the configuration to perform compression on uplink data, downlink data, or both uplink and downlink data, etc., without limitation.

[0199] Uplink data can refer to data sent from the terminal device to the network device, and downlink data can refer to data sent from the network device to the terminal device. It is understood that the network device determines the specific implementation of the configuration information based on the compression capability information reported by the terminal device, and can refer to existing technologies without limitation. The network device can also obtain this configuration information through any other possible implementation, and this application embodiment does not limit this. For ease of understanding, the following description uses the example of configuration information including the use of data compression format #1, performing compression on both uplink and downlink data, and will not be elaborated further.

[0200] Optionally, the configuration information may also include indication information for changing the data compression format, which can be denoted as indication information #a. That is, data compression format #1 can be a new data compression format. Before the terminal device applies this configuration information, the terminal device and the network device use other data compression formats, such as data compression format #2, to transmit data. Changing the data compression format can include: changing the data compression format from compressed (e.g., data compression format #2 is a compressed format, such as zip format) to uncompressed (data compression format #1 is an uncompressed format), changing the data compression format from uncompressed (data compression format #2 is an uncompressed format) to compressed (e.g., data compression format #1 is a compressed format, such as zip format), or changing the data compression algorithm (e.g., changing from UDC to AI compression, and the corresponding data format also changes), etc., without limitation. It is understood that the configuration information may also include any other possible signaling or parameters, without limitation.

[0201] It is understood that the above configuration information can be compressed configuration information or compressed reconfiguration information (such as if the previous compressed configuration needs to be changed). The compressed configuration information or compressed reconfiguration information can be carried or contained in the PDCP configuration information, that is, carried in the existing message to reduce the implementation difficulty, or it can be carried in the new message to improve the implementation flexibility, without limitation.

[0202] The first piece of information will be introduced below.

[0203] The first information can be used to indicate the time when the terminal device applies the configuration information, that is, the time when the terminal device sends data to the network device using the data compression format indicated by the configuration information, such as data compression format #1 (as described in the first data below), and / or decompresses the data received from the network device (as described in the second data).

[0204] It is understood that when the terminal device applies the configuration information, it has already completed the configuration process for the configuration information or the PDCP entity re-establishment process. Alternatively, the first information indicating the time when the terminal device applies the configuration information can be: the first information indicating the time when the terminal device completes the configuration process for the configuration information or the PDCP entity re-establishment process. In this case, the terminal device can determine the time when it needs to start executing the configuration of the configuration information or the PDCP entity re-establishment process, such as time #a, based on the time when the terminal device completes the configuration process for the configuration information or the PDCP entity re-establishment process and historical data (such as the configuration time required for the configuration information or the average time required for the PDCP entity re-establishment process, or a time greater than the average time). Subsequently, the terminal device can start executing the configuration process for the configuration information or the PDCP entity re-establishment process at time #a.

[0205] In one possible design scheme, the first information may include at least one of the following: first application time, first timestamp, first timestamp and first duration, number of first data packet, or number of second data packet and first value. For details, please refer to the specific description in step S803 below, which will not be repeated here.

[0206] Network devices can determine the first information based on the time required for terminal devices to complete configuration of configuration information or PDCP entity re-establishment (such as historical data reported by terminal devices), or any other possible implementation. This embodiment of the application does not limit this. It is understood that the first information may also include any other possible signaling or parameters, without limitation.

[0207] In this way, the network device can obtain the first message. This first message can be carried in an RRC reconfiguration message, a radio bearer setup request message, a radio bearer reconfiguration message, a cell update confirm message, an RRC connection setup message, etc., that is, it can be carried in an existing message to reduce implementation difficulty, or it can be carried in a new message to improve implementation flexibility; there is no limitation. It can be understood that the first message can also include any other possible signaling or parameters, without limitation.

[0208] It is understood that the naming of the above configuration information, first information, and first message is only an example and can be replaced with any other possible names without limitation.

[0209] In S802, the network device sends the first message to the terminal device. Correspondingly, the terminal device receives the first message from the network device.

[0210] The network device can send the first message generated in step S801 to the terminal device. For example, when the network device needs the terminal device to change the currently used data compression format (such as changing the data compression format #2 to the data compression format #1), or to process the data to be transmitted (such as the first data to be transmitted below) using new (compression-related) configuration information, the network device can send the first message to the terminal device through RRC reconfiguration messages, radio bearer establishment request messages, radio bearer configuration messages, cell update messages, RRC connection setup messages, etc. This application embodiment does not limit this.

[0211] S803, the terminal device uses the first information to apply the configuration information.

[0212] For example, step S803 may specifically include at least one of the following:

[0213] The terminal device displays application configuration information at the first application moment; or...

[0214] The terminal device obtains a first duration and applies configuration information at a second time, wherein the second time is determined based on the first timestamp and the first duration; or,

[0215] The terminal device applies configuration information at a second time, wherein the second time is determined based on the first timestamp and the first duration; or,

[0216] The terminal device applies configuration information when processing the first data packet based on the packet's number; or,

[0217] The terminal device applies configuration information when processing the third data packet based on the number of the third data packet. The number of the third data packet is determined based on the number of the second data packet and a first value, where the first value is the number of data packets.

[0218] The following is a specific example.

[0219] Case 1: The first information includes the first application moment.

[0220] The first application time can be understood as an absolute time, which can be denoted as T1. The terminal device can directly determine the first application time as the time of the application configuration information.

[0221] The first application time can be timed using methods such as Global Positioning System (GPS) or Coordinated Universal Time (UTC). Alternatively, it can be a Gregorian calendar date, such as the accumulated time since January 1, 1900, 00:00:00. The first application time can also be any other possible timekeeping method, without limitation. For example, the first application time could be July 1, 2024, 10:50:30:10 milliseconds (ms). The first application time can also be represented by one or more of the following: system frame, subframe, slot, or symbol, without limitation.

[0222] Scenario 2: The first piece of information includes the first timestamp.

[0223] The first timestamp can be the time when the network device (to the terminal device) sends the first message, which can be denoted as T2. This first timestamp can be similar in form to the representation of the first application moment mentioned above, and can be understood by reference without further explanation. For example, the first timestamp can be 9:50:30.10 milliseconds (ms) on July 1, 2024.

[0224] The first timestamp can be understood as a relative time. In case 2, the terminal device also needs to obtain the first duration (i.e., calculated by the terminal device itself), which can be denoted as t1. This first duration can be greater than or equal to the transmission delay between the terminal device and the network device. That is, the terminal device needs to determine the second time based on the first timestamp (i.e., the initial time) and the first duration. The terminal device can determine the second time as the time of the application configuration information, that is, T1 = T2 + t1.

[0225] It is understandable that if the configuration time required for the configuration information (or the time required for the terminal device to configure the configuration information, or the time for the configuration information to take effect) or the time required for the PDCP entity re-establishment process is short and can be ignored, then the terminal device can directly determine the transmission delay between the terminal device and the network device as the first duration. In other words, the time for the network device to send the first message plus the transmission delay between the terminal device and the network device is the time for the terminal device to apply the configuration information. If the configuration time required for the configuration information or the time required for the PDCP entity re-establishment process is long (e.g., greater than the preset duration, the specific value is not limited), then the terminal device can determine the first duration based on historical data, such as the average time (or greater than the average time) required for the configuration information or the PDCP entity re-establishment process, plus the transmission delay between the terminal device and the network device. In other words, the time for the network device to send the first message plus the first duration (i.e., greater than the transmission delay between the terminal device and the network device) is the time for the terminal device to apply the configuration information.

[0226] Scenario 3: The first information includes the first timestamp and the first duration.

[0227] In other words, the network device can directly send the first timestamp (T2) and the first duration (t1) to the terminal device together. It can be understood that if the configuration time required for the configuration information or the time required for the PDCP entity re-establishment process is short, it can be ignored. In this case, the network device can directly determine the transmission delay between the terminal device and the network device as the first duration. If the configuration time required for the configuration information or the time required for the PDCP entity re-establishment process is long (e.g., greater than the preset duration, the specific value is not limited), then the network device can determine the first duration based on historical data (e.g., data reported by the terminal device or obtained from queries with other devices or functional entities), such as the average time (or greater than the average time) required for the configuration information or the PDCP entity re-establishment process, plus the transmission delay between the terminal device and the network device.

[0228] In scenario 3, the terminal device does not need to calculate the first duration itself. It can directly determine the second time based on the first timestamp and the first duration, and set the second time as the time of the application configuration information, that is, T1 = T2 + t1. In this way, the terminal device can save computational overhead.

[0229] Case 4: The first information includes the number of the first data packet.

[0230] The number of the first data packet can also be understood as an absolute time. The terminal device can directly use the number of the first data packet to apply configuration information when processing the first data packet.

[0231] For example, the number of the first data packet can be a PDCP sequence number (SN), such as PDCP SDU SN or PDCP PDU SN; or it can be any other possible number, such as GPRS tunneling protocol-user plane (GTP-U) SN, etc., without limitation. For ease of understanding, the number of the first data packet can be recorded as PDCP SN#1.

[0232] Case 5: The first information includes the number of the second data packet and the first value.

[0233] The number of the second data packet can be understood as a relative time. This number can be represented in a similar way to the number of the first data packet, and will not be elaborated further. For ease of understanding, the number of the second data packet can be denoted as PDCP SN#2. The first value can be the number of data packets. That is, the terminal device needs to determine the number of the third data packet based on the number of the second data packet (i.e., the initial data packet) and the first value, and apply the configuration information when processing the third data packet. For example, the first value can be two, meaning the terminal device needs to process two more data packets based on the data packet corresponding to PDCP SN#2 to obtain the number of the third data packet, such as PDCP SN#3. The terminal device can apply this configuration information when processing the data packet corresponding to PDCP SN#3.

[0234] Based on situation 4 above, the number of the third data packet can be the same as or different from the number of the first data packet, without limitation.

[0235] It is understood that the above description is based on cases 1-5. There may also be coupling between cases 1-5. For example, the first information may include at least two items from cases 1-5. For instance, the first information may include the first application time and the number of the first data packet (case 1 and case 4). In this case, the terminal device may choose any parameter (such as the first application time or the number of the first data packet) and determine the time of the application configuration information based on the parameter. Alternatively, cases 1-5 may also have priorities. The terminal device may select the corresponding parameter according to the priority to determine the time of the application configuration information, etc. This application embodiment does not limit this.

[0236] Based on the above introduction, in one possible design scheme, the terminal device application configuration information may include:

[0237] The terminal device re-establishes the PDCP entity based on the configuration information.

[0238] The terminal device uses the re-established PDCP entity to process the first data to be transmitted and obtain the first data.

[0239] The terminal device sends the first data to the network device. Correspondingly, the network device receives the first data from the terminal device.

[0240] In other words, the first data can be obtained from the application configuration information at the time when the terminal device is configured.

[0241] The re-establishment of the PDCP entity by the terminal device based on the configuration information can be understood as the completion of the PDCP entity re-establishment by the terminal device at the time the configuration information is applied. For example, as shown in Figure 9, where the horizontal axis represents time, taking time T1 (i.e., the aforementioned first application time) as an example, after receiving the RRC reconfiguration message, the terminal device can perform the PDCP entity re-establishment according to the configuration information in the RRC reconfiguration message. The terminal device has completed the PDCP entity re-establishment at time T1 (i.e., the PDCP entity re-establishment is complete). At time T1, the terminal device can compress the uplink data using the data compression format #1 represented by the configuration information. For example, the terminal device can use the re-established PDCP entity to process the first data to be transmitted, and the format of this first data can be the aforementioned data compression format #1. The terminal device can then send the first data to the network device. It is understood that the specific implementation of the terminal device applying the compression-related configuration information can refer to existing implementations and is not limited thereto.

[0242] It should be understood that after the terminal device re-establishes the PDCP entity, for the signaling radio bearer (SRB), the terminal device can discard all stored PDCP SDUs and PDCP PDUs.

[0243] It is understood that the aforementioned first information may also include any other possible parameters or signaling, without limitation. The naming of the first application time, first timestamp, first duration, first data packet number, second data packet number, and first value is merely an example and may be replaced with any other possible naming, without limitation.

[0244] In summary, the network device can send a first message containing configuration information and first information to the terminal device. The first information can be used to indicate when the terminal device should apply the configuration information. Based on the first information, the terminal device can quickly determine the time to apply the configuration information and apply it at that time. That is, it can use the compression format corresponding to the configuration information to transmit with the network device. In this way, the data compression formats between the terminal device and the network device can be aligned, so as to avoid the transmission of business data and the user experience being affected by the misalignment of data compression formats between the network device and the terminal device.

[0245] In conjunction with the above embodiments, in one possible design scheme, the method may further include:

[0246] The terminal device sends instruction information to the network device. Correspondingly, the network device can receive instruction information from the terminal device.

[0247] The indication information can be used to indicate that the first data was obtained by the terminal device using application configuration information; alternatively, it can also be used to indicate that the compression configuration has been changed or a new compression configuration has been applied. This indication information can be denoted as indication information #b. Thus, the network device can explicitly determine that the first data was obtained by the terminal device using data compression format #1 based on this indication information #b, i.e., display the indication, enabling flexibility. Subsequently, the network device can directly use the decompression method corresponding to data compression format #1 to decompress the first data, thereby ensuring the normal transmission of service data (uplink data).

[0248] In one possible design scheme, the above method may further include:

[0249] When applying configuration information, the network device sends second data to the terminal device using a data compression format. Correspondingly, the terminal device receives the second data from the network device.

[0250] That is, the second data can be generated by the network device using a data compression format when applying configuration information. For example, when the terminal device applies configuration information, the network device can process the data to be transmitted, such as the second data to be transmitted, using data compression format #1 to obtain the second data (downlink data), and send the second data to the terminal device. Subsequently, the terminal device can directly decompress the second data using the decompression method corresponding to data compression format #1, thereby ensuring the normal transmission of service data (downlink data). It is understood that the network device can also trigger the sending of the second data to the terminal device after receiving the first data sent by the terminal device; this embodiment does not limit this.

[0251] For example, Figure 10 is a schematic flowchart of a communication method provided in an embodiment of this application. This method can be applied to communication between terminal devices and network devices in the above-described communication system.

[0252] Specifically, as shown in Figure 10, the communication method flow is as follows:

[0253] S1001, the network device sends configuration information to the terminal device. Correspondingly, the terminal device receives the configuration information from the network device.

[0254] The configuration information may include configurations related to data compression formats.

[0255] Network devices can send configuration information to terminal devices through RRC reconfiguration messages, radio bearer establishment request messages, radio bearer configuration messages, cell update messages, RRC connection establishment messages, etc. This application embodiment does not limit this.

[0256] It is understandable that the detailed description of the configuration information can be found in the relevant content of step S801 above, and will not be repeated here. For ease of understanding, the following description will take the example of the configuration information including the use of data compression format #1, which compresses both uplink and downlink data, and will not be repeated here.

[0257] It is understood that the naming of the above configuration information is only an example and can be replaced with any other possible names without limitation.

[0258] S1002, the terminal device sends the first information to the network device according to the configuration information. Correspondingly, the network device receives the first information from the terminal device.

[0259] The first piece of information can be used to indicate the time when the terminal device applies the configuration information. For a detailed description, please refer to the relevant content in step S801 above, which will not be repeated here.

[0260] In one possible design, the first information includes at least one of the following: a first application time, a first timestamp, a first timestamp and a first duration, a first data packet number, or a second data packet number and a first value.

[0261] Based on the aforementioned first information, in one possible design scheme, the above method embodiment may further include:

[0262] Based on the first information, the network device sends the second data to the terminal device using a data compression format. Correspondingly, the terminal device receives the second data from the network device.

[0263] In other words, the second data can be generated by the network device using a data compression format when the application configuration information is being used.

[0264] For example, when a network device sends second data to a terminal device using a data compression format based on first information, it may include at least one of the following:

[0265] In the first application moment, the network device sends the second data to the terminal device using a data compression format; or...

[0266] The network device acquires a first duration and, at a second time, sends second data to the terminal device using a modified data compression format, wherein the second time is determined based on the first timestamp and the first duration; or...

[0267] The network device sends second data to the terminal device at a second time using a data compression format, wherein the second time is determined based on the first timestamp and the first duration; or...

[0268] When the network device receives the data corresponding to the number of the first data packet, it sends the second data to the terminal device using a data compression format; or,

[0269] When a network device receives data corresponding to the number of a third data packet, it sends second data to the terminal device using a data compression format. The number of the third data packet is determined based on the number of the second data packet and a first value, where the first value is the number of data packets.

[0270] The following is a specific example.

[0271] Case 6: The first information includes the first application moment.

[0272] The first application time can be an absolute time, denoted as T3. That is, at the first application time, when the terminal device applies the configuration information, the network device can process the data to be transmitted, such as the second data to be transmitted, using data compression format #1, to obtain the second data (downlink data), and send the second data to the terminal device.

[0273] It is understandable that the representation of the first application moment is similar to that of the first application moment in Case 1 above, and can be understood by reference without further explanation.

[0274] Case 7: The first piece of information includes the first timestamp.

[0275] The first timestamp can be the time when the terminal device (to the network device) sends the first information, which can be denoted as T4. The representation of this first timestamp is similar to that of the first timestamp in case 2 above, and can be understood by reference, without further explanation.

[0276] The first timestamp can be understood as a relative time. In case 7, the network device also needs to obtain the first duration (i.e., calculated by the network device itself), which can be denoted as t2. This first duration is greater than or equal to the transmission delay between the terminal device and the network device. That is, the network device needs to determine the second time based on the first timestamp (i.e., the initial time) and the first duration. The network device can determine the second time as the time when the terminal device applies the configuration information, i.e., T3 = T4 + t2. At the second time, the network device can process the data to be transmitted, such as the second data to be transmitted, using data compression format #1 to obtain the second data (downlink data) and send the second data to the terminal device.

[0277] It is understandable that if the configuration time required for the configuration information (or the time required for the terminal device to configure the configuration information, or the time for the configuration information to take effect) or the time required for the PDCP entity re-establishment process is short and can be ignored, the network device can directly determine the transmission delay between the terminal device and the network device as the first duration. In other words, the time for the terminal device to send the first message plus the transmission delay between the terminal device and the network device is the time for the terminal device to apply the configuration information. If the configuration time required for the configuration information or the time required for the PDCP entity re-establishment process is long (e.g., greater than the preset duration, the specific value is not limited), the network device can determine the first duration based on historical data (e.g., data reported by the terminal device or obtained from queries with other devices), such as the average time (or greater than the average time) required for the configuration information or the PDCP entity re-establishment process, plus the transmission delay between the terminal device and the network device. In other words, the time for the network device to send the first message plus the first duration (i.e., greater than the transmission delay between the terminal device and the network device) is the time for the terminal device to apply the configuration information.

[0278] It is understandable that the representation of the first duration is similar to that of the first duration in case 2 above, and can be understood by reference without further explanation.

[0279] Case 8: The first information includes the first timestamp and the first duration.

[0280] In other words, the terminal device can directly send the first timestamp (T3) and the first duration (t2) to the network device together. It can be understood that if the configuration time required for the configuration information or the time required for the PDCP entity re-establishment process is short, it can be ignored. In this case, the terminal device can directly determine the transmission delay between the terminal device and the network device as the first duration. If the configuration time required for the configuration information or the time required for the PDCP entity re-establishment process is long (e.g., greater than the preset duration, the specific value is not limited), then the terminal device can determine the first duration based on historical data, such as the average time (or greater than the average time) required for the configuration information or the PDCP entity re-establishment process, plus the transmission delay between the terminal device and the network device.

[0281] In scenario 8, the network device does not need to calculate the first duration itself. It can directly determine the second duration based on the first timestamp and the first duration, and set the second duration as the time when the terminal device applies the configuration information. That is, T3 = T3 + t2. This saves the network device's computational overhead. The network device can process the data to be transmitted, such as the second data to be transmitted, using data compression format #1 at the second duration to obtain the second data (downlink data), and then send the second data to the terminal device.

[0282] This can save on the computing costs of network equipment.

[0283] Case 9: The first information includes the number of the first data packet.

[0284] The number of the first data packet can be understood as an absolute time. The network device can directly determine the time when it received the data corresponding to the number of the first data packet based on the number of the first data packet, and consider it to be the time when the terminal device applied the configuration information. In other words, the data corresponding to the number of the first data packet can be obtained by the terminal device applying the configuration information, i.e., by processing the first data packet using data compression format #1.

[0285] For example, a network device can determine the packet number corresponding to the received data in the following way: For instance, after the PDCP entity compresses the packet, it can include the packet number (such as a PDCPC SN) in the packet header. The network device can then parse the received data to obtain the packet number carried in the header, thus determining the packet number corresponding to the received data. The network device can also determine the packet number corresponding to the received data through any other possible implementation, without limitation.

[0286] For ease of understanding, the number of the first data packet can be recorded as PDCP SN#4.

[0287] Subsequently, the network device can use data compression format #1 to process the data to be transmitted, such as the second data to be transmitted, to obtain the second data (downlink data), and send the second data to the terminal device. At the same time, the network device can also use the decompression method corresponding to data compression format #1 to decompress the data (uplink data) corresponding to the number of the received first data packet, thereby ensuring the normal transmission of service data (uplink data and downlink data).

[0288] It is understandable that the representation of the number of the first data packet is similar to that of the number of the first data packet in case 4 above. This can be used as a reference for understanding, and will not be elaborated further.

[0289] Case 10: The first information includes the number of the second data packet and the first value.

[0290] The number of the second data packet can be understood as a relative time. This number can be represented similarly to the number of the first data packet in case 9 above, and will not be elaborated further. For ease of understanding, the number of the second data packet can be denoted as PDCP SN#5. The first value can be the number of data packets. That is, the network device needs to determine the number of the third data packet based on the number of the second data packet (i.e., the initial data packet) and the first value, which can be denoted as PDCP SN#6. The network device can directly determine the time when it received the data corresponding to the number of the third data packet based on the number of the third data packet, considering it as the time when the terminal device applied the configuration information. In other words, the data corresponding to the number of the third data packet can be obtained by the terminal device applying the configuration information, i.e., processing the third data packet using data compression format #1.

[0291] Subsequently, the network device can use data compression format #1 to process the data to be transmitted, such as the second data to be transmitted, to obtain the second data (downlink data), and send the second data to the terminal device. At the same time, the network device can also use the decompression method corresponding to data compression format #1 to decompress the data (uplink data) corresponding to the number of the received third data packet, thereby ensuring the normal transmission of service data (uplink data and downlink data).

[0292] It is understandable that the representation of the first value is similar to that of the first data in case 5 above, and can be used for reference without further explanation.

[0293] Based on scenario 4 above, the number of the third data packet can be the same as or different from the number of the first data packet; there is no limitation. Based on scenarios 6-10 above, the terminal device can directly use the decompression method corresponding to data compression format #1 to decompress the second data, thereby ensuring the normal transmission of business data (downlink data).

[0294] It is understandable that the above description is based on cases 6-10. There may also be coupling between cases 6-10. The implementation principle can be found in the relevant content of step S803 above, and will not be repeated here.

[0295] It is understood that the aforementioned first information can be carried in RRC reconfiguration completion message, radio bearer establishment response message, radio bearer configuration completion message, cell update completion message, RRC connection establishment completion message, etc., that is, carried in existing messages to reduce implementation difficulty, or it can be carried in new messages to improve implementation flexibility, without limitation.

[0296] It is understood that the aforementioned first information may also include any other possible parameters or signaling, without limitation. The naming of the first application time, first timestamp, first duration, first data packet number, second data packet number, and first value is merely an example and may be replaced with any other possible naming, without limitation.

[0297] In summary, when a terminal device receives configuration information, including data compression format settings, from a network device, the terminal device can send the time it applied the configuration information to the network device via the first information. The network device can then quickly determine the time when the terminal device applied the configuration information based on the first information. This ensures alignment of data compression formats between the terminal device and the network device, preventing data transmission and user experience from being affected by misalignment in data compression formats between the two devices.

[0298] In conjunction with the above embodiments, in one possible design scheme, the method may further include:

[0299] The terminal device uses the application configuration information at the time of application configuration.

[0300] For example, the terminal device application configuration information may include:

[0301] The terminal device re-establishes the Packet Data Convergence Protocol (PDCP) entity based on the configuration information.

[0302] The terminal device uses the re-established PDCP entity to process the first data to be transmitted and obtain the first data.

[0303] The terminal device sends the first data to the network device. Correspondingly, the network device receives the first data from the terminal device.

[0304] In other words, the first data can be obtained from the application configuration information at the time when the terminal device is configured.

[0305] After the terminal device re-establishes the PDCP entity, for the signaling radio bearer (SRB), the terminal device can discard all stored PDCP SDUs and PDCP PDUs. The specific implementation of this process can be understood by referring to the relevant content in the method shown in Figure 8 above, and will not be elaborated further.

[0306] In one possible design scheme, the above method may further include:

[0307] The terminal device sends instruction information to the network device. Correspondingly, the network device can receive instruction information from the terminal device.

[0308] The indication information can be used to indicate that the first data was obtained by the terminal device using application configuration information; alternatively, it can also be used to indicate that the compression configuration has been changed or a new compression configuration has been applied. This indication information can be denoted as indication information #c. Thus, the network device can explicitly determine that the first data was obtained by the terminal device using data compression format #1 based on this indication information #c, i.e., display the indication, enabling flexibility. Subsequently, the network device can directly use the decompression method corresponding to data compression format #1 to decompress the first data, thereby ensuring the normal transmission of service data (uplink data).

[0309] It is understandable that, based on the methods shown in Figures 8 and 10 above, the network device can send instruction information to the terminal device to indicate the time when the terminal device applies the configuration information (related to the data compression format), or, after receiving the configuration information (related to the data compression format) sent by the network device, the terminal device can report the time when it applied the configuration information to the network device. In this way, the data compression format alignment between the terminal device and the network device can be achieved. This implementation principle can also be applied to the alignment between the terminal device and the network device (or between other devices) based on the effective time of other information or other messages, such as the aforementioned RRC reconfiguration message, etc., which will not be elaborated further.

[0310] To address issue B above, Figure 11 is an exemplary flowchart of a communication method provided in an embodiment of this application. This method can be applied to communication between terminal devices and network devices in the aforementioned communication system.

[0311] Specifically, as shown in Figure 11, the communication method flow is as follows:

[0312] S1101, the network device sends configuration information to the terminal device. Correspondingly, the terminal device receives the configuration information from the network device.

[0313] The configuration information may include compressed configuration information and Radio Link Control (RLC) configuration information.

[0314] The compression configuration information may include configurations related to the data compression format. This compression configuration information may include a PDCP re-establishment request message to request the re-establishment of the PDCP entity. This compression configuration information may also include any other possible parameters or signaling, without limitation. It can be understood that this compression configuration information can be included in the PDCP configuration information (carried within the configuration information), that is, carried in an existing message to reduce implementation difficulty, or it can be carried in a new message to improve implementation flexibility, without limitation. The compression configuration information is similar to the configuration information in step S801 above, and can be understood by reference, without further elaboration. For ease of understanding, the following description uses the example of compression configuration information including the use of data compression format #1, performing compression on both uplink and downlink data, for subsequent explanations, without further elaboration.

[0315] RLC configuration information can include configurations related to changes to RLC bearers, specifically configuration information related to the release, addition, or modification of RLC bearers. For example, RLC configuration information can include an RLC bearer release list (rlc-BearerToReleaseList) and an RLC bearer addition list (rlc-BearerToAddModList). The RLC bearer release list can contain a group of RLC bearers that the RRC layer intends to release; the RLC bearer addition list can contain RLC bearers that the RRC layer wishes to add or modify, and can include new bearer configuration information, such as bearer ID, QoS, acknowledged mode (AM), unacknowledged mode (UM), etc., or requests to change existing bearers. This RLC configuration information can also include any other possible parameters or signaling, without limitation.

[0316] It is understandable that network devices require terminal devices to change the data compression format they are currently using. For example, changing from data compression format #2 (if the previous compression configuration needs to be changed) to data compression format #1 may lead to adjustments in the data traffic processing strategy of the PDCP layer, thereby affecting the use of logical channels and the re-establishment of PDCP entities. Therefore, network devices can send compression configuration information and corresponding RLC configuration information to the terminal devices together.

[0317] It is understandable that this configuration information can be carried in RRC reconfiguration messages, radio bearer establishment request messages, radio bearer configuration messages, cell update messages, RRC connection establishment messages, etc., that is, carried in existing messages to reduce implementation difficulty, or it can be carried in new messages to improve implementation flexibility, without limitation.

[0318] It is understood that the naming of the above configuration information, RLC configuration information, and compression configuration information is only an example and can be replaced with any other possible names without limitation.

[0319] S1102, the terminal device processes the first data to be transmitted according to the compression configuration information to obtain the first data.

[0320] The following example illustrates the implementation process in detail.

[0321] Case a: The terminal device performs compression at the PDCP layer.

[0322] In scenario a, the PDCP layer of the terminal device re-establishes the PDCP entity based on the compressed configuration information and uses the re-established PDCP entity to process the first data to be transmitted, obtaining the first data. For example, taking the configuration information carried in an RRC reconfiguration message as shown in Figure 12, the network device can send an RRC reconfiguration message to the RRC layer of the terminal device. The RRC layer can then send the compressed configuration information (including a PDCP re-establishment request message) to the PDCP layer based on this RRC reconfiguration message. The PDCP layer of the terminal device can then re-establish the PDCP entity based on the compressed configuration information and use the re-established PDCP entity to process the first data to be transmitted, obtaining the first data (in the aforementioned data compression format #1). That is, the re-established PDCP entity can use data compression format #1 to transmit subsequently collected data to the network device.

[0323] It is understood that the PDCP layer of the terminal device can also receive PDCP re-establishment request messages sent by other upper layers, such as the NAS layer, and perform PDCP entity re-establishment according to the PDCP re-establishment request message. This application embodiment does not limit this.

[0324] It is understandable that the specific implementation of the terminal device in re-establishing the PDCP entity based on the compression configuration information, and in using the re-established PDCP entity to process the first data to be transmitted, can refer to existing implementations and is not limited.

[0325] Case b: The terminal device performs compression at the RRC layer.

[0326] In scenario b, the RRC layer of the terminal device can process the first data to be transmitted based on the compression configuration information to obtain the first data. For example, taking the configuration information carried in an RRC reconfiguration message as shown in Figure 13, the network device can send an RRC reconfiguration message to the RRC layer of the terminal device. The RRC layer can then perform a change in the data compression format based on the compression configuration information in the RRC reconfiguration message, and transmit subsequently collected data to the network device using data compression format #1.

[0327] Based on scenario b, in one possible design scheme, the above method may also include:

[0328] The RRC layer of the terminal device sends a PDCP re-establishment request message to the PDCP layer of the terminal device based on the compressed configuration information. Correspondingly, the PDCP layer of the terminal device receives the PDCP re-establishment request message from the RRC layer of the terminal device.

[0329] The PDCP layer of the terminal device re-establishes the PDCP entity based on the PDCP re-establishment request message.

[0330] The PDCP Re-establishment Request message can be used to request the re-establishment of a PDCP entity.

[0331] Based on the above description, the compression configuration information may include a PDCP re-establishment request message, as shown in Figure 13. The RRC layer can send the PDCP re-establishment request message from the compression configuration information to the PDCP layer, so that the PDCP layer can re-establish the PDCP entity according to the PDCP re-establishment request message. Subsequently, the re-established PDCP entity can be used to transmit data with data compression format #1 (such as the first data mentioned above).

[0332] It is understandable that the specific implementation of the PDCP entity re-establishment performed by the terminal device based on the compressed configuration information can refer to existing implementations and is not limited thereto. It should be understood that after the terminal device re-establishes the PDCP entity, for the signaling radio bearer (SRB), the terminal device can discard all stored PDCP SDUs and PDCP PDUs.

[0333] S1103, the terminal device releases the first logical channel and adds the second logical channel according to the RLC configuration information.

[0334] The first logical channel can be the logical channel used by the terminal device before applying compressed configuration information, and the second logical channel can be the logical channel used by the terminal device after applying compressed configuration information. It can be understood that, based on the above situations a and b, as shown in Figures 12 and 13, the specific implementation of the terminal device's modification of the lower-level logical channels (including but not limited to control channels (for control message transmission) and data channels (for user plane data transmission) according to the RLC configuration information) can refer to existing implementations and is not limited thereto.

[0335] Releasing the first logical channel by the terminal device may include: clearing the data cached in the first logical channel by the terminal device to save overhead.

[0336] It is understood that the naming of the first and second logical channels mentioned above is only an example, and the first and second logical channels can be replaced with any other possible names without limitation.

[0337] S1104, the terminal device sends first data to the network device through the second logical channel. Correspondingly, the network device receives the first data from the terminal device.

[0338] In other words, the terminal device transmits data to the network device through the newly added second logical channel, that is, it sends the first data in a new data compression format, such as data compression format #1. At the same time, the terminal device can also use this second logical channel to receive the second data (in data compression format #1) from the network device, which will not be elaborated further.

[0339] In summary, network devices can send configuration information containing compression configuration information and RLC configuration information to terminal devices. Terminal devices can then perform logical channel changes based on this RLC configuration information. For example, they can release the first logical channel used before applying the compression configuration information and add a new second logical channel. The terminal device can use this second logical channel to send the first data obtained by processing the first data to be transmitted according to the data compression format indicated by the compression configuration information. In other words, the terminal device can carry the first data obtained by applying this configuration information through the new second logical channel. This allows data obtained before applying the compression configuration information and data obtained after applying the compression configuration information (the two data formats are different, i.e., a change has occurred) to be carried on different logical channels. The terminal device can directly release the first logical channel to avoid MAC layer reset due to PDCP entity re-establishment, which would clear other service data and reduce the impact on cached data on other radio bearers.

[0340] The communication methods shown in Figures 8, 10, and 11 above illustrate the solution provided by the embodiment using a network device as an example. In the O-RAN architecture network device shown in Figure 7 above, the interaction between the network device and the terminal device can also be converted into processing actions between the O-DU, O-RU, and the terminal device:

[0341] For example, Figure 14 is a flowchart illustrating a communication method applied to an O-RAN architecture according to an embodiment of this application (corresponding to the communication method shown in Figure 8 above). As shown in Figure 14, the network device includes an O-DU and an O-RU, and the communication method includes:

[0342] S1401, O-DU receives the first message.

[0343] The first message may include configuration information and first information.

[0344] S1402, the O-DU sends the first message to the O-RU. Correspondingly, the O-RU receives the first message from the O-DU.

[0345] S1403, the O-RU sends the first message to the terminal device. Correspondingly, the terminal device receives the first message from the O-RU.

[0346] S1404, The terminal device applies configuration information based on the first information.

[0347] It is understood that the specific implementation of steps S1401-S1404 can be referred to the relevant content in steps S801-S803 above, and will not be repeated here.

[0348] Furthermore, when the terminal device sends the first data to the network device, the terminal device can send the first data to the O-RU, and the O-RU can send the received first data to the O-DU; similarly, when the network device sends the second data to the terminal device, the O-DU can send the second data to the O-RU, and the O-RU can send the received second data to the terminal device.

[0349] Steps S1401-S1404 described above are specific implementations of the communication method shown in Figure 8 under the O-RAN architecture. The implementations of the communication methods shown in Figures 10 and 11 under the O-RAN architecture are similar. For example, step S1001 may specifically include: the O-DU sending configuration information to the O-RU, and the O-RU sending the received configuration information to the terminal device; step S1002 may specifically include: the terminal device sending first information to the O-RU, and the O-RU sending the received first information to the O-DU; step S1101 may specifically include: the O-DU sending configuration information to the O-RU, and the O-RU sending the received configuration information to the terminal device; step S1104 may specifically include: the terminal device sending first data to the O-RU, and the O-RU sending the received first data to the O-DU.

[0350] It is understandable that the communication methods shown in Figures 8, 10 and 11 above are not only applicable to the compression of collected AI data, but also to the compression of other data transmission processes. Their implementation principles are similar and can be understood by reference, so they will not be elaborated further.

[0351] The communication method provided by the embodiments of this application has been described in detail above with reference to Figures 8-14. The communication apparatus used to perform the communication method provided by the embodiments of this application is described in detail below with reference to Figures 15-16.

[0352] Figure 15 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. As exemplarily shown in Figure 15, the communication device 1500 includes a transceiver module 1501 and a processing module 1502. For ease of explanation, Figure 15 only shows the main components of the communication device 1500.

[0353] The transceiver module 1501 is used to perform the transceiver function of the method shown in Figures 8 and 10-14, and the processing module 1502 is used to perform other functions of the method shown in Figures 8 and 10-14 besides the transceiver function.

[0354] Optionally, the transceiver module 1501 may include a transmitting module (not shown in FIG. 15) and a receiving module (not shown in FIG. 15). The transmitting module is used to implement the transmitting function of the communication device 1500, and the receiving module is used to implement the receiving function of the communication device 1500.

[0355] Optionally, the communication device 1500 may further include a storage module (not shown in FIG. 15) that stores programs or instructions. When the processing module 1502 executes the program or instructions, the communication device 1500 can perform the functions of the terminal device and / or network device in the methods shown in FIG. 8 and FIG. 10-14.

[0356] It is understood that the communication device 1500 may be a terminal device, or a chip (system) or other component or assembly that can be disposed in a terminal device, or a device that includes a terminal device; or, the communication device 1500 may be a network device, or a chip (system) or other component or assembly that can be disposed in a network device, or a device that includes a network device. The embodiments of this application do not limit this.

[0357] Furthermore, the technical effects of the communication device 1500 can be seen in Figure 8 and the technical effects of the communication methods shown in Figures 10-14, which will not be repeated here.

[0358] For example, Figure 16 is a second schematic diagram of the structure of a communication device provided in an embodiment of this application. This communication device can be a terminal device or a network device, or it can be a chip (system) or other component or assembly of a terminal device or network device. As shown in Figure 16, the communication device 1600 may include a processor 1601. Optionally, the communication device 1600 may also include a memory 1602 and / or a transceiver 1603. The processor 1601 is coupled to the memory 1602 and the transceiver 1603, for example, they can be connected via a communication bus.

[0359] The following section, with reference to Figure 16, provides a detailed description of each component of the communication device 1600:

[0360] The processor 1601 is the control center of the communication device 1600. It can be a single processor or a collective term for multiple processing elements. For example, the processor 1601 can be one or more central processing units (CPUs), application-specific integrated circuits (ASICs), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0361] Optionally, the processor 1601 can perform various functions of the communication device 1600 by running or executing software programs stored in the memory 1602 and calling data stored in the memory 1602, such as performing the communication methods shown in FIG8 and FIG10-FIG14.

[0362] In a specific implementation, as one example, processor 1601 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG16.

[0363] In a specific implementation, as one embodiment, the communication device 1600 may also include multiple processors, such as processors 1601 and 1604 shown in FIG. 16. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). Here, a processor may refer to one or more devices, circuits, and / or processing cores used for processing data (e.g., computer program instructions).

[0364] The memory 1602 is used to store the software program that executes the solution of this application, and is controlled by the processor 1601 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.

[0365] Optionally, the memory 1602 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. The memory 1602 may be integrated with the processor 1601 or may exist independently and be coupled to the processor 1601 through the interface circuit of the communication device 1600 (not shown in FIG. 16). This embodiment of the application does not specifically limit this.

[0366] Transceiver 1603 is used for communication with other communication devices. For example, if communication device 1600 is a terminal device, transceiver 1603 can be used to communicate with a network device or with another terminal device. As another example, if communication device 1600 is a network device, transceiver 1603 can be used to communicate with a terminal device or with another network device.

[0367] Optionally, transceiver 1603 may include a receiver and a transmitter (not shown separately in Figure 16). The receiver is used to implement the receiving function, and the transmitter is used to implement the transmitting function.

[0368] Optionally, the transceiver 1603 can be integrated with the processor 1601 or exist independently and be coupled to the processor 1601 through the interface circuit of the communication device 1600 (not shown in FIG16). This application embodiment does not specifically limit this.

[0369] It should be noted that the structure of the communication device 1600 shown in Figure 16 does not constitute a limitation on the communication device. The actual communication device may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0370] Furthermore, the technical effects of the communication device 1600 can be referred to the technical effects of the communication method described in the above method embodiments, and will not be repeated here.

[0371] This application provides a communication system. The communication system may include the terminal device described in the above method embodiments, and network devices (such as access network devices, access and mobility management network elements, and tag management network elements).

[0372] It should be understood that the processor in the embodiments of this application can be a central processing unit (CPU), or it can be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0373] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0374] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or 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., 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 includes one or more sets of 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. A semiconductor medium can be a solid-state drive.

[0375] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0376] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

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

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

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

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

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

[0382] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

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

[0384] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: Receive a first message from a network device, wherein the first message includes configuration information and first information, the configuration information including relevant configuration of data compression format, and the first information is used to indicate the time when the configuration information is applied; Based on the first information, the configuration information is applied.

2. The method according to claim 1, characterized in that, The first information includes at least one of the following: a first application time, a first timestamp, the first timestamp and a first duration, the number of the first data packet, or the number of the second data packet and a first value.

3. The method according to claim 2, characterized in that, The step of applying the configuration information based on the first information includes at least one of the following: At the first application moment, the configuration information is applied; or... Obtain a first duration and apply the configuration information at a second time, wherein the second time is determined based on the first timestamp and the first duration; or... In a second time period, the configuration information is applied, wherein the second time period is determined based on the first timestamp and the first duration; or... Based on the number of the first data packet, the configuration information is applied when processing the first data packet; or, When processing the third data packet, the configuration information is applied based on the number of the third data packet, wherein the number of the third data packet is determined based on the number of the second data packet and the first value, where the first value is the number of data packets.

4. The method according to claim 2 or 3, characterized in that, The first timestamp is the time when the first message was sent, and the first duration is greater than or equal to the transmission delay between the terminal device and the network device.

5. The method according to any one of claims 1-4, characterized in that, The application of the configuration information includes: The Packet Data Convergence Protocol (PDCP) entity is re-established based on the configuration information. The re-established PDCP entity is used to process the first data to be transmitted to obtain the first data; The first data is sent to the network device.

6. The method according to claim 5, characterized in that, The method further includes: Send indication information to the network device, wherein the indication information is used to indicate that the first data was obtained by applying the configuration information.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Receive second data from the network device, wherein the second data is generated by the network device using the data compression format at the time the configuration information is applied.

8. A communication method, characterized in that, include: Generate a first message, wherein the first message includes configuration information and first information, the configuration information including relevant configurations for data compression format, and the first information is used to indicate the time when the configuration information is applied; Send the first message to the terminal device.

9. The method according to claim 8, characterized in that, The first information includes at least one of the following: a first application time, a first timestamp, the first timestamp and a first duration, the number of the first data packet, or the number of the second data packet and a first value.

10. The method according to claim 8 or 9, characterized in that, The method further includes: Receive first data from the terminal device, wherein the first data is obtained by applying the configuration information at the time when the configuration information is applied.

11. The method according to claim 10, characterized in that, The method further includes: The device receives an indication message from the terminal device, wherein the indication message is used to indicate that the first data was obtained by applying the configuration information.

12. The method according to any one of claims 8-11, characterized in that, The method further includes: When the configuration information is applied, second data is sent to the terminal device using the data compression format.

13. A communication method, characterized in that, include: Receive configuration information from network devices; wherein, the configuration information includes configuration related to data compression format; According to the configuration information, a first message is sent to the network device, wherein the first message is used to indicate the time when the terminal device applies the configuration information.

14. The method according to claim 13, characterized in that, The first information includes at least one of the following: a first application time, a first timestamp, the first timestamp and a first duration, the number of the first data packet, or the number of the second data packet and a first value.

15. The method according to claim 13 or 14, characterized in that, The method further includes: Receive second data from the network device, wherein the second data is generated by the network device using the data compression format at the time the configuration information is applied.

16. The method according to any one of claims 13-15, characterized in that, The method further includes: The configuration information is applied at the time when the configuration information is applied.

17. The method according to claim 16, characterized in that, The application of the configuration information includes: The Packet Data Convergence Protocol (PDCP) entity is re-established based on the configuration information. The re-established PDCP entity is used to process the first data to be transmitted to obtain the first data; The first data is sent to the network device.

18. The method according to claim 17, characterized in that, The method further includes: Send indication information to the network device, wherein the indication information is used to indicate that the first data was obtained by applying the configuration information.

19. A communication method, characterized in that, include: Send configuration information to the terminal device, wherein the configuration information includes configuration related to the data compression format; Receive first information from the terminal device, wherein the first information is used to indicate the time for applying the configuration information.

20. The method according to claim 19, characterized in that, The first information includes at least one of the following: a first application time, a first timestamp, the first timestamp and a first duration, the number of the first data packet, or the number of the second data packet and a first value.

21. The method according to claim 20, characterized in that, The method further includes: Based on the first information, the second data is sent to the terminal device using the data compression format.

22. The method according to claim 21, characterized in that, The step of sending second data to the terminal device using the data compression format based on the first information includes at least one of the following: At the first application moment, the second data is sent to the terminal device using the data compression format; or... Obtain a first duration, and at a second time, send the second data to the terminal device using the modified data compression format, wherein the second time is determined based on the first timestamp and the first duration; or... At a second time, the second data is sent to the terminal device using the data compression format, wherein the second time is determined based on the first timestamp and the first duration; or... Upon receiving the data corresponding to the number of the first data packet, the second data is sent to the terminal device using the data compression format; or, Upon receiving data corresponding to the number of the third data packet, the second data is sent to the terminal device using the data compression format, wherein the number of the third data packet is determined based on the number of the second data packet and the first value, where the first value is the number of data packets.

23. The method according to any one of claims 20-22, characterized in that, The first timestamp is the time when the first information was sent, and the first duration is greater than or equal to the transmission delay between the terminal device and the network device.

24. The method according to any one of claims 19-23, characterized in that, The method further includes: Receive first data from the terminal device, wherein the first data is obtained by applying the configuration information at the time when the configuration information is applied.

25. The method according to claim 24, characterized in that, The method further includes: The device receives an indication message from the terminal device, wherein the indication message is used to indicate that the first data was obtained by applying the configuration information.

26. A communication device, characterized in that, The apparatus includes a module for performing the method as described in any one of claims 1-25.

27. A communication device, characterized in that, include: A processor for executing a computer program to cause the communication device to perform the method as described in any one of claims 1-25.

28. A communication chip, characterized in that, It stores a computer program or instructions that, when the chip is run on a communication device, cause the method as described in any one of claims 1-25 to be implemented.

29. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, cause the computer to perform the communication method as described in any one of claims 1-25.

30. A computer program product, characterized in that, The computer program product includes: a computer program or instructions that, when executed on a computer, cause the computer to perform the communication method as described in any one of claims 1-25.

Images