WO2024032500A1 - 由用户设备执行的方法以及用户设备 - Google Patents

由用户设备执行的方法以及用户设备 Download PDF

Info

Publication number
WO2024032500A1
WO2024032500A1 PCT/CN2023/111227 CN2023111227W WO2024032500A1 WO 2024032500 A1 WO2024032500 A1 WO 2024032500A1 CN 2023111227 W CN2023111227 W CN 2023111227W WO 2024032500 A1 WO2024032500 A1 WO 2024032500A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
mrb
rrc
indication identifier
mbs
Prior art date
Application number
PCT/CN2023/111227
Other languages
English (en)
French (fr)
Inventor
肖芳英
刘仁茂
Original Assignee
夏普株式会社
肖芳英
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 夏普株式会社, 肖芳英 filed Critical 夏普株式会社
Publication of WO2024032500A1 publication Critical patent/WO2024032500A1/zh

Links

Classifications

    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present invention relates to the field of wireless communication technology, and more specifically, the present invention relates to a method executed by user equipment and the user equipment.
  • a research project SI (see SP-190625 for details) on the improvement of 5G multicast broadcast service architecture has been approved.
  • Objective A is to support universal MBS services in 5GS.
  • Use cases that can benefit from this feature include (but are not limited to) public safety, V2X applications, transparent IPv4/IPv6 multicast transport, IPTV, Wireless software transmission, group communication and Internet of Things applications, etc.
  • 3GPP 3rd Generation Partnership Project
  • RAN#86 plenary meeting the work item of NR multicast and broadcast service (NR MBS) was proposed (see non-patent document: RP-193248: New WID: NR Multicast and Broadcast Service) was approved.
  • This work item aims to provide support for Objective A in RAN.
  • the goal of this work project has been achieved.
  • 3GPP version 17 technical documents such as TS38.300-h10, TS38.331-h10, TS38.321-h10, etc.
  • a work item called Enhanced NR Broadcast Multicast was approved (see non-patent document: RP-213568: New WID: Enhancements of NR Multicast and Broadcast Services), aiming to implement version 17 MBS broadcast multicast is further enhanced.
  • One of the goals of this work item is to support user equipment in the RRC inactive state to receive multicast services.
  • This invention discusses the relevant issues involved in the RAN achieving support for user equipment in the RRC inactive state to receive multicast services.
  • the object of the present invention is to provide a method executed by user equipment and user equipment that can support user equipment in an RRC inactive state to receive multicast services.
  • a method performed by user equipment UE including: Receive a radio resource control RRC message from the base station; and in the case where the received RRC message contains an indication identifier for instructing the UE to receive a multicast broadcast service MBS session after entering the RRC inactive state, the UE performs and receives the The operation related to the MBS session indicated by the indication identifier.
  • a user equipment including: a processor; and a memory storing instructions; wherein the instructions execute the above method when executed by the processor.
  • user equipment in an RRC inactive state can be supported to receive multicast services, thereby saving communication resources and improving communication efficiency.
  • FIG. 1 are schematic diagrams showing specific configurations of radio bearers for receiving MBS services according to the present invention.
  • Figure 2 is a flowchart showing a method in user equipment UE based on an embodiment of the present invention.
  • FIG. 3 is a block diagram showing user equipment UE according to an embodiment of the present invention.
  • UE User Equipment, user equipment.
  • RRC Radio Resource Control, wireless resource control.
  • RRC_CONNECTED RRC connected state.
  • RRC_INACTIVE RRC inactive state.
  • RRC_IDLE RRC idle state.
  • RAN Radio Access Network, wireless access network.
  • New RAT new wireless access technology.
  • MBS Multicast/Broadcast Services, multicast/broadcast services.
  • PDCP Packet Data Convergence Protocol, packet data convergence protocol.
  • RLC Radio Link Control, wireless link control.
  • SDU Service Data Unit, service data unit.
  • SDUs Service Data Unit
  • PDU Protocol Data Unit, protocol data unit.
  • the data packets that this layer receives from or delivers to the lower layer are called PDUs.
  • PDCP data PDU is a data packet obtained by adding a PDCP header to PDCP SDU.
  • RB Radio Bearer, wireless bearer.
  • MRB MBS radio bearer, that is, a radio bearer that is configured for MBS delivery (Aradio bearer that is configured for MBS delivery).
  • TMGI Temporary Mobile Group Identity, temporary mobile group identifier, used to identify an MBS session.
  • RNTI Radio Network Temporary Identifier, wireless network temporary identifier.
  • PTM Point to Multipoint, point to multipoint, a delivery method for MBS services.
  • the base station delivers a single copy of MBS data packets to a set of UEs (gNB delivers a single copy of MBS data packets to a set of UEs).
  • gNB delivers a single copy of MBS data packets to a set of UEs.
  • the base station uses the G-RNTI scrambled group common physical downlink control channel PDCCH to schedule the same G-RNTI scrambled group common physical downlink shared channel PDSCH.
  • PTP Point to Point, point to point, a delivery method for MBS services.
  • the RAN node delivers copies of multiple MBS data packets to each UE individually (gNB individually delivers separate copies of MBS data packets to each UEs independently), that is, the base station uses UE-specific RNTI scrambling for UE-specific PDCCH scheduling uses the same UE-specific RNTI scrambled UE-specific PDSCH.
  • G-RNTI Group RNTI, group RNTI, used to scramble the scheduling and transmission of one or more MBS multicast services of PTM (Used to scramble the scheduling and transmission of PTM for one or more MBS multicast services).
  • G-CS-RNTI Group Configured Scheduling RNTI, group configuration scheduling RNTI.
  • network can be used interchangeably.
  • the network can be a Long Term Evolution LTE network, a NR network, an enhanced Long Term Evolution eLTE network, or other networks defined in subsequent evolution versions of 3GPP.
  • MBS broadcast provides a downlink-only MBS transmission mode for services with low service quality QoS, so that UEs in RRC connected state, RRC idle state and RRC inactive state can receive the MBS service.
  • the UE receives MBS broadcast through the broadcast control channel MCCH.
  • MBS multicast requires the UE to establish an RRC connection with the base station, and then the base station configures the UE through dedicated RRC signaling (also called RRC message), and the radio bearer MRB that receives these MBS services (or MBS multicast sessions) can also be configured by the base station through a dedicated RRC signaling is configured for the UE. Only the UE in the RRC connected state and configured with MRB can receive the corresponding MBS service.
  • MBS sessions include MBS broadcast sessions and MBS multicast sessions. Unless otherwise specified, the MBS session in the embodiment of the present disclosure is an MBS multicast session.
  • FIG. 1 are schematic diagrams showing the specific configuration of a radio bearer that receives MBS multicast.
  • the wireless bearer may be an MRB configured with only PTM transmission (as shown in Figure 1 (a)), or a split MRB (split MRB) configured with both PTM and PTP (as shown in Figure 1 (b)) Or only the MRB for PTP transmission is configured (as shown in (c) of Figure 1).
  • (a)-(c) of Figure 1 only show the bearer corresponding PDCP entity and RLC entity and the relationship between the two. In the downlink direction, the PDCP PDU encapsulated by the PDCP entity is delivered to the RLC entity.
  • the RRC reconfiguration message is a command used to modify an RRC connection.
  • the RRC release message is used to command the release of an RRC connection or the suspension of an RRC connection. Both messages are sent by the base station to the UE. . If the RRC release message contains the field suspendConfig indicating the configuration of the RRC inactive state, the UE shall follow the configuration in the field. Suspend the RRC connection, otherwise the UE releases the RRC connection.
  • the embodiments of this disclosure discuss how to configure PTM or MRB for a UE in the RRC inactive state, so the following embodiments all consider the situation where the RRC release message contains the suspendConfig field.
  • the indication identifier used to indicate the MBS session received after the UE enters the RRC inactive state may be included in the suspendConfig field.
  • the present disclosure provides the following embodiments.
  • Figure 2 is a flowchart showing a method in user equipment UE based on an embodiment of the present invention.
  • step S201 the user equipment UE receives an RRC message from the base station, which contains an indication identifier for indicating the MBS session received after the UE enters the RRC inactive state.
  • step S202 based on the received RRC message, the user equipment UE performs operations related to receiving the MBS session indicated by the indication identifier, for example, performs at least one of operations A-C:
  • RRC message contains the indication identifier, perform a partial MAC reset; if the RRC message does not contain the indication identifier, perform a MAC reset and/or release the default MAC cell group configuration. (This operation is performed only when there is a default MAC cell group configuration).
  • the transmitting PDCP entity may set the state variable TX_NEXT used to indicate the COUNT value of the next PDCP SDU to be transmitted to the initial value and/or Delete (discard) all stored PDCP PDUs.
  • the receiving PDCP entity can determine whether the timer t-Reordering configured by the upper layer to control waiting for unarrived PDCP SDUs is running. , if the timer is running, stop and reset the timer and/or perform header decompression of all stored PDCP SDUs and deliver them to the upper layer in order from small to large COUNT values,
  • the receiving PDCP entity can also be configured to indicate the next The values of the state variable RX_NEXT for the COUNT value of the PDCP SDU that is expected to be received and the state variable RX_DELIV used to indicate the COUNT value of the first PDCP SDU that has not been submitted to the upper layer (such as the Service Data Adaptation Protocol SDAP entity) are initial values.
  • COUNT is composed of the superframe number HFN and the PDCP sequence number SN.
  • the UE indicates to the upper layer (for example, the NAS layer) the TMGI corresponding to the MBS session indicated by the indication identifier or the TMGI corresponding to the MRB indicated by the indication identifier or the TMGI indicated by the indication identifier.
  • the upper layer for example, the NAS layer
  • the UE indicates to the lower layer (for example, the media access control MAC layer) the G-RNTI or G-CS-RNTI or MRB identifier corresponding to the MBS session or MRB received when the RRC is in the inactive state.
  • the lower layer for example, the media access control MAC layer
  • the G-RNTI or G-CS-RNTI or MRB identifier corresponding to the MBS session or MRB received when the RRC is in the inactive state.
  • TMGI When the MAC layer receives the indication or is configured with an MBS session or MRB received in an inactive state, it may monitor the G-RNTI corresponding to the MBS session configured to be received in an inactive state.
  • the UE will enter the When the RRC release message is in the RRC inactive state (or the RRC layer), it is considered or indicates to the lower layer (such as the MAC layer) that HARQ feedback is not enabled or HARQ feedback is not required or HARQ feedback is disabled.
  • the MAC layer Upon receiving the indication or when the UE is in the inactive state, the MAC layer does not perform HARQ feedback (or does not instruct the physical layer to generate a response to the received TB) for the MBS session (or MRB) configured to be received in the inactive state. Acknowledgment), in other words, for an MBS session configured to require HARQ feedback, HARQ feedback is only performed when the UE is in the RRC connected state (or the UE is not in the RRC inactive state).
  • the MAC reset described in this disclosure may include at least one of the following operations:
  • the next received transmission block is considered to be the first transmission.
  • the MAC partial reset described in this disclosure may include at least one of the following operations:
  • the next received transmission block is considered to be the first transmission.
  • step S201 and step S202 may be the RRC entity of the UE.
  • user equipment in the RRC inactive state can be supported to receive multicast services, thereby saving communication resources and improving communication efficiency.
  • MBS multicast supports two hybrid automatic repeat request HARQ feedback modes.
  • One of the HARQ feedback modes is ACK-NACK feedback, that is, when the UE correctly receives the transport block, the HARQ-ACK information is transmitted on the physical uplink control channel PUCCH and when HARQ-NACK information is transmitted on the PUCCH when the UE does not receive the transport block correctly;
  • another HARQ feedback mode is NACK feedback (nack-only), that is, HARQ-NACK information is transmitted on the PUCCH only when the UE does not receive the transport block correctly.
  • the base station configures whether HARQ feedback is required for each MBS session or G-RNTI or G-CS-RNTI through the RRC reconfiguration message.
  • the field harq-FeedbackEnablerMulticast is used to indicate whether the UE should provide HARQ feedback for MBS multicast (or receive a transport block scrambled by this G-RNTI). Furthermore, the feedback mode for the UE can also be configured as NACK feedback only or ACK-NACK feedback, which is configured through the harq-FeedbackOptionMulticast field.
  • the harq-FeedbackOptionMulticast field indicates the feedback mode of dynamically scheduled physical downlink shared channel PDSCH or semi-statically scheduled SPS PDSCH MBS multicast.
  • the MRB or MBS session or TMGI or G-RNTI or G-CS-RNTI indicated by the indication identifier may be defined as the MRB or MBS session or TMGI or G-RNTI or G-CS-RNTI for which HARQ feedback is not configured, that is, it is not configured.
  • the indication indicates that the MRB or MBS session or TMGI or G-RNTI or G-CS-RNTI received in the inactive state is the MRB or MBS session or TMGI or G-RNTI or G with HARQ feedback configured, -CS-RNTI, when the UE enters the RRC inactive state, it does not perform HARQ feedback of the corresponding MRB or MBS or indicates that HARQ feedback is not required.
  • the RRC message carrying the indication identifier and the indication manner of the indication identifier are described in detail below through different embodiments.
  • the base station sends the RRC reconfiguration message RRCReconfiguration to the UE to configure the MRB used to transmit the MBS session for the UE in the RRC connected state, and carries an indicator in the RRC release message RRCRelease sent to the UE to indicate that the UE enters the RRC inactive state. Post-collection MBS session.
  • the indication identifier field contains an MRB identifier list (denoted as ptmReceptionInInactiveList field). If the MRB identifier corresponding to an MBS session is included in the indication identifier, it means that the UE needs to receive the MBS session after entering the RRC inactive state. Or the MRB corresponding to the MRB identifier.
  • the RRC release message does not contain the indication identifier, perform MAC reset and/or release the default MAC cell group configuration (this operation is performed only when there is a default MAC cell group configuration).
  • the indication identifier field indicates Do not suspend (suspend) MRB.
  • the indication identifier includes an MRB identifier list. If the MRB identifier corresponding to an MBS session is not included in the indication identifier, it means that the UE needs to receive the MRB corresponding to the MBS session or the MRB identifier after entering the RRC inactive state. In other words, when the UE receives an indication to enter the RRC inactive state, it suspends the MRB contained in the indication identifier or suspends other RBs except SRB0 and/or MRBs not indicated by the indication identifier field), that is, the indication identifier Indicates the MRB to suspend.
  • the indication identifier contains a TMGI list. If the TMGI corresponding to an MBS session is included in the indication identifier, it means that the UE needs to receive the MRB corresponding to the MBS session or the TMGI after entering the RRC inactive state.
  • the UE when the UE receives an indication to enter the RRC inactive state, it does not suspend the MRB corresponding to the TMGI contained in the indication identifier (or suspend other RBs except SRB0 and/or the indication identifier indication), that is, the indication
  • the flag indicates the TMGI corresponding to the MRB that is not suspended.
  • the UE when the RRC release message received by the UE contains suspendConfig, and if the RRC release message also contains the indication identifier, the UE performs at least one of the following operations:
  • the RRC release message does not contain the indication identifier, perform MAC reset and/or release the default MAC cell group configuration (this operation is performed only when there is a default MAC cell group configuration).
  • the indication mark includes a TMGI list. If the TMGI corresponding to an MBS session is not included in the indication mark, it means that the UE needs to receive the MRB corresponding to the MBS session or the TMGI after entering the RRC inactive state. In other words, when the UE receives an indication to enter the RRC inactive state, it suspends the MRB corresponding to the TMGI contained in the indication identifier or suspends other RBs except SRB0 and/or the MRB corresponding to the TMGI not indicated by the indication identifier. ), that is, the indication flag indicates the TMGI corresponding to the MRB to be suspended.
  • the indication identifier contains a G-RNTI or G-CS-RNTI list. If the G-RNTI or G-CS-RNTI corresponding to an MBS session is included in the indication identifier, it indicates that the UE is entering RRC deactivation. After entering the state, it is necessary to receive the MRB corresponding to the MBS session or the G-RNTI or G-CS-RNTI. Among them, G-CS-RNTI is used to scramble the semi-statically scheduled SPS group public PDSCH and activate/deactivate the SPS group public PDSCH of one or more MBS multicast services.
  • the UE when the UE receives an indication to enter the RRC inactive state, it does not suspend the MRB corresponding to the G-RNTI or G-CS-RNTI contained in the indication identifier (or suspends the MRB except SRB0 and/or the indication identifier indication. (other than other RBs), that is, the indication flag indicates the G-RNTI or G-CS-RNTI corresponding to the MRB that is not suspended.
  • the UE when the RRC release message received by the UE contains suspendConfig, and if the RRC release message also contains the indication identifier, the UE performs at least one of the following operations:
  • the RRC release message does not contain the indication identifier, perform MAC reset and/or release the default MAC cell group configuration (this operation is performed only when there is a default MAC cell group configuration).
  • the indication identifier contains a G-RNTI or G-CS-RNTI list. If the G-RNTI or G-CS-RNTI corresponding to an MBS session is not included in the indication identifier, it means that the UE enters the RRC inactive state. It is necessary to receive the MRB corresponding to the MBS session or the G-RNTI or G-CS-RNTI. In other words, when the UE receives an indication to enter the RRC inactive state, it suspends the MRB corresponding to the G-RNTI or G-CS-RNTI included in the indication identifier or suspends all MRBs except SRB0 and/or the MRB not indicated by the indication identifier. RB other than the MRB corresponding to the G-RNTI or G-CS-RNTI), that is, the indication indicator indicates the G-RNTI or G-CS-RNTI corresponding to the MRB to be suspended.
  • the indication mark includes a bitmap, and each bit in the bitmap corresponds to an MRB (or each bit in the bitmap corresponds to an MBS session or MRB that is not configured to require HARQ feedback).
  • the MRB identifiers correspond to the bits in the bitmap in ascending order.
  • the value of the corresponding bit in the bitmap is 1, indicating that the UE needs to receive the MBS session corresponding to the MRB identifier or receive the MRB corresponding to the MRB identifier after entering the RRC inactive state.
  • the value of the corresponding bit in the bitmap is 0, indicating that the UE does not receive the MBS session corresponding to the MRB identifier or does not receive the MRB corresponding to the MRB identifier after entering the RRC inactive state.
  • the UE when the UE receives an indication to enter the RRC inactive state, it does not suspend the MRB whose corresponding bit in the bitmap has a value of 1 (or suspends the MRB except SRB0 and/or the MRB whose corresponding bit in the bitmap has a value of 1).
  • Other RBs that is, the corresponding bit in the bitmap has a value of 1 to indicate a non-suspended MRB, and a value of 0 indicates a suspended MRB.
  • the RRC release message received by the UE contains suspendConfig
  • the RRC release message also contains the bitmap, then perform at least one of the following operations:
  • bitmap method can save signaling overhead.
  • the indication mark includes a bitmap, and each bit in the bitmap corresponds to an MRB (or each bit in the bitmap corresponds to an MBS session or MRB that is not configured to require HARQ feedback).
  • the MRB identifiers correspond to the bits in the bitmap in ascending order.
  • the corresponding bit in the bitmap has a value of 1, indicating that the UE does not need to receive the MBS session or the MRB corresponding to the MRB identifier after entering the RRC inactive state.
  • the UE when the UE receives an indication to enter the RRC inactive state, it suspends the MRB corresponding to the bit of 1 in the bitmap, that is, the MRB whose indication flag indicates the suspension.
  • the indication flag is used to instruct the UE to still receive MBS sessions or MRBs that are not configured to require HARQ feedback after entering the RRC inactive state.
  • the UE does not suspend the MRB corresponding to the MBS session that is not configured to require HARQ feedback or the UE does not suspend the MRB that is not configured to require HARQ feedback. That is, when the received RRC message contains the indication identifier, the UE suspends the configuration of the MRB corresponding to the MBS session that requires HARQ feedback or the UE suspends the configuration of the MRB that requires HARQ feedback.
  • the received RRC release message contains suspendConfig
  • the RRC release message also contains an indicator indicating that the UE receives an MRB or MBS session configured to not require HARQ feedback in the inactive state, perform the following operations At least one of A-C:
  • the RRC release message does not contain the indication identifier, perform MAC reset and/or release the default MAC cell group configuration (this operation is performed only when there is a default MAC cell group configuration).
  • the base station uses the RRC reconfiguration message to configure the MRB for transmitting the MBS session for the UE in the RRC connected state, and includes an indicator in the corresponding MRB configuration field to indicate whether to receive the MRB when the UE enters the RRC inactive state. MRB.
  • the UE When the RRC release message received by the UE contains suspendConfig, if at least one MRB is configured with the indication identifier, the UE performs at least one of the following operations:
  • the base station includes an indication identifier through the RRC reconfiguration message, which is used to indicate the G-RNTI, G-CS-RNTI or TMGI corresponding to the MBS session or MRB received by the UE in the RRC inactive state.
  • the MRB received in the RRC inactive state described in Embodiment 2 is the MRB corresponding to the G-RNTI, G-CS-RNTI or TMGI corresponding to the MBS session or MRB indicated by the indication identifier.
  • the base station uses the RRCRelease message to configure the UE and instruct the MRB to transmit the MBS session to the UE in the RRC connected state.
  • the UE in the RRC inactive state sends a request to the base station to resume a suspended RRC connection due to receiving MBS multicast (for example, receiving a paging message containing the TMGI corresponding to one or more MBS sessions that the UE has joined). Or the RRC Resume Request message RRCResumeRequest used to perform RAN-based notification area (RNA) update.
  • the message contains a reason field ResumeCause, whose value is the TMGI of one or more MBS sessions that the UE wants to receive or for Indicates that the UE wants to receive the MBS session and trigger the sending of a value corresponding to the RRC connection resumption request.
  • the UE receives an RRC release message containing a suspendConfig field from the base station, where the message contains configuration information indicating the MRB of the MBS session received by the UE in the inactive state.
  • the UE configures the corresponding MRB according to the configuration information and receives the corresponding MBS session.
  • FIG. 3 is a block diagram showing user equipment UE30 based on an embodiment of the present invention.
  • 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 (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.
  • Memory 302 stores program instructions. When this instruction is executed by the processor 301, the above method in the user equipment described in detail in the present invention can be executed.
  • computer-executable instructions or programs running on the device according to the present invention may be programs that enable the computer to implement the functions of the embodiments of the present invention 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 various embodiments of the present invention may be recorded on a computer-readable storage medium. Corresponding functions can be realized by causing the computer system to read programs recorded on the recording medium and execute these programs.
  • the so-called "computer system” here This may be a computer system embedded in the device, which may include an operating system or hardware (such as peripheral devices).
  • a "computer-readable storage medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium for short-term dynamic storage of a program, or any other recording medium readable by a computer.
  • circuits eg, single-chip or multi-chip integrated circuits.
  • Circuitry designed to perform the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • a general-purpose processor can be a microprocessor or any existing processor, controller, microcontroller, or state machine.
  • the above circuit may be a digital circuit or an analog circuit.
  • the present invention is not limited to the above-described embodiment. Although various examples of the embodiments have been described, the invention is not limited thereto.
  • Fixed or non-mobile electronic equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, such as AV equipment, kitchen equipment, cleaning equipment, air 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

本发明提供一种由用户设备执行的方法以及用户设备，由用户设备UE执行的方法包括：从基站接收无线资源控制RRC消息；以及在接收到的所述RRC消息中包含用于指示UE进入RRC非激活态后接收的多播广播业务MBS会话的指示标识的情况下，UE执行与接收所述指示标识指示的MBS会话相关的操作。由此，能够支持RRC非激活态的用户设备接收多播业务，从而能够节省通信资源，提高通信效率。

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的支持。该工作项目的目标已达成，相关方案的具体描述见相关的3GPP版本17技术文档，例如TS38.300-h10、TS38.331-h10、TS38.321-h10等。在3GPP RAN#94次全会上，一项名为增强的NR广播多播工作项目被批准(参见非专利文献：RP-213568：New WID：Enhancements of NR Multicast and Broadcast Services)，旨在对版本17的MBS广播多播进一步增强。该工作项目的目标之一为支持RRC非激活态的用户设备接收多播业务。
本发明讨论RAN达成支持RRC非激活态的用户设备接收多播业务所涉及的相关问题。
发明内容
本发明的目的在于，提供能够支持RRC非激活态的用户设备接收多播业务的由用户设备执行的方法以及用户设备。
根据本发明的一个方面，提供一种由用户设备UE执行的方法，包括： 从基站接收无线资源控制RRC消息；以及在接收到的所述RRC消息中包含用于指示UE进入RRC非激活态后接收的多播广播业务MBS会话的指示标识的情况下，UE执行与接收所述指示标识指示的MBS会话相关的操作。
根据本发明的另一方面，提供一种用户设备，包括：处理器；以及存储器，存储有指令；其中，所述指令在由所述处理器运行时执行上述方法。
发明效果
根据本发明的由用户设备执行的方法以及用户设备，能够支持RRC非激活态的用户设备接收多播业务，从而能够节省通信资源，提高通信效率。
附图说明
通过下文结合附图的详细描述，本发明的上述和其它特征将会变得更加明显，其中：
图1的(a)～(c)是表示本发明涉及的接收MBS业务的无线承载的具体配置的示意图。
图2是表示基于本发明的实施例的用户设备UE中的方法的流程图。
图3是表示基于本发明的实施例的用户设备UE的框图。
具体实施方式
下面结合附图和具体实施方式对本发明进行详细阐述。应当注意，本发明不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本发明没有直接关联的公知技术的详细描述，以防止对本发明的理解造成混淆。
下面描述本发明涉及的部分术语，术语的具体含义可参见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，新无线接入技术。
MBS：Multicast/Broadcast Services，多播/广播业务。
PDCP：Packet Data Convergence Protocol，分组数据汇聚协议。
RLC：Radio Link Control，无线链路控制。
SDU：Service Data Unit，服务数据单元。将本层从上层接收或递交上层的数据包称为SDU。
PDU：Protocol Data Unit，协议数据单元。将本层从下层接收或递交下层的数据包称为PDU。例如，PDCP数据PDU是PDCP SDU增加PDCP报头后得到的数据包。
RB：Radio Bearer，无线承载。
MRB：MBS无线承载，即一个配置用于MBS传输的无线承载(Aradio bearer that is configured for MBS delivery)。
TMGI：Temporary Mobile Group Identity，临时移动组标识，用于标识一个MBS会话。
RNTI：Radio Network Temporary Identifier，无线网络临时标识。
PTM：Point to Multipoint，点到多点，一种MBS业务的递送(deliver)方式。在PTM递送方式中，基站将一份MBS数据包送给一组UE(gNB delivers a single copy of MBS data packets to a set of UEs)。例如，基站采用G-RNTI加扰的群组公共物理下行控制信道PDCCH调度相同的G-RNTI加扰的群组公共物理下行共享信道PDSCH。
PTP：Point to Point，点到点，一种MBS业务的递送方式。在PTP递送方式中，RAN节点将多个MBS数据包的副本分别单独递送给每个UE(gNB individually delivers separate copies of MBS data packets to each UEs independently)，即基站采用UE专用RNTI加扰的UE专用PDCCH调度采用相同的UE专用RNTI加扰的UE专用PDSCH。
G-RNTI：Group RNTI，群组RNTI，用于加扰PTM的一个或多个MBS组播业务的调度和传输(Used to scramble the scheduling and transmission of  PTM for one or more MBS multicast services)。
G-CS-RNTI：Group Configured Scheduling RNTI，群组配置调度RNTI。
本发明中，网络、基站和RAN可互换使用，所述网络可以是长期演进LTE网络、NR网络、增强的长期演进eLTE网络，也可以是3GPP后续演进版本中定义的其他网络。
目前，NR MBS业务包含MBS广播(或MBS广播会话)和MBS多播(或MBS多播会话)。MBS广播面向低服务质量QoS的业务提供仅下行的MBS传输模式，使得处于RRC连接态、RRC空闲态和RRC非激活态的UE均可以接收所述MBS业务，UE通过广播控制信道MCCH接收MBS广播的MBS配置。MBS多播需要UE与基站建立RRC连接，然后基站通过专用RRC信令(也称为RRC消息)为UE配置，并且接收这些MBS业务(或MBS多播会话)的无线承载MRB也可由基站通过专用RRC信令为UE配置，仅处于RRC连接态并且配置了MRB的UE才可以接收对应的MBS业务。
MBS会话包括MBS广播会话和MBS多播会话，如未特别说明，本公开实施例中所述MBS会话是MBS多播会话。
图1的(a)～(c)是表示接收MBS多播的无线承载的具体配置的示意图。所述无线承载可以是仅配置了PTM传输的MRB(如图1的(a)所示)，或者同时配置了PTM和PTP的分离MRB(split MRB)(如图1的(b)所示)或者仅配置了PTP传输的MRB(如图1的(c)所示)。需要说明的是，图1的(a)-(c)仅示出了承载对应的PDCP实体和RLC实体以及两者间的关系。在下行方向上，经PDCP实体封装后的PDCP PDU递交给RLC实体。
如果要实现处于RRC非激活态的UE也能像处于RRC连接态的UE一样采用PTM方式接收MBS多播业务，如何为处于非激活态的UE配置对应的MRB或PTM是需要解决的问题。
RRC重配置消息是用于修改一个RRC连接的指令(command)，RRC释放消息被用于命令释放一个RRC连接或挂起(suspension of)一个RRC连接，这两条消息都是由基站向UE发送。如果RRC释放消息中包含指示RRC非激活态的配置的字段suspendConfig，则UE按照所述字段中的配置 挂起RRC连接，否则UE释放RRC连接。本公开实施例讨论的是如何为处于RRC非激活态的UE配置PTM或MRB，故以下实施例均考虑RRC释放消息中包含suspendConfig字段的情形。此外，如未特别说明，用于指示在UE进入RRC非激活态后接收的MBS会话的指示标识均可包含在suspendConfig字段中。
针对上述问题，本公开提供以下实施例。
图2是表示基于本发明的实施例的用户设备UE中的方法的流程图。
在步骤S201中，用户设备UE接收来自基站的RRC消息，其中包含一个指示标识用于指示在UE进入RRC非激活态后接收的MBS会话。
在步骤S202中，基于接收到的所述RRC消息，用户设备UE执行与接收指示标识指示的MBS会话相关的操作，例如，执行操作A-C中的至少一项：
A.如果所述RRC消息中包含所述指示标识，则执行MAC部分重置；如果所述RRC消息中不包含所述指示标识，则执行MAC重置和/或释放缺省的MAC小区组配置(存在缺省的MAC小区组配置时才执行此操作)。
B.挂起(suspend)除SRB0和根据所述指示标识确定的在RRC非激活态下接收的多播MRB外的所有SRB和DRB和多播MRB。
C.向下层(例如PDCP层)指示除根据所述指示标识确定的在非激活态下接收的多播MRB外的所有DRB和多播MRB的PDCP挂起。在接收到来自上层(例如RRC层)的请求PDCP挂起时，发送PDCP实体(transmitting PDCP entity)可设置用于指示下一个将要传输的PDCP SDU的COUNT值的状态变量TX_NEXT为初始值和/或删除(discard)所有存储的PDCP PDU。在接收到来自上层(例如RRC层)的请求PDCP挂起时，接收PDCP实体(receiving PDCP entity)可确定由上层配置的用于控制等待未到达的PDCP SDU的时长定时器t-Reordering是否正在运行，如果所述定时器正在运行，停止并重置所述定时器和/或将所有存储的PDCP SDU执行头解压缩(header decompression)后按照COUNT值从小到大的顺序依次递交(deliver)上层，接收PDCP实体还可以设置用于指示下一个 期望接收到的PDCP SDU的COUNT值的状态变量RX_NEXT和用于指示第一个尚未递交上层(例如服务数据适配协议SDAP实体)的PDCP SDU的COUNT值的状态变量RX_DELIV的值为初始值。其中COUNT是由超帧号HFN和PDCP序列号SN组成。
可选的，UE(或RRC层)向上层(例如，NAS层)指示指示标识指示的MBS会话对应的TMGI或指示标识指示的MRB对应的TMGI或指示标识指示的TMGI。
可选的，UE(或RRC层)向下层(例如，媒体接入控制MAC层)指示处于RRC非激活态时接收的MBS会话或MRB对应的G-RNTI或G-CS-RNTI或MRB标识或TMGI。MAC层在接收到所述指示或被配置了非激活态下接收的MBS会话或MRB时，可以监听配置为非激活态下接收的MBS会话对应的G-RNTI。
可选的，对于被配置在RRC非激活态下接收的MBS会话或MRB，如果对应的MBS会话或G-RNTI或G-CS-RNTI或TMGI被配置为需要HARQ反馈，UE在接收到指示进入RRC非激活态的RRC释放消息时(或RRC层)认为或向下层(例如MAC层)指示HARQ反馈未被使能或不需要HARQ反馈或HARQ反馈被去使能。MAC层在接收到所述指示或当UE处于非激活态时，针对被配置为非激活态下接收的MBS会话(或MRB)不执行HARQ反馈(或不指示物理层产生对接收到的TB的确认(acknowledgement))，换言之，对于配置了需要HARQ反馈的MBS会话，只有在UE处于RRC连接态(或UE不处于RRC非激活态)才执行HARQ反馈。
本公开所述MAC重置(或UE未被配置RRC非激活态下可接收的MBS会话时MAC实体执行的MAC重置操作)可包括以下操作中的至少一项：
1.停止除MBS广播非持续接收DRX定时器外的所有定时器。
2.设置所有上行HARQ进程的新数据指示NDI的值为0。
3.停止正在进行的随机接入过程。
4.清空除用于MBS广播和下行HARQ进程外的所有下行进程的软缓存(soft buffer)。
5.对于每个下行HARQ进程，认为下一个接收到的传输块是第一次传输。
本公开所述MAC部分重置(或UE被配置了RRC非激活态下可接收的MBS会话时MAC实体执行的MAC重置或MAC部分重置操作)可包括以下操作中的至少一项：
1.停止除MBS广播非持续接收DRX定时器和被配置为RRC非激活态下可接收的MBS会话对应的DRX定时器外的所有定时器。
2.清空除用于MBS广播的下行HARQ进程和用于RRC非激活态下可接收的MBS会话的下行HARQ进程外的所有下行进程的软缓存。
3.设置所有上行HARQ进程的新数据指示NDI的值为0。备选的，设置除被配置为RRC非激活态下可接收的MBS会话对应的上行HARQ进程外的所有上行HARQ进程的新数据指示NDI的值为0。
4.对于除被配置为RRC非激活态下可接收的MBS会话对应的下行HARQ进程外的每个下行HARQ进程，认为下一个接收到的传输块是第一次传输。
5.清空所有上行HARQ缓存。
6.停止正在进行的随机接入过程。
7.清空消息3的缓存。
需要说明的是，如果UE执行A-C中的多项，则交换执行顺序得到的实施例也是本公开保护的范围。执行步骤S201和步骤S202的实体可以是UE的RRC实体。
根据上述方法，能够支持RRC非激活态的用户设备接收多播业务，从而能够节省通信资源，提高通信效率。
MBS多播支持两种混合自动重传请求HARQ反馈模式，其中一种HARQ反馈模式是ACK-NACK反馈，即当UE正确接收到传输块时在物理上行控制信道PUCCH上传输HARQ-ACK信息且当UE未正确接收传输块时在PUCCH上传输HARQ-NACK信息；另一种HARQ反馈模式是仅NACK反馈(nack-only)，即仅当UE未正确接收传输块时在PUCCH上传输HARQ-NACK信息。基站通过RRC重配置消息为每个MBS会话或G-RNTI或G-CS-RNTI配置是否需要HARQ反馈，这可通过为每个 G-RNTI关联的字段harq-FeedbackEnablerMulticast配置。所述字段harq-FeedbackEnablerMulticast用于指示UE是否应该为MBS多播(或接收到由该G-RNTI加扰的传输块)提供HARQ反馈。进一步的，还可以为UE配置反馈模式为仅NACK反馈或ACK-NACK反馈，这通过harq-FeedbackOptionMulticast字段配置。harq-FeedbackOptionMulticast字段指示动态调度物理下行共享信道PDSCH或半静态调度SPS PDSCH MBS多播的反馈模式。
可以限定所述指示标识指示的MRB或MBS会话或TMGI或G-RNTI或G-CS-RNTI为未配置HARQ反馈的MRB或MBS会话或TMGI或G-RNTI或G-CS-RNTI，即未配置字段harq-FeedbackEnablerMulticast的MRB或MBS会话或TMGI或G-RNTI或G-CS-RNTI。
还可以限定如果所述指示标识指示在非激活态下接收的MRB或MBS会话或TMGI或G-RNTI或G-CS-RNTI为配置了HARQ反馈的MRB或MBS会话或TMGI或G-RNTI或G-CS-RNTI，当UE进入RRC非激活态后，不执行对应的MRB或MBS的HARQ反馈或指示为不需要HARQ反馈。
以下通过不同实施例具体描述携带所述指示标识的RRC消息和所述指示标识的指示方式。
实施例1
基站向UE发送RRC重配置消息RRCReconfiguration为处于RRC连接态的UE配置用于传输MBS会话的MRB，并在向UE发送的RRC释放消息RRCRelease中携带一个指示标识用于指示在UE进入RRC非激活态后收的MBS会话。
所述指示标识字段可以采用以下方式实现：
方式一：所述指示标识字段包含一个MRB标识列表(记为ptmReceptionInInactiveList字段)，如果一个MBS会话对应的MRB标识包含在所述指示标识中，表示UE在进入RRC非激活态后需要接收该MBS会话或所述MRB标识对应的MRB。
具体的，UE在接收到的RRC释放消息包含suspendConfig时，如果 RRC释放消息还包含所述指示标识，则执行以下操作中的至少一项：
A.执行MAC部分重置。
B.挂起(suspend)除SRB0和所述指示标识指示的多播MRB外的所有SRB和DRB和多播MRB。
C.向下层指示除所述指示标识指示的多播MRB外的所有DRB和多播MRB的PDCP挂起。
需要说明的是，如果UE执行A-C中的多项，则交换执行顺序得到的实施例也是本公开保护的范围。
如果RRC释放消息中不包含所述指示标识，则执行MAC重置和/或释放缺省的MAC小区组配置(存在缺省的MAC小区组配置时才执行此操作)。
换言之，当RRC释放消息包含所述指示标识时，不挂起所述指示标识指示的MRB(或挂起除SRB0和/或所述指示标识指示的MRB外的其他RB)，即指示标识字段指示不挂起(suspend)的MRB。
【方式一的变形】
所述指示标识包含一个MRB标识列表，如果一个MBS会话对应的MRB标识未包含在所述指示标识中，表示UE在进入RRC非激活态后需要接收该MBS会话或所述MRB标识对应的MRB。换言之，UE在接收到进入RRC非激活态的指示时，挂起所述指示标识包含的MRB或挂起除SRB0和/或所述指示标识字段未指示的MRB外的其他RB)，即指示标识指示要挂起的MRB。
方式二：所述指示标识包含一个TMGI列表，如果一个MBS会话对应的TMGI包含在所述指示标识中，表示UE在进入RRC非激活态后需要接收该MBS会话或该TMGI对应的MRB。
换言之，UE在接收到进入RRC非激活态的指示时，不挂起所述指示标识包含的TMGI对应的MRB(或挂起除SRB0和/或所述指示标识指示外的其他RB)，即指示标识指示不挂起的MRB对应的TMGI。
具体的，UE在接收到的RRC释放消息包含suspendConfig时，如果RRC释放消息还包含所述指示标识，则执行以下操作中的至少一项：
A.执行MAC部分重置。
B.挂起(suspend)除SRB0和所述指示标识指示的TMGI对应的多播MRB外的所有SRB和DRB和多播MRB。
C.向下层指示除所述指示标识指示的TMGI对应的多播MRB外的所有DRB和多播MRB的PDCP挂起。
需要说明的是，如果UE执行A-C中的多项，则交换执行顺序得到的实施例也是本公开保护的范围。
如果RRC释放消息中不包含所述指示标识，则执行MAC重置和/或释放缺省的MAC小区组配置(存在缺省的MAC小区组配置时才执行此操作)。
【方式二的变形】
所述指示标识包含一个TMGI列表，如果一个MBS会话对应的TMGI未包含在所述指示标识中，表示UE在进入RRC非激活态后需要接收该MBS会话或该TMGI对应的MRB。换言之，UE在接收到进入RRC非激活态的指示时，挂起所述指示标识包含的TMGI对应的MRB或挂起除SRB0和/或所述指示标识未指示的TMGI对应的MRB外的其他RB)，即指示标识指示要挂起的MRB对应的TMGI。
方式三：所述指示标识包含一个G-RNTI或G-CS-RNTI列表，如果一个MBS会话对应的G-RNTI或G-CS-RNTI包含在所述指示标识中，表示UE在进入RRC非激活态后需要接收该MBS会话或该G-RNTI或G-CS-RNTI对应的MRB。其中，G-CS-RNTI用于加扰一个或多个MBS多播服务的半静态调度SPS群组公共PDSCH和激活/去激活SPS群组公共PDSCH。
换言之，UE在接收到进入RRC非激活态的指示时，不挂起所述指示标识包含的G-RNTI或G-CS-RNTI对应的MRB(或挂起除SRB0和/或所述指示标识指示外的其他RB)，即指示标识指示不挂起的MRB对应的G-RNTI或G-CS-RNTI。
具体的，UE在接收到的RRC释放消息包含suspendConfig时，如果RRC释放消息还包含所述指示标识，则执行以下操作中的至少一项：
A.执行MAC部分重置。
B.挂起(suspend)除SRB0和所述指示标识指示的G-RNTI或G-CS-RNTI对应的多播MRB外的所有SRB和DRB和多播MRB。
C.向下层指示除所述指示标识指示的G-RNTI或G-CS-RNTI对应的多播MRB外的所有DRB和多播MRB的PDCP挂起。
需要说明的是，如果UE执行A-C中的多项，则交换执行顺序得到的实施例也是本公开保护的范围。
如果RRC释放消息中不包含所述指示标识，则执行MAC重置和/或释放缺省的MAC小区组配置(存在缺省的MAC小区组配置时才执行此操作)。
【方式三的变形】
所述指示标识包含一个G-RNTI或G-CS-RNTI列表，如果一个MBS会话对应的G-RNTI或G-CS-RNTI未包含在所述指示标识中，表示UE在进入RRC非激活态后需要接收该MBS会话或该G-RNTI或G-CS-RNTI对应的MRB。换言之，UE在接收到进入RRC非激活态的指示时，挂起所述指示标识包含的G-RNTI或G-CS-RNTI对应的MRB或挂起除SRB0和/或所述指示标识未指示的G-RNTI或G-CS-RNTI对应的MRB外的其他RB)，即指示标识指示要挂起的MRB对应的G-RNTI或G-CS-RNTI。
方式四：所述指示标识包含一个位图，位图中的每一位对应一个MRB(或者位图中的每一位对应一个未配置为需要HARQ反馈的MBS会话或MRB)。例如，按照MRB标识从小到大的顺序依次对应位图中的位。位图中对应位取值为1，表示UE在进入RRC非激活态后需要接收所述MRB标识对应的MBS会话或接收所述MRB标识对应的MRB。位图中对应位取值为0，表示UE在进入RRC非激活态后不接收所述MRB标识对应的MBS会话或不接收所述MRB标识对应的MRB。换言之，UE在接收到进入RRC非激活态的指示时，不挂起位图中对应位取值为1的MRB(或挂起除SRB0和/或位图中对应位取值为1的MRB外的其他RB)，即位图中对应位取值为1指示不挂起的MRB，取值为0指示挂起的MRB。
具体的，UE在接收到的RRC释放消息包含suspendConfig时，如果 RRC释放消息还包含所述位图，则执行以下操作中的至少一项：
A.执行MAC部分重置。
B.挂起(suspend)除SRB0和所述位图取值为1的位对应的多播MRB外的所有SRB和DRB和多播MRB。
C.向下层指示除所述位图取值为1的位对应的多播MRB外的所有DRB和多播MRB的PDCP挂起。
相比于方式一、方式二和方式三，位图方式能节省信令开销。
【方式四的变形】
所述指示标识包含一个位图，位图中的每一位对应一个MRB(或者位图中的每一位对应一个未配置为需要HARQ反馈的MBS会话或MRB)。例如，按照MRB标识从小到大的顺序依次对应位图中的位。位图中对应位取值为1，表示UE在进入RRC非激活态后不需要接收该MBS会话或所述MRB标识对应的MRB。换言之，UE在接收到进入RRC非激活态的指示时，挂起位图为1的位对应的MRB，即指示标识指示挂起的MRB。
方式五：所述指示标识用于指示UE在进入RRC非激活态后仍然接收未配置为需要HARQ反馈的MBS会话或MRB。换言之，当接收到的RRC消息中包含所述指示标识时，UE不挂起未配置为需要HARQ反馈的MBS会话对应的MRB或UE不挂起未配置为需要HARQ反馈的MRB。即当接收到的RRC消息中包含所述指示标识时，UE挂起配置了需要HARQ反馈的MBS会话对应的MRB或UE挂起配置了需要HARQ反馈的MRB。
具体的，在接收到的RRC释放消息包含suspendConfig时，如果所述RRC释放消息还包含用于指示UE在非激活态接收配置为不需要HARQ反馈的MRB或MBS会话的指示标识，则执行以下操作A-C中的至少一项：
A.执行MAC部分重置。
B.挂起(suspend)除SRB0和所述未配置为需要HARQ反馈的MBS多播对应的MRB外的所有SRB和DRB和多播MRB。
C.向下层指示除所述未配置为需要HARQ反馈的MBS多播对应的多 播MRB外的所有DRB和多播MRB的PDCP挂起。
如果RRC释放消息中不包含所述指示标识，则执行MAC重置和/或释放缺省的MAC小区组配置(存在缺省的MAC小区组配置时才执行此操作)。
实施例2
基站采用RRC重配置消息为处于RRC连接态的UE配置用于传输MBS会话的MRB，并在对应的MRB的配置字段中包含一个指示标识，用来指示当UE进入RRC非激活态后是否接收该MRB。
UE在接收到的RRC释放消息包含suspendConfig时，如果至少一个MRB被配置了所述指示标识，则执行以下操作中的至少一项：
A.执行MAC部分重置。
B.挂起(suspend)除SRB0和配置了所述指示标识的多播MRB外的所有SRB和DRB和多播MRB。
C.向下层指示除配置了所述指示标识的多播MRB外的所有DRB和多播MRB的PDCP挂起。
需要说明的是，如果UE执行A-C中的多项，则交换执行顺序得到的实施例也是本公开保护的范围。
如果所有MRB都未被配置所述指示标识，则执行MAC重置和/或释放缺省的MAC小区组配置(存在缺省的MAC小区组配置时才执行此操作)。
【实施例2的变形】
基站通过RRC重配置消息包含一个指示标识，用于指示UE在RRC非激活态接收的MBS会话或MRB对应的G-RNTI或G-CS-RNTI或TMGI。相应地，实施例2中所述的在RRC非激活态接收的MRB就是该指示标识指示的MBS会话或MRB对应的G-RNTI或G-CS-RNTI或TMGI对应的MRB。
实施例3
基站采用RRCRelease消息为UE配置并指示为处于RRC连接态的UE传输MBS会话的MRB。
处于RRC非激活态的UE因要接收MBS多播(例如接收到寻呼消息，其中包含UE已经加入的一个或多个MBS会话对应的TMGI)向基站发送用于请求恢复一个挂起的RRC连接或用于执行基于RAN的通知区域(RNA)更新的RRC恢复请求消息RRCResumeRequest，所述消息中包含一个原因字段ResumeCause，其取值为UE想要接收的一个或多个MBS会话的TMGI或者用于指示UE要接收MBS会话而触发发送恢复RRC连接请求对应的值。
UE接收来自基站的包含suspendConfig字段的RRC释放消息，所述消息中包含指示UE在非激活态接收的MBS会话的MRB的配置信息。UE根据所述配置信息配置对应的MRB并接收对应的MBS会话。
对于同时配置了PTM和PTP传输的MRB，可以规定当UE处于RRC非激活态时，挂起PTP传输，即UE仅从PTM接收MBS会话。
图3是表示基于本发明的实施例的用户设备UE30的框图。如图3所示，UE30包括处理器301和存储器302。处理器301例如可以包括微处理器、微控制器、嵌入式处理器等。存储器302例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统等。存储器302上存储有程序指令。该指令在由处理器301运行时，可以执行本发明详细描述的用户设备中的上述方法。
另外，运行在根据本发明的设备上的计算机可执行指令或者程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统” 可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适当地组合不同实施例所发明的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种由用户设备UE执行的方法，包括：
    从基站接收无线资源控制RRC消息；以及
    在接收到的所述RRC消息中包含用于指示UE进入RRC非激活态后接收的多播广播业务MBS会话的指示标识的情况下，UE执行与接收所述指示标识指示的MBS会话相关的操作。
  2. 根据权利要求1所述的方法，其中，
    从基站接收RRC释放消息，在该RRC释放消息中包含所述指示标识。
  3. 根据权利要求2所述的方法，其中，
    所述指示标识包含MRB标识列表，
    UE执行以下操作中的至少一项：
    执行媒体接入控制MAC部分重置；
    挂起除信令无线承载SRB0和所述指示标识指示的多播MRB外的所有SRB、数据无线承载DRB和多播MRB；
    向下层指示除所述指示标识指示的多播MRB外的所有DRB和多播MRB的分组数据汇聚协议PDCP挂起。
  4. 根据权利要求2所述的方法，其中，
    所述指示标识包含临时移动组标识TMGI列表，
    UE执行以下操作中的至少一项：
    执行MAC部分重置；
    挂起除SRB0和所述指示标识指示的TMGI对应的多播MRB外的所有SRB、DRB和多播MRB；
    向下层指示除所述指示标识指示的TMGI对应的多播MRB外的所有DRB和多播MRB的PDCP挂起。
  5. 根据权利要求2所述的方法，其中，
    所述指示标识包含群组无线网络临时标识G-RNTI或群组配置调度无线网络临时标识G-CS-RNTI列表，
    UE执行以下操作中的至少一项：
    执行MAC部分重置；
    挂起除SRB0和所述指示标识指示的G-RNTI或G-CS-RNTI对应的多播MRB外的所有SRB、DRB和多播MRB；
    向下层指示除所述指示标识指示的G-RNTI或G-CS-RNTI对应的多播MRB外的所有DRB和多播MRB的PDCP挂起。
  6. 根据权利要求2所述的方法，其中，
    所述指示标识包含位图，
    UE执行以下操作中的至少一项：
    执行MAC部分重置；
    挂起除SRB0和所述位图取值为1的位对应的多播MRB外的所有SRB、DRB和多播MRB；
    向下层指示除所述位图取值为1的位对应的多播MRB外的所有DRB和多播MRB的PDCP挂起。
  7. 根据权利要求2所述的方法，其中，
    所述指示标识用于指示UE进入RRC非激活态后接收未配置为需要HARQ反馈的MBS会话或MRB，
    UE执行以下操作中的至少一项：
    执行MAC部分重置；
    挂起除SRB0和所述未配置为需要HARQ反馈的MBS多播对应的MRB外的所有SRB、DRB和多播MRB；
    向下层指示除所述未配置为需要HARQ反馈的MBS多播对应的多播MRB外的所有DRB和多播MRB的PDCP挂起。
  8. 根据权利要求1所述的方法，其中，
    从基站接收RRC重配置消息，该RRC重配置消息在对应的MRB的配置字段中包含所述指示标识，用于指示UE进入RRC非激活态后是否接收该MRB，
    在至少一个MRB被配置了所述指示标识的情况下，UE执行以下操作中的至少一项：
    执行MAC部分重置；
    挂起除SRB0和配置了所述指示标识的多播MRB外的所有SRB、DRB和多播MRB；
    向下层指示除配置了所述指示标识的多播MRB外的所有DRB和多播MRB的PDCP挂起。
  9. 根据权利要求1所述的方法，其中，
    从基站接收RRC释放消息，
    在所述RRC释放消息中包含指示UE在非激活态接收的MBS会话的MRB的配置信息，
    UE根据所述配置信息配置对应的MRB并接收对应的MBS会话。
  10. 一种用户设备，包括：
    处理器；以及
    存储器，存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求1至9中任一项所述的方法。
PCT/CN2023/111227 2022-08-08 2023-08-04 由用户设备执行的方法以及用户设备 WO2024032500A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210946585.0 2022-08-08
CN202210946585.0A CN117580195A (zh) 2022-08-08 2022-08-08 由用户设备执行的方法以及用户设备

Publications (1)

Publication Number Publication Date
WO2024032500A1 true WO2024032500A1 (zh) 2024-02-15

Family

ID=89850751

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/111227 WO2024032500A1 (zh) 2022-08-08 2023-08-04 由用户设备执行的方法以及用户设备

Country Status (2)

Country Link
CN (1) CN117580195A (zh)
WO (1) WO2024032500A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111771422A (zh) * 2018-02-26 2020-10-13 诺基亚技术有限公司 用于无线网络的多播业务区域管理和移动性
CN114513756A (zh) * 2020-10-23 2022-05-17 大唐移动通信设备有限公司 一种多播广播业务数据接收、指示方法、终端及网络设备
CN115443667A (zh) * 2021-04-01 2022-12-06 北京小米移动软件有限公司 广播多播业务传输方法、装置及存储介质
CN116347362A (zh) * 2023-03-28 2023-06-27 上海数字电视国家工程研究中心有限公司 一种mbs业务的激活方法及收发装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111771422A (zh) * 2018-02-26 2020-10-13 诺基亚技术有限公司 用于无线网络的多播业务区域管理和移动性
CN114513756A (zh) * 2020-10-23 2022-05-17 大唐移动通信设备有限公司 一种多播广播业务数据接收、指示方法、终端及网络设备
CN115443667A (zh) * 2021-04-01 2022-12-06 北京小米移动软件有限公司 广播多播业务传输方法、装置及存储介质
CN116347362A (zh) * 2023-03-28 2023-06-27 上海数字电视国家工程研究中心有限公司 一种mbs业务的激活方法及收发装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
VIVO: "Overview of NR MBS", 3GPP DRAFT; R2-2007033, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20200818 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911881 *

Also Published As

Publication number Publication date
CN117580195A (zh) 2024-02-20

Similar Documents

Publication Publication Date Title
US12010592B2 (en) Sidelink communications method and apparatus
AU2016234933B2 (en) Method for coordinating discontinuous reception, DRX
WO2024032500A1 (zh) 由用户设备执行的方法以及用户设备
WO2021027685A1 (zh) Pdcp实体发送端/接收端的执行方法、pdcp实体及通信设备
US20230247687A1 (en) Terminal apparatus, base station apparatus, and method
US20230309185A1 (en) Terminal apparatus, base station apparatus, and method
WO2021221009A1 (ja) 端末装置、方法、および、集積回路
WO2024032544A1 (zh) 由用户设备执行的处理寻呼消息的方法及用户设备
TW201921977A (zh) 服務資料單元處理方法、丟棄方法、相應的使用者設備和電腦可讀媒體
WO2024120476A1 (zh) 由用户设备执行的方法以及用户设备
WO2023001240A1 (zh) 由用户设备ue执行的方法及用户设备
JP7481588B2 (ja) 通信方法、ユーザ装置、移動通信システム、チップセット、及びプログラム
WO2023036173A1 (zh) 状态报告发送方法、无线承载重传执行方法及用户设备
WO2024120475A1 (zh) 恢复rrc连接的方法以及用户设备
WO2022255288A1 (ja) 端末装置、基地局装置、および方法
WO2023276947A1 (ja) 端末装置、基地局装置、および方法
WO2022255293A1 (ja) 端末装置、基地局装置、および方法
WO2022255305A1 (ja) 端末装置、基地局装置、および方法
WO2022255279A1 (ja) 端末装置、基地局装置、および方法
WO2022255303A1 (ja) 端末装置、基地局装置、および方法
WO2023036287A1 (zh) 用户设备执行的方法、基站的传输方法及用户设备
JP7469571B2 (ja) 通信方法、ユーザ装置、ネットワークノード、チップセット、及びプログラム
JP7494064B2 (ja) 端末装置、基地局装置、方法、および、集積回路
WO2021221010A1 (ja) 端末装置、方法、および、集積回路
WO2022138567A1 (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: 23851721

Country of ref document: EP

Kind code of ref document: A1