WO2022083533A1 - 非连续性接收方法以及用户设备 - Google Patents

非连续性接收方法以及用户设备 Download PDF

Info

Publication number
WO2022083533A1
WO2022083533A1 PCT/CN2021/124351 CN2021124351W WO2022083533A1 WO 2022083533 A1 WO2022083533 A1 WO 2022083533A1 CN 2021124351 W CN2021124351 W CN 2021124351W WO 2022083533 A1 WO2022083533 A1 WO 2022083533A1
Authority
WO
WIPO (PCT)
Prior art keywords
drx
discontinuous reception
rnti
mbs service
unicast
Prior art date
Application number
PCT/CN2021/124351
Other languages
English (en)
French (fr)
Inventor
常宁娟
刘仁茂
Original Assignee
夏普株式会社
常宁娟
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 夏普株式会社, 常宁娟 filed Critical 夏普株式会社
Priority to US18/032,583 priority Critical patent/US20230388972A1/en
Publication of WO2022083533A1 publication Critical patent/WO2022083533A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • 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
    • 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/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • 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/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • 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/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/188—Time-out mechanisms
    • H04L1/1883—Time-out mechanisms using multiple timers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]

Definitions

  • the present disclosure relates to the technical field of wireless communication, and more particularly, to a discontinuous reception method and a corresponding user equipment.
  • the purpose of the NR MBS work item in the RAN is to provide the support or capability that needs to be provided in the Radio Access Network (RAN) in order to achieve the above objectives of SA2.
  • one of the specific work items is to define the corresponding transmission mechanism and scheduling mechanism for UEs in the RRC_CONNECTED state of radio resource control, so that these UEs can receive broadcast/multicast services.
  • This disclosure discusses related issues involved in achieving the above-mentioned work objectives.
  • the purpose of the embodiments of the present disclosure is to solve the problem of discontinuous reception in the RRC connected state for MBS in the NR system. More specifically, the present disclosure proposes a solution to the problem of how to implement discontinuous reception on a unicast link when a UE enters a radio resource control (Radio Resource Control, RRC) connected state to receive a highly reliable MBS service.
  • RRC Radio Resource Control
  • the embodiments of the present disclosure provide a discontinuous reception method performed in a user equipment and a corresponding user equipment.
  • a discontinuous reception method including: a user equipment UE receives configuration information or scheduling information related to a multicast and broadcast service MBS service; the UE determines the configuration information or scheduling information Whether the DRX configuration for discontinuous reception is configured in the information; if the DRX configuration is not configured in the configuration information or scheduling information, the UE receives the MBS service using the DRX configuration corresponding to unicast.
  • the UE may use the DRX configuration corresponding to unicast to monitor the PDCCH addressed by the MBS service identifier.
  • the MBS service identifier may be a wireless network group identifier G-RNTI
  • the DRX configuration corresponding to the unicast may be included in the MAC cell group configuration information element MAC-CellGroupConfig DRX configuration.
  • a discontinuous reception method comprising: receiving, at a user equipment UE, a MAC PDU or PDCCH addressed with a multicast and broadcast service MBS service identifier, and the MBS service identifier is
  • the MAC entity of the UE enters the active time for the unicast discontinuous reception DRX operation, and monitors the PDCCH addressed with the UE-specific identity.
  • the MBS service identifier may be a wireless network group identifier G-RNTI; the UE-specific identifier may be a cell wireless network temporary identifier C-RNTI or CS-RNTI; the The DRX operation corresponding to unicast may be a DRX operation applying the DRX configuration contained in the MAC cell group configuration information element MAC-CellGroupConfig.
  • the MAC entity of the UE considers that it is in the active time.
  • the UE when the UE receives a MAC PDU or PDCCH addressed with an MBS service identifier, and the MBS service identifier is configured with uplink reception status feedback, the UE may The MAC entity starts the drx-HARQ-RTT-TimerDL timer associated with the corresponding HARQ process in the unicast DRX operation.
  • the MAC entity of the UE may start the drxRetransmision-TimerDL timer associated with the corresponding HARQ process, and in When the timer drxRetransmision-TimerDL is running, the UE considers that it is within the activation time.
  • the UE when the UE receives a MAC PDU or PDCCH addressed with an MBS service identifier, and the MBS service identifier is configured with uplink reception status feedback, the UE may The MAC entity starts a timer T1 for the unicast DRX operation, and when the timer T1 runs, the UE considers that it is within the active time to monitor the PDCCH addressed with the UE-specific identity.
  • a user equipment comprising: a processor; and a memory storing instructions; wherein the instructions, when executed by the processor, execute the discontinuous reception method according to the context .
  • FIG. 1 is a schematic diagram showing retransmission processing based on different protocol stack architectures.
  • FIG. 2 is a flowchart showing the processing of the discontinuous reception method according to Embodiment 1 of the present disclosure.
  • FIG. 3 shows a block diagram of a user equipment UE involved in the present disclosure.
  • LTE Long Term Evolution
  • NR New Radio
  • LTE system is also used to refer to 5G and later LTE systems (such as called eLTE system, or can be connected to 5G LTE system of the core network), and LTE can be replaced by Evolved Universal Terrestrial Radio Access (Evolved Universal Terrestrial Radio Access, E-UTRA) or Evolved Universal Terrestrial Radio Access Network E-UTRAN.
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • E-UTRAN Evolved Universal Terrestrial Radio Access
  • Cancel, Release, Delete, Empty, and Clear can be replaced.
  • Execution, use and application are interchangeable. Configuration and reconfiguration can be replaced. Links and connections can be replaced. Monitor and detect can be replaced.
  • SC-PTM Single Cell-Point To Multipoint
  • DRX discontinuous Reception
  • MBSFN Multimedia Broadcast Multicast Service Single Frequency Network
  • MBSFN single-cell point-to-multipoint
  • SC-PTM Single Frequency Network
  • the UE learns the MBMS services that the cell is going to perform or is currently performing and the configuration information required to receive these services, and based on which services it is interested in, the UE transmits the information on the single cell multicast transmission channel (Single Cell Multicast Transmission Channel). Transport Channel, SC-MTCH) to receive the corresponding services of interest.
  • SC-MTCH Single Cell Multicast Transmission Channel
  • the base station can notify the UE through a change notification, such as through the Physical Downlink Control Channel.
  • TMGI Temporary Mobile Group Identity
  • serviceId service identifier
  • the session ID is an optional MBMS session ID, which is generally used together with TMGI to identify the transmission or retransmission of a specific MBMS session.
  • G-RNTI Group-Radio Network Temparory Identifier
  • MRB MBMS Point to Multipoint Radio Bearer
  • the UE When the UE determines to receive an MBMS service, it establishes an MRB according to predefined parameters and uses the corresponding G-RNTI to receive MBMS data on the corresponding physical channel.
  • the above MRB refers to a single cell MRB (Single Cell MRB, SC-MRB).
  • the MAC entity For each G-RNTI, the MAC entity will be configured with a DRX function by the RRC layer to control the PDCCH monitoring of the G-RNTI by the UE.
  • the configuration and use of the DRX function do not distinguish the RRC state, that is, the RRC idle state and the RRC connected state are the same.
  • the DRX of different G-RNTIs operate independently.
  • RRC configures the following DRX parameters for each G-RNTI: timer onDurationTimerSCPTM, timer drx-InactivityTimerSCPTM, SCPTM-SchedulingCycle and SCPTM-SchedulingOffset.
  • the MAC entity When the timer onDurationTimerSCPTM or the timer drx-InactivityTimerSCPTM is running, the MAC entity considers that it is at the active time, and the UE needs to perform the PDCCH monitoring corresponding to the G-RNTI; otherwise, the UE does not need to perform the PDCCH monitoring corresponding to the G-RNTI. PDCCH monitoring.
  • the MAC entity starts the timer onDurationTimerSCPTM:
  • DRX Discontinuous Reception
  • the MAC entity can be configured with a DRX function by the RRC layer to control the MAC entity to identify the cell radio network temporary identifier C-RNTI (Cell-Radio Network Temparary Identifier) to the UE, cancel the indication of the radio network temporary identifier CI- RNTI (Cancellation Indication RNTI), configured scheduling wireless network temporary identifier CS-RNTI (Configured Scheduling RNTI), interrupted wireless network temporary identifier INT-RNTI (Interruption RNTI), slot format indication wireless network temporary identifier SFI-RNTI (Slot Format Indication RNTI), semi-static channel status indication wireless network temporary identifier SP-CSI-RNTI (Semi-Persistent CSI RNTI), transmit power control physical uplink control channel wireless network temporary identifier TPC-PUCCH-RNTI (Transmit Power Control-PUCCH-RNTI ), transmit power control physical uplink shared channel wireless network temporary identifier TPC-PUSCH
  • C-RNTI Cell-Radio Network
  • the parameters configured by the RRC layer to control the DRX operation include:
  • -drx-onDurationTimer the duration of the start of the DRX cycle
  • -drx-InactivityTimer indicates the duration after a new uplink or downlink transmitted PDCCH
  • -drx-RetransmissionTimerDL The longest duration before a downlink retransmission is received. This timer distinguishes each downlink Hybrid Automatic Repeat reQuest (HARQ) process, excluding the broadcast process;
  • HARQ Hybrid Automatic Repeat reQuest
  • -drx-RetransmissionTimerUL The longest duration before receiving an uplink grant for uplink retransmission, this timer is used to distinguish each uplink HARQ process;
  • Short DRX cycle this parameter is optional
  • -drx-HARQ-RTT-TimerDL The shortest duration before receiving a downlink assignment (assignment) for HARQ retransmission. This timer is used to distinguish each downlink HARQ process, excluding the broadcast process;
  • -drx-HARQ-RTT-TimerUL The shortest duration before an uplink grant for uplink HARQ retransmission is received, this timer is for each uplink HARQ process.
  • the RRC layer may divide the serving cells of the UE into two DRX groups, and each DRX lease is configured with a group of serving cells.
  • Each DRX group has its own drx-onDurationTimer and drx-InactivityTimer configurations, and other DRX parameter configurations are shared by the two DRX groups.
  • a serving cell in a DRX group its active time includes the following times: timers drx-onDurationTimer and drx-InactivityTimer are running, drx-RetransmissionTimerDL or drx-RetransmissionTimerUL
  • the random access response or the ra-ContentionResolutionTimer or msgB-ResponseWindow received by message B is running, and a scheduling request (SR) has been sent on the uplink control channel (Physical Uplink Control Channel, PUCCH) and is in a pending state (pending), etc.
  • SR scheduling request
  • the UE For a DRX group, if the short DRX cycle is configured, the UE starts to use the short DRX cycle after receiving a DRX command MAC control element or the drx-InactivityTimer times out.
  • the long DRX cycle is used when the short DRX cycle timer drx-ShortCycleTimer times out or when a long DRX command MAC control element is received.
  • the MAC entity starts the drx-onDurationTimer timer after the drx-slotOffset timeslot offsets at the beginning of the subframe are satisfied when the subframe meets the following formula:
  • the drx-onDurationTimer and drx-InactivityTimer timers are stopped when the MAC entity receives a (long) DRX Command MAC Control Element.
  • the MAC entity monitors the PDCCH on the serving cell within the DRX group. If a PDCCH indicates a downlink transmission, start the drx-HARQ-RTT-TimerDL timer of the corresponding HARQ process in the first symbol after the corresponding transmission carrying the downlink HARQ feedback ends, and stop the corresponding HARQ process.
  • drx - RetransmissionTimerDL timer start the drx-HARQ-RTT-TimerDL timer.
  • the drx of the corresponding HARQ process is started in the first symbol after the end of the first repetition (repetition) of the corresponding physical uplink control channel (Physical Uplink Control Channel, PUSCH) transmission - HARQ-RTT-TimerUL timer, and stop the drx-RetransmissionTimerUL timer of the corresponding HARQ process.
  • PUSCH Physical Uplink Control Channel
  • the drx-RetransmissionTimerDL timing of the corresponding HARQ process is started at the first symbol after the drx-HARQ-RTT-TimerDL times out.
  • the drx-RetransmissionTimerDL timer of the corresponding HARQ process is started in the first symbol after the drx-HARQ-RTT-TimerUL times out.
  • the PDCCH indicates a new uplink or downlink transmission
  • the drx-InactivityTimer timer is started or restarted in the first symbol after the PDCCH reception ends.
  • the UE needs to enter the connected state to perform the MBS session access procedure to After obtaining the authentication of the network side, the reception of the service is started; on the other hand, some services need to use the transmission mechanism in the connected state to ensure their service quality. That is to say, from the perspective of RRC, different services have different requirements on the state of RRC. For some MBS services that can be indistinguishable from the UE state, traditional LTE MBMS transmission methods such as SC-PTM can be used. For those MBS services that need to enter the connected state, the UE needs to access the network and enter the connected state to receive these MBS services.
  • the UE entering the RRC connected state can receive the corresponding MBS configuration through dedicated RRC signaling, such as the corresponding radio bearer configuration, feedback mechanisms such as channel state indication CSI or HARQ configuration, feedback-based retransmission service, etc. . That is to say, the reception of MBS in the NR system distinguishes the RRC state.
  • the MBS service (called the first type of service) that can be received in the RRC idle state or the RRC inactive state (RRC_INACTIVE)
  • the scheduling information used for configuring time-frequency domain resources or transmission information is provided through broadcast signaling.
  • the MBS service (called the second type of service) that must be received in the RRC connected state (RRC_CONNECTED), preferably, its scheduling information is provided through RRC dedicated signaling or Dynamically scheduled through PDCCH.
  • the MBS services it is interested in receiving may include both the first type of service and the second type of service.
  • the current reception modes include the following:
  • Receiving mode 1 Receive only through the point-to-multipoint PTM channel
  • Receiving mode 2 Receive only through the point-to-point PTP channel
  • Receiving mode 3 Receive independently on two channels through PTM and PTP at the same time;
  • Receiving mode 4 Receive through PTM and PTP, but the PTP channel is only used as a retransmission channel.
  • PTM and PTP channels For the relationship between PTM and PTP channels, they can be independent wireless bearers, or they can share some wireless protocol layer entities (such as Packet Data Convergence Protocol (PDCP)), but other wireless protocol layer entities are Each is independent, see Figure 1 for details.
  • PDCP Packet Data Convergence Protocol
  • the reception of the PTP channel uses a UE-specific identity addressing such as C-RNTI, while the reception of the PTM channel uses a public identity such as G-RNTI.
  • the retransmission on the PTP channel can be HARQ retransmission at the MAC layer.
  • the initial transmission data on the PTM channel and the retransmission on the PTP channel Data transmission can be combined by HARQ at the MAC layer; it can also be retransmission of data packets above the MAC layer, such as retransmission based on PDCP PDUs.
  • the PTM and PTP channels are similar to the split Radio Bearer (split Radio Bearer) in the NR system. )the concept of. But it is not limited to the above two methods.
  • DRX for SC-PTM and DRX for unicast operate independently, ie, there is no interaction between the two.
  • DRX operations in the aforementioned NR system are all about unicast downlink data reception.
  • the MBS reception can also be configured as DRX in the NR system, considering the above MBS reception mode 4 in the RRC connection state, the DRX configuration for MBS reception may include the following implementation modes:
  • DRX for unicast service and DRX for MBS operate completely independently and do not affect each other. This is similar to the way of operation between unicast DRX in LTE and DRX for SC-PTM.
  • Implementation mode 2 DRX used for unicast service and DRX used for MBS use the same DRX function, that is, DRX operation does not distinguish between unicast service and MBS service. In this way, the same DRX operation and configuration are adopted for the reception of MBS services and the reception of unicast services.
  • Implementation mode 3 The unicast DRX and the DRX used for the MBS are configured independently, and the DRX operations may affect each other.
  • the above-mentioned DRX for MBS refers to the DRX corresponding to the MBS received using the PTM channel, and the MBS receiving using the PTP channel is considered to perform a unicast DRX operation.
  • the present disclosure provides a solution for how to implement the functions of unicast DRX and DRX for MBS. More specifically, as in implementation 2, how to perform different DRX operations on MBS services of different reception types; in implementation 3, how to interoperate between operations between unicast DRX and DRX for MBS, All become the concerns of the present disclosure.
  • the following are several embodiments implemented on the UE based on the above problems in the present disclosure.
  • the following embodiments enable the UE to apply the corresponding DRX function to further save the UE energy consumption when receiving the MBS service using the receiving mode 4.
  • This embodiment provides a discontinuous reception method based on the foregoing implementation mode 2 of DRX for MBS implemented on a UE in an RRC connected state.
  • the MBS services it is interested in receiving may include both the first type of service and the second type of service.
  • the first type of service its DRX configuration and corresponding operation are similar to the DRX configuration and corresponding operation for SC-PTM in the existing LTE system.
  • DRX operates independently and does not affect each other.
  • the second type of service the same DRX configuration and operation as the unicast DRX is adopted, that is to say, the DRX configuration and operation in the existing NR system also acts on the second type of MBS service data.
  • the scheduling information of each MBS service of the first type of MBS service includes its corresponding PTM DRX configuration (such as the on duration timer, drx-InactivityTimer timer, drx-InactivityTimer timer, SchedulingCycle or SchedulingOffset), and the second type of MBS service uses the same DRX configuration as the existing unicast service (DRX-config or drx-ConfigSecondaryGroup contained in the MAC-CellGroupConfig information element), its scheduling information does not contain the corresponding DRX configuration.
  • PTM DRX configuration such as the on duration timer, drx-InactivityTimer timer, drx-InactivityTimer timer, SchedulingCycle or SchedulingOffset
  • this embodiment can be expressed as: for an MBS service, if a DRX configuration is not configured in its configuration information or scheduling information, the UE receives the MBS service using the DRX configuration corresponding to unicast, that is, for the MBS service
  • the corresponding identifier such as PDCCH monitoring addressed by G-RNTI, adopts the DRX configuration corresponding to unicast.
  • FIG. 2 is a flowchart showing the processing of the discontinuous reception method according to the first embodiment of the present disclosure.
  • step S201 the UE receives configuration information or scheduling information related to the MBS service of multicast and broadcast services.
  • step S202 the UE determines whether a DRX configuration is configured in the received configuration information or scheduling information.
  • step S203 if it is determined in step S202 that the DRX configuration is not configured in the above configuration information or scheduling information, the UE receives the MBS service using the DRX configuration corresponding to unicast.
  • the indication information is used to indicate whether the PDCCH monitoring with the identifier corresponding to the MBS service, such as the G-RNTI addressing, adopts the DRX configuration corresponding to unicast.
  • the indication information can indicate that the MBS service is a first-class service or a second-class service, and if the second-class service is the PDCCH monitoring with the corresponding identification of the MBS service, such as the G-RNTI addressing, using unicast corresponding DRX configuration.
  • the MAC entity can configure a DRX function by the RRC entity to control the UE pair including C-RNTI, CI-RNTI, UE-identified PDCCH monitoring activities including CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI and G-RNTI.
  • the MAC entity For PDCCH monitoring of G-RNTI, the MAC entity only does not configure a PTM DRX configuration in its associated configuration information or uses the configured DRX function in the indicated indication information.
  • This embodiment provides a discontinuous reception method based on the above-mentioned implementation mode 3 of DRX for MBS implemented on a UE in an RRC connected state.
  • the DRX configuration corresponding to the MBS service received in the PTM mode in the NR system and the DRX configuration corresponding to unicast are independent.
  • the unicast PTP channel is used for receiving the retransmission of the MBS service of the PTM channel
  • the unicast DRX operation operates according to the receiving state of the MBS service of the PTM channel.
  • the UE MAC entity When receiving a MAC PDU or PDCCH addressed by the MBS service identifier such as G-RNTI, and the G-RNTI is configured with uplink reception status feedback, the UE MAC entity enters the activation time for the unicast DRX operation to Monitor the PDCCH addressed by the C-RNTI (or CS-RNTI) corresponding to the retransmission of the MBS service data from the PTP channel.
  • the UE MAC entity considers that it is in the active time.
  • the fact that the G-RNTI is configured with MBS reception status feedback can also be described as that the G-RNTI is enabled with feedback corresponding to the MBS service or the G-RNTI is configured with associated uplink feedback transmission resources (such as PUCCH configuration).
  • the feedback may be HARQ feedback or L2 feedback (Radio Link Control (RLC) or PDCP status report).
  • the retransmission of the PTP may be based on the retransmission of different protocol layers.
  • This embodiment provides a further method to Embodiment 2 based on the protocol stack architecture (A in Fig. 1 ) in which the retransmission is the HARQ retransmission of the MAC layer.
  • the retransmission on the PTP channel is a HARQ retransmission
  • the initial transmission on the PTM channel and the HARQ retransmission on the PTP channel are performed in the same HARQ process, so that the initial transmission received on the PTM channel can be realized.
  • HARQ combining of blocks and retransmitted transport blocks received on the PTP channel are performed in the same HARQ process.
  • the UE MAC entity When receiving a MAC PDU or PDCCH addressed by the MBS service identifier such as G-RNTI, and the G-RNTI is configured with uplink reception status feedback, the UE MAC entity starts the corresponding HARQ process in the unicast DRX operation. Associated drx-HARQ-RTT-TimerDL timer. When the drx-HARQ-RTT-TimerDL timer expires, the MAC entity starts the drxRetransmision-TimerDL timer associated with the corresponding HARQ process. Preferably, the MAC entity starts the drx-HARQ-RTT-TimerDL timer of the corresponding HARQ process in the first symbol after the corresponding transmission carrying the HARQ feedback ends.
  • the MAC entity starts the drx-RetransmissionTimerDL timer of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL timer expires.
  • the UE considers that it is within the active time, so as to monitor the PDCCH addressed by the G-RNTI corresponding to the retransmission of the scheduled MBS service data from the PTP channel.
  • the UE MAC entity starts the drxRetransmision-TimerDL timer or drxRetransmision-TimerDL timer associated with the corresponding HARQ process.
  • the fact that the G-RNTI is configured with MBS reception status feedback can also be described as that the G-RNTI is enabled with feedback corresponding to the MBS service or the G-RNTI is configured with associated uplink feedback transmission resources (such as PUCCH configuration).
  • the unsuccessful decoding can also be expressed as the UE having fed back a NACK.
  • the retransmission of the PTP may be based on the retransmission of different protocol layers.
  • This embodiment provides a further method for Embodiment 2 based on the protocol stack architecture (B in FIG. 1 ) in which the retransmission is the retransmission of the PDU of the protocol layer above the MAC layer.
  • the initial transmission on the PTM channel and the retransmission data packets on the PTP channel are not performed in the same HARQ process, so combined decoding is not performed.
  • the UE directly discards the received transport block.
  • the UE MAC entity When receiving a MAC PDU or PDCCH addressed by an MBS service identifier such as G-RNTI, and the G-RNTI is configured with uplink reception status feedback, the UE MAC entity enables a newly defined DRX operation for unicast DRX operation. timer T.
  • the UE When the timer T is running, the UE considers that it is within the active time, so as to monitor the PDCCH addressed by the C-RNTI (or CS-RNTI) corresponding to the retransmission of the scheduled MBS service data from the PTP channel .
  • the UE MAC entity starts a timer T.
  • the fact that the G-RNTI is configured with MBS reception status feedback can also be described as that the G-RNTI is enabled with feedback corresponding to the MBS service or the G-RNTI is configured with associated uplink feedback transmission resources (such as PUCCH configuration).
  • the unsuccessful decoding can also be expressed as the UE having fed back a NACK.
  • the MAC entity starts the timer T in the first symbol after the corresponding transmission carrying the HARQ feedback ends.
  • the MAC entity starts the timer T after N symbols or milliseconds after the corresponding transmission carrying HARQ feedback ends.
  • the N may be configured by the base station through RRC, or may be a fixed constant value.
  • the timer T does not distinguish HARQ processes.
  • the value of the timer T may be configured by the base station through RRC.
  • FIG. 3 is a block diagram showing a user equipment UE according to the present invention.
  • the user equipment UE30 includes a processor 301 and a memory 302 .
  • the processor 301 may include, for example, a microprocessor, a microcontroller, an embedded processor, or the like.
  • the memory 302 may include, for example, volatile memory (eg, random access memory RAM), a hard disk drive (HDD), non-volatile memory (eg, flash memory), or other memory, or the like.
  • the memory 302 has program instructions stored thereon. When the instruction is executed by the processor 301, various methods such as the above-mentioned discontinuous reception method described in detail in the present invention can be performed.
  • base station refers to a mobile communication data and control switching center with larger transmit power and wider coverage area, including functions such as resource allocation and scheduling, data reception and transmission, and the like.
  • User equipment refers to a user's mobile terminal, for example, including a mobile phone, a notebook, and other terminal equipment that can wirelessly communicate with a base station or a micro base station.
  • the method and related apparatus of the present disclosure have been described above in conjunction with the preferred embodiments. Those skilled in the art will understand that the methods shown above are only exemplary. The methods of the present disclosure are not limited to the steps and sequences shown above.
  • the base station and user equipment shown above may include more modules, for example, may also include modules that can be developed or developed in the future and that can be used for the base station, MME, or UE, and so on.
  • the various identifiers shown above are only exemplary and not restrictive, and the present disclosure is not limited to the specific information elements exemplified by these identifiers. Numerous changes and modifications may occur to those skilled in the art in light of the teachings of the illustrated embodiments.
  • the program running on the device may be a program that causes a computer to implement 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 (eg, random access memory RAM), a hard disk drive (HDD), non-volatile memory (eg, flash memory), or other memory systems.
  • a program for realizing the functions of the embodiments of the present disclosure can be recorded on a computer-readable recording medium.
  • 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” as used herein may be a computer system embedded in the device, and may include an operating system or hardware (eg, peripheral devices).
  • the "computer-readable recording 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 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), 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 may be a microprocessor or any existing processor, controller, microcontroller, or state machine.
  • the above circuit may be a digital circuit or an analog circuit. In the event that new integrated circuit technologies emerge as a result of advances in semiconductor technology to replace existing integrated circuits, one or more embodiments of the present disclosure may also be implemented using these new integrated circuit technologies.

Landscapes

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

Abstract

本公开提供了一种非连续性接收方法以及用户设备。所述非连续性接收方法，包括：用户设备UE接收与多播和广播服务MBS业务相关的配置信息或调度信息；所述UE判断所述配置信息或调度信息中是否配置有非连续性接收DRX配置；在所述配置信息或调度信息中未被配置DRX配置的情况下，所述UE对所述MBS业务的接收采用单播对应的DRX配置。

Description

非连续性接收方法以及用户设备 技术领域
本公开涉及无线通信技术领域，更具体地，本公开涉及非连续性接收方法以及对应的用户设备。
背景技术
2019年12月，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#86次全会上，批准了一个下一代接入技术(New RAT，NR)多播和广播服务(Multicast and Broadcast Service，MBS)的工作项目(参见非专利文献：RP-193248：New WID：NR Multicast and Broadcast Service)。在SA2中对应的研究项目(见SP-190726)的工作目标之一(在SA2中称为Objective A)是在5G系统(5GS)中支持MBS服务，包括公共安全、V2X应用、IPTV、群组通信、物联网应用等。NR MBS在RAN的工作项目目的是为达成SA2上述目标在无线接入网(RAN)需要提供的支持或能力。其中，具体工作项目之一是对处于无线资源控制连接态RRC_CONNECTED的UE，定义对应的传输机制和调度机制使得这些UE可以接收广播/多播业务。
本公开讨论达成上述工作目标所涉及的相关问题。
发明内容
本公开实施例的目的在于解决NR系统中用于MBS的RRC连接态下的非连续性接收问题。更具体地，本公开针对UE进入无线资源控制(Radio Resource Control，RRC)连接态执行对高可靠性的MBS业务接收时如何实现在单播链路上的非连续性接收问题提出了解决方法。本公开实施例提供了在用户设备中执行的非连续性接收方法以及相应的用户设备。
根据本公开的第一方面，提出了一种非连续性接收方法，包括：用户设备UE接收与多播和广播服务MBS业务相关的配置信息或调度 信息；所述UE判断所述配置信息或调度信息中是否配置有非连续性接收DRX配置；在所述配置信息或调度信息中未被配置DRX配置的情况下，所述UE对所述MBS业务的接收采用单播对应的DRX配置。
在上述第一方面的非连续性接收方法中，所述UE可以采用单播对应的DRX配置，对以MBS业务标识寻址的PDCCH进行监听。
在上述第一方面的非连续性接收方法中，所述MBS业务标识可以是无线网络组标识G-RNTI，所述单播对应的DRX配置可以是包含在MAC小区组配置信息元素MAC-CellGroupConfig中的DRX配置。
根据本公开的第二方面，提出了一种非连续性接收方法，包括：在用户设备UE接收到以多播和广播服务MBS业务标识寻址的MAC PDU或PDCCH、且所述MBS业务标识被配置了上行接收状态反馈时，所述UE的MAC实体对于单播的非连续性接收DRX操作中进入激活时间，监听以UE特定标识寻址的PDCCH。
在上述第二方面的非连续性接收方法中，所述MBS业务标识可以是无线网络组标识G-RNTI；所述UE特定标识可以是小区无线网络临时标识C-RNTI或CS-RNTI；所述单播对应的DRX操作可以是应用包含在MAC小区组配置信息元素MAC-CellGroupConfig中的DRX配置的DRX操作。
在上述第二方面的非连续性接收方法中，在所述UE接收到的以所述MBS业务标识寻址的MAC PDU或PDCCH解码不成功时，所述UE的MAC实体认为处于激活时间。
在上述第二方面的非连续性接收方法中，可以在所述UE接收到以MBS业务标识寻址的MAC PDU或PDCCH、且所述MBS业务标识被配置了上行接收状态反馈时，所述UE的MAC实体对于单播的DRX操作中开启对应混合自动重传HARQ进程所关联的drx-HARQ-RTT-TimerDL定时器。
在上述第二方面的非连续性接收方法中，可以在所述drx-HARQ-RTT-TimerDL定时器超时后，所述UE的MAC实体开启对应的HARQ进程所关联的drxRetransmision-TimerDL定时器，在所 述定时器drxRetransmision-TimerDL运行时，所述UE认为处于激活时间内。
在上述第二方面的非连续性接收方法中，可以在所述UE接收到以MBS业务标识寻址的MAC PDU或PDCCH、且所述MBS业务标识被配置了上行接收状态反馈时，所述UE的MAC实体对于单播的DRX操作中开启定时器T1，在所述定时器T1运行时，所述UE认为处于激活时间内，以监听以所述UE特定标识寻址的PDCCH。
根据本公开的第三方面，提供一种用户设备，包括：处理器；以及存储器，存储有指令；其中，所述指令在由所述处理器运行时执行根据上下文所述的非连续性接收方法。
附图说明
为了更完整地理解本公开及其优势，现在将参考结合附图的以下描述，其中：
图1是表示基于不同的协议栈架构的重传处理的示意图。
图2是表示本公开的基于实施例1的非连续性接收方法的处理的流程图。
图3表示本公开所涉及的用户设备UE的框图。
在附图中，相同或相似的结构均以相同或相似的附图标记进行标识。
具体实施方式
根据结合附图对本公开示例性实施例的以下详细描述，本公开的其它方面、优势和突出特征对于本领域技术人员将变得显而易见。
在本公开中，术语“包括”和“含有”及其派生词意为包括而非限制；术语“或”是包含性的，意为和/或。
在本说明书中，下述用于描述本公开原理的各种实施例只是说明，不应该以任何方式解释为限制公开的范围。参照附图的下述描述用于帮助全面理解由权利要求及其等同物限定的本公开的示例性实施例。 下述描述包括多种具体细节来帮助理解，但这些细节应认为仅仅是示例性的。因此，本领域普通技术人员应认识到，在不背离本公开的范围和精神的情况下，可以对本文中描述的实施例进行多种改变和修改。此外，为了清楚和简洁起见，省略了公知功能和结构的描述。此外，贯穿附图，相同参考数字用于相似功能和操作。
下文以长期演进系统(Long Term Evolution，LTE)/NR移动通信系统及其后续的演进版本作为示例应用环境，具体描述了根据本公开的多个实施方式。然而，需要指出的是，本公开不限于以下实施方式，而是可适用于更多其它的无线通信系统。若无特殊说明，在本公开中，小区和基站或无线接入网络的概念可以互相替换；LTE系统也用于指代5G及其之后的LTE系统(如称为eLTE系统，或者可以连接到5G核心网的LTE系统)，同时LTE可以用演进的通用陆地无线接入(Evolved Universal Terrestrial Radio Access，E-UTRA)或演进的通用陆地无线接入网E-UTRAN来替换。取消、释放、删除、清空和清除等可以替换。执行、使用和应用可替换。配置和重配置可以替换。链路和连接可以替换。监测(monitor)和检测(detect)可替换。
下述先简要描述本公开实施例所涉及到的在先技术。
LTE中的多播广播业务单小区点对多点(Single Cell-Point To Multipoint，SC-PTM)传输机制及其非连续性接收(Discontinuous Reception，DRX)：
LTE系统中有两种主要的多媒体广播多播业务(Multimedia Broadcast Multicast Service，MBMS)传输方式：多播广播单频网(Multimedia Broadcast multicast service Single Frequency Network，MBSFN)和单小区点对多点(Single Cell-Point To Multipoint，SC-PTM)。在SC-PTM，基站通过系统信息和/或单小区多播控制信道(Single Cell Multicast Control Channel，SC-MCCH)上传输的控制信令广播其支持的MBMS业务及其调度信息如时频域资源等。通过获取这些MBMS接收配置，UE获知所述小区将要进行或正在进行的MBMS业务及接 收这些业务所需的配置信息，并基于自己对哪些业务感兴趣，在单小区多播传输信道(Single Cell Multicast Transport Channel，SC-MTCH)上接收对应的感兴趣的业务。若一个MBMS业务的控制信息有变化或一个MBS会话将要开始或结束或其传输信息要变更，则基站可以通过一个改变指示(change notification)来告知UE，比如通过物理下行控制信道(Physical Downlink Control Channel，PDCCH)发送的SC-MCCH信息改变指示；或通过媒体介入控制层控制元素(Media Access Control Control Element，MAC CE)方式的SC-PTM停止指示，通过PDCCH发送的SC-MCCH信息改变指示。对于MBMS，不同的业务(service)/会话(session)可以使用不同的标识来区分。在LTE中，临时移动组标识(Temporary Mobile Group Identity，TMGI)一般用于唯一标识一个MBMS业务，其包含PLMN标识和服务标识。服务标识(serviceId)用于在一个PLMN中唯一表示一个MBMS业务的标识。会话标识(sessionId)是一个可选的MBMS会话标识，一般用于和TMGI一起来标识一个特定的MBMS会话的的传输或重传。一个MBMS业务在无线网络中发送时，会关联到一个用于无线网络的组标识(Group-Radio Network Temparory Identifier，G-RNTI)。一般情况下，在一个无线网络中，MBMS业务和G-RNTI之间是一一对应的。LTE中用于MBMS业务的无线承载称为MBMS点到多点无线承载(MBMS Point to Multipoint Radio Bearer，MRB)，MRB对应的参数采用预配置(预定义)的方式，即无需UE通过信令的方式从网络侧获取。当UE确定接收一个MBMS业务时，按照预定义的参数建立MRB并使用对应的G-RNTI在对应的物理信道上接收MBMS数据。在SC-PTM机制中，上述MRB指单小区MRB(Single Cell MRB，SC-MRB)。
对每一个G-RNTI，MAC实体会由RRC层为其配置一个DRX功能以控制UE对该G-RNTI的PDCCH监听。该DRX功能的配置和使用不区分RRC状态，即对RRC空闲态和RRC连接态都是一样的。不同G-RNTI的DRX是独立操作的。RRC为每一个G-RNTI配置下述 DRX参数：定时器onDurationTimerSCPTM、定时器drx-InactivityTimerSCPTM、SCPTM-SchedulingCycle和SCPTM-SchedulingOffset。当定时器onDurationTimerSCPTM或定时器drx-InactivityTimerSCPTM在运行时，MAC实体认为处于激活时间(active time)，UE需要去执行该G-RNTI对应的PDCCH监听；否则，UE无需去执行该G-RNTI对应的PDCCH监听。
对于一个G-RNTI，若一个子帧满足下式时，MAC实体启动定时器onDurationTimerSCPTM：
[(H-SFN*10240+SFN*10)+子帧号]modulo(SCPTM-SchedulingCycle)＝SCPTM-SchedulingOffset，其中，H-SFN是超帧号，SFN是系统帧号，modulo是模的操作，SCPTM-SchedulingCycle和SCPTM-SchedulingOffset分别是上述由RRC配置的调度周期和调度偏移值。当处于激活时间内时，对于每一个PDCCH子帧，MAC实体监听PDCCH。若PDCCH指示了一个下行传输，则MAC实体启动或重启定时器drx-InactivityTimerSCPTM。
NR系统中RRC连接态下的非连续性接收(Discontinuous Reception，DRX)机制：
当UE处于RRC连接态时，MAC实体可由RRC层配置一个DRX功能以控制该MAC实体对UE标识小区无线网络临时标识C-RNTI(Cell-Radio Network Temparary Identifier)、取消指示无线网络临时标识CI-RNTI(Cancellation Indication RNTI)、配置的调度无线网络临时标识CS-RNTI(Configured Scheduling RNTI)、中断无线网络临时标识INT-RNTI(Interruption RNTI)、时隙格式指示无线网络临时标识SFI-RNTI(Slot Format Indication RNTI)、半静态信道状态指示无线网络临时标识SP-CSI-RNTI(Semi-Persistent CSI RNTI)、发送功率控制物理上行控制信道无线网络临时标识TPC-PUCCH-RNTI(Transmit Power Control-PUCCH-RNTI)、发送功率控制物理上行共享信道无线网络临时标识TPC-PUSCH-RNTI(Transmit Power Control-Physical Uplink Shared  Cannel-RNTI)、发送功率控制探测参考符号无线网络临时标识TPC-SRS-RNTI(Transmit Power Control-Sounding Reference Symbols-RNTI)和有效性指示无线网络临时标识AI-RNTI(Availability Indication-RNTI)的PDCCH监听活动。可以理解当前NR系统中的DRX是作用于单播的数据传输方式。如非特殊说明，当配置了DRX时，MAC实体对所有激活的服务小区使用DRX操作来非连续性监听PDCCH。
RRC层配置的用来控制DRX操作的参数包含：
-drx-onDurationTimer：DRX周期开始的持续时间；
-drx-SlotOffset：开启drx-onDurationTimer定时器之前的延迟时间；
-drx-InactivityTimer：指示了一个新的上行或下行传输的PDCCH之后的持续时间；
-drx-RetransmissionTimerDL：在收到一个下行重传之前的最长持续时间，该定时器是区分每个下行混合自动重传(Hybrid Automatic Repeat reQuest，HARQ)进程的，不包括广播进程；
-drx-RetransmissionTimerUL：在收到一个用于上行重传的上行许可(grant)之前的最长持续时间，该定时器是区分每个上行HARQ进程的；
-drx-LongCycleStartOffset：长DRX周期和DRX开始偏移值；
-drx-ShortCycle：短DRX周期，该参数是可选配置；
-drx-ShortCycleTimer：短DRX周期的持续时间，该参数是可选配置；
-drx-HARQ-RTT-TimerDL：在收到一个用于HARQ重传的下行分配(assignment)之前的最短持续时间，该定时器是区分每个下行HARQ进程的，不包括广播进程；
-drx-HARQ-RTT-TimerUL：在收到一个用于上行HARQ重传的上行许可(grant)之前的最短持续时间，该定时器是区分每个上行HARQ进程的。
RRC层可以将UE的服务小区分为两个DRX组，每个DRX租被配置一组服务小区。每个DRX组有其自己的drx-onDurationTimer和drx-InactivityTimer配置，其他DRX参数配置是两个DRX组共享的。
对于一个DRX组内的服务小区，其激活时间(active time)包括下述时间：定时器drx-onDurationTimer和drx-InactivityTimer正在运行、drx-RetransmissionTimerDL或drx-RetransmissionTimerUL正在运行、用于随机接入过程的随机接入响应或消息B接收的ra-ContentionResolutionTimer或msgB-ResponseWindow正在运行、上行控制信道(Physical Uplink Control Channel，PUCCH)上发送了调度请求(Scheduling Request，SR)且处于等待状态(pending)等。
对于一个DRX组，若配置了短DRX周期，则UE在收到一个DRX命令MAC控制元素或drx-InactivityTimer超时后，开始使用短DRX周期。当短DRX周期定时器drx-ShortCycleTimer超时后或收到一个长DRX命令MAC控制元素后，使用长DRX周期。若配置了短DRX周期，则MAC实体在满足下式的子帧时，在该子帧开始的drx-slotOffset个时隙偏移满足后开启drx-onDurationTimer定时器：
[(SFN*10)+子帧号]modulo(drx-ShortCycle)＝drx-StartOffset，若使用长DRX周期，则MAC实体在满足下式的子帧时，在该子帧开始的drx-slotOffset个时隙偏移满足后开启drx-onDurationTimer定时器：
[(SFN*10)+子帧号]modulo(drx-LongCycle)＝drx-StartOffset。
对一个DRX组，当MAC实体收到一个(长)DRX命令MAC控制元素时，停止drx-onDurationTimer和drx-InactivityTimer定时器。当处于激活时间时，MAC实体在该DRX组内的服务小区上监听PDCCH。若收到一个PDCCH指示了一个下行传输，则在相应的携带下行HARQ反馈的传输结束后的第一个符号启动对应的HARQ进程的drx-HARQ-RTT-TimerDL定时器，并停止相应HARQ进程的drx-RetransmissionTimerDL定时器。若收到一个PDCCH指示了一个上行传输，则在相应的物理上行控制信道(Physical Uplink Control Channel，PUSCH)传输的第一个副本(repetition)结束后的第一个符 号启动对应的HARQ进程的drx-HARQ-RTT-TimerUL定时器，并停止相应HARQ进程的drx-RetransmissionTimerUL定时器。当定时器drx-HARQ-RTT-TimerDL超时后，若相应的HARQ进程的数据未成功解码，则在drx-HARQ-RTT-TimerDL超时后的第一个符号启动相应的HARQ进程的drx-RetransmissionTimerDL定时器。当定时器drx-HARQ-RTT-TimerUL超时后，则在drx-HARQ-RTT-TimerUL超时后的第一个符号启动相应的HARQ进程的drx-RetransmissionTimerDL定时器。当PDCCH指示了一个上行或下行的新传输时，则在PDCCH接收结束后的第一个符号启动或重启drx-InactivityTimer定时器。
在正在进行的NR MBS工作项目中，与LTE中的MBMS机制不同的是，考虑到一些MBS业务的可靠性以及群组性，一方面，UE需要进入连接态来执行MBS会话接入过程，以得到网络侧的认证，开启对该服务的接收；另一方面，一些业务需要使用在连接态下的传输机制，才能保证其服务质量。也就是说，从RRC的角度，不同业务对RRC的状态有不同的要求。对于一些可以对UE状态无区别的MBS业务，可以采用传统LTE中的MBMS传输方式如SC-PTM，而对那些需要进入连接态的MBS业务，UE需要接入网络进入连接态才能接收这些MBS业务。进入到RRC连接状态的UE，可以通过专用RRC信令接收相对应的MBS配置，如对应的无线承载配置、反馈机制如信道状态指示CSI或混合自动重传HARQ配置、基于反馈的重传服务等。也就是说，NR系统中MBS的接收是区分RRC状态的。对于可以在RRC空闲态或RRC非激活态(RRC_INACTIVE)接收的MBS业务(称第一类业务)，优选地，其用于配置时频域资源或传输信息的调度信息是通过广播信令来提供的，如系统信息或MCCH信道上的schedulingInfo信息元素；而对于必须在RRC连接态(RRC_CONNECTED)接收的MBS业务(称第二类业务)，优选地，其调度信息是通过RRC专用信令提供或通过PDCCH动态调度的。对 一个处于RRC连接态的UE，其感兴趣去接收的MBS业务可以既有第一类业务也有第二类业务。
对于第一类MBS业务的接收，一般认为采用点到多点PTM的多播或广播方式，而对于第二类MBS业务，目前的接收方式包括下述几种：
接收方式1：仅通过点到多点PTM的通道接收；
接收方式2：仅通过点到点PTP的通道接收；
接收方式3：同时通过PTM和PTP的方式在两个通道上独立接收；
接收方式4：通过通过PTM和PTP的方式接收，但PTP通道仅作为重传通道。
对于PTM和PTP通道之间的关系，可以是各自独立的无线承载，也可以是共享一些无线协议层实体(如包数据汇聚协议层(Packet Data Convergence Protocol，PDCP))但其他无线协议层实体是各自独立的，具体可参见图1。本公开中，PTP通道的接收使用UE特定的标识寻址如C-RNTI，而PTM通道的接收使用公共标识如G-RNTI。在接收方式4中，基于不同的PTM和PTP的协议栈架构，对于用于PTP通道上的重传可以是MAC层的HARQ重传，此时PTM通道上的初传数据和PTP通道上的重传数据可以在MAC层进行HARQ合并；也可以是MAC层之上的数据包重传，如基于PDCP PDU的重传，此时PTM和PTP通道类似于NR系统中的分裂无线承载(split Radio Bearer)的概念。但并不限于上述两种方式。
在LTE系统中，用于SC-PTM的DRX和用于单播的DRX是独立操作的，即两者之间没有交互作用。而在NR系统中，目前仅对单播的DRX做了定义，前述NR系统中的DRX操作都是围绕单播的下行数据接收而言的。若MBS的接收在NR系统中也可以配置成DRX，考虑到上述RRC连接状态下的MBS接收方式4，用于MBS接收的DRX配置可包含下述几种实现方式：
实现方式1：用于单播业务的DRX和用于MBS的DRX是完全独立操作的，互不影响。这类似于LTE中的单播DRX和用于SC-PTM的DRX之间的操作方式。
实现方式2：用于单播业务的DRX和用于MBS的DRX使用同一个DRX功能，即DRX操作上不区分单播业务还是MBS业务。在这种方式下，对MBS业务的接收和单播业务的接收采用相同的DRX操作和配置。
实现方式3：单播的DRX和用于MBS的DRX是单独配置的，DRX操作上可以是互相影响的。
本公开中，上述用于MBS的DRX指的是采用PTM通道接收的MBS对应的DRX，而采用PTP通道的MBS接收则认为执行单播的DRX操作。本公开基于上述用于MBS的接收的实现方式，对具体如何实现单播DRX和用于MBS的DRX的功能给出了解决方法。更具体地，如在实现方式2中，如何对不同接收类型的MBS业务执行不同的DRX操作；在实现方式3中，单播DRX和用于MBS的DRX之间的操作之间如何交互操作，都成为本公开所关注的问题。
下述是本公开中基于上述问题在UE上执行的若干实施例，通过下述实施例，使得UE在使用接收方式4进行MBS业务的接收时，应用相应的DRX功能来进一步节省UE能耗。
实施例1
该实施例给出了一种在处于RRC连接态的UE上实现的基于上述用于MBS的DRX的实现方式2的一种非连续性接收方法。
如前所述，对一个处于RRC连接态的UE，其感兴趣去接收的MBS业务可以既有第一类业务也有第二类业务。在该实施例中的DRX实现中，对于第一类业务，其DRX配置和对应的操作类似于现有LTE系统中的用于SC-PTM的DRX配置和对应的操作，与用于单播的DRX独立操作，互不影响。而对于第二类业务，采用和单播的DRX相同 的DRX配置和操作，也就是说现有NR系统中的DRX配置和操作也作用于第二类MBS业务数据。
优选地，第一类MBS业务的每个MBS业务的调度信息中包含了其对应的PTM DRX配置(如包含在MBS业务标识所关联的schedulingInfo信息元素中on duration定时器、drx-InactivityTimer定时器、调度周期SchedulingCycle或调度偏移SchedulingOffset)，而第二类MBS业务因为使用和现有单播业务一样的DRX配置(包含在MAC-CellGroupConfig信息元素中的DRX-config或drx-ConfigSecondaryGroup)，其调度信息中不包含对应的DRX配置。此时该实施例可以表述为：对于一个MBS业务，若其配置信息或调度信息中未被配置一个DRX配置，则UE对该MBS业务的接收采用单播对应的DRX配置，即对以MBS业务对应的标识如G-RNTI寻址的PDCCH监听采用单播对应的DRX配置。
具体而言，作为一例，图2是表示本公开的基于实施例1的非连续性接收方法的处理的流程图。
如图2所示，在步骤S201中，UE接收与多播和广播服务MBS业务相关的配置信息或调度信息。
接下来，在步骤S202中，UE判断所接收的配置信息或调度信息中是否配置有DRX配置。
接下来，在步骤S203中，在步骤S202中判断为上述配置信息或调度信息中未被配置DRX配置的情况下，UE对MBS业务的接收采用单播对应的DRX配置。
备选地，对于每一个MBS业务，其配置中可以包含一个指示信息，所述指示信息用于指示以该MBS业务对应的标识如G-RNTI寻址的PDCCH监听是否采用单播对应的DRX配置；或所述指示信息可以指示所述MBS业务是第一类业务还是第二类业务，若是第二类业务则以该MBS业务对应的标识如G-RNTI寻址的PDCCH监听采用单播对应的DRX配置。
对于上述方式，在现有NR系统用于单播的DRX机制中(见协议 规范38.321的5.7章节)，MAC实体可以由RRC实体配置一个DRX功能来控制UE对包含C-RNTI、CI-RNTI，CS-RNTI，INT-RNTI，SFI-RNTI，SP-CSI-RNTI，TPC-PUCCH-RNTI，TPC-PUSCH-RNTI，，TPC-SRS-RNTI和G-RNTI在内的UE标识的PDCCH监听活动。对于G-RNTI的PDCCH监听，MAC实体仅对其关联的配置信息中未配置一个PTM DRX配置或所示指示信息采用所配置的DRX功能。
实施例2
该实施例给出了一种在处于RRC连接态的UE上实现的基于上述用于MBS的DRX的实现方式3的一种非连续性接收方法。
在该实施例中，类似于LTE中SC-PTM的MBS接收和单播接收的DRX配置方式，NR系统中采用PTM方式接收的MBS业务对应DRX配置和单播对应的DRX配置是独立的。考虑到单播PTP通道用于接收PTM通道的MBS业务重传的接收方式，所以在该实施例中，单播的DRX操作中根据PTM通道的MBS业务的接收状态来操作。当收到一个以MBS业务标识如G-RNTI寻址的MAC PDU或PDCCH，且所述G-RNTI被配置了上行接收状态反馈时，UE MAC实体对于单播的DRX操作中进入激活时间，以监听来自PTP通道的MBS业务数据的重传对应的以所述C-RNTI(或CS-RNTI)寻址的PDCCH。优选地，当所收到一个以MBS业务标识如G-RNTI寻址的MAC PDU或PDCCH解码不成功时，UE MAC实体认为处于激活时间。优选地，所述G-RNTI被配置了MBS接收状态反馈也可以描述为所述G-RNTI被使能了对应MBS业务的反馈或所述G-RNTI被配置了相关联的上行反馈传输资源(如PUCCH配置)。所述反馈可以是HARQ反馈或L2反馈(无线链路控制层(Radio Link Control，RLC)或PDCP状态报告)。
实施例3
如前所述，在接收方式4中，基于不同的PTM和PTP的协议栈架构，所述PTP的重传可以是基于不同协议层的重传。该实施例基于 所述重传是MAC层的HARQ重传的协议栈架构(如图1中的A)对实施例2给出进一步的方法。在PTP通道上的重传是HARQ重传的情况下，PTM通道上的初传和PTP通道上的HARQ重传在同一个HARQ进程中进行，这样可以实现所述PTM通道上接收的初传传输块和PTP通道上接收的重传的传输块的HARQ合并。
当收到一个以MBS业务标识如G-RNTI寻址的MAC PDU或PDCCH、且所述G-RNTI被配置了上行接收状态反馈时，UE MAC实体对于单播的DRX操作中开启对应HARQ进程所关联的drx-HARQ-RTT-TimerDL定时器。当drx-HARQ-RTT-TimerDL定时器超时后，MAC实体开启对应的HARQ进程所关联的drxRetransmision-TimerDL定时器。优选地，MAC实体在相应的携带HARQ反馈的发送结束后的第一个符号启动对应的HARQ进程的drx-HARQ-RTT-TimerDL定时器。优选地，MAC实体在drx-HARQ-RTT-TimerDL定时器超时后的第一个符号启动相应的HARQ进程的drx-RetransmissionTimerDL定时器。当所述drxRetransmision-TimerDL定时器在运行时，UE认为处于激活时间内，以监听来自PTP通道的用于调度MBS业务数据的重传对应的以所述G-RNTI寻址的PDCCH。优选地，当所收到一个以MBS业务标识如G-RNTI寻址的MAC PDU或PDCCH解码不成功时，UE MAC实体开启对应的HARQ进程所关联的drxRetransmision-TimerDL定时器或drxRetransmision-TimerDL定时器。优选地，所述G-RNTI被配置了MBS接收状态反馈也可以描述为所述G-RNTI被使能了对应MBS业务的反馈或所述G-RNTI被配置了相关联的上行反馈传输资源(如PUCCH配置)。所述解码不成功也可以表述为UE反馈了NACK。
实施例4
如前所述，在接收方式4中，基于不同的PTM和PTP的协议栈架构，所述PTP的重传可以是基于不同协议层的重传。该实施例基于所述重传是MAC层之上的协议层的PDU的重传的协议栈架构(如图 1中的B)对实施例2给出进一步的方法。在这种情况下，PTM通道上的初传和PTP通道上的重传数据包不在同一个HARQ进程中进行，因此并不进行合并解码。对于PTM通道上的初传如果解码不成功，UE直接丢弃所收到的传输块。
当收到一个以MBS业务标识如G-RNTI寻址的MAC PDU或PDCCH、且所述G-RNTI被配置了上行接收状态反馈时，UE MAC实体对于单播的DRX操作中开启一个新定义的定时器T。当所述定时器T在运行时，UE认为处于激活时间内，以监听来自PTP通道的用于调度MBS业务数据的重传对应的以所述C-RNTI(或CS-RNTI)寻址的PDCCH。优选地，当所收到一个以MBS业务标识如G-RNTI寻址的MAC PDU或PDCCH解码不成功时，UE MAC实体开启定时器T。优选地，所述G-RNTI被配置了MBS接收状态反馈也可以描述为所述G-RNTI被使能了对应MBS业务的反馈或所述G-RNTI被配置了相关联的上行反馈传输资源(如PUCCH配置)。所述解码不成功也可以表述为UE反馈了NACK。
优选地，MAC实体在相应的携带HARQ反馈的发送结束后的第一个符号启动定时器T。备选地，MAC实体在相应的携带HARQ反馈的发送结束后的N个符号或毫秒之后启动定时器T。所述N可以由基站通过RRC配置，也可以是固定的常数值。
在该实施例中，所述定时器T是不区分HARQ进程的。所述定时器T的值可以由基站通过RRC配置。
实施例5
该实施例对本公开的用户设备UE进行说明。图3是表示本发明所涉及的用户设备UE的框图。如图3所示，该用户设备UE30包括处理器301和存储器302。处理器301例如可以包括微处理器、微控制器、嵌入式处理器等。存储器302例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器302上存储有程序指令。该指 令在由处理器301运行时，可以执行本发明中详细描述的上述非连续性接收方法等的各种方法。
本公开中，一些不同实施例之间可以协同工作，除非特别指出，实施例之间的概念或定义可以通用。
在本公开中，“基站”是指具有较大发射功率和较广覆盖面积的移动通信数据和控制交换中心，包括资源分配调度、数据接收发送等功能。“用户设备”是指用户移动终端，例如包括移动电话、笔记本等可以与基站或者微基站进行无线通信的终端设备。
上文已经结合优选实施例对本公开的方法和涉及的设备进行了描述。本领域技术人员可以理解，上面示出的方法仅是示例性的。本公开的方法并不局限于上面示出的步骤和顺序。上面示出的基站和用户设备可以包括更多的模块，例如还可以包括可以开发的或者将来开发的可用于基站、MME、或UE的模块等等。上文中示出的各种标识仅是示例性的而不是限制性的，本公开并不局限于作为这些标识的示例的具体信元。本领域技术人员根据所示实施例的教导可以进行许多变化和修改。
运行在根据本公开的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本公开的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本公开各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例 如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本公开的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本公开并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本公开并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本公开的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本公开也包括不偏离本公开主旨的任何设计改动。另外，可以在权利要求的范围内对本公开进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本公开的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种非连续性接收方法，包括：
    用户设备UE接收与多播和广播服务MBS业务相关的配置信息或调度信息；
    所述UE判断所述配置信息或调度信息中是否配置有非连续性接收DRX配置；
    在所述配置信息或调度信息中未被配置DRX配置的情况下，所述UE对所述MBS业务的接收采用单播对应的DRX配置。
  2. 根据权利要求1所述的非连续性接收方法，其中，
    所述UE采用单播对应的DRX配置，对以MBS业务标识寻址的PDCCH进行监听。
  3. 根据权利要求2所述的非连续性接收方法，其中，
    所述MBS业务标识是无线网络组标识G-RNTI，
    所述单播对应的DRX配置是包含在MAC小区组配置信息元素MAC-CellGroupConfig中的DRX配置。
  4. 一种非连续性接收方法，包括：
    在用户设备UE接收到以多播和广播服务MBS业务标识寻址的MAC PDU或PDCCH、且所述MBS业务标识被配置了上行接收状态反馈时，所述UE的MAC实体对于单播的非连续性接收DRX操作中进入激活时间，监听以UE特定标识寻址的PDCCH。
  5. 根据权利要求4所述的非连续性接收方法，其中，
    所述MBS业务标识是无线网络组标识G-RNTI；
    所述UE特定标识是小区无线网络临时标识C-RNTI或配置的调度无线网络临时标识CS-RNTI；
    所述单播对应的DRX操作是应用包含在MAC小区组配置信息元素MAC-CellGroupConfig中的DRX配置的DRX操作。
  6. 根据权利要求4或5所述的非连续性接收方法，其中，
    在所述UE接收到的以所述MBS业务标识寻址的MAC PDU或 PDCCH解码不成功时，所述UE的MAC实体认为处于激活时间。
  7. 根据权利要求4或5所述的非连续性接收方法，其中，
    在所述UE接收到以MBS业务标识寻址的MAC PDU或PDCCH、且所述MBS业务标识被配置了上行接收状态反馈时，所述UE的MAC实体对于单播的DRX操作中开启对应混合自动重传HARQ进程所关联的drx-HARQ-RTT-TimerDL定时器。
  8. 根据权利要求4或5所述的非连续性接收方法，其中，
    在所述drx-HARQ-RTT-TimerDL定时器超时后，所述UE的MAC实体开启对应的HARQ进程所关联的drxRetransmision-TimerDL定时器，
    在所述定时器drxRetransmision-TimerDL运行时，所述UE认为处于激活时间内。
  9. 根据权利要求4或5所述的非连续性接收方法，其中，
    在所述UE接收到以MBS业务标识寻址的MAC PDU或PDCCH、且所述MBS业务标识被配置了上行接收状态反馈时，所述UE的MAC实体对于单播的DRX操作中开启定时器T1，
    在所述定时器T1运行时，所述UE认为处于激活时间内，以监听以所述UE特定标识寻址的PDCCH。
  10. 一种用户设备UE，包括：
    处理器；以及
    存储器，存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求1至9中任一项所述的非连续性接收方法。
PCT/CN2021/124351 2020-10-20 2021-10-18 非连续性接收方法以及用户设备 WO2022083533A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/032,583 US20230388972A1 (en) 2020-10-20 2021-10-18 Discontinuous reception method and user equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011128470.8A CN114390446A (zh) 2020-10-20 2020-10-20 非连续性接收方法以及用户设备
CN202011128470.8 2020-10-20

Publications (1)

Publication Number Publication Date
WO2022083533A1 true WO2022083533A1 (zh) 2022-04-28

Family

ID=81193689

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/124351 WO2022083533A1 (zh) 2020-10-20 2021-10-18 非连续性接收方法以及用户设备

Country Status (3)

Country Link
US (1) US20230388972A1 (zh)
CN (1) CN114390446A (zh)
WO (1) WO2022083533A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116389940A (zh) * 2023-03-31 2023-07-04 广西上善若水发展有限公司 基于eDRX通讯技术的水表远程抄表方法

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220132277A1 (en) * 2020-10-22 2022-04-28 Samsung Electronics Co., Ltd. Methods and systems for energy efficient and synchronized reception of mbs in 5g communication network

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102651850A (zh) * 2011-02-25 2012-08-29 中兴通讯股份有限公司 实现mbms业务连续性的上报方法和用户设备
US20130114405A1 (en) * 2011-11-04 2013-05-09 Lg Electronics Inc. Method for receiving service at user equipment in wireless communication system and apparatus for the same
CN106031200A (zh) * 2014-03-13 2016-10-12 Lg电子株式会社 无线通信系统中发送用于公共报警系统的多媒体广播补充的方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102651850A (zh) * 2011-02-25 2012-08-29 中兴通讯股份有限公司 实现mbms业务连续性的上报方法和用户设备
US20130114405A1 (en) * 2011-11-04 2013-05-09 Lg Electronics Inc. Method for receiving service at user equipment in wireless communication system and apparatus for the same
CN106031200A (zh) * 2014-03-13 2016-10-12 Lg电子株式会社 无线通信系统中发送用于公共报警系统的多媒体广播补充的方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Overview of NR MBS work item", 3GPP DRAFT; R2-2007639, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic meeting; 20200817 - 20200828, 6 August 2020 (2020-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911087 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116389940A (zh) * 2023-03-31 2023-07-04 广西上善若水发展有限公司 基于eDRX通讯技术的水表远程抄表方法

Also Published As

Publication number Publication date
US20230388972A1 (en) 2023-11-30
CN114390446A (zh) 2022-04-22

Similar Documents

Publication Publication Date Title
US10375757B2 (en) Method and device for terminal performing PDCCH monitoring on SCPTM
JP6567560B2 (ja) Ｃ−ＤＲＸを用いてＳＰＳ構成のＶｏＬＴＥにおける電力節約を与える装置、方法、およびコンピュータプログラム製品
US10389493B2 (en) Terminal device, communication method, and integrated circuit
JP2021100258A (ja) ２ステップ・グラントでのアクティブ時間処理
WO2022083533A1 (zh) 非连续性接收方法以及用户设备
CN114845322A (zh) 无线通信系统中用于控制用户设备状态转变的方法和设备
EP4030867A1 (en) Method for configuring discontinuous reception setting and user equipment
WO2022078256A1 (zh) 无线连接控制方法以及用户设备
EP4294106A1 (en) Sidelink communication method and apparatus
WO2022078384A1 (zh) 用户设备执行的传输方法、用户设备、基站以及基站执行的传输方法
WO2022078328A1 (zh) 用户设备执行的传输方法、用户设备、基站以及基站执行的传输方法
EP3308501B1 (en) Method and apparatus for group communication in wireless communication system
US20230363051A1 (en) Discontinuous reception control method and apparatus
US20230224090A1 (en) Method and apparatus for handling discontinuous reception (drx) timer for data reception of unicast and multicast in a wireless communication system
WO2022082593A1 (zh) 通信方法及装置
TW202247678A (zh) 針對nr多播和廣播服務的bwp操作
CN116803155A (zh) 用于管理drx和wus操作以接收mbs服务的方法和系统
WO2023207568A1 (zh) 一种通信方法及装置
WO2023065224A1 (en) Discontinuous reception for multicast and broadcast service
EP4354777A1 (en) Method and apparatus of handling discontinuous reception (drx) timer for multicast data reception in a wireless communication system
US20240080935A1 (en) Communication control method and user equipment
WO2022184045A1 (zh) 多播业务的接收方法、装置及电子设备
WO2023036165A1 (zh) 一种被用于无线通信的方法和设备
US20240187823A1 (en) Method and apparatus for new radio multicast broadcast service receiption
CN117580194A (zh) 由用户设备执行的处理寻呼消息的方法及用户设备

Legal Events

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

Ref document number: 21881950

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18032583

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21881950

Country of ref document: EP

Kind code of ref document: A1