A data compression method and apparatus

Abstract

The embodiment of the present disclosure discloses a data compression method and device, the method comprises: a terminal device receives small data packet transmission SDT configuration information of a network side device; wherein the SDT configuration information instructs the terminal device to perform small data packet transmission SDT; determine a target data compression area; in response to the terminal device being in the target data compression area, perform data compression when performing small data packet transmission SDT. In this way, the terminal device can perform data compression in the target data compression area when performing small data transmission SDT, thereby improving the performance of data transmission.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a data compression method and apparatus. Background Technology

[0002] Among the related technologies, it is proposed to support small data transmission (SDT) in the inactive state. SDT supports SDT based on random access procedures and SDT based on semi-static configuration.

[0003] The packet header compression function in 5G systems includes ROHC (Robust Header Compression) and EHC (Ethernet Header Compression). When a terminal device is switching or changing from a connected state to an inactive state, in order to ensure that the terminal device can continue to compress packets, the network-side device can be configured to instruct the terminal device to retain the current compression context. Summary of the Invention

[0004] This disclosure provides a data compression method and apparatus to enable terminal devices to perform data compression within the target data compression area when performing Small Data Transmission Technology (SDT), thereby improving data transmission performance.

[0005] In a first aspect, embodiments of this disclosure provide a data compression method applied to a terminal device. The method includes: receiving Small Data Packet Transmission (SDT) configuration information from a network-side device; wherein the SDT configuration information instructs the terminal device to perform Small Data Packet Transmission (SDT); determining a target data compression area; and performing data compression when the terminal device is in the target data compression area and performing Small Data Packet Transmission (SDT).

[0006] By implementing the embodiments of this disclosure, a terminal device can receive Small Data Packet Transmission (SDT) configuration information from a network-side device; wherein, the SDT configuration information instructs the terminal device to perform Small Data Packet Transmission (SDT); determines a target data compression area; and, in response to the terminal device being in the target data compression area, performs data compression during Small Data Packet Transmission (SDT). In this way, the terminal device can perform data compression within the target data compression area when performing Small Data Transmission (SDT), thereby improving data transmission performance.

[0007] Secondly, embodiments of this disclosure provide another data compression method, which is applied to a network-side device. The method includes: sending SDT configuration information to a terminal device to instruct the terminal device to perform Small Data Packet Transmission (SDT); sending data compression configuration to the terminal device; wherein the data compression configuration includes data compression area configuration.

[0008] Thirdly, embodiments of this disclosure provide a communication device that implements some or all of the functions of the terminal device described in the first aspect above. For example, the communication device may have the functions of some or all of the embodiments in this disclosure, or it may have the functions of any one embodiment in this disclosure implemented individually. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0009] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions described in the above method. The transceiver module supports communication between the communication device and other devices. The communication device may also include a storage module, coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.

[0010] In one implementation, the communication device includes: a transceiver module for receiving Small Data Packet Transmission (SDT) configuration information from a network-side device; wherein the SDT configuration information instructs a terminal device to perform Small Data Packet Transmission (SDT); and a processing module for determining a target data compression region; and performing data compression when the terminal device is in the target data compression region and performing Small Data Packet Transmission (SDT).

[0011] As an example, the processing module can be a processor, the transceiver module can be a transceiver or a communication interface, and the storage module can be a memory.

[0012] Fourthly, embodiments of this disclosure provide another communication device that has some or all of the functions of the network-side device in the method example described in the second aspect above. For example, the communication device may have the functions of some or all of the embodiments in this disclosure, or it may have the functions of any one embodiment in this disclosure implemented individually. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0013] In one implementation, the communication device may include a transceiver module for supporting communication between the communication device and other devices. The communication device may also include a storage module coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.

[0014] In one implementation, the communication device includes: a transceiver module, configured to send SDT configuration information to a terminal device, instructing the terminal device to perform Small Data Packet Transmission (SDT); and to send data compression configuration to the terminal device; wherein the data compression configuration includes a data compression region configuration.

[0015] Fifthly, embodiments of this disclosure provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the first aspect.

[0016] In a sixth aspect, embodiments of this disclosure provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the second aspect above.

[0017] In a seventh aspect, embodiments of this disclosure provide a communication device including a processor and a memory, the memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the first aspect above.

[0018] Eighthly, embodiments of this disclosure provide a communication device including a processor and a memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the second aspect above.

[0019] Ninthly, embodiments of this disclosure provide a communication device including a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, which is configured to execute the code instructions to cause the device to perform the method described in the first aspect above.

[0020] In a tenth aspect, embodiments of this disclosure provide a communication device including a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, which is configured to execute the code instructions to cause the device to perform the method described in the second aspect above.

[0021] Eleventhly, embodiments of this disclosure provide a data compression system, which includes the communication device described in the third aspect and the communication device described in the fourth aspect, or the system includes the communication device described in the fifth aspect and the communication device described in the sixth aspect, or the system includes the communication device described in the seventh aspect and the communication device described in the eighth aspect, or the system includes the communication device described in the ninth aspect and the communication device described in the tenth aspect.

[0022] In a twelfth aspect, embodiments of the present invention provide a computer-readable storage medium for storing instructions for use by the aforementioned terminal device, which, when executed, cause the terminal device to perform the method described in the first aspect.

[0023] In a thirteenth aspect, embodiments of the present invention provide a readable storage medium for storing instructions for use by the network-side device, which, when executed, cause the network device to perform the method described in the second aspect.

[0024] In a fourteenth aspect, this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0025] In a fifteenth aspect, this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect above.

[0026] In a sixteenth aspect, this disclosure provides a chip system including at least one processor and an interface for supporting a terminal device in implementing the functions involved in the first aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the terminal device. The chip system may be composed of chips or may include chips and other discrete devices.

[0027] In a seventeenth aspect, this disclosure provides a chip system including at least one processor and an interface for supporting network-side devices in implementing the functions involved in the second aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the network device. The chip system may be composed of chips or may include chips and other discrete devices.

[0028] In an eighteenth aspect, this disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0029] In a nineteenth aspect, this disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect above. Attached Figure Description

[0030] To more clearly illustrate the technical solutions in the embodiments or background art of this disclosure, the accompanying drawings used in the embodiments or background art of this disclosure will be described below.

[0031] Figure 1 This is an architecture diagram of a communication system provided in an embodiment of this disclosure;

[0032] Figure 2 This is a flowchart of a data compression method provided in an embodiment of this disclosure;

[0033] Figure 3 This is a flowchart of another data compression method provided in this disclosure embodiment;

[0034] Figure 4 This is a flowchart of yet another data compression method provided in this disclosure embodiment;

[0035] Figure 5 This is a flowchart of yet another data compression method provided in this disclosure embodiment;

[0036] Figure 6 This is a flowchart of yet another data compression method provided in this disclosure embodiment;

[0037] Figure 7 This is a structural diagram of a communication device provided in an embodiment of this disclosure;

[0038] Figure 8 This is a structural diagram of another communication device provided in an embodiment of this disclosure;

[0039] Figure 9 This is a schematic diagram of the structure of a chip provided in an embodiment of this disclosure. Detailed Implementation

[0040] To better understand the data compression method and apparatus disclosed in this disclosure, the communication system to which this disclosure applies will be described first.

[0041] Please see Figure 1 , Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of the present disclosure. The communication system may include, but is not limited to, a network-side device and a terminal device. Figure 1 The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of this disclosure. In actual applications, there may be two or more network-side devices and two or more terminal devices. Figure 1 The communication system shown is exemplified by a network-side device 101 and a terminal device 102.

[0042] It should be noted that the technical solutions of this disclosure can be applied to various communication systems. For example, Long Term Evolution (LTE) systems, 5th Generation (5G) mobile communication systems, 5G New Radio (NR) systems, or other future new mobile communication systems. It should also be noted that the side link in this disclosure can also be referred to as a side link or a direct link.

[0043] The network-side device 101 in this embodiment is a network-side entity used for transmitting or receiving signals. For example, the network-side device 101 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in an NR system, a network-side device in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. This disclosure does not limit the specific technology or device form used in the network-side device. The network-side device provided in this disclosure can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure, the network-side device, for example, can have its protocol layer separated. Some protocol layer functions are centrally controlled by the CU, while the remaining or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0044] The terminal device 102 in this disclosure is a user-side entity used to receive or transmit signals, such as a mobile phone. The terminal device can also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device can be a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, etc. This disclosure does not limit the specific technology or device form used in the terminal device.

[0045] It is understood that the communication system described in the embodiments of this disclosure is for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and does not constitute a limitation on the technical solutions provided in the embodiments of this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this disclosure are also applicable to similar technical problems.

[0046] The data compression method and apparatus provided in this disclosure will now be described in detail with reference to the accompanying drawings.

[0047] In related technologies, when a network-side device configures a terminal device to use a small data transmission function on a certain bearer, a packet header compression function (such as ROHC or EHC) also needs to be configured for the terminal device in order to enable data compression for the small data transmission function. The problem that needs to be solved is how to enable the terminal device to continuously perform data compression and how to ensure that the network-side device and the terminal device have a consistent understanding of the area for continuous data compression.

[0048] Based on this, embodiments of this disclosure provide a data compression method to ensure that, for the bearer configured to transmit small data, the network-side device and the terminal device have a consistent understanding of the area where data compression can be performed, thereby enabling data compression within a specific area when the terminal device transmits small data, thus improving data transmission performance.

[0049] Please see Figure 2 , Figure 2 This is a flowchart of a data compression method provided in an embodiment of this disclosure.

[0050] like Figure 2 As shown, this method is applied to a terminal device, and the method may include, but is not limited to, the following steps:

[0051] S21: Receive small data packet transmission SDT configuration information from the network-side device; wherein, the SDT configuration information instructs the terminal device to perform small data packet transmission SDT.

[0052] In this embodiment of the disclosure, the network-side device sends SDT configuration information to the terminal device. For example, the network-side device indicates the SDT configuration information in the RRC Release (Radio Resource Control) message to instruct the terminal device to perform small data packet transmission SDT and to send and receive data through the SDT process.

[0053] S22: Determine the target data compression area; in response to the terminal device being in the target data compression area, perform data compression during Small Data Packet Transmission (SDT).

[0054] In this embodiment of the disclosure, the terminal device determines the target data compression area through a protocol agreement, or by configuration or pre-configuration to the terminal device by the network side device, or by determining the target data compression area from other devices. This embodiment of the disclosure does not impose specific limitations on this.

[0055] It is understood that, in the embodiments of this disclosure, after determining the target data compression area, the terminal device is able to determine that when it is in the target data compression area, it will perform small data packet transmission SDT to compress data.

[0056] In some embodiments, in response to the terminal device being in a target data compression region, data compression is performed during Small Packet Transmission (SDT), including:

[0057] In response to the fact that the cell currently in which the terminal device is camped, or the cell to be reselected, or the selected cell, or the reselected access network type belongs to the target data compression area, data compression is performed during small data packet transmission SDT.

[0058] In some embodiments, the terminal device performs data compression, including at least one of the following:

[0059] During the reconstruction of the Packet Data Convergence Protocol (PDCP) entity, the compressed entity is maintained in a compressed state;

[0060] During PDCP entity reconstruction, the compressed state of the decompressed entity is maintained;

[0061] During PDCP entity recovery, the compressed entity remains in a compressed state;

[0062] During PDCP entity recovery, the compressed state of the decompressed entity is maintained;

[0063] When the Radio Resource Control (RRC) connection is restored, the compressed entity remains compressed.

[0064] When the RRC connection is restored, maintain the compressed state of the decompressed entity;

[0065] When the RRC connection is released, the compressed entity remains compressed.

[0066] When the RRC connection is released, the compressed state of the decompressed entity is maintained.

[0067] Specifically, during the reconstruction of the Packet Data Convergence Protocol (PDCP) entity, the compressed state of the compressed entity is maintained. For example, the compressed entity is not reset or the compression context is preserved.

[0068] During PDCP entity reconstruction, the compression state of the decompressed entity is maintained. For example, decompression is not reset or the decompression context is preserved.

[0069] When a PDCP entity is restored, the compressed state of the compressed entity is maintained. For example, the compressed entity is not reset or the compression context is preserved.

[0070] When a PDCP entity is restored, the compressed state of the decompressed entity is maintained. For example, decompression is not reset or the decompression context is preserved.

[0071] When the Radio Resource Control (RRC) connection is restored, the compressed entity is maintained in its compressed state. For example, the compressed entity is not reset or the compression context is preserved.

[0072] When the RRC connection is restored, the compressed state of the decompressed entity is maintained. For example, decompression is not reset or the decompression context is preserved.

[0073] When the RRC connection is released, the compressed entity remains compressed. For example, the compressed entity is not reset or the compression context is preserved.

[0074] When the RRC connection is released, the compressed state of the decompressed entity is maintained. For example, decompression is not reset or the decompression context is not preserved.

[0075] In some embodiments, a data compression method provided in this disclosure further includes:

[0076] In response to the terminal device not being in the target data compression area, data compression is stopped during Small Data Packet Transmission (SDT).

[0077] It is understood that, in this embodiment of the present disclosure, after the terminal device determines the target data compression area, it is able to determine that when it is not in the target data compression area, the Small Data Packet Transmission (SDT) will stop performing data compression.

[0078] In some embodiments, the terminal device stops performing data compression, including at least one of the following:

[0079] During PDCP entity reconstruction, the compressed entity is reset;

[0080] During PDCP entity reconstruction, the decompressed entity is reset;

[0081] The compressed entity is reset during PDCP entity recovery;

[0082] When restoring the PDCP entity, reset the decompressed entity;

[0083] The compressed entity is reset when the RRC connection is restored;

[0084] The decompression entity is reset when the RRC connection is restored;

[0085] The compressed entity is reset when the RRC connection is released;

[0086] The decompression entity is reset when the RRC connection is released;

[0087] Release the data compression region configuration;

[0088] Entering idle state.

[0089] By implementing the embodiments of this disclosure, a terminal device can receive Small Data Packet Transmission (SDT) configuration information from a network-side device; wherein, the SDT configuration information instructs the terminal device to perform Small Data Packet Transmission (SDT); determines a target data compression area; and, in response to the terminal device being in the target data compression area, performs data compression during Small Data Packet Transmission (SDT). In this way, the terminal device can perform data compression within the target data compression area when performing Small Data Transmission (SDT), thereby improving data transmission performance.

[0090] Please see Figure 3 , Figure 3 This is a flowchart of another data compression method provided in this embodiment.

[0091] like Figure 3 As shown, this method is applied to a terminal device, and the method may include, but is not limited to, the following steps:

[0092] S31: Receive small data packet transmission SDT configuration information from the network-side device; wherein, the SDT configuration information instructs the terminal device to perform small data packet transmission SDT.

[0093] For a detailed description of embodiment S31 of this disclosure, please refer to the relevant description of embodiment S21 of this disclosure above, which will not be repeated here.

[0094] S32: Determine the target data compression area; in response to the terminal device being in the target data compression area, perform data compression during Small Data Packet Transmission (SDT); wherein, the protocol specifies the access network indication area identifier, and the target data compression area is determined to be the access network indication area indicated by the access network indication area identifier.

[0095] In this embodiment of the disclosure, the protocol specifies an access network indication area identifier. The terminal device determines the target data compression area as the access network indication area indicated by the access network indication area identifier according to the access network indication area identifier specified in the protocol.

[0096] In some embodiments, the protocol specifies an access network indication area identifier, including any one of the following:

[0097] The agreement stipulates that for the configuration of authorized CG-SDT, the access network indication area identifier is the access network indication area identifier to which the cell configured with CG-SDT resources belongs;

[0098] The agreement stipulates that the access network indication area identifier is the access network indication area identifier of the cell to which the terminal device receives the connection suspension indication;

[0099] The agreement stipulates that the access network indication area identifier is the access network indication area identifier of the cell to which the terminal device receives the connection release instruction.

[0100] The agreement stipulates that for a configured grant (CG-SDT), the access network indication area identifier is the access network indication area identifier of the cell to which the configured CG-SDT resource belongs. For example, the cell to which the configured CG-SDT resource is located is cell #1, and cell #1 belongs to the access network indication area identifier (e.g., RNA-1 (RAN-based NotificationArea)).

[0101] The protocol stipulates that the access network indication area identifier is the access network indication area identifier of the cell to which the terminal device receives the connection suspension indication. For example, the cell to which the terminal device receives the connection suspension indication is cell #2, and cell #2 belongs to the access network indication area identifier (e.g., RNA-1).

[0102] The protocol stipulates that the access network indication area identifier is the access network indication area identifier of the cell to which the terminal device receives the connection release indication. For example, the cell to which the terminal device receives the connection release indication is cell #3, and cell #3 belongs to the access network indication area identifier (e.g., RNA-1).

[0103] In some embodiments, in response to the terminal device being in a target data compression region, data compression is performed during Small Packet Transmission (SDT), including:

[0104] In response to the fact that the cell currently in which the terminal device is camped, or the cell to be reselected, or the selected cell, or the reselected access network type belongs to the target data compression area, data compression is performed during small data packet transmission SDT.

[0105] For example, when the protocol specifies the access network indication area identifier, if the cell where the terminal device is currently camped belongs to the access network indication area indicated by the access network indication area identifier, the terminal device determines that it is within the target data compression area.

[0106] In another example, when the protocol specifies the access network indication area identifier, if the terminal device reselects or selects a cell that belongs to the access network indication area indicated by the access network indication area identifier, the terminal device determines that it is within the target data compression area.

[0107] Please see Figure 4 , Figure 4 This is a flowchart of another data compression method provided in the embodiments of this disclosure.

[0108] like Figure 4 As shown, this method is applied to a terminal device, and the method may include, but is not limited to, the following steps:

[0109] S41: Receive small data packet transmission SDT configuration information from the network-side device; wherein, the SDT configuration information instructs the terminal device to perform small data packet transmission SDT.

[0110] For a detailed description of embodiment S41 of this disclosure, please refer to the relevant description of embodiment S21 of this disclosure above, which will not be repeated here.

[0111] S42: Determine the target data compression area; in response to the terminal device being in the target data compression area, perform data compression during Small Data Packet Transmission (SDT); wherein, the protocol specifies a cell indication, and the target data compression area is the target cell determined by the cell indication.

[0112] In this embodiment of the disclosure, the protocol specifies a cell indication, and the terminal device determines the target data compression area as the target cell indicated by the cell indication according to the protocol-specified cell indication.

[0113] In some embodiments, in response to the terminal device being in a target data compression region, data compression is performed during Small Packet Transmission (SDT), including:

[0114] In response to the fact that the cell currently in which the terminal device is camped, or the cell to be reselected, or the selected cell, or the reselected access network type belongs to the target data compression area, data compression is performed during small data packet transmission SDT.

[0115] For example, when the protocol specifies a cell indication, if the cell currently in which the terminal device is camped belongs to the target cell determined by the cell indication, the terminal device determines that it is within the target data compression area.

[0116] In another example, when the protocol specifies a cell indication, if the terminal device reselects or selects a cell that belongs to the target cell indicated by the cell indication, the terminal device determines that it is within the target data compression area.

[0117] In some embodiments, the cell indication includes at least one of the following:

[0118] Community signage;

[0119] Community type identifier.

[0120] The cell identifier is used here. For example, the cell identifier is cell #1.

[0121] Cell type identifier. Examples include PCell (Primary Cell), PSCell (Primary-Secondary Cell), SpCell (Special Cell), and SCell (Secondary Cell), etc.

[0122] In some embodiments, the protocol specifies a cell instruction, including any of the following:

[0123] The agreement stipulates that for CG-SDT, the cell indication is the cell that has been configured with CG-SDT resources;

[0124] The agreement defines the cell indicator as the cell in which the terminal device receives a connection suspension indication;

[0125] The agreement stipulates that the cell indicator is the cell in which the terminal device receives the connection release instruction.

[0126] In some embodiments, the cell in which the terminal device receives a connection suspension indication includes any of the following:

[0127] The terminal device successfully received the cell indicating a connection hangup.

[0128] The terminal device receives the cell for the first time a connection hangup indication;

[0129] The cell in which the terminal device last received a connection hangup indication.

[0130] In this context, the cell in which the terminal device successfully received the connection suspension indication is the cell in which the connection suspension indication was received. For example, the RRCRelease message has two segments: segment-1 is sent through cell-1, and segment-2 is sent through cell-2. If the terminal device successfully merges and decodes the RRCRelease message only after receiving segment-2, then cell-2 is considered to be the cell in which the connection suspension indication was successfully received, or the cell in which the connection release indication was received.

[0131] The terminal device first receives the connection suspension indication in the cell. For example, the RRCRelease message has two segments: segment-1 is sent through cell-1, and segment-2 is sent through cell-2. Cell-1 is the cell that first receives the connection suspension indication. In another example, the RRCRelease message is first transmitted in cell-1 via HARQ (hybrid automatic repeat request) process 1; cell-1 is the cell that first receives the connection suspension indication.

[0132] The cell in which the terminal device last received a connection suspension indication. For example, the RRCRelease message has two segments: segment-1 is sent through cell-1, and segment-2 is sent through cell-2. Cell-2 is the cell in which the connection suspension indication was last received. Another example is that the RRCRelease message was last transmitted in cell-2 via HARQ process 1, or the terminal device successfully received the RRCRelease message in cell-2 via HARQ process 1, where cell-2 is the cell in which the connection suspension indication was last received.

[0133] In some embodiments, the cell in which the terminal device receives a connection release indication includes any of the following:

[0134] The terminal device successfully received the cell connection release instruction;

[0135] The cell in which the terminal device first receives the connection release instruction;

[0136] The cell in which the terminal device last received a connection release instruction.

[0137] In this context, the cell in which the terminal device successfully received the connection release instruction is considered the cell. For example, the RRCRelease message has two segments: segment-1 is sent through cell-1, and segment-2 is sent through cell-2. If the terminal device successfully merges and decodes the RRCRelease message only after receiving segment-2, then cell-2 is the cell in which the connection release instruction was successfully received.

[0138] The cell in which the terminal device first receives the connection release indication. For example, the RRCRelease message has two segments: segment-1 is sent through cell-1, and segment-2 is sent through cell-2. Cell-1 is the cell in which the connection release indication is first received. In another example, the RRCRelease message is first transmitted in cell-1 via HARQ process 1; cell-1 is the cell in which the connection release indication is first received.

[0139] The cell in which the terminal device last received the connection release indication. For example, the RRCRelease message has two segments: segment-1 is sent through cell-1, and segment-2 is sent through cell-2. Cell-2 is the cell in which the connection release indication was last received. In another example, the RRCRelease message is last transmitted in cell-2 via HARQ process 1, or the terminal device successfully receives the RRCRelease message in cell-2 via HARQ process 1, where cell-2 is the cell in which the connection release indication was last received.

[0140] It should be noted that in the embodiments of this disclosure, S41 and S42 can be implemented individually or in combination with any other embodiments of this disclosure. For example, they can be implemented together with S21 and S22 and / or S31 and S32 in this disclosure. The embodiments of this disclosure do not impose specific limitations on this.

[0141] Please see Figure 5 , Figure 5 This is a flowchart of another data compression method provided in the embodiments of this disclosure.

[0142] like Figure 5 As shown, this method is applied to a terminal device, and the method may include, but is not limited to, the following steps:

[0143] S51: Receive small data packet transmission SDT configuration information from the network-side device; wherein, the SDT configuration information instructs the terminal device to perform small data packet transmission SDT.

[0144] For a detailed description of embodiment S51 of this disclosure, please refer to the relevant description of embodiment S21 of this disclosure above, which will not be repeated here.

[0145] S52: Determine the target data compression area; in response to the terminal device being in the target data compression area, perform data compression during Small Data Packet Transmission (SDT); wherein, receive the data compression configuration configured by the network-side device; wherein, the data compression configuration includes a data compression area configuration; determine the target data compression area based on the data compression area configuration.

[0146] In some embodiments, determining a target data compression region based on a data compression region configuration includes:

[0147] If the data compression area is configured as the access network indication area identifier, the target data compression area is determined to be the access network indication area indicated by the access network indication area identifier.

[0148] In this embodiment of the disclosure, in the data compression configuration configured by the network-side device, the data compression area is configured as an access network indication area identifier. The terminal device determines the target data compression area as the access network indication area indicated by the access network indication area identifier according to the data compression configuration configured by the network-side device.

[0149] In some embodiments, in response to the terminal device being in a target data compression region, data compression is performed during Small Packet Transmission (SDT), including:

[0150] In response to the fact that the cell currently in which the terminal device is camped, or the cell to be reselected, or the selected cell, or the reselected access network type belongs to the target data compression area, data compression is performed during small data packet transmission SDT.

[0151] For example, when the data compression area is configured as the access network indication area identifier, if the cell where the terminal device is currently camped belongs to the access network indication area indicated by the access network indication area identifier, the terminal device determines that it is within the target data compression area.

[0152] In another example, when the data compression area is configured as the access network indication area identifier, if the terminal device reselects or selects a cell that belongs to the access network indication area indicated by the access network indication area identifier, the terminal device determines that it is within the target data compression area.

[0153] In some embodiments, determining a target data compression region based on a data compression region configuration includes:

[0154] If the data compression area is configured as a cell indicator, the target data compression area is determined as the target cell specified by the cell indicator.

[0155] In this embodiment of the disclosure, in the data compression configuration configured by the network-side device, the data compression area is configured as a cell indicator. The terminal device determines the target data compression area as the target cell determined by the cell indicator based on the data compression configuration configured by the network-side device.

[0156] In some embodiments, in response to the terminal device being in a target data compression region, data compression is performed during Small Packet Transmission (SDT), including:

[0157] In response to the fact that the cell currently in which the terminal device is camped, or the cell to be reselected, or the selected cell, or the reselected access network type belongs to the target data compression area, data compression is performed during small data packet transmission SDT.

[0158] For example, when the data compression area is configured as a cell indicator, if the cell currently camped by the terminal device belongs to the target cell determined by the cell indicator, the terminal device determines that it is within the target data compression area.

[0159] In another example, when the data compression area is configured as a cell indication, if the terminal device reselects or selects a cell that belongs to the target cell determined by the cell indication, the terminal device determines that it is within the target data compression area.

[0160] In some embodiments, the cell indication includes at least one of the following:

[0161] Community signage;

[0162] Community type identifier.

[0163] The cell identifier is used here. For example, the cell identifier is cell #1.

[0164] Cell type identifier. Examples include PCell (Primary Cell), PSCell (Primary-Secondary Cell), SpCell (Special Cell), and SCell (Secondary Cell), etc.

[0165] In some embodiments, the data compression configuration further includes:

[0166] Data compression bearer configuration and data compression type configuration.

[0167] In some embodiments, the data compression bearer configuration includes at least one of the following:

[0168] Data compression corresponds to the bearer type;

[0169] The bearer identifier corresponding to data compression.

[0170] This includes the bearer type corresponding to data compression. For example, MCG (Master Cell Group) or SCG (Secondary Cell Group) bearer.

[0171] The bearer identifier corresponding to data compression. For example, DRB-1 (Data Radio Bearer).

[0172] In some embodiments, the data compression type configuration includes at least one of the following:

[0173] The type indicator corresponding to data compression;

[0174] Indicator of ongoing data compression;

[0175] Indication that data compression has stopped;

[0176] Data compression direction indicator.

[0177] This indicates the type of data compression. Examples include EHC or ROHC.

[0178] Indicators for continuous data compression and indications for continuous data compression stop. Examples include drb-ContinueEHC or drb-ContinueROHC.

[0179] Data compression direction indicator. For example, continuous compression for uplink data (drb-ContinueEHC-UL or...)

[0180] drb-ContinueROHC-UL), or continuous compression of downlink data (drb-ContinueEHC-DL or drb-ContinueROHC-DL), or continuous compression of both uplink and downlink data (drb-ContinueEHC or drb-ContinueROHC), etc.

[0181] In some embodiments, the terminal device stops performing data compression, including at least one of the following:

[0182] Release data compression configuration;

[0183] Remove data compression configuration;

[0184] Release the compression context corresponding to the data compression configuration;

[0185] Delete the compression context corresponding to the data compression configuration.

[0186] This involves releasing or deleting the data compression configuration. For example, deleting the drb-ContinueROHC configuration.

[0187] Release or delete the compression context corresponding to the data compression configuration. For example, delete the compression context of the ROHC entity.

[0188] It should be noted that in the embodiments of this disclosure, S51 and S52 can be implemented individually or in combination with any other embodiments of this disclosure. For example, they can be implemented together with S21 and S22 in this disclosure. The embodiments of this disclosure do not impose specific limitations on this.

[0189] Please see Figure 6 , Figure 6 This is a flowchart of another data compression method provided in the embodiments of this disclosure.

[0190] like Figure 6 As shown, this method is applied to network-side devices, and the method may include, but is not limited to, the following steps:

[0191] S61: Send SDT configuration information to the terminal device to instruct the terminal device to perform small data packet transmission (SDT); send data compression configuration to the terminal device; wherein, the data compression configuration includes data compression area configuration.

[0192] In this embodiment of the disclosure, the network-side device sends SDT configuration information to the terminal device. For example, the network-side device indicates the SDT configuration information in the RRC Release (Radio Resource Control) message to instruct the terminal device to perform small data packet transmission SDT and to send and receive data through the SDT process.

[0193] By implementing the embodiments of this disclosure, a terminal device can receive Small Data Packet Transmission (SDT) configuration information from a network-side device; wherein, the SDT configuration information instructs the terminal device to perform Small Data Packet Transmission (SDT); the terminal device can also receive data compression configuration from the network-side device; wherein, the data compression configuration includes a data compression region configuration. Therefore, the terminal device can determine a target data compression region based on the network-side device's data compression configuration; and perform data compression when performing Small Data Packet Transmission (SDT) within the target data compression region. In this way, the terminal device can perform data compression within the target data compression region when performing Small Data Transmission (SDT), improving data transmission performance.

[0194] In some embodiments, the data compression region configuration includes at least one of the following:

[0195] Access network indication area identifier;

[0196] Community signage.

[0197] In this embodiment of the disclosure, the network-side device sends a data compression configuration to the terminal device; wherein, the data compression configuration includes a data compression area configuration, which includes: an access network indication area identifier; or a cell indication, or an access network indication area identifier and a cell indication.

[0198] In this embodiment of the disclosure, the data compression configuration of the network-side device is configured with the data compression area as the access network indication area identifier, so that the terminal device determines the target data compression area as the access network indication area indicated by the access network indication area identifier according to the data compression configuration of the network-side device.

[0199] In this embodiment of the disclosure, the data compression configuration of the network-side device is configured with a cell indication, so that the terminal device determines the target data compression area as the target cell determined by the cell indication according to the data compression configuration of the network-side device.

[0200] In some embodiments, the cell indication includes at least one of the following:

[0201] Community signage;

[0202] Community type identifier.

[0203] The cell identifier is used here. For example, the cell identifier is cell #1.

[0204] Cell type identifier. Examples include PCell (Primary Cell), PSCell (Primary-Secondary Cell), SpCell (Special Cell), and SCell (Secondary Cell), etc.

[0205] In some embodiments, the data compression configuration further includes:

[0206] Data compression bearer configuration and data compression type configuration.

[0207] In some embodiments, the data compression bearer configuration includes at least one of the following:

[0208] Data compression corresponds to the bearer type;

[0209] The bearer identifier corresponding to data compression.

[0210] This includes the bearer type corresponding to data compression. For example, MCG (Master Cell Group) or SCG (Secondary Cell Group) bearer.

[0211] The bearer identifier corresponding to data compression. For example, DRB-1 (Data Radio Bearer).

[0212] In some embodiments, the data compression type configuration includes at least one of the following:

[0213] The type indicator corresponding to data compression;

[0214] Indicator of ongoing data compression;

[0215] Indication that data compression has stopped;

[0216] Data compression direction indicator.

[0217] This indicates the type of data compression. Examples include EHC or ROHC.

[0218] Indicators for continuous data compression and indications for continuous data compression stop. Examples include drb-ContinueEHC or drb-ContinueROHC.

[0219] Data compression direction indicator. For example, continuous compression for uplink data (drb-ContinueEHC-UL or...)

[0220] drb-ContinueROHC-UL), or continuous compression of downlink data (drb-ContinueEHC-DL or drb-ContinueROHC-DL), or continuous compression of both uplink and downlink data (drb-ContinueEHC or drb-ContinueROHC), etc.

[0221] In the embodiments provided above, the methods provided by the present disclosure are described from the perspectives of network-side devices and terminal devices, respectively. To implement the functions of the methods provided in the embodiments of the present disclosure, the network-side devices and terminal devices may include hardware structures and software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. One of the above functions can be executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules.

[0222] Please see Figure 7 This is a structural diagram of a communication device 1 provided in an embodiment of the present disclosure. Figure 7 The communication device 1 shown may include a transceiver module 11 and a processing module 12. The transceiver module 11 may include a sending module and / or a receiving module. The sending module is used to implement the sending function, and the receiving module is used to implement the receiving function. The transceiver module 11 can implement both sending and / or receiving functions.

[0223] The communication device 1 can be a terminal device, a device within a terminal device, or a device that can be used in conjunction with a terminal device.

[0224] Communication device 1 is a terminal device:

[0225] The device includes: a transceiver module 11, used to receive small data packet transmission SDT configuration information from network-side devices; wherein the SDT configuration information instructs the terminal device to perform small data packet transmission SDT.

[0226] Processing module 12 is used to determine the target data compression area; in response to the terminal device being in the target data compression area, it performs data compression during Small Data Packet Transmission (SDT).

[0227] In some embodiments, the processing module 12 is further configured to stop performing data compression during Small Data Packet Transmission (SDT) in response to the terminal device not being in the target data compression area.

[0228] In some embodiments, the processing module 12 is specifically used to determine the target data compression area according to the agreement.

[0229] In some embodiments, the processing module 12 is specifically used to agree on the access network indication area identifier and determine that the target data compression area is the access network indication area indicated by the access network indication area identifier.

[0230] In some embodiments, the protocol specifies an access network indication area identifier, including any one of the following:

[0231] The agreement stipulates that for the configuration of authorized CG-SDT, the access network indication area identifier is the access network indication area identifier to which the cell configuring CG-SDT resources belongs;

[0232] The agreement stipulates that the access network indication area identifier is the access network indication area identifier of the cell to which the terminal device receives the connection suspension indication;

[0233] The agreement stipulates that the access network indication area identifier is the access network indication area identifier of the cell to which the terminal device receives the connection release instruction.

[0234] In some embodiments, the processing module 12 is specifically used to agree on a cell indication and determine the target data compression area as the target cell indicated by the cell indication.

[0235] In some embodiments, the cell indication includes at least one of the following:

[0236] Community signage;

[0237] Community type identifier.

[0238] In some embodiments, the protocol specifies a cell instruction, including any of the following:

[0239] The agreement stipulates that for CG-SDT, the cell indicated is a cell configured with CG-SDT resources;

[0240] The agreement stipulates that the cell indication refers to the cell in which the terminal device receives a connection suspension indication;

[0241] The protocol stipulates that the cell indicator is the cell in which the terminal device receives the connection release instruction.

[0242] In some embodiments, the cell in which the terminal device receives a connection suspension indication includes any of the following:

[0243] The terminal device successfully received the cell indicating a connection hangup.

[0244] The terminal device receives the cell for the first time a connection hangup indication;

[0245] The cell in which the terminal device last received a connection hangup indication.

[0246] In some embodiments, the cell in which the terminal device receives a connection release indication includes any of the following:

[0247] The terminal device successfully received the cell connection release instruction;

[0248] The cell in which the terminal device first receives the connection release instruction;

[0249] The cell in which the terminal device last received a connection release instruction.

[0250] In some embodiments, the processing module 12 is specifically configured to receive a data compression configuration configured by a network-side device; wherein the data compression configuration includes a data compression region configuration; and to determine the target data compression region based on the data compression region configuration.

[0251] In some embodiments, the processing module 12 is specifically configured to determine the target data compression area as the access network indication area indicated by the access network indication area identifier if the data compression area is configured as an access network indication area identifier.

[0252] In some embodiments, the processing module 12 is specifically configured to determine the target data compression area as the target cell determined by the cell indication if the data compression area is configured as a cell indication.

[0253] In some embodiments, the cell indication includes at least one of the following:

[0254] Community signage;

[0255] Community type identifier.

[0256] In some embodiments, the data compression configuration further includes:

[0257] Data compression bearer configuration and data compression type configuration.

[0258] In some embodiments, the data compression bearer configuration includes at least one of the following:

[0259] Data compression corresponds to the bearer type;

[0260] The bearer identifier corresponding to data compression.

[0261] In some embodiments, the data compression type configuration includes at least one of the following:

[0262] The type indicator corresponding to data compression;

[0263] Indicator of ongoing data compression;

[0264] Indication that data compression has stopped;

[0265] Data compression direction indicator.

[0266] In some embodiments, the processing module 12 is specifically used to perform data compression during Small Data Packet Transmission (SDT) in response to the current cell where the terminal device is camped, or the reselected cell, or the selected cell, or the reselected access network type belonging to the target data compression area.

[0267] In some embodiments, the processing module 12 is specifically configured to perform data compression, including at least one of the following:

[0268] During the reconstruction of the Packet Data Convergence Protocol (PDCP) entity, the compressed entity is maintained in a compressed state;

[0269] During PDCP entity reconstruction, the compressed state of the decompressed entity is maintained;

[0270] During PDCP entity recovery, the compressed entity remains in a compressed state;

[0271] During PDCP entity recovery, the compressed state of the decompressed entity is maintained;

[0272] When the Radio Resource Control (RRC) connection is restored, the compressed entity remains compressed.

[0273] When the RRC connection is restored, maintain the compressed state of the decompressed entity;

[0274] When the RRC connection is released, the compressed entity remains compressed.

[0275] When the RRC connection is released, the compressed state of the decompressed entity is maintained.

[0276] In some embodiments, the processing module 12 is specifically configured to stop performing data compression, including at least one of the following:

[0277] During PDCP entity reconstruction, the compressed entity is reset;

[0278] During PDCP entity reconstruction, the decompressed entity is reset;

[0279] The compressed entity is reset during PDCP entity recovery;

[0280] When restoring the PDCP entity, reset the decompressed entity;

[0281] The compressed entity is reset when the RRC connection is restored;

[0282] The decompression entity is reset when the RRC connection is restored;

[0283] The compressed entity is reset when the RRC connection is released;

[0284] The decompression entity is reset when the RRC connection is released;

[0285] Release the data compression region configuration;

[0286] Entering idle state.

[0287] In some embodiments, the processing module 12 is specifically configured to stop performing data compression, including at least one of the following:

[0288] Release the data compression configuration;

[0289] Delete the data compression configuration;

[0290] Release the compression context corresponding to the data compression configuration;

[0291] Delete the compression context corresponding to the data compression configuration.

[0292] In this embodiment of the disclosure, the communication device 1 may be a network-side device, a device within a network-side device, or a device that can be used in conjunction with a network-side device.

[0293] Communication device 1 is a network-side device:

[0294] The device includes: a transceiver module 11, configured to send SDT configuration information to a terminal device to instruct the terminal device to perform Small Data Packet Transmission (SDT); and to send data compression configuration to the terminal device; wherein the data compression configuration includes a data compression area configuration.

[0295] In some embodiments, the data compression region configuration includes at least one of the following:

[0296] Access network indication area identifier;

[0297] Community signage.

[0298] In some embodiments, the cell indication includes at least one of the following:

[0299] Community signage;

[0300] Community type identifier.

[0301] In some embodiments, the data compression configuration further includes:

[0302] Data compression bearer configuration and data compression type configuration.

[0303] In some embodiments, the data compression bearer configuration includes at least one of the following:

[0304] Data compression corresponds to the bearer type;

[0305] The bearer identifier corresponding to data compression.

[0306] In some embodiments, the data compression type configuration includes at least one of the following:

[0307] The type indicator corresponding to data compression;

[0308] Indicator of ongoing data compression;

[0309] Indication that data compression has stopped;

[0310] Data compression direction indicator.

[0311] Regarding the communication device 1 in the above embodiments, the specific methods by which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated here.

[0312] The communication device 1 provided in the above embodiments of this disclosure achieves the same or similar beneficial effects as the resource configuration method provided in some of the above embodiments, and will not be repeated here.

[0313] Please see Figure 8 , Figure 8 This is a schematic diagram of another communication device 1000 provided in this embodiment. The communication device 1000 can be a network-side device, a terminal device, a chip, chip system, or processor that supports the network-side device in implementing the above methods, or a chip, chip system, or processor that supports the terminal device in implementing the above methods. This communication device 1000 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0314] The communication device 1000 may include one or more processors 1001. The processor 1001 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0315] Optionally, the communication device 1000 may further include one or more memories 1002, which may store a computer program 1004. The memories 1002 execute the computer program 1004 to cause the communication device 1000 to perform the methods described in the above method embodiments. Optionally, the memories 1002 may also store data. The communication device 1000 and the memories 1002 may be provided separately or integrated together.

[0316] Optionally, the communication device 1000 may further include a transceiver 1005 and an antenna 1006. The transceiver 1005 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 1005 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0317] Optionally, the communication device 1000 may further include one or more interface circuits 1007. The interface circuit 1007 is used to receive code instructions and transmit them to the processor 1001. The processor 1001 executes the code instructions to cause the communication device 1000 to perform the method described in the above method embodiments.

[0318] Communication device 1000 is a terminal device: transceiver 1005 is used to perform... Figure 2 S21 in; Figure 3 S31 in; Figure 4 S41 in; Figure 5 The S51 processor 1001 is used to execute... Figure 2 S22 in the middle; Figure 3 S32 in the middle; Figure 4 S42 in; Figure 5 S52 in the middle.

[0319] Communication device 1000 is a network-side device: transceiver 1005 is used to perform... Figure 6 S61 in the middle.

[0320] In one implementation, the processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0321] In one implementation, processor 1001 may store computer program 1003, which runs on processor 1001 and causes communication device 1000 to execute the methods described in the above method embodiments. Computer program 1003 may be embedded in processor 1001, in which case processor 1001 may be implemented in hardware.

[0322] In one implementation, the communication device 1000 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this disclosure can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide-semiconductor (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal-oxide-semiconductor (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0323] The communication device described in the above embodiments may be a terminal device, but the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may vary. Figure 8 The communication device may be a standalone device or part of a larger device. For example, the communication device may be:

[0324] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0325] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0326] (3) ASIC, such as modem;

[0327] (4) Modules that can be embedded in other devices;

[0328] (5) Receivers, terminal equipment, smart terminal equipment, cellular phones, wireless equipment, handheld devices, mobile units, vehicle-mounted equipment, network equipment, cloud equipment, artificial intelligence equipment, etc.

[0329] (6) Others, etc.

[0330] For cases where the communication device can be a chip or a chip system, please refer to [link / reference]. Figure 9 This is a structural diagram of a chip provided in an embodiment of this disclosure.

[0331] Chip 1100 includes processor 1101 and interface 1103. The number of processors 1101 can be one or more, and the number of interfaces 1103 can be multiple.

[0332] Regarding the case where the chip is used to implement the functions of the terminal device in the embodiments of this disclosure:

[0333] Interface 1103 is used to receive code instructions and transmit them to the processor.

[0334] Processor 1101 is used to run code instructions to perform data compression methods as described in some of the embodiments above.

[0335] For cases where the chip is used to implement the functions of the network-side device in the embodiments of this disclosure:

[0336] Interface 1103 is used to receive code instructions and transmit them to the processor.

[0337] Processor 1101 is used to run code instructions to perform data compression methods as described in some of the embodiments above.

[0338] Optionally, chip 1100 may also include memory 1102, which is used to store necessary computer programs and data.

[0339] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this disclosure can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented in hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this disclosure.

[0340] This disclosure also provides a resource allocation system, which includes the aforementioned... Figure 7 In the embodiments, the communication device serves as a terminal device and the communication device serves as a network-side device; alternatively, the system includes the aforementioned components. Figure 8 The embodiments include a communication device as a terminal device and a communication device as a network-side device.

[0341] This disclosure also provides a readable storage medium having instructions stored thereon that, when executed by a computer, implement the functions of any of the above method embodiments.

[0342] This disclosure also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0343] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0344] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., used in this disclosure are merely for the convenience of description and are not intended to limit the scope of the embodiments of this disclosure, nor do they indicate the order of events.

[0345] At least one of the features described in this disclosure can also be described as one or more, and multiple features can be two, three, four or more, and this disclosure does not impose any limitations. In the embodiments of this disclosure, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no sequential order or size order among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0346] The correspondences shown in the tables of this disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this disclosure is not limiting. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this disclosure may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headers of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0347] The predefined terms in this disclosure can be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0348] 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 disclosure.

[0349] 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.

[0350] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure 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 disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A data compression method, characterized in that, The method is applied to a terminal device and includes: Receive small data packet transmission SDT configuration information from network-side devices; wherein, the SDT configuration information instructs the terminal device to perform small data packet transmission SDT; Determine the target data compression area; In response to the terminal device being in the target data compression area, data compression is performed during Small Data Packet Transmission (SDT). The determination of the target data compression area includes: Upon receiving a data compression configuration sent by a network-side device, the target data compression region is determined based on the data compression region configuration included in the data compression configuration. The data compression region is configured as an access network indication region identifier or a cell indication. When data compression is configured according to the protocol, the target data compression area is determined based on the access network indication area identifier or cell indication specified in the protocol. The target data compression area is the access network indication area indicated by the access network indication area identifier or the target cell determined by the cell indication; The method further includes: stopping data compression during Small Data Packet Transmission (SDT) in response to the terminal device not being in the target data compression area; and, upon receiving the data compression configuration, stopping data compression includes at least one of the following: Release the data compression configuration; Delete the data compression configuration; Release the compression context corresponding to the data compression configuration; Delete the compression context corresponding to the data compression configuration.

2. The method as described in claim 1, characterized in that, The access network indication area identifier stipulated in the agreement includes any one of the following: The agreement stipulates that for the configuration of authorized CG-SDT, the access network indication area identifier is the access network indication area identifier to which the cell configuring CG-SDT resources belongs; The agreement stipulates that the access network indication area identifier is the access network indication area identifier of the cell to which the terminal device receives the connection suspension indication; The agreement stipulates that the access network indication area identifier is the access network indication area identifier of the cell to which the terminal device receives the connection release instruction.

3. The method as described in claim 1, characterized in that, The cell indication includes at least one of the following: Community signage; Community type identifier.

4. The method as described in claim 1, characterized in that, The cell instruction stipulated in the agreement includes any one of the following: The agreement stipulates that for CG-SDT, the cell indicated is a cell configured with CG-SDT resources; The agreement stipulates that the cell indication refers to the cell in which the terminal device receives a connection suspension indication; The protocol stipulates that the cell indicator is the cell in which the terminal device receives the connection release instruction.

5. The method as described in claim 4, characterized in that, The cell in which the terminal device receives a connection suspension indication includes any one of the following: The terminal device successfully received the cell indicating a connection hangup. The terminal device receives the cell for the first time a connection hangup indication; The cell in which the terminal device last received a connection hangup indication.

6. The method as described in claim 4, characterized in that, The cell in which the terminal device receives the connection release indication includes any one of the following: The terminal device successfully received the cell connection release instruction; The cell in which the terminal device first receives the connection release instruction; The cell in which the terminal device last received a connection release instruction.

7. The method as described in claim 1, characterized in that, The data compression configuration also includes: Data compression bearer configuration and data compression type configuration.

8. The method as described in claim 7, characterized in that, The data compression bearer configuration includes at least one of the following: Data compression corresponds to the bearer type; The bearer identifier corresponding to data compression.

9. The method as described in claim 7, characterized in that, The data compression type configuration includes at least one of the following: The type indicator corresponding to data compression; Indicator of ongoing data compression; Indication that data compression has stopped; Data compression direction indicator.

10. The method according to any one of claims 1 to 9, characterized in that, The step of performing data compression during Small Data Packet Transmission (SDT) in response to the terminal device being in the target data compression area includes: In response to the fact that the cell currently in which the terminal device is camped, or the cell to be reselected, or the selected cell, or the access network type to be reselected belongs to the target data compression area, data compression is performed during small data packet transmission SDT.

11. The method according to any one of claims 1 to 9, characterized in that, The data compression process includes at least one of the following: During the reconstruction of the Packet Data Convergence Protocol (PDCP) entity, the compressed entity is maintained in a compressed state; During PDCP entity reconstruction, the compressed state of the decompressed entity is maintained; During PDCP entity recovery, the compressed entity remains in a compressed state; During PDCP entity recovery, the compressed state of the decompressed entity is maintained; When the Radio Resource Control (RRC) connection is restored, the compressed entity remains compressed. When the RRC connection is restored, maintain the compressed state of the decompressed entity; When the RRC connection is released, the compressed entity remains compressed. When the RRC connection is released, the compressed state of the decompressed entity is maintained.

12. The method according to any one of claims 1 to 9, characterized in that, The cessation of data compression includes at least one of the following: During PDCP entity reconstruction, the compressed entity is reset; During PDCP entity reconstruction, the decompressed entity is reset; The compressed entity is reset during PDCP entity recovery; When restoring the PDCP entity, reset the decompressed entity; The compressed entity is reset when the RRC connection is restored; The decompression entity is reset when the RRC connection is restored; The compressed entity is reset when the RRC connection is released; The decompression entity is reset when the RRC connection is released; Release the data compression region configuration; Entering idle state.

13. A data compression method, characterized in that, The method is applied to network-side devices, including: Send SDT configuration information to the terminal device to instruct the terminal device to perform small data packet transmission SDT; A data compression configuration is sent to the terminal device; wherein, the data compression configuration includes a data compression region configuration, which is used by the terminal device, upon receiving the data compression configuration sent by the network-side device, to determine a target data compression region based on the data compression region configuration included in the data compression configuration, wherein the data compression region configuration is an access network indication region identifier or a cell indication; in the case of a data compression configuration agreed upon through a protocol, the target data compression region is determined according to the access network indication region identifier or the cell indication as agreed upon in the protocol; the target data compression region is the access network indication region indicated by the access network indication region identifier or the target cell determined by the cell indication. The data compression area configuration is further configured to stop data compression when the terminal device is not in the target data compression area and is performing Small Data Packet Transmission (SDT). The stopping of data compression includes at least one of the following: Release the data compression configuration; Delete the data compression configuration; Release the compression context corresponding to the data compression configuration; Delete the compression context corresponding to the data compression configuration.

14. The method as described in claim 13, characterized in that, The data compression area configuration includes at least one of the following: Access network indication area identifier; Community signage.

15. The method as described in claim 13 or 14, characterized in that, The cell indication includes at least one of the following: Community signage; Community type identifier.

16. The method as described in claim 13, characterized in that, The data compression configuration also includes: Data compression bearer configuration and data compression type configuration.

17. The method as described in claim 16, characterized in that, The data compression bearer configuration includes at least one of the following: Data compression corresponds to the bearer type; The bearer identifier corresponding to data compression.

18. The method as described in claim 16, characterized in that, The data compression type configuration includes at least one of the following: The type indicator corresponding to data compression; Indicator of ongoing data compression; Indication that data compression has stopped; Data compression direction indicator.

19. A communication device, characterized in that, include: The transceiver module is used to receive Small Data Packet Transmission (SDT) configuration information from the network-side device; wherein, the SDT configuration information instructs the terminal device to perform Small Data Packet Transmission (SDT). The processing module is used to determine the target data compression area; and to perform data compression when the terminal device is in the target data compression area during Small Data Packet Transmission (SDT). The processing module is configured to, upon receiving a data compression configuration sent by a network-side device, determine the target data compression region based on the data compression region configuration included in the data compression configuration, wherein the data compression region configuration is an access network indication region identifier or a cell indication; and, upon agreeing on a data compression configuration through a protocol, determine the target data compression region based on the access network indication region identifier or cell indication agreed on in the protocol, wherein the target data compression region is the access network indication region indicated by the access network indication region identifier or the target cell determined by the cell indication. The processing module is further configured to stop performing data compression during Small Data Packet Transmission (SDT) in response to the terminal device not being in the target data compression area; and to stop performing data compression upon receiving the data compression configuration, including at least one of the following: Release the data compression configuration; Delete the data compression configuration; Release the compression context corresponding to the data compression configuration; Delete the compression context corresponding to the data compression configuration.

20. A communication device, characterized in that, include: The transceiver module is used to send SDT configuration information to the terminal device, instructing the terminal device to perform small data packet transmission SDT; The transceiver module is further configured to send a data compression configuration to the terminal device; wherein, the data compression configuration includes a data compression region configuration, which is used by the terminal device, upon receiving the data compression configuration sent by the network-side device, to determine a target data compression region based on the data compression region configuration included in the data compression configuration, wherein the data compression region configuration is an access network indication region identifier or a cell indication; and in the case of data compression configuration agreed upon through a protocol, to determine the target data compression region based on the access network indication region identifier or cell indication agreed upon in the protocol; wherein the target data compression region is the access network indication region indicated by the access network indication region identifier or the target cell determined by the cell indication. The data compression area configuration is further configured to stop data compression when the terminal device is not in the target data compression area and is performing Small Data Packet Transmission (SDT). The stopping of data compression includes at least one of the following: Release the data compression configuration; Delete the data compression configuration; Release the compression context corresponding to the data compression configuration; Delete the compression context corresponding to the data compression configuration.

21. A communication device, characterized in that, The device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method as described in any one of claims 1 to 12; Alternatively, the processor may execute a computer program stored in the memory to cause the apparatus to perform the method as described in any one of claims 13 to 18.

22. A communication device, characterized in that, include: Processor and interface circuitry; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to execute the code instructions to perform the method as described in any one of claims 1 to 12; Or it may be used to run the code instructions to perform the method as described in any one of claims 13 to 18.

23. A computer-readable storage medium for storing instructions that, when executed, cause the method of any one of claims 1 to 12 to be implemented; or, when executed, cause the method of any one of claims 13 to 18 to be implemented.

Images