WO2023036173A1 - 状态报告发送方法、无线承载重传执行方法及用户设备 - Google Patents
状态报告发送方法、无线承载重传执行方法及用户设备 Download PDFInfo
- Publication number
- WO2023036173A1 WO2023036173A1 PCT/CN2022/117521 CN2022117521W WO2023036173A1 WO 2023036173 A1 WO2023036173 A1 WO 2023036173A1 CN 2022117521 W CN2022117521 W CN 2022117521W WO 2023036173 A1 WO2023036173 A1 WO 2023036173A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- pdcp pdu
- pdcp
- rlc entity
- base station
- received
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 34
- 230000005540 biological transmission Effects 0.000 claims description 42
- 230000015654 memory Effects 0.000 claims description 13
- 230000004044 response Effects 0.000 claims description 4
- 230000001419 dependent effect Effects 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 7
- 230000011664 signaling Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 238000002716 delivery method Methods 0.000 description 3
- 230000007774 longterm Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000006731 degradation reaction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
Definitions
- the present disclosure relates to the technical field of wireless communication, and more specifically, the present disclosure relates to a method for sending a status report performed by a user equipment, a method for performing radio bearer retransmission performed by a base station, and the user equipment.
- Goal A 5G Multicast Broadcast Service Architecture Improvement
- 3rd Generation Partnership Project 3rd Generation Partnership Project: 3GPP
- RAN#86 plenary meeting Huawei proposed the work item of NR Multicast and Broadcast Service (NR MBS) (see non-patent literature: RP-193248 : New WID: NR Multicast and Broadcast Service) was approved. This work item is intended to provide support for Objective A in the RAN.
- This disclosure discusses related issues involved in the RAN achieving the above work objectives.
- the purpose of the present invention is to provide a solution capable of retransmitting radio bearers in time to reduce data loss.
- an aspect of the present invention provides a method of transmitting a status report performed by a user equipment, including: when a PDCP PDU is received via a specific RLC entity among a plurality of RLC entities, it is determined whether the currently received PDCP PDU is the first PDCP PDU received consecutively via the specific RLC entity configured to transmit the corresponding split radio bearer; and the currently received PDCP PDU is the first
- a PDCP status report is sent to the base station, and the PDCP status report includes information indicating whether the historical PDCP PDUs sent by the base station are correctly received by the user equipment.
- the separate radio bearer is a separate MBS radio bearer
- the specific RLC is a PTP RLC entity among multiple RLC entities configured to transmit the separate MBS radio bearer.
- the method further includes: before sending the PDCP status report to the base station, determining whether the detached radio bearer corresponding to the currently received PDCP PDU is configured with report sending indication information, and the report sending indication information is used to indicate sending the PDCP status report to the base station.
- sending the PDCP status report to the base station may include: when the currently received PDCP PDU is the first PDCP PDU, and the currently received PDCP PDU
- the detached radio bearer corresponding to the PDU is configured with report sending indication information
- the PDCP status report is sent to the base station.
- the report sending instruction information is configured for any of the following separate radio bearers: each separate radio bearer; the corresponding multiple RLC entities are configured with separate radio bearers with different response modes.
- the response mode indicates whether to respond to the base station mode (such as the AM mode and UM mode described in this specification); at least one of the corresponding RLC entities in the plurality of RLC entities is configured to send The base station responds to the separated radio bearer in the acknowledged mode; the corresponding PTP RLC entity among the plurality of RLC entities is configured as the separated radio bearer in the acknowledged mode.
- determining whether the currently received PDCP PDU is the first PDCP PDU received consecutively via the specific RLC entity comprises: determining that the currently received PDCP PDU is The first PDCP PDU successively received via the specific RLC entity, the timer is started or restarted upon receipt of the PDCP PDU via the specific RLC entity.
- the timer is stopped when any of the following conditions is met: a PDCP PDU is received via another RLC entity of the plurality of RLC entities that is different from the specific RLC entity type; via the A PDCP PDU is received by another RLC entity and a PDCP PDU is not received by the specific RLC entity within a predetermined period from when the PDCP PDU is received by the other RLC entity; receiving by the other RLC entity to PDCP PDU and no PDCP PDU is received via the specific RLC entity during the period until the PDCP PDU received via the other RLC entity reaches a predetermined number; handover information is received from the base station, the handover The information indicates switching from the first transmission mode corresponding to the certain RLC entity to the second transmission mode corresponding to the other RLC entity.
- the report sending indication information includes timer configuration information for the timer.
- a method for performing radio bearer retransmission performed by a base station including: determining whether there is a PDCP PDU that has not been successfully received by the user equipment according to a PDCP status report received from the user equipment, The PDCP status report is sent to the base station by the user equipment through the method of sending a status report as described above; and if there is a PDCP PDU that is not successfully received by the user equipment, send a message to the corresponding PTP PLC entity via the corresponding PTP PLC entity The user equipment retransmits the PDCP PDU.
- the method further includes: sending timer configuration information to the user equipment, where the timer configuration information is used to configure a timer for determining the first PDCP PDU.
- user equipment including: a processor; and a memory storing instructions, wherein the instructions execute the method for sending a status report as described above when executed by the processor.
- the radio bearer can be retransmitted in time to reduce data loss.
- FIG. 1 is a diagram showing an example of a PDCP status report format according to an embodiment of the present invention.
- Fig. 2 is a flowchart of a transmission method performed by a user equipment.
- FIG. 3 is a block diagram for explaining a user equipment according to an embodiment of the present invention.
- Fig. 4 is a flowchart of an example of a method for sending a status report according to an embodiment of the present invention.
- Fig. 5 is a flowchart of another example of a method for sending a status report according to an embodiment of the present invention.
- FIG. 6 is a diagram for explaining an example of a switching procedure from the PTM transfer mode to the PTP transfer mode.
- FIG. 7 is a block diagram of a user equipment according to an embodiment of the present invention.
- Fig. 8 is a schematic diagram of the parameters involved in the illustration.
- UE User Equipment, user equipment.
- RRC Radio Resource Control, radio resource control.
- RRC_CONNECTED RRC connected state.
- RRC_INACTIVE RRC is inactive.
- RRC_IDLE RRC idle state.
- RAN Radio Access Network, wireless access network.
- New RAT new radio access technology.
- MBMS Multimedia Broadcast/Multicast Service, multimedia broadcast multicast service.
- MBS Multicast Broadcast Services, multicast broadcast service.
- PDCP Packet Data Convergence Protocol, packet data convergence protocol.
- FIG. 1 shows an example of the format of a PDCP status report (PDCP Status Report).
- D/C occupies 1 bit and is used to indicate whether the corresponding PDCP PDU is a PDCP data PDU or a PDCP control PDU; the PDU type (PDU Type) occupies 3 bits and is used to indicate the corresponding PDCP control PDU.
- FMC First Missing COUNT
- COUNT represents the number of PDU
- COUNT is composed of HFN and PDCP serial number PDCP SN, as shown in Figure 8
- the field indicates the COUNT value of the first lost PDCP SDU in the reordering window (that is, RX_DELIV);
- bitmap Bitmap
- Table 1 gives an example of the meaning of each bit value, where the bit position of the Nth bit in the bitmap is (bit position of N th bit in the Bitmap is N); R occupies 1 bit, which is a reserved bit, and the reserved bit will be ignored by the receiving end.
- RLC Radio Link Control, wireless link control.
- the RLC can be an RLC in an acknowledged mode (Acknowledged Mode, AM), that is, AM RLC, or an RLC in an unacknowledged mode (Unacknowledged Mode, UM), that is, UM RLC, or a transparent mode (Transparent Mode).
- AM Acknowledged Mode
- UM unacknowledged Mode
- TM transparent Mode
- a UM RLC entity is configured as a transmitting UM RLC entity or as a receiving UM RLC entity, and submits or receives RLC data PDUs.
- the AM RLC entity includes a transmitting end and a receiving end, and submits or receives RLC data PDUs and RLC control PDUs.
- the RLC entity submits or receives RLC data PDU and RLC control PDU (i.e. status PDU), and the receiving end of the AM RLC entity uses the status PDU to inform the peer RLC entity (i.e. the sending end of another AM RLC entity) about Its successfully received RLC data PDUs and RLC data PDUs detected as lost.
- RLC data PDU and RLC control PDU i.e. status PDU
- SDU Service Data Unit, service data unit.
- SDU Service Data Unit
- PDU Protocol Data Unit, protocol data unit.
- the data packets received or delivered by this layer from the lower layer are called PDUs.
- a PDCP data PDU is a data packet obtained by adding a PDCP header to a PDCP SDU.
- RB Radio Bearer, radio bearer.
- MRB MBS radio bearer, that is, a radio bearer that is configured for MBS multicast/broadcast transmission (A radio bearer that is configured for MBS multicast/broadcast delivery).
- the MBS-MCCH Multicast Control Channel, multicast control channel.
- the MBS-MCCH is used to transmit control information related to receiving MBS services.
- SC-MCCH Single Cell Multicast Control Channel, single cell multicast control channel.
- TMGI Temporary Mobile Group Identity, temporary mobile group identity.
- PLMN Public Land Mobile Network, public land mobile network.
- RNTI Radio Network Temporary Identifier, wireless network temporary identifier.
- PTM Point to Multipoint, point to multipoint, a delivery method of MBS business.
- the RAN node delivers a single copy of MBS data packets over radio to a set of UEs via radio (a RAN node delivers a single copy of MBS data packets over radio to a set of UEs).
- PTP Point to Point, point to point, a delivery method of MBS business.
- the RAN node delivers copies of multiple MBS data packets to each UE via radio (a RAN node delivers separate copies of MBS data packet over radio to individual UE).
- LTE SC-PTM LTE Single Cell Point to Multipoint, long term evolution single cell point to multipoint.
- MBS multicast or multicast communication service means that the same service and the same specific content are simultaneously provided to a group of specific UEs.
- a multicast traffic is delivered to the UE using the multicast session.
- a UE in RRC_CONNECTED can use PTP and/or PTM to receive a multicast communication service.
- G-RNTI Group RNTI, group RNTI, used to scramble the scheduling and transmission of MTCH (used to scramble the scheduling and transmission of MTCH).
- NR MBS supports 1-1 mapping between G-RNTI and MBS session (One-to-one mapping between G-RNTI and MBS session is supported in NR MBS).
- network can be used interchangeably, and the network can be a long-term evolution LTE network, an NR network, an enhanced long-term evolution eLTE network, or other networks defined in subsequent evolution versions of 3GPP.
- the base station broadcasts the MBMS service and its scheduling information supported by the system information and the message transmitted on the SC-MCCH channel.
- the radio bearer configuration information used to transmit the MBMS service is predefined .
- the UE can know the MBMS service that the current cell or base station supports or is in progress by receiving the corresponding system information and the message transmitted on the SC-MCCH.
- the UE needs to receive a certain MBMS service, it establishes a radio bearer according to predefined parameters and receives data. In this case, UE can receive MBMS service without establishing RRC connection.
- MBS MBS services
- some MBS services can also be scheduled in a manner similar to SC-PTM, so that UEs in the RRC idle state and RRC inactive state can also receive the MBS services.
- MBS services there are another part of MBS services that require the UE to establish an RRC connection with the base station, and then the base station configures for the UE through dedicated RRC signaling (also called a dedicated RRC message), and the radio bearer for receiving these MBS services can also be configured by the base station through dedicated RRC signaling.
- the order is UE configuration.
- FIG. 2 is a block diagram representing such a transmission method performed by a user equipment.
- the UE establishes an RRC connection with the base station, and in S102, the base station configures a radio bearer for the UE to receive the MBS service through an RRC message.
- the radio bearer may be an MRB configured with only PTM transmission (as shown in (a) of Figure 3), or a separate MRB (split MRB) configured with PTM and PTP at the same time (as shown in (b) of Figure 3) Or only MRBs for PTP transmission are configured (as shown in (c) of FIG. 3 ). It should be noted that (a)-(c) of FIG. 3 only show the PDCP entity and RLC entity corresponding to the bearer and the relationship between them.
- the base station can dynamically decide whether to use PTM or PTP to transmit the MBS session (or PDCP PDU). For example, when the quality of the link corresponding to PTM deteriorates or cannot meet the quality of service (QoS) of the MBS session, the base station can use PTP transmission (that is, the base station submits the PDCP PDU to the PTP RLC entity). For an MRB configured with only PTM transmission, the base station reconfigures the MRB as an MRB with PTP transmission through RRC signaling.
- the base station dynamically decides to use PTM transmission or PTP transmission and does not explicitly indicate to the UE, that is, when the base station enables PTP or PTM transmission, it directly transmits data without sending an indication to the UE .
- the base station uses PTP for transmission.
- the base station will retransmit some PDCP PDUs through PTP (or PTP RLC entity) to reduce data loss, and these PDCP PDUs have been submitted to PTM (or PTM RLC entity).
- PTP or PTP RLC entity
- the present disclosure provides the following embodiments to solve the above-mentioned problems.
- FIG. 4 is a flow chart of + examples of a method of sending a status report according to an embodiment of the present invention.
- the user equipment receives PDCP PDUs via multiple RLC entities.
- the multiple RLC entities may be, for example, the RLC entities for the split MRB in (b) of FIG. 3 , namely, the PTM RLC entity and the PTP RLC entity.
- a split radio bearer may be a split MBS radio bearer.
- the multiple RLC entities for example, one PTM RLC entity and one PTP RLC entity may be included. In other examples, the number of PTM RLC entities and PTP RLC entities can be arbitrary.
- the user equipment Upon receiving the PDCP PDU, the user equipment determines at S204 whether the received PDCP PDU is a PDCP PDU received via a specific RLC entity.
- the specific RLC entity may be a PTP RLC entity among a plurality of RLC entities configured to transport the split MBS radio bearer.
- the PDCP PDU is received via a specific RLC entity, that is, if a PDCP PDU is received via a specific RLC entity, then at S206, determine whether the currently received PDCP PDU is the first one received continuously via a specific RLC entity PDCP PDUs.
- the user equipment sends a PDCP status report to the base station.
- the PDCP status report includes information indicating whether the historical PDCP PDUs sent by the base station are correctly received by the user equipment.
- the base station receives the PDCP status report, it can determine whether there is a PDCP PDU that has not been correctly received by the user equipment according to the PDCP status report. If there is a PDCP PDU that is not correctly received by the user equipment, retransmission may be initiated for the PDCP PDU. That is, retransmit the PDCP PDU to the user equipment.
- the timer may be started or restarted upon receipt of a PDCP PDU via a specific RLC entity. If the timer is not running when a PDCP PDU is received via a specific RLC entity, it can be determined that the currently received PDCP PDU is the first PDCP PDU successively received via the specific RLC entity. At this point, start the timer.
- the timer can be restarted.
- the base station maintains the state of transmitting radio bearers through a specific RLC entity
- the user equipment will continuously receive PDCP PDUs via the specific RLC entity, and then receive the first PDCP PDU via the specific RLC entity Afterwards, when the PDCP PDU is received via the specific RLC entity again, the timer is in the running state, so that it can be determined that the currently received PDCP PDU is not the first PDCP PDU continuously received via the specific RLC entity.
- the value of the timer can be appropriately set according to actual needs, which is not particularly limited in the present invention.
- the base station may send a configuration message for the timer to the user equipment through an RRC message, and the base station may set the timer according to the configuration message.
- the timer may be stopped if the user equipment considers that the base station has switched from a first transmission mode corresponding to a specific RLC entity to another transmission mode different from the first transmission mode, wherein the other transmission mode corresponds to Another RLC entity whose corresponding transmission mode is different from the specific RLC entity.
- the base station switches to the first transmission mode again, when the user equipment receives a PDCP PDU via a specific RLC entity corresponding to the first transmission mode, if the timer is not in the running state, it can be determined that this The PDCP PDU received at this time is the first PDCP PDU received consecutively via this particular RLC entity.
- the so-called base station switching transmission mode means that the base station switches the RLC entity used for data transmission.
- RLC entities exist on the base station side and the user equipment side correspondingly.
- the base station side includes a PTP RLC entity and a PTM RLC entity
- the user equipment side also correspondingly has a PTP RLC entity and a PTM RLC entity corresponding to the PTP RLC entity and the PTM RLC entity on the base station side.
- the PTP RLC entity (or PTM RLC entity) on the base station side and the PTP RLC entity (or PTM RLC entity) on the UE side are called peer RLC entities.
- the base station decides to transmit data through the PTP mode
- the data is sent to the user equipment side via the PTP RLC entity on the base station side, and the user equipment receives data through its PTP RLC entity accordingly.
- the base station switches the transmission mode, for example, the base station switches from the PTP mode to the PTM mode
- the base station side switches from the PTP RLC entity to the PTM RLC entity
- the user equipment side also switches to receive data through the corresponding PTM RLC entity.
- the user equipment may determine whether the base station has switched the transmission mode according to a certain strategy. The user equipment may consider that the base station has switched the transmission mode when any of the following conditions is met, and the timer may be stopped at this time: to PDCP PDU; a PDCP PDU is received via another RLC entity and a PDCP PDU is not received via a specific RLC entity within a predetermined period from when a PDCP PDU is received via another RLC entity (the base station may configure the UE via an RRC message the predetermined period); a PDCP PDU is received via another RLC entity and no PDCP PDU is received via a specific RLC entity during the period until the PDCP PDU received via another RLC entity reaches a predetermined number; received from the base station Referring to switching information, the switching information indicates switching from a first transmission mode corresponding to a certain RLC entity to a
- Fig. 5 is a flowchart of another example of a method for sending a status report according to an embodiment of the present invention.
- the operation of S302 is the same as that of S202, and the operation of S304 may be the same as that of S304.
- the operation of S308 is the same as that of S206, and the operation of S310 is the same as that of S208. Therefore, descriptions of these operations are not repeated.
- the user equipment may determine in S306 whether the detached radio bearer corresponding to the currently received PDCP PDU is configured with report sending indication information.
- the report sending indication information is used to instruct to send the PDCP status report to the base station, and can be configured by the base station.
- the base station may configure report sending indication information for each separate radio bearer.
- the report sending indication information may also be configured only for the separated radio bearers meeting the requirements.
- the report sending indication information may include timer configuration information for the timer.
- the case where the report sending instruction information is the timer configuration information for the timer is taken as an example to describe which separate radio bearer the report sending instruction information is configured for.
- the detached radio bearer corresponding to the currently received PDCP PDU is configured with report sending indication information, further perform operations of S308 and S310.
- the operation of S306 may also be performed after the operation of S308.
- the received PDCP PDU described in the embodiment of the present disclosure may also be replaced by the received PDCP SDU. It may be further defined that the received PDCP PDU is a PDCP data PDU.
- a split radio bearer is configured with a first RLC entity and a second RLC entity.
- the PDCP entity corresponding to the separated radio bearer receives the PDCP PDU from the lower layer (that is, the RLC entity), and if the PDCP PDU (or the PDCP SDU corresponding to the PDCP PDU) is received from the first RLC entity, perform the following operations:
- restarting the timer may also be described as starting the timer.
- the value of the timer is configured for the UE by the base station through RRC signaling. If the value of the timer is configured by the base station, it may also be stipulated that only the separated radio bearer configured with the timer can execute this embodiment. Furthermore, it may also be stipulated whether the corresponding radio bearer or PDCP entity is configured with the information element statusReportRequired, and only when statusReportRequired is configured or its value is true, this embodiment is executed. Wherein, statusReportRequired is included in the RRC message sent by the base station to the UE (may be included in the RRC message configuring the first timer), and is used to indicate whether the corresponding radio bearer is configured to send a PDCP status report on the uplink.
- the timer is stopped.
- the parameters of the RLC entity corresponding to the PDCP entity will be reset, and the timer can be stopped at this time.
- the timer is stopped.
- the base station may configure the timer for each separate radio bearer.
- the base station may also configure the timer only for separate radio bearers configured with different modes for the associated first RLC entity and the second RLC entity, for example, the mode of the first RLC entity is UM, and the mode of the second RLC entity is UM.
- the mode is AM, that is, the first RLC entity is a UM RLC entity, and the second RLC entity is an AM RLC entity.
- the base station may also only configure the timer for the detached radio bearer associated with at least one AM RLC entity.
- AM RLC is usually configured for services with high QoS requirements. For such services, when the transmission of the first RLC entity cannot meet the QoS requirements, the base station will enable the second RLC entity. In order to avoid data loss, it is necessary to trigger the UE to send PDCP Status reporting, so that the base station can retransmit those PDCP PDUs or SDUs that have been sent but have not been correctly received by the UE.
- the base station configures a separate MRB for the UE through RRC signaling, and the separate MRB is associated with two RLC entities, one of which is a PTM RLC entity and the other is a PTP RLC entity.
- a timer (or a value of the timer) is configured for the corresponding detached MRB in the RRC signaling.
- the PDCP entity separating the MRB receives the PDCP PDU from the lower layer entity (ie, the RLC entity), and when the PDCP PDU (or the PDCP SDU corresponding to the PDCP PDU) is received from the PTP RLC entity, the following operations are performed:
- the PDCP PDUs used to transmit separate MRBs include PDCP PDU No. 1 to PDCP PDU No. N, where N is a positive integer.
- the base station transmits PDCP PDU No. 1 through PTM transmission, but when transmitting PDCP PDU No. 2, it detects QoS degradation, which may affect data loss, so the base station can decide to switch to PTP mode to transmit PDCP PDU No. 2.
- the user equipment receives PDCP PDU No. 2 via PTP RLC. When the user equipment receives the No. 2 PDCP PDU, since the No.
- the user equipment can perform the operations of this embodiment to send the PDCP status report to the base station.
- the status report may include information indicating whether each PDCP PDU sent by the base station has been successfully received so far. For example, if the user equipment has not received the No. 1 PDCP PDU, the PDCP status report may include information indicating that the No. 1 PDCP PDU has not been received.
- the base station After receiving the PDCP status report, the base station can retransmit the No. 1 PDCP PDU through PTP transmission.
- the timer is configured only when the two RLC entities associated with the separated MRB are used for PTM transmission and PTP transmission respectively.
- the detached MRB is configured by upper layers to send a PDCP status report in the uplink (configured by upper layers to send a PDCP status report in the uplink), and the receiving PDCP entity triggers a PDCP status report when the following conditions are met: a PDCP PDU from a PTP RLC entity is received ( or the PDCP SDU corresponding to the PDCP PDU) and the timer is not running.
- the PDCP entity can judge whether it is configured by the upper layer to send a PDCP status report through the information element statusReportRequired.
- statusReportRequired is included in the RRC message sent by the base station to the UE (may be included in the RRC message configuring the first timer), used to indicate the corresponding radio Whether the bearer is configured to send PDCP status reports on the uplink.
- RCVD_COUNT is the COUNT of the received PDCP data PDU, that is, [RCVD_HFN, RCVD_SN]; where, RCVD_HFN and RCVD_SN are the parameters of the two fields of RCVD_COUNT.
- RCVD_SN is the PDCP SN of the received PDCP data PDU
- the PDCP SN is included in the PDU header of the PDU (PDCP SN of the received PDCP Data PDU, included in the PDU header)
- RCVD_HFN is the received PDCP data PDU
- the HFN is calculated by the receiving PDCP entity (the HFN of the received PDCP Data PDU, calculated by the receiving PDCP entity).
- the PTM RLC entity is also referred to as the RLC entity associated with PTM or the RLC entity configured with G-RNTI or the RLC entity associated with G-RNTI or the RLC entity used for PTM transmission;
- the PTP RLC entity is also referred to as PTP The associated RLC entity or the RLC entity used for PTP transport.
- an MBS service (or MBS session) can be identified by an MBS identifier, and the MBS identifier can be a TMGI and/or a session identifier sessionId, where the TMGI can include a PLMN identifier and/or a service identifier, so The above service identifier uniquely identifies an MBS service within a PLMN.
- Fig. 7 is a brief structural block diagram of a user equipment UE involved in the present disclosure.
- the user equipment user equipment 700 includes a processor 701 and a memory 702 .
- the processor 701 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
- the memory 702 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memories.
- Memory 702 has program instructions stored thereon. When the instructions are executed by the processor 701, the above method described in detail in this disclosure and executed by the user equipment may be executed.
- computer-executable instructions or programs running on the device according to the present disclosure may be programs that cause a computer to realize the functions of the embodiments of the present disclosure by controlling a central processing unit (CPU).
- the program or information processed by the program may 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 disclosure can be recorded on computer-readable storage media.
- the corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs.
- the so-called “computer system” here may be a computer system embedded in the device, which 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 that dynamically stores a program for a short period of 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 may include general-purpose processors, digital signal processors (DSPs), application-specific 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.
- DSPs digital signal processors
- ASICs application-specific integrated circuits
- FPGAs field-programmable gate arrays
- a general-purpose processor can be a microprocessor, or it can be any existing processor, controller, microcontroller, or state machine.
- the above-mentioned circuits may be digital circuits or analog circuits. Where new integrated circuit technologies have emerged to replace existing integrated circuits due to advances in semiconductor technology, one or more embodiments of the present disclosure may also be implemented using these new integrated circuit technologies.
- present disclosure is not limited to the above-described embodiments. Although various examples of the embodiments have been described, the present disclosure 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 conditioners, office equipment, vending machines, and other household appliances.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本发明提供由用户设备执行的状态报告发送方法、由基站执行的无线承载重传执行方法及用户设备。由用户设备执行的发送状态报告的方法包括:在经由多个RLC实体中的特定RLC实体而接收到PDCP PDU时,确定当前接收到的PDCP PDU是否是经由所述特定RLC实体而连续接收到的第一个PDCP PDU,所述多个RLC实体被配置为用于传输对应的分离无线承载;以及在当前接收到的PDCP PDU是所述第一个PDCP PDU的情况下,向基站发送PDCP状态报告,所述PDCP状态报告包括表示当前所述基站已发送的历史PDCP PDU是否被所述用户设备正确接收的信息。
Description
本公开涉及无线通信技术领域,更具体地,本公开涉及由用户设备执行的发送状态报告的方法、由基站执行的执行无线承载重传的方法以及用户设备。
一项关于5G组播广播服务架构改进的研究项目SI(具体见SP-190625)已获得批准,并正在进行中。此SI的目标之一(称为目标A)是在5GS中支持通用MBS服务,已经确定的可以受益于此特性的用例包括(但不限于)公共安全、V2X应用,透明IPv4/IPv6组播传输,IPTV,无线软件传输,群组通信和物联网应用。相应的,在第三代合作伙伴计划(3rd Generation Partnership Project:3GPP)RAN#86次全会上,华为提出了NR多播和广播服务(NR MBS)的工作项目(参见非专利文献:RP-193248:New WID:NR Multicast and Broadcast Service)获得批准。该工作项目旨在RAN中提供对目标A的支持。
本公开讨论RAN达成上述工作目标所涉及的相关问题。
发明内容
本发明的目的在于提供一种能够及时对无线承载进行重传,以减少数据丢失的方案。
为了解决上述问题,本发明的一个方面提供了由用户设备执行的发送状态报告的方法,包括:在经由多个RLC实体中的特定RLC实体而接收到PDCP PDU时确定当前接收到的PDCP PDU是否是经由所述特定RLC实体而连续接收到的第一个PDCP PDU,所述多个RLC实体被配置为用于传输对应的分离无线承载;以及在当前接收到的PDCP PDU是所述第一个PDCP PDU的情况下,向基站发送PDCP状态报告,所述PDCP状态报告包括表示所述基站已发送的历史PDCP PDU是否被所述用户设备正确接收的信息。
可选地,所述分离无线承载为分离MBS无线承载,所述特定RLC是 被配置为用于传输所述分离MBS无线承载的多个RLC实体中的PTP RLC实体。
可选地,所述方法还包括:在向基站发送PDCP状态报告之前,确定当前接收到的PDCP PDU所对应的分离无线承载是否被配置了报告发送指示信息,所述报告发送指示信息用于指示向所述基站发送所述PDCP状态报告。在当前接收到的PDCP PDU是所述第一个PDCP PDU的情况下,向基站发送PDCP状态报告可以包括:在当前接收到的PDCP PDU是所述第一个PDCP PDU,并且当前接收到的PDCP PDU所对应的分离无线承载被配置了报告发送指示信息的情况下,向基站发送PDCP状态报告。
可选地,所述报告发送指示信息针对以下中的任一种分离无线承载而配置:每个分离无线承载;所对应的所述多个RLC实体被配置了不同的响应模式的分离无线承载而配置,所述响应模式指示是否向所述基站作出响应的模式(例如本说明书中所述的AM模式和UM模式);所对应的所述多个RLC实体中的至少一个RLC实体被配置为向所述基站作出响应的确认模式的分离无线承载;所对应的多个RLC实体中的PTP RLC实体被配置为确认模式的分离无线承载而被配置。
可选地,确定当前接收到的PDCP PDU是否是经由所述特定RLC实体而连续接收到的第一个PDCP PDU包括:在定时器不处于运行状态的情况下,确定当前接收到的PDCP PDU是经由所述特定RLC实体而连续接收到的第一个PDCP PDU,所述定时器在经由所述特定RLC实体而接收到所述PDCP PDU时被启动或被重启。
可选地,所述定时器在满足以下中的任一条件时被停止:经由所述多个RLC实体中与所述特定RLC实体不同类型的另一RLC实体而接收到PDCP PDU;经由所述另一RLC实体而接收到PDCP PDU并且从经由所述另一RLC实体而接收到PDCP PDU时起的预定期间内未经由所述特定RLC实体接收到PDCP PDU;经由所述另一RLC实体而接收到PDCP PDU并且从直到经由所述另一RLC实体而接收到的PDCP PDU达到预定数量为止的期间内未经由所述特定RLC实体接收到PDCP PDU;从所述基站接收到切换信息,所述切换信息表示从与所述某RLC实体对应的第一传输模式切换到与所述另一RLC实体对应的第二传输模式。
可选地,所述报告发送指示信息包括针对所述定时器的定时器配置信息。
根据本发明的另一方面,还提供由基站执行的执行无线承载重传的方法,包括:根据从用户设备接收到的PDCP状态报告,确定是否存在未成功被所述用户设备接收的PDCP PDU,所述PDCP状态报告由所述用户设备通过如上所述的发送状态报告的方法而发送给所述基站;以及如果存在未成功被所述用户设备接收的PDCP PDU,则经由对应的PTP PLC实体向所述用户设备重新传输该PDCP PDU。
可选地,该方法还包括:向所述用户设备发送定时器配置信息,所述定时器配置信息用于配置用于确定所述第一个PDCP PDU的定时器。
根据本发明的另一方面,还提供用户设备,包括:处理器;以及存储器,存储有指令,其中,所述指令在由所述处理器运行时执行如上所述的发送状态报告的方法。
发明效果
根据本发明,能够及时对无线承载进行重传,以减少数据丢失。
通过下文结合附图的详细描述,本公开的上述和其它特征将会变得更加明显,其中:
图1是示出本发明的实施例涉及的PDCP状态报告格式的一个示例的图。
图2是由用户设备执行的传输方法的流程图。
图3是用于说明根据本发明的实施例的用户设备的框图。
图4是根据本发明的实施例的发送状态报告的方法的一个示例的流程图。
图5是根据本发明的实施例的发送状态报告的方法的另一示例的流程图。
图6是用于说明从PTM传输模式向PTP传输模式的切换过程的一个示例的图。
图7是根据本发明的实施例的用户设备的框图。
图8是用于说明中所涉及的参数的示意图。
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意,本公开不应局限于下文所述的具体实施方式。另外,为了简便起见,省略了对与本公开没有直接关联的公知技术的详细描述,以防止对本公开的理解造成混淆。
下面描述本公开涉及的部分术语,术语的具体含义可参见3GPP最新相关文档,例如TS38.300、TS38.321、TS38.323、TS38.331等。此外,本公开实施例不限于广播/组播业务,也可以应用于其他应用场景。
UE:User Equipment,用户设备。
RRC:Radio Resource Control,无线资源控制。
RRC_CONNECTED:RRC连接态。
RRC_INACTIVE:RRC非激活态。
RRC_IDLE:RRC空闲态。
RAN:Radio Access Network,无线接入网。
NR:New RAT,新无线访问技术。
MBMS:Multimedia Broadcast/Multicast Service,多媒体广播多播业务。
MBS:Multicast Broadcast Services,多播广播业务。
PDCP:Packet Data Convergence Protocol,分组数据汇聚协议。
图1示出了PDCP状态报告(PDCP Status Report)格式的一种示例。如图1所示,D/C占1比特,用于指示对应的PDCP PDU是PDCP数据PDU还是PDCP控制PDU;PDU类型(PDU Type)占3比特,用于指示包含在对应PDCP控制PDU中的控制信息的类型;FMC(First Missing COUNT)占32比特,用于指示第一个丢失的COUNT(COUNT表示PDU的编号,COUNT由HFN和PDCP序列号PDCP SN组成,如图8所示),这个域指示重排序窗中第一个丢失的PDCP SDU的COUNT值(即RX_DELIV);位图(Bitmap)长度可变,用于指示在接收PDCP实体中,哪些SDU丢失以及哪些SDU已正确接收(indicates which SDUs are missing and which SDUs are correctly received in the receiving PDCP entity),表1中给出了每个比特取值含义的示 例,其中在位图中第N个比特的比特位置是(bit position of N
th bit in the Bitmap is N);R占1个比特,是保留比特,保留比特将被接收端忽略。
表1
比特 | 含义 |
0 | COUNT=(FMC+比特位)模2 32的PDCP SDU丢失 |
1 | COUNT=(FMC+比特位)模2 32的PDCP SDU正确接收 |
RLC:Radio Link Control,无线链路控制。
作为一种示例,RLC可以是确认模式(Acknowledged Mode,AM)的RLC,即AM RLC,也可以是非确认模式(Unacknowledged Mode,UM)的RLC,即UM RLC,还可以是透传模式(Transparent Mode,TM)的RLC,即TM RLC。UM RLC实体被配置为传输UM RLC实体或接收UM RLC实体,并提交或接收RLC数据PDU。AM RLC实体包括传输端和接收端,并提交或接收RLC数据PDU和RLC控制PDU。在AM模式下,RLC实体提交或接收RLC数据PDU和RLC控制PDU(即状态PDU),所述AM RLC实体接收端采用状态PDU通知对等RLC实体(即另一个AM RLC实体的发送端)关于其成功接收的RLC数据PDU和检测为丢失的RLC数据PDU。
SDU:Service Data Unit,服务数据单元。本层从上层接收或递交上层的数据包称为SDU。
PDU:Protocol Data Unit,协议数据单元。本层从下层接收或递交下层的数据包称为PDU。例如,PDCP数据PDU是PDCP SDU增加PDCP报头后得到的数据包。
RB:Radio Bearer,无线承载。
MRB:MBS无线承载,即一个配置用于MBS多播/广播传输的无线承载(A radio bearer that is configured for MBS multicast/broadcast delivery)。
MCCH:Multicast Control Channel,多播控制信道。MBS-MCCH用于传输与接收MBS服务相关的控制信息。
SC-MCCH:Single Cell Multicast Control Channel,单小区多播控制信道。
TMGI:Temporary Mobile Group Identity,临时移动组标识。
PLMN:Public Land Mobile Network,公众陆地移动网。
RNTI:Radio Network Temporary Identifier,无线网络临时标识。
PTM:Point to Multipoint,点到多点,一种MBS业务的递送(deliver)方式。在PTM递送方式中,RAN节点将一份MBS数据包通过无线电递送给一组UE(a RAN node delivers a single copy of MBS data packets over radio to a set of UEs)。
PTP:Point to Point,点到点,一种MBS业务的递送方式。在PTP递送方式中,RAN节点将多个MBS数据包的副本通过无线电分别递送给每个UE(a RAN node delivers separate copies of MBS data packet over radio to individual UE)。
LTE SC-PTM:LTE Single Cell Point to Multipoint,长期演进单小区点到多点。
MTCH:Multicast Traffic Channel,多播业务信道。MBS组播(或组播通信业务)是指相同的服务和相同的特定内容被同时提供给一组特定的UE。使用组播会话将一个组播通信业务递送给UE。
一个处于RRC_CONNECTED的UE可以采用PTP和/或PTM来接收一个组播通信业务。
G-RNTI:Group RNTI,群组RNTI,用于加扰MTCH的调度和传输(used to scramble the scheduling and transmission of MTCH)。NR MBS支持G-RNTI和MBS会话之间1-1映射关系(One-to-one mapping between G-RNTI and MBS session is supported in NR MBS)。
本公开中,网络、基站和RAN可互换使用,所述网络可以是长期演进LTE网络、NR网络、增强的长期演进eLTE网络,也可以是3GPP后续演进版本中定义的其他网络。
在LTE SC-PTM中,基站通过***信息及SC-MCCH信道上传输的消息广播其支持的多媒体广播多播服务MBMS业务及其调度信息,用于传输MBMS业务的无线承载配置信息是预定义的。UE通过接收对应的***信息和SC-MCCH上传输的消息就可以知道当前小区或基站支持或正在进行的MBMS业务。当UE需要接收某个MBMS业务时,按照预定义的参数建立 无线承载并接收数据。在这种情况下,UE不需要建立RRC连接就可以接收MBMS业务。
在NR MBS中,一部分MBS业务(service)也可采用与SC-PTM类似的方式调度,使得处于RRC空闲态和RRC非激活态的UE也可以接收所述MBS业务。但是,还存在另一部分MBS业务需要UE与基站建立RRC连接,然后基站通过专用RRC信令(也称为专用RRC消息)为UE配置,并且接收这些MBS业务的无线承载也可由基站通过专用RRC信令为UE配置。图2为表示这种用户设备执行的传输方法的框图。其中S101为UE与基站建立RRC连接,S102为基站通过RRC消息为UE配置接收MBS业务的无线承载。所述无线承载可以是仅配置了PTM传输的MRB(如图3的(a)所示),或同时配置了PTM和PTP的分离MRB(split MRB)(如图3的(b)所示)或者仅配置了PTP传输的MRB(如图3的(c)所示)。需要说明的是,图3的(a)-(c)仅示出了承载对应的PDCP实体和RLC实体以及两者间的关系。在下行方向上,经PDCP实体封装(即增加PDCP报头)后的PDCP PDU递交给RLC实体。对于分离MRB,基站可以动态的决定采用PTM还是PTP传输MBS会话(或PDCP PDU)。例如,当PTM对应的链路质量变差或不能满足MBS会话的服务质量(QoS)时,基站可以采用PTP方式传输(即基站将PDCP PDU递交给PTP RLC实体)。对于仅配置了PTM传输的MRB,基站通过RRC信令将所述MRB重配置为具有PTP传输的MRB。对于同时配置了PTM传输和PTP传输的分离MRB,基站动态决定采用PTM传输或PTP传输并且不显式的向UE指示,即当基站启用PTP或PTM传输时,直接传输数据而不向UE发送指示。在这种情况下,当PTM对应的链路质量变差时,基站采用PTP传输。但是为了满足对于MBS业务的QoS要求,基站将通过PTP(或PTP RLC实体)重传部分PDCP PDU以减少数据丢失,这些PDCP PDU已经递交给PTM(或PTM RLC实体)。UE如何触发PDCP状态报告以使得基站确定应该在PTP上重传哪些PDCP PDU是需要解决的问题。
本公开提供以下实施例解决上述问题。
以下结合附图来对本发明进行详细说明。
图4是根据本发明的实施例的发送状态报告的方法的+个示例的流程图。
如图4所示,在S202,用户设备经由多个RLC实体而接收PDCP PDU。多个RLC实体例如可以是图3的(b)中的针对分离MRB的RLC实体,即PTM RLC实体和PTP RLC实体。分离无线承载可以是分离MBS无线承载。此时,在多个RLC实体中,例如可以包括一个PTM RLC实体和一个PTP RLC实体。在其它示例中,PTM RLC实体和PTP RLC实体的数量可以是任意的。
在接收到PDCP PDU时,用户设备在S204,确定所接收到的PDCP PDU是否是经由特定RLC实体而接收到的PDCP PDU。
在一个示例中,在分离无线承载是分离MBS无线承载的情况下,特定RLC实体可以是被配置为用于传输分离MBS无线承载的多个RLC实体中的PTP RLC实体。
如果该PDCP PDU是经由特定RLC实体接收到的,即如果经由特定RLC实体而接收到了PDCP PDU,则在S206,确定当前接收到的PDCP PDU是否是经由特定RLC实体而连续接收到的第一个PDCP PDU。
如果当前接收到的PDCP PDU是经由特定RLC实体而连续接收到的第一个PDCP PDU,则在S208,用户设备向基站发送PDCP状态报告。PDCP状态报告包括表示基站已发送的历史PDCP PDU是否被用户设备正确接收的信息。基站在收到PDCP状态报告时,可以根据PDCP状态报告来确定是否存在未被用户设备正确接收到的PDCP PDU。如果存在未被用户设备正确接收到的PDCP PDU,则可以针对该PDCP PDU,发起重传。即,重新向用户设备传输该PDCP PDU。
例如,可以通过定时器的运行状态来确定当前接收到的PDCP PDU是否是经由特定RLC实体而连续接收到的第一个PDCP PDU。在经由特定RLC实体而接收到PDCP PDU时,可以启动或重启该定时器。如果在经由特定RLC实体而接收到PDCP PDU时,该定时器处于未运行状态,可以确定当前接收到的PDCP PDU是经由该特定RLC实体而接连续接收到的第一个PDCP PDU。此时,启动定时器。那么当下一次经由该特定RLC实体而接收到PDCP PDU时,由于定时器处于运行状态,因而可以确定此次接收 到的PDCP PDU不是经由该RLC实体而连续接收到的第一个PDCP PDU。此时,可以重启定时器。由此,如果基站保持通过特定RLC实体来传输无线承载的状态,则用户设备将会连续地经由该特定RLC实体而接收到PDCP PDU,进而在经由该特定RLC实体而接收到第一个PDCP PDU之后,再次经由该特定RLC实体而接收到PDCP PDU时,定时器处于运行状态,从而可以判定出当前所接收到的PDCP PDU不是经由该特定RLC实体而连续接收到的第一个PDCP PDU。
定时器的值可以根据实际需要而适当设定,本发明对此没有特别限定。可以由基站通过RRC消息来向用户设备发送针对该定时器的配置消息,基站可以根据该配置消息来设定定时器。
在一个示例中,如果用户设备认为基站已从与特定RLC实体对应的第一传输模式切换到了与第一传输模式不同的另一传输模式,则可以停止定时器,其中,该另一传输模式对应于所对应的传输模式与特定RLC实体不同的另一RLC实体。由此,在基站再次切换到第一传输模式的情况下,在用户设备经由对应于第一传输模式的特定RLC实体而接收到PDCP PDU时,如果该定时器未处于运行状态,则可以确定此时接收到的PDCP PDU是经由该特定RLC实体而连续接收到的第一个PDCP PDU。
所谓基站切换传输模式,是指基站切换用于进行数据传输的RLC实体。RLC实体对应地存在于基站侧和用户设备侧。例如,在基站侧包括PTP RLC实体和PTM RLC实体的情况下,用户设备侧也对应地存在分别与基站侧的PTP RLC实体和PTM RLC实体对应的PTP RLC实体和PTM RLC实体。基站侧的PTP RLC实体(或PTM RLC实体)和UE侧的PTP RLC实体(或PTM RLC实体)互称为对等RLC实体。在基站决定通过PTP模式进行数据传输时,经由基站侧的PTP RLC实体向用户设备侧发送数,用户设备对应地通过其PTP RLC实体接收数据。而当基站切换了传输模式时,例如基站从PTP模式切换到了PTM模式,则在基站侧从PTP RLC实体切换到PTM RLC实体,在用户设备侧也切换为通过对应的PTM RLC实体来接收数据。
然而,用哪种传输模式来传输PDCP PDU是由基站决定的,而不由用户设备决定。对此,用户设备可以根据一定的策略来确定基站是否切换了传输模式。在满足以下条件中的任一条件的情况下,用户设备可以认为基 站已切换了传输模式,此时可以停止定时器:经由多个RLC实体中与特定RLC实体不同类型的另一RLC实体而接收到PDCP PDU;经由另一RLC实体而接收到PDCP PDU并且从经由另一RLC实体而接收到PDCP PDU时起的预定期间内未经由特定RLC实体接收到PDCP PDU(基站可以通过RRC消息为UE配置所述预定期间);经由另一RLC实体而接收到PDCP PDU并且从直到经由另一RLC实体而接收到的PDCP PDU达到预定数量为止的期间内未经由特定RLC实体接收到PDCP PDU;从基站接收到切换信息,切换信息表示从与某RLC实体对应的第一传输模式切换到与另一RLC实体对应的第二传输模式。
图5是根据本发明的实施例的发送状态报告的方法的另一示例的流程图。
在图5中,S302的操作与S202的操作相同,S304的操作可以与S304的操作相同。此外,S308的操作与S206的操作相同,S310的操作与S208的操作相同。因而,对这些操作不再重复描述。
如图5所示,用户设备可以在S306中,确定当前接收到的PDCP PDU所对应的分离无线承载是否被配置了报告发送指示信息。报告发送指示信息用于指示向基站发送PDCP状态报告,可以由基站来配置。
基站可以针对每个分离无线承载而配置报告发送指示信息。也可以仅针对满足要求的分离无线承载而配置报告发送指示信息。在通过定时器来确定上述第一个PDCP PDU的情况下,报告发送指示信息可以包括针对该定时器的定时器配置信息。在下文中,将以报告发送指示信息是针对该定时器的定时器配置信息的情况为例,对针对哪种分离无线承载而配置报告发送指示信息进行说明。
如果当前接收到的PDCP PDU所对应的分离无线承载被配置了报告发送指示信息,则进一步执行S308和S310的操作。在另一示例中,也可以在S308的操作之后执行S306的操作。
需要说明的是,本公开实施例中所述接收到的PDCP PDU也可以替换为接收到的PDCP SDU。可以进一步限定,所述接收到的PDCP PDU是PDCP数据PDU。
以下举出具体的实施例来进一步说明本发明。
实施例
分离无线承载被配置了第一RLC实体和第二RLC实体。所述分离无线承载对应的PDCP实体从下层(即RLC实体)接收PDCP PDU,如果所述PDCP PDU(或所述PDCP PDU对应的PDCP SDU)接收自第一RLC实体,则执行以下操作:
(1)如果定时器未运行,则触发PDCP状态报告和/或启动(start)所述定时器。
(2)如果所述定时器正在运行,则重启(restart)所述定时器。需要说明的是,本公开中,重启定时器也可以描述为启动定时器。
可选的,所述定时器的值由基站通过RRC信令为UE配置。如果所述定时器的值是由基站配置的,还可以规定,只有配置了所述定时器的分离无线承载才可以执行本实施例。进一步的,还可以规定对应的无线承载或PDCP实体是否被配置了信息元素statusReportRequired,只有在配置了statusReportRequired时或其取值为真时,才执行本实施例。其中,statusReportRequired包含在由基站发送给UE的RRC消息中(可以包含在配置第一定时器的RRC消息中),用于指示对应的无线承载是否被配置为在上行链路上发送PDCP状态报告。
可选的,当重建PDCP实体时,停止所述定时器。在重建PDCP实体时,将会重置与PDCP实体对应的RLC实体的参数,此时可以停止定时器。
可选的,当启用第二RLC实体时,停止所述定时器。
基站可以为每个分离无线承载配置所述定时器。基站也可以仅为所关联的第一RLC实体和第二RLC实体被配置了不同模式的分离无线承载配置所述定时器,例如所述第一RLC实体的模式为UM,所述第二RLC实体的模式为AM,即第一RLC实体为UM RLC实体,第二RLC实体为AM RLC实体。基站还可以仅为至少关联了一个AM RLC实体的分离无线承载配置所述定时器。AM RLC通常被配置用于对于QoS要求较高的业务,对于这类业务,当第一RLC实体传输不能满足QoS要求时,基站将启用第二RLC实体,为了避免数据丢失,需要触发UE发送PDCP状态报告,使得基站可以重传那些已经发送但尚未被UE正确接收的PDCP PDU或SDU。
下面以分离MRB为例描述上述过程。
基站通过RRC信令为UE配置分离MRB,所述分离MRB关联了两个RLC实体,其中一个是PTM RLC实体,另一个是PTP RLC实体。可选的,还在所述RRC信令中为对应分离MRB配置定时器(或定时器的取值)。
分离MRB的PDCP实体从下层实体(即RLC实体)接收PDCP PDU,当所述PDCP PDU(或所述PDCP PDU对应的PDCP SDU)是从PTP RLC实体接收到的,则执行以下操作:
(1)如果所述定时器未运行,则触发PDCP状态报告,和/或启动所述定时器(定时器的值设置为配置的值)。
(2)如果定时器正在运行,则重启所述定时器(定时器的值设置为配置的值)。
参照图6对该实施例的场景的一个示例进行说明。如图6所示,假设用于传输分离MRB的PDCP PDU包括1号PDCP PDU至N号PDCP PDU,其中N为正整数。基站通过PTM传输来传输1号PDCP PDU,但在传输2号PDCP PDU时,检测到QoS下降,可能影响造成数据丢失,因而基站可以决定转换到PTP方式来传输2号PDCP PDU。对应地,用户设备经由PTP RLC来接收2号PDCP PDU。用户设备在接收到2号PDCP PDU时,由于该2号PDCP PDU是经由PTP RLC接收到的第一个PDCP PDU,因而用户设备可以执行本实施例的操作,以向基站发送PDCP状态报告。该状态报告中可以包括表示到目前为止基站发送的各个PDCP PDU是否被成功接收的信息。例如,如果用户设备未接收到1号PDCP PDU,则在PDCP状态报告中可以包括表示未接收到1号PDCP PDU的信息。基站在接收到PDCP状态报告之后,可以通过PTP传输对1号PDCP PDU进行重传。
可以规定,仅当PTP RLC实体的模式为AM时,才配置所述定时器。也可以规定仅当分离MRB关联的两个RLC实体分别用于PTM传输和PTP传输时,才配置所述定时器。
分离MRB被上层配置在上行发送PDCP状态报告(configured by upper layers to send a PDCP status report in the uplink),接收PDCP实体在满足以下条件时触发PDCP状态报告:接收到来自PTP RLC实体的PDCP PDU(或 PDCP PDU对应的PDCP SDU)且定时器未运行。PDCP实体可通过信息元素statusReportRequired判断是否被上层配置发送PDCP状态报告,statusReportRequired包含在由基站发送给UE的RRC消息中(可以包含在配置第一定时器的RRC消息中),用于指示对应的无线承载是否被配置为在上行链路上发送PDCP状态报告。
如果从PTP RLC实体接到的PDCP数据PDU(其COUNT值为RCVD_COUNT)没有被丢弃,则接收PDCP实体(receiving PDCP entity)执行以下操作:启动或重启所述定时器。其中,RCVD_COUNT是接收到的PDCP数据PDU的COUNT,即[RCVD_HFN,RCVD_SN];其中,RCVD_HFN、RCVD_SN是RCVD_COUNT的两个字段的参数。RCVD_SN是接收到的PDCP数据PDU的PDCP SN,所述PDCP SN包含在所述PDU的PDU头中(PDCP SN of the received PDCP Data PDU,included in the PDU header),RCVD_HFN是接收到的PDCP数据PDU的HFN,具体由接收PDCP实体计算(the HFN of the received PDCP Data PDU,calculated by the receiving PDCP entity)。
本公开实施例中PTM RLC实体也称为PTM关联的RLC实体或配置了G-RNTI的RLC实体或关联了G-RNTI的RLC实体或用于PTM传输的RLC实体;PTP RLC实体也称为PTP关联的RLC实体或用于PTP传输的RLC实体。
需要说明的是,一个MBS业务(或称为MBS会话)可通过一个MBS标识来标识,所述MBS标识可以是TMGI和/或会话标识sessionId,其中TMGI可以包括PLMN标识和/或服务标识,所述服务标识在一个PLMN内唯一标识一个MBS业务。
图7是本公开涉及的用户设备UE的简要结构框图。如图7所示,该用户设备用户设备700包括处理器701和存储器702。处理器701例如可以包括微处理器、微控制器、嵌入式处理器等。存储器702例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器702上存储有程序指令。该 指令在由处理器701运行时,可以执行本公开详细描述的由用户设备执行的上述方法。
另外,运行在根据本公开的设备上的计算机可执行指令或者程序可以是通过控制中央处理单元(CPU)来使计算机实现本公开的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器***中。
用于实现本公开各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机***读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机***”可以是嵌入在该设备中的计算机***,可以包括操作***或硬件(如***设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如,单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器,也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路,也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下,本公开的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外,本公开并不局限于上述实施例。尽管已经描述了所述实施例的各种示例,但本公开并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备,如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上,已经参考附图对本公开的实施例进行了详细描述。但是,具体的结构并不局限于上述实施例,本公开也包括不偏离本公开主旨的任何设计改动。另外,可以在权利要求的范围内对本公开进行多种改动,通过适 当地组合不同实施例所公开的技术手段所得到的实施例也包含在本公开的技术范围内。此外,上述实施例中所描述的具有相同效果的组件可以相互替代。
Claims (10)
- 一种由用户设备执行的发送状态报告的方法,包括:在经由多个RLC实体中的特定RLC实体而接收到PDCP PDU时,确定当前接收到的PDCP PDU是否是经由所述特定RLC实体而连续接收到的第一个PDCP PDU,所述多个RLC实体被配置为用于传输对应的分离无线承载;以及在当前接收到的PDCP PDU是所述第一个PDCP PDU的情况下,向基站发送PDCP状态报告,所述PDCP状态报告包括表示所述基站已发送的历史PDCP PDU是否被所述用户设备正确接收的信息。
- 根据权利要求1所述的方法,其中,所述分离无线承载为分离MBS无线承载,所述特定RLC是被配置为用于传输所述分离MBS无线承载的多个RLC实体中的PTP RLC实体。
- 根据权利要求1所述的方法,还包括:在向基站发送PDCP状态报告之前,确定当前接收到的PDCP PDU所对应的分离无线承载是否被配置了报告发送指示信息,所述报告发送指示信息用于指示向所述基站发送所述PDCP状态报告;在当前接收到的PDCP PDU是所述第一个PDCP PDU的情况下,向基站发送PDCP状态报告包括:在当前接收到的PDCP PDU是所述第一个PDCP PDU,并且当前接收到的PDCP PDU所对应的分离无线承载被配置了报告发送指示信息的情况下,向基站发送PDCP状态报告。
- 根据权利要求3所述的方法,其中,所述报告发送指示信息针对以下中的任一种分离无线承载而配置:每个分离无线承载;所对应的所述多个RLC实体被配置了不同的响应模式的分离无线承载而配置,所述响应模式指示是否向所述基站作出响应的模式;所对应的所述多个RLC实体中的至少一个RLC实体被配置为向所述基站作出响应的确认模式的分离无线承载;所对应的多个RLC实体中的PTP RLC实体被配置为确认模式的分离无线承载而被配置。
- 根据权利要求1~4中任一项所述的方法,其中,确定当前接收到的PDCP PDU是否是经由所述特定RLC实体而连续接收到的第一个PDCP PDU包括:在定时器不处于运行状态的情况下,确定当前接收到的PDCP PDU是经由所述特定RLC实体而连续接收到的第一个PDCP PDU,所述定时器在经由所述特定RLC实体而接收到所述PDCP PDU时被启动或被重启。
- 根据权利要求5所述的方法,其中,所述定时器在满足以下中的任一条件时被停止:经由所述多个RLC实体中与所述特定RLC实体不同类型的另一RLC实体而接收到PDCP PDU;经由所述另一RLC实体而接收到PDCP PDU并且从经由所述另一RLC实体而接收到PDCP PDU时起的预定期间内未经由所述特定RLC实体接收到PDCP PDU;经由所述另一RLC实体而接收到PDCP PDU并且从直到经由所述另一RLC实体而接收到的PDCP PDU达到预定数量为止的期间内未经由所述特定RLC实体接收到PDCP PDU;从所述基站接收到切换信息,所述切换信息表示从与所述某RLC实体对应的第一传输模式切换到与所述另一RLC实体对应的第二传输模式。
- 根据引用权利要求3的权利要求5所述的方法,其中,所述报告发送指示信息包括针对所述定时器的定时器配置信息。
- 一种由基站执行的执行无线承载重传的方法,包括:根据从用户设备接收到的PDCP状态报告,确定是否存在未成功被所 述用户设备接收的PDCP PDU,所述PDCP状态报告由所述用户设备通过权利要求1-7中任一项所述的方法而发送给所述基站;以及如果存在未成功被所述用户设备接收的PDCP PDU,则经由对应的PTP PLC实体向所述用户设备重新传输该PDCP PDU。
- 根据权利要求8所述的方法,还包括:向所述用户设备发送定时器配置信息,所述定时器配置信息用于配置用于确定所述第一个PDCP PDU的定时器。
- 一种用户设备,包括:处理器;以及存储器,存储有指令,其中,所述指令在由所述处理器运行时执行根据权利要求1至7中的任一项所述的方法。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202111055582.X | 2021-09-09 | ||
CN202111055582.XA CN115802406A (zh) | 2021-09-09 | 2021-09-09 | 状态报告发送方法、无线承载重传执行方法及用户设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023036173A1 true WO2023036173A1 (zh) | 2023-03-16 |
Family
ID=85473202
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/117521 WO2023036173A1 (zh) | 2021-09-09 | 2022-09-07 | 状态报告发送方法、无线承载重传执行方法及用户设备 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN115802406A (zh) |
WO (1) | WO2023036173A1 (zh) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109391376A (zh) * | 2017-08-09 | 2019-02-26 | 华为技术有限公司 | 状态报告的发送方法、设备及*** |
CN110546987A (zh) * | 2017-04-26 | 2019-12-06 | 三星电子株式会社 | 下一代移动通信***中发送无线链路控制状态报告的方法和装置 |
CN113038632A (zh) * | 2019-12-24 | 2021-06-25 | 夏普株式会社 | Pdcp实体的控制方法以及pdcp实体 |
-
2021
- 2021-09-09 CN CN202111055582.XA patent/CN115802406A/zh active Pending
-
2022
- 2022-09-07 WO PCT/CN2022/117521 patent/WO2023036173A1/zh unknown
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110546987A (zh) * | 2017-04-26 | 2019-12-06 | 三星电子株式会社 | 下一代移动通信***中发送无线链路控制状态报告的方法和装置 |
CN109391376A (zh) * | 2017-08-09 | 2019-02-26 | 华为技术有限公司 | 状态报告的发送方法、设备及*** |
CN113038632A (zh) * | 2019-12-24 | 2021-06-25 | 夏普株式会社 | Pdcp实体的控制方法以及pdcp实体 |
Non-Patent Citations (2)
Title |
---|
ERICSSON: "Reliability for Multicast and for Multicast Service Continuity", 3GPP DRAFT; R2-2108080, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic meeting; 20210816, 5 August 2021 (2021-08-05), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052032442 * |
FUTUREWEI, QUALCOMM INC., INTEL, UIC, KYOCERA, NEC, SAMSUNG, ERICSSON: "L2 ARQ by PDCP for PTM", 3GPP DRAFT; R2-2107539, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20210809 - 20210827, 6 August 2021 (2021-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052034193 * |
Also Published As
Publication number | Publication date |
---|---|
CN115802406A (zh) | 2023-03-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5351329B2 (ja) | 無線通信システムにおいて1対多サービスを受信する方法及び端末 | |
JP7516542B2 (ja) | マルチキャスト/ブロードキャストサービス配信の動的変更 | |
WO2022085640A1 (ja) | 端末装置、基地局装置、および方法 | |
TW202226860A (zh) | 發起pdcp狀態報告進程的方法和使用者設備 | |
WO2023036173A1 (zh) | 状态报告发送方法、无线承载重传执行方法及用户设备 | |
WO2022080300A1 (ja) | 端末装置および方法 | |
WO2022085664A1 (ja) | 端末装置、基地局装置、および方法 | |
WO2021221009A1 (ja) | 端末装置、方法、および、集積回路 | |
WO2021027685A1 (zh) | Pdcp实体发送端/接收端的执行方法、pdcp实体及通信设备 | |
WO2023001240A1 (zh) | 由用户设备ue执行的方法及用户设备 | |
JP2023126994A (ja) | 端末装置、基地局装置、方法、および、集積回路 | |
JP2023130533A (ja) | 端末装置、基地局装置、方法、および、集積回路 | |
WO2023036287A1 (zh) | 用户设备执行的方法、基站的传输方法及用户设备 | |
WO2022255293A1 (ja) | 端末装置、基地局装置、および方法 | |
WO2022255279A1 (ja) | 端末装置、基地局装置、および方法 | |
WO2022138567A1 (ja) | 端末装置、基地局装置、および方法 | |
US20240260117A1 (en) | Terminal apparatus, base station apparatus, and method | |
WO2023276947A1 (ja) | 端末装置、基地局装置、および方法 | |
WO2022255303A1 (ja) | 端末装置、基地局装置、および方法 | |
WO2022255305A1 (ja) | 端末装置、基地局装置、および方法 | |
US20240260118A1 (en) | Terminal apparatus, base station apparatus, and method | |
US20240260119A1 (en) | Terminal apparatus, base station apparatus, and method | |
WO2022255288A1 (ja) | 端末装置、基地局装置、および方法 | |
WO2022080304A1 (ja) | 端末装置、基地局装置、および方法 | |
WO2022080339A1 (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: 22866636 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |