JP2022519554A - Processing method and communication equipment - Google Patents

Abstract

The embodiments of the present disclosure provide processing methods and communication devices, the method comprising determining a ROHC entity for compression or decompression according to the first information, wherein the first information is of a PDCP packet. Instruction information in the packet header, mobility procedure completion information, PDCP identifier of the PDCP packet, connection corresponding to the PDCP packet, instruction information in the PDCP control packet, PDCP setting information, and ROHC entity for compression or decompression. It is any one of the setting information of.

Description

(Mutual reference of related applications)
The present application claims the priority of Chinese Patent Application No. 201910093599.0 filed in China on January 30, 2019, the entire contents of which are incorporated herein by reference.
The embodiments of the present disclosure relate to the technical field of communication, and specifically to processing methods and communication equipment.

On the network side, a robust header compression ROHC for compression (or decompression) that works for one data wireless bearer DRB (Data Radio Bearer) (or packet data convergence protocol PDCP (Packet Data Convergence Protocol)) of the terminal. (Robust Header Compression) When there are a plurality of entities, how to realize compression or decompression of packet headers on the terminal side and the network side is an urgent issue to be solved.

One of the objects of the embodiments of the present disclosure is to provide a processing method and a communication device for solving the problem of compression or decompression of packet headers on the terminal side and the network side.

According to the first aspect of the embodiment of the present disclosure, it is a processing method applied to a communication device.
Including determining the Robust Header Compression ROHC (Robust Header Compression) entity for compression or decompression according to the first information.
Here, the first information includes instruction information in the packet header of the packet data convergence protocol PDCP (Packet Data Convergence Protocol) packet, information on the completion of the mobility procedure, the PDCP identifier of the PDCP packet, and the connection corresponding to the PDCP packet. And, the processing method which is one or more of the instruction information in the PDCP control packet, the PDCP setting information, and the setting information of the ROHC entity for compression or decompression is provided.

According to the second aspect of the embodiment of the present disclosure, it is a communication device.
Contains a decompression module for decompressing robust header compression ROHC entities for compression or decompression according to the first information.
Here, the first information includes instruction information in the packet header of the PDCP packet, information on the completion of the mobility procedure, the PDCP identifier of the PDCP packet, the connection corresponding to the PDCP packet, and the instruction information in the PDCP control packet. , The communication device which is one or more of the PDCP setting information and the setting information of the ROHC entity for compression or decompression is further provided.

According to the third aspect of the embodiments of the present disclosure, the processor, the memory, and the program stored in the memory and capable of operating on the processor are included, and when the program is executed by the processor, the above is described. Further provided are communication devices that realize the described processing method.

According to the fourth aspect of the embodiment of the present disclosure, it is a computer-readable storage medium that stores a computer program, and when the computer program is executed by a processor, the processing method described above is realized. It also provides a computer-readable storage medium.

In the embodiments of the present disclosure, even if there are a plurality of compression or decompression ROHC entities working for one DRB (or PDCP) of the terminal on the network side, the terminal side and the network side , The function of compressing or decompressing the packet header can be realized.

Reading the detailed description of the optional embodiments below will reveal a variety of other advantages and benefits to those of skill in the art. The drawings are for illustrative purposes only and should not be considered a limitation of the present disclosure. Further, throughout the drawings, the same members are designated by the same reference numerals.

It is the architecture schematic diagram of the wireless communication system which concerns on embodiment of this disclosure. It is a flowchart of the processing method which concerns on embodiment of this disclosure. It is one of the structural diagrams of the communication equipment according to the embodiment of this disclosure. FIG. 2 is a structural diagram of a communication device according to an embodiment of the present disclosure.

Hereinafter, the technical proposals 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 clearly, the illustrated embodiments are a part of the embodiments of the present disclosure. And not all examples. All other examples obtained by one of ordinary skill in the art without creative labor based on the examples in this disclosure shall be within the scope of this disclosure.

The term "contains" and any variation thereof in the specification and claims of the present application covers non-exclusive inclusion, eg, procedures, methods, systems, products or products comprising a series of steps or units. Equipment is not limited to including only those steps or units that are explicitly listed, but is specific to other steps or units that are not explicitly listed, or to these procedures, methods, products or equipment. Other steps or units may be included. In addition, "and / or" used in the specification and claims represents at least one of the connection objects, for example, "A and / or B" means only A. It includes three cases: existing, only B exists, and both A and B exist.

In the embodiments of the present disclosure, terms such as "exemplary" or "for example" are intended to illustrate or explain by way of example. In the embodiments of the present disclosure, any embodiment or design proposal described in terms such as "exemplary" or "eg" is more suitable or more advantageous than other examples or design proposals. Must not be construed as having. Appropriately, terms such as "exemplary" or "eg" are used to indicate a relevant concept in a concrete form.

In order to make it easier to understand the technical proposals of the examples of the present disclosure, some technical points are introduced below.

1. Introduction of robust header compression or robust header compression ROHC (Robust Header Compression).
In the new Radio NR (New Radio) system of Long Term Evolution (LTE) or 5th Generation Mobile Communication 5G (5th-generation), the network side is within the Packet Data Convergence Protocol (PDCP) entity. It is possible to set the ROHC function. The ROHC function includes up to one ROHC compression (eg, corresponding uplink data transmission on the terminal side) entity (or module, or protocol layer, or context) and up to one ROHC decompression (eg, in a PDCP entity). , Corresponding downlink data reception on the terminal side) entity (or module, or protocol layer, or context). The ROHC entity can compress and decompress the packet headers of upper layer data packets (eg, transmission control protocol TCP (Transmission Control Protocol) / Internet Protocol IP (Internet Protocol)), while the ROHC decompression entity It is possible to send feedback information about the decompression status to the other ROHC compression entity.

During the handover procedure, the network side can set whether the ROHC entity of the PDCP entity needs to be reset (ie, indicate through DRB ROHC continuous (drb-Continue ROHC) signaling).

For example, if the network side still wants the terminal to adopt the pre-handover ROHC entity during the handover procedure, it can set the drb-Continue ROHC in the terminal so that the terminal does not reset its own ROHC and pre-handover. Will continue to use the ROHC entity of.

2. Introduction of dual connection DC (Dual connection) handover.
Since it is necessary to satisfy the interruption delay of the mobility procedure of 0 ms in the 5G system, it is necessary for the terminal to secure a connection for data transmission / reception on both the source node and the target node during the movement. Data connections must be maintained on both the source and target nodes. The corresponding source node and target node on the network side have independent ROHC compression or decompression entities.

The techniques described herein are not limited to 5G systems and subsequent evolutionary communication systems, as well as LTE / LTE evolved LTE-A (LTE-Advanced) systems, but various radio communication systems, such as code division multiple access. CDMA (Code Division Multiple Access), Time Division Multiple Access TDMA (Time Division Multiple Access), Frequency Division Multiple Access FDMA (Frequency Division Multiple Access Frequency Division Multiple Access Multiple Access Multiple Access Multiple Access Multiple Access Multiple Access Multiple Access It can also be used for multiple connection SC-FDMA (Single-carrier Frequency-Division Multiple Access) and other systems.

The terms "system" and "network" are often used interchangeably. The CDMA system can realize radio technology such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). UTRA includes wideband CDMA (Wideband Code Division Multiple Access, WCDMA®) and other CDMA variants. The TDMA system can realize radio technology such as Global System for Mobile Communication (GSM), for example. OFDMA systems include, for example, Ultra Mobile Broadband UMB (Ultra Mobile Broadband), Evolved UTRA (Evolution-UTRA, E-UTRA), IEEE 802.11 (Wireless Fidelity Wi-Fi), and IEEE 802.16 Micro. Global interoperability of wave access It is possible to realize radio technologies such as WiMAX (World Interoperability for Broadwave Access), IEEE 802.120, and Flash-OFDM. UTRA and E-UTRA are part of the Universal Mobile Telecommunications Systems System (UMTS). LTE and more advanced LTE (eg LTE-A) are new UMTS versions using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in the literature from an organization named "3rd Generation Partnership Project" 3GPP (3rd Generation Partnership Project). CDMA2000 and UMB are described in the literature from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used with the above system and radio techniques, as well as with other system and radio techniques.

Hereinafter, examples of the present disclosure will be introduced together with the drawings. The processing methods and devices according to the embodiments of the present disclosure are applicable to wireless communication systems. With reference to FIG. 1, the figure is a schematic architecture diagram 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 described as a user device UE (User Equipment) 12, and the UE 12 is described as a user device UE (User Equipment) 12. Communication (signaling transmission or data transmission) with the first network device 10 and the second network device 11 is possible. In an actual application, the connection between the above devices may be a wireless connection, but in order to make it easier to intuitively show the connection relationship between the devices, FIG. 1 schematically shows them using solid lines. ing. It should be explained that the communication system may include a plurality of UEs 12, and the first network device 10 and the second network device 11 can communicate with the plurality of UEs 12.

The terminals according to the embodiments of the present disclosure include a mobile phone, a tablet PC, a notebook PC, an ultra-mobile personal computer UMPC (Ultra-Mobile Personal Computer), a netbook or a personal digital assistant PDA (Personal Digital Assistant), and a mobile Internet device MID (Mobile). It may be an Internet device), a wearable device (Wearable Device), an in-vehicle device, or the like.

The first network device 10 and the second network device 11 according to the embodiment of the present disclosure may be a base station, and the base station may be a commonly used base station or an evolved base. It may be a station eNB (evolved node base station), and may be a network device in a 5G system (for example, a next-generation base station gNB (next generation node base station) or a transmission / reception point TRP (transmission and reception point)). It may be a device.

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

With reference to FIG. 2, the embodiments of the present disclosure further provide a processing method, wherein the execution subject of the method may be a communication device, for example, a terminal or a network device, the method of which is step 201. including.

Step 201: Determine the ROHC entity for compression or decompression according to the first information.
Here, the first information includes instruction information in the packet header of the PDCP packet, information on the completion of the mobility procedure, the PDCP identifier of the PDCP packet, the connection corresponding to the PDCP packet, and the instruction information in the PDCP control packet. , PDCP setting information and setting information of ROHC entity for compression or decompression may be one or more.

It should be explained that the PDCP packet may be a PDCP data packet and / or a ROHC feedback packet.

If the communication device has multiple ROHC entities for compression or decompression, exemplary
(1.1) Add instruction information to indicate the ROHC entity to be used in the PDCP packet header.
(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. , Communication equipment adopts ROHC entity 2.
(1.3) The ROHC entity 1 related to the connection 1 is adopted for the PDCP packet from the connection 1, and the ROHC entity 2 related to the connection 2 is adopted for the PDCP packet from the connection 2.
(1.4) The instruction information in the PDCP control packet indicates whether to change the ROHC entity used by the communication device.

If the communication device has one ROHC entity, exemplary
(2.1) The instruction information in the PDCP control packet instructs the communication device to delete the previous ROHC entity (former ROHC entity) and establish a new ROHC entity.
(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. ROHC Entity 2 is established and adopted.

Illustratively, when a communication device employs the ROHC Continue function, the communication device employs one compression or decompression ROHC entity, otherwise the communication device adopts a compression or decompression ROHC. To adopt multiple. As can be understood, when the communication device employs one ROHC entity for compression or decompression, any of the methods described in (2.1) to (2.2) above can be applied. When the communication device employs a plurality of ROHC entities for compression or decompression, any of the methods described in (1.1) to (1.4) above can be applied.

In the embodiment of the present disclosure, the PDCP setting information selectively indicates that the communication device adopts the ROHC continuous function, and one PDCP entity of the communication device is a compression or decompression ROHC entity. You may include one.

In the embodiments of the present disclosure, selectively, the PDCP setting information does not indicate that the communication device adopts the ROHC continuous function, and one PDCP entity of the communication device is a compression or decompression ROHC entity. You may include more than one.

In the embodiments of the present disclosure, selectively, the instruction information in the PDCP control packet is
(1) Making a communication device change the ROHC entity for compression or decompression,
(2) Do not allow communication equipment to change the ROHC entity for compression or decompression.
(3) It may instruct at least one of having a communication device delete the previous compression or decompression ROHC entity and establishing a new compression or decompression ROHC entity.

In the embodiments of the present disclosure, selectively, prior to step 201, the method shown in FIG.
It may further include establishing the corresponding first information according to a particular instruction scheme.
Here, the specific instruction method is
(1) Instructions from the packet header of the PDCP packet and
(2) Instructions based on the PDCP identifier setting information of the PDCP packet,
(3) Instructions based on the connection setting information corresponding to the PDCP packet,
(4) One or more of the instructions by the PDCP control packet may be included.

In the embodiments of the present disclosure, optionally, the particular instruction scheme may be set by the network side or specified by a protocol.

In the embodiment of the present disclosure, selectively, the setting information of the PDCP identifier is used as the setting information.
(1) The specified PDCP packet identifier and
(2) The compression or decompression ROHC entity adopted before the specified PDCP packet identifier, and
(3) One or more of the compression or decompression ROHC entities adopted after the specified PDCP packet identifier may be included.

In the embodiments of the present disclosure, if the PDCP entity of the communication device selectively includes a plurality of ROHC entities for compression or decompression, step 201 is
(1) If the PDCP identifier of the PDCP packet precedes the specified PDCP identifier, the corresponding compression or decompression ROHC entity is adopted.
(2) If the PDCP identifier of the PDCP packet is after the specified PDCP identifier, it may include any one of adopting the corresponding compression or decompression ROHC entity.

In the embodiments of the present disclosure, if the PDCP entity of the communication device optionally contains one ROHC entity for compression or decompression, step 201
(1) If the PDCP identifier of the PDCP packet precedes the specified PDCP identifier, the ROHC entity for first compression or decompression is adopted.
(2) If the PDCP identifier of the PDCP packet is after the specified PDCP identifier, the first compression or decompression ROHC entity is deleted, and a new compression or decompression ROHC entity is established and adopted. , Any one may be included
Here, the first compression or decompression ROHC entity is one specific compression or decompression ROHC entity established by the communication device according to the setting information of the plurality of compression or decompression ROHC entities.

In the embodiment of the present disclosure, the setting information of the connection corresponding to the PDCP packet is selectively used.
(1) Correspondence between a specific connection and a specific ROHC entity for compression,
(2) One or more of the correspondence between the specific connection and the specific decompression ROHC entity may be included.

Optionally, in the embodiments of the present disclosure, step 201
If the connection corresponding to the PDCP packet is the first connection, it may include adopting the compression or decompression ROHC entity corresponding to the first connection.

Optionally, in the embodiments of the present disclosure, step 201
(1) To establish a plurality of compression or decompression ROHC entities according to the setting information of a plurality of compression or decompression ROHC entities.
(2) One or more of establishing one specific compression or decompression ROHC entity according to the setting information of one compression or decompression ROHC entity may be included.

Optionally, in the embodiments of the present disclosure, step 201
After the mobility procedure is completed, it may include determining the compression or decompression ROHC entity corresponding to the target connection according to the information of the mobility procedure completion.

In the embodiments of the present disclosure, selectively, after step 201, the method shown in FIG. 2 is:
(1) Resetting the compression or decompression ROHC entity corresponding to the source connection,
(2) Of deleting the compression or decompression ROHC entity corresponding to the source connection, one or more may be further included.

In the embodiments of the present disclosure, selectively, the trigger event for completing the mobility procedure is
(1) The terminal received the instruction information for completing the mobility procedure sent from the network side, and
(2) The terminal sent the instruction information for completing the mobility procedure to the network side, and
(3) The random access procedure for the target connection has been completed, and
(4) One or more of the instruction information that the processing for the data of the source connection is completed is received by the terminal.

In the embodiments of the present disclosure, selectively, after step 201, the method shown in FIG. 2 is:
(1) Confirming the connection to which the PDCP packet is transmitted according to the PDCP identifier of the PDCP packet, and
(2) It may further include any one of determining the connection to which the PDCP packet is transmitted according to the compression ROHC entity that compressed the PDCP packet.

In the embodiments of the present disclosure, selectively, after step 201, the method shown in FIG. 2 is:
(1) When transmitting ROHC entity change information, the packet header of the PDCP packet is compressed or decompressed by the changed ROHC entity for compression or decompression.
(2) Before transmitting the ROHC entity change information, the packet header of the PDCP packet is compressed or decompressed by the changed compression or decompression ROHC entity.
(3) After transmitting the ROHC entity change information, any one of compressing or decompressing the packet header of the PDCP packet by the changed compression or decompression ROHC entity may be further included.

In the embodiments of the present disclosure, selectively, after step 201, the method shown in FIG. 2 is:
(1) When changing the compression or decompression ROHC entity to be used, if the PDCP setting information indicates that the communication device adopts the ROHC continuous function, the compression used before that. Or do not reset the ROHC entity for decompression,
(2) Before changing the compression or decompression ROHC entity to be used, if the PDCP setting information indicates that the communication device adopts the ROHC continuous function, it was used before that. Do not reset the ROHC entity for compression or decompression,
(3) After changing the compression or decompression ROHC entity to be used, if the PDCP setting information indicates that the communication device adopts the ROHC continuous function, the compression used before that. Alternatively, it further includes any one of not resetting the decompression ROHC entity.

In the embodiments of the present disclosure, selectively, after step 201, the method shown in FIG. 2 is:
(1) When changing the compression or decompression ROHC entity to be used, if the PDCP setting information does not instruct the communication device to adopt the ROHC continuous function, the compression used before that. Or resetting the decompression ROHC entity,
(2) Before changing the compression or decompression ROHC entity to be used, if the PDCP setting information does not instruct the communication device to adopt the ROHC continuous function, it was used before that. Resetting the ROHC entity for compression or decompression,
(3) After changing the compression or decompression ROHC entity used, if the PDCP setting information does not instruct the communication device to adopt the ROHC continuous function, the compression used before that. Alternatively, it further includes any one of resetting the decompression ROHC entity.

In the embodiments of the present disclosure, selectively, after step 201, the method shown in FIG. 2 is:
(1) When changing the used compression or decompression ROHC entity, resetting the previously used compression or decompression ROHC entity.
(2) To reset the previously used compression or decompression ROHC entity before changing the compression or decompression ROHC entity used.
(3) After changing the compression or decompression ROHC entity used, any one of resetting the previously used compression or decompression ROHC entity may be further included.

In the embodiments of the present disclosure, selectively, after step 201, the method shown in FIG. 2 is:
(1) When changing the used compression or decompression ROHC entity, deleting the previously used compression or decompression ROHC entity.
(2) Before changing the used compression or decompression ROHC entity, delete the previously used compression or decompression ROHC entity.
(3) After changing the compressed or decompressed ROHC entity used, any one of deleting the previously used compressed or decompressed ROHC entity may be further included.

In the embodiments of the present disclosure, even if there are a plurality of compression or decompression ROHC entities working for one DRB (or PDCP) of the communication device on the network side, the communication device is a packet. It is possible to realize a header compression or decompression function.

In order to better understand the embodiments of the present disclosure, the PDCP transmitting ends in the following examples correspond to the PDCP transmitting ends on the UE and network side, respectively, and the PDCP receiving ends are on the UE and network side, respectively. It can correspond to the PDCP receiving end.

Example 1.1: A packet header of a PDCP packet indicates a plurality of compression or decompression ROHC entities.

Step 1: The network side has set or the protocol that the UE manages a plurality of ROHC entities for compression or decompression by adopting the method of instruction by the packet header (for example, the instruction information of the PDCP packet header). Prescribed by.

Step 2: When the UE receives the setting information of multiple compression or decompression ROHC entities of one PDCP entity, the UE establishes multiple compression ROHC entities for uplink transmission and for downlink reception. On the other hand, multiple ROHC entities for decompression are established.

Illustratively, in the case of a DC handover procedure, for the same PDCP entity, both the source connection and the target connection have the corresponding compression or decompression ROHC entity (eg, compression or decompression ROHC1 and compression or decompression). If each of the ROHC2) is set, the UE establishes a plurality of compression ROHC entities for uplink transmission and a plurality of decompression ROHC entities for downlink reception.

Step 3.1: According to step 2, the behavior of the PDCP receiving end is
After the PDCP receiving end receives a PDCP packet (eg, a PDCP data packet and / or a ROHC feedback packet), it is specified according to the ROHC entity instruction information in the packet header of the PDCP protocol data unit PDU (protocol data unit) of the PDCP packet. Includes adopting and processing ROHC entities for compression or decompression.

For example, when the PDCP receiving entity of the UE receives the PDCP data packet, if the packet header of the PDCP PDU of the PDCP data packet indicates the decompression ROHC1 adopted in the PDCP data packet, the PDCP receiving entity of the UE. Uses ROHC1 for decompression to decompress the packet header of the PDCP PDU.

Further, for example, when the ROHC feedback packet is received by the PDCP receiving entity of the UE, if the packet header of the PDCP PDU of the ROHC feedback packet indicates the decompression ROHC1 adopted in the packet header packet of the PDCP PDU, the UE. The PDCP receiving entity of the above adopts ROHC1 for decompression and processes the packet header of the PDCP PDU.

Step 3.2: According to step 1, the behavior of the PDCP transmitting end is
When the PDCP transmit end adopts and compresses a specific compression or decompression ROHC entity (or sends a ROHC feedback packet (eg, "Control PDU for interspersed ROHC fedback")), the PDCP transmit end sends the PDCP. In the packet header, it includes specifying the ROHC entity for compression or decompression to be adopted.

For example, when the data is transmitted by the PDCP transmission entity of the UE, if the compression ROHC1 is adopted for the PDCP packet header compression of the data, the compression ROHC1 is adopted in the packet header of the PDCP PDU of the data. Instruct that it was done.

Further, for example, when the ROHC feedback packet (for example, "Control PDU for interspersed ROHC fedback") is transmitted by the PDCP transmission entity of the UE, if the ROHC1 for compression is adopted as the ROHC feedback packet, the ROHC feedback packet is used. In the packet header of the PDCP PDU, it is instructed that ROHC1 for compression has been adopted.

Additionally, the PDCP transmit end employs a compression or decompression ROHC entity for each connection for data packets transmitted to each connection.

Illustratively, according to network-side configuration information (eg, the source connection employs compression or decompression ROHC1 and the target connection employs compression or decompression ROHC2), the PDCP transmit end of the UE sends to the source connection. ROHC1 for compression or decompression is adopted for the data to be compressed, and ROHC2 for compression or decompression is adopted for the data transmitted to the target connection.

Additionally, for step 4: mobility procedure (eg, handover or secondary cell group change SCG change), the UE will have its PDCP sending entity respond to the target connection after the mobility procedure is complete. Adopt the compression or decompression ROHC entity (ie, no longer adopt the compression or decompression ROHC entity corresponding to the source connection).

In addition, the sending PDCP entity of the UE resets and / or deletes the compression or decompression ROHC entity corresponding to the source connection.

Here, the trigger event for completing the mobility procedure is
(1) The information of the mobility procedure completion instruction sent from the network side was received, for example, the setting message to delete the source connection was sent from the network side.
(2) The instruction information for completing the mobility procedure was sent to the network side, for example, the UE sent an instruction message to delete the source connection to the network side.
(3) The random access procedure for the target connection has been completed, and
(4) The processing for all the data of the source connection received by the PDCP transmission entity is completed (for example, the decompression is completed, the decryption is completed, or the data is transmitted to the upper layer). Of these, any combination of one or more is included.

Example 1.2: A PDCP identifier indicates multiple compression or decompression ROHC entities.

Step 1: The network side has set up that the UE manages multiple compression or decompression ROHC entities by adopting a method of instruction by a PDCP identifier (eg, PDCP SN or count (COUNT)). It is specified by the protocol.

Here, the PDCP identifier setting information includes
(1) Downlink PDCP packet identifier and
(2) Uplink PDCP packet identifier and
(3) One of the compression or decompression ROHC entities adopted before (or after) the downlink or uplink PDCP packet identifier is included.

Illustratively, the network side is set to use the compression or decompression ROHC1 before the specified PDCP SN (eg, 100) and then the compression or decompression ROHC2.

Step 2: When the UE receives the setting information of multiple compression or decompression ROHC entities of one PDCP entity, the UE establishes multiple compression ROHC entities for uplink transmission and for downlink reception. On the other hand, multiple ROHC entities for decompression are established.

Illustratively, in the case of a DC handover procedure, for the same PDCP entity, both the source connection and the target connection have the corresponding compression or decompression ROHC entity (eg, compression or decompression ROHC1 and compression or decompression). If each of the ROHC2) is set, the UE establishes a plurality of compression ROHC entities for uplink transmission and a plurality of decompression ROHC entities for downlink reception.

Step 3.1: According to step 2, the behavior of the PDCP receiving end is
After the PDCP receiving end receives a PDCP packet (eg, PDCP data packet and / or ROHC feedback packet), the UE adopts and processes a specific compression or decompression ROHC entity according to the received PDCP packet identifier. include.

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 set PDCP SN, the UE. PDCP receiving entity adopts compression or decompression ROHC1 to decompress the packet header of the PDCP PDU, otherwise adopts compression or decompression ROHC2.

Further, for example, when the PDCP receiving entity of the UE receives the ROHC feedback packet, if the PDCP SN of the PDCP packet received (or transmitted) before the ROHC feedback packet is a number before the set PDCP SN number. For example, the PDCP receiving entity of the UE adopts the compression or decompression ROHC1 to process the packet header of the PDCP PDU, otherwise adopts the compression or decompression ROHC2.

Step 3.2: According to step 1, the behavior of the PDCP transmitting end is
Includes that when a PDCP packet (eg, a PDCP data packet and / or a ROHC feedback packet) is transmitted by the PDCP transmit end, the UE employs and processes a particular compression or decompression ROHC entity according to the transmitted PDCP packet identifier. ..

For example, when the PDCP transmitting entity of the UE transmits data, if the PDCP SN of the PDCP data packet is a number before the set PDCP SN, the PDCP receiving entity of the UE adopts ROHC1 for compression or decompression. Then, the packet header of the PDCP PDU is compressed, and if not, the compression or decompression ROHC2 is adopted.

In addition, the PDCP transmitting end determines the connection to which the data packet is transmitted according to the PDCP identifier for the data packet transmitted to each connection. For example, in the DC handover procedure, when the PDCP transmitting entity of the UE transmits data, if the PDCP SN of the data packet is a number before the set PDCP SN number, the UE sends the data packet. Send over the source connection, otherwise over the target connection.

Additionally, for step 4: mobility procedure (eg, handover or SCG change), the UE adopts the compression or decompression ROHC entity corresponding to the target connection for the PDCP entity after the mobility procedure is completed. That is, it does not employ the compression or decompression ROHC entity that corresponds to the source connection.

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

Here, the trigger event for completing the mobility procedure is
(1) The information of the mobility procedure completion instruction sent from the network side was received, for example, the setting message to delete the source connection was sent from the network side.
(2) The instruction information for completing the mobility procedure was sent to the network side, for example, the UE sent an instruction message to delete the source connection to the network side.
(3) The random access procedure for the target connection has been completed, and
(4) Of the fact that the processing for all the data of the source connection received by PDCP is completed (for example, the decompression is completed, the decoding is completed, or the data is transmitted to the upper layer). Includes any combination of one or more.

Example 1.3: From a plurality of compression or decompression ROHC entities, the compression or decompression ROHC entity is selected according to the connection corresponding to the PDCP packet.

Step 1: It is set by the network side or specified by the protocol that the UE adopts the connection corresponding to the PDCP packet and manages a plurality of compression or decompression ROHC entities.

Here, the connection setting information corresponding to the PDCP packet includes a specific compression or decompression ROHC entity corresponding to a specific connection.

For example, the network side sets to adopt the decompression ROHC1 for the received data packet of the connection 1 and to adopt the compression ROHC1 for the transmitted data packet of the connection 1.

Step 2: When the UE receives the setting information of multiple compression or decompression ROHC entities of one PDCP entity, the UE establishes multiple compression ROHC entities for uplink transmission and for downlink reception. On the other hand, multiple ROHC entities for decompression are established.

For example, in the case of a DC handover procedure, for the same PDCP entity, both the source connection and the target connection have the corresponding compression or decompression ROHC entities (eg, compression or decompression ROHC1 and compression or decompression ROHC2). ) Is set, the UE establishes a plurality of compression ROHC entities for uplink transmission and a plurality of decompression ROHC entities for downlink reception.

Step 3.1: According to step 2, the behavior of the PDCP receiving end is
After the PDCP receiving end receives a PDCP packet (eg, PDCP data packet and / or ROHC feedback packet), the UE adopts and processes a specific compression or decompression ROHC entity according to the connection of the received PDCP packet. including.

For example, when the PDCP receiving entity of the UE receives the PDCP data packet, if the PDCP data packet is from connection 1, the PDCP receiving entity of the UE adopts ROHC1 for decompression and the PDCP PDU of the PDCP data packet. Unzip the packet header of.

Further, for example, when the ROHC feedback packet is received by the PDCP receiving entity of the UE, if the ROHC feedback packet is from connection 1, the PDCP receiving entity of the UE adopts the decompression ROHC 1 and processes the PDCP PDU. do.

Step 3.2: According to step 1, the behavior of the PDCP transmitting end is
When the PDCP transmitting end transmits a PDCP packet (eg, PDCP data packet and / or ROHC feedback packet), the UE adopts and processes a specific compression or decompression ROHC entity according to the connection of the transmitted PDCP packet. including.

For example, when the PDCP transmission entity of the UE transmits a PDCP data packet, if the PDCP data packet is transmitted via connection 1, the PDCP transmission entity of the UE adopts ROHC1 for compression and the PDCP data. Compress the packet's PDCP PDU.

Further, for example, when the ROHC feedback packet is transmitted by the PDCP transmission entity of the UE, if the ROHC feedback packet is a ROHC feedback packet with respect to the received data packet of ROHC1, the PDCP transmission entity of the UE adopts ROHC1 for compression. The packet header of the ROHC PDCP PDU is processed, and the ROHC feedback packet is transmitted to the connection corresponding to the compression ROHC1.

In addition, the PDCP transmitting end determines which connection the PDCP packet is transmitted to, according to the compressed or decompressed ROHC entity adopted for the PDCP packet transmitted to each connection.

For example, in the DC handover procedure, when the PDCP transmission entity of the UE transmits a PDCP packet, if the PDCP packet adopted is the compression ROHC1, the PDCP packet makes a connection corresponding to the compression ROHC1. Sent via.

Additionally, for step 4: mobility procedure (eg, handover or SCG change), the UE adopts the compression or decompression ROHC entity corresponding to the target connection by the PDCP entity after the mobility procedure is completed (eg, handover or SCG change). That is, it will no longer adopt the compression or decompression ROHC entity that corresponds to the source connection).

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

Here, the trigger event for completing the mobility procedure is
(1) The information of the mobility procedure completion instruction sent from the network side was received, for example, the setting message to delete the source connection was sent from the network side.
(2) The instruction information for completing the mobility procedure was sent to the network side, for example, the UE sent an instruction message to delete the source connection to the network side.
(3) The random access procedure for the target connection has been completed, and
(4) Of the fact that the processing for all the data of the source connection received by PDCP is completed (for example, the decompression is completed, the decoding is completed, or the data is transmitted to the upper layer). Includes any combination of one or more.

Example 1.4: Multiple compression or decompression ROHC entities are altered by PDCP control packets.

Step 1: It is set by the network side or specified by the protocol that the UE adopts the PDCP control packet method to manage a plurality of compression or decompression ROHC entities.

For example, after receiving the PDCP control packet, the compression or decompression ROHC entity to be adopted thereafter is determined according to the instruction information of the PDCP control packet.

Step 2: When the UE receives the setting information of multiple compression or decompression ROHC entities of one PDCP entity, the UE establishes multiple compression ROHC entities for uplink transmission and for downlink reception. On the other hand, multiple ROHC entities for decompression are established.

For example, in the case of a DC handover procedure, for the same PDCP entity, both the source connection and the target connection have the corresponding compression or decompression ROHC entities (eg, compression or decompression ROHC1 and compression or decompression ROHC2). ) Is set, the UE establishes a plurality of compression ROHC entities for uplink transmission and a plurality of decompression ROHC entities for downlink reception.

Step 3: After receiving the ROHC entity change information (for example, PDCP control packet) transmitted from the network side, the UE adopts the changed compression or decompression ROHC entity.

For example, if a PDCP control packet is received by one PDCP entity in the UE and the PDCP control packet indicates a compression or decompression ROHC entity to be adopted for the PDCP, that PDCP entity is used for it. Change the compression or decompression ROHC entity.

Alternatively, when transmitting (or before or after transmitting) the ROHC entity change information to the network side, the UE adopts the changed compression or decompression ROHC entity.

For example, at the time of transmission (or before or after transmission) of a PDCP control packet by one PDCP entity of the UE, the PDCP control packet indicates the compression or decompression ROHC entity to be adopted for the PDCP. If so, the PDCP entity modifies the compression or decompression ROHC entity used for it.

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

Additionally, the PDCP entity of the UE is the compression or decompression ROHC entity that was used before (or before, or after) the compression or decompression ROHC entity used for it. To delete.

Example 2.1: One compression or decompression ROHC entity is altered by a PDCP control packet.

Step 1: It is set by the network side or specified by the protocol that the UE adopts the method of PDCP control packet and manages one ROHC entity for compression or decompression.

For example, after receiving the PDCP control packet, the compression or decompression ROHC entity to be adopted thereafter is determined according to the instruction information of the PDCP control packet.

Step 2: When the UE receives the setting information of a plurality of compression or decompression ROHC entities of one PDCP entity, it first uses one specific compression or decompression ROHC entity.

For example, in the case of a DC handover procedure, for the same PDCP entity, both the source connection and the target connection have the corresponding compression or decompression ROHC entities (eg, compression or decompression ROHC1 and compression or decompression ROHC2). ) Is set, the UE first adopts the compression ROHC1 for the uplink transmission, and first adopts the decompression ROHC1 for the downlink reception.

Step 3: After receiving the ROHC entity change information (for example, PDCP control packet) transmitted from the network side, the UE adopts (or establishes) the changed compression or decompression ROHC entity.

For example, if a PDCP control packet is received by one PDCP entity in the UE and the PDCP control packet indicates a compression or decompression ROHC entity to be adopted for PDCP, that PDCP entity is used for it. Change the ROHC entity for compression or decompression.

Alternatively, the UE adopts (or establishes) the compressed or decompressed ROHC entity when transmitting (or before or after transmitting) the compressed or decompressed ROHC entity change information to the network side.

For example, at the time of transmission (or before or after transmission) of a PDCP control packet by one PDCP entity of the UE, the PDCP control packet indicates the compression or decompression ROHC entity to be adopted for the PDCP. If so, the PDCP entity modifies the compression or decompression ROHC entity used for it.

Additionally, the PDCP entity of the UE resets the ROHC entity when it changes (or before, or after) the compression or decompression ROHC entity used for it.

Additionally, when the PDCP entity of the UE changes (or before, or after) the compression or decompression ROHC entity used for it, it deletes the previously used ROHC entity.

Additionally, when the PDCP entity of the UE modifies (or before, or after) the compression or decompression ROHC entity used for it, if by the network side, the ROHC continuous function (eg drb-). If NetworkROHC) is set, the PDCP entity of the UE does not reset the compression or decompression ROHC entity.

Additionally, when the PDCP entity of the UE changes (or before, or after) the ROHC entity used for it, the ROHC continuous function for compression or decompression (eg drb-), if by the network side. If NetworkROHC) is not set, the PDCP entity of the UE resets the ROHC entity for compression or decompression.

Example 2.2: Change one compression or decompression ROHC entity by PDCP identifier.

Step 1: It is set by the network side or specified by the protocol that the UE adopts the method of PDCP identifier (for example, PDCP SN or COUNT) to manage one ROHC entity for compression or decompression. deep.
Here, the PDCP identifier setting information includes
(1) Downlink PDCP packet identifier and
(2) Uplink PDCP packet identifier and
(3) One of the compression or decompression ROHC entity adopted before (or after) the PDCP packet identifier is included.

For example, the network side is set to use the compression or decompression ROHC1 before the specified PDCP SN (for example, 100), and then to adopt the compression or decompression ROHC2.

Step 2: When the UE receives the setting information of a plurality of compression or decompression ROHC entities of one PDCP entity, it first uses one specific compression or decompression ROHC entity.

For example, in the case of a DC handover procedure, for the same PDCP entity, both the source connection and the target connection have the corresponding compression or decompression ROHC entities (eg, compression or decompression ROHC1 and compression or decompression ROHC2). ) Is set, the UE first adopts the compression ROHC1 for the uplink transmission, and first adopts the decompression ROHC1 for the downlink reception.

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

For example, if the PDCP identifier received by one PDCP entity of the UE is a number before the set PDCP SN number, the PDCP receiving entity of the UE adopts ROHC1 for decompression to process the PDCP PDU. If not, ROHC2 for defrosting is adopted.

Alternatively, the UE adopts (or establishes) the modified compression or decompression ROHC entity according to the corresponding PDCP identifier information transmitted to the network side.

For example, if the PDCP identifier transmitted by one PDCP entity of the UE is the number before the configured PDCP SN, the PDCP receiving entity of the UE adopts ROHC1 for compression to process the PDCP PDU. If not, ROHC2 for compression is adopted.

Additionally, the PDCP entity of the UE is the compression or decompression ROHC entity that was used before (or before, or after) the compression or decompression ROHC entity used for it. To reset.

Additionally, the PDCP entity of the UE is the compression or decompression ROHC entity that was used before (or before, or after) the compression or decompression ROHC entity used for it. To delete.

Additionally, when the PDCP entity of the UE changes (or before, or after) the ROHC entity used for it, the ROHC continuity function (eg, drb-ContinueROHC) is set by the network side. If so, the UE's PDCP entity does not reset the previously used compression or decompression ROHC entity.

Additionally, when the PDCP entity of the UE changes (or before, or after) the ROHC entity used for it, the ROHC continuous function (eg, drb-ContinueROHC) is set by the network side. If not, the UE's PDCP entity resets the previously used compression or decompression ROHC entity.

Example 2.3: Change one compression or decompression ROHC entity by changing the connection corresponding to the PDCP packet.

Step 1: It is set by the network side or specified by the protocol that the UE adopts the connection corresponding to the PDCP packet and manages one ROHC entity for compression or decompression.

Here, the connection setting information corresponding to the PDCP packet includes a specific compression or decompression ROHC entity corresponding to a specific connection.

For example, the network side sets to adopt the decompression ROHC1 for the received data packet of the connection 1 and to adopt the compression ROHC1 for the transmitted data packet of the connection 1.

Step 2: When the UE receives the setting information of a plurality of compression or decompression ROHC entities of one PDCP entity, it first uses one specific compression or decompression ROHC entity.

For example, in the case of a DC handover procedure, for the same PDCP entity, both the source connection and the target connection have the corresponding compression or decompression ROHC entities (eg, compression or decompression ROHC1 and compression or decompression ROHC2). ) Is set, the UE first adopts the compression ROHC1 for the uplink transmission, and first adopts the decompression ROHC1 for the downlink reception.

Step 3.1: According to step 2, the behavior of the PDCP receiving end is
After the PDCP receiving end receives a PDCP packet (eg, a PDCP data packet and / or a ROHC feedback packet), it involves the UE adopting and processing a particular decompression ROHC entity according to the connection of the received PDCP packet. ..

For example, when a PDCP data packet is received by the UE's PDCP receiving entity, if the PDCP data packet is from a source connection, the UE's PDCP receiving entity employs the decompression ROHC1 corresponding to the source connection. Unzip the packet header of the PDCP PDU of the PDCP data packet.

When the connection of the PDCP data packet received by the 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.

Further, for example, when the ROHC feedback packet is received by the PDCP receiving entity of the UE, if the ROHC feedback packet is from the connection 1, the PDCP receiving entity of the UE adopts the decompression ROHC 1 corresponding to the connection 1. , Decompress the packet header of the PDCP PDU.

Step 3.2: According to step 1, the behavior of the PDCP transmitting end is
When a PDCP packet (eg, a PDCP data packet and / or a ROHC feedback packet) is transmitted by the PDCP transmitting end, the UE includes adopting and processing a specific ROHC entity for compression according to the connection of the transmitted PDCP packet.

For example, when a PDCP data packet is transmitted by the UE's PDCP transmitting entity, if the PDCP data packet is transmitted over the source connection, the UE's PDCP transmitting entity employs the compression ROHC1 corresponding to the source connection. Compress the PDCP PDU of the PDCP data packet.

When the connection of the PDCP data packet transmitted by the PDCP sending entity of the UE is changed from the source connection to the target connection, the PDCP entity modifies the previously used compression or decompression ROHC entity.

Further, for example, when the ROHC feedback packet is transmitted by the PDU transmission entity of the UE, if the ROHC feedback packet is a ROHC feedback packet with respect to the received data packet of the compression ROHC1, the PDU transmission entity of the UE adopts the compression ROHC1. Then, the packet header of the PDCP PDU is processed, and the ROHC feedback packet is transmitted to the connection corresponding to the compression ROHC1.

Additionally, the PDCP entity of the UE is the compression or decompression ROHC entity that was used before (or before, or after) the compression or decompression ROHC entity used for it. To reset.

Additionally, the PDCP entity of the UE is the compression or decompression ROHC entity that was used before (or before, or after) the compression or decompression ROHC entity used for it. To delete.

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

Additionally, when the PDCP entity of the UE modifies (or before, or after) the compression or decompression ROHC entity used for it, if by the network side, the ROHC continuous function (eg drb-). If NetworkROHC) is set, the PDCP entity of the UE does not reset the previously used compression or decompression ROHC entity.

Additionally, when the PDCP entity of the UE modifies (or before, or after) the compression or decompression ROHC entity used for it, if by the network side, the ROHC continuous function (eg drb-). If NetworkROHC) is not set, the PDCP entity of the UE resets the previously used compression or decompression ROHC entity.

In addition, the PDCP transmitting end determines the connection to which the PDCP packet is transmitted according to the adopted compression ROHC entity for the PDCP packet transmitted to each connection.

For example, in the DC handover procedure, when the PDCP transmission entity of the UE transmits a PDCP packet, if the PDCP packet adopted is the compression ROHC1, the PDCP packet makes a connection corresponding to the compression ROHC1. Sent via.

Additionally, for step 4: mobility procedure (eg, handover or SCG change), the UE adopts the compression or decompression ROHC entity corresponding to the target connection by the PDCP entity after the mobility procedure is completed (eg, handover or SCG change). That is, it will no longer adopt the compression or decompression ROHC entity that corresponds to the source connection).

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

Here, the trigger event for completing the mobility procedure is
(1) The information of the mobility procedure completion instruction sent from the network side was received, for example, the setting message to delete the source connection was sent from the network side.
(2) The instruction information for completing the mobility procedure was sent to the network side, for example, the UE sent an instruction message to delete the source connection to the network side.
(3) The random access procedure for the target connection has been completed, and
(4) Of the fact that the processing for all the data of the source connection received by PDCP is completed (for example, the decompression is completed, the decoding is completed, or the data is transmitted to the upper layer). Includes any combination of one or more.

Example 3: By setting and controlling the ROHC continuous function by the network side, it is controlled whether one ROHC entity for compression or decompression is adopted or a plurality of ROHC entities are adopted.

Step 1: The network side controls whether one PDCP entity of the UE simultaneously establishes one or more ROHC for compression or decompression by setting the ROHC continuous function (for example, drb-Continue ROHC). do.

Step 2: Depending on the setting information of step 1, the behavior of the UE includes any one of the following (1) to (3).
(1) If the PDCP setting information indicates that the ROHC continuous function should be adopted (that is, an instruction that ROHC is not reset), the PDCP entity concerned has one ROHC entity for compression or decompression at the same time. It is possible to adopt and not to adopt the function of changing the ROHC entity for compression or decompression in Example 2.1 or 2.2.
(2) If the PDCP setting information does not indicate that the ROHC continuous function is adopted, and the UE receives the setting information of a plurality of compression or decompression ROHC entities of one PDCP entity, the UE. Establishes a plurality of compression ROHC entities for uplink transmission and a plurality of decompression ROHC entities for downlink reception.
(3) Unless the PDCP setting information indicates that the ROHC continuous function is adopted (that is, an instruction that ROHC is not reset), the PDCP entity concerned has one ROHC entity for compression or decompression at the same time. It is possible to adopt and adopt the function of changing the ROHC entity for compression or decompression in Example 2.1 or 2.2.

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 is repeated here. Do not explain.

If the UE adopts (or establishes) one compression or decompression ROHC entity at the same time, the behavior of the UE will be if the function of changing the compression or decompression ROHC entity in Example 2.1 or 2.2 is adopted. , The same as the function of changing the compression or decompression ROHC entity in Example 2.1 or 2.2, which will not be repeated here.

In the embodiments of the present disclosure, the communication device is further provided, but since the principle that the communication device solves the problem is similar to the processing method in the embodiment of the present disclosure, the implementation of the communication device is described. The implementation of the method can be referred to and the overlap is not explained repeatedly.

With reference to FIG. 3, the embodiments of the present disclosure further provide a communication device, for example, a terminal or a network device, wherein the communication device 300 is described.
Includes a first confirmation module 301 for determining a ROHC entity for compression or decompression according to the first information.
Here, the first information includes instruction information in the packet header of the PDCP packet, information on the completion of the mobility procedure, the PDCP identifier of the PDCP packet, the connection corresponding to the PDCP packet, and the instruction information in the PDCP control packet. , PDCP setting information and one or more of the setting information of the ROHC entity for compression or decompression.

In the embodiment of the present disclosure, the PDCP setting information selectively indicates that the communication device adopts the ROHC continuous function, and the PDCP entity of the communication device is a compression or decompression ROHC entity. Including or
The PDCP setting information does not indicate that the communication device adopts the ROHC continuous function, and the PDCP entity of the communication device includes a plurality of ROHC entities for compression or decompression.

In the embodiments of the present disclosure, selectively, the instruction information in the PDCP control packet is
To have the communication device change the ROHC entity for compression or decompression,
Do not allow the communication device to change the ROHC entity for compression or decompression.
It indicates at least one of having the communication device delete the previous compression or decompression ROHC entity and establishing a new compression or decompression ROHC entity.

In the embodiments of the present disclosure, optionally, the communication device 300 further comprises a second deterministic module for determining the corresponding first information according to a particular instruction scheme.
Here, the specific instruction method is
Instructions from the packet header of the PDCP packet and
Instructions from the PDCP identifier setting information of the PDCP packet,
Instructions from the connection setting information corresponding to the PDCP packet,
Includes one or more of the instructions by the PDCP control packet.

In the embodiments of the present disclosure, optionally, the particular instruction scheme is set by the network side or specified by a protocol.

In the embodiment of the present disclosure, selectively, the setting information of the PDCP identifier is used as the setting information.
With the specified PDCP packet identifier,
The compression or decompression ROHC entity adopted before the specified PDCP packet identifier,
Includes one or more of the compression or decompression ROHC entities adopted after the specified PDCP packet identifier.

In the embodiments of the present disclosure, selectively, the first determination module 301 is
If the PDCP identifier of the PDCP packet precedes the specified PDCP identifier, then the corresponding compression or decompression ROHC entity is adopted.
If the PDCP identifier of the PDCP packet follows the specified PDCP identifier, it is further used to perform any one of adopting the corresponding compression or decompression ROHC entity.

In the embodiments of the present disclosure, selectively, the first determination module 301 is
If the PDCP identifier of the PDCP packet precedes the specified PDCP identifier, then the ROHC entity for first compression or decompression is adopted.
If the PDCP identifier of the PDCP packet is after the specified PDCP identifier, either the first compression or decompression ROHC entity is deleted and a new compression or decompression ROHC entity is established and adopted. Further used to perform one,
Here, the first compression or decompression ROHC entity is one specific compression or decompression ROHC entity established by the communication device according to the setting information of the plurality of compression or decompression ROHC entities.

In the embodiment of the present disclosure, the setting information of the connection corresponding to the PDCP packet is selectively used.
Correspondence between a specific connection and a specific ROHC entity for compression,
Includes one or more of the correspondence between a particular connection and a particular decompression ROHC entity.

In the embodiments of the present disclosure, selectively, the first determination module 301 is
If the connection corresponding to the PDCP packet is the first connection, it is further used to employ the compression or decompression ROHC entity corresponding to the first connection.

In the embodiments of the present disclosure, selectively, the first determination module 301 is
Establishing multiple compression or decompression ROHC entities according to the setting information of multiple compression or decompression ROHC entities.
It is further used to perform one or more of establishing one specific compression or decompression ROHC entity according to the configuration information of one compression or decompression ROHC entity.

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

In the embodiments of the present disclosure, selectively, the communication device 300 further includes a first processing module, and the first processing module is the first processing module.
Resetting the compression or decompression ROHC entity that corresponds to the source connection,
Of deleting the compression or decompression ROHC entity corresponding to the source connection, is to perform one or more.

In the embodiments of the present disclosure, selectively, the trigger event for completing the mobility procedure is
The terminal received the instruction information for completing the mobility procedure sent from the network side, and
The instruction information for completing the mobility procedure was sent from the terminal to the network side, and
The random access procedure for the target connection has been completed and
It includes one or more of the instruction information that the processing for the data of the source connection is completed is received by the terminal.

In the embodiments of the present disclosure, selectively, the communication device 300 further includes a second processing module, and the second processing module is the second processing module.
Determining the connection to which the PDCP packet is transmitted according to the PDCP identifier of the PDCP packet.
It is for executing any one of determining the connection to which the PDCP packet is transmitted according to the compression ROHC entity that compressed the PDCP packet.

In the embodiments of the present disclosure, selectively, the communication device 300 further includes a third processing module, and the third processing module is the third processing module.
When transmitting the ROHC entity change information, the packet header of the PDCP packet is compressed or decompressed by the changed ROHC entity for compression or decompression.
Before transmitting the ROHC entity change information, the packet header of the PDCP packet is compressed or decompressed by the modified ROHC entity for compression or decompression.
After transmitting the ROHC entity change information, the purpose is to execute any one of compression or decompression of the packet header of the PDCP packet by the changed compression or decompression ROHC entity.

In the embodiments of the present disclosure, selectively, the communication device 300 further includes a fourth processing module, and the fourth processing module is the fourth processing module.
When changing the compression or decompression ROHC entity used, if the PDCP setting information indicates that the communication device should adopt the ROHC continuous function, the compression or decompression used before that. Do not reset the ROHC entity and
Before changing the compression or decompression ROHC entity used, if the PDCP configuration information indicates that the communication device should adopt the ROHC continuous function, the compression or decompression previously used. Do not reset the ROHC entity for
After changing the compression or decompression ROHC entity used, if the PDCP setting information indicates that the communication device should adopt the ROHC continuous function, the compression or decompression used before that. It is for executing any one of not resetting the ROHC entity.

In the embodiments of the present disclosure, selectively, the communication device 300 further includes a fifth processing module, and the fifth processing module is the fifth processing module.
When changing the compression or decompression ROHC entity used, if the PDCP setting information does not instruct the communication device to adopt the ROHC continuous function, the compression or decompression used before that. Resetting the ROHC entity and
Before changing the compression or decompression ROHC entity used, if the PDCP configuration information does not instruct the communication device to adopt the ROHC continuous function, the compression or decompression previously used. To reset the ROHC entity for
After changing the compression or decompression ROHC entity used, if the PDCP setting information does not instruct the communication device to adopt the ROHC continuous function, the compression or decompression used before that. It is for performing any one of resetting the ROHC entity.

In the embodiments of the present disclosure, selectively, the communication device 300 further includes a sixth processing module, and the sixth processing module is the sixth processing module.
When changing the used compression or decompression ROHC entity, resetting the previously used compression or decompression ROHC entity,
To reset the previously used compression or decompression ROHC entity before changing the compression or decompression ROHC entity used.
After changing the compression or decompression ROHC entity used, resetting the previously used compression or decompression ROHC entity is to perform any one.

In the embodiments of the present disclosure, selectively, the communication device 300 further includes a seventh processing module, and the seventh processing module is the seventh processing module.
When changing the used compression or decompression ROHC entity, deleting the previously used compression or decompression ROHC entity,
Before changing the used compression or decompression ROHC entity, delete the previously used compression or decompression ROHC entity.
It is for performing any one of changing the used compression or decompression ROHC entity and then deleting the previously used compression or decompression ROHC entity.

The communication device according to the embodiment of the present disclosure can carry out the embodiment of the above method, and its realization principle and technical effect are similar, and this embodiment will not be repeatedly described here.

With reference to FIG. 4, FIG. 4 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.

In one embodiment of the present disclosure, the communication device 400 further includes a program stored in memory 403 and capable of operating on processor 401, and when the program is executed by processor 401, it is for compression or decompression according to the first information. It is realized that the ROHC entity is determined, where the first information is the instruction information in the packet header of the PDCP packet, the information on the completion of the mobility procedure, the PDCP identifier of the PDCP packet, and the connection corresponding to the PDCP packet. , One or more of the instruction information in the PDCP control packet, the PDCP setting information, and the setting information of the compression or decompression ROHC entity.

In FIG. 4, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors typified by processor 401 and memory typified by memory 403. It is connected to various circuits of. Bus architectures can also connect various other circuits such as peripherals, voltage regulators, power management circuits, etc. to each other, but these are known in the art and are described further herein. do not do. The bus interface provides the interface. The transmitter / receiver 402 may be a plurality of elements, that is, may include a transmitter and a receiver, and provides means for communicating with various other devices on a transmission medium.

The processor 401 is responsible for managing the bus architecture and general processing, and the memory 403 can store data used when the operation is executed by the processor 401.

The communication device according to the embodiment of the present disclosure can carry out the embodiment of the above method, and its realization principle and technical effect are similar, and this embodiment will not be repeatedly described here.

The methods or algorithmic steps described in conjunction with the disclosures of the present disclosure may be implemented in the form of hardware or in the form of executing software commands on a processor. The software command consists of the corresponding software module. The software module includes a random access memory RAM (Random Access Memory), a flash memory, a read-only memory ROM (Read-Only Memory), an erasable programmable read-only memory EEPROM (Erasable PROM), and an electrically erasable programmable read-only memory EEPROM (Erasable PROM). It may be stored in an Electrically EEPROM), a register, a hard disk, a portable hard disk, a read-only optical disk, or a storage medium of any type known in the art. An exemplary storage medium is coupled to the processor. Therefore, the processor can read the information from the storage medium and write the information to the storage medium. Of course, the storage medium may be a component of the processor. The processor and storage medium may be integrated into the ASIC. Further, the ASIC may be incorporated in the core network interface device. Of course, the processor and storage medium may be located in the core network interface equipment as separate components.

One of ordinary skill in the art will be aware that in one or more of the above examples, the functionality described in this disclosure can be achieved by hardware, software, firmware or any combination thereof. When implemented in software, these functions are stored on a computer-readable medium or transmitted as one or more commands or codes on the computer-readable medium. Computer-readable media include computer storage media and communication media. Communication media include any medium that facilitates the transmission of computer programs from one location to another. The storage medium is any available medium accessible by a general purpose or special purpose computer.

Those skilled in the art will appreciate that the units and algorithm steps in each of the examples described herein in conjunction with the embodiments 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 of the technical proposal and the design constraint requirements. One of ordinary skill in the art may use different methods to achieve the functions described for each particular application, but such implementations should not be considered outside the scope of this disclosure.

For convenience and brevity of description, the specific working procedures of the systems, devices and units described above can be referred to by the corresponding procedures in the above method embodiments and will not be repeated here. It will be clearly understood by those skilled in the art.

It should be understood that in the embodiments according to the present application, the disclosed devices and methods may be implemented in other ways. For example, the device embodiments described above are merely exemplary. For example, the division of the unit is merely a division by a logical function, and other division methods may be possible at the time of actual realization. For example, multiple units or components may be combined or integrated into another system, some features may be ignored or not realized. In addition, the posted or described interconnect, direct coupling or communication connection may be implemented using several interfaces. The indirect coupling or communication connection between devices or units may be in electronic form, mechanical form, or other form.

The units described as separate parts may or may not be physically separated, and the parts posted as units may or may not be physical units. It may be located in a location or may be distributed over a plurality of network units. In order to achieve the purpose of the technical proposal according to this embodiment, some or all units may be selected according to actual needs.

Further, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, each unit may physically exist independently, and two or more units may be present. It may be integrated into one unit.

The above functions are realized in the form of software functional units and may be stored on a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the essential parts of the proposed technology of the present disclosure, or the parts that contribute to the related technology, can be embodied in the form of software products. The computer software product is stored on a storage medium to allow a computer device (which may be a personal computer, server, or network device) to perform all or part of the steps in the methods described in each embodiment of the present disclosure. Includes several commands for. The above storage medium includes any medium capable of storing a program code such as a USB flash drive, a portable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

As can be understood by those skilled in the art, all or part of the flow in the method according to the above embodiment may be realized by controlling the related hardware by a computer program, and the program may be read by a computer. It may be stored in a possible storage medium, and the program may include a flow of embodiments of each of the above methods when executed. Among them, the storage medium may be a magnetic disk, an optical disk, a read-only memory ROM (Read-Only Memory), a random access memory RAM (Random Access Memory), or the like.

As will be appreciated, these embodiments described in the embodiments of the present disclosure are feasible by hardware, software, firmware, middleware, microcode, or a combination thereof. Regarding realization by hardware, the processing unit includes one or more integrated circuits ASIC (Application Specific Integrated Circuits), digital signal processor DSP (Digital Signal Processor), digital signal processing device DSPD (DSP Device), and programmable logic. Device PLD (Programmable Logic Device), Field Programmable Gate Array FPGA (Field-Programmable Gate Array), General Purpose Processor, Controller, Microcontroller, Microprocessor, Other Electronic Units for Performing the Functions Described in the Present Disclosure, or Combinations thereof. It is feasible in.

For software realization, the techniques described in the embodiments of the present disclosure can be realized by modules (eg, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure. The software code can be stored in memory and executed by the processor. The memory can be realized inside the processor or outside the processor.

Although the purpose, the technical proposal, and the beneficial effects of the present disclosure have been described in more detail by the specific embodiments described above, the above description is merely a specific embodiment of the present disclosure, and the above description is merely a specific embodiment of the present disclosure. It is not intended to limit the scope of protection. All modifications, even substitutions and improvements made based on the proposed technology of the present disclosure should be included in the scope of protection of the present disclosure.

Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, the embodiments of the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or a combination of software and hardware embodiments. Moreover, in the embodiments of the present disclosure, one or more computer-usable storage media (magnetic disk memory, compact disk read-only memory CD-ROM (Compact Disc Read-Only Memory)), which includes a computer-usable program code,. It may take the form of a computer program product implemented in, but not limited to, optical memory and the like.

The embodiments of the present disclosure are described with reference to the flow charts and / or block diagrams of the methods, devices (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 flow chart and / or block diagram, and the combination of flow and / or block in the flowchart and / or block diagram, can be realized by computer program commands. These computer program commands are provided to a general purpose computer, a dedicated computer, an inset processor or the processor of another programmable data processing device to form a device, and commands executed by the computer or the processor of another programmable data processing device. To form a device for realizing a function specified by one or more flows and / or one or more blocks in a block diagram.

These computer program commands may be stored in computer-readable memory that can lead the computer or other programmable data processing device to operate in a particular manner, by commands stored in the computer-readable memory. Form a product that includes a command device. The command device implements a function specified by one or more flows in a flowchart and / or one or more blocks in a block diagram.

These computer program commands may be loaded into a computer or other programmable data processing device, forming a computer-implemented process by performing a series of operational steps on the computer or other programmable device. Alternatively, a command executed on another programmable device provides a step for realizing the function specified by one or more flows and / or blocks of a block diagram.

Obviously, one of ordinary skill 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 modifications of the embodiments of the present disclosure also belong to the scope of the claims of the present disclosure and the scope of the equivalent technology thereof, the present disclosure shall include these modifications and modifications.

Claims (23)

It is a processing method applied to communication equipment.
Including determining the Robust Header Compression ROHC (Robust Header Compression) entity for compression or decompression according to the first information.
Here, the first information includes instruction information in the packet header of the packet data convergence protocol PDCP (Packet Data Convergence Protocol) packet, information on the completion of the mobility procedure, the PDCP identifier of the PDCP packet, and the connection corresponding to the PDCP packet. , One or more of the instruction information in the PDCP control packet, the PDCP setting information, and the setting information of the ROHC entity for compression or decompression. The PDCP setting information indicates that the communication device adopts the ROHC continuous function, and the PDCP entity of the communication device includes one ROHC entity for compression or decompression, or
The method according to claim 1, wherein the PDCP setting information does not instruct the communication device to adopt the ROHC continuous function, and the PDCP entity of the communication device includes a plurality of ROHC entities for compression or decompression. The instruction information in the PDCP control packet is
To have the communication device change the ROHC entity for compression or decompression,
Do not allow the communication device to change the ROHC entity for compression or decompression.
The method of claim 1, wherein the communication device is instructed to delete the previous compression or decompression ROHC entity and establish a new compression or decompression ROHC entity. Prior to determining the ROHC entity for compression or decompression according to the first information above, the method is described.
Further including establishing the corresponding first information according to a particular instruction method.
Here, the specific instruction method is
Instructions from the packet header of the PDCP packet and
Instructions from the PDCP identifier setting information of the PDCP packet,
Instructions from the connection setting information corresponding to the PDCP packet,
The method of claim 1, comprising one or more of the instructions by the PDCP control packet. The method of claim 4, wherein the particular instruction scheme is set by the network side or specified by a protocol. The PDCP identifier setting information includes
With the specified PDCP packet identifier,
The compression or decompression ROHC entity adopted before the specified PDCP packet identifier,
The method of claim 4, wherein one or more of the compression or decompression ROHC entities adopted after the specified PDCP packet identifier is included. The PDCP entity of the communication device includes a plurality of ROHC entities for compression or decompression, and it is possible to determine the ROHC entity for compression or decompression according to the first information described above.
If the PDCP identifier of the PDCP packet precedes the specified PDCP identifier, then the corresponding compression or decompression ROHC entity is adopted.
The method of claim 1, wherein the PDCP identifier of the PDCP packet comprises any one of adopting the corresponding compression or decompression ROHC entity if it follows the specified PDCP identifier. The PDCP entity of the communication device includes one ROHC entity for compression or decompression, and it is possible to determine the ROHC entity for compression or decompression according to the first information described above.
If the PDCP identifier of the PDCP packet precedes the specified PDCP identifier, then the ROHC entity for first compression or decompression is adopted.
If the PDCP identifier of the PDCP packet is after the specified PDCP identifier, either the first compression or decompression ROHC entity is deleted and a new compression or decompression ROHC entity is established and adopted. Including one
Here, claim 1, the first compression or decompression ROHC entity is one specific compression or decompression ROHC entity established by the communication device according to the setting information of a plurality of compression or decompression ROHC entities. The method described. The connection setting information corresponding to the PDCP packet includes
Correspondence between a specific connection and a specific ROHC entity for compression,
The method of claim 4, wherein one or more of the correspondence between the particular connection and the particular decompression ROHC entity is included. Determining the ROHC entity for compression or decompression according to the first information above
The method according to claim 1, wherein if the connection corresponding to the PDCP packet is the first connection, the compression or decompression ROHC entity corresponding to the first connection is adopted. Determining the ROHC entity for compression or decompression according to the first information above
Establishing multiple compression or decompression ROHC entities according to the setting information of multiple compression or decompression ROHC entities.
The method according to claim 1, wherein one or more of establishing one compression or decompression ROHC entity according to the setting information of one compression or decompression ROHC entity. Determining the ROHC entity for compression or decompression according to the first information above
The method of claim 1, wherein after the completion of the mobility procedure, the compression or decompression ROHC entity corresponding to the target connection is determined according to the information of the completion of the mobility procedure. After determining the compression or decompression ROHC entity corresponding to the target connection, the method
Resetting the compression or decompression ROHC entity that corresponds to the source connection,
12. The method of claim 12, comprising deleting one or more of the compression or decompression ROHC entities corresponding to the source connection. The trigger event for completing the mobility procedure is
The terminal received the instruction information for completing the mobility procedure sent from the network side, and
The instruction information for completing the mobility procedure was sent from the terminal to the network side, and
The random access procedure for the target connection has been completed and
The method according to claim 12, wherein the terminal has received instruction information indicating that the processing for the data of the source connection has been completed, including one or more. After determining the ROHC entity for compression or decompression according to the first information above, the method.
Determining the connection to which the PDCP packet is transmitted according to the PDCP identifier of the PDCP packet.
The method according to claim 1, further comprising one of the determination of the connection to which the PDCP packet is transmitted according to the compression ROHC entity that compressed the PDCP packet. After determining the ROHC entity for compression or decompression according to the first information above, the method.
When transmitting the ROHC entity change information, the packet header of the PDCP packet is compressed or decompressed by the changed ROHC entity for compression or decompression.
Before transmitting the ROHC entity change information, the packet header of the PDCP packet is compressed or decompressed by the modified ROHC entity for compression or decompression.
The method according to claim 1, further comprising any one of compressing or decompressing the packet header of the PDCP packet by the modified ROHC entity for compression or decompression after transmitting the ROHC entity change information. After determining the ROHC entity for compression or decompression according to the first information above, the method.
When changing the compression or decompression ROHC entity used, if the PDCP setting information indicates that the communication device should adopt the ROHC continuous function, the compression or decompression used before that. Do not reset the ROHC entity and
Before changing the compression or decompression ROHC entity used, if the PDCP configuration information indicates that the communication device should adopt the ROHC continuous function, the compression or decompression previously used. Do not reset the ROHC entity for
After changing the compression or decompression ROHC entity used, if the PDCP setting information indicates that the communication device should adopt the ROHC continuous function, the compression or decompression used before that. The method of claim 2, further comprising not resetting the ROHC entity. After determining the ROHC entity for compression or decompression according to the first information above, the method.
When changing the compression or decompression ROHC entity used, if the PDCP setting information does not instruct the communication device to adopt the ROHC continuous function, the compression or decompression used before that. Resetting the ROHC entity and
Before changing the compression or decompression ROHC entity used, if the PDCP configuration information does not instruct the communication device to adopt the ROHC continuous function, the compression or decompression previously used. To reset the ROHC entity for
After changing the compression or decompression ROHC entity used, if the PDCP setting information does not instruct the communication device to adopt the ROHC continuous function, the compression or decompression used before that. The method of claim 2, further comprising resetting the ROHC entity. After determining the ROHC entity for compression or decompression according to the first information above, the method.
When changing the used compression or decompression ROHC entity, resetting the previously used compression or decompression ROHC entity,
To reset the previously used compression or decompression ROHC entity before changing the compression or decompression ROHC entity used.
The method of claim 1, further comprising resetting the previously used compression or decompression ROHC entity after changing the compression or decompression ROHC entity used. .. After determining the ROHC entity for compression or decompression according to the first information above, the method.
When changing the used compression or decompression ROHC entity, deleting the previously used compression or decompression ROHC entity,
Before changing the used compression or decompression ROHC entity, delete the previously used compression or decompression ROHC entity.
The method of claim 1, further comprising any one of changing the used compression or decompression ROHC entity and then deleting the previously used compression or decompression ROHC entity. .. It ’s a communication device,
Contains a decompression module for decompressing robust header compression ROHC entities for compression or decompression according to the first information.
Here, the first information includes instruction information in the packet header of the packet data convergence protocol PDCP packet, information on the completion of the mobility procedure, the PDCP identifier of the PDCP packet, the connection corresponding to the PDCP packet, and the PDCP control packet. The communication device, which is one or more of the instruction information, the PDCP setting information, and the setting information of the ROHC entity for compression or decompression. The processing method according to any one of claims 1 to 20, which includes a processor, a memory, and a program stored in the memory and capable of operating on the processor, and when the program is executed by the processor. Is realized, communication equipment. A computer-readable storage medium that stores a computer program, wherein when the computer program is executed by a processor, the processing method according to any one of claims 1 to 20 is realized. Storage medium.

Images