WO2020156427A1 - 处理方法及通信设备 - Google Patents

处理方法及通信设备 Download PDF

Info

Publication number
WO2020156427A1
WO2020156427A1 PCT/CN2020/073778 CN2020073778W WO2020156427A1 WO 2020156427 A1 WO2020156427 A1 WO 2020156427A1 CN 2020073778 W CN2020073778 W CN 2020073778W WO 2020156427 A1 WO2020156427 A1 WO 2020156427A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
rohc
entity
decompression
compression
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/073778
Other languages
English (en)
French (fr)
Inventor
吴昱民
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Priority to ES20749437T priority Critical patent/ES3055610T3/es
Priority to JP2021544648A priority patent/JP7279173B2/ja
Priority to EP20749437.8A priority patent/EP3920502B1/en
Priority to KR1020217026361A priority patent/KR102502507B1/ko
Publication of WO2020156427A1 publication Critical patent/WO2020156427A1/zh
Priority to US17/388,629 priority patent/US12284550B2/en
Anticipated expiration legal-status Critical
Priority to US19/063,780 priority patent/US20260122533A1/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/04—Protocols for data compression, e.g. ROHC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the embodiments of the present disclosure relate to the field of communication technologies, and in particular to a processing method and communication equipment.
  • ROHC Robust Header Compression
  • DRB data radio bearer
  • PDCP Packet Data Convergence Protocol
  • One purpose of the embodiments of the present disclosure is to provide a processing method and communication device to solve the problem of header compression or decompression on the terminal side and the network side.
  • a processing method which is applied to a communication device, and the method includes:
  • the first information is one or more of the following: indication information in the header of the PDCP packet of the Packet Data Convergence Protocol; information on completion of the mobility process; PDCP identifier of the PDCP packet; connection corresponding to the PDCP packet; PDCP control packet Indication information in; PDCP configuration information; Compression or decompression of ROHC entity configuration information.
  • a communication device including:
  • the determining module is used to determine the compression or decompression ROHC entity according to the first information
  • the first information is one or more of the following: indication information in the header of the PDCP packet; information on completion of the mobility process; PDCP identifier of the PDCP packet; connection corresponding to the PDCP packet; indication information in the PDCP control packet ; PDCP configuration information; compress or decompress the configuration information of the ROHC entity.
  • a communication device including: a processor, a memory, and a program stored on the memory and capable of running on the processor, the program being processed by the When the processor is executed, the steps of the processing method described above are implemented.
  • a computer-readable storage medium having a computer program stored on the computer-readable storage medium, and when the computer program is executed by a processor, the processing method described above is implemented A step of.
  • ROHC entities when multiple compressed or decompressed ROHC entities may work as a DRB (or PDCP) of the terminal on the network side, the terminal side and the network side can still realize the header compression or decompression function.
  • DRB or PDCP
  • FIG. 1 is a schematic diagram of the architecture of a wireless communication system according to an embodiment of the disclosure
  • FIG. 2 is a flowchart of a processing method according to an embodiment of the disclosure
  • FIG. 3 is one of the structural diagrams of the communication device of the embodiment of the disclosure.
  • Fig. 4 is the second structural diagram of the communication device according to the embodiment of the disclosure.
  • words such as “exemplary” or “for example” are used as examples, illustrations, or illustrations. Any embodiment or design solution described as “exemplary” or “for example” in the embodiments of the present disclosure should not be construed as being more optional or advantageous than other embodiments or design solutions. To be precise, words such as “exemplary” or “for example” are used to present related concepts in a specific manner.
  • the network side can specify the Packet Data Convergence Protocol (PDCP) entity Configure ROHC function in the.
  • the ROHC function corresponds to a maximum of 1 ROHC compression (for example, the terminal side corresponds to uplink data transmission) entity (or module, or protocol layer, or context) in the PDCP entity and a maximum of 1 ROHC decompression (for example, the terminal side corresponds to downlink data) Receiving) entity (or module, or protocol layer, or context).
  • the ROHC entity can compress and decompress the header of high-level data packets (for example, Transmission Control Protocol (TCP)/Internet Protocol (IP)), and the ROHC decompression entity can send feedback on the state of decompression.
  • TCP Transmission Control Protocol
  • IP Internet Protocol
  • the information is given to the opposite ROHC compression entity.
  • the network side can configure (that is, indicated by DRB ROHC (drb-Continue ROHC) signaling) whether the ROHC entity of the PDCP entity needs to be reset.
  • DRB ROHC darb-Continue ROHC
  • the terminal is configured with drb-ContinueROHC, and the terminal does not reset its ROHC but continues to use the ROHC entity before the handover.
  • the terminal since the interruption delay of the mobility process of 0ms needs to be met, it is necessary for the terminal to have a connection between the source node and the target node during the movement to send and receive data. To maintain data connections at the source node and target node at the same time.
  • the source node and target node on the corresponding network side have independent ROHC compression or decompression entities.
  • LTE-Advanced LTE-Advanced, LTE-A
  • LTE-A LTE/LTE evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the terms “system” and “network” are often used interchangeably.
  • the CDMA system can implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA).
  • UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants.
  • the TDMA system can implement radio technologies such as the Global System for Mobile Communication (GSM).
  • OFDMA system can realize such as ultra mobile broadband (Ultra Mobile Broadband, UMB), evolved UTRA (Evolution-UTRA, E-UTRA), IEEE 802.11 (wireless fidelity (Wi-Fi)), IEEE 802.16 (global microwave Access interoperability (World Interoperability for Microwave Access, WiMAX), IEEE 802.20, Flash-OFDM and other radio technologies.
  • UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS).
  • LTE and more advanced LTE (such as LTE-A) are new UMTS versions that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project” (3GPP).
  • CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • the techniques described in this article can be used for the systems and radio technologies mentioned above, as well as other systems and radio technologies.
  • the wireless communication system may include: a first network device 10, a second network device 11, and a terminal.
  • the terminal is denoted as User Equipment (UE) 12, and the UE 12 may interact with the first network device 10 and
  • the second network device 11 communicates (transmits signaling or transmits data).
  • UE User Equipment
  • the connection between the above-mentioned various devices may be a wireless connection.
  • FIG. 1 In order to conveniently and intuitively indicate the connection relationship between the various devices, a solid line is used in FIG. 1 to indicate. It should be noted that the foregoing communication system may include multiple UEs 12, and the first network device 10 and the second network device 11 may communicate with multiple UEs 12.
  • the terminal provided by the embodiment of the present disclosure may be a mobile phone, a tablet computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook or a personal digital assistant (PDA), and a mobile Internet device (Mobile Internet).
  • UMPC ultra-mobile personal computer
  • PDA personal digital assistant
  • Mobile Internet Mobile Internet
  • Device MID
  • Wearable Device Wearable Device
  • vehicle-mounted equipment etc.
  • the first network device 10 and the second network device 11 provided in the embodiments of the present disclosure may be base stations.
  • the base stations may be commonly used base stations, evolved node base stations (eNB), or 5G systems.
  • Network equipment for example, next generation node base station (gNB) or transmission and reception point (TRP)) and other equipment.
  • gNB next generation node base station
  • TRP transmission and reception point
  • the ROHC entity may also be referred to as an ROHC module, ROHC protocol layer, or ROHC context.
  • an embodiment of the present disclosure also provides a processing method.
  • the execution subject of the method may be a communication device, such as a terminal or a network device.
  • the method includes step 201.
  • Step 201 Determine the compression or decompression ROHC entity according to the first information
  • the first information may be one or more of the following: indication information in the header of the PDCP packet; information about the completion of the mobility process; PDCP identifier of the PDCP packet; connection corresponding to the PDCP packet; indication in the PDCP control packet Information; PDCP configuration information; compression or decompression of ROHC entity configuration information.
  • the above-mentioned PDCP packet may be a PDCP data packet and/or an ROHC feedback packet.
  • the communication device has multiple compression or decompression ROHC entities, exemplarily:
  • the indication information in the PDCP control packet indicates whether to change the ROHC entity used by the communication device.
  • the communication device has 1 ROHC entity, exemplarily:
  • Indication information in the PDCP control packet instruct the communication device to delete the previous (old) ROHC entity and establish a new ROHC entity.
  • the communication device Before the designated PDCP SN number, the communication device adopts ROHC entity 1, and after the designated PDCP SN number, the communication device deletes ROHC entity 1 and establishes and adopts ROHC entity 2.
  • the communication device uses one compression or decompression ROHC entity; otherwise, the communication device uses multiple compression or decompression ROHC. It is understandable that when the communication device uses one ROHC entity for compression or decompression, all the methods described in (2.1) to (2.2) above are applicable. When the communication device compresses or decompresses multiple ROHC entities, the methods described in (1.1) to (1.4) above are all applicable.
  • the PDCP configuration information may indicate that the communication device adopts the ROHC continuous function, and a PDCP entity of the communication device includes: a compression or decompression ROHC entity.
  • the PDCP configuration information does not indicate that the communication device adopts the ROHC continuous function
  • one PDCP entity of the communication device includes: multiple compression or decompression ROHC entities.
  • the indication information in the PDCP control packet may indicate at least one of the following:
  • the communication device deletes the previous compressed or decompressed ROHC entity, and establishes a new compressed or decompressed ROHC entity.
  • the method shown in FIG. 2 may further include:
  • the specific instruction method may include one or more of the following:
  • the specific indication manner may be configured by the network side or agreed by a protocol.
  • the configuration information of the PDCP identifier may include one or more of the following:
  • step 201 may include any one of the following:
  • step 201 may include any one of the following:
  • the PDCP identifier of the PDCP packet is before the designated PDCP identifier, the first compressed or decompressed ROHC entity is used;
  • the first compressed or decompressed ROHC entity is a specific compressed or decompressed ROHC entity established by the communication device according to configuration information of multiple compressed or decompressed ROHC entities.
  • the configuration information of the connection corresponding to the PDCP packet may include one or more of the following:
  • step 201 may include any one of the following:
  • connection corresponding to the PDCP packet is the first connection
  • the compressed or decompressed ROHC entity corresponding to the first connection is used.
  • step 201 may include one or more of the following:
  • step 201 may include:
  • the compression or decompression ROHC entity corresponding to the target connection is determined.
  • the method shown in FIG. 2 may further include one or more of the following:
  • the trigger event for completion of the mobility process includes one or more of the following:
  • the terminal receives the indication information that the mobility process is completed sent by the network side;
  • the terminal sends the indication information that the mobility process is completed to the network side;
  • the terminal receives an indication that the data processing of the source connection is complete.
  • the method shown in FIG. 2 may further include any one of the following:
  • the method shown in FIG. 2 may further include any one of the following:
  • step 201 optionally, after step 201, the method shown in FIG. 2 further includes any one of the following:
  • step 201 optionally, after step 201, the method shown in FIG. 2 further includes any one of the following:
  • the method shown in FIG. 2 may further include any one of the following:
  • the method shown in FIG. 2 may further include any one of the following:
  • the communication device when there are multiple compression or decompression ROHC entities working as a DRB (or PDCP) of the communication device on the network side, the communication device can still realize the header compression or decompression function.
  • the PDCP transmitter in the following embodiments may correspond to the UE and the PDCP transmitter on the network side
  • the PDCP receiver corresponds to the UE and the PDCP receiver on the network side, respectively.
  • Embodiment 1.1 The header of the PDCP packet indicates multiple compressed or decompressed ROHC entities.
  • Step 1 The network side configuration or protocol agreement, the UE adopts a packet header indication (for example, PDCP packet header indication information) to manage multiple compressed or decompressed ROHC entities.
  • a packet header indication for example, PDCP packet header indication information
  • Step 2 When the UE receives the configuration information of multiple compressed or decompressed ROHC entities of one PDCP entity, the UE establishes multiple compressed ROHC entities for uplink transmission, and the UE establishes multiple decompressed ROHC entities for downlink reception.
  • the source connection and the target connection are respectively configured with their corresponding compression or decompression ROHC entities (for example, compression or decompression ROHC1 and compression or decompression ROHC2), Then the UE establishes multiple compressed ROHC entities for uplink transmission, and the UE establishes multiple decompressed ROHC entities for downlink reception.
  • compression or decompression ROHC entities for example, compression or decompression ROHC1 and compression or decompression ROHC2
  • Step 3.1 According to step 2, the behavior of the PDCP receiver includes:
  • the PDCP receiver When the PDCP receiver receives a PDCP packet (for example, a PDCP data packet and/or an ROHC feedback packet), it adopts a specific ROHC entity indication information according to the PDCP protocol data unit (protocol data unit, PDU) of the PDCP packet header. Compress or decompress ROHC entities for processing.
  • a PDCP packet for example, a PDCP data packet and/or an ROHC feedback packet
  • PDU protocol data unit
  • the PDCP PDU header of the PDCP data packet indicates the decompression ROHC1 used for the PDCP data packet, and the PDCP receiving entity of the UE uses decompression ROHC1 to decompress the PDCP PDU header compression.
  • the header of the PDCP PDU of the ROHC feedback packet indicates the decompressed ROHC1 used by the header packet of the PDCP PDU, and the PDCP receiving entity of the UE uses the decompressed ROHC1 for the PDCP PDU
  • the header of the package is processed.
  • Step 3.2 According to step 1, the behavior of the PDCP sender includes:
  • the PDCP sender When the PDCP sender uses a specific compression or decompression ROHC entity for compression (or ROHC feedback packet (for example, "Control PDU for interspersed ROHC feedback") is sent), the PDCP sender indicates the compression used in the PDCP packet header sent Or decompress ROHC entities.
  • ROHC feedback packet for example, "Control PDU for interspersed ROHC feedback”
  • the PDCP sending entity of the UE sends data
  • the PDCP header compression of the data uses compressed ROHC1
  • the PDCP PDU header of the data indicates that compressed ROHC1 is adopted.
  • ROHC feedback packet eg, "Control PDU for interspersed ROHC feedback”
  • the PDCP PDU header of the ROHC feedback packet indicates Compressed ROHC1 is used.
  • the PDCP sender uses the compression or decompression ROHC entity corresponding to each connection for the data packets sent to each connection.
  • the PDCP sender of the UE uses compression or decompression ROHC1 for the data sent to the source connection.
  • Compress or decompress ROHC2 for the data sent to the target connection.
  • step 4 For the mobility process (for example, handover or secondary cell group change (SCG change)), after the UE completes the mobility process, the PDCP sending entity of the UE adopts the compression corresponding to the target connection Or decompress the ROHC entity (that is, no longer use the compressed or decompressed ROHC entity corresponding to the source connection).
  • SCG change secondary cell group change
  • the sending PDCP entity of the UE resets and/or deletes the compressed or decompressed ROHC entity corresponding to the source connection.
  • the trigger event for completion of the mobility process includes any combination of one or more of the following:
  • Mobility process completion indication information sent to the network side for example, the UE sends an indication message to delete the source connection to the network side;
  • the data of the source connection received by the PDCP sending entity is all processed, for example, decompression is completed, or decryption is completed, or sent to a higher layer.
  • Embodiment 1.2 The PDCP identifier indicates multiple compressed or decompressed ROHC entities.
  • Step 1 The network side configuration or protocol agreement, the UE uses the PDCP identifier (for example, PDCP SN or count (COUNT)) to indicate the management of multiple compressed or decompressed ROHC entities.
  • PDCP identifier for example, PDCP SN or count (COUNT)
  • the PDCP identification configuration information includes any one of the following:
  • the network side is configured to use compression or decompression ROHC1 before a designated PDCP SN (for example, 100), and then use compression or decompression ROHC2.
  • Step 2 When the UE receives the configuration information of multiple compressed or decompressed ROHC entities of one PDCP entity, the UE establishes multiple compressed ROHC entities for uplink transmission, and the UE establishes multiple decompressed ROHC entities for downlink reception.
  • the source connection and the target connection are respectively configured with their corresponding compression or decompression ROHC entities (for example, compression or decompression ROHC1 and compression or decompression ROHC2), Then the UE establishes multiple compressed ROHC entities for uplink transmission, and the UE establishes multiple decompressed ROHC entities for downlink reception.
  • compression or decompression ROHC entities for example, compression or decompression ROHC1 and compression or decompression ROHC2
  • Step 3.1 According to step 2, the behavior of the PDCP receiver includes:
  • the UE After the PDCP receiver receives a PDCP packet (for example, a PDCP data packet and/or an ROHC feedback packet), the UE uses a specific compression or decompression ROHC entity for processing according to the received PDCP packet identifier.
  • a PDCP packet for example, a PDCP data packet and/or an ROHC feedback packet
  • the UE uses a specific compression or decompression ROHC entity for processing according to the received PDCP packet identifier.
  • the packet header of the PDCP PDU indicates that the PDCP SN of the PDCP packet is the number before the configured PDCP SN, and the PDCP receiving entity of the UE compresses or decompresses the packet header of the PDCP PDU by ROHC1 Perform decompression, otherwise use compression or decompression ROHC2.
  • the PDCP receiving entity of the UE when the PDCP receiving entity of the UE receives the ROHC feedback packet, the PDCP SN of the PDCP packet received (or sent) before the ROHC feedback packet is the number before the configured PDCP SN number, then the PDCP receiving entity of the UE uses Compress or decompress ROHC1 to process the header of the PDCP PDU; otherwise, compress or decompress ROHC2.
  • Step 3.2 According to step 1, the behavior of the PDCP sender includes:
  • the UE uses a specific compression or decompression ROHC entity for processing according to the sent PDCP packet identifier.
  • the PDCP sending entity of the UE sends data
  • the PDCPSN of the PDCP data packet is the number before the configured PDCP SN
  • the PDCP receiving entity of the UE uses compression or decompression ROHC1 to compress the header of the PDCP PDU, otherwise Use compression or decompression ROHC2.
  • the PDCP sender determines the connection to which the data packet is sent according to the PDCP identifier for the data packet sent to each connection. For example, in the DC handover process, when the PDCP sending entity of the UE sends data, the PDCP SN of the data packet is the number before the configured PDCP SN number, then the UE sends the data packet through the source connection, otherwise through the target Connect to send.
  • step 4 For a mobility process (for example, handover or SCG change), after the UE completes the mobility process, the PDCP entity of the UE uses the compressed or decompressed ROHC entity corresponding to the target connection, that is, the source is no longer used Connect the corresponding compression or decompression ROHC entity.
  • a mobility process for example, handover or SCG change
  • the PDCP entity of the UE resets and/or deletes the compressed or decompressed ROHC entity corresponding to the source connection.
  • the trigger event for completion of the mobility process includes any combination of one or more of the following:
  • Mobility process completion indication information sent to the network side for example, the UE sends an indication message to delete the source connection to the network side;
  • the data of the source connection received by PDCP is all processed, for example, decompression is completed, or decryption is completed, or sent to the higher layer.
  • Embodiment 1.3 multiple compressed or decompressed ROHC entities, select the compressed or decompressed ROHC entity according to the connection corresponding to the PDCP package.
  • Step 1 The network side configuration or protocol agreement, the UE uses the connection corresponding to the PDCP packet to manage multiple compressed or decompressed ROHC entities.
  • connection configuration information corresponding to the PDCP packet includes: a specific compression or decompression ROHC entity corresponding to a specific connection.
  • the network side configuration uses decompression ROHC1 for the received data packets of connection 1, and the network side configuration uses compressed ROHC1 for the sent data packets of connection 1.
  • Step 2 When the UE receives the configuration information of multiple compressed or decompressed ROHC entities of one PDCP entity, the UE establishes multiple compressed ROHC entities for uplink transmission, and the UE establishes multiple decompressed ROHC entities for downlink reception.
  • the source connection and the target connection are configured with their corresponding compression or decompression ROHC entities (for example, compression or decompression ROHC1 and compression or decompression ROHC2), and the UE is
  • the uplink transmission establishes multiple compressed ROHC entities, and the UE establishes multiple decompressed ROHC entities for downlink reception.
  • Step 3.1 According to step 2, the behavior of the PDCP receiver includes:
  • the UE After the PDCP receiver receives the PDCP packet (for example, the PDCP data packet and/or the ROHC feedback packet), the UE uses a specific compression or decompression ROHC entity for processing according to the connection of the received PDCP packet.
  • the PDCP packet for example, the PDCP data packet and/or the ROHC feedback packet
  • the UE uses a specific compression or decompression ROHC entity for processing according to the connection of the received PDCP packet.
  • the PDCP receiving entity of the UE uses decompression ROHC1 to decompress the PDCP PDU header of the PDCP data packet.
  • the PDCP receiving entity of the UE uses the decompressed ROHC1 to process the PDCP PDU.
  • Step 3.2 According to step 1, the behavior of the PDCP sender includes:
  • the UE uses a specific compression or decompression ROHC entity for processing according to the connection of the sent PDCP packet.
  • the PDCP sending entity of the UE uses compression ROHC1 to compress the PDCP PDU of the PDCP data packet.
  • the ROHC feedback packet is a ROHC feedback packet for the received data packet of ROHC1, and the PDCP sending entity of the UE uses ROHC1 to compress the header of the ROHC PDCP PDU.
  • the ROHC feedback packet is sent to the connection corresponding to the compressed ROHC1.
  • the PDCP sender determines the connection to which the PDCP packet is sent according to the adopted compression or decompression ROHC entity.
  • the PDCP sending entity of the UE sends a PDCP packet, and the PDCP packet uses compressed ROHC1, the PDCP packet is sent through the connection corresponding to the compressed ROHC1.
  • step 4 For a mobility process (for example, handover or SCG change), after the UE completes the mobility process, the PDCP entity of the UE uses the compression or decompression ROHC entity corresponding to the target connection (ie, no longer uses the source Connect the corresponding compression or decompression ROHC entity).
  • a mobility process for example, handover or SCG change
  • the PDCP entity of the UE uses the compression or decompression ROHC entity corresponding to the target connection (ie, no longer uses the source Connect the corresponding compression or decompression ROHC entity).
  • the PDCP entity of the UE resets and/or deletes the compressed or decompressed ROHC entity corresponding to the source connection.
  • the trigger event for completion of the mobility process includes any combination of one or more of the following:
  • Mobility process completion indication information sent to the network side for example, the UE sends an indication message to delete the source connection to the network side;
  • the data of the source connection received by PDCP is all processed, for example, decompression is completed, or decryption is completed, or sent to the higher layer.
  • Embodiment 1.4 Transform multiple compressed or decompressed ROHC entities through PDCP control packets.
  • Step 1 Network side configuration or protocol agreement, UE adopts PDCP control packet to manage multiple compressed or decompressed ROHC entities.
  • the ROHC entity For example, after receiving the PDCP control packet, determine the ROHC entity to be subsequently compressed or decompressed according to the indication information of the PDCP control packet.
  • Step 2 When the UE receives the configuration information of multiple compressed or decompressed ROHC entities of one PDCP entity, the UE establishes multiple compressed ROHC entities for uplink transmission, and the UE establishes multiple decompressed ROHC entities for downlink reception.
  • the source connection and the target connection are configured with their corresponding compression or decompression ROHC entities (for example, compression or decompression ROHC1 and compression or decompression ROHC2), and the UE is
  • the uplink transmission establishes multiple compressed ROHC entities, and the UE establishes multiple decompressed ROHC entities for downlink reception.
  • Step 3 After receiving the ROHC entity change information (for example, a PDCP control packet) sent by the network side, the UE adopts the compressed or decompressed ROHC entity after the change.
  • the ROHC entity change information for example, a PDCP control packet
  • the PDCP control packet indicates the compression or decompression ROHC entity to be used by the PDCP, and the PDCP entity changes the compression or decompression ROHC entity it uses.
  • the UE when the UE sends the ROHC entity change information to the network side (or before or after), the compressed or decompressed ROHC entity after the change is used.
  • the PDCP control packet indicates the compression or decompression ROHC entity to be used by the PDCP, and the PDCP entity changes the compression used Or decompress ROHC entities.
  • the PDCP entity of the UE resets the compression or decompression ROHC entity when it changes the compression or decompression ROHC entity it uses (or before or after).
  • the PDCP entity of the UE changes the compressed or decompressed ROHC entity it uses (or before or after), it deletes the previously used compressed or decompressed ROHC entity.
  • Embodiment 2.1 Transform a compressed or decompressed ROHC entity through the PDCP control packet.
  • Step 1 Network side configuration or protocol agreement, UE adopts PDCP control packet to manage 1 compressed or decompressed ROHC entity.
  • the ROHC entity For example, after receiving the PDCP control packet, determine the ROHC entity to be subsequently compressed or decompressed according to the indication information of the PDCP control packet.
  • Step 2 When the UE receives the configuration information of multiple compressed or decompressed ROHC entities of one PDCP entity, it first uses one specific compressed or decompressed ROHC entity.
  • the source connection and the target connection are configured with their corresponding compression or decompression ROHC entities (for example, compression or decompression ROHC1 and compression or decompression ROHC2), then the UE For the uplink transmission, the compressed ROHC1 is first used, and the UE first uses the decompressed ROHC1 for the downlink reception.
  • compression or decompression ROHC entities for example, compression or decompression ROHC1 and compression or decompression ROHC2
  • Step 3 After receiving the ROHC entity change information (for example, PDCP control packet) sent by the network side, the UE adopts (or establishes) the changed compressed or decompressed ROHC entity.
  • the ROHC entity change information for example, PDCP control packet
  • a PDCP entity of the UE receives a PDCP control packet, and the PDCP control packet indicates the compression or decompression ROHC entity to be used by PDCP, then the PDCP entity changes the compression or decompression ROHC entity it uses.
  • the UE uses (or establishes) the changed compressed or decompressed ROHC entity when sending (or before or after) the compressed or decompressed ROHC entity change information to the network side.
  • the PDCP control packet indicates the compression or decompression ROHC entity to be used by the PDCP, and the PDCP entity changes the compression used Or decompress ROHC entities.
  • the PDCP entity of the UE resets the ROHC entity when (or before or after) the compression or decompression ROHC entity it uses.
  • the PDCP entity of the UE changes the ROHC entity used for compression or decompression (or before or after), the previously used ROHC entity is deleted.
  • the PDCP entity of the UE changes its compressed or decompressed ROHC entity (or before or after), if the ROHC continuous function (for example, drb-ContinueROHC) is configured on the network side, the PDCP entity of the UE does not Set to compress or decompress ROHC entities.
  • the ROHC continuous function for example, drb-ContinueROHC
  • the PDCP entity of the UE changes the ROHC entity it uses (or before, or after), if the network side is not configured to compress or decompress the ROHC continuous function (for example, drb-ContinueROHC), the PDCP entity of the UE is reset Compress or decompress ROHC entities.
  • the ROHC continuous function for example, drb-ContinueROHC
  • Embodiment 2.2 PDCP identification transforms 1 compressed or decompressed ROHC entity.
  • Step 1 Network side configuration or agreement agreement, UE adopts PDCP identification (for example, PDCP SN or COUNT) to manage 1 compressed or decompressed ROHC entity.
  • PDCP identification for example, PDCP SN or COUNT
  • the PDCP identification configuration information includes any one of the following:
  • the network side is configured to use compression or decompression ROHC1 before the designated PDCP SN (for example, 100), and then use compression or decompression ROHC2.
  • Step 2 When the UE receives the configuration information of multiple compressed or decompressed ROHC entities of one PDCP entity, it first uses one specific compressed or decompressed ROHC entity.
  • the source connection and the target connection are configured with their corresponding compression or decompression ROHC entities (for example, compression or decompression ROHC1 and compression or decompression ROHC2), then the UE For the uplink transmission, the compressed ROHC1 is first used, and the UE first uses the decompressed ROHC1 for the downlink reception.
  • compression or decompression ROHC entities for example, compression or decompression ROHC1 and compression or decompression ROHC2
  • Step 3 After receiving the corresponding PDCP identification information sent by the network side, the UE adopts (or establishes) the changed compressed or decompressed ROHC entity.
  • the PDCP receiving entity of the UE uses the decompressed ROHC1 to process the PDCP PDU, otherwise, the decompressed ROHC2 is used.
  • the UE adopts (or establishes) the changed compressed or decompressed ROHC entity according to the corresponding PDCP identification information sent to the network side.
  • the PDCP receiving entity of the UE uses compressed ROHC1 to process the PDCP PDU, otherwise, uses compressed ROHC2.
  • the PDCP entity of the UE resets the previously used compression or decompression ROHC entity when it changes the compression or decompression ROHC entity it uses (or before or after).
  • the PDCP entity of the UE changes the compressed or decompressed ROHC entity it uses (or before or after), it deletes the previously used compressed or decompressed ROHC entity.
  • the PDCP entity of the UE changes the ROHC entity it uses (or before, or after), if the network side is configured with the ROHC continuous function (for example, drb-ContinueROHC), the PDCP entity of the UE does not reset the previously used ROHC entity Compress or decompress ROHC entities.
  • the ROHC continuous function for example, drb-ContinueROHC
  • the PDCP entity of the UE changes the ROHC entity it uses (or before, or after), if the network side does not configure the ROHC continuous function (for example, drb-ContinueROHC), the PDCP entity of the UE resets the compression used before Or decompress ROHC entities.
  • the ROHC continuous function for example, drb-ContinueROHC
  • Embodiment 2.3 Transform a compressed or decompressed ROHC entity by transforming the connection corresponding to the PDCP packet
  • Step 1 The network side configuration or protocol agreement, the UE uses the connection corresponding to the PDCP packet to manage a compressed or decompressed ROHC entity.
  • connection configuration information corresponding to the PDCP packet includes: a specific compression or decompression ROHC entity corresponding to a specific connection.
  • the network side configuration uses decompression ROHC1 for the received data packets of connection 1, and the network side configuration uses compressed ROHC1 for the sent data packets of connection 1.
  • Step 2 When the UE receives the configuration information of multiple compressed or decompressed ROHC entities of one PDCP entity, it first uses one specific compressed or decompressed ROHC entity.
  • the source connection and the target connection are configured with their corresponding compression or decompression ROHC entities (for example, compression or decompression ROHC1 and compression or decompression ROHC2), then the UE For the uplink transmission, the compressed ROHC1 is first used, and the UE first uses the decompressed ROHC1 for the downlink reception.
  • compression or decompression ROHC entities for example, compression or decompression ROHC1 and compression or decompression ROHC2
  • Step 3.1 According to step 2, the behavior of the PDCP receiver includes:
  • the UE After the PDCP receiver receives the PDCP packet (for example, the PDCP data packet and/or the ROHC feedback packet), the UE uses a specific decompressed ROHC entity for processing according to the connection of the received PDCP packet.
  • the PDCP packet for example, the PDCP data packet and/or the ROHC feedback packet
  • the UE uses a specific decompressed ROHC entity for processing according to the connection of the received PDCP packet.
  • the PDCP receiving entity of the UE when the PDCP receiving entity of the UE receives the PDCP data packet, the PDCP data packet is from the source connection, and the PDCP receiving entity of the UE uses the decompression ROHC1 corresponding to the source connection to decompress the PDCP PDU header of the PDCP data packet .
  • the PDCP entity changes the previously used compression or decompression ROHC entity.
  • the PDCP receiving entity of the UE uses the decompressed ROHC1 corresponding to connection 1 to decompress the packet header of the PDCP PDU.
  • Step 3.2 According to step 1, the behavior of the PDCP sender includes:
  • the UE uses a specific compressed ROHC entity for processing according to the connection of the sent PDCP packets.
  • PDCP packets for example, PDCP data packets and/or ROHC feedback packets
  • the PDCP sending entity of the UE when the PDCP sending entity of the UE sends the PDCP data packet, the PDCP data packet is sent through the source connection, and the PDCP sending entity of the UE uses the compression ROHC1 corresponding to the source connection to compress the PDCP PDU of the PDCP data packet.
  • the PDCP entity changes the previously used compression or decompression ROHC entity.
  • the ROHC feedback packet is a ROHC feedback packet for compressing the received data packet of ROHC1
  • the PDCP sending entity of the UE uses ROHC1 to compress the header of the PDCP PDU
  • the ROHC feedback packet is sent to the connection corresponding to the compressed ROHC1.
  • the PDCP entity of the UE resets the previously used compression or decompression ROHC entity when it changes the compression or decompression ROHC entity it uses (or before or after).
  • the PDCP entity of the UE changes the compressed or decompressed ROHC entity it uses (or before or after), it deletes the previously used compressed or decompressed ROHC entity.
  • the PDCP entity of the UE changes the ROHC entity it uses (or before or after), it resets the previously used compressed or decompressed ROHC entity.
  • the PDCP entity of the UE changes the ROHC entity used for compression or decompression (or before, or after), if the network side is configured with the ROHC continuous function (for example, drb-ContinueROHC), the PDCP entity of the UE is not repeated Set the previously used compression or decompression ROHC entity.
  • the ROHC continuous function for example, drb-ContinueROHC
  • the PDCP entity of the UE changes its compressed or decompressed ROHC entity (or before, or after), if the network side is not configured with ROHC continuous function (for example, drb-ContinueROHC), the PDCP entity of the UE is reset The previously used compression or decompression ROHC entity.
  • ROHC continuous function for example, drb-ContinueROHC
  • the PDCP sender judges the connection to which the PDCP packet is sent according to the adopted compression ROHC entity.
  • the PDCP sending entity of the UE sends a PDCP packet, and the PDCP packet uses compressed ROHC1, the PDCP packet is sent through the connection corresponding to the compressed ROHC1.
  • step 4 For a mobility process (for example, handover or SCG change), after the UE completes the mobility process, the PDCP entity of the UE uses the compression or decompression ROHC entity corresponding to the target connection (ie, no longer uses the source Connect the corresponding compression or decompression ROHC entity).
  • a mobility process for example, handover or SCG change
  • the PDCP entity of the UE uses the compression or decompression ROHC entity corresponding to the target connection (ie, no longer uses the source Connect the corresponding compression or decompression ROHC entity).
  • the PDCP entity of the UE resets and/or deletes the compressed or decompressed ROHC entity corresponding to the source connection.
  • the trigger event for completion of the mobility process includes any combination of one or more of the following:
  • Mobility process completion indication information sent to the network side for example, the UE sends an indication message to delete the source connection to the network side;
  • the data of the source connection received by PDCP is all processed, for example, decompression is completed, or decryption is completed, or sent to the higher layer.
  • Embodiment 3 The ROHC continuous function control is configured through the network side, whether one or multiple compressed or decompressed ROHC entities are used.
  • Step 1 The network side configures the ROHC continuous function (for example, drb-ContinueROHC) to control whether one PDCP entity of the UE establishes one compressed or decompressed ROHC at the same time or establishes multiple compressed or decompressed ROHC entities.
  • the ROHC continuous function for example, drb-ContinueROHC
  • Step 2 According to the configuration information of step 1.
  • the behavior of the UE includes any of the following:
  • the PDCP entity uses 1 compressed or decompressed ROHC entity at the same time, and the compression or change in example 2.1 or 2.2 may not be used. Decompress the function of ROHC entities.
  • the UE If the PDCP configuration information does not indicate the use of the ROHC continuous function, and the UE receives the configuration information of multiple compressed or decompressed ROHC entities of one PDCP entity, the UE establishes multiple compressed ROHC entities for uplink transmission. The downlink reception establishes multiple decompressed ROHC entities.
  • the PDCP entity uses 1 compression or decompression ROHC entity at the same time, and the compression or change in Example 2.1 or 2.2 can be used Decompress the function of ROHC entities.
  • the UE behavior is the same as in Examples 1.1, 1.2, 1.3 and 1.4, and the description is not repeated here.
  • the embodiment of the present disclosure also provides a communication device. Since the principle of the communication device to solve the problem is similar to the processing method in the embodiment of the present disclosure, the implementation of the communication device can refer to the implementation of the method, and the repetition will not be repeated.
  • an embodiment of the present disclosure also provides a communication device, such as a terminal or a network device, and the communication device 300 includes:
  • the first determining module 301 is configured to determine the compression or decompression ROHC entity according to the first information
  • the first information is one or more of the following: indication information in the header of the PDCP packet; information about the completion of the mobility process; PDCP identifier of the PDCP packet; connection corresponding to the PDCP packet; indication information in the PDCP control packet ; PDCP configuration information; compress or decompress the configuration information of the ROHC entity.
  • the PDCP configuration information indicates that the communication device adopts ROHC continuous function
  • the PDCP entity of the communication device includes: a compression or decompression ROHC entity; or,
  • the PDCP configuration information does not indicate that the communication device adopts the ROHC continuous function, and the PDCP entity of the communication device includes: multiple compressed or decompressed ROHC entities.
  • the indication information in the PDCP control packet indicates at least one of the following:
  • the communication device changes the compression or decompression ROHC entity
  • the communication device does not change the compression or decompression ROHC entity
  • the communication device deletes the previous compressed or decompressed ROHC entity, and establishes a new compressed or decompressed ROHC entity.
  • the communication device 300 further includes a second determining module, configured to determine the corresponding first information according to a specific indication manner;
  • the specific instruction method includes one or more of the following:
  • the PDCP packet corresponds to the configuration information indication of the connection
  • the specific indication manner is configured by the network side or agreed by a protocol.
  • the configuration information of the PDCP identifier includes one or more of the following:
  • the first determining module 301 is further configured to perform any one of the following:
  • the PDCP identifier of the PDCP packet is before the designated PDCP identifier, use the corresponding compressed or decompressed ROHC entity;
  • the PDCP identifier of the PDCP packet is after the designated PDCP identifier, the corresponding compressed or decompressed ROHC entity is used.
  • the first determining module 301 is further configured to perform any one of the following:
  • the first compressed or decompressed ROHC entity is used
  • the PDCP identifier of the PDCP packet is after the designated PDCP identifier, delete the first compressed or decompressed ROHC entity, and establish and adopt a new compressed or decompressed ROHC entity;
  • the first compressed or decompressed ROHC entity is a specific compressed or decompressed ROHC entity established by the communication device according to configuration information of multiple compressed or decompressed ROHC entities.
  • the configuration information of the connection corresponding to the PDCP packet includes one or more of the following:
  • the first determining module 301 is further configured to:
  • connection corresponding to the PDCP packet is the first connection
  • the compressed or decompressed ROHC entity corresponding to the first connection is used.
  • the first determining module 301 is further configured to perform one or more of the following:
  • a specific compressed or decompressed ROHC entity is established.
  • the first determining module 301 is further configured to determine the compression or decompression ROHC entity corresponding to the target connection according to the completed information of the mobility process after the mobility process is completed.
  • the communication device 300 further includes a first processing module configured to perform one or more of the following:
  • the trigger event for completion of the mobility process includes one or more of the following:
  • the terminal receives the indication information that the mobility process is completed sent by the network side;
  • the terminal sends the indication information that the mobility process is completed to the network side;
  • the terminal receives the information indicating that the data processing of the source connection is complete.
  • the communication device 300 further includes a second processing module configured to perform any one of the following:
  • the communication device 300 further includes a third processing module, and the third processing module is configured to perform any one of the following:
  • the header of the PDCP packet is compressed or decompressed by the changed compression or decompression ROHC entity.
  • the communication device 300 further includes a fourth processing module, and the fourth processing module is configured to perform any one of the following:
  • the PDCP configuration information instructs the communication device to use the ROHC continuous function, the previously used compression or decompression ROHC entity is not reset;
  • the PDCP configuration information indicates that the communication device adopts the ROHC continuous function, the previously used compression or decompression ROHC entity is not reset.
  • the communication device 300 further includes a fifth processing module, and the fifth processing module is configured to perform any one of the following:
  • the communication device 300 further includes a sixth processing module, and the sixth processing module is configured to perform any one of the following:
  • the communication device 300 further includes a seventh processing module, and the seventh processing module is configured to perform any one of the following:
  • the communication device provided in the embodiments of the present disclosure can execute the foregoing method embodiments, and its implementation principles and technical effects are similar, and details are not described herein again in this embodiment.
  • FIG. 4 is a structural diagram of a communication device applied in an embodiment of the present disclosure.
  • the communication device 400 includes a processor 401, a transceiver 402, a memory 403, and a bus interface, where:
  • the communication device 400 further includes: a program stored in the memory 403 and capable of running on the processor 401.
  • the program When the program is executed by the processor 401, the following steps are implemented: Determine the compression or Decompress the ROHC entity; where the first information is one or more of the following: indication information in the header of the PDCP packet; information about the completion of the mobility process; the PDCP identifier of the PDCP packet; the connection corresponding to the PDCP packet; PDCP control The indication information in the package; PDCP configuration information; the configuration information of the ROHC entity that is compressed or decompressed.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 401 and various circuits of the memory represented by the memory 403 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further description will be given herein.
  • the bus interface provides the interface.
  • the transceiver 402 may be a plurality of elements, that is, including a transmitter and a receiver, and provide a unit 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 by the processor 401 when performing operations.
  • the communication device provided in the embodiments of the present disclosure can execute the foregoing method embodiments, and its implementation principles and technical effects are similar, and details are not described herein again in this embodiment.
  • the steps of the method or algorithm described in connection with the disclosure of the present disclosure may be implemented in a hardware manner, or may be implemented in a manner of executing software instructions on a processor.
  • Software instructions can be composed of corresponding software modules, which can be stored in random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read-Only Memory, ROM), erasable programmable read-only memory (Erasable PROM, EPROM), Electrically Erasable Programmable Read-Only Memory (Electrically EPROM, EEPROM), registers, hard disks, mobile hard disks, CD-ROMs, or any other form of storage medium known in the art.
  • RAM Random Access Memory
  • ROM read-only memory
  • EPROM erasable programmable read-only memory
  • Electrically Erasable Programmable Read-Only Memory Electrically Erasable Programmable Read-Only Memory
  • registers hard disks, mobile hard disks, CD-ROMs, or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium can be carried in an ASIC.
  • the ASIC can be carried in the core network interface device.
  • the processor and the storage medium may also exist as discrete components in the core network interface device.
  • Computer readable media include computer storage media and communication media, where communication media includes any media that facilitates the transfer of computer programs from one place to another.
  • the storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.
  • the disclosed device and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present disclosure can be embodied in the form of a software product in essence or a part that contributes to the related technology.
  • the computer software product is stored in a storage medium and includes several instructions to make a A computer device (which may be a personal computer, a server, or a network device, etc.) executes all or part of the steps of the methods described in the various embodiments of the present disclosure.
  • the aforementioned storage media include: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk and other media that can store program codes.
  • the program can be stored in a computer readable storage medium. When executed, it may include the procedures of the above-mentioned method embodiments.
  • the storage medium may be a magnetic disk, an optical disc, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM), etc.
  • the embodiments described in the embodiments of the present disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (Digital Signal Processor, DSP), digital signal processing equipment (DSP Device, DSPD), programmable Logic device (Programmable Logic Device, PLD), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, and others for performing the functions described in this disclosure Electronic unit or its combination.
  • ASICs application specific integrated circuits
  • DSP digital signal processors
  • DSP Device digital signal processing equipment
  • PLD programmable Logic Device
  • PLD Field-Programmable Gate Array
  • FPGA Field-Programmable Gate Array
  • the technology described in the embodiments of the present disclosure can be implemented by modules (for example, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure.
  • the software codes can be stored in the memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.
  • the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the embodiments of the present disclosure may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of the present disclosure may use one or more computer-usable storage media containing computer-usable program codes (including but not limited to disk storage, CD-ROM (Compact Disc Read-Only Memory), CD-ROM), Optical storage, etc.) in the form of a computer program product implemented on it.
  • computer-usable storage media including but not limited to disk storage, CD-ROM (Compact Disc Read-Only Memory), CD-ROM), Optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Compression, Expansion, Code Conversion, And Decoders (AREA)

Abstract

本公开实施例提供一种处理方法及通信设备，该方法包括：根据第一信息，确定压缩或解压缩ROHC实体；其中，所述第一信息为以下任意一项：PDCP包的包头中的指示信息；移动性过程完成的信息；PDCP包的PDCP标识；PDCP包对应的连接；PDCP控制包中的指示信息；PDCP配置信息；压缩或解压缩ROHC实体的配置信息。

Description

处理方法及通信设备
相关申请的交叉引用
本申请主张在2019年1月30日在中国提交的中国专利申请号No.201910093599.0的优先权，其全部内容通过引用包含于此。
技术领域
本公开实施例涉及通信技术领域，具体涉及一种处理方法及通信设备。
背景技术
当网络侧有多个压缩(或解压缩)鲁棒头压缩(Robust Header Compression，ROHC)实体为终端的一个数据无线承载(Data Radio Bearer，DRB)(或包数据汇聚协议(Packet Data Convergence Protocol，PDCP))工作的时候，如何实现终端侧和网络侧的包头压缩或解压缩是亟需解决的问题。
发明内容
本公开实施例的一个目的在于提供一种处理方法及通信设备，解决终端侧和网络侧的包头压缩或解压缩的问题。
依据本公开实施例的第一方面，提供了一种处理方法，应用于通信设备，所述方法包括：
根据第一信息，确定压缩或解压缩鲁棒头压缩ROHC实体；
其中，所述第一信息为以下一项或多项：包数据汇聚协议PDCP包的包头中的指示信息；移动性过程完成的信息；PDCP包的PDCP标识；PDCP包对应的连接；PDCP控制包中的指示信息；PDCP配置信息；压缩或解压缩ROHC实体的配置信息。
依据本公开实施例的第二方面，还提供一种通信设备，包括：
确定模块，用于根据第一信息，确定压缩或解压缩ROHC实体；
其中，所述第一信息为以下一项或多项：PDCP包的包头中的指示信息；移动性过程完成的信息；PDCP包的PDCP标识；PDCP包对应的连接；PDCP 控制包中的指示信息；PDCP配置信息；压缩或解压缩ROHC实体的配置信息。
依据本公开实施例的第三方面，还提供了一种通信设备，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序，所述程序被所述处理器执行时实现如上所述的处理方法的步骤。
依据本公开实施例的第四方面，还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如上所述的处理方法的步骤。
在本公开实施例中，可以在网络侧有多个压缩或解压缩ROHC实体为终端的一个DRB(或PDCP)工作时，终端侧和网络侧仍然能够实现包头压缩或解压缩功能。
附图说明
通过阅读下文可选实施方式的详细描述，各种其他的优点和益处对于本领域普通技术人员将变得清楚明了。附图仅用于示出可选实施方式的目的，而并不认为是对本公开的限制。而且在整个附图中，用相同的参考符号表示相同的部件。在附图中：
图1为本公开实施例的无线通信系统的架构示意图；
图2为本公开实施例的处理方法的流程图；
图3为本公开实施例的通信设备的结构图之一；
图4为本公开实施例的通信设备的结构图之二。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
本申请的说明书和权利要求书中的术语“包括”以及它的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、 系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。此外，说明书以及权利要求中使用“和/或”表示所连接对象的至少其中之一，例如A和/或B，表示包含单独A，单独B，以及A和B都存在三种情况。
在本公开实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本公开实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更可选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
为了便于理解本公开实施例的技术方案，下面介绍几个技术点：
一、关于鲁棒头压缩或稳健头压缩(Robust Header Compression，ROHC)的介绍。
在长期演进(Long Term Evolution，LTE)或第五代移动通信(5th-generation，5G)新空口(New Radio，NR)系统中，网络侧可以在包数据汇聚协议(PacketData Convergence Protocol，PDCP)实体中配置ROHC功能。该ROHC功能在PDCP实体内对应最多1个ROHC压缩(比如，终端侧对应上行数据发送)实体(或模块，或协议层，或上下文)和最多1个ROHC解压缩(比如，终端侧对应下行数据接收)实体(或模块，或协议层，或上下文)。ROHC实体可以对高层数据包(比如，传输控制协议(Transmission Control Protocol，TCP)/互联网协议(Internet Protocol，IP))的包头进行压缩和解压缩，同时ROHC解压缩实体可以对解压缩的状态发送反馈信息给对端的ROHC压缩实体。
在切换过程中，网络侧可以配置(即，通过DRB ROHC连续(drb-ContinueROHC)信令指示)是否该PDCP实体的ROHC实体需要重置。
比如，网络侧希望在切换过程中终端仍然采用切换前的ROHC实体，则给终端配置drb-ContinueROHC，则终端不重置其ROHC，而继续使用切换前的ROHC实体。
二、关于双连接(Dual connectivity，DC)切换的介绍。
在5G系统中，由于要满足0ms的移动性过程的中断延时，因此需要终端在移动的过程中同时在源节点和目标节点有连接进行数据的收发。要在源节点和目标节点同时保持数据连接。对应的网络侧的源节点和目标节点有独 立的ROHC压缩或解压缩实体。
本文所描述的技术不限于5G系统以及后续演进通信系统，以及不限于LTE/LTE的演进(LTE-Advanced，LTE-A)系统，并且也可用于各种无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access，SC-FDMA)和其他系统。
术语“系统”和“网络”常被可互换地使用。CDMA系统可实现诸如CDMA2000、通用地面无线电接入(Universal Terrestrial Radio Access，UTRA)等无线电技术。UTRA包括宽带CDMA(Wideband Code Division Multiple Access，WCDMA)和其他CDMA变体。TDMA系统可实现诸如全球移动通信系统(Global System for Mobile Communication，GSM)之类的无线电技术。OFDMA系统可实现诸如超移动宽带(Ultra Mobile Broadband，UMB)、演进型UTRA(Evolution-UTRA，E-UTRA)、IEEE 802.11(无线保真(wireless fidelity，Wi-Fi))、IEEE 802.16(全球微波接入互操作性(World Interoperability for Microwave Access，WiMAX))、IEEE 802.20、Flash-OFDM等无线电技术。UTRA和E-UTRA是通用移动电信系统(Universal Mobile Telecommunications System，UMTS)的部分。LTE和更高级的LTE(如LTE-A)是使用E-UTRA的新UMTS版本。UTRA、E-UTRA、UMTS、LTE、LTE-A以及GSM在来自名为“第三代伙伴项目”(3rd Generation Partnership Project，3GPP)的组织的文献中描述。CDMA2000和UMB在来自名为“第三代伙伴项目2”(3GPP2)的组织的文献中描述。本文所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。
下面结合附图介绍本公开的实施例。本公开实施例提供的处理方法和设备可以应用于无线通信系统中。参考图1，为本公开实施例提供的一种无线通信系统的架构示意图。如图1所示，该无线通信系统可以包括：第一网络设备10、第二网络设备11和终端，终端记做用户设备(User Equipment，UE)12，UE 12可以与第一网络设备10和第二网络设备11通信(传输信令或传 输数据)。在实际应用中上述各个设备之间的连接可以为无线连接，为了方便直观地表示各个设备之间的连接关系，图1中采用实线示意。需要说明的是，上述通信系统可以包括多个UE 12，第一网络设备10和第二网络设备11可以与多个UE 12通信。
本公开实施例提供的终端可以为手机、平板电脑、笔记本电脑、超级移动个人计算机(Ultra-Mobile Personal Computer，UMPC)、上网本或者个人数字助理(Personal Digital Assistant，PDA)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备等。
本公开实施例提供的第一网络设备10和第二网络设备11可以为基站，该基站可以为通常所用的基站，也可以为演进型基站(evolved node base station，eNB)，还可以为5G系统中的网络设备(例如，下一代基站(next generation node base station，gNB)或发送和接收点(transmission and reception point，TRP))等设备。
在本公开实施例中，ROHC实体也可以称为ROHC模块、ROHC协议层或者ROHC上下文。
参见图2，本公开实施例还提供一种处理方法，该方法的执行主体可以为通信设备，例如终端或网络设备，该方法包括步骤201。
步骤201：根据第一信息，确定压缩或解压缩ROHC实体；
其中，所述第一信息可以为以下一项或多项：PDCP包的包头中的指示信息；移动性过程完成的信息；PDCP包的PDCP标识；PDCP包对应的连接；PDCP控制包中的指示信息；PDCP配置信息；压缩或解压缩ROHC实体的配置信息。
需要说明的是，上述PDCP包可以是PDCP数据包和/或ROHC反馈包。
如果通信设备有多个压缩或解压缩ROHC实体，示例性地：
(1.1)在PDCP包头中添加指示信息，指示是使用的ROHC实体。
(1.2)如果PDCP包的序列号在指定的PDCP序列号(Serial Number，SN)之前，通信设备采用ROHC实体1，在指定的PDCP SN号之后，通信设备采用ROHC实体2。
(1.3)对于来自连接1的PDCP包采用与连接1相关的ROHC实体1， 对于来自连接2的PDCP包采用与连接2相关的ROHC实体2。
(1.4)PDCP控制包中的指示信息，指示是否变更通信设备使用的ROHC实体。
如果通信设备有1个ROHC实体，示例性地：
(2.1)PDCP控制包中的指示信息：指示通信设备删除之前(旧)的ROHC实体，并建立新的ROHC实体。
(2.2)在指定的PDCP SN号之前，通信设备采用ROHC实体1，在指定的PDCP SN号之后，通信设备删除ROHC实体1，建立并采用ROHC实体2。
示例性地，当通信设备采用ROHC连续(ROHC Continue)功能时，通信设备采用1个压缩或解压缩ROHC实体；否则通信设备采用多个压缩或解压缩ROHC。可以理解的是，当通信设备采用1个压缩或解压缩ROHC实体的时候，上述(2.1)～(2.2)所描述的方式都适用。当通信设备多个压缩或解压缩ROHC实体的时候，上述(1.1)～(1.4)所描述的方式都适用。
在本公开实施例中，可选地，PDCP配置信息可以指示所述通信设备采用ROHC连续功能，所述通信设备的一个PDCP实体包括：一个压缩或解压缩ROHC实体。
在本公开实施例中，可选地，PDCP配置信息不指示通信设备采用ROHC连续功能，所述通信设备的一个PDCP实体包括：多个压缩或解压缩ROHC实体。
在本公开实施例中，可选地，所述PDCP控制包中的指示信息可以指示以下至少一项：
(1)通信设备变更压缩或解压缩ROHC实体；
(2)通信设备不变更压缩或解压缩ROHC实体；
(3)通信设备删除之前的压缩或解压缩ROHC实体，并建立新的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，在步骤201之前，图2所示的方法还可以包括：
根据特定的指示方式，确定对应的所述第一信息；
其中，所述特定的指示方式可以包括以下一项或多项：
(1)PDCP包的包头指示；
(2)PDCP包的PDCP标识的配置信息指示；
(3)PDCP包对应连接的配置信息指示；
(4)PDCP控制包指示。
在本公开实施例中，可选地，所述特定的指示方式可以由网络侧配置或者由协议约定。
在本公开实施例中，可选地，所述PDCP标识的配置信息可以包括以下一项或多项：
(1)指定的PDCP包标识；
(2)在所述指定的PDCP包标识之前采用的压缩或解压缩ROHC实体；
(3)在所述指定的PDCP包标识之后采用的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，如果通信设备的PDCP实体包括：多个压缩或解压缩ROHC实体，步骤201可以包括以下任意一项：
(1)如果所述PDCP包的PDCP标识在指定的PDCP标识之前，则采用对应的压缩或解压缩ROHC实体；
(2)如果所述PDCP包的PDCP标识在指定的PDCP标识之后，则采用对应的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，如果通信设备的PDCP实体包括：一个压缩或解压缩ROHC实体，步骤201可以包括以下任意一项：
(1)如果所述PDCP包的PDCP标识在指定的PDCP标识之前，则采用第一压缩或解压缩ROHC实体；
(2)如果所述PDCP包的PDCP标识在指定的PDCP标识之后，则删除第一压缩或解压缩ROHC实体，建立并采用新的压缩或解压缩ROHC实体；
其中，所述第一压缩或解压缩ROHC实体为所述通信设备根据多个压缩或解压缩ROHC实体的配置信息建立的一个特定的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，所述PDCP包对应连接的配置信息可以包括以下一项或多项：
(1)特定连接与特定压缩ROHC实体的对应关系；
(2)特定连接与特定解压缩ROHC实体的对应关系。
在本公开实施例中，可选地，步骤201可以包括以下任意一项：
如果所述PDCP包对应的连接为第一连接，则采用所述第一连接对应的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，步骤201可以包括以下一项或多项：
(1)根据多个压缩或解压缩ROHC实体的配置信息，建立多个压缩或解压缩ROHC实体；
(2)根据一个压缩或解压缩ROHC实体的配置信息，建立一个特定的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，步骤201可以包括：
在移动性过程完成后，根据移动性过程完成的信息，确定目标连接对应的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，在步骤201之后，图2所示的方法还可以包括以下一项或多项：
(1)将源连接对应的压缩或解压缩ROHC实体进行重置；
(2)将源连接对应的压缩或解压缩ROHC实体删除。
在本公开实施例中，可选地，所述移动性过程完成的触发事件包括以下一项或多项：
(1)终端接收到网络侧发送的移动性过程完成的指示信息；
(2)终端向网络侧发送移动性过程完成的指示信息；
(3)目标连接的随机接入过程完成；
(4)终端接收到源连接的数据处理完成的指示信息。
在本公开实施例中，可选地，在步骤201之后，图2所示的方法还可以包括以下任意一项：
(1)根据PDCP包的PDCP标识，确定发送PDCP包的连接；
(2)根据压缩PDCP包的压缩ROHC实体，确定发送PDCP包的连接。
在本公开实施例中，可选地，在步骤201之后，图2所示的方法还可以包括以下任意一项：
(1)在发送ROHC实体变更信息时，通过变更后的压缩或解压缩ROHC 实体对PDCP包的包头进行压缩或解压缩；
(2)在发送ROHC实体变更信息之前，通过变更后的压缩或解压缩ROHC实体对PDCP包的包头进行压缩或解压缩；
(3)在发送ROHC实体变更信息之后，通过变更后的压缩或解压缩ROHC实体对PDCP包的包头进行压缩或解压缩。
在本公开实施例中，可选地，在步骤201之后，图2所示的方法还包括以下任意一项：
(1)在变更使用的压缩或解压缩ROHC实体时，如果所述PDCP配置信息指示所述通信设备采用ROHC连续功能，不重置之前使用的压缩或解压缩ROHC实体；
(2)在变更使用的压缩或解压缩ROHC实体之前，如果所述PDCP配置信息指示所述通信设备采用ROHC连续功能，不重置之前使用的压缩或解压缩ROHC实体；
(3)在变更使用的压缩或解压缩ROHC实体之后，如果所述PDCP配置信息指示所述通信设备采用ROHC连续功能，不重置之前使用的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，在步骤201之后，图2所示的方法还包括以下任意一项：
(1)在变更使用的压缩或解压缩ROHC实体时，如果所述PDCP配置信息没有指示所述通信设备采用ROHC连续功能，对之前使用的压缩或解压缩ROHC实体进行重置；
(2)在变更使用的压缩或解压缩ROHC实体之前，如果所述PDCP配置信息没有指示所述通信设备采用ROHC连续功能，对之前使用的压缩或解压缩ROHC实体进行重置；
(3)在变更使用的压缩或解压缩ROHC实体之后，如果所述PDCP配置信息没有指示所述通信设备采用ROHC连续功能，对之前使用的压缩或解压缩ROHC实体进行重置。
在本公开实施例中，可选地，在步骤201之后，图2所示的方法还可以包括以下任意一项：
(1)在变更使用的压缩或解压缩ROHC实体时，对之前使用的压缩或解压缩ROHC实体进行重置；
(2)在变更使用的压缩或解压缩ROHC实体之前，对之前使用的压缩或解压缩ROHC实体进行重置；
(3)在变更使用的压缩或解压缩ROHC实体之后，对之前使用的压缩或解压缩ROHC实体进行重置。
在本公开实施例中，可选地，在步骤201之后，图2所示的方法还可以包括以下任意一项：
(1)在变更使用的压缩或解压缩ROHC实体时，将之前使用的压缩或解压缩ROHC实体删除；
(2)在变更使用的压缩或解压缩ROHC实体之前，将之前使用的压缩或解压缩ROHC实体删除；
(3)在变更使用的压缩或解压缩ROHC实体之后，将之前使用的压缩或解压缩ROHC实体删除。
在本公开实施例中，可以在网络侧有多个压缩或解压缩ROHC实体为通信设备的一个DRB(或PDCP)工作时，通信设备仍然能够实现包头压缩或解压缩功能。
为了便于更好的理解本公开实施例，以下实施例中PDCP发送端可以分别对应UE和网络侧的PDCP发送端，PDCP接收端分别对应UE和网络侧的PDCP接收端。
实施例1.1：PDCP包的包头指示多个压缩或解压缩ROHC实体。
步骤1：网络侧配置或协议约定，UE采用包头指示(比如，PDCP包头的指示信息)的方式进行多个压缩或解压缩ROHC实体的管理。
步骤2：当UE接收到1个PDCP实体的多个压缩或解压缩ROHC实体的配置信息的时候，UE对于上行发送建立多个压缩ROHC实体，UE对于下行接收建立多个解压缩ROHC实体。
示例性地，对于DC切换过程，对于同1个PDCP实体，源连接和目标连接分别都配置了其对应的压缩或解压缩ROHC实体(比如，压缩或解压缩ROHC1和压缩或解压缩ROHC2)，则UE对于上行发送建立多个压缩ROHC 实体，UE对于下行接收建立多个解压缩ROHC实体。
步骤3.1：根据步骤2，PDCP接收端的行为包括：
当PDCP接收端在接收到PDCP包(比如，PDCP数据包和/或ROHC反馈包)之后，根据该PDCP包的PDCP协议数据单元(protocol data unit，PDU)的包头的ROHC实体指示信息采用特定的压缩或解压缩ROHC实体进行处理。
例如，UE的PDCP接收实体在接收PDCP数据包时，PDCP数据包的PDCPPDU的包头指示该PDCP数据包采用的解压缩ROHC1，则UE的PDCP接收实体采用解压缩ROHC1对该PDCP PDU的包头进行解压缩。
又例如，UE的PDCP接收实体在接收ROHC反馈包时，ROHC反馈包的PDCP PDU的包头指示该PDCP PDU的包头包采用的解压缩ROHC1，则UE的PDCP接收实体采用解压缩ROHC1对该PDCP PDU的包头进行处理。
步骤3.2：根据步骤1，PDCP发送端的行为包括：
当PDCP发送端采用特定的压缩或解压缩ROHC实体进行压缩(或ROHC反馈包(比如，“Control PDU for interspersed ROHC feedback”)发送)的时候，PDCP发送端在发送的PDCP包头中指示采用的压缩或解压缩ROHC实体。
例如，UE的PDCP发送实体在发送数据的时候，如果该数据的PDCP包头压缩是采用的压缩ROHC1，则该数据的PDCP PDU的包头中指示采用了压缩ROHC1。
又例如，UE的PDCP发送实体在发送ROHC反馈包(如，“Control PDU for interspersed ROHC feedback”)的时候，如果该ROHC反馈包采用的压缩ROHC1，则该ROHC反馈包的PDCP PDU的包头中指示采用了压缩ROHC1。
额外的，PDCP发送端对于发送给各个连接的数据包，采用各个连接对应的压缩或解压缩ROHC实体。
示例性地，根据网络侧的配置信息(比如，源连接采用压缩或解压缩ROHC1，目标连接采用压缩或解压缩ROHC2)，UE的PDCP发送端对于发送给源连接的数据采用压缩或解压缩ROHC1，对于发送给目标连接的数据采用压缩或解压缩ROHC2。
额外的，步骤4：对于移动性过程(比如，切换或辅小区组变更(secondary cell group change，SCG change))，UE在该移动性过程完成后，UE的PDCP 发送实体采用目标连接对应的压缩或解压缩ROHC实体(即，不再采用源连接对应的压缩或解压缩ROHC实体)。
进一步地，UE的发送PDCP实体重置和/或删除源连接对应的压缩或解压缩ROHC实体。
其中，该移动性过程完成的触发事件包括以下一项或多项的任意组合：
(1)接收到网络侧发送的移动性过程完成指示信息，比如，网络侧发送删除源连接的配置消息；
(2)给网络侧发送的移动性过程完成指示信息，比如，UE给网络侧发送删除源连接的指示消息；
(3)目标连接的随机接入过程完成；
(4)PDCP发送实体接收到的源连接的数据全部处理完成，比如，解压完成，或解密完成，或发送给了高层。
实施例1.2：PDCP标识指示多个压缩或解压缩ROHC实体。
步骤1：网络侧配置或协议约定，UE采用PDCP标识(比如，PDCP SN或计数(COUNT))指示的方式进行多个压缩或解压缩ROHC实体的管理。
其中，该PDCP标识配置信息包括以下任意一项：
(1)下行PDCP包标识；
(2)上行PDCP包标识；
(3)该下行或上行PDCP包标识之前(或之后)采用的压缩或解压缩ROHC实体。
示例性地，网络侧配置在指定的PDCP SN(比如，100)前使用压缩或解压缩ROHC1，之后采用压缩或解压缩ROHC2。
步骤2：当UE接收到1个PDCP实体的多个压缩或解压缩ROHC实体的配置信息的时候，UE对于上行发送建立多个压缩ROHC实体，UE对于下行接收建立多个解压缩ROHC实体。
示例性地，对于DC切换过程，对于同1个PDCP实体，源连接和目标连接分别都配置了其对应的压缩或解压缩ROHC实体(比如，压缩或解压缩ROHC1和压缩或解压缩ROHC2)，则UE对于上行发送建立多个压缩ROHC实体，UE对于下行接收建立多个解压缩ROHC实体。
步骤3.1：根据步骤2，PDCP接收端的行为包括：
当PDCP接收端在接收到PDCP包(比如，PDCP数据包和/或ROHC反馈包)之后，UE根据接收的PDCP包标识采用特定的压缩或解压缩ROHC实体进行处理。
例如，UE的PDCP接收实体在接收数据时PDCP PDU的包头指示该PDCP数据包的PDCP SN为配置的PDCP SN前的编号，则UE的PDCP接收实体采用压缩或解压缩ROHC1对该PDCP PDU的包头进行解压缩，否则采用压缩或解压缩ROHC2。
又例如，UE的PDCP接收实体在接收ROHC反馈包的时候，在该ROHC反馈包之前接收(或发送)的PDCP包的PDCP SN为配置的PDCP SN号前的编号，则UE的PDCP接收实体采用压缩或解压缩ROHC1对该PDCP PDU的包头进行处理，否则采用压缩或解压缩ROHC2。
步骤3.2：根据步骤1，PDCP发送端的行为包括：
当PDCP发送端在发送PDCP包(如，PDCP数据包和/或ROHC反馈包。)时，UE根据发送的PDCP包标识采用特定的压缩或解压缩ROHC实体进行处理。
例如，UE的PDCP发送实体在发送数据的时候，该PDCP数据包的PDCPSN为配置的PDCP SN前的编号，则UE的PDCP接收实体采用压缩或解压缩ROHC1对该PDCP PDU的包头进行压缩，否则采用压缩或解压缩ROHC2。
额外的，PDCP发送端对于发送给各个连接的数据包，根据PDCP标识判断该数据包发送的连接。比如，在DC切换过程中，UE的PDCP发送实体在发送数据的时候，该数据包的PDCP SN为配置的PDCP SN号前的编号，则UE将该数据包通过源连接进行发送，否则通过目标连接进行发送。
额外的，步骤4：对于移动性过程(比如，切换或SCG change)，UE在该移动性过程完成后，UE的PDCP实体采用目标连接对应的压缩或解压缩ROHC实体，即，不再采用源连接对应的压缩或解压缩ROHC实体。
额外的，UE的PDCP实体重置和/或删除源连接对应的压缩或解压缩ROHC实体。
其中，该移动性过程完成的触发事件包括以下一项或多项的任意组合：
(1)接收到网络侧发送的移动性过程完成指示信息，比如，网络侧发送删除源连接的配置消息；
(2)给网络侧发送的移动性过程完成指示信息，比如，UE给网络侧发送删除源连接的指示消息；
(3)目标连接的随机接入过程完成；
(4)PDCP接收到的源连接的数据全部处理完成，比如，解压完成，或解密完成，或发送给了高层。
实施例1.3：多个压缩或解压缩ROHC实体，根据PDCP包对应的连接选择压缩或解压缩ROHC实体。
步骤1：网络侧配置或协议约定，UE采用PDCP包对应的连接进行多个压缩或解压缩ROHC实体的管理。
其中，该PDCP包对应的连接配置信息包括：特定连接对应的特定压缩或解压缩ROHC实体。
比如，网络侧配置对于接收的连接1的数据包采用解压缩ROHC1，网络侧配置对于发送的连接1的数据包采用压缩ROHC1。
步骤2：当UE接收到1个PDCP实体的多个压缩或解压缩ROHC实体的配置信息的时候，UE对于上行发送建立多个压缩ROHC实体，UE对于下行接收建立多个解压缩ROHC实体。
例如，对于DC切换过程，对于同1个PDCP实体，源连接和目标连接分别都配置了其对应的压缩或解压缩ROHC实体(如，压缩或解压缩ROHC1和压缩或解压缩ROHC2)，UE对于上行发送建立多个压缩ROHC实体，UE对于下行接收建立多个解压缩ROHC实体。
步骤3.1：根据步骤2，PDCP接收端的行为包括：
当PDCP接收端在接收到PDCP包(比如，PDCP数据包和/或ROHC反馈包)后，UE根据接收的PDCP包的连接采用特定的压缩或解压缩ROHC实体进行处理。
例如，UE的PDCP接收实体在接收PDCP数据包时，PDCP数据包是来自于连接1，则UE的PDCP接收实体采用解压缩ROHC1对该PDCP数据包的PDCP PDU的包头进行解压缩。
又例如，UE的PDCP接收实体在接收ROHC反馈包时，该ROHC反馈包来自于连接1，则UE的PDCP接收实体采用解压缩ROHC1对该PDCP PDU进行处理。
步骤3.2：根据步骤1，PDCP发送端的行为包括：
当PDCP发送端在发送PDCP包(比如，PDCP数据包和/或ROHC反馈包)时，UE根据发送的PDCP包的连接采用特定的压缩或解压缩ROHC实体进行处理。
例如，UE的PDCP发送实体在发送PDCP数据包时，PDCP数据包是通过连接1发送，则UE的PDCP发送实体采用压缩ROHC1对该PDCP数据包的PDCP PDU进行压缩。
又例如，UE的PDCP发送实体在发送ROHC反馈包的时候，该ROHC反馈包是针对ROHC1的接收数据包的ROHC反馈包，则UE的PDCP发送实体采用压缩ROHC1对该ROHC PDCP PDU的包头进行处理，同时该ROHC反馈包发送给压缩ROHC1对应的连接。
额外的，PDCP发送端对于发送给各个连接的PDCP包，根据采用的压缩或解压缩ROHC实体判断该PDCP包发送的连接。
例如，在DC切换过程中，UE的PDCP发送实体在发送PDCP包的时候，该PDCP包的采用的是压缩ROHC1，则该PDCP包通过压缩ROHC1对应的连接进行发送。
额外的，步骤4：对于移动性过程(比如，切换或SCG change)，UE在该移动性过程完成后，UE的PDCP实体采用目标连接对应的压缩或解压缩ROHC实体(即，不再采用源连接对应的压缩或解压缩ROHC实体)。
额外的，UE的PDCP实体重置和/或删除源连接对应的压缩或解压缩ROHC实体。
其中，该移动性过程完成的触发事件包括以下一项或多项的任意组合：
(1)接收到网络侧发送的移动性过程完成指示信息，比如，网络侧发送删除源连接的配置消息；
(2)给网络侧发送的移动性过程完成指示信息，比如，UE给网络侧发送删除源连接的指示消息；
(3)目标连接的随机接入过程完成；
(4)PDCP接收到的源连接的数据全部处理完成，比如，解压完成，或解密完成，或发送给了高层。
实施例1.4：通过PDCP控制包变换多个压缩或解压缩ROHC实体。
步骤1：网络侧配置或协议约定，UE采用PDCP控制包的方式进行多个压缩或解压缩ROHC实体的管理。
例如，在接收到PDCP控制包后，根据该PDCP控制包的指示信息判断后续要采用的压缩或解压缩ROHC实体。
步骤2：当UE接收到1个PDCP实体的多个压缩或解压缩ROHC实体的配置信息的时候，UE对于上行发送建立多个压缩ROHC实体，UE对于下行接收建立多个解压缩ROHC实体。
例如，对于DC切换过程，对于同1个PDCP实体，源连接和目标连接分别都配置了其对应的压缩或解压缩ROHC实体(如，压缩或解压缩ROHC1和压缩或解压缩ROHC2)，UE对于上行发送建立多个压缩ROHC实体，UE对于下行接收建立多个解压缩ROHC实体。
步骤3：UE在接收到网络侧发送的ROHC实体变更信息(比如，PDCP控制包)后，采用变更后的压缩或解压缩ROHC实体。
例如，UE的1个PDCP实体，接收到PDCP控制包，该PDCP控制包指示了该PDCP要采用的压缩或解压缩ROHC实体，则该PDCP实体变更其使用的压缩或解压缩ROHC实体。
或者，UE在给网络侧发送ROHC实体变更信息时(或之前，或之后)，采用变更后的压缩或解压缩ROHC实体。
例如，UE的1个PDCP实体，在发送PDCP控制包时(或之前，或之后)，该PDCP控制包指示了该PDCP要采用的压缩或解压缩ROHC实体，则该PDCP实体变更其使用的压缩或解压缩ROHC实体。
额外的，UE的PDCP实体在变更其使用的压缩或解压缩ROHC实体时(或之前，或之后)对压缩或解压缩ROHC实体进行重置。
额外的，UE的PDCP实体在变更其使用的压缩或解压缩ROHC实体时(或之前，或之后)，删除之前使用的压缩或解压缩ROHC实体。
实施例2.1：通过PDCP控制包变换1个压缩或解压缩ROHC实体。
步骤1：网络侧配置或协议约定，UE采用PDCP控制包的方式进行1个压缩或解压缩ROHC实体的管理。
例如，在接收到PDCP控制包后，根据该PDCP控制包的指示信息判断后续要采用的压缩或解压缩ROHC实体。
步骤2：当UE接收到1个PDCP实体的多个压缩或解压缩ROHC实体的配置信息的时候，先使用1个特定的压缩或解压缩ROHC实体。
例如，对于DC切换过程，对于同1个PDCP实体，源连接和目标连接分别都配置了其对应的压缩或解压缩ROHC实体(如，压缩或解压缩ROHC1和压缩或解压缩ROHC2)，则UE对于上行发送先采用压缩ROHC1，UE对于下行接收先采用解压缩ROHC1。
步骤3：UE在接收到网络侧发送的ROHC实体变更信息(如，PDCP控制包)后，采用(或建立)变更后的压缩或解压缩ROHC实体。
例如，UE的1个PDCP实体，接收到PDCP控制包，该PDCP控制包指示了PDCP要采用的压缩或解压缩ROHC实体，则该PDCP实体变更其使用的压缩或解压缩ROHC实体。
或者，UE在给网络侧发送压缩或解压缩ROHC实体变更信息时(或之前，或之后)，采用(或建立)变更后的压缩或解压缩ROHC实体。
例如，UE的1个PDCP实体，在发送PDCP控制包时(或之前，或之后)，该PDCP控制包指示了该PDCP要采用的压缩或解压缩ROHC实体，则该PDCP实体变更其使用的压缩或解压缩ROHC实体。
额外的，UE的PDCP实体在变更其使用的压缩或解压缩ROHC实体时(或之前，或之后)对ROHC实体进行重置。
额外的，UE的PDCP实体在变更其使用的压缩或解压缩ROHC实体时(或之前，或之后)，删除之前使用的ROHC实体。
额外的，UE的PDCP实体在变更其使用的压缩或解压缩ROHC实体时(或之前，或之后)，如果网络侧配置了ROHC连续功能(如，drb-ContinueROHC)，则UE的PDCP实体不重置压缩或解压缩ROHC实体。
额外的，UE的PDCP实体在变更其使用的ROHC实体时(或之前，或 之后)，如果网络侧没有配置压缩或解压缩ROHC连续功能(如，drb-ContinueROHC)，则UE的PDCP实体重置压缩或解压缩ROHC实体。
实施例2.2：PDCP标识变换1个压缩或解压缩ROHC实体。
步骤1：网络侧配置或协议约定，UE采用PDCP标识(比如，PDCP SN或COUNT)的方式进行1个压缩或解压缩ROHC实体的管理。
其中，该PDCP标识配置信息包括以下任意一项：
(1)下行PDCP包标识；
(2)上行PDCP包标识；
(3)PDCP包标识之前(或之后)采用的压缩或解压缩ROHC实体。
例如，网络侧配置在指定的PDCP SN(比如，100)前使用压缩或解压缩ROHC1，之后采用压缩或解压缩ROHC2。
步骤2：当UE接收到1个PDCP实体的多个压缩或解压缩ROHC实体的配置信息的时候，先使用1个特定的压缩或解压缩ROHC实体。
例如，对于DC切换过程，对于同1个PDCP实体，源连接和目标连接分别都配置了其对应的压缩或解压缩ROHC实体(如，压缩或解压缩ROHC1和压缩或解压缩ROHC2)，则UE对于上行发送先采用压缩ROHC1，UE对于下行接收先采用解压缩ROHC1。
步骤3：UE在接收到网络侧发送的对应的PDCP标识信息后，采用(或建立)变更后的压缩或解压缩ROHC实体。
比如，UE的1个PDCP实体，在接收到的PDCP标识为配置的PDCP SN号前的编号，则UE的PDCP接收实体采用解压缩ROHC1对该PDCP PDU进行处理，否则采用解压缩ROHC2。
或者，UE根据发送给到网络侧的对应的PDCP标识信息，采用(或建立)变更后的压缩或解压缩ROHC实体。
例如，UE的1个PDCP实体，在发送的PDCP标识为配置的PDCP SN前的编号，则UE的PDCP接收实体采用压缩ROHC1对该PDCP PDU进行处理，否则采用压缩ROHC2。
额外的，UE的PDCP实体在变更其使用的压缩或解压缩ROHC实体时(或之前，或之后)，对之前使用的压缩或解压缩ROHC实体进行重置。
额外的，UE的PDCP实体在变更其使用的压缩或解压缩ROHC实体时(或之前，或之后)，删除之前使用的压缩或解压缩ROHC实体。
额外的，UE的PDCP实体在变更其使用的ROHC实体时(或之前，或之后)，如果网络侧配置了ROHC连续功能(如，drb-ContinueROHC)，则UE的PDCP实体不重置之前使用的压缩或解压缩ROHC实体。
额外的，UE的PDCP实体在变更其使用的ROHC实体时(或之前，或之后)，如果网络侧没有配置ROHC连续功能(如，drb-ContinueROHC)，则UE的PDCP实体重置之前使用的压缩或解压缩ROHC实体。
实施例2.3：通过变换PDCP包对应的连接变换1个压缩或解压缩ROHC实体
步骤1：网络侧配置或协议约定，UE采用PDCP包对应的连接进行1个压缩或解压缩ROHC实体的管理。
其中，该PDCP包对应的连接配置信息包括：特定连接对应的特定压缩或解压缩ROHC实体。
比如，比如，网络侧配置对于接收的连接1的数据包采用解压缩ROHC1，网络侧配置对于发送的连接1的数据包采用压缩ROHC1。
步骤2：当UE接收到1个PDCP实体的多个压缩或解压缩ROHC实体的配置信息的时候，先使用1个特定的压缩或解压缩ROHC实体。
例如，对于DC切换过程，对于同1个PDCP实体，源连接和目标连接分别都配置了其对应的压缩或解压缩ROHC实体(如，压缩或解压缩ROHC1和压缩或解压缩ROHC2)，则UE对于上行发送先采用压缩ROHC1，UE对于下行接收先采用解压缩ROHC1。
步骤3.1：根据步骤2，PDCP接收端的行为包括：
当PDCP接收端在接收到PDCP包(比如，PDCP数据包和/或ROHC反馈包)后，UE根据接收的PDCP包的连接采用特定的解压缩ROHC实体进行处理。
例如，UE的PDCP接收实体在接收PDCP数据包时，PDCP数据包是来自于源连接，则UE的PDCP接收实体采用源连接对应的解压缩ROHC1对该PDCP数据包的PDCP PDU的包头进行解压缩。
当该UE的PDCP接收实体接收的PDCP数据包的连接由源连接变更成目标连接时，则该PDCP实体变更其之前使用的压缩或解压缩ROHC实体。
又例如，UE的PDCP接收实体在接收ROHC反馈包时，该ROHC反馈包来自于连接1，则UE的PDCP接收实体采用连接1对应的解压缩ROHC1对该PDCP PDU的包头进行解压缩处理。
步骤3.2：根据步骤1，PDCP发送端的行为包括：
当PDCP发送端在发送PDCP包(比如，PDCP数据包和/或ROHC反馈包)时，UE根据发送的PDCP包的连接采用特定的压缩ROHC实体进行处理。
例如，UE的PDCP发送实体在发送PDCP数据包时，PDCP数据包是通过源连接发送，则UE的PDCP发送实体采用源连接对应的压缩ROHC1对该PDCP数据包的PDCP PDU进行压缩。
当该UE的PDCP发送实体发送的PDCP数据包的连接由源连接变更成目标连接时，则该PDCP实体变更其之前使用的压缩或解压缩ROHC实体。
又例如，UE的PDCP发送实体在发送ROHC反馈包的时候，该ROHC反馈包是针对压缩ROHC1的接收数据包的ROHC反馈包，则UE的PDCP发送实体采用压缩ROHC1对该PDCP PDU的包头进行处理，同时该ROHC反馈包发送给压缩ROHC1对应的连接。
额外的，UE的PDCP实体在变更其使用的压缩或解压缩ROHC实体时(或之前，或之后)，对之前使用的压缩或解压缩ROHC实体进行重置。
额外的，UE的PDCP实体在变更其使用的压缩或解压缩ROHC实体时(或之前，或之后)，删除之前使用的压缩或解压缩ROHC实体。
额外的，UE的PDCP实体在变更其使用的ROHC实体时(或之前，或之后)，对之前使用的压缩或解压缩ROHC实体进行重置。
额外的，UE的PDCP实体在变更其使用的压缩或解压缩ROHC实体时(或之前，或之后)，如果网络侧配置了ROHC连续功能(如，drb-ContinueROHC)，则UE的PDCP实体不重置之前使用的压缩或解压缩ROHC实体。
额外的，UE的PDCP实体在变更其使用的压缩或解压缩ROHC实体时 (或之前，或之后)，如果网络侧没有配置ROHC连续功能(如，drb-ContinueROHC)，则UE的PDCP实体重置之前使用的压缩或解压缩ROHC实体。
额外的，PDCP发送端对于发送给各个连接的PDCP包，根据采用的压缩ROHC实体判断该PDCP包发送的连接。
例如，在DC切换过程中，UE的PDCP发送实体在发送PDCP包的时候，该PDCP包的采用的是压缩ROHC1，则该PDCP包通过压缩ROHC1对应的连接进行发送。
额外的，步骤4：对于移动性过程(比如，切换或SCG change)，UE在该移动性过程完成后，UE的PDCP实体采用目标连接对应的压缩或解压缩ROHC实体(即，不再采用源连接对应的压缩或解压缩ROHC实体)。
额外的，UE的PDCP实体重置和/或删除源连接对应的压缩或解压缩ROHC实体。
其中，该移动性过程完成的触发事件包括以下一项或多项的任意组合：
(1)接收到网络侧发送的移动性过程完成指示信息，比如，网络侧发送删除源连接的配置消息；
(2)给网络侧发送的移动性过程完成指示信息，比如，UE给网络侧发送删除源连接的指示消息；
(3)目标连接的随机接入过程完成；
(4)PDCP接收到的源连接的数据全部处理完成，比如，解压完成，或解密完成，或发送给了高层。
实施例3：通过网络侧配置控制ROHC连续功能控制，是采用1个还是多个压缩或解压缩ROHC实体。
步骤1：网络侧通过配置ROHC连续功能(如，drb-ContinueROHC)来控制UE的1个PDCP实体在是同时建立1个压缩或解压缩ROHC还是建立多个压缩或解压缩ROHC实体。
步骤2：根据步骤1的配置信息。UE的行为包括以下任意一种：
(1)如果PDCP配置信息指示采用ROHC连续功能(即，ROHC不重置指示)，则该PDCP实体同一时刻采用1个压缩或解压缩ROHC实体，且 可以不采用实例2.1或2.2中变更压缩或解压缩ROHC实体的功能。
(2)如果PDCP配置信息没有指示采用ROHC连续功能，且UE接收到1个PDCP实体的多个压缩或解压缩ROHC实体的配置信息的时候，UE对于上行发送建立多个压缩ROHC实体，UE对于下行接收建立多个解压缩ROHC实体。
(3)如果PDCP配置信息没有指示采用ROHC连续功能(即，ROHC不重置指示)，则该PDCP实体同一时刻采用1个压缩或解压缩ROHC实体，且可以采用实例2.1或2.2中变更压缩或解压缩ROHC实体的功能。
当UE同时采用(或建立)多个压缩或解压缩ROHC实体的时候，UE行为同实例1.1、1.2、1.3和1.4，在此不再重复描述。
当UE同时采用(或建立)1个压缩或解压缩ROHC实体的时候，若采用实例2.1或2.2中的变更压缩或解压缩ROHC实体的功能，则UE行为同实例2.1或2.2中的变更压缩或解压缩ROHC实体的功能，在此不再重复描述。
本公开实施例中还提供了一种通信设备，由于通信设备解决问题的原理与本公开实施例中处理方法相似，因此该通信设备的实施可以参见方法的实施，重复之处不再敷述。
参见图3，本公开实施例还提供一种通信设备，例如终端或网络设备，该通信设备300包括：
第一确定模块301，用于根据第一信息，确定压缩或解压缩ROHC实体；
其中，所述第一信息为以下一项或多项：PDCP包的包头中的指示信息；移动性过程完成的信息；PDCP包的PDCP标识；PDCP包对应的连接；PDCP控制包中的指示信息；PDCP配置信息；压缩或解压缩ROHC实体的配置信息。
在本公开实施例中，可选地，所述PDCP配置信息指示所述通信设备采用ROHC连续功能，所述通信设备的PDCP实体包括：一个压缩或解压缩ROHC实体；或者，
所述PDCP配置信息没有指示所述通信设备采用ROHC连续功能，所述通信设备的PDCP实体包括：多个压缩或解压缩ROHC实体。
在本公开实施例中，可选地，所述PDCP控制包中的指示信息指示以下 至少一项：
所述通信设备变更压缩或解压缩ROHC实体；
所述通信设备不变更压缩或解压缩ROHC实体；
所述通信设备删除之前的压缩或解压缩ROHC实体，并建立新的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，通信设备300还包括第二确定模块，用于根据特定的指示方式，确定对应的所述第一信息；
其中，所述特定的指示方式包括以下一项或多项：
PDCP包的包头指示；
PDCP包的PDCP标识的配置信息指示；
PDCP包对应连接的配置信息指示；
PDCP控制包指示。
在本公开实施例中，可选地，所述特定的指示方式由网络侧配置或者由协议约定。
在本公开实施例中，可选地，所述PDCP标识的配置信息包括以下一项或多项：
指定的PDCP包标识；
在所述指定的PDCP包标识之前采用的压缩或解压缩ROHC实体；
在所述指定的PDCP包标识之后采用的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，第一确定模块301进一步用于执行以下任意一项：
如果所述PDCP包的PDCP标识在指定的PDCP标识之前，则采用对应的压缩或解压缩ROHC实体；
如果所述PDCP包的PDCP标识在指定的PDCP标识之后，则采用对应的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，第一确定模块301进一步用于执行以下任意一项：
如果所述PDCP包的PDCP标识在指定的PDCP标识之前，则采用第一压缩或解压缩ROHC实体；
如果所述PDCP包的PDCP标识在指定的PDCP标识之后，则删除第一压缩或解压缩ROHC实体，建立并采用新的压缩或解压缩ROHC实体；
其中，所述第一压缩或解压缩ROHC实体为所述通信设备根据多个压缩或解压缩ROHC实体的配置信息建立的一个特定的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，所述PDCP包对应连接的配置信息包括以下一项或多项：
特定连接与特定压缩ROHC实体的对应关系；
特定连接与特定解压缩ROHC实体的对应关系。
在本公开实施例中，可选地，第一确定模块301进一步用于：
如果所述PDCP包对应的连接为第一连接，则采用所述第一连接对应的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，第一确定模块301进一步用于执行以下一项或多项：
根据多个压缩或解压缩ROHC实体的配置信息，建立多个压缩或解压缩ROHC实体；
根据一个压缩或解压缩ROHC实体的配置信息，建立一个特定的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，第一确定模块301进一步用于在移动性过程完成后，根据所述移动性过程完成的信息，确定目标连接对应的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，通信设备300还包括第一处理模块，该第一处理模块用于执行以下一项或多项：
将源连接对应的压缩或解压缩ROHC实体进行重置；
将源连接对应的压缩或解压缩ROHC实体删除。
在本公开实施例中，可选地，所述移动性过程完成的触发事件包括以下一项或多项：
终端接收到网络侧发送的移动性过程完成的指示信息；
终端向网络侧发送移动性过程完成的指示信息；
目标连接的随机接入过程完成；
终端接收到源连接的数据处理完成的指示信息。
在本公开实施例中，可选地，通信设备300还包括第二处理模块，该第二处理模块用于执行以下任意一项：
根据所述PDCP包的PDCP标识，确定发送所述PDCP包的连接；
根据压缩所述PDCP包的压缩ROHC实体，确定发送所述PDCP包的连接。
在本公开实施例中，可选地，通信设备300还包括第三处理模块，该第三处理模块用于执行以下任意一项：
在发送ROHC实体变更信息时，通过变更后的压缩或解压缩ROHC实体对PDCP包的包头进行压缩或解压缩；
在发送ROHC实体变更信息之前，通过变更后的压缩或解压缩ROHC实体对PDCP包的包头进行压缩或解压缩；
在发送ROHC实体变更信息之后，通过变更后的压缩或解压缩ROHC实体对PDCP包的包头进行压缩或解压缩。
在本公开实施例中，可选地，通信设备300还包括第四处理模块，该第四处理模块用于执行以下任意一项：
在变更使用的压缩或解压缩ROHC实体时，如果所述PDCP配置信息指示所述通信设备采用ROHC连续功能，不重置之前使用的压缩或解压缩ROHC实体；
在变更使用的压缩或解压缩ROHC实体之前，如果所述PDCP配置信息指示所述通信设备采用ROHC连续功能，不重置之前使用的压缩或解压缩ROHC实体；
在变更使用的压缩或解压缩ROHC实体之后，如果所述PDCP配置信息指示所述通信设备采用ROHC连续功能，不重置之前使用的压缩或解压缩ROHC实体。
在本公开实施例中，可选地，通信设备300还包括第五处理模块，该第五处理模块用于执行以下任意一项：
在变更使用的压缩或解压缩ROHC实体时，如果所述PDCP配置信息没有指示所述通信设备采用ROHC连续功能，对之前使用的压缩或解压缩 ROHC实体进行重置；
在变更使用的压缩或解压缩ROHC实体之前，如果所述PDCP配置信息没有指示所述通信设备采用ROHC连续功能，对之前使用的压缩或解压缩ROHC实体进行重置；
在变更使用的压缩或解压缩ROHC实体之后，如果所述PDCP配置信息没有指示所述通信设备采用ROHC连续功能，对之前使用的压缩或解压缩ROHC实体进行重置。
在本公开实施例中，可选地，通信设备300还包括第六处理模块，该第六处理模块用于执行以下任意一项：
在变更使用的压缩或解压缩ROHC实体时，对之前使用的压缩或解压缩ROHC实体进行重置；
在变更使用的压缩或解压缩ROHC实体之前，对之前使用的压缩或解压缩ROHC实体进行重置；
在变更使用的压缩或解压缩ROHC实体之后，对之前使用的压缩或解压缩ROHC实体进行重置。
在本公开实施例中，可选地，通信设备300还包括第七处理模块，该第七处理模块用于执行以下任意一项：
在变更使用的压缩或解压缩ROHC实体时，将之前使用的压缩或解压缩ROHC实体删除；
在变更使用的压缩或解压缩ROHC实体之前，将之前使用的压缩或解压缩ROHC实体删除；
在变更使用的压缩或解压缩ROHC实体之后，将之前使用的压缩或解压缩ROHC实体删除。
本公开实施例提供的通信设备，可以执行上述方法实施例，其实现原理和技术效果类似，本实施例此处不再赘述。
请参阅图4，图4是本公开实施例应用的通信设备的结构图，如图4所示，通信设备400包括：处理器401、收发机402、存储器403和总线接口，其中：
在本公开的一个实施例中，通信设备400还包括：存储在存储器上403 并可在处理器401上运行的程序，程序被处理器401执行时实现如下步骤：根据第一信息，确定压缩或解压缩ROHC实体；其中，所述第一信息为以下一项或多项：PDCP包的包头中的指示信息；移动性过程完成的信息；PDCP包的PDCP标识；PDCP包对应的连接；PDCP控制包中的指示信息；PDCP配置信息；压缩或解压缩ROHC实体的配置信息。
在图4中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器401代表的一个或多个处理器和存储器403代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机402可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。
处理器401负责管理总线架构和通常的处理，存储器403可以存储处理器401在执行操作时所使用的数据。
本公开实施例提供的通信设备，可以执行上述方法实施例，其实现原理和技术效果类似，本实施例此处不再赘述。
结合本公开公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以由在处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以携带在ASIC中。另外，该ASIC可以携带在核心网接口设备中。当然，处理器和存储介质也可以作为分立组件存在于核心网接口设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本公开所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质 上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得 一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来控制相关的硬件来完成，所述的程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储器(Read-Only Memory，ROM)或随机存取存储器(Random Access Memory，RAM)等。
可以理解的是，本公开实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processor，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本公开所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本公开实施例所述功能的模块(例如过程、函数等)来实现本公开实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
以上所述的具体实施方式，对本公开的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本公开的具体实施方式而已，并不用于限定本公开的保护范围，凡在本公开的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本公开的保护范围之内。
本领域内的技术人员应明白，本公开实施例可提供为方法、系统、或计算机程序产品。因此，本公开实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本公开实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、只读光盘驱动器(Compact Disc Read-Only Memory，CD-ROM)、光学存储器等)上实施的计算机程序产品的形式。
本公开实施例是参照根据本公开实施例的方法、设备(系统)、和计算机 程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本公开实施例进行各种改动和变型而不脱离本公开的精神和范围。这样，倘若本公开实施例的这些修改和变型属于本公开权利要求及其等同技术的范围之内，则本公开也意图包含这些改动和变型在内。

Claims (23)

  1. 一种处理方法，应用于通信设备，包括：
    根据第一信息，确定压缩或解压缩鲁棒头压缩ROHC实体；
    其中，所述第一信息为以下一项或多项：包数据汇聚协议PDCP包的包头中的指示信息；移动性过程完成的信息；PDCP包的PDCP标识；PDCP包对应的连接；PDCP控制包中的指示信息；PDCP配置信息；压缩或解压缩ROHC实体的配置信息。
  2. 根据权利要求1所述的方法，其中，
    所述PDCP配置信息指示所述通信设备采用ROHC连续功能，所述通信设备的PDCP实体包括：一个压缩或解压缩ROHC实体；或者，
    所述PDCP配置信息没有指示所述通信设备采用ROHC连续功能，所述通信设备的PDCP实体包括：多个压缩或解压缩ROHC实体。
  3. 根据权利要求1所述的方法，其中，所述PDCP控制包中的指示信息指示以下至少一项：
    所述通信设备变更压缩或解压缩ROHC实体；
    所述通信设备不变更压缩或解压缩ROHC实体；
    所述通信设备删除之前的压缩或解压缩ROHC实体，并建立新的压缩或解压缩ROHC实体。
  4. 根据权利要求1所述的方法，其中，在所述根据第一信息，确定压缩或解压缩ROHC实体的步骤之前，所述方法还包括：
    根据特定的指示方式，确定对应的所述第一信息；
    其中，所述特定的指示方式包括以下一项或多项：
    PDCP包的包头指示；
    PDCP包的PDCP标识的配置信息指示；
    PDCP包对应连接的配置信息指示；
    PDCP控制包指示。
  5. 根据权利要求4所述的方法，其中，所述特定的指示方式由网络侧配置或者由协议约定。
  6. 根据权利要求4所述的方法，其中，所述PDCP标识的配置信息包括以下一项或多项：
    指定的PDCP包标识；
    在所述指定的PDCP包标识之前采用的压缩或解压缩ROHC实体；
    在所述指定的PDCP包标识之后采用的压缩或解压缩ROHC实体。
  7. 根据权利要求1所述的方法，其中，所述通信设备的PDCP实体包括：多个压缩或解压缩ROHC实体，所述根据第一信息，确定压缩或解压缩ROHC实体，包括以下任意一项：
    如果所述PDCP包的PDCP标识在指定的PDCP标识之前，则采用对应的压缩或解压缩ROHC实体；
    如果所述PDCP包的PDCP标识在指定的PDCP标识之后，则采用对应的压缩或解压缩ROHC实体。
  8. 根据权利要求1所述的方法，其中，所述通信设备的PDCP实体包括：一个压缩或解压缩ROHC实体，所述根据第一信息，确定压缩或解压缩ROHC实体，包括以下任意一项：
    如果所述PDCP包的PDCP标识在指定的PDCP标识之前，则采用第一压缩或解压缩ROHC实体；
    如果所述PDCP包的PDCP标识在指定的PDCP标识之后，则删除第一压缩或解压缩ROHC实体，建立并采用新的压缩或解压缩ROHC实体；
    其中，所述第一压缩或解压缩ROHC实体为所述通信设备根据多个压缩或解压缩ROHC实体的配置信息建立的一个特定的压缩或解压缩ROHC实体。
  9. 根据权利要求4所述的方法，其中，所述PDCP包对应连接的配置信息包括以下一项或多项：
    特定连接与特定压缩ROHC实体的对应关系；
    特定连接与特定解压缩ROHC实体的对应关系。
  10. 根据权利要求1所述的方法，其中，所述根据第一信息，确定压缩或解压缩ROHC实体，包括：
    如果所述PDCP包对应的连接为第一连接，则采用所述第一连接对应的压缩或解压缩ROHC实体。
  11. 根据权利要求1所述的方法，其中，所述根据第一信息，确定压缩或解压缩ROHC实体，包括以下一项或多项：
    根据多个压缩或解压缩ROHC实体的配置信息，建立多个压缩或解压缩ROHC实体；
    根据一个压缩或解压缩ROHC实体的配置信息，建立一个压缩或解压缩ROHC实体。
  12. 根据权利要求1所述的方法，其中，所述根据第一信息，确定压缩或解压缩ROHC实体，包括：
    在移动性过程完成后，根据所述移动性过程完成的信息，确定目标连接对应的压缩或解压缩ROHC实体。
  13. 根据权利要求12所述的方法，其中，在所述确定目标连接对应的压缩或解压缩ROHC实体之后，所述方法还包括以下一项或多项：
    将源连接对应的压缩或解压缩ROHC实体进行重置；
    将源连接对应的压缩或解压缩ROHC实体删除。
  14. 根据权利要求12所述的方法，其中，所述移动性过程完成的触发事件包括以下一项或多项：
    终端接收到网络侧发送的移动性过程完成的指示信息；
    终端向网络侧发送移动性过程完成的指示信息；
    目标连接的随机接入过程完成；
    终端接收到源连接的数据处理完成的指示信息。
  15. 根据权利要求1所述的方法，其中，在所述根据第一信息，确定压缩或解压缩ROHC实体之后，所述方法还包括以下任意一项：
    根据所述PDCP包的PDCP标识，确定发送所述PDCP包的连接；
    根据压缩所述PDCP包的压缩ROHC实体，确定发送所述PDCP包的连接。
  16. 根据权利要求1所述的方法，其中，在所述根据第一信息，确定压缩或解压缩ROHC实体之后，所述方法还包括以下任意一项：
    在发送ROHC实体变更信息时，通过变更后的压缩或解压缩ROHC实体对PDCP包的包头进行压缩或解压缩；
    在发送ROHC实体变更信息之前，通过变更后的压缩或解压缩ROHC实体对PDCP包的包头进行压缩或解压缩；
    在发送ROHC实体变更信息之后，通过变更后的压缩或解压缩ROHC实体对PDCP包的包头进行压缩或解压缩。
  17. 根据权利要求2所述的方法，其中，在所述根据第一信息，确定压缩或解压缩ROHC实体之后，所述方法还包括以下任意一项：
    在变更使用的压缩或解压缩ROHC实体时，如果所述PDCP配置信息指示所述通信设备采用ROHC连续功能，不重置之前使用的压缩或解压缩ROHC实体；
    在变更使用的压缩或解压缩ROHC实体之前，如果所述PDCP配置信息指示所述通信设备采用ROHC连续功能，不重置之前使用的压缩或解压缩ROHC实体；
    在变更使用的压缩或解压缩ROHC实体之后，如果所述PDCP配置信息指示所述通信设备采用ROHC连续功能，不重置之前使用的压缩或解压缩ROHC实体。
  18. 根据权利要求2所述的方法，其中，在所述根据第一信息，确定压缩或解压缩ROHC实体之后，所述方法还包括以下任意一项：
    在变更使用的压缩或解压缩ROHC实体时，如果所述PDCP配置信息没有指示所述通信设备采用ROHC连续功能，对之前使用的压缩或解压缩ROHC实体进行重置；
    在变更使用的压缩或解压缩ROHC实体之前，如果所述PDCP配置信息没有指示所述通信设备采用ROHC连续功能，对之前使用的压缩或解压缩ROHC实体进行重置；
    在变更使用的压缩或解压缩ROHC实体之后，如果所述PDCP配置信息没有指示所述通信设备采用ROHC连续功能，对之前使用的压缩或解压缩ROHC实体进行重置。
  19. 根据权利要求1所述的方法，其中，在所述根据第一信息，确定压缩或解压缩ROHC实体之后，所述方法还包括以下任意一项：
    在变更使用的压缩或解压缩ROHC实体时，对之前使用的压缩或解压缩 ROHC实体进行重置；
    在变更使用的压缩或解压缩ROHC实体之前，对之前使用的压缩或解压缩ROHC实体进行重置；
    在变更使用的压缩或解压缩ROHC实体之后，对之前使用的压缩或解压缩ROHC实体进行重置。
  20. 根据权利要求1所述的方法，其中，在所述根据第一信息，确定压缩或解压缩ROHC实体之后，所述方法还包括以下任意一项：
    在变更使用的压缩或解压缩ROHC实体时，将之前使用的压缩或解压缩ROHC实体删除；
    在变更使用的压缩或解压缩ROHC实体之前，将之前使用的压缩或解压缩ROHC实体删除；
    在变更使用的压缩或解压缩ROHC实体之后，将之前使用的压缩或解压缩ROHC实体删除。
  21. 一种通信设备，包括：
    确定模块，用于根据第一信息，确定压缩或解压缩鲁棒头压缩ROHC实体；
    其中，所述第一信息为以下一项或多项：包数据汇聚协议PDCP包的包头中的指示信息；移动性过程完成的信息；PDCP包的PDCP标识；PDCP包对应的连接；PDCP控制包中的指示信息；PDCP配置信息；压缩或解压缩ROHC实体的配置信息。
  22. 一种通信设备，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序，所述程序被所述处理器执行时实现如权利要求1至20中任一项所述的处理方法的步骤。
  23. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至20中任一项所述的处理方法的步骤。
PCT/CN2020/073778 2019-01-30 2020-01-22 处理方法及通信设备 Ceased WO2020156427A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
ES20749437T ES3055610T3 (en) 2019-01-30 2020-01-22 Processing method and communication device
JP2021544648A JP7279173B2 (ja) 2019-01-30 2020-01-22 処理方法及び通信機器
EP20749437.8A EP3920502B1 (en) 2019-01-30 2020-01-22 Processing method and communication device
KR1020217026361A KR102502507B1 (ko) 2019-01-30 2020-01-22 처리 방법 및 통신 기기
US17/388,629 US12284550B2 (en) 2019-01-30 2021-07-29 Processing method and communications device
US19/063,780 US20260122533A1 (en) 2019-01-30 2025-02-26 Processing Method and Communications Device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910093599.0 2019-01-30
CN201910093599.0A CN111277556B (zh) 2019-01-30 2019-01-30 处理方法及通信设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/388,629 Continuation US12284550B2 (en) 2019-01-30 2021-07-29 Processing method and communications device

Publications (1)

Publication Number Publication Date
WO2020156427A1 true WO2020156427A1 (zh) 2020-08-06

Family

ID=71001545

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/073778 Ceased WO2020156427A1 (zh) 2019-01-30 2020-01-22 处理方法及通信设备

Country Status (7)

Country Link
US (2) US12284550B2 (zh)
EP (1) EP3920502B1 (zh)
JP (2) JP7279173B2 (zh)
KR (1) KR102502507B1 (zh)
CN (1) CN111277556B (zh)
ES (1) ES3055610T3 (zh)
WO (1) WO2020156427A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115443643A (zh) * 2022-08-03 2022-12-06 北京小米移动软件有限公司 确定用于压缩信道状态信息的压缩模型的方法、装置及存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020222436A1 (en) * 2019-04-30 2020-11-05 Lg Electronics Inc. Method and apparatus for transmitting packets based on receiving a handover command in wireless communication system
CN121001126A (zh) * 2024-05-21 2025-11-21 华为技术有限公司 通信方法及相关装置
CN121334752A (zh) * 2024-07-12 2026-01-13 华为技术有限公司 通信方法及装置
WO2026065060A1 (zh) * 2024-09-26 2026-04-02 北京小米移动软件有限公司 通信方法、通信设备、通信系统、存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090080374A1 (en) * 2007-09-21 2009-03-26 Posdata Co., Ltd. Method of creating and deleting service flow for robust header compression, and wireless communication system supporting the same
CN103581033A (zh) * 2012-07-27 2014-02-12 重庆重邮信科通信技术有限公司 数据流处理的方法及设备
CN108632901A (zh) * 2017-03-24 2018-10-09 维沃移动通信有限公司 一种数据传输方法及终端
CN108810984A (zh) * 2017-05-05 2018-11-13 维沃移动通信有限公司 数据处理方法及装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI110739B (fi) 2000-10-18 2003-03-14 Nokia Corp Otsikkokenttien kompressoinnin määrittäminen datapakettiyhteydelle
EP1773004A1 (en) * 2005-10-10 2007-04-11 Nec Technologies (UK) Limited Header compression optimisation method during and after handovers in a cellular communication network
JP2012169764A (ja) * 2011-02-10 2012-09-06 Panasonic Corp 通信システム、送信制御装置及び送信制御方法
EP2675920A4 (en) 2011-02-18 2015-04-08 Nvs Technologies Inc QUANTITATIVE HIGHLY MULTIPLEXED DETECTION OF NUCLEIC ACIDS
CN104703230A (zh) * 2013-12-09 2015-06-10 中兴通讯股份有限公司 一种基于鲁棒性头压缩协议的切换方法、设备和系统
JP2016092700A (ja) 2014-11-07 2016-05-23 株式会社Ｎｔｔドコモ ユーザ装置、及び重複パケット処理方法
US10917815B2 (en) * 2017-09-18 2021-02-09 Samsung Electronics Co., Ltd. Method and apparatus for processing a packet in a wireless communication system
CN107801212A (zh) * 2017-10-17 2018-03-13 京信通信系统（中国）有限公司 一种通信方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090080374A1 (en) * 2007-09-21 2009-03-26 Posdata Co., Ltd. Method of creating and deleting service flow for robust header compression, and wireless communication system supporting the same
CN103581033A (zh) * 2012-07-27 2014-02-12 重庆重邮信科通信技术有限公司 数据流处理的方法及设备
CN108632901A (zh) * 2017-03-24 2018-10-09 维沃移动通信有限公司 一种数据传输方法及终端
CN108810984A (zh) * 2017-05-05 2018-11-13 维沃移动通信有限公司 数据处理方法及装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
See also references of EP3920502A4 *
VIVO: "RoHC issue on NR PDCP", 3GPP TSG-RAN WG2 NR AD HOC R2-1707077, 29 June 2017 (2017-06-29), XP051301573, DOI: 20200405153501X *
VIVO: "Unified UE behavior for ROHC continue", 3GPP TSG-RAN WG2 MEETING #102 R2-1807588, 25 May 2018 (2018-05-25), XP051443949, DOI: 20200405153614A *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115443643A (zh) * 2022-08-03 2022-12-06 北京小米移动软件有限公司 确定用于压缩信道状态信息的压缩模型的方法、装置及存储介质

Also Published As

Publication number Publication date
ES3055610T3 (en) 2026-02-13
EP3920502C0 (en) 2025-11-26
EP3920502B1 (en) 2025-11-26
EP3920502A4 (en) 2022-03-23
CN111277556B (zh) 2023-04-07
JP7789716B2 (ja) 2025-12-22
CN111277556A (zh) 2020-06-12
EP3920502A1 (en) 2021-12-08
JP2023099609A (ja) 2023-07-13
JP2022519554A (ja) 2022-03-24
KR102502507B1 (ko) 2023-02-21
US20210360473A1 (en) 2021-11-18
KR20210113685A (ko) 2021-09-16
JP7279173B2 (ja) 2023-05-22
US20260122533A1 (en) 2026-04-30
US12284550B2 (en) 2025-04-22

Similar Documents

Publication Publication Date Title
CN104067523B (zh) 一种数据包处理方法和装置
WO2020156427A1 (zh) 处理方法及通信设备
CN110891287B (zh) 以太网包头压缩、解压缩的方法和设备、及可读存储介质
TWI734010B (zh) 傳輸數據的方法和設備
CN102724646B (zh) 心跳信息的传输方法及设备
WO2018137716A1 (zh) 一种保持udc功能连续性的方法及设备
WO2019173951A1 (zh) 一种ue策略的更新方法及装置、计算机存储介质
CN111107539B (zh) 一种终端通信能力发送、接收方法及装置
KR102621466B1 (ko) 제어면 메시지의 전송 방법 및 기기
WO2017185368A1 (zh) 一种信令传输方法和设备
WO2017096592A1 (zh) 无线通信中的数据处理方法及装置
WO2021109966A1 (zh) 通信处理方法和通信处理装置
WO2021000763A1 (zh) 数据传输方法及装置
CN105874873B (zh) 状态迁移的方法、用户设备和无线网络控制器
WO2021004207A1 (zh) 数据处理的方法和设备
CN105323786A (zh) 一种pdcp状态报告组建方法及装置
CN110351103B (zh) 服务数据适配协议sdap实体的配置方法及设备
TWI670983B (zh) 一種保持ｕｄｃ功能連續性的方法及設備
CN109716822B (zh) 控制终端设备产生上行信令的方法、终端设备和网络设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20749437

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021544648

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20217026361

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020749437

Country of ref document: EP

Effective date: 20210830

WWG Wipo information: grant in national office

Ref document number: 2020749437

Country of ref document: EP