Processing methods and communication devices

Abstract

To provide a processing method and a communication apparatus for solving the problem of packet header compression or decompression on a terminal side and a network side.SOLUTION: A working example of the present disclosure provides a processing method and a communication apparatus. The method includes determining a ROHC entity for compression or decompression according to first information. Here, the first information is any one of indication information in the packet header of a PDCP packet, mobility procedure completion information, a PDCP identifier of the PDCP packet, a connection corresponding to the PDCP packet, indication information in a PDCP control packet, PDCP setting information, and setting information on the ROHC entity for compression or decompression.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims priority from Chinese Patent Application No. 201910093599.0, filed in China on January 30, 2019, the entire contents of which are incorporated herein by reference.

[0002] TECHNICAL FIELD Embodiments of the present disclosure relate to the technical field of communications, and in particular to a processing method and a communication device. [Background technology]

[0003] When there are multiple ROHC (Robust Header Compression) entities for compression (or decompression) on the network side for one Data Radio Bearer (DRB) (or Packet Data Convergence Protocol (PDCP)) of a terminal, how to realize the compression or decompression of packet headers on the terminal side and the network side has become an urgent issue to be solved. Summary of the Invention [Problem to be solved by the invention]

[0004] One of the objectives of the embodiments of the present disclosure is to provide a processing method and communication device for solving the problem of packet header compression or decompression on the terminal side and the network side. [Means for solving the problem]

[0005] According to a first aspect of an embodiment of the present disclosure, there is provided a processing method applied to a communication device, comprising: determining a Robust Header Compression (ROHC) entity for compression or decompression according to the first information; Here, the first information is one or more of indication information in a packet header of a Packet Data Convergence Protocol (PDCP) packet, information on completion of a mobility procedure, a PDCP identifier of a PDCP packet, a connection corresponding to the PDCP packet, indication information in a PDCP control packet, PDCP configuration information, and configuration information of a compression or decompression ROHC entity.

[0006] According to a second aspect of an embodiment of the present disclosure, there is provided a communication device, a determining module for determining a robust header compressed ROHC entity for compression or decompression according to the first information; Here, the first information further provides the communication device with one or more of: indication information in a packet header of a PDCP packet, information on completion of a mobility procedure, a PDCP identifier of the PDCP packet, a connection corresponding to the PDCP packet, indication information in a PDCP control packet, PDCP configuration information, and configuration information of a compression or decompression ROHC entity.

[0007] According to a third aspect of an embodiment of the present disclosure, there is further provided a communication device including a processor, a memory, and a program stored in the memory and operable on the processor, wherein the processing method described above is realized when the program is executed by the processor.

[0008] According to a fourth aspect of an embodiment of the present disclosure, there is further provided a computer-readable storage medium storing a computer program, the computer program being capable of realizing the above-described processing method when executed by a processor. [Effects of the Invention]

[0009] In the embodiments of the present disclosure, even if there are multiple ROHC entities for compression or decompression on the network side working for one DRB (or PDCP) of the terminal, the terminal side and the network side can realize the compression or decompression function of the packet header. [Brief explanation of the drawings]

[0010] Various other benefits and advantages will become apparent to those skilled in the art upon reading the following detailed description of select embodiments. The drawings are only for purposes of illustrating select embodiments and should not be construed as limitations on the present disclosure. Furthermore, like elements will be designated by like reference numerals throughout the drawings. [Figure 1] 1 is a schematic diagram illustrating the architecture of a wireless communication system according to an embodiment of the present disclosure. [Figure 2] 1 is a flowchart of a processing method according to an embodiment of the present disclosure. [Figure 3] 1 is a structural diagram of a communication device according to an embodiment of the present disclosure. [Figure 4] FIG. 2 is a second structural diagram of a communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, the technical solutions in the embodiments of the present disclosure will be clearly and completely described with reference to the drawings in the embodiments of the present disclosure, but it should be apparent that the described embodiments are only some of the embodiments of the present disclosure, and not all of the embodiments. Based on the embodiments of the present disclosure, other embodiments obtained by those skilled in the art without paying creative labor shall all fall within the scope of protection of the present disclosure.

[0012] The term "comprises" and any variations thereof in the specification and claims of this application cover non-exclusive inclusions, for example, a procedure, method, system, product, or device including a series of steps or units is not limited to including only those steps or units that are explicitly enumerated, but may also include other steps or units that are not explicitly enumerated, or other steps or units that are inherent to the procedure, method, product, or device. Note that "and / or" used in the specification and claims indicates at least one of the connected objects, for example, "A and / or B" includes the three cases of only A being present, only B being present, and both A and B being present.

[0013] In the embodiments of the present disclosure, terms such as "exemplary" or "for example" are intended to illustrate or explain by way of example. Any embodiment or design described with terms such as "exemplary" or "for example" in the embodiments of the present disclosure should not be construed as being more preferred or advantageous than other embodiments or designs. Where appropriate, terms such as "exemplary" or "for example" are used to present related concepts in a concrete form.

[0014] In order to facilitate understanding of the technical solutions of the embodiments of the present disclosure, some technical points are introduced below.

[0015] 1. Introduction to Robust Header Compression (ROHC).

[0016] In a Long Term Evolution (LTE) or 5G (5th-generation) New Radio (NR) system, a network can configure a ROHC function within a Packet Data Convergence Protocol (PDCP) entity. The ROHC function is associated with up to one ROHC compression (e.g., corresponding uplink data transmission on the terminal side) entity (or module, protocol layer, or context) and up to one ROHC decompression (e.g., corresponding downlink data reception on the terminal side) entity (or module, protocol layer, or context) within the PDCP entity. The ROHC entity can compress and decompress packet headers of upper-layer data packets (e.g., Transmission Control Protocol (TCP) / Internet Protocol (IP)), while the ROHC decompression entity can send feedback information about the decompression status to the other ROHC compression entity.

[0017] During the handover procedure, the network side can configure (ie indicate through DRB-ContinueROHC signaling) whether the ROHC entity of the PDCP entity needs to be reset.

[0018] For example, if the network side wants the terminal to still adopt the ROHC entity before the handover during the handover procedure, by setting drb-ContinueROHC to the terminal, the terminal will continue to use the ROHC entity before the handover without resetting its own ROHC.

[0019] 2. Introduction to dual connectivity (DC) handover.

[0020] In a 5G system, since the mobility procedure interruption delay of 0 ms needs to be met, a terminal needs to secure a connection for data transmission and reception with both the source node and the target node during its movement. The data connection must be maintained with both the source node and the target node. The source node and the target node on the corresponding network side have independent ROHC compression or decompression entities.

[0021] The techniques described in this specification are not limited to 5G systems and subsequent evolved communication systems, as well as LTE / LTE evolved LTE-Advanced (LTE-A) systems, but can also be used in various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), and other systems.

[0022] The terms "system" and "network" are often used interchangeably. A CDMA system can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants. A TDMA system can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA system can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolution-UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). LTE and more advanced LTE (e.g., LTE-A) are newer versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP®). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein may be used with the above systems and radio technologies, as well as other systems and radio technologies.

[0023] Hereinafter, embodiments of the present disclosure will be described in conjunction with the drawings. Processing methods and devices according to embodiments of the present disclosure are applicable to wireless communication systems. Referring to FIG. 1, the figure is a schematic diagram of the architecture of a wireless communication system according to an embodiment of the present disclosure. As shown in FIG. 1, the wireless communication system may include a first network device 10, a second network device 11, and a terminal. The terminal is referred to as a user equipment (UE) 12. The UE 12 is capable of communicating (signaling transmission or data transmission) with the first network device 10 and the second network device 11. In actual applications, the connections between the above devices may be wireless. However, in FIG. 1, the connections between the above devices are schematically shown using solid lines to more intuitively illustrate the connection relationships between the devices. It should be noted that the communication system may include multiple UEs 12, and the first network device 10 and the second network device 11 are capable of communicating with the multiple UEs 12.

[0024] The terminal according to the embodiment of the present disclosure may be a mobile phone, a tablet PC, a notebook PC, an ultra-mobile personal computer (UMPC), a netbook or a personal digital assistant (PDA), a mobile internet device (MID), a wearable device, or an in-vehicle device, etc.

[0025] The first network device 10 and the second network device 11 according to the embodiments of the present disclosure may be base stations, which may be commonly used base stations or evolved node base stations (eNBs), and may also be network devices in a 5G system (for example, next generation node base stations (gNBs) or transmission and reception points (TRPs)).

[0026] In the embodiments of the present disclosure, a ROHC entity may be referred to as a ROHC module, a ROHC protocol layer, or a ROHC context.

[0027] Referring to FIG. 2 , an embodiment of the present disclosure further provides a processing method, where an execution body of the method may be a communication device, such as a terminal or a network device, and the method includes step 201.

[0028] Step 201: Determine a ROHC entity for compression or decompression according to the first information.

[0029] Here, the first information may be one or more of: indication information in a packet header of a PDCP packet; information on completion of a mobility procedure; a PDCP identifier of the PDCP packet; a connection corresponding to the PDCP packet; indication information in a PDCP control packet; PDCP configuration information; and configuration information of a compression or decompression ROHC entity.

[0030] It should be noted that the PDCP packets may be PDCP data packets and / or ROHC feedback packets.

[0031] In the case where a communication device has multiple ROHC entities for compression or decompression, for example: (1.1) Add indication information to the PDCP packet header to indicate the ROHC entity to be used.

[0032] (1.2) If the serial number of the PDCP packet is before the specified PDCP serial number SN (Serial Number), the communication device adopts ROHC entity 1, and if it is after the specified PDCP SN number, the communication device adopts ROHC entity 2.

[0033] (1.3) For PDCP packets from connection 1, ROHC entity 1 associated with connection 1 is employed, and for PDCP packets from connection 2, ROHC entity 2 associated with connection 2 is employed.

[0034] (1.4) The indication information in the PDCP control packet indicates whether to change the ROHC entity used by the communication device.

[0035] In the case where a communication device has one ROHC entity, for example, (2.1) The instruction information in the PDCP control packet instructs the communication device to delete its previous ROHC entity (old ROHC entity) and establish a new ROHC entity.

[0036] (2.2) If it is before the specified PDCP SN number, the communication device adopts ROHC entity 1, and if it is after the specified PDCP SN number, the communication device deletes ROHC entity 1 and establishes and adopts ROHC entity 2.

[0037] For example, if a communication device employs a ROHC Continue function, the communication device employs one ROHC entity for compression or decompression; otherwise, the communication device employs multiple ROHC entities for compression or decompression. As can be understood, if a communication device employs one ROHC entity for compression or decompression, the methods described in (2.1) to (2.2) above are all applicable. If a communication device employs multiple ROHC entities for compression or decompression, the methods described in (1.1) to (1.4) above are all applicable.

[0038] In an embodiment of the present disclosure, optionally, the PDCP configuration information may instruct the communication device to adopt a ROHC continuity function, and one PDCP entity of the communication device may include one ROHC entity for compression or decompression.

[0039] In an embodiment of the present disclosure, optionally, the PDCP configuration information may not instruct the communication device to adopt the ROHC continuity function, and one PDCP entity of the communication device may include multiple ROHC entities for compression or decompression.

[0040] In an embodiment of the present disclosure, optionally, the indication information in the PDCP control packet is: (1) causing a communication device to modify a compression or decompression ROHC entity; (2) not allowing communications devices to modify compression or decompression ROHC entities; and (3) causing the communication device to delete the previous compression or decompression ROHC entity and establish a new compression or decompression ROHC entity.

[0041] In an embodiment of the present disclosure, optionally, before step 201, the method shown in FIG. 2 includes: The method may further include determining the corresponding first information according to a specific instruction manner; Here, the specific instruction method is: (1) Instructions in the packet header of the PDCP packet, (2) An instruction based on the setting information of the PDCP identifier of the PDCP packet; (3) an instruction by the setting information of the connection corresponding to the PDCP packet; (4) An instruction by a PDCP control packet may be included.

[0042] In the embodiment of the present disclosure, optionally, the specific indication manner may be set by the network side or defined by a protocol.

[0043] In the embodiments of the present disclosure, optionally, the PDCP identifier configuration information includes: (1) a specified PDCP packet identifier; and (2) a compression or decompression ROHC entity employed before the specified PDCP packet identifier; and (3) A compression or decompression ROHC entity employed after the specified PDCP packet identifier may be included.

[0044] In the embodiment of the present disclosure, optionally, if the PDCP entity of the communication device includes multiple ROHC entities for compression or decompression, step 201 may include: (1) if the PDCP identifier of the PDCP packet is before a specified PDCP identifier, employing a corresponding ROHC entity for compression or decompression; (2) If the PDCP identifier of the PDCP packet is after a specified PDCP identifier, employing a corresponding ROHC entity for compression or decompression.

[0045] In the embodiment of the present disclosure, optionally, if the PDCP entity of the communication device includes one ROHC entity for compression or decompression, step 201 includes: (1) employing a first compression or decompression ROHC entity if the PDCP identifier of the PDCP packet precedes a specified PDCP identifier; (2) if the PDCP identifier of the PDCP packet is after the specified PDCP identifier, deleting the first compression or decompression ROHC entity and establishing and adopting a new compression or decompression ROHC entity; Here, the first compression or decompression ROHC entity is one specific compression or decompression ROHC entity established by the communication device according to configuration information of multiple compression or decompression ROHC entities.

[0046] In the embodiments of the present disclosure, optionally, the connection setting information corresponding to the PDCP packet includes: (1) A correspondence between a particular connection and a particular ROHC entity for compression; (2) A correspondence between a specific connection and a specific ROHC entity for decompression may be included.

[0047] In an embodiment of the present disclosure, optionally, step 201 includes: If the connection corresponding to the PDCP packet is a first connection, the method may include employing a compression or decompression ROHC entity corresponding to the first connection.

[0048] In an embodiment of the present disclosure, optionally, step 201 includes: (1) establishing a plurality of compression or decompression ROHC entities according to configuration information of the plurality of compression or decompression ROHC entities; (2) Establishing a specific compression or decompression ROHC entity according to configuration information of the compression or decompression ROHC entity.

[0049] In an embodiment of the present disclosure, optionally, step 201 includes: After the mobility procedure is completed, the method may include determining a compression or decompression ROHC entity corresponding to the target connection according to the information of the mobility procedure completion.

[0050] In an embodiment of the present disclosure, optionally, after step 201, the method shown in FIG. 2 includes: (1) resetting the compression or decompression ROHC entity corresponding to the source connection; (2) Deleting the compression or decompression ROHC entity corresponding to the source connection.

[0051] In an embodiment of the present disclosure, optionally, the trigger event of the mobility procedure completion is: (1) The terminal receives a mobility procedure completion indication sent from the network side; and (2) The terminal sends a mobility procedure completion instruction to the network side; and (3) the random access procedure for the target connection is completed; and (4) An indication that processing of the data on the source connection has been completed is received by the terminal.

[0052] In an embodiment of the present disclosure, optionally, after step 201, the method shown in FIG. 2 includes: (1) determining a connection through which a PDCP packet is transmitted according to a PDCP identifier of the PDCP packet; (2) determining a connection over which the PDCP packets are transmitted in accordance with the compression ROHC entity that compressed the PDCP packets.

[0053] In an embodiment of the present disclosure, optionally, after step 201, the method shown in FIG. 2 includes: (1) compressing or decompressing the packet header of the PDCP packet by the modified compression or decompression ROHC entity when sending the ROHC entity modification information; (2) compressing or decompressing the packet header of the PDCP packet by the modified compression or decompression ROHC entity before sending the ROHC entity modification information; (3) After transmitting the ROHC entity modification information, compressing or decompressing the packet header of the PDCP packet by the modified compression or decompression ROHC entity.

[0054] In an embodiment of the present disclosure, optionally, after step 201, the method shown in FIG. 2 includes: (1) When changing the compression or decompression ROHC entity to be used, if the PDCP configuration information instructs the communication device to adopt the ROHC continuity function, not resetting the compression or decompression ROHC entity that was previously used; (2) before changing the compression or decompression ROHC entity to be used, if the PDCP configuration information instructs the communication device to adopt the ROHC continuity function, not resetting the compression or decompression ROHC entity that was previously used; (3) after changing the compression or decompression ROHC entity to be used, if the PDCP configuration information instructs the communication device to adopt the ROHC continuity function, not resetting the compression or decompression ROHC entity that was previously used.

[0055] In an embodiment of the present disclosure, optionally, after step 201, the method shown in FIG. 2 includes: (1) when changing the compression or decompression ROHC entity to be used, if the PDCP configuration information does not instruct the communication device to adopt the ROHC continuity function, resetting the compression or decompression ROHC entity that was previously used; (2) before changing the compression or decompression ROHC entity used, if the PDCP configuration information does not instruct the communication device to adopt the ROHC continuity function, resetting the previously used compression or decompression ROHC entity; (3) after changing the compression or decompression ROHC entity to be used, if the PDCP configuration information does not instruct the communication device to adopt the ROHC continuity function, resetting the compression or decompression ROHC entity that was previously used.

[0056] In an embodiment of the present disclosure, optionally, after step 201, the method shown in FIG. 2 includes: (1) When changing the compression or decompression ROHC entity to be used, resetting the compression or decompression ROHC entity that was previously used; (2) before changing the compression or decompression ROHC entity to be used, resetting the previously used compression or decompression ROHC entity; (3) After changing the compression or decompression ROHC entity to be used, resetting the compression or decompression ROHC entity that was previously used.

[0057] In an embodiment of the present disclosure, optionally, after step 201, the method shown in FIG. 2 includes: (1) When changing the compression or decompression ROHC entity to be used, the previously used compression or decompression ROHC entity is deleted; (2) before changing the compression or decompression ROHC entity to be used, delete the previously used compression or decompression ROHC entity; (3) After changing the compression or decompression ROHC entity to be used, deleting the compression or decompression ROHC entity that was previously used.

[0058] In an embodiment of the present disclosure, even if there are multiple compression or decompression ROHC entities working for one DRB (or PDCP) of the communication device on the network side, the communication device can realize the compression or decompression function of the packet header.

[0059] For a better understanding of the embodiments of the present disclosure, the PDCP transmitting end in the following embodiments may correspond to the PDCP transmitting end on the UE and the network side, respectively, and the PDCP receiving end may correspond to the PDCP receiving end on the UE and the network side, respectively.

[0060] Example 1.1: Multiple ROHC entities for compression or decompression are indicated by the packet header of a PDCP packet.

[0061] Step 1: The UE manages multiple ROHC entities for compression or decompression by using a packet header indication method (e.g., PDCP packet header indication information), which is configured by the network side or specified by a protocol.

[0062] Step 2: When the UE receives the configuration information of multiple compression or decompression ROHC entities of one PDCP entity, the UE establishes multiple compression ROHC entities for uplink transmission and multiple decompression ROHC entities for downlink reception.

[0063] For example, in the case of a DC handover procedure, if both the source connection and the target connection are configured with corresponding compression or decompression ROHC entities (e.g., compression or decompression ROHC1 and compression or decompression ROHC2) for the same PDCP entity, the UE establishes multiple compression ROHC entities for uplink transmission and multiple decompression ROHC entities for downlink reception.

[0064] Step 3.1: Depending on Step 2, the behavior of the PDCP receiving end is After the PDCP receiving end receives a PDCP packet (e.g., a PDCP data packet and / or a ROHC feedback packet), it employs a specific ROHC entity for compression or decompression to process the PDCP packet according to the ROHC entity indication information in the packet header of the PDCP protocol data unit (PDU) of the PDCP packet.

[0065] For example, when a PDCP receiving entity of a UE receives a PDCP data packet, if the packet header of the PDCP PDU of the PDCP data packet indicates the ROHC1 decompression method to be adopted for the PDCP data packet, the PDCP receiving entity of the UE will adopt the ROHC1 decompression method to decompress the packet header of the PDCP PDU.

[0066] Furthermore, for example, when a ROHC feedback packet is received by a PDCP receiving entity of a UE, if the packet header of a PDCP PDU of the ROHC feedback packet indicates that ROHC1 decompression should be adopted for the packet header of the PDCP PDU, the PDCP receiving entity of the UE will adopt ROHC1 decompression to process the packet header of the PDCP PDU.

[0067] Step 3.2: According to Step 1, the behavior of the PDCP transmitting end is When a PDCP transmitter employs a specific compression or decompression ROHC entity for compression (or transmits a ROHC feedback packet (e.g., "Control PDU for interspersed ROHC feedback")), the PDCP transmitter indicates the employed compression or decompression ROHC entity in the transmitted PDCP packet header.

[0068] For example, when a PDCP transmitting entity of a UE transmits data, if ROHC1 compression is used to compress the PDCP packet header of the data, the packet header of the PDCP PDU of the data indicates that ROHC1 compression has been used.

[0069] Furthermore, for example, when a ROHC feedback packet (e.g., "Control PDU for interspersed ROHC feedback") is transmitted by the PDCP transmitting entity of the UE, if the ROHC feedback packet uses compressed ROHC1, the packet header of the PDCP PDU of the ROHC feedback packet indicates that compressed ROHC1 has been used.

[0070] Additionally, the PDCP sender employs a compression or decompression ROHC entity corresponding to each connection for data packets sent to each connection.

[0071] Illustratively, according to the configuration information on the network side (e.g., the source connection adopts ROHC1 for compression or decompression, and the target connection adopts ROHC2 for compression or decompression), the PDCP transmitting end of the UE adopts ROHC1 for compression or decompression for data sent to the source connection, and adopts ROHC2 for compression or decompression for data sent to the target connection.

[0072] Additionally, in step 4, for a mobility procedure (e.g., handover or secondary cell group change (SCG) change), after the mobility procedure is completed, the UE's PDCP transmitting entity adopts the compression or decompression ROHC entity corresponding to the target connection (i.e., no longer adopts the compression or decompression ROHC entity corresponding to the source connection).

[0073] Additionally, the transmitting PDCP entity of the UE resets and / or deletes the compression or decompression ROHC entity corresponding to the source connection.

[0074] Here, the trigger event for completing the mobility procedure is: (1) A mobility procedure completion indication sent from the network side is received, for example, a setup message for deleting the source connection is sent from the network side; and (2) A mobility procedure completion indication is sent to the network side, for example, a source connection deletion indication message is sent from the UE to the network side; (3) the random access procedure for the target connection is completed; and (4) Processing of all data received by the PDCP transmitting entity for the source connection is complete (e.g., decompression is complete, decoding is complete, or transmission to upper layers is complete).

[0075] Example 1.2: Multiple compression or decompression ROHC entities are indicated by a PDCP identifier.

[0076] Step 1: The UE is configured by the network side or specified by a protocol to manage multiple compression or decompression ROHC entities by using a PDCP identifier (e.g., PDCP SN or COUNT) indication method.

[0077] Here, the PDCP identifier setting information includes: (1) a downlink PDCP packet identifier; and (2) an uplink PDCP packet identifier; and (3) A compression or decompression ROHC entity employed before (or after) the downlink or uplink PDCP packet identifier.

[0078] For example, the network side is configured to use ROHC1 for compression or decompression before a specified PDCP SN (for example, 100), and then adopt ROHC2 for compression or decompression thereafter.

[0079] Step 2: When the UE receives the configuration information of multiple compression or decompression ROHC entities of one PDCP entity, the UE establishes multiple compression ROHC entities for uplink transmission and multiple decompression ROHC entities for downlink reception.

[0080] For example, in the case of a DC handover procedure, if both the source connection and the target connection are configured with corresponding compression or decompression ROHC entities (e.g., compression or decompression ROHC1 and compression or decompression ROHC2) for the same PDCP entity, the UE establishes multiple compression ROHC entities for uplink transmission and multiple decompression ROHC entities for downlink reception.

[0081] Step 3.1: Depending on Step 2, the behavior of the PDCP receiving end is After the PDCP receiving end receives a PDCP packet (e.g., a PDCP data packet and / or a ROHC feedback packet), the UE employs a specific compression or decompression ROHC entity for processing according to the received PDCP packet identifier.

[0082] For example, when the PDCP receiving entity of the UE receives data, if the packet header of the PDCP PDU indicates that the PDCP SN of the PDCP data packet is the number before the configured PDCP SN, the PDCP receiving entity of the UE employs ROHC1 for compression or decompression to decompress the packet header of the PDCP PDU; otherwise, it employs ROHC2 for compression or decompression.

[0083] Further, for example, when a ROHC feedback packet is received by the PDCP receiving entity of the UE, if the PDCP SN of the PDCP packet received (or transmitted) before the ROHC feedback packet is a number before the configured PDCP SN number, the PDCP receiving entity of the UE employs ROHC1 for compression or decompression to process the packet header of the PDCP PDU; otherwise, it employs ROHC2 for compression or decompression.

[0084] Step 3.2: According to Step 1, the behavior of the PDCP transmitting end is When a PDCP packet (e.g., a PDCP data packet and / or a ROHC feedback packet) is sent by the PDCP sending end, the UE employs a specific ROHC entity for compression or decompression for processing according to the transmitted PDCP packet identifier.

[0085] For example, when the PDCP transmitting entity of the UE transmits data, if the PDCP SN of the PDCP data packet is a number previous to the configured PDCP SN, the PDCP receiving entity of the UE employs ROHC1 for compression or decompression to compress the packet header of the PDCP PDU; otherwise, it employs ROHC2 for compression or decompression.

[0086] Additionally, for a data packet to be transmitted to each connection, the PDCP transmitting end determines the connection to which the data packet is transmitted according to the PDCP identifier. For example, during a DC handover procedure, when the PDCP transmitting entity of the UE transmits data, if the PDCP SN of the data packet is the number before the configured PDCP SN number, the UE transmits the data packet via the source connection; otherwise, it transmits the data packet via the target connection.

[0087] Additionally, in step 4, for a mobility procedure (e.g., handover or SCG change), after the mobility procedure is completed, the UE's PDCP entity adopts the ROHC entity for compression or decompression corresponding to the target connection, i.e., no longer adopts the ROHC entity for compression or decompression corresponding to the source connection.

[0088] Additionally, the PDCP entity of the UE resets and / or deletes the compression or decompression ROHC entity corresponding to the source connection.

[0089] Here, the trigger event for completing the mobility procedure is: (1) A mobility procedure completion indication sent from the network side is received, for example, a setup message for deleting the source connection is sent from the network side; and (2) A mobility procedure completion indication is sent to the network side, for example, a source connection deletion indication message is sent from the UE to the network side; (3) the random access procedure for the target connection is completed; and (4) Processing of all data received by PDCP on the source connection has been completed (e.g., decompression has been completed, or decoding has been completed, or transmission to a higher layer has been completed).

[0090] Example 1.3: Selecting a compression or decompression ROHC entity from multiple compression or decompression ROHC entities according to the connection corresponding to the PDCP packet.

[0091] Step 1: The UE adopts a connection corresponding to PDCP packets to manage multiple ROHC entities for compression or decompression, which is configured by the network side or specified by a protocol.

[0092] Here, the connection setup information corresponding to the PDCP packet includes a specific compression or decompression ROHC entity corresponding to the specific connection.

[0093] For example, the network side is configured to adopt ROHC1 for decompression for received connection 1 data packets and ROHC1 for compression for transmitted connection 1 data packets.

[0094] Step 2: When the UE receives the configuration information of multiple compression or decompression ROHC entities of one PDCP entity, the UE establishes multiple compression ROHC entities for uplink transmission and multiple decompression ROHC entities for downlink reception.

[0095] For example, in the case of a DC handover procedure, if both the source connection and the target connection are configured with corresponding compression or decompression ROHC entities (e.g., compression or decompression ROHC1 and compression or decompression ROHC2) for the same PDCP entity, the UE will establish multiple compression ROHC entities for uplink transmission and multiple decompression ROHC entities for downlink reception.

[0096] Step 3.1: Depending on Step 2, the behavior of the PDCP receiving end is After the PDCP receiving end receives a PDCP packet (e.g., a PDCP data packet and / or a ROHC feedback packet), the UE processes the received PDCP packet by employing a specific compression or decompression ROHC entity according to the connection.

[0097] For example, when a PDCP receiving entity of a UE receives a PDCP data packet, if the PDCP data packet is from connection 1, the PDCP receiving entity of the UE employs ROHC1 for decompression to decompress the packet header of the PDCP PDU of the PDCP data packet.

[0098] Further, for example, upon receiving a ROHC feedback packet by the PDCP receiving entity of the UE, if the ROHC feedback packet is from connection 1, the PDCP receiving entity of the UE employs ROHC1 for decompression to process the PDCP PDU.

[0099] Step 3.2: According to Step 1, the behavior of the PDCP transmitting end is When the PDCP transmitting end transmits a PDCP packet (e.g., a PDCP data packet and / or a ROHC feedback packet), the UE employs a specific compression or decompression ROHC entity for processing according to the connection of the transmitted PDCP packet.

[0100] For example, when a PDCP transmitting entity of a UE transmits a PDCP data packet, if the PDCP data packet is transmitted via connection 1, the PDCP transmitting entity of the UE employs ROHC1 for compression to compress the PDCP PDU of the PDCP data packet.

[0101] Furthermore, for example, when a ROHC feedback packet is sent by the PDCP transmitting entity of the UE, if the ROHC feedback packet is a ROHC feedback packet for a received data packet of ROHC1, the PDCP transmitting entity of the UE employs ROHC1 for compression to process the packet header of the ROHC PDCP PDU, and transmits the ROHC feedback packet to the connection corresponding to ROHC1 for compression.

[0102] Additionally, for each PDCP packet sent to a connection, the PDCP sending end determines the connection to which the PDCP packet is sent according to the adopted compression or decompression ROHC entity.

[0103] For example, during a DC handover procedure, when a PDCP packet is transmitted by a PDCP transmitting entity of a UE, if ROHC1 is adopted for compression for the PDCP packet, the PDCP packet is transmitted via a connection corresponding to ROHC1 for compression.

[0104] Additionally, in step 4, for a mobility procedure (e.g., handover or SCG change), after the mobility procedure is completed, the UE's PDCP entity adopts the compression or decompression ROHC entity corresponding to the target connection (i.e., no longer adopts the compression or decompression ROHC entity corresponding to the source connection).

[0105] Additionally, the PDCP entity of the UE resets and / or deletes the compression or decompression ROHC entity corresponding to the source connection.

[0106] Here, the trigger event for completing the mobility procedure is: (1) A mobility procedure completion indication sent from the network side is received, for example, a setup message for deleting the source connection is sent from the network side; and (2) A mobility procedure completion indication is sent to the network side, for example, a source connection deletion indication message is sent from the UE to the network side; (3) the random access procedure for the target connection is completed; and (4) Processing of all data received by PDCP on the source connection has been completed (e.g., decompression has been completed, or decoding has been completed, or transmission to a higher layer has been completed).

[0107] Example 1.4: PDCP control packets change multiple ROHC entities for compression or decompression.

[0108] Step 1: The UE adopts the PDCP control packet method to manage multiple ROHC entities for compression or decompression, which is configured by the network side or specified by the protocol.

[0109] For example, after receiving a PDCP control packet, it determines the ROHC entity for compression or decompression to be employed thereafter according to the instruction information in the PDCP control packet.

[0110] Step 2: When the UE receives the configuration information of multiple compression or decompression ROHC entities of one PDCP entity, the UE establishes multiple compression ROHC entities for uplink transmission and multiple decompression ROHC entities for downlink reception.

[0111] For example, in the case of a DC handover procedure, if both the source connection and the target connection are configured with corresponding compression or decompression ROHC entities (e.g., compression or decompression ROHC1 and compression or decompression ROHC2) for the same PDCP entity, the UE will establish multiple compression ROHC entities for uplink transmission and multiple decompression ROHC entities for downlink reception.

[0112] Step 3: After receiving the ROHC entity modification information (eg, PDCP control packet) sent from the network side, the UE adopts the modified compression or decompression ROHC entity.

[0113] For example, if a PDCP entity in a UE receives a PDCP control packet indicating the compression or decompression ROHC entity that should be employed by that PDCP entity, that PDCP entity changes the compression or decompression ROHC entity that it uses.

[0114] Alternatively, the UE adopts the modified compression or decompression ROHC entity when (or before or after) sending the ROHC entity modification information to the network side.

[0115] For example, when (or before or after) a PDCP control packet is transmitted by one PDCP entity of a UE, if the PDCP control packet indicates a compression or decompression ROHC entity to be employed by that PDCP entity, that PDCP entity changes the compression or decompression ROHC entity it uses.

[0116] Additionally, the PDCP entity of the UE resets the compression or decompression ROHC entity when (or before or after) changing the compression or decompression ROHC entity used by it.

[0117] Additionally, when the PDCP entity of the UE changes the compression or decompression ROHC entity used by it (or before or after the change), it deletes the compression or decompression ROHC entity that was previously used.

[0118] Example 2.1: Changing one compression or decompression ROHC entity via PDCP control packets.

[0119] Step 1: The UE adopts the PDCP control packet method to manage one ROHC entity for compression or decompression, which is configured by the network side or specified by the protocol.

[0120] For example, after receiving a PDCP control packet, it determines the ROHC entity for compression or decompression to be employed thereafter according to the instruction information in the PDCP control packet.

[0121] Step 2: When the UE receives the configuration information of multiple compression or decompression ROHC entities of one PDCP entity, it first uses one specific compression or decompression ROHC entity.

[0122] For example, in the case of a DC handover procedure, if both the source connection and the target connection are configured with corresponding compression or decompression ROHC entities (e.g., compression or decompression ROHC1 and compression or decompression ROHC2) for the same PDCP entity, the UE will first adopt compression ROHC1 for uplink transmission and decompression ROHC1 for downlink reception.

[0123] Step 3: After receiving the ROHC entity modification information (eg, PDCP control packet) sent from the network side, the UE adopts (or establishes) the modified compression or decompression ROHC entity.

[0124] For example, if a PDCP entity in a UE receives a PDCP control packet indicating the compression or decompression ROHC entity that should be employed by the PDCP, the PDCP entity changes the compression or decompression ROHC entity that it uses.

[0125] Alternatively, the UE adopts (or establishes) the modified compression or decompression ROHC entity when (or before or after) transmitting compression or decompression ROHC entity modification information to the network side.

[0126] For example, when (or before or after) a PDCP control packet is transmitted by one PDCP entity of a UE, if the PDCP control packet indicates a compression or decompression ROHC entity to be employed by that PDCP entity, that PDCP entity changes the compression or decompression ROHC entity it uses.

[0127] Additionally, the PDCP entity of the UE resets the ROHC entity when (or before or after) changing the compression or decompression ROHC entity used by it.

[0128] Additionally, when the PDCP entity of the UE changes the compression or decompression ROHC entity used by it (or before or after the change), it deletes the previously used ROHC entity.

[0129] Additionally, when the PDCP entity of the UE changes the compression or decompression ROHC entity used by it (or before or after the change), if the ROHC continuity function (e.g., drb-ContinueROHC) is configured by the network side, the PDCP entity of the UE does not reset the compression or decompression ROHC entity.

[0130] Additionally, when the PDCP entity of the UE changes the ROHC entity used by it (or before or after the change), if the ROHC continuation function for compression or decompression (e.g., drb-ContinueROHC) is not configured by the network side, the PDCP entity of the UE resets the ROHC entity for compression or decompression.

[0131] Example 2.2: Changing one compression or decompression ROHC entity according to the PDCP identifier.

[0132] Step 1: The UE adopts the method of PDCP identifier (for example, PDCP SN or COUNT) to manage one compression or decompression ROHC entity, which is configured by the network side or specified by the protocol.

[0133] Here, the PDCP identifier setting information includes: (1) a downlink PDCP packet identifier; and (2) an uplink PDCP packet identifier; and (3) A compression or decompression ROHC entity employed before (or after) the PDCP packet identifier.

[0134] For example, the network side is configured to use ROHC1 for compression or decompression before a specified PDCP SN (for example, 100), and to adopt ROHC2 for compression or decompression thereafter.

[0135] Step 2: When the UE receives the configuration information of multiple compression or decompression ROHC entities of one PDCP entity, it first uses one specific compression or decompression ROHC entity.

[0136] For example, in the case of a DC handover procedure, if both the source connection and the target connection are configured with corresponding compression or decompression ROHC entities (e.g., compression or decompression ROHC1 and compression or decompression ROHC2) for the same PDCP entity, the UE will first adopt compression ROHC1 for uplink transmission and decompression ROHC1 for downlink reception.

[0137] Step 3: After receiving the corresponding PDCP identifier information sent from the network side, the UE adopts (or establishes) the modified compression or decompression ROHC entity.

[0138] For example, if the PDCP identifier received by one PDCP entity of the UE is a number before the configured PDCP SN number, the PDCP receiving entity of the UE adopts ROHC1 for decompression to process the PDCP PDU; otherwise, it adopts ROHC2 for decompression.

[0139] Or, the UE adopts (or establishes) a modified compression or decompression ROHC entity according to the corresponding PDCP identifier information sent to the network side.

[0140] For example, if the PDCP identifier sent by one PDCP entity of the UE is a number before the configured PDCP SN, the PDCP receiving entity of the UE will adopt ROHC1 for compression to process the PDCP PDU; otherwise, it will adopt ROHC2 for compression.

[0141] Additionally, when the PDCP entity of the UE changes the compression or decompression ROHC entity used by it (or before or after changing it), it resets the compression or decompression ROHC entity that was previously used.

[0142] Additionally, when the PDCP entity of the UE changes the compression or decompression ROHC entity used by it (or before or after the change), it deletes the compression or decompression ROHC entity that was previously used.

[0143] Additionally, when the PDCP entity of the UE changes the ROHC entity used by it (or before or after the change), if the ROHC continuity function (e.g., drb-ContinueROHC) is configured by the network side, the PDCP entity of the UE does not reset the compression or decompression ROHC entity that was previously used.

[0144] Additionally, when the PDCP entity of the UE changes the ROHC entity used by it (or before or after the change), if the ROHC continuity function (e.g., drb-ContinueROHC) is not configured by the network side, the PDCP entity of the UE resets the compression or decompression ROHC entity that was previously used.

[0145] Example 2.3: Changing one compression or decompression ROHC entity by changing the connection corresponding to the PDCP packet.

[0146] Step 1: The UE adopts a connection corresponding to a PDCP packet to manage one ROHC entity for compression or decompression, which is configured by the network side or specified by a protocol.

[0147] Here, the connection setup information corresponding to the PDCP packet includes a specific compression or decompression ROHC entity corresponding to the specific connection.

[0148] For example, the network side is configured to adopt ROHC1 for decompression for received connection 1 data packets and ROHC1 for compression for transmitted connection 1 data packets.

[0149] Step 2: When the UE receives the configuration information of multiple compression or decompression ROHC entities of one PDCP entity, it first uses one specific compression or decompression ROHC entity.

[0150] For example, in the case of a DC handover procedure, if both the source connection and the target connection are configured with corresponding compression or decompression ROHC entities (e.g., compression or decompression ROHC1 and compression or decompression ROHC2) for the same PDCP entity, the UE will first adopt compression ROHC1 for uplink transmission and decompression ROHC1 for downlink reception.

[0151] Step 3.1: Depending on Step 2, the behavior of the PDCP receiving end is The method includes: after the PDCP receiving end receives a PDCP packet (e.g., a PDCP data packet and / or a ROHC feedback packet), the UE adopts a specific ROHC entity for decompression according to the connection of the received PDCP packet for processing.

[0152] For example, when a PDCP receiving entity of a UE receives a PDCP data packet, if the PDCP data packet is from a source connection, the PDCP receiving entity of the UE employs a decompression ROHC1 corresponding to the source connection to decompress the packet header of the PDCP PDU of the PDCP data packet.

[0153] When the connection of a PDCP data packet received by a PDCP receiving entity of the UE is changed from the source connection to the target connection, the PDCP entity changes the previously used compression or decompression ROHC entity.

[0154] Furthermore, for example, when the PDCP receiving entity of the UE receives a ROHC feedback packet, if the ROHC feedback packet is from connection 1, the PDCP receiving entity of the UE employs decompression ROHC1 corresponding to connection 1 to decompress the packet header of the PDCP PDU.

[0155] Step 3.2: According to Step 1, the behavior of the PDCP transmitting end is When a PDCP packet (for example, a PDCP data packet and / or a ROHC feedback packet) is sent by the PDCP sending end, the UE employs a specific ROHC entity for compression according to the connection of the PDCP packet to be sent for processing.

[0156] For example, when a PDCP transmitting entity of a UE transmits a PDCP data packet, if the PDCP data packet is transmitted via a source connection, the PDCP transmitting entity of the UE employs compression ROHC1 corresponding to the source connection to compress the PDCP PDU of the PDCP data packet.

[0157] When the connection of a PDCP data packet transmitted by a PDCP transmitting entity of the UE is changed from a source connection to a target connection, the PDCP entity changes the previously used compression or decompression ROHC entity.

[0158] Furthermore, for example, when a ROHC feedback packet is transmitted by the PDCP transmitting entity of the UE, if the ROHC feedback packet is a ROHC feedback packet for a received data packet of compressed ROHC1, the PDCP transmitting entity of the UE employs compressed ROHC1 to process the packet header of the PDCP PDU, and transmits the ROHC feedback packet to the connection corresponding to compressed ROHC1.

[0159] Additionally, when the PDCP entity of the UE changes the compression or decompression ROHC entity used by it (or before or after changing it), it resets the compression or decompression ROHC entity that was previously used.

[0160] Additionally, when the PDCP entity of the UE changes the compression or decompression ROHC entity used by it (or before or after the change), it deletes the compression or decompression ROHC entity that was previously used.

[0161] Additionally, when the PDCP entity of the UE changes the ROHC entity used by it (or before or after changing it), it resets the ROHC entity used previously for compression or decompression.

[0162] Additionally, when the PDCP entity of the UE changes the compression or decompression ROHC entity it uses (or before or after the change), if the ROHC continuity function (e.g., drb-ContinueROHC) is configured by the network side, the PDCP entity of the UE does not reset the compression or decompression ROHC entity that was previously used.

[0163] Additionally, when the PDCP entity of the UE changes the compression or decompression ROHC entity it uses (or before or after the change), if the ROHC continuity function (e.g., drb-ContinueROHC) is not configured by the network side, the PDCP entity of the UE resets the compression or decompression ROHC entity that was previously used.

[0164] Additionally, for each PDCP packet sent to a connection, the PDCP sending end determines the connection to which the PDCP packet is sent according to the adopted ROHC entity for compression.

[0165] For example, during a DC handover procedure, when a PDCP packet is transmitted by a PDCP transmitting entity of a UE, if ROHC1 is adopted for compression for the PDCP packet, the PDCP packet is transmitted via a connection corresponding to ROHC1 for compression.

[0166] Additionally, in step 4, for a mobility procedure (e.g., handover or SCG change), after the mobility procedure is completed, the UE's PDCP entity adopts the compression or decompression ROHC entity corresponding to the target connection (i.e., no longer adopts the compression or decompression ROHC entity corresponding to the source connection).

[0167] Additionally, the PDCP entity of the UE resets and / or deletes the compression or decompression ROHC entity corresponding to the source connection.

[0168] Here, the trigger event for completing the mobility procedure is: (1) A mobility procedure completion indication sent from the network side is received, for example, a setup message for deleting the source connection is sent from the network side; and (2) A mobility procedure completion indication is sent to the network side, for example, a source connection deletion indication message is sent from the UE to the network side; (3) the random access procedure for the target connection is completed; and (4) Processing of all data received by PDCP on the source connection has been completed (e.g., decompression has been completed, or decoding has been completed, or transmission to a higher layer has been completed).

[0169] Embodiment 3: Whether one or multiple ROHC entities for compression or decompression are employed is controlled by setting and controlling the ROHC continuity function on the network side.

[0170] Step 1: The network side controls whether one PDCP entity of the UE establishes one or multiple ROHCs for compression or decompression at the same time by configuring the ROHC continuity function (e.g., drb-ContinueROHC).

[0171] Step 2: Depending on the configuration information in step 1, the behavior of the UE includes one of the following (1) to (3).

[0172] (1) If the PDCP configuration information indicates that the ROHC continuity function is to be adopted (i.e., an instruction that ROHC will not be reset), the PDCP entity can adopt one ROHC entity for compression or decompression at the same time and not adopt the function of changing the ROHC entity for compression or decompression in embodiment 2.1 or 2.2.

[0173] (2) If the PDCP configuration information does not indicate that the ROHC continuity function should be adopted and the UE has received configuration information for multiple compression or decompression ROHC entities for one PDCP entity, the UE establishes multiple compression ROHC entities for uplink transmission and multiple decompression ROHC entities for downlink reception.

[0174] (3) If the PDCP configuration information does not instruct the adoption of the ROHC continuity function (i.e., an instruction that ROHC will not be reset), the PDCP entity can adopt one ROHC entity for compression or decompression at the same time and adopt the function of changing the ROHC entity for compression or decompression in embodiment 2.1 or 2.2.

[0175] If the UE employs (or establishes) multiple ROHC entities for compression or decompression at the same time, the behavior of the UE is the same as in Examples 1.1, 1.2, 1.3 and 1.4 and will not be repeated here.

[0176] If the UE adopts (or establishes) one ROHC entity for compression or decompression at the same time, if it adopts the function of changing the ROHC entity for compression or decompression in Example 2.1 or 2.2, the behavior of the UE is the same as the function of changing the ROHC entity for compression or decompression in Example 2.1 or 2.2, and is not repeated here.

[0177] In the embodiments of the present disclosure, a communication device is further provided, and the principle by which the communication device solves the problem is similar to the processing method in the embodiments of the present disclosure, so for the implementation of the communication device, reference can be made to the implementation of the method, and the overlapping parts will not be repeatedly described.

[0178] Referring to FIG. 3 , an embodiment of the present disclosure further provides a communication device, for example a terminal or a network device, wherein the communication device 300 includes: A first determination module 301 for determining a compression or decompression ROHC entity according to first information; Here, the first information is one or more of: indication information in a packet header of a PDCP packet; information on completion of a mobility procedure; a PDCP identifier of the PDCP packet; a connection corresponding to the PDCP packet; indication information in a PDCP control packet; PDCP configuration information; and configuration information of a compression or decompression ROHC entity.

[0179] In an embodiment of the present disclosure, optionally, the PDCP configuration information instructs the communication device to adopt a ROHC continuity function, and the PDCP entity of the communication device includes one ROHC entity for compression or decompression; or The PDCP configuration information does not instruct the communication device to adopt the ROHC continuity function, and the PDCP entity of the communication device includes multiple ROHC entities for compression or decompression.

[0180] In an embodiment of the present disclosure, optionally, the indication information in the PDCP control packet is: causing the communication device to modify a compression or decompression ROHC entity; not allowing the communication device to modify compression or decompression ROHC entities; and causing the communication device to delete the previous compression or decompression ROHC entity and establish a new compression or decompression ROHC entity.

[0181] In an embodiment of the present disclosure, optionally, the communication device 300 further includes a second determination module for determining the corresponding first information according to a specific instruction manner; Here, the specific instruction method is: An instruction in the packet header of the PDCP packet, An instruction based on the setting information of the PDCP identifier of the PDCP packet; an indication by the configuration information of the connection corresponding to the PDCP packet; and an instruction by a PDCP control packet.

[0182] In the embodiment of the present disclosure, optionally, the specific indication manner is set by the network side or defined by a protocol.

[0183] In the embodiments of the present disclosure, optionally, the PDCP identifier configuration information includes: a specified PDCP packet identifier; and a compression or decompression ROHC entity employed before the specified PDCP packet identifier; and a ROHC entity for compression or decompression employed after the specified PDCP packet identifier.

[0184] In an embodiment of the present disclosure, optionally, the first determining module 301: If the PDCP identifier of the PDCP packet is before a specified PDCP identifier, employing a corresponding ROHC entity for compression or decompression; If the PDCP identifier of the PDCP packet is after the specified PDCP identifier, it is further used to perform one of the following: employing the corresponding compression or decompression ROHC entity.

[0185] In an embodiment of the present disclosure, optionally, the first determining module 301: employing a first compression or decompression ROHC entity if the PDCP identifier of the PDCP packet is before a specified PDCP identifier; if the PDCP identifier of the PDCP packet is after a specified PDCP identifier, deleting the first compression or decompression ROHC entity and establishing and adopting a new compression or decompression ROHC entity; Here, the first compression or decompression ROHC entity is one specific compression or decompression ROHC entity established by the communication device according to configuration information of multiple compression or decompression ROHC entities.

[0186] In the embodiments of the present disclosure, optionally, the connection setting information corresponding to the PDCP packet includes: A correspondence between a particular connection and a particular ROHC entity for compression; It includes one or more of: a specific connection and a correspondence with a specific ROHC entity for decompression.

[0187] In an embodiment of the present disclosure, optionally, the first determining module 301: If the connection corresponding to the PDCP packet is a first connection, it is further used to employ a compression or decompression ROHC entity corresponding to the first connection.

[0188] In an embodiment of the present disclosure, optionally, the first determining module 301: establishing a plurality of compression or decompression ROHC entities according to configuration information of the plurality of compression or decompression ROHC entities; and establishing a specific compression or decompression ROHC entity according to the configuration information of the compression or decompression ROHC entity.

[0189] In the embodiment of the present disclosure, optionally, the first determination module 301 is further used, after the mobility procedure is completed, to determine a compression or decompression ROHC entity corresponding to the target connection according to the information of the mobility procedure completion.

[0190] In an embodiment of the present disclosure, optionally, the communication device 300 further includes a first processing module, and the first processing module is resetting the compression or decompression ROHC entity corresponding to the source connection; and deleting the compression or decompression ROHC entity corresponding to the source connection.

[0191] In an embodiment of the present disclosure, optionally, the trigger event of the mobility procedure completion is: The terminal receives a mobility procedure completion indication sent from the network side; and The terminal has transmitted to the network side an instruction to complete the mobility procedure; The random access procedure for the target connection has been completed, and and an indication that processing of the data on the source connection has been completed is received by the terminal.

[0192] In an embodiment of the present disclosure, optionally, the communication device 300 further includes a second processing module, which is determining a connection through which the PDCP packet is transmitted according to a PDCP identifier of the PDCP packet; determining a connection over which the PDCP packets are transmitted in accordance with the compression ROHC entity that compressed the PDCP packets.

[0193] In an embodiment of the present disclosure, optionally, the communication device 300 further includes a third processing module, which is When sending the ROHC entity modification information, compressing or decompressing the packet header of the PDCP packet by the modified compression or decompression ROHC entity; compressing or decompressing packet headers of PDCP packets by the modified compression or decompression ROHC entity before transmitting the ROHC entity modification information; and compressing or decompressing the packet header of the PDCP packet by the modified compression or decompression ROHC entity after transmitting the ROHC entity modification information.

[0194] In an embodiment of the present disclosure, optionally, the communication device 300 further includes a fourth processing module, which is When changing the compression or decompression ROHC entity to be used, if the PDCP configuration information instructs the communication device to adopt a ROHC continuity function, not resetting the compression or decompression ROHC entity that was previously used; before changing the compression or decompression ROHC entity used, if the PDCP configuration information instructs the communication device to adopt a ROHC continuity function, not resetting the compression or decompression ROHC entity previously used; and after changing the compression or decompression ROHC entity used, if the PDCP configuration information instructs the communication device to adopt the ROHC continuity function, not resetting the compression or decompression ROHC entity that was previously used.

[0195] In an embodiment of the present disclosure, optionally, the communication device 300 further includes a fifth processing module, which is When changing the compression or decompression ROHC entity to be used, if the PDCP configuration information does not instruct the communication device to adopt a ROHC continuity function, resetting the compression or decompression ROHC entity that was previously used; before changing the compression or decompression ROHC entity used, if the PDCP configuration information does not instruct the communication device to employ a ROHC continuity function, resetting the previously used compression or decompression ROHC entity; and resetting the previously used compression or decompression ROHC entity if the PDCP configuration information does not instruct the communication device to adopt the ROHC continuity function after changing the compression or decompression ROHC entity used.

[0196] In an embodiment of the present disclosure, optionally, the communication device 300 further includes a sixth processing module, which is resetting the previously used compression or decompression ROHC entity when changing the compression or decompression ROHC entity used; resetting the previously used compression or decompression ROHC entity before changing the compression or decompression ROHC entity used; and resetting the previously used compression or decompression ROHC entity after changing the compression or decompression ROHC entity used.

[0197] In an embodiment of the present disclosure, optionally, the communication device 300 further includes a seventh processing module, which is When changing the compression or decompression ROHC entity to be used, deleting the previously used compression or decompression ROHC entity; before changing the compression or decompression ROHC entity used, deleting the previously used compression or decompression ROHC entity; and, after changing the compression or decompression ROHC entity used, deleting the compression or decompression ROHC entity that was previously used.

[0198] The communication device according to the embodiment of the present disclosure can implement the above method embodiment, and the realization principles and technical effects thereof are similar, so this embodiment will not be described again here.

[0199] 4, which is a structural diagram of a communication device applied to an embodiment of the present disclosure. As shown in FIG. 4, the communication device 400 includes a processor 401, a transceiver 402, a memory 403, and a bus interface.

[0200] In one embodiment of the present disclosure, the communication device 400 further includes a program stored in the memory 403 and operable on the processor 401, and when the program is executed by the processor 401, it realizes determining a compression or decompression ROHC entity according to first information, where the first information is one or more of: indication information in a packet header of a PDCP packet; information of mobility procedure completion; a PDCP identifier of the PDCP packet; a connection corresponding to the PDCP packet; indication information in a PDCP control packet; PDCP configuration information; and configuration information of the compression or decompression ROHC entity.

[0201] In Figure 4, the bus architecture may include any number of interconnected buses and bridges, specifically connecting various circuits to one or more processors, such as processor 401, and memory, such as memory 403. The bus architecture may also connect various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be further described herein. The bus interface provides an interface. The transceiver 402 may be multiple elements, i.e., may include a transmitter and a receiver, and provides a means for communicating with various other devices over a transmission medium.

[0202] The processor 401 is responsible for managing the bus architecture and general processing, and the memory 403 can store data used by the processor 401 when performing operations.

[0203] The communication device according to the embodiment of the present disclosure can implement the above method embodiment, and the realization principles and technical effects thereof are similar, so this embodiment will not be described again here.

[0204] The steps of the methods or algorithms described in connection with the disclosure of this disclosure may be implemented in hardware or by a processor executing software commands. The software commands may comprise corresponding software modules. The software modules may be stored in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, a hard disk, a portable hard disk, a read-only optical disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, such that the processor can read information from and write information to the storage medium. Of course, the storage medium may be an integral part of the processor. The processor and the storage medium may be incorporated into an ASIC. Alternatively, the ASIC may be incorporated into the core network interface device. Of course, the processor and the storage medium may be located in the core network interface device as separate components.

[0205] Those skilled in the art will recognize that in one or more of the above examples, the functions described in this disclosure can be implemented by hardware, software, firmware, or any combination thereof. If implemented in software, these functions are stored on a computer-readable medium or transmitted as one or more commands or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media. Communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media are any available media that can be accessed by a general-purpose or special-purpose computer.

[0206] Those skilled in the art may recognize that the units and algorithm steps in each example described in conjunction with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are realized by hardware or software depends on the specific application and design constraint requirements of the technical solution. Those skilled in the art may use different methods to realize the described functions for each specific application, but such implementation should not be considered outside the scope of the present disclosure.

[0207] For convenience and brevity of explanation, those skilled in the art will clearly understand that the specific operating procedures of the systems, devices and units described above can be referred to the corresponding procedures in the above method embodiments, and will not be repeated here.

[0208] It should be understood that the disclosed devices and methods in the embodiments of the present application may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is merely a division based on logical functions, and other division methods are possible in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented. Furthermore, the mutual couplings, direct couplings, or communication connections shown or described may be implemented using several interfaces. Indirect couplings or communication connections between devices or units may be electronic, mechanical, or other forms.

[0209] The units described as separate components may or may not be physically separated, and the components described as units may or may not be physical units, and may be located in one place or distributed across multiple network units. To achieve the objectives of the technical solution of this embodiment, some or all of the units may be selected according to actual needs.

[0210] Furthermore, each functional unit in each embodiment of the present disclosure may be integrated into a single processing unit, each unit may exist physically alone, and further, two or more units may be integrated into a single unit.

[0211] The above functions may be realized in the form of a software functional unit and stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, an essential part of the technical solution of the present disclosure or a part that contributes to the related art may be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several commands that cause a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in each embodiment of the present disclosure. The above storage medium includes any medium that can store program code, such as a USB flash drive, a portable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0212] As can be understood by those skilled in the art, all or part of the steps of the methods according to the above embodiments may be realized by controlling related hardware using a computer program, and the program may be stored in a computer-readable storage medium, which may include the steps of the above method embodiments when executed. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), etc.

[0213] As can be appreciated, the embodiments described in the embodiments of the present disclosure can be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof. For a hardware implementation, the processing unit can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units, or a combination thereof for performing the functions described in the present disclosure.

[0214] For a software implementation, the techniques described in the embodiments of the present disclosure may be implemented with modules (e.g., procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure. The software code may be stored in a memory and executed by a processor. The memory may be within the processor or external to the processor.

[0215] Although the specific embodiments described above have further detailed the objectives, technical solutions and beneficial effects of the present disclosure, the above descriptions are merely specific embodiments of the present disclosure and are not intended to limit the scope of protection of the present disclosure. Any modifications, equivalent substitutions and improvements made based on the technical solutions of the present disclosure should all be included in the scope of protection of the present disclosure.

[0216] Those skilled in the art will appreciate that embodiments of the present disclosure may be provided as a method, a system, or a computer program product. Accordingly, embodiments of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, embodiments of the present disclosure may take the form of a computer program product embodied in one or more computer-usable storage media (including, but not limited to, magnetic disk memory, compact disc read-only memory (CD-ROM), optical memory, etc.) containing computer-usable program code.

[0217] The embodiments of the present disclosure are described with reference to flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and combinations of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program commands. These computer program commands are provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to form an apparatus, and the commands executed by the processor of the computer or other programmable data processing device form an apparatus for implementing the functions specified in one or more flows in the flowcharts and / or one or more blocks in the block diagrams.

[0218] These computer program instructions may be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, with the instructions stored in the computer-readable memory forming an article of manufacture that includes a command apparatus that implements the functions specified in one or more flows of the flowcharts and / or one or more blocks of the block diagrams.

[0219] These computer program instructions may be loaded into a computer or other programmable data processing device and cause the computer or other programmable device to execute a series of operational steps to form a computer-implemented process, the commands executed on the computer or other programmable device providing steps for implementing the functions specified in one or more flows of the flowcharts and / or one or more blocks of the block diagrams.

[0220] Obviously, those skilled in the art can make various modifications and variations to the embodiments of the present disclosure without departing from the spirit and scope of the present disclosure. If these modifications and variations of the embodiments of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure also includes these modifications and variations.

Claims

1. A processing method performed by a communication device, comprising: When the communication device has a connection for data transmission and reception with both a source node and a target node while moving, determining a Robust Header Compression (ROHC) entity for compression or decompression according to the first information; wherein the first information is a connection corresponding to a PDCP packet; determining a compression or decompression ROHC entity according to the first information includes, if a connection corresponding to the PDCP packet is a first connection, employing a compression or decompression ROHC entity corresponding to the first connection; the first connection is a source connection, or the first connection is a target connection; A processing method in which, for the same PDCP entity, the source connection and the target connection are each configured with a corresponding compression or decompression ROHC entity.

2. before determining a compression or decompression ROHC entity according to said first information; The method comprises: Further comprising determining the corresponding first information according to a specific instruction manner; Here, the specific instruction method is: An instruction based on the connection setting information corresponding to the PDCP packet; The method of claim 1 , comprising:

3. The PDCP entity of the communication device includes a plurality of ROHC entities for compression or decompression, and determining the ROHC entity for compression or decompression according to the first information includes: If the PDCP SN of the PDCP packet is before the specified PDCP SN, employ the corresponding ROHC entity for compression or decompression. The method of claim 1 , comprising:

4. 2. The method of claim 1, wherein the PDCP entity of the communication device includes a plurality of compression or decompression ROHC entities, and determining the compression or decompression ROHC entity according to the first information includes employing a corresponding compression or decompression ROHC entity if a PDCP SN of the PDCP packet is after a specified PDCP SN.

5. The PDCP entity of the communication device includes one ROHC entity for compression or decompression, and determining the ROHC entity for compression or decompression according to the first information includes: If the PDCP SN of the PDCP packet is before a specified PDCP SN, employing a first compression or decompression ROHC entity; if the PDCP SN of the PDCP packet is after a specified PDCP SN, deleting the first compression or decompression ROHC entity and establishing and employing a new compression or decompression ROHC entity; 2. The method of claim 1, wherein the first compression or decompression ROHC entity is one specific compression or decompression ROHC entity established by the communication device according to configuration information of multiple compression or decompression ROHC entities.

6. The connection setting information corresponding to the PDCP packet includes: A correspondence between a particular connection and a particular ROHC entity for compression; The method of claim 2 , wherein the information includes one or more of: a specific connection; and a correspondence with a specific ROHC entity for decompression.

7. determining a compression or decompression ROHC entity according to the first information, establishing a plurality of compression or decompression ROHC entities according to configuration information of the plurality of compression or decompression ROHC entities; establishing one compression or decompression ROHC entity according to configuration information of the one compression or decompression ROHC entity.

8. determining a compression or decompression ROHC entity according to the first information, The method of claim 1 , further comprising: after a mobility procedure is completed, determining a compression or decompression ROHC entity corresponding to a target connection according to information of the mobility procedure completion.

9. After determining a compression or decompression ROHC entity corresponding to the target connection, the method further comprises: resetting a compression or decompression ROHC entity corresponding to the source connection; and deleting a compression or decompression ROHC entity corresponding to the source connection.

10. After determining a compression or decompression ROHC entity according to the first information, The method comprises: determining a connection through which the PDCP packet is transmitted according to the PDCP SN of the PDCP packet; determining a connection through which the PDCP packet is transmitted according to a compression ROHC entity that compressed the PDCP packet; The PDCP SN of the PDCP packet includes a PDCP SN; determining a connection through which the PDCP packet is transmitted according to a PDCP SN of the PDCP packet; If the PDCP SN is a number before the configured PDCP SN number, determining the source connection as the connection from which the PDCP packet is sent; and If the PDCP SN is a number subsequent to a configured PDCP SN number, determining the target connection as the connection through which the PDCP packet is transmitted; determining a connection over which the PDCP packet is transmitted according to a compression ROHC entity that compressed the PDCP packet, determining a connection corresponding to a compression ROHC entity that compressed the PDCP packet as a connection through which the PDCP packet is transmitted; The method of claim 1.

11. After determining a compression or decompression ROHC entity according to the first information, The method comprises: When sending the ROHC entity modification information, compressing or decompressing the packet header of the PDCP packet by the modified compression or decompression ROHC entity; resetting the previously used compression or decompression ROHC entity when changing the compression or decompression ROHC entity used; Or, When changing the compression or decompression ROHC entity to be used, deleting the previously used compression or decompression ROHC entity; The method of claim 1 further comprising:

12. After determining a compression or decompression ROHC entity according to the first information, The method comprises: compressing or decompressing packet headers of PDCP packets by the modified compression or decompression ROHC entity before sending the ROHC entity modification information; resetting the previously used compression or decompression ROHC entity before changing the compression or decompression ROHC entity used; Or, Before changing the compression or decompression ROHC entity to be used, the previously used compression or decompression ROHC entity must be deleted; The method of claim 1 further comprising:

13. After determining a compression or decompression ROHC entity according to the first information, The method comprises: After sending the ROHC entity modification information, compressing or decompressing the packet header of the PDCP packet by the modified compression or decompression ROHC entity; resetting the previously used compression or decompression ROHC entity after changing the compression or decompression ROHC entity used; Or, After changing the compression or decompression ROHC entity used, deleting the previously used compression or decompression ROHC entity; The method of claim 1 further comprising:

14. A communication device, a determining module for determining a compression or decompression robust header compression ROHC entity according to the first information when the communication device has a connection for data transmission and reception with both a source node and a target node during movement; wherein the first information is a connection corresponding to a PDCP packet; The determination module: If the connection corresponding to the PDCP packet is a first connection, it is further used to employ a compression or decompression ROHC entity corresponding to the first connection; the first connection is a source connection, or the first connection is a target connection; For the same PDCP entity, the source connection and the target connection are each configured with a corresponding compression or decompression ROHC entity; Communication equipment.

15. A communication device comprising a processor, a memory, and a program stored in the memory and operable on the processor, wherein when the program is executed by the processor, the processing method described in any one of claims 1 to 13 is realized.

16. A computer-readable storage medium storing a computer program, the computer program implementing the processing method according to any one of claims 1 to 13 when executed by a processor.

Images