WO2026026909A1 - 同步方法以及用户设备 - Google Patents

同步方法以及用户设备

Info

Publication number
WO2026026909A1
WO2026026909A1 PCT/CN2025/111788 CN2025111788W WO2026026909A1 WO 2026026909 A1 WO2026026909 A1 WO 2026026909A1 CN 2025111788 W CN2025111788 W CN 2025111788W WO 2026026909 A1 WO2026026909 A1 WO 2026026909A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu
pdcp
synchronization
sdu
cluster
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.)
Pending
Application number
PCT/CN2025/111788
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.)
Sharp Corp
Original Assignee
Sharp Corp
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 Sharp Corp filed Critical Sharp Corp
Publication of WO2026026909A1 publication Critical patent/WO2026026909A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/0055—Synchronisation arrangements determining timing error of reception due to propagation delay
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/08—Trunked mobile radio systems

Definitions

  • This invention relates to the field of wireless communication technology, and more specifically, to synchronization methods and user equipment.
  • This invention discusses related issues involving multi-mode synchronization and/or coordination.
  • the present invention provides a synchronization method and a user equipment.
  • a synchronization method comprising: associating a synchronization timer with each synchronization PDU cluster or PDU set, the value of the timer being configured by a base station for a UE via an RRC message or provided by an upper layer; the UE performing multi-mode data synchronization by maintaining the synchronization timer; when the value of the synchronization timer is configured by the base station, the base station configures the value of the timer for each group of data streams that need to be synchronized; when the value of the synchronization timer is provided by an upper layer, the base station configures an indication identifier for the UE, the indication identifier being used to indicate whether the UE is allowed to start or run the synchronization timer or whether inter-PDU set synchronization or multi-mode data synchronization is supported.
  • the synchronization timer runs at the SDAP layer, PDCP layer, or RLC layer.
  • the transmitting PDCP entity when submitting a PDCP PDU to the lower layer, or when receiving an indication of successful submission of a PDCP PDU or PDCP SDU from the lower layer, or when receiving an indication that a PDCP PDU or PDCP SDU has been transmitted from the lower layer, or when receiving an indication of successful transmission of a PDCP PDU or PDCP SDU from the lower layer, the transmitting PDCP entity performs the following operations: if the UE or the PDCP entity is configured for multi-mode data synchronization and/or the PDCP PDU belongs to a synchronization PDU cluster and/or the PDCP PDU belongs to a PDU set, then at least one of operations 1-1 to 1-3 is performed.
  • Operation 1-1 If the synchronization timer associated with the synchronization PDU cluster to which the PDCP PDU or PDCP SDU belongs is not running, or if the synchronization timer associated with the PDU set to which the PDCP PDU or PDCP SDU belongs is not running, or if the synchronization timer associated with the PDU set to which the PDCP PDU or PDCP SDU belongs is not running, then start the synchronization timer;
  • Operation 1-2 If the PDCP PDU or PDCP SDU is the first PDCP PDU or PDCP SDU in its PDU set, and/or if a synchronization timer is configured, and/or the synchronization timer associated with the synchronization PDU cluster to which the PDCP PDU or PDCP SDU belongs is not running or the synchronization timer associated with the PDU set to which the PDCP PDU or PDCP SDU belongs is not running, and/or the synchronization timer associated with the PDU set to which the PDCP PDU or PDCP SDU belongs is not running, then: (1) if the synchronization timer of the PDU set to which the PDCP PDU or PDCP SDU belongs or the synchronization PDU cluster is running, then stop the synchronization timer, and/or (2) start the synchronization timer, and/or (3) indicate the submission information to the upper layer so that the upper layer starts the timer associated with the PDU set or the synchronization PDU cluster upon receiving
  • Operations 1-3 If the PDCP PDU or PDCP SDU is the last PDCP PDU or PDCP SDU submitted to the lower layer in its PDU set or synchronous PDU cluster, or if the PDCP PDU or PDCP SDU is the first PDCP PDU or PDCP SDU submitted to the lower layer in its PDU set that was the last to submit a PDCP PDU to the lower layer in its synchronous PDU cluster, or if the PDCP PDU or PDCP SDU is the last PDCP PDU or PDCP SDU in its PDU set or synchronous PDU cluster that was confirmed to have been successfully transmitted by the lower layer, then stop the synchronization timer associated with the PDU set or synchronous PDU cluster to which the PDCP PDU or PDCP SDU belongs, or indicate the submission to the upper layer.
  • the PDCP entity when the PDCP entity receives an indication or transmission indication of successful submission of the last PDCP PDU or PDCP SDU from the lower-level PDU set or the synchronization PDU cluster, it stops the synchronization timer associated with the PDU set or the synchronization PDU cluster.
  • the indication or transmission indication of successful submission of the PDCP PDU or PDCP SDU can come from the MAC or RLC layer.
  • the transmitting PDCP entity performs at least one of the following operations:
  • Operation 2-1 If pdu-SetDiscard is configured, then: (1a) Discard all PDCP SDUs belonging to the PDU set to which the PDCP SDU belongs, as well as the corresponding PDCP data PDUs, and/or (2a) if interPdu-setDiscard is configured or the synchronization timer expires, discard all PDCP SDUs belonging to the synchronous PDU cluster to which the PDCP SDU belongs, as well as the corresponding PDCP data PDUs, and/or (3a) if interPdu-setDiscard is configured, or if the PDCP SDU belongs to a synchronous PDU cluster, or if the synchronization timer expires, discard all PDCP SDUs belonging to the synchronous PDU cluster to which the PDCP SDU belongs.
  • Operation 2-2 If interPdu-setDiscard is configured and/or a synchronization timer is configured and/or the PDCP SDU belongs to a PDU set or a synchronized PDU cluster and/or there exists a PDU set that is synchronized with the PDU set to which the PDCP SDU belongs, then: (1b) Discard all PDCP SDUs belonging to the PDU set to which the PDCP SDU belongs, as well as the corresponding PDCP data PDUs, and/or (2b) Discard all PDCP SDUs belonging to the synchronized PDU cluster to which the PDCP SDU belongs, as well as the corresponding PDCP data PDUs, and/or (3b) Discard PDUs belonging to the PDU set to which the PDCP SDU belongs that are synchronized with the PDU set to which the PDCP SDU belongs.
  • the SDAP PDU or SDU is the last SDAP PDU or SDU in its PDU set, or if the SDAP PDU or SDU is the last SDAP PDU or SDU in its PDU set that has been indicated as submitted or successfully transmitted, or if the SDAP PDU or SDU is the first or last SDAP PDU or SDU in the last PDU set in its synchronous PDU cluster that has been indicated as submitted or successfully transmitted, then stop the synchronization timer associated with the PDU set synchronized by the PDU set to which the SDAP PDU or SDU belongs, or stop the synchronization timer associated with the PDU set to which the SDAP PDU or SDU belongs, or stop the synchronization timer associated with the synchronous PDU cluster to which the SDAP PDU or SDU belongs.
  • a user equipment comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, perform the above-described synchronization method.
  • the synchronization method and corresponding user equipment provided by the present invention can effectively solve the problem of synchronization between PDUs or PDU sets.
  • Figure 1 is a schematic diagram of the protocol stack involved in the air interface transmission of data according to the present invention.
  • Figure 2 is a schematic diagram illustrating a mapping relationship between data flow and RLC in multimodal services.
  • Figure 3 is a schematic diagram illustrating another mapping relationship between data flow and bearer in multimodal services.
  • FIG. 4 is a block diagram illustrating the user equipment (UE) involved in this invention.
  • UE User Equipment.
  • RRC Radio Resource Control
  • RRC_CONNECTED RRC connection state.
  • RRC_INACTIVE RRC inactive state.
  • RRC_IDLE RRC idle state.
  • RAN Radio Access Network
  • New RAT New Wireless Access Technology.
  • AS Access Stratum, the access layer.
  • NAS Non-Access Stratum.
  • DRB Radio Bearer.
  • DRB is the data radio bearer.
  • Each DRB can be associated with an SDAP entity, and has a corresponding PDCP entity and one or more RLC entities.
  • PDCP Packet Data Convergence Protocol
  • the HARQ entity or process is located at the MAC layer or MAC entity.
  • a PDU set consists of one or more PDUs that carry the payload of a single information unit (e.g., a frame or video slice from an XR service) generated at the application level.
  • the application layer requires all PDUs in the set to use the corresponding information unit. In other implementations, the application layer can still recover some or all of the information unit even if some PDUs are lost.
  • One PDU in the set corresponds to one PDCP SDU.
  • a multi-modal service is a communication service consisting of multiple interconnected data streams that require application coordination. These data streams can transmit different types of data (e.g., audio, video, location, haptic data) and may originate from different sources (e.g., a single UE, a single device connected to a single UE, or multiple devices, or multiple UEs). In the case of a single UE, these data streams are closely related and require strong application coordination to correctly execute multi-modal applications; therefore, all these data streams are transmitted within a single PDU session.
  • data streams e.g., audio, video, location, haptic data
  • sources e.g., a single UE, a single device connected to a single UE, or multiple devices, or multiple UEs.
  • a Multi-modal Service ID (MMSID) is used to indicate a data flow associated with a multi-modal service. Data flows with the same MMSID belong to the same multi-modal service.
  • Synchronization threshold A multi-modal synchronization threshold can be defined as the maximum tolerable temporal separation of the onset of two stimuli, one of which is presented to one sense and the other to another sense, such that the accompanying sensory objects are perceived as being synchronous. Synchronization relationships may exist between single-modal data within the same multi-modal dataset.
  • a PDU set from one single-modal dataset may be synchronized with PDU sets from one or more other single-modal datasets. For example, when data transmission of one PDU set begins (or ends), data transmission of one or more PDU sets synchronized with it must begin (or end) within the time limit limited by the synchronization threshold.
  • a collection of PDU sets consisting of two or more PDU sets that have a synchronization relationship is referred to as a synchronous PDU cluster.
  • a synchronous PDU cluster also includes a synchronous PDU cluster that contains only one PDU set, and where the PDUs in that PDU set have dependencies or synchronization relationships.
  • the synchronous PDU cluster described in the embodiments of this disclosure may refer to a case that contains one or more PDU sets.
  • Figure 1 illustrates an example of the protocol stack involved in air interface data transmission according to this disclosure.
  • the protocol stack from top to bottom, consists of SDAP, PDCP, RLC, MAC, and the physical layer.
  • the layer below the SDAP layer can be PDCP and/or RLC and/or MAC and/or the physical layer; the layer below the PDCP layer can be RLC and/or MAC and/or the physical layer; and the layer below the RLC layer can be MAC and/or the physical layer.
  • the layer above the MAC layer can be SDAP and/or PDCP and/or RLC; the layer above the RLC layer can be SDAP and/or PDCP; and the layer above the PDCP layer can be SDAP.
  • each layer is implemented by corresponding entities.
  • the functions of the MAC layer are implemented by the MAC entity, the RLC layer by the RLC entity, the PDCP layer by the PDCP entity, and the SDAP layer by the SDAP entity.
  • layers and entities are used interchangeably.
  • SDU and PDU are used interchangeably. Those skilled in the art can easily deduce from the context that the SDU is the SDU corresponding to the PDU, and similarly, the PDU is the PDU corresponding to the SDU. Therefore, unless otherwise specified, embodiments obtained by replacing PDU with SDU or SDU with PDU are also within the scope of this disclosure.
  • the RLC entity processes the data and then submits it to the MAC layer.
  • the MAC layer processes the data and then submits it to the physical layer.
  • the physical layer processes the data and then sends it to the base station over the air interface.
  • SDU the data received from the upper layer
  • PDU the data submitted to the lower layer
  • PDCP SDU data received or transmitted from the SDAP layer to the SDAP layer by the PDCP layer
  • PDCP PDU data received or submitted from the RLC layer to the RLC layer by the PDCP layer
  • PDCP PDU data received or submitted from the RLC layer to the RLC layer by the PDCP layer
  • a TM RLC entity can also be configured to perform receiving and transmitting operations as a receiving TM RLC entity and a transmitting TM RLC entity, respectively.
  • An AM RLC entity includes a transmitting side of an AM RLC entity and a receiving side of an AM RLC entity, respectively used to receive data from the upper layer and transmit it to the peer AM RLC entity through the lower layer, and to deliver data to the upper layer and receive data from the peer AM RLC entity through the lower layer.
  • RLC entities in this disclosure those skilled in the art can correspondingly replace them with transmitting or receiving UM RLC entities, transmitting or receiving TM RLC entities, or transmitting or receiving sides of AM RLC entities.
  • a synchronization timer is associated with each synchronization PDU cluster or PDU set.
  • the value of the timer can be configured by the base station for the UE via RRC messages or provided by an upper layer (e.g., the NAS layer).
  • the UE achieves multi-mode data synchronization by maintaining the synchronization timer.
  • the base station can configure the timer value separately for each group of data streams that need to be synchronized, for example, configuring the timer value for each DRB or each PDCP entity.
  • Figure 2 illustrates a mapping relationship between data flows and RLCs in a multi-mode service.
  • the SDAP entity maps all QoS flows associated with a multi-mode service to a data bearer (DRB), and the PDCP then submits the PDCP SDUs (or corresponding PDCP PDUs) of different QoS flows to the RLC entity corresponding to the QoS flow.
  • DRB data bearer
  • the PDCP SDU of QoS flow 1 is mapped to RLC1
  • the PDCP SDU of QoS flow 2 is mapped to RLC2.
  • the synchronization timer can run at the SDAP layer, PDCP layer, or RLC layer. For example, if the mapping relationship in Figure 2 is used, the synchronization timer can run at the PDCP layer; if the mapping relationship in Figure 3 is used, the synchronization timer can run at the SDAP layer.
  • the following describes the operations performed by the PDCP entity during transmission.
  • the transmitting PDCP entity upon submitting a PDCP PDU to a lower layer, or upon receiving an indication of successful submission (i.e., submission or submission for transmission) of a PDCP PDU or PDCP SDU from a lower layer (e.g., RLC or MAC), or upon receiving an indication that a PDCP PDU or PDCP SDU has been transmitted from a lower layer (e.g., RLC or MAC), or upon receiving an indication that a PDCP PDU or PDCP SDU has been successfully transmitted from a lower layer (e.g., RLC or MAC), the transmitting PDCP entity performs the following operations:
  • the UE or the PDCP entity is configured for multi-mode data synchronization and/or the PDCP PDU belongs to a synchronized PDU cluster (in other words, the PDCP PDU belongs to a set of PDUs within a synchronized PDU cluster) and/or the PDCP PDU belongs to a set of PDUs (this set of conditions is optional; for example, if an indication of successful submission of a PDCP PDU or PDCP SDU is received from a lower layer, then at least one of the following operations is performed directly):
  • Operation 1-1 If the synchronization timer associated with the synchronization PDU cluster to which the PDCP PDU or PDCP SDU belongs is not running, or if the synchronization timer associated with the PDU set to which the PDCP PDU or PDCP SDU belongs is not running, or if the synchronization timer associated with the PDU set to which the PDCP PDU or PDCP SDU belongs is not running, then start the synchronization timer.
  • Operation 1-2 If the PDCP PDU or PDCP SDU is the first PDCP PDU or PDCP SDU in its PDU set or synchronous PDU cluster, and/or if a synchronization timer is configured, and/or the synchronization timer associated with the synchronous PDU cluster to which the PDCP PDU or PDCP SDU belongs is not running or the synchronization timer associated with a PDU set that has a synchronization relationship with the PDU set to which the PDCP PDU or PDCP SDU belongs is not running, and/or the PDU to which the PDCP PDU or PDCP SDU belongs...
  • the synchronization timer associated with the set is not running, then: (1) if the synchronization timer of the PDU set or synchronization PDU cluster to which the PDCP PDU or PDCP SDU belongs is running, then stop the synchronization timer, and/or (2) start the synchronization timer, and/or (3) indicate the submission information to the upper layer (i.e., SDAP), for example, indicating to the upper layer the relevant information of the first PDCP PDU or PDCP SDU that has been submitted to the PDU set or synchronization PDU cluster, so that the upper layer starts the timer associated with the PDU set or synchronization PDU cluster when it receives the indication.
  • the upper layer i.e., SDAP
  • the synchronization timer associated with the PDU set to which the PDCP PDU or PDCP SDU belongs is not running
  • Operations 1-3 If the PDCP PDU or PDCP SDU is the last PDCP PDU or PDCP SDU submitted to the lower layer in its PDU set or synchronous PDU cluster (in other words, all PDCP PDUs or PDCP SDUs in the PDU set or synchronous PDU cluster have been submitted to the lower layer or transmitted), or if the PDCP PDU or PDCP SDU is the first (or last) PDCP PDU or PDCP SDU submitted to the lower layer (or confirmed by the lower layer to have been sent or successfully transmitted) in the PDU set of its synchronous PDU cluster that was the last to submit a PDCP PDU to the lower layer (in other words, all other PDU sets in the synchronous PDU cluster have PDCP PDUs or PDCP SDUs submitted to the lower layer or transmitted).
  • the synchronization timer associated with the PDU set or synchronous PDU cluster to which the PDCP PDU or PDCP SDU belongs is stopped, or the submission is indicated to the upper layer (e.g., SDAP), for example, indicating to the upper layer that the PDCP PDU or PDCP SDU is the last PDCP PDU or PDCP SDU in its PDU set or synchronous PDU cluster to be submitted to the lower layer.
  • a PDCP entity receives an indication of successful submission or transmission of the last PDCP PDU or PDCP SDU in a PDU set or synchronous PDU cluster from a lower layer (RLC or MAC) (in other words, all PDCP PDUs or PDCP SDUs in the PDU set or synchronous PDU cluster have been indicated by the lower layer to have been submitted to the lower layer or have been confirmed by the lower layer to have been successfully transmitted), the synchronization timer associated with the PDU set or the synchronous PDU cluster can be stopped.
  • RLC or MAC lower layer
  • the indication or transmission indication of successful submission of the PDCP PDU or PDCP SDU can come from the MAC or RLC layer. Specifically, if the indication of successful submission of the PDCP PDU or SDU comes from the MAC layer, the MAC entity is required to send an indication to the PDCP layer or the upper layer when confirming that the PDCP PDU or SDU or its containing transport block has been successfully transmitted; if the indication of transmission of the PDCP PDU or SDU comes from the MAC layer, the MAC entity is required to send an indication to the PDCP layer when multiplexing the PDCP PDU into a MAC PDU and/or submitting the MAC PDU to the lower layer for transmission.
  • the RLC entity is required to send an indication to the upper layer (PDCP layer) when submitting an RLCPDU containing the PDCP PDU (or the last byte or the first byte of the PDCP PDU) to the lower layer. Furthermore, it can be stipulated that the MAC or RLC will only send an indication or transmission indication of successful submission of the PDCP PDU or SDU when it determines that the PDCP PDU or SDU is the first PDCP PDU or SDU in its PDU set, or the MAC or RLC entity will only send an indication or transmission indication of successful submission of the PDCP PDU or SDU when multi-mode data synchronization is configured.
  • the indication of successful transmission from the lower layer comes from the MAC layer.
  • the MAC layer After the MAC layer confirms that a transport block containing the PDCP PDU or SDU (or a portion thereof) has been successfully transmitted, it sends an indication to the upper layer (PDCP layer).
  • the first PDCP PDU or SDU of the PDU set can be replaced by one of the following descriptions: the first PDCP PDU or SDU submitted to the lower layer of the PDU set, the first PDCP PDU or SDU of the PDU set that has been confirmed to be successfully transmitted, the last PDCP PDU or SDU of the PDU set, the last PDCP PDU or SDU of the PDU set submitted to the lower layer of the PDU set, the last PDCP PDU or SDU of the PDU set that has been confirmed to be successfully transmitted, the first PDCP PDU or SDU of the synchronous PDU cluster, the first PDCP PDU or SDU of the synchronous PDU cluster submitted to the lower layer of the PDU cluster, the first PDCP PDU or SDU of the synchronous PDU cluster that has been confirmed to be successfully transmitted, the first PDCP PDU or SDU of the first PDU set in the synchronous PDU cluster, the first PDCP PDU or SDU or SDU
  • the timer associated with the synchronization PDU cluster can also be replaced with the timer associated with the PDU set to which the PDCP PDU or its corresponding PDCP SDU belongs.
  • the UE being configured for multi-mode data synchronization can be replaced with the PDCP entity being configured for multi-mode data synchronization.
  • the UE, PDCP, or SDAP being configured for multi-mode data synchronization can refer to one of the following: being configured with a synchronization timer, being configured for inter-PDU set discarding (i.e., if a PDCP PDU or SDU in a PDU set is discarded, then all PDCP PDUs or SDUs in the synchronization PDU cluster to which that PDU set belongs are discarded), or being configured for inter-PDU set synchronization.
  • a PDCP PDU or SDU belonging to a synchronous PDU cluster means one of the following: the PDCP SDU corresponding to the PDCP PDU belongs to a synchronous PDU cluster; the PDCP PDU or its corresponding PDCP SDU's PDU set belongs to a synchronous PDU cluster; the PDCP PDU or its corresponding PDCP SDU has a synchronization relationship with other PDCP PDUs or PDCP SDUs in the synchronous PDU cluster; or the PDCP PDU or its corresponding PDCP SDU's PDU set has a synchronization relationship with other PDU sets in the synchronous PDU cluster to which the PDU set belongs.
  • the synchronous PDU cluster to which the PDCP PDU or SDU belongs is simply the synchronous PDU cluster of the PDU set to which the PDCP PDU or SDU belongs.
  • the PDU set or synchronous PDU cluster to which the PDCP PDU belongs in the embodiments of this disclosure is the same as the PDU set or synchronous PDU cluster to which the PDCP SDU corresponding to the PDCP PDU belongs, and vice versa.
  • the PDCP SDU of a synchronous PDU cluster is the same as the PDCP PDU of the synchronous PDU cluster, that is, the PDCP SDU or PDCP PDU of the PDU set in the synchronous PDU cluster.
  • a PDCP PDU belonging to a PDU set or synchronous PDU cluster is the same as a PDCP SDU belonging to a PDU set or synchronous PDU cluster, and vice versa.
  • discarding the PDCP PDU or SDU may render other PDCP PDUs or SDUs in other PDU sets within the synchronous PDU cluster invalid. Continuing to transmit these unnecessary or invalid PDCP PDUs or SDUs will result in wasted resources.
  • the following embodiments address this problem.
  • the following describes the operations involved in a PDCP entity discarding a PDCP SDU.
  • the PDCP transport entity When a PDCP SDU's discard timer expires, or its low-importance discard timer expires, or its synchronization timer (i.e., the synchronization timer associated with the PDU set or the synchronization PDU cluster to which the PDCP SDU belongs) expires, the PDCP transport entity performs at least one of the following operations:
  • Operation 2-1 If pdu-SetDiscard is configured, then: (1a) Discard all PDCP SDUs belonging to the PDU set to which the PDCP SDU belongs, as well as the corresponding PDCP data PDUs; and/or (2a) if interPdu-setDiscard is configured or the synchronization timer expires, discard all PDCP SDUs belonging to the synchronous PDU cluster to which the PDCP SDU belongs, as well as the corresponding PDCP data PDUs (i.e., PDCP SDUs belonging to all PDU sets of the synchronous PDU cluster to which the PDCP SDU belongs, as well as the corresponding PDCP data PDUs); and/or (3a) if interPdu-setDiscard is configured, or if the PDCP SDU belongs to a synchronous PDU cluster (i.e., the PDU set to which the PDCP SDU belongs belongs to a synchronous PDU cluster), or if the synchronization timer expires, discard
  • Operation 2-2 If interPdu-setDiscard is configured and/or a synchronization timer is configured and/or the PDCP SDU belongs to a PDU set or a synchronized PDU cluster and/or there exists a PDU set that is synchronized with the PDU set to which the PDCP SDU belongs, then: (1b) Discard all PDCP SDUs belonging to the PDU set to which the PDCP SDU belongs, as well as the corresponding PDCP data PDUs, and/or (2b) Discard all PDCP SDUs belonging to the synchronized PDU cluster to which the PDCP SDU belongs, as well as the corresponding PDCP data PDUs, and/or (3b) Discard all PDCP SDUs belonging to the PDU set synchronized with the PDU set to which the PDCP SDU belongs, as well as the corresponding PDCP data PDUs, and/or (4b) Indicate the discard to the upper layer (i.e., SDAP).
  • the upper layer
  • the PDCP SDU belongs to a synchronous PDU cluster (i.e., the PDU set to which the PDCP SDU belongs belongs to a synchronous PDU cluster), discard all PDCP SDUs belonging to the synchronous PDU cluster to which the PDCP SDU belongs, as well as the corresponding PDCP data PDUs, and/or (6b) if the PDCP SDU belongs to a PDU set or a synchronous PDU cluster (i.e., the PDU set to which the PDCP SDU belongs belongs to a synchronous PDU cluster, this condition is optional), instruct the upper layer (i.e., SDAP) to discard, and/or (7b) stop the synchronization timer associated with the PDU set to which the PDCP SDU belongs, the synchronous PDU cluster, or other PDU sets synchronized with the PDU set to which the PDCP SDU belongs (the synchronization timer performs this operation only during runtime).
  • a synchronous PDU cluster i.e., the P
  • the discarding is only indicated to the upper layer when the discarded PDCP SDU is the first discarded PDCP SDU in the PDU set or the synchronous PDU cluster.
  • the PDCP transmission when an instruction to discard a PDCP SDU is received from the upper layer (i.e., SDAP), the PDCP transmission performs the following operations: discards the PDCP SDU and the corresponding PDCP data PDU, and/or if pdu-SetDiscard is configured (this condition is optional), discards all PDCP SDUs and the corresponding PDCP data PDUs belonging to the PDU set to which the PDCP SDU belongs.
  • the upper layer i.e., SDAP
  • the synchronization timer expiration refers to the expiration of the synchronization timer associated with the PDU set to which the PDCP SDU belongs, the synchronous PDU cluster to which the PDCP SDU belongs, or the PDU set synchronized with the PDU set to which the PDCP SDU belongs.
  • the synchronization timer can be maintained by the transport end, and its duration can be configured for the UE by the base station via RRC messages (e.g., RRC reconfiguration messages).
  • RRC messages e.g., RRC reconfiguration messages.
  • One synchronization timer can be associated with each PDU set or synchronous PDU cluster.
  • the discard timer is configured only for DRB, and its duration is configured for the UE by the base station via RRC messages.
  • a new discard timer is started after a PDCP SDU is received from the upper layer; in other words, one discard timer is associated with each PDCP SDU.
  • the low-importance discard timer is configured only for DRB, and its duration is configured for the UE by the base station via RRC messages.
  • a new low-importance discard timer is started when a PDCP SDU belonging to a low-importance PDU set is received from the upper layer.
  • the parameter ⁇ pdu-SetDiscard ⁇ is configured by the base station for each PDCP entity of the UE via RRC messages.
  • ⁇ pdu-SetDiscard ⁇ If ⁇ pdu-SetDiscard ⁇ is set to true, the UE performs PDU-based discarding for this PDCP entity. This parameter is configured only for DRB.
  • the parameter ⁇ interPdu-setDiscard ⁇ can be configured by the base station for each PDCP entity or each SDAP entity of the UE via RRC messages (i.e., included in the parameters ⁇ PDCP-Config ⁇ or ⁇ SDAP-Config ⁇ ). If ⁇ interPdu-SetDiscard ⁇ is set to true, the UE performs synchronous PDU-based discarding for this PDCP entity or SDAP entity. This parameter can be specified to be configured only for DRB.
  • ⁇ PDCP-Config ⁇ is used to set configurable PDCP parameters for signaling, MBS multicast radio bearers, or data radio bearers
  • ⁇ SDAP-Config ⁇ is used to set configurable SDAP parameters for DRB.
  • the transport SDAP entity When the transport SDAP entity receives an SDAP SDU from a QoS stream from the upper layer, and constructs the SDAP data PDU corresponding to the SDAP SDU and submits it to the lower layer, if the SDAP data PDU belongs to a PDU set or a synchronous PDU cluster, and/or if a synchronization timer is configured, and/or if multi-mode data synchronization is configured, the SDAP entity indicates to the lower layer (e.g., the PDCP layer) the relevant information that the SDAP PDU belongs to a PDU set or a synchronous PDU cluster.
  • the lower layer e.g., the PDCP layer
  • the SDAP PDU or SDU is the first (or last) SDAP PDU or SDU in its PDU set or the first (or last) SDAP PDU or SDU in its PDU set that has been indicated to have been submitted or successfully transmitted, then start the synchronization timer associated with the PDU set to which the SDAP PDU or SDU belongs, or start the synchronization timer associated with the PDU set to which the SDAP PDU or SDU belongs, or start the synchronization timer associated with the synchronization PDU cluster to which the SDAP PDU or SDU belongs.
  • the SDAP PDU or SDU is the first SDAP PDU or SDU in the last PDU set of its corresponding synchronous PDU cluster, then stop the synchronization timer associated with the PDU set synchronized with the PDU set to which the SDAP PDU or SDU belongs, or stop the synchronization timer associated with the PDU set to which the SDAP PDU or SDU belongs, or stop the synchronization timer associated with the synchronous PDU cluster to which the SDAP PDU or SDU belongs.
  • the SDAP PDU or SDU is the last SDAP PDU or SDU in its PDU set, or if the SDAP PDU or SDU is the last SDAP PDU or SDU in its PDU set that has been indicated as submitted or successfully transmitted, or if the SDAP PDU or SDU is the first or last SDAP PDU or SDU in the last PDU set in its synchronous PDU cluster that has been indicated as submitted or successfully transmitted, then stop the synchronization timer associated with the PDU set synchronized by the PDU set to which the SDAP PDU or SDU belongs, or stop the synchronization timer associated with the PDU set to which the SDAP PDU or SDU belongs, or stop the synchronization timer associated with the synchronous PDU cluster to which the SDAP PDU or SDU belongs.
  • a transmitting SDAP entity When a transmitting SDAP entity receives a discard instruction for an SDAP PDU (i.e., a PDCP SDU) or its corresponding SDAP SDU from a lower layer (i.e., a PDCP entity), and/or the SDAP PDU or SDU belongs to a PDU set that is synchronized with other PDU sets, or belongs to a synchronized PDU cluster, or a PDU set belonging to a synchronized PDU cluster, it stops the synchronization timer associated with the PDU set or the synchronized PDU cluster, and/or instructs other PDCP entities to delete the PDCP SDU belonging to the synchronized PDU cluster.
  • the other PDCP entities are PDCP entities used to transmit PDCP SDUs or PDUs from other PDU sets that are synchronized with the SDAP PDU or SDU of the PDU set.
  • SDAP PDU belonging to a PDU set or synchronous PDU cluster means that the SDAP SDU corresponding to the SDAP PDU belongs to a PDU set or synchronous PDU cluster, and vice versa.
  • FIG. 4 is a block diagram illustrating the user equipment (UE) involved in this invention.
  • the user equipment UE400 includes a processor 401 and a memory 402.
  • the processor 401 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc.
  • the memory 402 may include, for example, volatile memory (such as random access memory, RAM), a hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory.
  • Program instructions are stored in the memory 402. When executed by the processor 401, these instructions can perform the methods described in detail herein, executed by the user equipment.
  • This synchronization method and corresponding user equipment involved in this invention have been described in detail above based on embodiments.
  • This synchronization method can be executed by the user equipment.
  • This invention is not limited to the synchronization method and corresponding user equipment; it can be implemented in other ways as long as the spirit of this invention is achieved.
  • the user equipment shown above may include more modules, such as modules that can be developed or will be developed in the future for use with base stations, MMEs, or UEs, etc.
  • modules such as modules that can be developed or will be developed in the future for use with base stations, MMEs, or UEs, etc.
  • the various identifiers shown above are merely exemplary and not limiting, and this disclosure is not limited to the specific information elements exemplified by these identifiers. Many variations and modifications can be made by those skilled in the art based on the teachings of the illustrated embodiments.
  • circuits e.g., monolithic or multi-chip integrated circuits.
  • Circuits designed to perform the functions described in this specification may include general-purpose processors, digital signal processors (DSPs), proprietary integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above devices.
  • DSPs digital signal processors
  • ASICs proprietary integrated circuits
  • FPGAs field-programmable gate arrays
  • a general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine.
  • the above circuits may be digital circuits or analog circuits. In cases where advancements in semiconductor technology have led to new integrated circuit technologies that replace existing integrated circuits, one or more embodiments of the present invention may also be implemented using these new integrated circuit technologies.
  • the present invention is not limited to the embodiments described above. Although various examples of the embodiments have been described, the present invention is not limited thereto.
  • Fixed or non-mobile electronic devices installed indoors or outdoors can be used as terminal devices or communication devices, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

Landscapes

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

Abstract

本发明提供一种同步方法以及用户设备。同步方法包括：为每个同步PDU集群或PDU集关联一个同步定时器，所述定时器的值由基站通过RRC消息为UE配置或者由上层提供；所述UE通过维护所述同步定时器来实现多模式数据同步；在由基站配置所述同步定时器的值的情况下，所述基站为每组需要同步的数据流分别配置所述定时器的值，在由上层提供所述同步定时器的值的情况下，基站为所述UE配置指示标识，所述指示标识用于指示是否允许所述UE启动或运行所述同步定时器或是否支持PDU集间同步或多模式数据同步。

Description

同步方法以及用户设备 技术领域
本发明涉及无线通信技术领域，更具体地，本发明涉及同步方法以及用户设备。
背景技术
目前，3GPP中在版本19中扩展现实(eXtended Reality，XR)的相关研究目标之一是提升对具有多模式数据相互依赖(multi-modal inter-dependencies)的多QoS流的XR应用程序有效支持，满足多模式QoS要求，例如同步和/或协调，另见TR 22.847、TR 23.70060。预计在容量或功耗方面，效率的提高将是显而易见的。相关潜在影响如下：a)通过来自核心网的信令和/或UE的指示增强RAN的感知，b)增强用户平面，例如调度、逻辑信道优先级LCP、资源分配、数据包丢弃，等等。
本发明讨论多模式同步和/或协调所涉及的相关问题。
发明内容
为了解决上述问题中的至少一部分，本发明提供了一种同步方法以及用户设备。
根据本发明的第一方面，提供了一种同步方法，包括：为每个同步PDU集群或PDU集关联一个同步定时器，所述定时器的值由基站通过RRC消息为UE配置或者由上层提供；所述UE通过维护所述同步定时器来实现多模式数据同步；在由基站配置所述同步定时器的值的情况下，所述基站为每组需要同步的数据流分别配置所述定时器的值，在由上层提供所述同步定时器的值的情况下，基站为所述UE配置指示标识，所述指示标识用于指示是否允许所述UE启动或运行所述同步定时器或是否支持PDU集间同步或多模式数据同步。
在上述第一方面的同步方法中，基于QoS流与DRB间的映射关系，所述同步定时器运行在SDAP层或者PDCP层或者RLC层。
在上述第一方面的同步方法中，在向下层提交一个PDCP PDU时，或者在接收到来自下层的PDCP PDU或PDCP SDU成功提交的指示时，或者在接收到来自下层的PDCP PDU或PDCP SDU已传输的指示时，或者在接收到来自下层的PDCP PDU或PDCP SDU传输成功的指示时，传输PDCP实体执行以下操作：如果UE或所述PDCP实体被配置了多模式数据同步和/或所述PDCP PDU属于一个同步PDU集群和/或所述PDCP PDU属于一个PDU集，则执行操作1-1至操作1-3的至少一项。
在上述第一方面的同步方法中，所述操作1-1至操作1-3分别为：
所述操作1-1：如果所述PDCP PDU或PDCP SDU所属同步PDU集群所关联的同步定时器未运行，或如果与所述PDCP PDU或PDCP SDU所属PDU集存在同步关系的PDU集所关联的同步定时器未运行，或如果所述PDCP PDU或PDCP SDU所属PDU集所关联的同步定时器未运行，则启动所述同步定时器；
所述操作1-2：如果所述PDCP PDU或PDCP SDU是其所属PDU集的第一个PDCP PDU或PDCP SDU，和/或如果被配置了同步定时器，和/或所述PDCP PDU或PDCP SDU所属的同步PDU集群所关联的同步定时器未运行或与所述PDCP PDU或PDCP SDU所属PDU集存在同步关系的PDU集所关联的同步定时器未运行，和/或所述PDCP PDU或PDCP SDU所属PDU集所关联的同步定时器未运行，则：(1)如果所述PDCP PDU或PDCP SDU所属PDU集或同步PDU集群的同步定时器正在运行，则停止所述同步定时器，和/或(2)启动所述同步定时器，和/或(3)向上层指示所述提交信息，以便上层在接收到所述指示时启动所述PDU集或同步PDU集群所关联的定时器；
所述操作1-3：如果所述PDCP PDU或PDCP SDU是其所属PDU集或所属同步PDU集群的最后一个被提交下层的PDCP PDU或PDCP SDU，或者如果所述PDCP PDU或PDCP SDU是其所属同步PDU集群的最后一个向下层提交PDCP PDU的PDU集中第一个被提交下层的PDCP PDU或PDCP SDU，或者如果所述PDCP PDU或PDCP SDU是其所属PDU集或所属同步PDU集群的最后一个被下层确认传输成功的PDCP PDU或PDCP SDU，则停止所述PDCP PDU或PDCP SDU所属PDU集或所属同步PDU集群所关联的同步定时器，或者向上层指示所述提交。
在上述第一方面的同步方法中，PDCP实体在接收到来自下层的PDU集或同步PDU集群的最后一个PDCP PDU或PDCP SDU的成功提交的指示或者传输指示，则停止所述PDU集或所述同步PDU集群所关联的同步定时器。
在上述第一方面的同步方法中，所述PDCP PDU或PDCP SDU成功提交的指示或者传输指示可以来自MAC或RLC层。
在上述第一方面的同步方法中，在一个PDCP SDU的丢弃定时器到期或低重要性丢弃定时器到期或同步定时器到期的情况下，传输PDCP实体执行以下操作的至少一项：
操作2-1：如果被配置了pdu-SetDiscard，则：(1a)丢弃属于PDCP SDU所属PDU集的所有PDCP SDU以及相应的PDCP数据PDU，和/或(2a)如果被配置了interPdu-setDiscard或所述同步定时器到期，丢弃属于PDCP SDU所属同步PDU集群的所有PDCP SDU以及相应的PDCP数据PDU，和/或(3a)如果被配置了interPdu-setDiscard或如果所述PDCP SDU属于一个同步PDU集群或如果同步定时器到期，丢弃属于PDCP SDU所属同步PDU集群的所有PDCP SDU以及相应的PDCP数据PDU，和/或(4a)如果被配置了interPdu-setDiscard和/或如果所述PDCP SDU属于一个同步PDU集群，向上层指示所述丢弃，和/或(5a)如果被配置了interPdu-setDiscard和/或如果所述PDCP SDU属于一个同步PDU集群的PDU集或属于一个同步PDU集群和/或如果存在与所述PDCP SDU所属PDU集存在同步关系的PDU集，则停止所述PDCP SDU所属PDU集或所述同步PDU集群或与所述PDCP SDU所属PDU集存在同步关系的PDU集所关联的同步定时器；
操作2-2：如果配置了interPdu-setDiscard和/或被配置了同步定时器和/或所述PDCP SDU属于一个PDU集或同步PDU集群和/或存在与所述PDCP SDU所属PDU集有同步关系的PDU集，则：(1b)丢弃属于PDCP SDU所属PDU集的所有PDCP SDU以及相应的PDCP数据PDU，和/或(2b)丢弃属于PDCP SDU所属同步PDU集群的所有PDCP SDU以及相应的PDCP数据PDU，和/或(3b)丢弃属于与所述PDCP SDU所属PDU集同步的PDU集的所有PDCP SDU以及相应的PDCP数据PDU，和/或(4b)向上层指示所述丢弃，和/或(5b)如果所述PDCP SDU属于一个同步PDU集群，丢弃属于PDCP SDU所属同步PDU集群的所有PDCP SDU以及相应的PDCP数据PDU，和/或(6b)如果所述PDCP SDU属于一个PDU集或同步PDU集群，向上层指示所述丢弃，和/或(7b)停止所述PDCP SDU所属PDU集或所述同步PDU集群或与所述PDCP SDU所属PDU集同步的其他PDU集所关联的同步定时器。
在上述第一方面的同步方法中，当接收到来自上层即SDAP的丢弃PDCP SDU的指示，传输PDCP执行以下操作：丢弃所述PDCP SDU以及相应的PDCP数据PDU，和/或如果配置了pdu-SetDiscard，丢弃属于PDCP SDU所属PDU集的所有PDCP SDU以及相应的PDCP数据PDU。
在上述第一方面的同步方法中，传输SDAP实体在接收到来自下层的SDAP PDU或SDU已提交的指示或已成功传输的指示，则执行以下至少一项：
(1)如果所述SDAP PDU或SDU是其所属PDU集的第一个或最后一个SDAP PDU或SDU或者是其所属PDU集的第一个或最后一个被指示已提交或已成功传输的SDAP PDU或SDU，则启动所述SDAP PDU或SDU所属PDU集同步的PDU集所关联的同步定时器，或者启动所述SDAP PDU或SDU所属PDU集所关联的同步定时器，或者启动所述SDAP PDU或SDU所属同步PDU集群所关联的同步定时器；
(2)如果所述SDAP PDU或SDU是其所属同步PDU集群中的最后一个PDU集中的第一个SDAP PDU或SDU，则停止与所述SDAP PDU或SDU所属PDU集同步的PDU集所关联的同步定时器，或者停止所述SDAP PDU或SDU所属PDU集所关联的同步定时器，或者停止所述SDAP PDU或SDU所属同步PDU集群所关联的同步定时器；
(3)如果所述SDAP PDU或SDU是其所属PDU集的最后一个SDAP PDU或SDU，或者如果所述SDAP PDU或SDU是其所属PDU集的最后一个被指示已提交或已成功传输的SDAP PDU或SDU，或者如果所述SDAP PDU或SDU是其所属同步PDU集群的最后一个PDU集的第一个或最后一个被指示已提交或已成功传输的SDAP PDU或SDU，则停止所述SDAP PDU或SDU所属PDU集同步的PDU集所关联的同步定时器，或者停止所述SDAP PDU或SDU所属PDU集所关联的同步定时器，或者停止所述SDAP PDU或SDU所属同步PDU集群所关联的同步定时器。
此外，根据本发明的第二方面提供了一种用户设备，包括：处理器；以及存储器，存储有指令，其中，所述指令在由所述处理器运行时执行上述的同步方法。
发明效果
根据本发明提供的同步方法以及相应的用户设备，能够有效地解决PDU或PDU集间的同步的问题。
附图说明
通过下文结合附图的详细描述，本发明的上述和其它特征将会变得更加明显，其中：
图1是表示本发明的数据在空口传输所涉及的协议栈示意图。
图2是表示多模式服务中数据流与RLC之间的一种映射关系的示意图。
图3是表示多模式服务中数据流与承载之间的另一种映射关系的示意图。
图4是表示本发明所涉及的用户设备UE的框图。
具体实施方式
下面描述本发明涉及的部分术语，术语的具体含义可参见3GPP最新相关文档，例如TS38.300-i20、TS38.321-i20、TS38.323-i20、TS38.331-i20等。此外，本发明实施例以广播/多播服务为例进行描述，但本发明实施例不限于广播/多播服务，也可以应用于其他应用场景。
UE：User Equipment，用户设备。
RRC：Radio Resource Control，无线资源控制。
RRC_CONNECTED：RRC连接态。
RRC_INACTIVE：RRC非激活态。
RRC_IDLE：RRC空闲态。
RAN：Radio Access Network，无线接入网。
NR：New RAT，新无线接入技术。
AS：Access Stratum，接入层或访问层。
NAS：Non Access Stratum，非接入层或非访问层。
RB：Radio Bearer，无线承载。DRB是数据无线承载。每个DRB可以关联到一个SDAP实体，并且有一个对应的PDCP实体和一个或多个RLC实体。
PDU：Protocol Data Unit协议数据单元
SDU：Service Data Unit服务数据单元
AM：Acknowledged Mode确认模式
UM：Unacknowledged Mode非确认模式
TM：Transparent Mode透传模式
SDAP：Service Data Adaptation Protocol业务数据自适应协议
PDCP：Packet Data Convergence Protocol分组数据汇聚协议
RLC：Radio Link Control无线链路控制
MAC：Medium Access Control媒体接入控制
HARQ：Hybrid Automatic Repeat reQuest混合自动重传请求，HARQ实体或进程位于MAC层或MAC实体。
PDU集：PDU Set，PDU集由一个或多个PDU组成，这些PDU携带在应用程序级别生成的一个信息单元的有效载荷(例如，XR服务的帧或视频切片)。在一些实现中，应用层需要PDU集中的所有PDU来使用相应的信息单元。在其他实现中，当某些PDU丢失时，应用层仍然可以恢复信息单元的部分或全部。PDU集中的一个PDU对应一个PDCP SDU。
多模式数据：Multi-modal Data，多模式数据被定义为描述同一任务或应用程序所需的来自不同类型设备/传感器的输入数据或到不同类型目的地(例如一个或多个UE)的输出数据。多模式数据由多个单模式数据组成，每个单模式数据之间存在很强的依赖性。单模式数据可以看作是一种数据。每个单模式数据可以映射到一个数据流(data flow)。每个数据流都有对应的服务质量QoS要求，因此数据流又称为服务质量流(QoS Flow)或QoS流。
多模式服务：multi-modal service是一种通信服务，由多个相互关联的数据流组成，这些数据流需要应用程序协调。数据流可以传输不同类型的数据(例如音频、视频、定位、触觉数据)，并且可能来自不同的来源(例如，单个UE、连接到单个UE的单个设备或多个设备，或多个UE)。对于单个UE的情况，这些数据流密切相关，需要强有力的应用协调才能正确执行多模式应用，因此，所有这些数据流都在单个PDU会话中传输。
多模式服务ID(Multi-modal Service ID，MMSID)用来指示与多模式服务关联的数据流。具有相同MMSID的数据流属于一个多模式服务。
同步阈值：synchronisation threshold，多模式同步阈值可以定义为两个刺激开始的最大可容忍时间间隔，其中一个刺激呈现给一个感官，另一个呈现给另一个感官，使得伴随的感觉对象被感知为同步的(Amulti-modal synchronisation threshold can be defined as the maximum tolerable temporal separation of the onset of two stimuli.one of which is presented to one sense and the other to another sense，such that the accompanying sensory objects are perceived as being synchronous)。同一个多模式数据的单模式数据间可能存在同步关系，来自一个单模式数据的PDU集与来自另一个或多个单模式数据的PDU集之间存在同步关系，例如当一个PDU集的数据传输开始(也可替换为结束)时，要求与之同步的一个或多个PDU集的数据传输必须在同步阈值所限制的时间内开始(也可替换为结束)。本公开中，将存在同步关系的两个或多个PDU集所组成的PDU集的集合称为同步PDU集群。同步PDU集群也包含所述同步PDU集群中仅包含一个PDU集且所述PDU集的PDU之间存在依赖关系或同步关系。如未特别说明，本公开实施例所述同步PDU集群可以指包含一个或多个PDU集的情况。
图1示出了本公开中数据在空口传输所涉及的协议栈示例。协议栈从上到下依次为SDAP、PDCP、RLC、MAC、物理层。SDAP层的下层可以是PDCP和/或RLC和/或MAC和/或物理层，PDCP层的下层可以是RLC和/或MAC和/或物理层，RLC层的下层可以是MAC和/或物理层。相应的，MAC层的上层可以是SDAP和/或PDCP和/或RLC，RLC层的上层可以是SDAP和/或PDCP，PDCP层的上层可以是SDAP。各层的功能由对应的实体实现，具体的MAC层的功能由MAC实体实现、RLC层的功能由RLC实体实现、PDCP层的功能由PDCP实体实现、SDAP层的功能由SDAP实体实现。在本公开中，层和实体可互换使用。本公开在涉及某层或某个实体时，如未具体言明是实体还是层，本领域技术人员可以根据上下文推断是指对应的层还是实体。本公开实施例中SDU与PDU混合适用，本领域技术人员可以根据上下文容易的得出所述SDU是PDU所对应的SDU，同样的所述PDU是SDU所对应的PDU。因此，如未特别说明，将PDU替换为SDU或将SDU替换为PDU得到的实施例也是本公开包含的范围。
从UE角度看，对于下行，物理层在接收到来自基站的数据时，传送(deliver)给MAC层，MAC层进行相应的处理后传送给相应的RLC实体，RLC实体处理后传送给PDCP层，PDCP层处理后传送给SDAP层，SDAP层处理后又传送给上层(例如NAS层)。对于上行，SDAP层接收来自上层(例如NAS层)的数据并经SDAP层处理后提交(submit)给相应的PDCP实体，PDCP实体对所述数据处理后提交给相应的RLC实体，RLC实体对所述数据处理后提交给MAC层，MAC层对所述数据处理后提交给物理层，物理层对所述数据处理后在空口发送给基站。对每层来说，从上层接收的数据称为SDU，提交给下层的数据称为PDU。例如，PDCP层从SDAP层接收或传送到SDAP层的数据称为PDCP SDU(即SDAP PDU)，PDCP层从RLC层接收或提交给RLC层的数据称为PDCP PDU(即RLC SDU)，其他层亦是如此。
本发明中，网络、基站和RAN可互换使用，所述网络可以是长期演进LTE网络、NR网络、增强的长期演进eLTE网络，也可以是3GPP后续演进版本中定义的其他网络，例如6G网络。对于下行(即UE侧数据接收过程)，PDCP实体也称为接收PDCP实体(receiving PDCP entity)，相应的对端实体(即位于基站的PDCP实体)是传输PDCP实体(transmitting PDCP entity)。对于上行(即UE侧数据发送过程)，PDCP实体也称为传输PDCP实体，相应的对端实体(即位于基站的PDCP实体)是接收PDCP实体。RLC实体支持三种模式，一种是AM RLC，一种是UM RLC，一种是TM RLC，它们对应的RLC实体分别为AM RLC实体、UM RLC实体和TM RLC实体。UM RLC实体可以被配置为接收UM RLC实体(receiving UM RLC entity)和传输UM RLC实体(transmitting UM RLC entity)来分别执行接收和发送操作。TM RLC实体也可以被配置为接收TM RLC实体和发送TM RLC实体来分别执行接收和发送操作。AM RLC实体包括AM RLC实体的传输端(transmitting side of an AM RLC entity)和AM RLC实体的接收端(receiving side of an AM RLC entity)，分别用于从上层接收数据并通过下层发送到对端(peer)AM RLC实体和向上层递送数据并通过下层接收来自对端AM RLC实体的数据。在本公开实施例中提及RLC实体时，本领域技术人员可以相应的替换为发送或接收UM RLC实体、送或接收TM RLC实体、AM RLC实体的传输端或接收端。
当前版本R19 XR讨论所关注的一个方面是多模式数据间的同步。换而言之，要实现来自不同数据流的数据(或PDU或PDU集)间同步或协同，当一个PDU或PDU集的数据传输开始(也可替换为结束)时，要求与之同步的一个或多个PDU集的数据(即同步PDU集群内的其他PDU集)传输必须在同步阈值所限制的时间内开始(也可替换为结束)。如何实现PDU或PDU集间的同步是需要解决的问题。
以下提供实施例来解决这一问题。
为每个同步PDU集群或PDU集关联一个同步定时器，所述定时器的值可以由基站通过RRC消息为UE配置或者由上层(例如NAS层)提供。UE通过维护同步定时器来实现多模式数据同步。如果所述同步定时器的值由基站配置，基站在配置所述同步定时器的值时，可以为每组需要同步的数据流分别配置所述定时器的值，例如为每个DRB或每个PDCP实体配置所述定时器的值。如果同步定时器的值由上层提供，基站可以为UE配置指示标识(即同步PDU集群参数)来指示是否允许UE启动或运行所述同步定时器或是否支持(或允许或被配置了)PDU集间同步或多模式数据同步。
图2示出了多模式服务中数据流与RLC之间的一种映射关系示意图。如图2所示，SDAP实体将一个多模式服务关联的所有QoS流映射到一个数据承载DRB，PDCP再将不同QoS流的PDCP SDU(或与PDCP SDU对应的PDCP PDU)提交给与所述QoS流对应的RLC实体。例如，QoS流1的PDCP SDU映射到RLC1，QoS流2的PDCP SDU映射到RLC2。
图3示出了多模式服务中数据流与承载之间的另一种映射关系示意图。如图3所述，SDAP实体将一个多模式服务关联的不同QoS流(即QoS流的数据)映射到不同的数据承载DRB或其对应的PDCP实体。例如，将QoS流1的数据(或SDAP PDU)映射到DRB1或PDCP1，将QoS流2的数据(或SDAP PDU)映射到DRB2或PDCP2。
基于QoS流与DRB间的不同映射关系，所述同步定时器可以运行在SDAP层或者PDCP层或者RLC层。例如，如果采用图2的映射关系，同步定时器可以运行在PDCP层，如果采用图3的映射关系，同步定时器可以运行在SDAP层。
以下描述传输PDCP实体执行的操作。
在一个实施例中，在向下层提交一个PDCP PDU时(upon)，或者在接收到来自下层(例如RLC或MAC)的PDCP PDU或PDCP SDU成功提交的指示(即已提交或已提交用于传输的指示)时，或者在接收到来自下层(例如RLC或MAC)的PDCP PDU或PDCP SDU已传输的指示时，或者在接收到来自下层(例如RLC或MAC)的PDCP PDU或PDCP SDU传输成功的指示时，传输PDCP实体执行以下操作：
如果UE或所述PDCP实体被配置了多模式数据同步和/或所述PDCP PDU属于一个同步PDU集群(换言之，所述PDCP PDU属于一个同步PDU集群中的PDU集)和/或所述PDCP PDU属于一个PDU集(这组判断条件是可选的，例如，如果接收到来自下层的的PDCP PDU或PDCP SDU成功提交的指示，则直接执行以下操作至少一项)，则执行以下操作至少一项：
操作1-1：如果所述PDCP PDU或PDCP SDU所属同步PDU集群所关联的同步定时器未运行，或如果与所述PDCP PDU或PDCP SDU所属PDU集存在同步关系的PDU集所关联的同步定时器未运行，或如果所述PDCP PDU或PDCP SDU所属PDU集所关联的同步定时器未运行，则启动所述同步定时器。
操作1-2：如果所述PDCP PDU或PDCP SDU是其所属PDU集或所属同步PDU集群的第一个PDCP PDU或PDCP SDU，和/或如果被配置了同步定时器，和/或所述PDCP PDU或PDCP SDU所属的同步PDU集群所关联的同步定时器未运行或与所述PDCP PDU或PDCP SDU所属PDU集存在同步关系的PDU集所关联的同步定时器未运行，和/或所述PDCP PDU或PDCP SDU所属PDU集所关联的同步定时器未运行，则：(1)如果所述PDCP PDU或PDCP SDU所属PDU集或同步PDU集群的同步定时器正在运行，则停止所述同步定时器，和/或(2)启动所述同步定时器，和/或(3)向上层(即SDAP)指示所述提交信息，例如向上层指示已提交所述PDU集或同步PDU集群的第一个PDCP PDU或PDCP SDU的相关信息，以便上层在接收到所述指示时启动所述PDU集或同步PDU集群所关联的定时器。需要说明的是，所述条件“与所述PDCP PDU或PDCP SDU所属的PDU集存在同步关系的PDU集所关联的同步定时器未运行”中与所述PDCP PDU或PDCP SDU所属的PDU集存在同步关系的PDU集可能有多个，相应的同步定时器也有多个，如果应用所述条件，则分别启动与所述PDCP PDU或SDU所属的PDU集存在同步关系的PDU集所关联的同步定时器。
操作1-3：如果所述PDCP PDU或PDCP SDU是其所属PDU集或所属同步PDU集群的最后一个被提交下层的PDCP PDU或PDCP SDU(换言之，所述PDU集或同步PDU集群中的所有PDCP PDU或PDCP SDU均已提交下层或已传输)，或者如果所述PDCP PDU或PDCP SDU是其所属同步PDU集群的最后一个向下层提交PDCP PDU的PDU集中第一个(或最后一个)被提交下层(或被下层确认已发送或已成功传输)的PDCP PDU或PDCP SDU(换言之，所述同步PDU集群中的其他PDU集均存在PDCP PDU或PDCP SDU已提交下层或已传输)，或者如果所述PDCP PDU或PDCP SDU是其所属PDU集或所属同步PDU集群的最后一个被下层确认传输成功的PDCP PDU或PDCP SDU(换言之，所述PDU集或同步PDU集群中的所有PDCP PDU或PDCP SDU均已被下层确认传输成功)，则停止所述PDCP PDU或PDCP SDU所属PDU集或所属同步PDU集群所关联的同步定时器(定时器在运行时才执行)，或者向上层(例如SDAP)指示所述提交，例如，向上层指示所述PDCP PDU或PDCP SDU是其所属PDU集或所属同步PDU集群的最后一个PDCP PDU或PDCP SDU已被提交下层。
可以规定，PDCP实体在接收到来自下层(RLC或MAC)的PDU集或同步PDU集群的最后一个PDCP PDU或PDCP SDU的成功提交的指示或者传输指示(换言之，所述PDU集或同步PDU集群中的所有PDCP PDU或PDCP SDU均已被下层指示已提交下层或者被下层确认成功传输)，则停止所述PDU集或所述同步PDU集群所关联的同步定时器。
在本实施例中，所述PDCP PDU或PDCP SDU成功提交的指示或者传输指示可以来自MAC或RLC层。具体的，如果PDCP PDU或SDU成功提交的指示来自MAC层就要求MAC实体在确认所述PDCP PDU或SDU或其所在传输块传输成功时，向PDCP层或上层发送指示；如果PDCP PDU或SDU传输指示来自MAC层就要求MAC实体在将所述PDCP PDU复用到一个MAC PDU和/或将所述MAC PDU提交下层传输时，向PDCP层发送指示。如果PDCP PDU或SDU成功提交的指示或者传输指示来自RLC层就要求RLC实体在将包含所述PDCP PDU(或所述PDCP PDU的最后一个字节或第一个字节)的RLCPDU提交下层时，向上层(PDCP层)发送指示。进一步的，可以规定，MAC或RLC在确定所述所述PDCP PDU或SDU是其所属PDU集的第一个PDCP PDU或SDU时才发送所述PDCP PDU或SDU成功提交的指示或者传输指示，或者在被配置了多模式数据同步时，MAC或RLC实体才发送所述PDCP PDU或SDU成功提交的指示或者传输指示。
所述来自下层的传输成功的指示来自MAC层，在MAC层确认一个包含所述PDCP PDU或SDU(或其部分)的传输块被成功传输后，向上层(PDCP层)发送指示。
需要说明的是，本实施例中操作1-2中，PDU集的第一个PDCP PDU或SDU可以替换为以下描述之一：PDU集的第一个被提交下层的PDCP PDU或SDU、PDU集的第一个被确认传输成功的PDCP PDU或SDU、PDU集的最后一个PDCP PDU或SDU、PDU集的最后一个被提交下层PDCP PDU或SDU、PDU集的最后一个被确认传输成功的PDCP PDU或SDU、同步PDU集群的第一个PDCP PDU或SDU、同步PDU集群的第一个被提交下层的PDCP PDU或SDU、同步PDU集群的第一个被确认传输成功的PDCP PDU或SDU、同步PDU集群中第一个PDU集的第一个PDCP PDU或SDU、同步PDU集群中第一个PDU集的第一个被提交下层的PDCP PDU或SDU、同步PDU集群中第一个PDU集的第一个被确认传输成功的PDCP PDU或SDU。
本公开实施例中，所述同步PDU集群所关联的定时器也可以替换为PDCP PDU或其对应的PDCP SDU所属PDU集所关联的定时器。UE被配置了多模式数据同步可以替换为PDCP实体被配置了多模式数据同步。所述UE或PDCP或SDAP被配置了多模式数据同步可以指以下之一：被配置了同步定时器、被配置了PDU集间丢弃(即如果一个PDU集中的PDCP PDU或SDU被丢弃，则丢弃所述PDU集所属同步PDU集群中所有PDCP PDU或SDU)、被配置了PDU集间同步。PDCP PDU或SDU属于一个同步PDU集群是指以下之一：PDCP PDU所对应的PDCP SDU属于一个同步PDU集群、PDCP PDU或其对应的PDCP SDU所属PDU集属于一个同步PDU集群、所述PDCP PDU或其对应的PDCP SDU与同步PDU集群中的其他PDCP PDU或PDCP SDU存在同步关系、所述PDCP PDU或其对应的PDCP SDU所属PDU集与该PDU集所属的同步PDU集群中的其他PDU集间存在同步关系。PDCP PDU或SDU所属同步PDU集群就是所述PDCP PDU或SDU所属的PDU集的同步PDU集群。
本公开实施例所述PDCP PDU所属的PDU集或同步PDU集群就是所述PDCP PDU所对应的PDCP SDU所属的PDU集或同步PDU集群，反之亦然。同步PDU集群的PDCP SDU就是同步PDU集群的PDCP PDU，也就是同步PDU集群中的PDU集的PDCP SDU或PDCP PDU。PDCP PDU属于一个PDU集或同步PDU集群就是PDCP SDU属于一个PDU集或同步PDU集群，反之亦然。
当属于一个PDU集的PDCP PDU或SDU被丢弃，如果所述PDU集属于一个同步PDU集群，则丢弃所述PDCP PDU或SDU可能导致所述同步PDU集群中的其他PDU集中的PDCP PDU或SDU不再有效，继续传输这些不必要或无效的PDCP PDU或SDU将导致资源浪费。以下提供实施例解决这一问题。
以下描述PDCP实体丢弃PDCP SDU所涉及的操作。
当一个PDCP SDU的丢弃定时器(discardTimer)到期或低重要性丢弃定时器(discardTimerForLowlmprotance)到期或同步定时器(即所述PDCP SDU所属PDU集或所属同步PDU集群所关联的同步定时器)到期，传输PDCP实体执行以下操作至少一项：
操作2-1：如果被配置了pdu-SetDiscard，则：(1a)丢弃属于PDCP SDU所属PDU集的所有PDCP SDU以及相应的PDCP数据PDU，和/或(2a)如果被配置了interPdu-setDiscard或所述同步定时器到期，丢弃属于PDCP SDU所属同步PDU集群的所有PDCP SDU以及相应的PDCP数据PDU(即所属同步PDU集群的所有PDU集的PDCP SDU以及相应的PDCP数据PDU)，和/或(3a)如果被配置了interPdu-setDiscard或如果所述PDCP SDU属于一个同步PDU集群(即PDCP SDU所属PDU集属于一个同步PDU集群)或如果同步定时器到期，丢弃属于PDCP SDU所属同步PDU集群的所有PDCP SDU以及相应的PDCP数据PDU，和/或(4a)如果被配置了interPdu-setDiscard和/或如果所述PDCP SDU属于一个同步PDU集群(即PDCP SDU所属PDU集属于一个同步PDU集群)或存在与所述PDCP SDU所属PDU集同步的PDU集，向上层(即SDAP)指示所述丢弃，和/或(5a)如果被配置了interPdu-setDiscard和/或如果所述PDCP SDU属于一个同步PDU集群的PDU集或属于一个同步PDU集群和/或如果存在与所述PDCP SDU所属PDU集存在同步关系的PDU集，则停止所述PDCP SDU所属PDU集或所述同步PDU集群或与所述PDCP SDU所属PDU集存在同步关系的PDU集所关联的同步定时器(所述同步定时器在运行时才执行此操作)。需要说明的，本操作中“丢弃属于PDCP SDU所属同步PDU集群的所有PDCP SDU以及相应的PDCP数据PDU”可以替换为“丢弃属于与所述PDCP SDU所属PDU集存在同步关系的PDU集的所有PDCP SDU以及相应的PDCP数据PDU”。
操作2-2：如果配置了interPdu-setDiscard和/或被配置了同步定时器和/或所述PDCP SDU属于一个PDU集或同步PDU集群和/或存在与所述PDCP SDU所属PDU集有同步关系的PDU集，则：(1b)丢弃属于PDCP SDU所属PDU集的所有PDCP SDU以及相应的PDCP数据PDU，和/或(2b)丢弃属于PDCP SDU所属同步PDU集群的所有PDCP SDU以及相应的PDCP数据PDU，和/或(3b)丢弃属于与所述PDCP SDU所属PDU集同步的PDU集的所有PDCP SDU以及相应的PDCP数据PDU，和/或(4b)向上层(即SDAP)指示所述丢弃，和/或(5b)如果所述PDCP SDU属于一个同步PDU集群(即PDCP SDU所属PDU集属于一个同步PDU集群)，丢弃属于PDCP SDU所属同步PDU集群的所有PDCP SDU以及相应的PDCP数据PDU，和/或(6b)如果所述PDCP SDU属于一个PDU集或同步PDU集群(即PDCP SDU所属PDU集属于一个同步PDU集群，这个判断条件是可选的)，向上层(即SDAP)指示所述丢弃，和/或(7b)停止所述PDCP SDU所属PDU集或所述同步PDU集群或与所述PDCP SDU所属PDU集同步的其他PDU集所关联的同步定时器(所述同步定时器在运行时才执行此操作)。
需要说明的是，在上述操作中，可以进一步规定只有在所述被丢弃的PDCP SDU是所属PDU集或同步PDU集群的第一个被丢弃的PDCP SDU时才向上层指示所述丢弃。
此外，当接收到来自上层(即SDAP)的丢弃PDCP SDU的指示，传输PDCP执行以下操作：丢弃所述PDCP SDU以及相应的PDCP数据PDU，和/或如果配置了pdu-SetDiscard(这个条件是可选的)，丢弃属于PDCP SDU所属PDU集的所有PDCP SDU以及相应的PDCP数据PDU。
本公开实施例中，如未特别说明，同步定时器到期是PDCP SDU所属PDU集或所述PDCP SDU所属同步PDU集群或与所述PDCP SDU所属PDU集同步的PDU集所关联的同步定时器到期。同步定时器可由传输端维护，所述定时器的持续时间可由基站通过RRC消息(例如RRC重配置消息)为UE配置。可以为每个PDU集或同步PDU集群关联一个同步定时器。丢弃定时器(discardTimer)仅配置用于DRB，所述定时器的持续时间由基站通过RRC消息为UE配置。在传输端(即传输PDCP实体)，在从上层接收到PDCP SDU后，会启动一个新的丢弃定时器，换言之，每个PDCP SDU关联一个丢弃定时器。低重要性丢弃定时器仅配置用于DRB，所述定时器的持续时间由基站通过RRC消息为UE配置。在传输端(即传输PDCP实体)，当从上层接收到属于低重要性PDU集的PDCP SDU时，会启动一个新的低重要性丢弃定时器。参数pdu-SetDiscard是由基站通过RRC消息为UE的每个PDCP实体配置的，如果pdu-SetDiscard被设置为真(true)，UE为这个PDCP实体执行基于PDU集的丢弃，这个参数仅配置用于DRB。参数interPdu-setDiscard可由基站通过RRC消息为UE的每个PDCP实体或者每个SDAP实体配置(即包含在参数PDCP-Config或SDAP-Config中)。如果interPdu-SetDiscard被设置为真(true)，UE为这个PDCP实体或SDAP实体执行基于同步PDU集群的丢弃，可以规定这个参数仅配置用于DRB。所述PDCP-Config用于设置信令、MBS多播无线承载或数据无线承载的可配置的PDCP参数，所述SDAP-Config用于为DRB设置可配置的SDAP参数。
本公开实施例中，所述丢弃PDU或PDU集或数据可以是PDCP实体所丢弃的PDCP PDU和/或PDCP SDU和/或RLC实体所丢弃的RLC PDU和/或RLC SDU或其分段。
以下描述为实现多模式数据同步SDAP实体所执行的操作的实施例。
传输SDAP实体接收到来自上层的一个QoS流的SDAP SDU，SDAP实体在构建所述SDAP SDU对应的SDAP数据PDU并提交下层时，如果所述SDAP数据PDU属于一个PDU集或同步PDU集群，和/或如果被配置了同步定时器，和/或如果被配置了多模式数据同步，则将所述SDAP PDU属于一个PDU集或同步PDU集群的相关信息指示给下层(例如PDCP层)。
传输SDAP实体在接收到来自下层的SDAP PDU或SDU已提交的指示或已成功传输的指示，则执行以下至少一项：
(1)如果所述SDAP PDU或SDU是其所属PDU集的第一个(或最后一个)SDAP PDU或SDU或者是其所属PDU集的第一个(或最后一个)被指示已提交或已成功传输的SDAP PDU或SDU，则启动与所述SDAP PDU或SDU所属PDU集同步的PDU集所关联的同步定时器，或者启动所述SDAP PDU或SDU所属PDU集所关联的同步定时器，或者启动所述SDAP PDU或SDU所属同步PDU集群所关联的同步定时器。
(2)如果所述SDAP PDU或SDU是其所属同步PDU集群中的最后一个PDU集中的第一个SDAP PDU或SDU，则停止与所述SDAP PDU或SDU所属PDU集同步的PDU集所关联的同步定时器，或者停止所述SDAP PDU或SDU所属PDU集所关联的同步定时器，或者停止所述SDAP PDU或SDU所属同步PDU集群所关联的同步定时器。需要说明的是，与所述SDAP PDU或SDU所属PDU集同步的PDU集可能有多个，则分别停止与所述SDAP PDU或SDU所属PDU集同步的PDU集所关联的同步定时器。
(3)如果所述SDAP PDU或SDU是其所属PDU集的最后一个SDAP PDU或SDU，或者如果所述SDAP PDU或SDU是其所属PDU集的最后一个被指示已提交或已成功传输的SDAP PDU或SDU，或者如果所述SDAP PDU或SDU是其所属同步PDU集群的最后一个PDU集的第一个或最后一个被指示已提交或已成功传输的SDAP PDU或SDU，则停止所述SDAP PDU或SDU所属PDU集同步的PDU集所关联的同步定时器，或者停止所述SDAP PDU或SDU所属PDU集所关联的同步定时器，或者停止所述SDAP PDU或SDU所属同步PDU集群所关联的同步定时器。
传输SDAP实体在接收到来自下层(即一个PDCP实体)的SDAP PDU(即PDCP SDU)或其对应的SDAP SDU的丢弃指示，和/或所述SDAP PDU或SDU属于一个与其他PDU集存在同步关系的PDU集或者属于一个同步PDU集群或属于一个同步PDU集群的PDU集，则停止所述PDU集或所述同步PDU集群所关联的同步定时器，和/或指示其他PDCP实体删除属于所述同步PDU集群的PDCP SDU。可以规定，所述其他PDCP实体是用于传输与所述SDAP PDU或SDU所述PDU集同步的其他PDU集中的PDCP SDU或PDU的PDCP实体。
可以规定，本公开实施例中，在执行启动同步定时器之前，可以先判断所述同步定时器是否正在运行，如果未运行才启动所述同步定时器。
当一个PDU集或同步PDU集群所关联的同步定时器到期，指示下层(即PDCP实体)删除属于所述PDU集或同步PDU集群的PDCP SDU。可以规定，所述PDCP实体是用于传输所述PDU集或同步PDU集群的PDCP SDU的PDCP实体。
需要说明的是，本公开中，SDAP PDU属于一个PDU集或同步PDU集群就是指所述SDAP PDU对应的SDAP SDU属于一个PDU集或同步PDU集群，反之亦然。
本公开中，字段、域、信息元素可互换使用。在本公开实施例中，如果在需要执行多个操作时，如未特别说明，变换操作的执行顺序得到的实施例也是本公开保护的范围，在包含多个并列的判断条件时，变换判断条件的顺序得到的实施例也是本公开保护的范围。本公开实施例中所涉及的条件中的“和”“或”“和/或”“且”“并且”互换使用，得到的实施例也是本公开包含的范围。
下面，利用图4来说明作为一实施例的可执行本发明上面所详细描述的同步方法的用户设备。
图4是表示本发明所涉及的用户设备UE的框图。
如图4所示，该用户设备UE400包括处理器401和存储器402。处理器401例如可以包括微处理器、微控制器、嵌入式处理器等。存储器402例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器402上存储有程序指令。该指令在由处理器401运行时，可以执行本发明详细描述的由用户设备执行的上述方法。
以上，基于实施例对本发明所涉及的同步方法以及相应的用户设备进行了详细说明，该同步方法可以由用户设备执行。本发明并不限于同步方法以及相应的用户设备，只要能够实现本发明的主旨也可以通过其他方式实现。
上文已经结合优选实施例对本公开的方法和涉及的设备进行了描述。本领域技术人员可以理解，上面示出的方法仅是示例性的，而且以上说明的各实施例在不发生矛盾的情况下能够相互组合。本发明的方法并不局限于上面示出的步骤和顺序。
在本公开实施例中，在包含多个操作的情况下，本公开实施例示例性的列出了各操作执行顺序，改变各操作的执行顺序得到的实施例也是本公开保护范围。此外，在包含多个判断条件的情况下，该变各判断条件的执行顺序得到的实施例也是本公开保护范围。此外，在本公开中，如未特别说明，在一个实施例中定义的域的含义也可应用于其他实施例中涉及的相应域。此外，本公开实施例中“如果......”、“当.......”、“当.......时”、“在......时”、“满足......”或“满足......条件”可以替换为“在......的情况下”。本公开实施例中，将部分或全部条件中的“和”、“且”、“并且”替换为“或”得到的实施例也是本公开保护的范围；将部分或全部条件中的“或”替换为“和”得到的实施例也是本公开保护的范围
另外，上面示出的用户设备可以包括更多的模块，例如还可以包括可以开发的或者将来开发的可用于基站、MME、或UE的模块等等。上文中示出的各种标识仅是示例性的而不是限制性的，本公开并不局限于作为这些标识的示例的具体信元。本领域技术人员根据所示实施例的教导可以进行许多变化和修改。
应该理解，本公开的上述实施例可以通过软件、硬件或者软件和硬件两者的结合来实现。例如，上述实施例中的基站和用户设备内部的各种组件可以通过多种器件来实现，这些器件包括但不限于：模拟电路器件、数字电路器件、数字信号处理(DSP)电路、可编程处理器、专有集成电路(ASIC)、现场可编程门阵列(FPGA)、可编程逻辑器件(CPLD)，等等。
另外，运行在根据本发明的设备上的计算机可执行指令或者程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专有集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适当地组合不同实施例所发明的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种同步方法，包括：
    为每个同步PDU集群或PDU集关联一个同步定时器，所述定时器的值由基站通过RRC消息为UE配置或者由上层提供；
    所述UE通过维护所述同步定时器来实现多模式数据同步；
    在由基站配置所述同步定时器的值的情况下，所述基站为每组需要同步的数据流分别配置所述定时器的值，
    在由上层提供所述同步定时器的值的情况下，基站为所述UE配置指示标识，所述指示标识用于指示是否允许所述UE启动或运行所述同步定时器或是否支持PDU集间同步或多模式数据同步。
  2. 根据权利要求1所述的同步方法，其中，
    基于QoS流与DRB间的映射关系，所述同步定时器运行在SDAP层或者PDCP层或者RLC层。
  3. 根据权利要求2所述的同步方法，其中，
    在向下层提交一个PDCP PDU时，或者在接收到来自下层的PDCP PDU或PDCP SDU成功提交的指示时，或者在接收到来自下层的PDCP PDU或PDCP SDU已传输的指示时，或者在接收到来自下层的PDCP PDU或PDCP SDU传输成功的指示时，传输PDCP实体执行以下操作：
    如果UE或所述PDCP实体被配置了多模式数据同步和/或所述PDCP PDU属于一个同步PDU集群和/或所述PDCP PDU属于一个PDU集，则执行操作1-1至操作1-3的至少一项。
  4. 根据权利要求3所述的同步方法，其中，
    所述操作1-1：如果所述PDCP PDU或PDCP SDU所属同步PDU集群所关联的同步定时器未运行，或如果与所述PDCP PDU或PDCP SDU所属PDU集存在同步关系的PDU集所关联的同步定时器未运行，或如果所述PDCP PDU或PDCP SDU所属PDU集所关联的同步定时器未运行，则启动所述同步定时器；
    所述操作1-2：如果所述PDCP PDU或PDCP SDU是其所属PDU集的第一个PDCP PDU或PDCP SDU，和/或如果被配置了同步定时器，和/或所述PDCP PDU或PDCP SDU所属的同步PDU集群所关联的同步定时器未运行或与所述PDCP PDU或PDCP SDU所属PDU集存在同步关系的PDU集所关联的同步定时器未运行，和/或所述PDCP PDU或PDCP SDU所属PDU集所关联的同步定时器未运行，则：(1)如果所述PDCP PDU或PDCP SDU所属PDU集或同步PDU集群的同步定时器正在运行，则停止所述同步定时器，和/或(2)启动所述同步定时器，和/或(3)向上层指示所述提交信息，以便上层在接收到所述指示时启动所述PDU集或同步PDU集群所关联的定时器；
    所述操作1-3：如果所述PDCP PDU或PDCP SDU是其所属PDU集或所属同步PDU集群的最后一个被提交下层的PDCP PDU或PDCP SDU，或者如果所述PDCP PDU或PDCP SDU是其所属同步PDU集群的最后一个向下层提交PDCP PDU的PDU集中第一个被提交下层的PDCP PDU或PDCP SDU，或者如果所述PDCP PDU或PDCP SDU是其所属PDU集或所属同步PDU集群的最后一个被下层确认传输成功的PDCP PDU或PDCP SDU，则停止所述PDCP PDU或PDCP SDU所属PDU集或所属同步PDU集群所关联的同步定时器，或者向上层指示所述提交。
  5. 根据权利要求2所述的同步方法，其中，
    PDCP实体在接收到来自下层的PDU集或同步PDU集群的最后一个PDCP PDU或PDCP SDU的成功提交的指示或者传输指示，则停止所述PDU集或所述同步PDU集群所关联的同步定时器。
  6. 根据权利要求2所述的同步方法，其中，
    所述PDCP PDU或PDCP SDU成功提交的指示或者传输指示可以来自MAC或RLC层。
  7. 根据权利要求1所述的同步方法，其中，
    在一个PDCP SDU的丢弃定时器到期或低重要性丢弃定时器到期或同步定时器到期的情况下，传输PDCP实体执行以下操作的至少一项：
    操作2-1：如果被配置了pdu-SetDiscard，则：(1a)丢弃属于PDCP SDU所属PDU集的所有PDCP SDU以及相应的PDCP数据PDU，和/或(2a)如果被配置了interPdu-setDiscard或所述同步定时器到期，丢弃属于PDCP SDU所属同步PDU集群的所有PDCP SDU以及相应的PDCP数据PDU，和/或(3a)如果被配置了interPdu-setDiscard或如果所述PDCP SDU属于一个同步PDU集群或如果同步定时器到期，丢弃属于PDCP SDU所属同步PDU集群的所有PDCP SDU以及相应的PDCP数据PDU，和/或(4a)如果被配置了interPdu-setDiscard和/或如果所述PDCP SDU属于一个同步PDU集群，向上层指示所述丢弃，和/或(5a)如果被配置了interPdu-setDiscard和/或如果所述PDCP SDU属于一个同步PDU集群的PDU集或属于一个同步PDU集群和/或如果存在与所述PDCP SDU所属PDU集存在同步关系的PDU集，则停止所述PDCP SDU所属PDU集或所述同步PDU集群或与所述PDCP SDU所属PDU集存在同步关系的PDU集所关联的同步定时器；
    操作2-2：如果配置了interPdu-setDiscard和/或被配置了同步定时器和/或所述PDCP SDU属于一个PDU集或同步PDU集群和/或存在与所述PDCP SDU所属PDU集有同步关系的PDU集，则：(1b)丢弃属于PDCP SDU所属PDU集的所有PDCP SDU以及相应的PDCP数据PDU，和/或(2b)丢弃属于PDCP SDU所属同步PDU集群的所有PDCP SDU以及相应的PDCP数据PDU，和/或(3b)丢弃属于与所述PDCP SDU所属PDU集同步的PDU集的所有PDCP SDU以及相应的PDCP数据PDU，和/或(4b)向上层指示所述丢弃，和/或(5b)如果所述PDCP SDU属于一个同步PDU集群，丢弃属于PDCP SDU所属同步PDU集群的所有PDCP SDU以及相应的PDCP数据PDU，和/或(6b)如果所述PDCP SDU属于一个PDU集或同步PDU集群，向上层指示所述丢弃，和/或(7b)停止所述PDCP SDU所属PDU集或所述同步PDU集群或与所述PDCP SDU所属PDU集同步的其他PDU集所关联的同步定时器。
  8. 根据权利要求7所述的同步方法，其中，
    当接收到来自上层即SDAP的丢弃PDCP SDU的指示，传输PDCP执行以下操作：丢弃所述PDCP SDU以及相应的PDCP数据PDU，和/或如果配置了pdu-SetDiscard，丢弃属于PDCP SDU所属PDU集的所有PDCP SDU以及相应的PDCP数据PDU。
  9. 根据权利要求1所述的同步方法，其中，
    传输SDAP实体在接收到来自下层的SDAP PDU或SDU已提交的指示或已成功传输的指示，则执行以下至少一项：
    (1)如果所述SDAP PDU或SDU是其所属PDU集的第一个或最后一个SDAP PDU或SDU或者是其所属PDU集的第一个或最后一个被指示已提交或已成功传输的SDAP PDU或SDU，则启动所述SDAP PDU或SDU所属PDU集同步的PDU集所关联的同步定时器，或者启动所述SDAP PDU或SDU所属PDU集所关联的同步定时器，或者启动所述SDAP PDU或SDU所属同步PDU集群所关联的同步定时器；
    (2)如果所述SDAP PDU或SDU是其所属同步PDU集群中的最后一个PDU集中的第一个SDAP PDU或SDU，则停止与所述SDAP PDU或SDU所属PDU集同步的PDU集所关联的同步定时器，或者停止所述SDAP PDU或SDU所属PDU集所关联的同步定时器，或者停止所述SDAP PDU或SDU所属同步PDU集群所关联的同步定时器；
    (3)如果所述SDAP PDU或SDU是其所属PDU集的最后一个SDAP PDU或SDU，或者如果所述SDAP PDU或SDU是其所属PDU集的最后一个被指示已提交或已成功传输的SDAP PDU或SDU，或者如果所述SDAP PDU或SDU是其所属同步PDU集群的最后一个PDU集的第一个或最后一个被指示已提交或已成功传输的SDAP PDU或SDU，则停止所述SDAP PDU或SDU所属PDU集同步的PDU集所关联的同步定时器，或者停止所述SDAP PDU或SDU所属PDU集所关联的同步定时器，或者停止所述SDAP PDU或SDU所属同步PDU集群所关联的同步定时器。
  10. 一种用户设备UE，包括：
    处理器；以及
    存储器，存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求1～9中的任意一项所述的同步方法。
PCT/CN2025/111788 2024-08-02 2025-07-31 同步方法以及用户设备 Pending WO2026026909A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202411063045.3 2024-08-02
CN202411063045.3A CN121463179A (zh) 2024-08-02 2024-08-02 同步方法以及用户设备

Publications (1)

Publication Number Publication Date
WO2026026909A1 true WO2026026909A1 (zh) 2026-02-05

Family

ID=98578228

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/111788 Pending WO2026026909A1 (zh) 2024-08-02 2025-07-31 同步方法以及用户设备

Country Status (2)

Country Link
CN (1) CN121463179A (zh)
WO (1) WO2026026909A1 (zh)

Also Published As

Publication number Publication date
CN121463179A (zh) 2026-02-03

Similar Documents

Publication Publication Date Title
CN109246766B (zh) 无线配置方法和相应的用户设备
CN112312587A (zh) 用户设备及其执行的方法和基站及其执行的方法
CN116114373A (zh) 终端装置、基站装置以及方法
JP7761784B2 (ja) 通信方法、ユーザ装置、プロセッサ、プログラム、及び移動通信システム
CN116982394A (zh) 侧链路逻辑信道优先化
JP7668929B2 (ja) 通信方法、ユーザ装置、移動通信システム、チップセット、及びプログラム
CN113498220A (zh) 用户设备及其方法、基站及其方法
JP7636608B2 (ja) 通信方法、ユーザ装置、プログラム、及びプロセッサ
EP4572522A1 (en) Method executed by ue, and ue
CN115517006A (zh) 终端装置、方法以及集成电路
CN115517004A (zh) 终端装置、方法以及集成电路
US20250008603A1 (en) Method performed by user equipment, transmission method for base station, and user equipment
JP7802678B2 (ja) 端末装置、基地局装置、および、方法
JP7777081B2 (ja) 端末装置、基地局装置、および、方法
WO2023066188A1 (zh) 进行小区切换的方法及用户设备
CN121463179A (zh) 同步方法以及用户设备
CN116582897A (zh) 终端装置、方法以及集成电路
CN116158093A (zh) 终端装置、基站装置以及方法
WO2026032261A1 (zh) 用户设备及其方法
WO2026032262A1 (zh) 用户设备、基站及其方法
WO2026021427A1 (zh) 由用户设备执行的方法以及用户设备
JP7839098B2 (ja) 端末装置および方法
WO2024120476A1 (zh) 由用户设备执行的方法以及用户设备
CN110035455A (zh) 实现pdcp复制功能时的处理方法、装置、用户设备及基站
CN118175653A (zh) 恢复rrc连接的方法以及用户设备

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

Country of ref document: EP

Kind code of ref document: A1