WO2021017812A1 - 用户设备及其执行的方法和基站及其执行的方法 - Google Patents

用户设备及其执行的方法和基站及其执行的方法 Download PDF

Info

Publication number
WO2021017812A1
WO2021017812A1 PCT/CN2020/101837 CN2020101837W WO2021017812A1 WO 2021017812 A1 WO2021017812 A1 WO 2021017812A1 CN 2020101837 W CN2020101837 W CN 2020101837W WO 2021017812 A1 WO2021017812 A1 WO 2021017812A1
Authority
WO
WIPO (PCT)
Prior art keywords
ehc
drb
uplink
continueehc
pdcp
Prior art date
Application number
PCT/CN2020/101837
Other languages
English (en)
French (fr)
Inventor
肖芳英
刘仁茂
Original Assignee
夏普株式会社
肖芳英
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 夏普株式会社, 肖芳英 filed Critical 夏普株式会社
Publication of WO2021017812A1 publication Critical patent/WO2021017812A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • 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/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
    • 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

Definitions

  • the present disclosure relates to the field of wireless communication technology. More specifically, the present disclosure relates to user equipment and the configuration method, entity reconstruction method, and entity operation method performed by the user equipment, as well as the base station and the method performed by it.
  • Ethernet header compression is a method to reduce the overhead caused by Ethernet header transmission. Ethernet frames can be transmitted in the Ethernet PDU session type through the 5G system. In an Ethernet-based industrial Internet of Things network, the payload size is relatively small relative to the overall size of the frame. Therefore, compressing the Ethernet frame header can improve transmission efficiency and reduce delay.
  • Ethernet header compression (EHC) mechanism It was reached at the 3GPP RAN2#105bis meeting held in April 2019 that 100% of the Ethernet header compression (EHC) mechanism will be defined in 3GPP. Reached at the 3GPP RAN2#106 meeting held in May 2019: Separate configuration of Ethernet header compression protocol for the uplink and downlink of each data radio bearer DRB; the compression end (Compressor) and decompression end (Decompressor) use contextual identification
  • the concept of (Context ID) associates a context identifier with Ethernet header contents; and EHC is based on the following mechanism: For an Ethernet stream that generates a new context, the compression end sends at least one containing a complete header and a context identifier , So that the decompression end can establish the context, and then the compression end will transmit the compressed packet; the header of the data packet generated by Ethernet header compression includes at least the following fields: context identifier, used to indicate the header format of the data packet The indication identifier (that is, it indicates whether the header of the data
  • this disclosure discusses the related problems and solutions involved in Ethernet header compression, including: the configuration of EHC related parameters; if EHC is adopted, what operations need to be performed when the PDCP entity is rebuilt; when the received includes a suspended RRC connection When the indication (that is, the RRC release message contains the configuration suspendConfig used to indicate the RRC_INACTIVE state), what operations the PDCP entity should perform and how the PDCP entity sender manages the context of Ethernet header compression.
  • the present disclosure has been completed in view of the above problems, and its purpose is to provide a user equipment that can improve transmission efficiency, reduce delay, and reduce overhead caused by Ethernet header transmission, and a configuration method, entity reconstruction method and entity performed by the user equipment. Operation method, base station and method of execution thereof.
  • a method executed by a user equipment which is a method for configuring an EHC indicator for Ethernet header compression implemented on a user equipment UE, including the following steps: UE receives radio resource control from a base station RRC message, the RRC message contains the indication identifier maxCID and/or indication identifier drb-ContinueEHC for uplink EHC and/or downlink EHC, the indication identifier maxCID is used to indicate the maximum context identifier, and the indication identifier drb-ContinueEHC is used to indicate when Whether the PDCP entity continues the uplink and/or downlink EHC when the PDCP re-establishment of the packet data convergence protocol occurs; the UE shares and/or separately configures the indication identifier maxCID and/or the indication identifier drb-ContinueEHC for the uplink EHC and the downlink EHC.
  • the maximum value of the context identifier maxCID_DL, the value of maxCID or maxCID_UL or maxCID_DL is one of the following: the maximum value of the context identifier is maxCID or maxCID_UL or maxCID_DL, or the maximum value of the context identifier is maxCID-1 or maxCID_UL-1 Or maxCID_DL-1; indicates the number of bits or bytes occupied by the context identifier; indicates whether the maximum value of the context identifier is a large value or a small value.
  • the maximum context identifier is configured separately for the uplink EHC and the downlink EHC, then for the uplink data radio bearer DRB with reflected quality of service, the maximum context identifier allocated for the uplink EHC
  • the value maxCID_UL is the same as the maximum context identifier maxCID_DL configured for downlink EHC, or the value of maxCID_UL is less than or equal to the value of maxCID_DL, or the value of maxCID_UL is greater than or equal to the value of maxCID_DL.
  • the user equipment it is preferable to configure only one continued EHC indicator drb-ContinueEHC for the uplink EHC and downlink EHC to use together; or configure a continued EHC indicator drb-ContinueEHC_UL for the uplink EHC, which is Downlink EHC is configured with a continued EHC indication flag drb-ContinueEHC_DL, the value of drb-ContinueEHC or drb-ContinueEHC_UL or drb-ContinueEHC_DL is one of the following: represents the value of the PDCP entity continuing EHC when PDCP re-establishment occurs; represents when PDCP occurs The PDCP entity resets the EHC value during reconstruction.
  • a method executed by a user equipment which is a method for entity reconstruction of a packet data convergence protocol PDCP based on the Ethernet header compression EHC mechanism implemented on the user equipment UE, including the following steps: UE
  • the PDCP entity receives the PDCP entity reconstruction request from the upper layer; the EHC context is processed in one of the following ways: for the data of the non-acknowledged mode UM that uses the radio link control RLC, the radio bearer UM DRB and the data of the acknowledged mode AM that uses the RLC Radio bearer AM DRB, if EHC or uplink EHC or downlink EHC is configured, discard or release the context of EHC or uplink EHC or downlink EHC and/or set CID to 0 or 1 or initial value; for UM DRB and AM DRB, If EHC or uplink EHC or downlink EHC is configured, when drb-ContinueEHC or drb-ContinueEHC_UL or drb-Contin
  • a method executed by a user equipment which is implemented on the user equipment UE when the radio resource control RRC connection is released or suspended, and the PDCP entity performs the Ethernet header compression EHC
  • the method of operation includes the following steps: the RRC entity of the UE receives from the base station an RRCelease message for ordering to release or suspend the RRC connection, the RRCelease message contains a suspendConfig cell, and the suspendConfig cell is used to indicate the configuration of the RRC inactive RRC_INACTIVE state ; If the received RRCRelease message is not a response message for requesting to continue a suspended RRC connection, the lower-layer entity is instructed to suspend PDCP. After the PDCP entity receives the request from the upper layer to suspend the PDCP entity, the sender of the PDCP entity Or the receiving end performs operations on EHC.
  • the PDCP entity sending end performs the following operations: if the uplink EHC is configured, the storage between the Ethernet header and the context identifier CID Or store the mapping relationship between the compressed Ethernet header and the context identifier CID, and/or store the current assigned maximum context identifier CID; when the upper layer requests the suspension of the PDCP entity, the PDCP entity receiver Perform the following operations: If the downlink EHC is configured, store the mapping relationship between the Ethernet header and the context identifier CID, or store the mapping relationship between the compressed Ethernet header and the context identifier CID.
  • a method executed by a base station for enabling a user equipment UE to implement the configuration of an EHC indicator for Ethernet header compression includes the following steps: sending a radio resource control RRC message to the UE.
  • the RRC message contains the indication identifier maxCID and/or the indication identifier drb-ContinueEHC for the uplink EHC and/or the downlink EHC, which are used to enable the UE to share and/or separately configure the indication identifier maxCID and/or the indication identifier for the uplink EHC and the downlink EHC.
  • the indication identifier drb-ContinueEHC is used to indicate the maximum value of the context identifier, and the indication identifier drb-ContinueEHC is used to indicate whether the PDCP entity continues uplink and/or downlink EHC when the packet data convergence protocol PDCP reestablishment occurs.
  • a user equipment including: a processor; and a memory on which instructions are stored, and when the instructions are executed by the processor, the user equipment is The method performed by the user equipment described above.
  • a base station including: a processor; and a memory on which instructions are stored.
  • the base station executes The described method is performed by the base station.
  • entity reconstruction method since it involves the content of Ethernet header compression EHC, it can improve transmission efficiency and reduce delay , And can reduce the overhead caused by Ethernet header transmission.
  • Fig. 1 is a configuration method of an EHC indicator for Ethernet header compression implemented on a user equipment UE.
  • Fig. 2 is a method for configuring the indicator of the Ethernet header compression EHC executed by the base station for the user equipment UE.
  • Fig. 3 is a method of PDCP entity reconstruction based on the EHC mechanism implemented on the user equipment UE.
  • FIG. 4 is a method of operations performed by a PDCP entity on EHC when the RRC connection is released or suspended, implemented on the user equipment UE.
  • Fig. 5 is a schematic block diagram of a user equipment UE involved in the present disclosure.
  • Fig. 6 is a schematic block diagram of a base station involved in the present disclosure.
  • EHC Ethernet Header Compression, Ethernet header compression.
  • DRB Data Radio Bearer, data radio bearer.
  • RRC Radio Resource Control, radio resource control.
  • PDCP Packet Data Convergence Protocol, packet data convergence protocol.
  • SDAP Service Data Adaptation Protocol, service data adaptation protocol.
  • RLC Radio Link Control, radio link control.
  • the RLC entity can be configured to use one of the following three modes for data transmission: transparent transmission mode TM, unconfirmed mode UM or confirmed mode AM.
  • MAC Medium Access Control, media access control.
  • RLC AM DRB Use RLC AM DRB (a data radio bearer which utilizes RLC AM).
  • SDU Service Data Unit, service data unit.
  • PDU Protocol Data Unit, protocol data unit.
  • data received or delivered from the upper layer is referred to as SDU
  • data submitted or received from the lower layer is referred to as PDU
  • the data received by the PDCP entity from the upper layer or the data transmitted by the upper layer is called PDCP SDU
  • the data received by the PDCP entity from the RLC entity or the data submitted to the RLC entity is called PDCP PDU (that is, RLC SDU).
  • 3GPP has reached an agreement to separately configure uplink and downlink EHC for a DRB.
  • uplink and downlink EHC There are two different understandings for configuring uplink and downlink EHC separately.
  • Parameters such as profiles that can be activated or support header compression can be configured separately, but some parameters can be configured together (that is, a parameter is configured for uplink and/or downlink use).
  • Figure 1 is used to describe the method for configuring the indicator of the Ethernet header compression EHC implemented on the user equipment UE.
  • the UE receives an RRC message from the base station, and the message contains configuration information of uplink EHC and/or downlink EHC.
  • the RRC message includes an indication identifier maxCID for the uplink EHC and/or downlink EHC for indicating the maximum value of the context identifier and/or for indicating whether the PDCP entity continues to uplink and/or when PDCP re-establishment occurs. Or the indication of downstream EHC (or whether to reset EHC) drb-ContinueEHC.
  • step S1002 the UE configures the indication identifier maxCID and/or the indication identifier drb-ContinueEHC in common and/or separately for the uplink EHC and the downlink EHC.
  • Embodiment 1 Uplink EHC and downlink EHC share a maximum context identifier
  • maxCID of the context identifier CID is configured for both uplink and downlink use.
  • the value of maxCID can be an integer.
  • the meaning of maxCID value can be one of the following: 1) indicates that the maximum value of the context identifier is maxCID or the maximum value of the context identifier is maxCID-1; 2) indicates the number of bits or bytes occupied by the context identifier (for example, , The number of bits or bytes occupied in the PDCP header or PDCP PDU header or compressed packet header); 3) indicates whether the maximum value of the context identifier is a large value or a small value.
  • maxCID of 2 means that the context identifier CID occupies 2 bits or 2 bytes.
  • the maximum value of CID is 3 or 4. If it is 2 bytes, the maximum value of CID is 65536 or 65535.
  • the pre-defined maxCID there are two possible values for the pre-defined maxCID, one is 15 and the other is 65535 (or two other different values), when the maxCID value is "true” or true or "1" or said If the logo appears, it means that the maximum value that the upstream text identifier can take is a large value.
  • the maxCID value is "false” or false or "0" or the logo does not appear, it means that the maximum value that the upstream text identifier can take is a small value, and vice versa.
  • the maxCID value is "false” or false or "0" or the logo does not appear, it means that the maximum value that the upstream text identifier can take is a small value, and vice versa.
  • Embodiment 2 Uplink EHC and downlink EHC respectively configure the maximum value of the context identifier
  • a maximum context identifier maxCID_UL is configured for uplink EHC
  • a maximum context identifier maxCID_DL is configured for downlink EHC.
  • the meaning of the value of maxCID_UL (or maxCID_DL) can be one of the following: 1) It means that the maximum value of the context identifier is maxCID_UL (or maxCID_DL) or the maximum value of the context identifier is maxCID_UL-1 (or maxCID_DL) -1); 2) indicates the number of bits or bytes occupied by the context identifier (for example, the number of bits or bytes occupied by the PDCP header or PDCP PDU header or compressed packet header); 3) indicates the context identifier Whether the maximum value is a large value or a small value.
  • maxCID_UL (or maxCID_DL) of 2 means that the context identifier CID occupies 2 bits or 2 bytes. If it is 2 bits, the maximum value of CID is 3 or 4, and if it is 2 bytes, the maximum value of CID is The value is 65536 or 65535.
  • maxCID_UL (or maxCID_DL) takes the value "true” or True or "1" or the presence of the identifier indicates that the maximum value that the uplink identifier can take is a large value.
  • maxCID_UL or maxCID_DL
  • the maximum value that can be taken for the writing mark is a small value, and vice versa.
  • the maximum value of the context identifier maxCID_UL for the uplink EHC should be the same as the maximum value of the context identifier for the downlink EHC.
  • the maxCID_DL is the same (or the value of maxCID_UL should be less than or equal to the value of maxCID_DL or the value of maxCID_UL should be greater than or equal to the value of maxCID_DL).
  • the DRB that uses reflective QoS is the DRB that uses the reflective QoS flow to the DRB mapping or the information element used to configure the SDAP configurable parameters of the DRB in the received RRC message is not included in the SDAP-Config
  • the DRB of the cell mappedQoS-FlowsToAdd or the DRB without the mapping relationship between the quality of service flow (QoS-Flows) and the DRB or the DRB without the quality of service flow mapped to this DRB or the DRB configured with the downlink SDAP header (header) DRB for example, the SDAP-Config information element used to configure the SDAP configurable parameter of the DRB in the received RRC message contains the sdap-HeaderDL information element whose value is set to "present").
  • the cell mappedQoS-FlowsToAdd is used to indicate the list of QFIs that are additionally mapped to this DRB in a PDU session (Indicates the list of QFIs of UL QoS flows of the PDU session to be additionally mapped to this DRB)
  • the sdap-HeaderDL information element is used to indicate whether the downlink data corresponding to the DRB contains the SDAP header.
  • Reflective QoS flow to DRB mapping (Reflective QoS flow to DRB mapping) is a QoS flow to DRB mapping mechanism, in which the UE monitors the downlink QoS flow to DRB mapping rule and applies it to the uplink.
  • the context identifier CID assigned to the Ethernet header or the compressible field of the header may be indicated by a variable, such as CID_Next, and its initial value may be set to 0 or 1.
  • the processing of the context identifier may be one of the following methods:
  • CID_Next For Ethernet packets or frames or PDCP SDU headers or compressible fields that need to be assigned a context identifier CID (for example, Ethernet packets or frames received from the upper layer or PDCP S
  • CID_Next For Ethernet packets or frames or PDCP SDU headers or compressible fields that need to be assigned a context identifier CID (for example, Ethernet packets or frames received from the upper layer or PDCP SDU headers or headers Some compressible fields are not mapped to any context identifier) and/or if there is an available CID value or CID_Next does not reach the maximum value that can be used (for example, CID_Next is less than maxCID or maxCID-1, or CID_Next is less than or equal to maxCID or maxCID-1) , Increase the current value of CID_Next by 1, and then associate it with this header or header compressible field. In this case, CID_Next always saves the value of the context identifier last assigned to the header or compressible field of the Ethernet packet or frame or PDCP SDU or data packet.
  • CID_Next always saves the value of the context identifier last assigned to the header or compressible field of the Ethernet packet or frame or PDCP SDU or data packet.
  • CID For Ethernet packets or frames or PDCP SDU headers or compressible fields that need to be assigned a context identifier CID (for example, Ethernet packets or frames received from the upper layer or PDCP SDU headers or headers The compressible field is not mapped to any context identifier), and the minimum value of the CID that is not currently allocated (or available or not yet associated with any Ethernet header or header compressible field) is associated with this header or header Compressible fields.
  • the received Ethernet packet or frame or PDCP PDU or data packet is not within the allowable range (for example, the CID is greater than or equal to maxCID or maxCID-1), then the received Ethernet packet is discarded Text or frame or PDCP PDU or PDCP SDU or data packet.
  • the packet type indicator indicates this Ethernet packet Or frame or PDCP PDU is an Ethernet message or frame or PDCP PDU or data packet that contains a complete header, then the mapping relationship between CID and Ethernet message or frame or PDCP PDU or data packet header or header compressible field is stored ; If the packet type indicator indicates that this Ethernet message or frame or PDCP PDU or data packet is a compressed packet, then according to the CID carried in this Ethernet message or frame or PDCP PDU or data packet to restore its Ethernet header or The header can compress field information.
  • the uncompressed packet refers to this Ethernet packet or frame or PDCP PDU or data packet containing a complete header Ethernet packet or frame or PDCP PDU or data packet
  • the compressed packet refers to this Ethernet packet or
  • the frame, PDCP PDU, or data packet does not include a complete header or does not include a compressible header.
  • the packet type indicator is used to indicate whether the corresponding Ethernet packet or frame or PDCP PDU or data packet is a compressed packet or an uncompressed packet (that is, includes this indicator).
  • a value can be pre-defined or configured through an RRC message to indicate that the PDCP PDU carrying the CID value is not compressed, and the pre-defined or configured CID value through the RRC message is called an uncompressed indication.
  • the CID field of the PDCP PDU also called Ethernet packet or frame or data packet or compressed packet
  • a predefined value for example, 0
  • a configured value it means that the Ethernet packet or frame or The data packet or PDCP PDU carries a complete Ethernet header.
  • the PDCP entity receiving end uses EHC for decompression, if the CID field in the received PDCP PDU is set to the predefined or configured value, the PDCP entity receiving end does not store the mapping relationship between the CID and the Ethernet header .
  • This pre-defined or RRC configured value is used when the PDCP entity sender thinks that the Ethernet header does not need to be compressed (or there is no available CID value or all CID values except this value have been established with the Ethernet Header mapping relationship) set the CID field of the PDCP PDU to this predefined or RRC configured value.
  • associating the context identifier CID with the Ethernet header or establishing a mapping relationship refers to combining a CID with a specific value with a compressible field of the Ethernet header (that is, the compressible field of the Ethernet header) A value of the compressed field).
  • the compressible fields of the Ethernet header may include one or more of the following fields: destination address (DESTINATION ADDRESS), source address (SOURCE ADDRESS), type/length (TYPE/ LENGTH), Q-TAGs.
  • the Q-TAGs field may include the following fields: VLAN identification VID field, PRI field indicating the priority of the Ethernet frame, frame type field TPID, and DEI field used to indicate whether it is discardable.
  • VLAN identification VID field PRI field indicating the priority of the Ethernet frame
  • frame type field TPID TPID
  • DEI field used to indicate whether it is discardable.
  • the available CID value described in this disclosure is a context identifier that is not associated/mapped to any Ethernet header or header compressible field, and the context identifier is not an uncompressed indication (or called a default context identifier, which is applicable to The system supports the default context identification).
  • mapping (or associating) the header or compressible field of the Ethernet packet or frame or PDCP SDU to the context identifier is to map (or associate) the context identifier to the Ethernet packet or frame or
  • the header or compressible field of the PDCP SDU also means that the Ethernet packet or frame or the header or compressible field of the PDCP SDU is assigned a context identifier.
  • Embodiment 3 Uplink EHC and downlink EHC share one continue EHC indicator drb-ContinueEHC
  • only one continued EHC indicator drb-ContinueEHC is configured for both uplink and downlink use.
  • the value of drb-ContinueEHC is one of the following: 1) indicates the value of the PDCP entity continuing EHC when the PDCP reconstruction occurs; 2) indicates the value of the PDCP entity resetting the EHC when the PDCP reconstruction occurs.
  • the PDCP entity continues EHC header compression (ie, uplink EHC header compression and/or downlink EHC header compression) when PDCP re-establishment occurs ;
  • EHC header compression ie, uplink EHC header compression and/or downlink EHC header compression
  • the EHC header compression is reset in the PDCP entity. vice versa.
  • the PDCP entity's continued EHC header compression refers to the operations performed on the EHC when the PDCP entity is rebuilt when the Ethernet header compression EHC is configured as described in other embodiments of the present disclosure.
  • PDCP entity reset EHC header compression (also called reset EHC or reset uplink EHC or downlink EHC) is the EHC context and EHC context and EHC header compression involved in resetting EHC header compression at the transmitting end or receiving end of the PDCP entity described in other embodiments of the present disclosure. / Or processing of related variables.
  • the PDCP entity discards or releases the mapping relationship between the uplink and/or downlink context identifier CID and the compressible field of the Ethernet header, and the PDCP entity sender resends the PDCP PDU containing the complete header and its corresponding context identifier CID for use
  • Establishing the correspondence between the CID and the compressible field of the Ethernet header may also include initializing the value of the header compression related variable, for example, setting the CID_Next mentioned in other embodiments to the initial value.
  • Resetting the uplink EHC means resetting the EHC at the receiving end of the PDCP entity
  • resetting the downlink EHC means resetting the EHC at the PDCP sending end.
  • Embodiment 4 Uplink EHC and Downlink EHC are configured separately to continue EHC indicator
  • a continuous EHC indicator drb-ContinueEHC_UL is configured for uplink EHC
  • a continuous EHC indicator drb-ContinueEHC_DL is configured for downlink EHC.
  • the value of drb-ContinueEHC_UL or drb-ContinueEHC_DL is one of the following: 1) indicates the value of the PDCP entity continuing the uplink or downlink EHC when PDCP reestablishment occurs; 2) indicates the value of the PDCP entity resetting the uplink or downlink EHC when PDCP reestablishment occurs value.
  • the PDCP entity when the value of drb-ContinueEHC_UL (or drb-ContinueEHC_DL) is TRUE or true or the indicator appears, the PDCP entity continues EHC header compression or uplink EHC header compression (or downlink EHC header compression) when PDCP re-establishment occurs. EHC header compression); when the value of drb-ContinueEHC_UL (or drb-ContinueEHC_DL) is False or false or the indicator does not appear, the PDCP entity resets EHC header compression or uplink EHC header compression (or downlink EHC header compression). vice versa.
  • this embodiment also supports the configuration of only the continuous EHC indicator drb-ContinueEHC_UL of the uplink EHC or the configuration of only the continued EHC indicator drb-ContinueEHC_DL of the downlink EHC.
  • the SDAP entity maps all QoS flows that do not define the DRB that should be mapped to the default DRB.
  • EHC including uplink EHC and/or downlink EHC
  • the default DRB means that the cell SDAP-Config used to set the SDAP configurable parameter of the DRB does not contain the cell defaultDRB or the value of the defaultDRB is set to "false".
  • the cell defaultDRB is used to indicate whether the corresponding DRB is the default DRB of this PDU session (PDU session).
  • FIG. 2 specifically uses FIG. 2 to describe the method for configuring the indicator identifier of the Ethernet header compression EHC executed by the base station for the user equipment UE to implement.
  • a radio resource control RRC message is sent to the UE.
  • the RRC message includes an indication identifier maxCID and/or an indication identifier drb-ContinueEHC for uplink EHC and/or downlink EHC, which is used to make the UE target
  • the uplink EHC and the downlink EHC share and/or separately configure the indication identifier maxCID and/or the indication identifier drb-ContinueEHC.
  • the indication identifier maxCID is used to indicate the maximum value of the context identifier
  • the indication identifier drb-ContinueEHC is used to indicate whether the PDCP entity continues uplink and/or downlink EHC when the PDCP reestablishment of the packet data convergence protocol occurs.
  • the method for configuring the two indicator flags, the indicator flag maxCID and the indicator flag drb-ContinueEHC, is also the same as the foregoing embodiment.
  • the method executed by the base station corresponding to the method executed by the user equipment is also similar to this embodiment.
  • EHC and PDCP entities can be one of the following:
  • EHC uplink EHC and/or downlink EHC
  • the PDCP entity is always (always) rebuilt during DRB reconfiguration. Specifically, if EHC (or uplink EHC or downlink EHC) is configured, when performing DRB reconfiguration, the PDCP entity is always rebuilt.
  • the indicator reestablishPDCP defined in the existing TS38.331 protocol used to indicate that the PDCP entity should be reestablished must carry and/ Or set to "true” (that is, the reestablishPDCP corresponding to this DRB is set to "true” in the RRC message containing the reconfiguration of the DRB sent by the network or base station to the UE).
  • EHC uplink EHC and/or downlink EHC
  • the PDCP entity can (be able to) be re-established during DRB reconfiguration.
  • EHC uplink EHC and/or downlink EHC
  • the network instructs the UE to instruct the UE by configuring the indicator reestablishPDCP defined in the existing TS38.331 protocol to indicate that the PDCP entity should be reestablished Whether to rebuild the PDCP entity for the corresponding DRB.
  • Fig. 3 is used to describe the method of PDCP entity reconstruction based on the EHC mechanism implemented on the user equipment UE.
  • step S3001 the PDCP entity of the UE receives a PDCP entity re-establishment request from the upper layer.
  • the PDCP entity (that is, the PDCP entity transmitter or receiver) can process the EHC context in one of the following ways:
  • EHC For UM DRB and AM DRB, if downlink EHC is configured, when drb-ContinueEHC_DL is not configured, EHC is reset. Specifically, the downstream EHC context is discarded or released (and/or the downstream EHC is reset and starts from the complete header or from the complete header and the complete header indicator).
  • the cell rohc is used to configure the relevant parameters that need to be configured using ROHC (including uplink and downlink) (Robust Header Compression), and the cell uplinkOnlyROHC is used to configure the relevant parameters that need to be configured for the uplink using ROHC, and the cell drb -ContinueROHC is used to indicate whether the PDCP entity continues or resets the ROHC header compression protocol when the PDCP entity is rebuilt.
  • ROHC including uplink and downlink
  • ROHC Robust Header Compression
  • the cell uplinkOnlyROHC is used to configure the relevant parameters that need to be configured for the uplink using ROHC
  • the cell drb -ContinueROHC is used to indicate whether the PDCP entity continues or resets the ROHC header compression protocol when the PDCP entity is rebuilt.
  • the information element drb-ContinueEHC is used to indicate whether the PDCP entity continues or resets the EHC header compression protocol when the PDCP entity is rebuilt
  • the information element drb-ContinueEHC_UL is used to indicate whether the PDCP entity sender continues or resets the EHC header compression when the PDCP entity is rebuilt Protocol
  • the information element drb-ContinueEHC_DL is used to indicate whether the receiving end of the PDCP entity continues or resets the EHC header compression protocol when the PDCP entity is rebuilt.
  • EHC is EHC header compression protocol or Ethernet header compression protocol.
  • Drb-ContinueROHC (or drb-ContinueEHC or drb-ContinueEHC_UL or drb-ContinueEHC_UL) is not configured or includes the drb-ContinueROHC (or drb-ContinueEHC or drb-ContinueEHC_UL or drb-ContinueEHC_UL) cell in the received RRC message, or drb -ContinueROHC (or drb-ContinueEHC or drb-ContinueEHC_UL or drb-ContinueEHC_UL) cell value is not the value corresponding to continue ROCH (or EHC), such as drb-ContinueROHC (or drb-ContinueEHC or drb-ContinueEHC_UL or drb-ContinueEHC_UL) ) The cell value is false
  • the suspendConfig cell is used to indicate the configuration of the RRC_INACTIVE state.
  • the RRCRelease message is used to command to release the RRC connection or suspend the RRC connection.
  • the RRCResumeRequest message is a 48-bit message that is used to request to continue a suspended RRC connection or perform an RNA update.
  • the RRCResumeRequest1 message is a 64-bit message that is used to request to continue a suspended RRC connection or perform RAN-based Notification Area (RNA) update.
  • RNA Notification Area
  • Figure 4 is used to describe the method for the operation performed by the PDCP entity on the EHC when the RRC connection is released or suspended on the user equipment UE.
  • step S4001 the RRC entity of the UE receives an RRCelease message for ordering to release or suspend the RRC connection from the base station;
  • step S4002 if the received RRCRelease message is not a message for requesting to continue a suspended RRC connection, the lower layer entity (ie, the PDCP entity) is instructed to suspend PDCP.
  • the PDCP entity receives a request from the upper layer (ie, RRC) to suspend the PDCP entity, the sender or receiver of the PDCP entity performs operations on the EHC (uplink EHC or downlink EHC).
  • the EHC context is stored, or if the EHC (or uplink EHC or downlink EHC) is configured, the EHC (or Uplink EHC or Downlink EHC) context.
  • the PDCP entity sender When the upper layer (for example, RRC) requests the PDCP entity to suspend, the PDCP entity sender performs the following operations: if the uplink EHC is configured, the EHC (ie, uplink EHC) context is stored. Specifically, the mapping relationship between the Ethernet header and the context identifier CID is stored, or the mapping relationship between the compressed Ethernet header and the context identifier CID is stored, and/or the largest context identifier CID currently assigned ( If the assigned context identifier CID is also indicated by a variable, such as CID_Next, then the current value of CID_Next is saved).
  • the EHC ie, uplink EHC
  • the mapping relationship between the Ethernet header and the context identifier CID is stored, or the mapping relationship between the compressed Ethernet header and the context identifier CID is stored, and/or the largest context identifier CID currently assigned ( If the assigned context identifier CID is also indicated by a variable, such as CID_Next, then the current value of C
  • the PDCP entity receiving end performs the following operations: if the downlink EHC is configured, the EHC (ie, downlink EHC) context is stored. Specifically, the mapping relationship between the Ethernet header and the context identifier CID is stored, or the mapping relationship between the compressed Ethernet header and the context identifier CID is stored.
  • the uplink EHC configured means that the configuration message of the corresponding DRB (that is, the RRC message for configuring or reconfiguring the DRB) contains an ehc_UL cell for indicating compression of the uplink Ethernet header, and the ehc_UL cell contains Related parameters that need to be configured when the PDCP entity performs uplink EHC, and the parameters may include: maxCID_UL, drb-ContinueEHC_UL.
  • Configured downlink EHC means that the corresponding DRB configuration message (that is, the RRC message for configuring or reconfiguring the DRB) contains the ehc_DL cell used to indicate the compression of the downlink Ethernet header, and the ehc_DL cell contains the PDCP entity that is required when performing downlink EHC Configuration related parameters, the parameters may include: maxCID_DL, drb-ContinueEHC_DL.
  • EHC configured means that uplink EHC and/or downlink EHC are configured.
  • the following describes an embodiment of the EHC context management by the PDCP entity transmitter.
  • the UE receives the RRC message from the base station (for example, gNB), which contains the cell ehc_Timer, which is used to set the value of the timer ehc_Timer.
  • the RRC message includes an information element ehc_UL for configuring uplink EHC related parameters, and the information element ehc_Timer is included in ehc_UL.
  • the ehc_Timer is associated with the CID carried in the PDCP PDU, that is, CIDs with different values Associate an ehc_Timer.
  • the association of ehc_Timer with CID means that ehc_Timer is associated with a specific compressible field in the Ethernet header.
  • the Ethernet compressed packet may be a PDCP PDU containing a complete Ethernet header or a PDCP PDU that does not carry a complete Ethernet header for establishing a CID and the compressible field of the Ethernet header. In other words, the value of the CID field included in the PDCP PDU containing the Ethernet compressed packet is not an uncompressed indication.
  • Fig. 5 is a schematic block diagram of a user equipment UE involved in the present disclosure.
  • the user equipment UE500 includes a processor 501 and a memory 502.
  • the processor 501 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 502 may include, for example, volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memories.
  • the memory 502 stores program instructions. When the instruction is executed by the processor 501, it can execute the above-mentioned method executed by the user equipment described in detail in this disclosure.
  • Fig. 6 is a schematic block diagram of a base station involved in the present disclosure.
  • the base station 600 includes a processor 601 and a memory 602.
  • the processor 601 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 602 may include, for example, volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memories.
  • the memory 602 stores program instructions. When the instruction is executed by the processor 601, it can execute the above-mentioned method executed by the base station described in detail in this disclosure.
  • the computer-executable instructions or program running on the device according to the present invention may be a program that enables the computer to implement the functions of the embodiments of the present invention by controlling a central processing unit (CPU).
  • the program or the information processed by the program can be temporarily stored in volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.
  • Computer-executable instructions or programs for implementing the functions of the various embodiments of the present invention may be recorded on a computer-readable storage medium. Corresponding functions can be realized by causing the computer system to read the programs recorded on the recording medium and execute these programs.
  • the so-called “computer system” herein may be a computer system embedded in the device, and may include an operating system or hardware (such as peripheral devices).
  • the "computer-readable storage medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium storing a program dynamically for a short time, or any other recording medium readable by a computer.
  • circuits for example, single-chip or multi-chip integrated circuits.
  • Circuits designed to perform the functions described in this specification can include general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the above devices.
  • the general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine.
  • the above-mentioned circuit can be a digital circuit or an analog circuit. In the case of new integrated circuit technologies that replace existing integrated circuits due to advances in semiconductor technology, one or more embodiments of the present invention can also be implemented using these new integrated circuit technologies.
  • the present invention is not limited to the above-mentioned embodiment. Although various examples of the embodiment have been described, the present invention is not limited thereto.
  • Fixed or non-mobile electronic equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, such as AV equipment, kitchen equipment, cleaning equipment, air conditioning, office equipment, vending machines, and other household appliances.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明提供一种用户设备及其执行的方法和基站及其执行的方法。由用户设备执行的方法是在用户设备UE上实现的以太网头压缩EHC的指示标识的配置方法，包括如下步骤：UE接收来自基站的无线资源控制RRC消息，该RRC消息包含针对上行EHC和/或下行EHC的指示标识maxCID和/或指示标识drb-ContinueEHC，该指示标识maxCID用于指示上下文标识最大值，该指示标识drb-ContinueEHC用于指示当发生分组数据汇聚协议PDCP重建时PDCP实体是否继续上行和/或下行EHC；UE针对上行EHC和下行EHC共用和/或分开配置所述指示标识maxCID和/或所述指示标识drb-ContinueEHC。

Description

用户设备及其执行的方法和基站及其执行的方法 技术领域
本公开涉及无线通信技术领域，更具体地，本公开涉及用户设备及其执行的配置方法、实体重建方法和实体操作方法、以及基站及其执行的方法。
背景技术
2019年3月，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#83次全会上批准了一个支持NR工业物联网的工作项目(参见RP-190728：New WID：Support of NR Industrial Internet of Things(IoT))。该工作项目的目标之一是定义基于结构感知(structure-aware)算法的以太网头压缩协议。以太网头压缩是一种减少以太网头传输带来的开销的方法，以太网帧可以通过5G系统以以太网PDU会话类型传输。在基于以太网的工业物联网网络中，有效负载大小相对于帧的整体大小相对较小，因此对以太网帧头部进行压缩可以提高传输效率、减少延迟。
在2019年4月召开的3GPP RAN2#105bis次会议上达成：将100％的在3GPP定义以太网头压缩(Ethernet Header Compression，EHC)机制。在2019年5月召开的3GPP RAN2#106次会议上达成：对每个数据无线承载DRB的上行和下行分别单独配置以太网头压缩协议；压缩端(Compressor)和解压端(Decompressor)采用上下文标识(Context ID)的概念将一个上下文标识与以太网头部内容(Ethernet header contents)关联；且EHC基于以下机制：对于产生新上下文的以太网流，压缩端至少发送一个包含完整头部和上下文标识的报文，以便于解压端建立上下文，之后压缩端传输压缩后的报文；以太网头压缩产生的数据包的头部至少包括以下字段：上下文标识，用于指示本数据包的头部格式的指示标识(即指示本数据包的头部是完整头部还是压缩后的头部)。
基于以上结论，本公开讨论以太网头压缩所涉及的相关问题及解决方案，具体包括：EHC相关参数的配置；如果采用EHC，PDCP实体重建时需要执行哪些操作；当接收到包含挂起RRC连接的指示(即RRC释放消息中包含用于指示RRC_INACTIVE状态的配置suspendConfig)时，PDCP实体应该执行哪些操作以及PDCP实体发送端如何管理以太网头压缩的上下文。
发明内容
本公开正是鉴于上述问题而完成的，其目的在于，提供一种能够提高传输效率、减少延迟并减少以太网头传输带来的开销的用户设备及其执行的配置方法、实体重建方法和实体操作方法、以及基站及其执行的方法。
根据本发明的一个方面，提供了一种由用户设备执行的方法，是在用户设备UE上实现的以太网头压缩EHC的指示标识的配置方法，包括如下步骤：UE接收来自基站的无线资源控制RRC消息，该RRC消息包含针对上行EHC和/或下行EHC的指示标识maxCID和/或指示标识drb-ContinueEHC，该指示标识maxCID用于指示上下文标识最大值，该指示标识drb-ContinueEHC用于指示当发生分组数据汇聚协议PDCP重建时PDCP实体是否继续上行和/或下行EHC；UE针对上行EHC和下行EHC共用和/或分开配置所述指示标识maxCID和/或所述指示标识drb-ContinueEHC。
在上述的由用户设备执行的方法中，优选的是，仅配置一个上下文标识最大值maxCID供上行EHC和下行EHC共同使用；或者，为上行EHC配置一个上下文标识最大值maxCID_UL，为下行EHC配置一个上下文标识最大值maxCID_DL，所述maxCID或maxCID_UL或maxCID_DL的取值是以下之一：表示上下文标识的最大取值为maxCID或maxCID_UL或maxCID_DL、或者上下文标识的最大取值为maxCID-1或maxCID_UL-1或maxCID_DL-1；表示上下文标识所占的比特数或字节数；表示上下文标识的最大取值是大值还是小值。
在上述的由用户设备执行的方法中，优选的是，如果为上行EHC和下行EHC分开配置上下文标识最大值，则对于上行采用反射服务质量的数据无线承载DRB，为上行EHC分配的上下文标识最大值maxCID_UL与为 下行EHC配置的上下文标识最大值maxCID_DL相同、或者maxCID_UL的值小于或等于maxCID_DL的值、或者maxCID_UL的值大于或等于maxCID_DL的值。
在上述的由用户设备执行的方法中，优选的是，仅配置一个继续EHC指示标识drb-ContinueEHC供上行EHC和下行EHC共同使用；或者，为上行EHC配置一个继续EHC指示标识drb-ContinueEHC_UL，为下行EHC配置一个继续EHC指示标识drb-ContinueEHC_DL，所述drb-ContinueEHC或drb-ContinueEHC_UL或drb-ContinueEHC_DL的取值是以下之一：表示当发生PDCP重建时PDCP实体继续EHC的值；表示当发生PDCP重建时PDCP实体重置EHC的值。
根据本发明的另一个方面，提供了一种由用户设备执行的方法，是在用户设备UE上实现的基于以太网头压缩EHC机制的分组数据汇聚协议PDCP实体重建的方法，包括如下步骤：UE的PDCP实体从上层接收PDCP实体重建请求；对EHC的上下文采用以下方式之一进行处理：对于使用无线链路控制RLC的非确认模式UM的数据无线承载UM DRB和使用RLC的确认模式AM的数据无线承载AM DRB，如果配置了EHC或上行EHC或下行EHC，则丢弃或释放EHC或上行EHC或下行EHC的上下文和/或将CID置为0或1或初始值；对于UM DRB和AM DRB，如果配置了EHC或上行EHC或下行EHC，当没有配置drb-ContinueEHC或drb-ContinueEHC_UL或drb-ContinueEHC_DL时，则丢弃或释放EHC或上行EHC或下行EHC的上下文和/或将CID置为0或1或初始值，所述drb-ContinueEHC或drb-ContinueEHC_UL或drb-ContinueEHC_DL用于指示在PDCP实体重建时PDCP实体或PDCP实体发送端或PDCP实体接收端是否继续或重置EHC头压缩协议。
根据本发明的另一个方面，提供了一种由用户设备执行的方法，是在用户设备UE上实现的释放或挂起无线资源控制RRC连接时分组数据汇聚协议PDCP实体对以太网头压缩EHC执行的操作方法，包括如下步骤：UE的RRC实体从基站接收用于命令释放或挂起RRC连接的RRCRelease消息，该RRCRelease消息包含suspendConfig信元，该suspendConfig信元用于指示RRC非激活RRC_INACTIVE状态的配置；如果接收到的RRCRelease消息不是用于请求继续一个挂起的RRC连接的应答消息，则指示下层实体 挂起PDCP，PDCP实体接收到来自上层的挂起PDCP实体的请求后，PDCP实体的发送端或接收端对EHC执行操作。
在上述的由用户设备执行的方法中，优选的是，当上层请求PDCP实体挂起时，PDCP实体发送端执行以下操作：如果配置了上行EHC，则存储以太网头部与上下文标识CID之间的映射关系，或者存储被压缩的以太网头部与上下文标识CID之间的映射关系，和/或存储当前已分配的最大的上下文标识CID；当上层请求PDCP实体挂起时，PDCP实体接收端执行以下操作：如果配置了下行EHC，则存储以太网头部与上下文标识CID之间的映射关系，或者存储被压缩的以太网头部与上下文标识CID之间的映射关系。
根据本发明的另一个方面，提供了一种由基站执行的方法，用于使用户设备UE实现以太网头压缩EHC的指示标识的配置，包括如下步骤：向UE发送无线资源控制RRC消息，该RRC消息包含针对上行EHC和/或下行EHC的指示标识maxCID和/或指示标识drb-ContinueEHC，用于使得UE针对上行EHC和下行EHC共用和/或分开配置所述指示标识maxCID和/或所述指示标识drb-ContinueEHC，所述指示标识maxCID用于指示上下文标识最大值，所述指示标识drb-ContinueEHC用于指示当发生分组数据汇聚协议PDCP重建时PDCP实体是否继续上行和/或下行EHC。
根据本发明的另一个方面，提供了一种用户设备，包括：处理器；以及存储器，所述存储器上存储有指令，所述指令在由所述处理器运行时，使所述用户设备执行根据上文所描述的由用户设备执行的方法。
根据本发明的另一个方面，提供了一种基站，包括：处理器；以及存储器，所述存储器上存储有指令，所述指令在由所述处理器运行时，使所述基站执行根据上文所描述的由基站执行的方法。
根据本公开所涉及的用户设备及其执行的配置方法、实体重建方法和实体操作方法、以及基站及其执行的方法，由于涉及到以太网头压缩EHC的内容，因此能够提高传输效率、减少延迟，并且能够减少以太网头传输带来的开销。
附图说明
通过下文结合附图的详细描述，本公开的上述和其它特征将会变得更 加明显，其中：
图1是在用户设备UE上实现的以太网头压缩EHC的指示标识的配置方法。
图2是由基站执行的用于使得用户设备UE实现的以太网头压缩EHC的指示标识的配置方法。
图3是在用户设备UE上实现的基于EHC机制的PDCP实体重建的方法。
图4是在用户设备UE上实现的释放或挂起RRC连接时PDCP实体对EHC执行的操作的方法。
图5是本公开涉及的用户设备UE的简要结构框图。
图6是本公开涉及的基站的简要结构框图。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。
下面描述本公开涉及的部分术语，如未特别说明，所述术语与3GPP协议当前最新版本中采用的术语相同，现摘录如下。
EHC：Ethernet Header Compression，以太网头压缩。
DRB：Data Radio Bearer，数据无线承载。
RRC：Radio Resource Control，无线资源控制。
PDCP：Packet Data Convergence Protocol，分组数据汇聚协议。
SDAP：Service Data Adaptation Protocol，服务数据适应协议。
RLC：Radio Link Control，无线链路控制。RLC实体可以配置为采用以下三种模式之一进行数据传输：透传模式TM、非确认模式UM或确认模式AM。
MAC：Medium Access Control，媒体访问控制。
AM DRB：使用RLC AM的DRB(a data radio bearer which utilizes RLC AM)。
UM DRB：使用RLC UM的DRB。
SDU：Service Data Unit，服务数据单元。
PDU：Protocol Data Unit，协议数据单元。
在本公开中，将从上层接收或传送(deliver)上层的数据称为SDU，将提交(submit)下层或从下层接收的数据称为PDU。例如，PDCP实体从上层接收的数据或传送上层的数据称为PDCP SDU；PDCP实体从RLC实体接收到的数据或提交RLC实体的数据称为PDCP PDU(也就是RLC SDU)。
下面具体描述配置以太网头压缩EHC操作的实施例。
3GPP已经达成为一个DRB分开配置上行和下行EHC，对于分开配置上行和下行EHC可以有两种不同的理解，一种是EHC的所有相关参数都分别配置，另一种是上行和下行EHC功能使能或激活、支持头压缩的协议类型(profile)等参数可以单独配置，但部分参数可以共同配置(即配置一个参数供上行和/或下行使用)。下面具体描述用于指示上下文标识最大值的指示标识maxCID和用于指示当发生PDCP重建(re-establishment)时PDCP实体是否继续EHC头压缩(即指示PDCP实体继续EHC头压缩还是重置EHC头压缩)的指示标识drb-ContinueEHC的配置方法。
利用图1来描述在用户设备UE上实现的以太网头压缩EHC的指示标识的配置方法。
在步骤S1001，UE接收来自基站的RRC消息，所述消息中包含上行EHC和/或下行EHC的配置信息。具体的，RRC消息中包含针对上行EHC和/或下行EHC的用于指示上下文标识最大值的指示标识maxCID和/或用于指示当发生PDCP重建(re-establishment)时PDCP实体是否继续上行和/或下行EHC(或是否重置EHC)的指示标识drb-ContinueEHC。
在步骤S1002，UE针对上行EHC和下行EHC共用和/或分开配置所述指示标识maxCID和/或所述指示标识drb-ContinueEHC。
下面通过具体的实施例1～4来说明这两个指示标识的配置方法。
实施例1：上行EHC和下行EHC共用一个上下文标识最大值
在本实施例中，仅配置一个上下文标识CID最大值maxCID供上行和下行共同使用。maxCID的取值可以是整数。maxCID取值的含义可以是以下之一：1)表示上下文标识的最大取值为maxCID或上下文标识的最大取值为maxCID-1；2)表示上下文标识所占的比特数或字节数(例如，在PDCP头部或PDCP PDU头部或压缩包头部所占的比特数或字节数)；3)表示上下文标识最大取值是大值还是小值。例如maxCID为2表示上下文标识CID 占2个比特或2个字节，如果是2个比特，则CID最大取值为3或4，如果是2个字节，则CID的最大取值为65536或65535。又例如，预定义maxCID可能的两个取值，一个为15，另一个为65535(也可以是其他两个不同的值)，当maxCID取值为“true”或真或“1”或所述标识出现，表示上行文标识可取的最大值是大值，当maxCID取值为“false”或假或“0”或所述标识不出现，表示上行文标识可取的最大值是小值，反之亦然。
实施例2：上行EHC和下行EHC分别配置上下文标识最大值
在本实施例中，为上行EHC配置一个上下文标识最大值maxCID_UL，为下行EHC配置一个上下文标识最大值maxCID_DL。与实施例1类似，maxCID_UL(或maxCID_DL)取值的含义可以是以下之一：1)表示上下文标识的最大取值为maxCID_UL(或maxCID_DL)或上下文标识的最大取值为maxCID_UL-1(或maxCID_DL-1)；2)表示上下文标识所占的比特数或字节数(例如，在PDCP头部或PDCP PDU头部或压缩包头部所占的比特数或字节数)；3)表示上下文标识最大取值是大值还是小值。例如maxCID_UL(或maxCID_DL)为2表示上下文标识CID占2个比特或2个字节，如果是2个比特，则CID最大取值为3或4，如果是2个字节，则CID的最大取值为65536或65535。又例如，预定义maxCID_UL(或maxCID_DL)可能的两个取值，一个为15，另一个为65535(也可以是其他两个不同的值)，当maxCID_UL(或maxCID_DL)取值为“true”或真或“1”或所述标识出现，表示上行文标识可取的最大值是大值，当maxCID_UL(或maxCID_DL)取值为“false”或假或“0”或所述标识不出现，表示上行文标识可取的最大值是小值，反之亦然。
可选的，如果为上行EHC和下行EHC分开配置上下文标识的最大取值，对于上行采用反射服务质量(reflective QoS)的DRB来说，上行EHC的上下文标识的最大值maxCID_UL应与为下行EHC配置的maxCID_DL相同(或者maxCID_UL的值应小于或等于maxCID_DL的值或maxCID_UL的值应大于或等于maxCID_DL的值)。其中，采用反射服务质量(reflective QoS)的DRB就是采用反射服务质量流到DRB映射的DRB或者在接收到的RRC消息中用于配置该DRB的SDAP可配置参数的信元SDAP-Config中不包括信元mappedQoS-FlowsToAdd的DRB或者没有配置服务质量流(QoS-Flows)与DRB之间映射关系的DRB或没有配置映射到这个DRB的服 务质量流的DRB或者配置了下行SDAP头部(header)的DRB(例如接收到的RRC消息中用于配置该DRB的SDAP可配置参数的信元SDAP-Config中包含值被设置为“present”的sdap-HeaderDL信元)。其中，信元mappedQoS-FlowsToAdd用于指示一个PDU会话中额外映射到这个DRB的上行服务质量流的QFI的列表(Indicates the list of QFIs of UL QoS flows of the PDU session to be additionally mapped to this DRB)，sdap-HeaderDL信元用于指示对应DRB的下行数据中是否包含SDAP头部。反射服务质量流到DRB映射(Reflective QoS flow to DRB mapping)是一种QoS流到DRB的映射机制，在这种机制中UE监测下行的QoS流到DRB的映射规则并将其应用于上行。
在本公开实施例中，为以太网头部或头部可压缩字段分配的上下文标识CID可以用一个变量指示，例如CID_Next，其初始值可以设置为0或1。在PDCP实体发送端采用EHC进行头压缩的过程中，对上下文标识的处理可以是以下方式之一：
1)对于需要分配一个上下文标识CID的以太网报文或帧或PDCP SDU的头部或头部可压缩字段(例如，从上层接收到的以太网报文或帧或PDCP SDU的头部或头部可压缩字段没有映射到任何上下文标识)和/或如果有可用的CID值或CID_Next没有达到可使用的最大值(例如CID_Next小于maxCID，或CID_Next小于或等于maxCID)，将当前CID_Next的值关联到这个头部或头部可压缩字段，然后将CID_Next的值增加1(即CID_Next＝CID_Next+1)。在这种情况下，CID_Next总是保存下一个可分配的上下文标识。
2)对于需要分配一个上下文标识CID的以太网报文或帧或PDCP SDU的头部或头部可压缩字段(例如，从上层接收到的以太网报文或帧或PDCP SDU的头部或头部可压缩字段没有映射到任何上下文标识)和/或如果有可用的CID值或CID_Next没有达到可使用的最大值(例如CID_Next小于maxCID或maxCID-1，或CID_Next小于或等于maxCID或maxCID-1)，将当前CID_Next的值增加1，然后关联到这个头部或头部可压缩字段。在这种情况下，CID_Next总是保存最近一次分配给以太网报文或帧或PDCP SDU或数据包的头部或头部可压缩字段的上下文标识的值。
3)对于需要分配一个上下文标识CID的以太网报文或帧或PDCP SDU 的头部或头部可压缩字段(例如，从上层接收到的以太网报文或帧或PDCP SDU的头部或头部可压缩字段没有映射到任何上下文标识)，将当前尚未分配的(或可用的或尚未关联到任意以太网头部或头部可压缩字段的)CID的最小值关联到这个头部或头部可压缩字段。
在为所述以太网报文或帧或PDCP SDU或数据包的头部或头部可压缩字段关联一个上下文标识CID后，存储这个以太网报文或帧或PDCP SDU或数据包的头部或头部可压缩字段与上下文标识的映射关系。
同样的，在PDCP实体接收端采用EHC进行解压缩的过程中，执行以下操作：
如果接收到的以太网报文或帧或PDCP PDU或数据包中包含的CID的取值不在许可的范围内(例如CID大于或等于maxCID或maxCID-1)，则丢弃这个接收到的以太网报文或帧或PDCP PDU或PDCP SDU或数据包。如果接收到的以太网报文或帧或PDCP PDU或数据包中包含的CID的取值在许可的范围内(例如CID小于maxCID或maxCID+1)，如果包类型指示标识指示这个以太网报文或帧或PDCP PDU是包含完整头部的以太网报文或帧或PDCP PDU或数据包，则存储CID与以太网报文或帧或PDCP PDU或数据包头部或头部可压缩字段的映射关系；如果包类型指示标识指示这个以太网报文或帧或PDCP PDU或数据包是压缩包，则按照这个以太网报文或帧或PDCP PDU或数据包中携带的CID恢复其以太网头部或头部可压缩字段信息。
所述未压缩包是指这个以太网报文或帧或PDCP PDU或数据包包含完整头部的以太网报文或帧或PDCP PDU或数据包，所述压缩包是指这个以太网报文或帧或PDCP PDU或数据包中不包括完整头部或不包含可压缩的头部。
所述包类型指示标识用于指示对应(即包含这个指示标识)的以太网报文或帧或PDCP PDU或数据包是压缩包还是未压缩包。
此外，可以预定义或通过RRC消息配置一个值用来表示携带该CID值的PDCP PDU未压缩，所述预定义或通过RRC消息配置的CID值称为未压缩指示。换言之，当PDCP PDU(也可称为以太网报文或帧或数据包或压缩包)的CID字段设置为预定义的值(例如，0)或配置的值时表示以太网报文或帧或数据包或PDCP PDU中携带完整的以太网头部。在PDCP实 体接收端在采用EHC进行解压缩时，如果接收到的PDCP PDU中的CID字段被设置为所述预定义或配置的值，PDCP实体接收端不存储CID与以太网头部的映射关系。这个预定义或RRC配置的值用于当PDCP实体发送端认为不需要对这个以太网头部进行压缩(或没有可用的CID值或除这个值之外的所有CID值都已经建立了与以太网头部的映射关系)时将PDCP PDU的CID字段设置为这个预定义或RRC配置的值。
需要说明的是，在本公开中，上下文标识CID与以太网头部关联或建立映射关系是指将一个特定取值的CID与一个以太网头部的可压缩字段(即以太网头部的可压缩字段的一个取值)关联起来。所述以太网头部可压缩字段(也称以太网头部需要压缩的字段)可以包括以下一个或多个字段：目的地址(DESTINATION ADDRESS)、源地址(SOURCE ADDRESS)、类型/长度(TYPE/LENGTH)、Q-TAGs。其中Q-TAGs字段可包括以下字段：VLAN标识VID字段、指示以太网帧优先级的PRI字段、帧类型字段TPID、用于指示是否可丢弃的DEI字段。本公开所述可用的CID值是没有关联/映射到任何以太网头部或头部可压缩字段的上下文标识，且所述上下文标识不是未压缩指示(或称缺省的上下文标识，这适用于系统支持缺省的上下文标识的情况)。
在本公开中，将以太网报文或帧或PDCP SDU的头部或头部可压缩字段映射(或关联)到上下文标识也就是将上下文标识映射(或关联)到以太网报文或帧或PDCP SDU的头部或头部可压缩字段，也表示为以太网报文或帧或PDCP SDU的头部或头部可压缩字段分配一个上下文标识。
实施例3：上行EHC和下行EHC共用一个继续EHC指示标识drb-ContinueEHC
在本实施例中，仅配置一个继续EHC指示标识drb-ContinueEHC供上行和下行共同使用。drb-ContinueEHC的取值是以下之一：1)表示当发生PDCP重建时PDCP实体继续EHC的值；2)表示当发生PDCP重建时PDCP实体重置EHC的值。例如，当drb-ContinueEHC取值为TRUE或真或所述指示标识出现，则当发生PDCP重建(re-establishment)时PDCP实体继续EHC头压缩(即上行EHC头压缩和/或下行EHC头压缩)；当drb-ContinueEHC取值为False或假或所述指示标识不出现，在PDCP实体 重置EHC头压缩(即上行EHC头压缩和/或下行EHC头压缩)。反之亦然。
在本公开实施例中，PDCP实体继续EHC头压缩是指本公开其他实施例中描述的在配置了以太网头压缩EHC时PDCP实体重建时对EHC执行的操作。PDCP实体重置EHC头压缩(也称重置EHC或重置上行EHC或下行EHC)是本公开其他实施例中描述的PDCP实体发送端或接收端重置EHC头压缩所涉及的对EHC上下文和/或相关变量的处理。例如，PDCP实体丢弃或释放上行和/或下行上下文标识CID和以太网头部可压缩字段间的映射关系、PDCP实体发送端重新发送包含完整头部及其对应的上下文标识CID的PDCP PDU用于建立CID与以太网头部可压缩字段间的对应关系，可能还包括初始化头压缩相关变量的值，例如将其他实施例中提到的CID_Next设置为初始值。重置上行EHC是指PDCP实体接收端重置EHC，重置下行EHC是指PDCP发送端重置EHC。
实施例4：上行EHC和下行EHC分开配置继续EHC指示标识
在本实施例中，为上行EHC配置一个继续EHC指示标识drb-ContinueEHC_UL，为下行EHC配置一个继续EHC指示标识drb-ContinueEHC_DL。drb-ContinueEHC_UL或drb-ContinueEHC_DL的取值是以下之一：1)表示当发生PDCP重建时PDCP实体继续上行或下行EHC的值；2)表示当发生PDCP重建时PDCP实体重置上行或下行EHC的值。例如，当drb-ContinueEHC_UL(或drb-ContinueEHC_DL)取值为TRUE或真或所述指示标识出现，则当发生PDCP重建(re-establishment)时PDCP实体继续EHC头压缩或上行EHC头压缩(或下行EHC头压缩)；当drb-ContinueEHC_UL(或drb-ContinueEHC_DL)取值为False或假或所述指示标识不出现，在PDCP实体重置EHC头压缩或上行EHC头压缩(或下行EHC头压缩)。反之亦然。需要说明的是，本实施例也支持仅配置上行EHC的继续EHC指示标识drb-ContinueEHC_UL或仅配置下行EHC的继续EHC指示标识drb-ContinueEHC_DL的情况。
此外，对于缺省的DRB，在现有的协议中，SDAP实体将所有没有定义应映射到的DRB的QoS流映射到缺省DRB。考虑映射到缺省DRB的QoS流以太网头部相差较大，可以规定不为缺省的DRB配置EHC(包括上行EHC和/或下行EHC)。所述缺省DRB是指用于设置该DRB的SDAP可 配置参数的信元SDAP-Config中不包含信元defaultDRB或者defaultDRB的值被设置为“false”。其中，信元defaultDRB用于指示对应的DRB是否是这个PDU会话(PDU session)的缺省DRB。
下面具体利用图2来描述由基站执行的用于使得用户设备UE实现的以太网头压缩EHC的指示标识的配置方法。
在步骤S2001，向UE发送无线资源控制RRC消息，与上述实施例同样地，该RRC消息包含针对上行EHC和/或下行EHC的指示标识maxCID和/或指示标识drb-ContinueEHC，用于使得UE针对上行EHC和下行EHC共用和/或分开配置所述指示标识maxCID和/或所述指示标识drb-ContinueEHC。其中，该指示标识maxCID用于指示上下文标识最大值，该指示标识drb-ContinueEHC用于指示当发生分组数据汇聚协议PDCP重建时PDCP实体是否继续上行和/或下行EHC。关于指示标识maxCID和指示标识drb-ContinueEHC这两个指示标识的配置方法，也与上述实施例相同。
另外，在其他实施例中，用户设备执行的方法所对应的基站执行的方法也与本实施例类似。
下面具体描述在配置了以太网头压缩EHC时PDCP实体重建操作的实施例。
EHC与PDCP实体之间的关系可以是以下之一：
(1)如果配置了EHC(即上行EHC和/或下行EHC)，在进行DRB重配置时，总是(始终)重建PDCP实体。具体地，如果配置了EHC(或上行EHC或下行EHC)，在进行DRB重配置时，总是重建PDCP实体。换言之，如果一个DRB配置了EHC(或上行EHC或下行EHC)，那么在重配置这个DRB时，现有的TS38.331协议中定义的用于指示PDCP实体应该重建的指示标识reestablishPDCP必须携带和/或设置为“true”(即网络或基站发送给UE的包含重配置这个DRB的RRC消息中，将这个DRB对应的reestablishPDCP设置为“true”)。
(2)如果配置了EHC(即上行EHC和/或下行EHC)，在进行DRB重配置时，可以(能够)重建PDCP实体。具体地，如果配置了EHC(或上行EHC或下行EHC)，在进行DRB重配置时，网络通过配置现有的TS38.331 协议中定义的用于指示PDCP实体应该重建的指示标识reestablishPDCP来指示UE是否为对应的DRB重建PDCP实体。
利用图3来描述在用户设备UE上实现的基于EHC机制的PDCP实体重建的方法。
在步骤S3001，UE的PDCP实体从上层接收PDCP实体重建请求。
在步骤S3002，PDCP实体(即PDCP实体发送端或接收端)对EHC的上下文可以采用以下方式之一进行处理：
1)对于UM DRB和AM DRB，如果配置了rohc或uplinkOnlyROHC，当没有配置drb-ContinueROHC时，重置(reset)上行头压缩协议并从U-mode中的IR状态开始。对于UM DRB和AM DRB，如果配置了EHC(或上行EHC或下行EHC)，则重置EHC。具体地，丢弃或释放EHC(或上行EHC或下行EHC)上下文(和/或重置上行EHC并从完整头部开始，或者重置上行EHC)和/或将CID置为0或1或初始值。(这适用于不支持继续EHC头压缩的情况)
2)对于UM DRB和AM DRB，如果配置了rohc或uplinkOnlyROHC，当没有配置drb-ContinueROHC时，重置上行头压缩协议并从U-mode中的IR状态开始。对于UM DRB和AM DRB，如果配置了EHC(即上行EHC或下行EHC)，当没有配置drb-ContinueEHC时，则重置EHC。具体地，丢弃或释放EHC上下文(和/或重置上行EHC并从完整头部开始或从完整的头部和完整头部指示标识开始)和/或将CID置为0或1或初始值。(这适用于仅配置一个drb-ContinueEHC供上行和下行共同使用的情况)
3)对于UM DRB和AM DRB，如果配置了rohc或uplinkOnlyROHC，当没有配置drb-ContinueROHC时，重置上行头压缩协议并从U-mode中的IR状态开始。对于UM DRB和AM DRB，如果配置了上行EHC，当没有配置drb-ContinueEHC_UL时，则重置EHC。具体地，丢弃或释放上行EHC上下文(和/或重置上行EHC并从完整头部开始或从完整的头部和完整头部指示标识开始)和/或将CID置为0或1或初始值。对于UM DRB和AM DRB，如果配置了下行EHC，当没有配置drb-ContinueEHC_DL时，则重置EHC。具体地，丢弃或释放下行EHC上下文(和/或重置下行EHC并从完整头部开始或从完整的头部和完整头部指示标识开始)。
其中，信元rohc用于配置采用ROHC(包括上行和下行)(Robust Header  Compression，健壮性头压缩)需要配置的相关参数，信元uplinkOnlyROHC用于配置上行采用ROHC需要配置的相关参数，信元drb-ContinueROHC用于指示在PDCP实体重建时PDCP实体是否继续或重置ROHC头压缩协议。关于这些信元的具体描述参见TS38.331。信元drb-ContinueEHC用于指示在PDCP实体重建时PDCP实体是否继续或重置EHC头压缩协议，信元drb-ContinueEHC_UL用于指示在PDCP实体重建时PDCP实体发送端是否继续或重置EHC头压缩协议，信元drb-ContinueEHC_DL用于指示在PDCP实体重建时PDCP实体接收端是否继续或重置EHC头压缩协议。
在本公开中，EHC是EHC头压缩协议或以太网头压缩协议。没有配置drb-ContinueROHC(或drb-ContinueEHC或drb-ContinueEHC_UL或drb-ContinueEHC_UL)或包括接收到的RRC消息中部包含drb-ContinueROHC(或drb-ContinueEHC或drb-ContinueEHC_UL或drb-ContinueEHC_UL)信元，或者drb-ContinueROHC(或drb-ContinueEHC或drb-ContinueEHC_UL或drb-ContinueEHC_UL)信元的取值不是继续ROCH(或EHC)对应的取值，例如drb-ContinueROHC(或drb-ContinueEHC或drb-ContinueEHC_UL或drb-ContinueEHC_UL)信元取值为false或0。
下面描述RRC释放RRCRelease消息中包含suspendConfig时针对EHC执行的操作的实施例。
suspendConfig信元用于指示RRC_INACTIVE状态的配置。
RRCRelease消息用于命令(command)释放RRC连接或挂起RRC连接。
RRCResumeRequest消息是一个48比特的消息，用于请求继续一个挂起的RRC连接或执行RNA更新。
RRCResumeRequest1消息是一个64比特的消息，用于请求继续一个挂起的RRC连接或执行RAN通知区域(RAN-based Notification Area，RNA)更新。
以上信元或消息的具体描述参见TS38.331。
利用图4来描述在用户设备UE上实现的释放或挂起RRC连接时PDCP实体对EHC执行的操作的方法。
在步骤S4001，UE的RRC实体从基站接收用于命令释放或挂起RRC 连接的RRCRelease消息；
在步骤S4002，如果接收到的RRCRelease消息不是用于请求继续一个挂起的RRC连接的消息，则指示下层实体(即PDCP实体)挂起PDCP。PDCP实体接收到来自上层(即RRC)的挂起PDCP实体的请求后，PDCP实体的发送端或接收端对EHC(上行EHC或下行EHC)执行操作。
例如，如果UE从基站接收到的所述包含suspendConfig的RRCRelease消息不是RRCResumeRequest消息或RRCResumeRequest1消息的应答消息，则存储EHC上下文，或者如果配置了EHC(或上行EHC或下行EHC)，则存储EHC(或上行EHC或下行EHC)上下文。
当上层(例如RRC)请求PDCP实体挂起(suspend)时，PDCP实体发送端执行以下操作：如果配置了上行EHC，存储EHC(即上行EHC)上下文。具体的，存储以太网头部与上下文标识CID之间的映射关系，或者存储被压缩的以太网头部与上下文标识CID之间的映射关系，和/或当前已分配的最大的上下文标识CID(如果分配的上下文标识CID也用一个变量指示，例如CID_Next，那么保存当前CID_Next的取值)。
当上层(例如RRC)请求PDCP实体挂起(suspend)时，PDCP实体接收端执行以下操作：如果配置了下行EHC，存储EHC(即下行EHC)上下文。具体的，存储以太网头部与上下文标识CID之间的映射关系，或者存储被压缩的以太网头部与上下文标识CID之间的映射关系。
在本公开实施例中，配置了上行EHC是指对应的DRB的配置消息(即配置或重配置DRB的RRC消息)中包含用于指示上行以太网头压缩的ehc_UL信元，ehc_UL信元中包含PDCP实体执行上行EHC时需要配置的相关参数，所述参数可以包括：maxCID_UL、drb-ContinueEHC_UL。配置了下行EHC是指对应的DRB的配置消息(即配置或重配置DRB的RRC消息)中包含用于指示下行以太网头压缩的ehc_DL信元，ehc_DL信元中包含PDCP实体执行下行EHC时需要配置的相关参数，所述参数可以包括：maxCID_DL、drb-ContinueEHC_DL。配置了EHC是指配置了上行EHC和/或下行EHC。
下面描述PDCP实体发送端对EHC上下文管理的实施例。
UE接收到来自基站(例如gNB)的RRC消息，其中包含信元ehc_Timer，用来设置定时器ehc_Timer的值。优选的，所述RRC消息包含用于配置上行EHC相关参数的信元ehc_UL，所述信元ehc_Timer包含在ehc_UL中。
当PDCP实体发送端发送(或向下层提交)一个包含以太网压缩包的PDCP PDU时，启动或重启对应的ehc_Timer，该ehc_Timer是与这个PDCP PDU中携带的CID关联，即不同取值的CID各自关联一个ehc_Timer。ehc_Timer与CID关联就是ehc_Timer与特定的以太网头部可压缩字段关联。所述以太网压缩包可以是用于建立CID与以太网头部可压缩字段的包含完整以太网头部的PDCP PDU或者是不携带完整以太网头部的PDCP PDU。换言之，所述包含以太网压缩包的PDCP PDU中包含的CID字段的取值不是未压缩指示。
当ehc_Timer到期，丢弃或释放其对应CID与以太网头部可压缩字段(即以太网头部可压缩字段的一个取值)间的映射关系，使得这个CID可以被重新映射到新的以太网头部可压缩字段(或以太网头部可压缩字段的其他取值)。
图5是本公开涉及的用户设备UE的简要结构框图。如图5所示，该用户设备UE500包括处理器501和存储器502。处理器501例如可以包括微处理器、微控制器、嵌入式处理器等。存储器502例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器502上存储有程序指令。该指令在由处理器501运行时，可以执行本公开详细描述的由用户设备执行的上述方法。
图6是本公开涉及的基站的简要结构框图。如图6所示，该基站600包括处理器601和存储器602。处理器601例如可以包括微处理器、微控制器、嵌入式处理器等。存储器602例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器602上存储有程序指令。该指令在由处理器601运行时，可以执行本公开详细描述的由基站执行的上述方法。
运行在根据本发明的设备上的计算机可执行指令或者程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (4)

  1. 一种由用户设备执行的方法，是在用户设备UE上实现的以太网头压缩EHC的指示标识的配置方法，包括如下步骤：
    UE接收来自基站的无线资源控制RRC消息，该RRC消息包含针对上行EHC的指示标识maxCID_UL和/或指示标识drb-ContinueEHC_UL和/或针对下行EHC的指示标识drb-ContinueEHC_DL，该指示标识maxCID_UL用于指示上行上下文标识的最大取值，该指示标识drb-ContinueEHC_UL用于指示当发生分组数据汇聚协议PDCP重建时PDCP实体是否继续上行EHC；该指示标识drb-ContinueEHC_DL用于指示当发生分组数据汇聚协议PDCP重建时PDCP实体是否继续下行EHC。
  2. 一种由基站执行的方法，用于使用户设备UE实现以太网头压缩EHC的指示标识的配置，包括如下步骤：
    向UE发送无线资源控制RRC消息，该RRC消息包含针对上行EHC的指示标识maxCID_UL和/或指示标识drb-ContinueEHC_UL和/或针对下行EHC的指示标识drb-ContinueEHC_DL，该指示标识maxCID_UL用于指示上行上下文标识的最大取值，该指示标识drb-ContinueEHC_UL用于指示当发生分组数据汇聚协议PDCP重建时PDCP实体是否继续上行EHC；该指示标识drb-ContinueEHC_DL用于指示当发生分组数据汇聚协议PDCP重建时PDCP实体是否继续下行EHC。
  3. 一种用户设备，包括：
    处理器；以及
    存储器，所述存储器上存储有指令，
    所述指令在由所述处理器运行时，使所述用户设备执行根据权利要求1所述的方法。
  4. 一种基站，包括：
    处理器；以及
    存储器，所述存储器上存储有指令，
    所述指令在由所述处理器运行时，使所述基站执行根据权利要求2所述的方法。
PCT/CN2020/101837 2019-07-30 2020-07-14 用户设备及其执行的方法和基站及其执行的方法 WO2021017812A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910699371.6A CN112312587A (zh) 2019-07-30 2019-07-30 用户设备及其执行的方法和基站及其执行的方法
CN201910699371.6 2019-07-30

Publications (1)

Publication Number Publication Date
WO2021017812A1 true WO2021017812A1 (zh) 2021-02-04

Family

ID=74230100

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/101837 WO2021017812A1 (zh) 2019-07-30 2020-07-14 用户设备及其执行的方法和基站及其执行的方法

Country Status (2)

Country Link
CN (1) CN112312587A (zh)
WO (1) WO2021017812A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024066704A1 (zh) * 2022-09-30 2024-04-04 大唐移动通信设备有限公司 数据传输方法、终端及网络侧实体
CN118055446A (zh) * 2024-04-15 2024-05-17 上海移芯通信科技股份有限公司 一种健壮性头部压缩解压方法、系统及通讯终端
EP4387206A4 (en) * 2021-08-09 2024-07-10 Guangdong Oppo Mobile Telecommunications Corp Ltd DATA TRANSMISSION METHOD AND DEVICE

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115484312B (zh) * 2021-05-31 2024-05-17 展讯通信（上海）有限公司 以太网包头压缩方法及装置
CN115696298A (zh) * 2021-07-28 2023-02-03 华为技术有限公司 信息指示方法和装置
CN115968561A (zh) * 2021-08-11 2023-04-14 华为技术有限公司 通信方法及通信装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102196497A (zh) * 2002-08-14 2011-09-21 Lg电子株式会社 双向分组数据传输系统和方法
CN105723682A (zh) * 2014-06-26 2016-06-29 Lg电子株式会社 发送/接收广播信号的方法和装置
WO2017035752A1 (zh) * 2015-08-31 2017-03-09 华为技术有限公司 一种数据流报头压缩传输方法、系统及控制器、节点
CN107925679A (zh) * 2015-08-31 2018-04-17 三星电子株式会社 用于在多媒体系统中发送和接收信号的装置和方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102196497A (zh) * 2002-08-14 2011-09-21 Lg电子株式会社 双向分组数据传输系统和方法
CN105723682A (zh) * 2014-06-26 2016-06-29 Lg电子株式会社 发送/接收广播信号的方法和装置
WO2017035752A1 (zh) * 2015-08-31 2017-03-09 华为技术有限公司 一种数据流报头压缩传输方法、系统及控制器、节点
CN107925679A (zh) * 2015-08-31 2018-04-17 三星电子株式会社 用于在多媒体系统中发送和接收信号的装置和方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "TP for NR BL CR for TS 38.463): on corrections of ROHC parameters over E1", 3GPP DRAFT; R3-185997 (TP FOR NR BL CR FOR TS 38.463) ON CORRECTIONS OF ROHC PARAMETERS OVER E1, vol. RAN WG3, 29 September 2018 (2018-09-29), Chengdu, China, pages 1 - 4, XP051529263 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4387206A4 (en) * 2021-08-09 2024-07-10 Guangdong Oppo Mobile Telecommunications Corp Ltd DATA TRANSMISSION METHOD AND DEVICE
WO2024066704A1 (zh) * 2022-09-30 2024-04-04 大唐移动通信设备有限公司 数据传输方法、终端及网络侧实体
CN118055446A (zh) * 2024-04-15 2024-05-17 上海移芯通信科技股份有限公司 一种健壮性头部压缩解压方法、系统及通讯终端

Also Published As

Publication number Publication date
CN112312587A (zh) 2021-02-02

Similar Documents

Publication Publication Date Title
WO2021017812A1 (zh) 用户设备及其执行的方法和基站及其执行的方法
US12010592B2 (en) Sidelink communications method and apparatus
WO2019131345A1 (ja) 端末装置、方法、および、集積回路
WO2019098267A1 (ja) 端末装置および方法
WO2019098148A1 (ja) 端末装置、基地局装置、および方法
WO2021185202A1 (zh) 用户设备及其方法、基站及其方法
TW201921977A (zh) 服務資料單元處理方法、丟棄方法、相應的使用者設備和電腦可讀媒體
WO2021027685A1 (zh) Pdcp实体发送端/接收端的执行方法、pdcp实体及通信设备
JP2023176001A (ja) 端末装置、通信方法、および基地局装置
US12022549B2 (en) Terminal device, base station device, and method
WO2020091047A1 (ja) 端末装置、基地局装置、および方法
WO2021223623A1 (zh) 针对信令无线承载pdcp重复的配置方法及rrc实体
WO2019031217A1 (ja) 端末装置、基地局装置、及び、これらの装置により実行される方法
WO2024120476A1 (zh) 由用户设备执行的方法以及用户设备
WO2023036287A1 (zh) 用户设备执行的方法、基站的传输方法及用户设备
EP3103279B1 (en) Mtc device, serving node, and various methods for implementing an uplink stack reduction feature
WO2023036173A1 (zh) 状态报告发送方法、无线承载重传执行方法及用户设备
WO2023280205A1 (zh) 由用户设备执行的方法及用户设备
WO2023001240A1 (zh) 由用户设备ue执行的方法及用户设备
WO2020091048A1 (ja) 端末装置、および、方法
WO2024120475A1 (zh) 恢复rrc连接的方法以及用户设备
US20150230121A1 (en) Mtc device, serving node, and various methods for implementing a downlink stack reduction feature
JP2024060299A (ja) ネットワークシステムおよび基地局装置
WO2019213905A1 (zh) 一种绑定数据流的方法及装置、计算机存储介质
WO2019098266A1 (ja) 端末装置および方法

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: 20846939

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20846939

Country of ref document: EP

Kind code of ref document: A1