Method for sending multicast session in RRC (Radio Resource Control) inactive state in NR (Noise Ratio) cell

By configuring multicast SIB, MCCH and CFR in the NR cell and transmitting multicast session data using dynamic or semi-static scheduling methods, the problem of UE receiving multicast sessions in RRC is solved, reducing power consumption and improving Receive ability.

CN118945906APending Publication Date: 2024-11-12CHENGDU TD TECH LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310531508.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-11
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In the NR cell, the UE causes high power consumption when receiving multicast sessions in the RRC connected state, and when the number of UEs is large, the cell cannot support all UEs in the RRC connected state to receive multicast sessions. The prior art is difficult to realize that the UE is in the RRC inactive state. Receive multicast sessions.

Method used

在NR小区中,gNB配置多播SIB、MCCH和CFR,根据多播会话的调度方式分配资源,并通过专用信令发送多播会话的配置信息给RRC非激活态UE,采用动态或半静态调度方式传输多播会话数据,UE根据配置信息接收多播会话。

Benefits of technology

It realizes that the UE receives multicast sessions in the RRC inactive state, reduces power consumption and improves the cell's support for multicast session reception.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945906A_ABST
    Figure CN118945906A_ABST
Patent Text Reader

Abstract

The invention provides a method for sending a multicast session in an RRC inactive state in an NR cell, and the method comprises the steps: enabling a gNB to configure a DRX mode according to whether the multicast session supports the retransmission to the multicast session in a PTM mode or not under dynamic scheduling; under semi-static scheduling, the gNB configures the number of HARQ processes and a DRX mode according to whether the multicast session supports retransmission to the multicast session in a PTM mode; the gNB sends the configuration information of the multicast session through the special signaling and the multicast MCCH, schedules the multicast session according to the configuration information of the multicast session, and sends the data of the multicast session; and the UE in the RRC inactive state receives the configuration information of the multicast session, and receives the multicast session according to the configuration information of the multicast session.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method for sending a multicast session in an RRC inactive state in an NR cell. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) release 17 provides the NR MBS feature, which supports sending multicast sessions and broadcast sessions in New Radio Access (NR) cells.

[0003] When sending a multicast session, the user equipment (UE) receiving the multicast session is required to be in the radio resource control (RRC) connected state, and the base station (gNB) sends a multicast session through the point to multipoint (PTM) mode and / or the point to point (PTP) mode. When a large number of UEs receive multicast sessions in a cell, the cell may not be able to support all these UEs in the RRC connected state to receive the multicast session. At the same time, when the UE only receives the multicast session, allowing the UE to receive the multicast session in the RRC connected state will cause higher power consumption.

[0004] Therefore, how to enable the UE to receive the multicast session in the RRC inactive state is an urgent problem to be solved. Summary of the invention

[0005] An embodiment of the present application provides a method for sending a multicast session in an RRC inactive state in an NR cell, which is used to solve the problem of how to enable a UE to receive a multicast session in an RRC inactive state.

[0006] In a first aspect, an embodiment of the present application provides a method for sending a multicast session in an RRC inactive state in an NR cell, including:

[0007] The gNB configures a multicast SIB, a multicast MCCH and a multicast CFR for the NR cell, wherein the multicast SIB carries the configuration information of the multicast MCCH, the multicast MCCH is used to transmit the configuration information of the multicast session in the RRC inactive state, and the multicast CFR is used to transmit the multicast session in the RRC inactive state;

[0008] The gNB determines, for a multicast session in an RRC inactive state, a scheduling mode of the multicast session, where the scheduling mode of the multicast session is dynamic scheduling or semi-static scheduling;

[0009] The gNB allocates resources to the multicast session according to the scheduling mode of the multicast session, and determines configuration information of the multicast session;

[0010] The gNB sends the configuration information of the multicast session to the RRC inactive UE receiving the multicast session through dedicated signaling and the multicast MCCH;

[0011] The gNB schedules the multicast session and sends data of the multicast session;

[0012] The RRC inactive UE receives configuration information of the multicast session, and receives data of the multicast session according to the configuration information of the multicast session.

[0013] In a specific implementation, when the scheduling mode of the multicast session is dynamic scheduling, the gNB allocates resources to the multicast session according to the scheduling mode of the multicast session, including:

[0014] When the gNB transmits the multicast session only to the RRC inactive UE, the gNB allocates a G-RNTI and a DRX mode to the multicast session, and the DRX mode allocated to the multicast session does not support retransmission of the multicast session;

[0015] When the gNB transmits the multicast session to all or part of the RRC connected UEs and RRC inactive UEs through the same PTM resources on the multicast CFR, the gNB allocates a G-RNTI and a DRX mode to the multicast session, where the G-RNTI is used to identify the multicast session on the air interface, and the DRX mode is used to transmit the multicast session through the same PTM resources on the multicast CFR; when the gNB does not retransmit the TB of the multicast session in PTM mode, the DRX mode configured by the gNB for the multicast session does not support retransmission of the multicast session; when the gNB retransmits the TB of the multicast session in PTM mode, the DRX mode configured by the gNB for the multicast session supports retransmission of the multicast session;

[0016] When the gNB transmits the multicast session to the RRC connected UE and the RRC inactive UE through different PTM resources, the gNB allocates a G-RNTI to the multicast session for identifying the multicast session on the air interface, the gNB transmits the multicast session to the RRC inactive UE through the PTM resources on the multicast CFR, the gNB configures a DRX mode for the multicast session, the DRX mode is used to send the multicast session to the RRC inactive UE on the multicast CFR, and the DRX mode does not support retransmission of the multicast session.

[0017] In a specific implementation manner, the configuration information of the multicast session includes: G-RNTI, DRX mode configuration information.

[0018] In a specific implementation, when the scheduling mode of the multicast session is semi-static scheduling, the gNB allocates resources to the multicast session according to the scheduling mode of the multicast session, including:

[0019] When the gNB transmits the multicast session only to the RRC inactive UE, the gNB allocates a G-CS-RNTI and a DRX mode to the multicast session, allocates at least one SPS resource to the multicast session, the multicast session uses only one HARQ process, and the DRX mode of the multicast session does not support retransmission;

[0020] When the gNB transmits the multicast session to all or part of the RRC connected UEs and RRC inactive UEs through the same semi-static PTM resources on the multicast CFR, the gNB allocates a G-CS-RNTI and a DRX mode to the multicast session, and allocates at least one SPS resource to the multicast session, the G-CS-RNTI is used to identify the multicast session on the air interface, and the DRX mode is used to transmit the multicast session through the same semi-static PTM resources on the multicast CFR; when the gNB does not retransmit the TB of the multicast session in PTM mode, the multicast session uses only one HARQ process, and the DRX mode of the multicast session does not support retransmission; when the gNB retransmits the TB of the multicast session in PTM mode, multiple HARQ processes are allocated to the multicast session, and the DRX mode of the multicast session supports retransmission;

[0021] When the gNB transmits the multicast session to the RRC connected UE and the RRC inactive UE through different semi-static PTM resources, the gNB transmits the multicast session to the RRC inactive UE through the semi-static PTM resources on the multicast CFR, the gNB allocates a G-CS-RNTI to the multicast session for identifying the multicast session on the air interface, allocates a DRX mode to the multicast session for transmitting the multicast session on the multicast CFR, allocates at least one SPS resource to the multicast session, the SPS resource is used to transmit the multicast session on the multicast CFR, the multicast session uses only one HARQ process on the multicast CFR, and the DRX mode of the multicast session does not support retransmission.

[0022] In a specific embodiment, the method further comprises:

[0023] The gNB configures activated semi-static PTM resources for the multicast session on the multicast CFR: the gNB selects an SPS resource from the SPS resources allocated to the multicast session and determines the frequency domain resources, time domain resources, VRB to PRB mapping method and coding modulation method used when transmitting the multicast session through the selected SPS resource, and generates activated semi-static PTM resources.

[0024] In a specific implementation, when the gNB adopts a semi-static scheduling method to transmit the multicast session, the configuration information of the multicast session includes: G-CS-RNTI, DRX mode configuration information, and configuration information of multiple SPS resources; or includes: G-CS-RNTI, DRX mode configuration information, configuration information of multiple SPS resources, and configuration information of activated semi-static PTM resources.

[0025] In a specific implementation, when the DRX mode does not support retransmission of the multicast session, the parameters in the configuration information of the DRX mode include: a first timer drx-onDurationTimerPTM, a time slot offset drx-SlotOffsetPTM, a second timer drx-InactivityTimerPTM, and a DRX cycle and start subframe offset drx-LongCycleStartOffsetPTM.

[0026] In a specific implementation, when the DRX mode supports retransmission of the multicast session, the parameters in the configuration information of the DRX mode include: a first timer drx-onDurationTimerPTM, a time slot offset drx-SlotOffsetPTM, a second timer drx-InactivityTimerPTM, a DRX cycle and a start subframe offset drx-LongCycleStartOffsetPTM, a third timer drx-RetransmissionTimerDL-PTM, and a fourth timer drx-HARQ-RTT-TimerDL-PTM.

[0027] In a specific implementation manner, the gNB sends the configuration information of the multicast session to an RRC inactive UE receiving the multicast session through dedicated signaling and the multicast MCCH, including:

[0028] Before the UE joins the multicast session and enters the RRC inactive state, the gNB sends configuration information of the multicast session to the UE through dedicated signaling;

[0029] The gNB sends the multicast SIB and the multicast MCCH in the NR cell, the multicast SIB carries the configuration information of the multicast MCCH, and the multicast MCCH carries the configuration information of the multicast session.

[0030] In a specific implementation, when the scheduling mode of the multicast session is dynamic scheduling, the gNB schedules the multicast session and sends data of the multicast session, including:

[0031] Whenever the gNB schedules the multicast session, the gNB sends the PDCCH and PDSCH of the multicast session, the CRC of the PDCCH is scrambled with the G-RNTI, the DCI format on the PDCCH is the scheduling information of the PDSCH of the multicast session, the PDSCH of the multicast session uses the G-RNTI during bit scrambling, and the PDSCH of the multicast session carries the TB of the multicast session;

[0032] When the multicast session sent on the multicast CFR does not support retransmission, the fields in the DCI format on the PDCCH of the multicast session include: frequency domain resource allocation, time domain resource allocation, VRB to PRB mapping, modulation and coding method, and redundancy version.

[0033] In a specific implementation, when the scheduling mode of the multicast session is dynamic scheduling, the gNB schedules the multicast session and sends data of the multicast session, including:

[0034] Whenever the gNB schedules the multicast session, the gNB sends the PDCCH and PDSCH of the multicast session, the CRC of the PDCCH is scrambled with the G-RNTI, the DCI format on the PDCCH is the scheduling information of the PDSCH of the multicast session, the PDSCH of the multicast session uses the G-RNTI during bit scrambling, and the PDSCH of the multicast session carries the TB of the multicast session;

[0035] When the multicast session sent on the multicast CFR supports retransmission, the fields in the DCI format on the PDCCH of the multicast session include: frequency domain resource allocation, time domain resource allocation, VRB to PRB mapping, modulation and coding method, redundancy version, HARQ process number, downlink allocation subscript, PUCCH resource indication, and PDSCH to HARQ feedback timing indication.

[0036] In a specific implementation, the gNB scheduling the multicast session includes:

[0037] The gNB schedules the multicast session supporting retransmission or not supporting retransmission using DCI format 4-1;

[0038] If the multicast session supports retransmission, the gNB sets each field in DCI format 4-1 except the reserved bit field according to the scheduling information carried on the PDCCH of the multicast session;

[0039] If the multicast session does not support retransmission, the gNB sets the frequency domain resource allocation, time domain resource allocation, VRB to PRB mapping, modulation and coding method, and redundancy version in DCI format 4-1 according to the scheduling information carried on the PDCCH of the multicast session.

[0040] In a specific implementation, when the scheduling mode of the multicast session is semi-persistent scheduling, the gNB schedules the multicast session and sends data of the multicast session, including:

[0041] The gNB allocates a semi-static PTM resource to the multicast session, and sends configuration information of the semi-static PTM resource allocated to the multicast session to an RRC inactive UE receiving the multicast session through mode 1;

[0042] The gNB sends a PDSCH through a semi-static PTM resource allocated to the multicast session, the PDSCH uses a G-CS-RNTI during bit scrambling, and the PDSCH carries a TB of the multicast session;

[0043] Among them, method 1: the gNB activates the semi-static PTM resources of the multicast session through the PDCCH encrypted with G-CS-RNTI by CRC, and the DCI format on the PDCCH is DCI format 4-1.

[0044] In a specific implementation, when the scheduling mode of the multicast session is semi-persistent scheduling, the gNB schedules the multicast session and sends data of the multicast session, including:

[0045] The gNB allocates a semi-static PTM resource to the multicast session, and sends configuration information of the semi-static PTM resource allocated to the multicast session to an RRC inactive UE receiving the multicast session through mode 2;

[0046] The gNB sends a PDSCH through a semi-static PTM resource allocated to the multicast session, the PDSCH uses a G-CS-RNTI during bit scrambling, and the PDSCH carries a TB of the multicast session;

[0047] Among them, method 2: the gNB sends the configuration information of the multicast session through the multicast MCCH, and the configuration information of the multicast session provides the semi-static PTM resource configuration information of the multicast session; when the gNB sends the configuration information of the multicast session on the multicast MCCH for the first time or whenever the configuration information of the multicast session is updated, the gNB sends a multicast MCCH change notification;

[0048] The multicast MCCH change notification is sent through 2 bits in the DCI format on the PDCCH that schedules the multicast MCCH: when the configuration information of a multicast session is sent for the first time on the multicast MCCH, the first bit is set to 1, otherwise the first bit is set to 0; when the configuration information of an existing multicast session on the multicast MCCH is updated, the second bit is set to 1, otherwise the second bit is set to 0.

[0049] In a specific implementation manner, the RRC inactive UE receives the configuration information of the multicast session, and receives the data of the multicast session according to the configuration information of the multicast session, including:

[0050] When the multicast session adopts dynamic scheduling, the RRC inactive UE obtains the configuration information of the multicast session through dedicated signaling and the multicast MCCH;

[0051] When the multicast session adopts semi-persistent scheduling, the RRC inactive UE obtains the configuration information of the multicast session through dedicated signaling, the PDCCH scrambled by the CRC using the G-CS-RNTI, and the multicast MCCH;

[0052] When the multicast session does not support retransmission, the RRC inactive UE receives data of the multicast session according to configuration information of the DRX mode in the configuration information of the multicast session;

[0053] The RRC inactive UE receives data of the multicast session according to the configuration information of the DRX mode in the configuration information of the multicast session, including:

[0054] When the gNB configures DRX mode for a multicast session, the activation time includes the time when the following two timers run:

[0055] The first timer drx-onDurationTimerPTM;

[0056] The second timer drx-InactivityTimerPTM;

[0057] The RRC inactive UE performs the following processing:

[0058] If the preset formula "[(SFN×10)+subframe number]modulo(drx-LongCycle-PTM)=drx-StartOffset-PTM" holds, starting from the subframe that satisfies the preset formula, the RRC inactive UE starts the first timer drx-onDurationTimerPTM after drx-SlotOffsetPTM time slots, where modulo represents a modulo operation, SFN represents a radio frame number, subframe number represents a subframe number, drx-LongCycle-PTM represents a DRX cycle, drx-StartOffset-PTM represents a starting subframe offset, and drx-SlotOffsetPTM represents a time slot offset;

[0059] During the activation time, the RRC inactive UE monitors the PDCCH scrambled by G-RNTI / G-CS-RNTI for CRC; if the PDCCH indicates a downlink transmission, the RRC inactive UE starts or restarts the second timer drx-InactivityTimerPTM within the first symbol after the PDCCH reception ends.

[0060] In a specific implementation manner, the RRC inactive UE receives the configuration information of the multicast session, and receives the data of the multicast session according to the configuration information of the multicast session, including:

[0061] When the multicast session adopts dynamic scheduling, the RRC inactive UE obtains the configuration information of the multicast session through dedicated signaling and the multicast MCCH;

[0062] When the multicast session adopts semi-persistent scheduling, the RRC inactive UE obtains the configuration information of the multicast session through dedicated signaling, the PDCCH scrambled by the CRC using the G-CS-RNTI, and the multicast MCCH;

[0063] When the multicast session supports retransmission, the RRC inactive UE receives data of the multicast session according to configuration information of the DRX mode in the configuration information of the multicast session;

[0064] The RRC inactive UE receives data of the multicast session according to the configuration information of the DRX mode in the configuration information of the multicast session, including:

[0065] When the gNB configures DRX mode for a multicast session, the activation time includes the time when the following three timers run:

[0066] The first timer drx-onDurationTimerPTM;

[0067] The second timer drx-InactivityTimerPTM;

[0068] The third timer drx-RetransmissionTimerDL-PTM;

[0069] The RRC inactive UE performs the following processing: when a MAC PDU is received on the configured semi-static resource, if HARQ feedback is triggered, the RRC inactive UE does not need to provide HARQ feedback, the RRC inactive UE determines the position for sending downlink HARQ feedback, and starts the fourth timer drx-HARQ-RTT-TimerDL-PTM of the corresponding HARQ process within the first symbol after the end of sending the downlink HARQ feedback;

[0070] The RRC inactive UE stops the third timer drx-RetransmissionTimerDL-PTM of the corresponding HARQ process;

[0071] When a fourth timer drx-HARQ-RTT-TimerDL-PTM times out, if data of the corresponding HARQ process is not successfully decoded, the RRC inactive UE starts the third timer drx-RetransmissionTimerDL-PTM of the corresponding HARQ process within the first symbol after the fourth timer drx-HARQ-RTT-TimerDL-PTM times out;

[0072] When the RRC inactive UE receives a DRX Command MAC CE in a DCI format scrambled by CRC using G-RNTI, the RRC inactive UE stops a first timer drx-onDurationTimerPTM and a second timer drx-InactivityTimerPTM;

[0073] When the preset formula "[(SFN×10)+subframe number]modulo(drx-LongCycle-PTM)=drx-StartOffset-PTM" holds, starting from the subframe that satisfies the preset formula, the RRC inactive UE starts the first timer drx-onDurationTimerPTM after drx-SlotOffsetPTM time slots, where modulo represents a modulo operation, SFN represents a radio frame number, subframe number represents a subframe number, drx-LongCycle-PTM represents a DRX cycle, drx-StartOffset-PTM represents a start subframe offset, and drx-SlotOffsetPTM represents a time slot offset;

[0074] During the activation time, the RRC inactive UE monitors the PDCCH scrambled by the CRC using the G-RNTI / G-CS-RNTI;

[0075] If the received PDCCH indicates a downlink transmission, if the HARQ feedback is triggered, the RRC inactive UE does not need to provide HARQ feedback, the RRC inactive UE determines the position for sending the downlink HARQ feedback, starts the fourth timer drx-HARQ-RTT-TimerDL-PTM of the corresponding HARQ process within the first symbol after the end of the transmission carrying the downlink HARQ feedback, and stops the third timer drx-RetransmissionTimerDL-PTM of the corresponding HARQ process;

[0076] If the PDCCH indicates a new downlink transmission, the RRC inactive UE starts or restarts the second timer drx-InactivityTimerPTM in the first symbol after the PDCCH reception ends.

[0077] In the method for sending a multicast session in an RRC inactive state in an NR cell provided in an embodiment of the present application, under dynamic scheduling, the gNB configures the DRX mode according to whether the multicast session supports retransmission to the multicast session in PTM mode; under semi-static scheduling, the gNB configures the number of HARQ processes and the DRX mode according to whether the multicast session supports retransmission to the multicast session in PTM mode; the gNB sends the configuration information of the multicast session through dedicated signaling and multicast MCCH, and schedules the multicast session and sends the data of the multicast session according to the configuration information of the multicast session; the RRC inactive UE receives the configuration information of the multicast session, and receives the multicast session according to the configuration information of the multicast session. Therefore, the method for sending a multicast session in an RRC inactive state in an NR cell provided in an embodiment of the present application realizes the function of the UE receiving the multicast session in the RRC inactive state. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following is a brief introduction to the drawings required for use in the embodiments or the description of the prior art. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0079] Figure 1 A flowchart of a method for sending a multicast session in an RRC inactive state in an NR cell provided in the present application. DETAILED DESCRIPTION

[0080] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments made by ordinary technicians in this field under the enlightenment of the embodiments belong to the scope of protection of the present application.

[0081] The terms "first", "second", "third", "fourth", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0082] The 3rd Generation Partnership Project (3GPP) version 17 provides the New Radio Access (NR) Multicast / Broadcast Service (MBS) feature. The NR MBS feature supports sending multicast sessions and broadcast sessions in the NR cell. When sending a multicast session, the user equipment (UE) receiving the multicast session is required to be in the Radio Resource Control (RRC) connected state, and the base station (gNB) sends a multicast session through a point-to-multipoint (PTM) mode and / or a point-to-point (PTP) mode.

[0083] When a large number of UEs in a cell receive multicast sessions, the NR cell may not be able to support all of these UEs in the RRC connected state to receive multicast sessions. At the same time, when the UE only receives multicast sessions, allowing the UE to receive multicast sessions in the RRC connected state will cause higher power consumption. Therefore, the NR MBS enhancement project was established in 3GPP Release 18. The goal of this project is to allow UEs to receive multicast sessions in the RRC inactive state.

[0084] When a multicast session allows UEs to receive in RRC inactive state, the following issues need to be addressed when sending the multicast session to RRC inactive UEs:

[0085] (1) How to configure the discontinuous reception (DRX) mode for the multicast session.

[0086] (2) How to send the configuration information of the multicast session to the UE.

[0087] (3) How to schedule multicast sessions.

[0088] (4) How does the UE receive a multicast session according to the DRX mode of the multicast session?

[0089] In view of the problems existing in the prior art, the inventors found in the process of studying the sending method of multicast session in RRC inactive state in NR cell that under dynamic scheduling, the DRX mode can be configured according to whether the multicast session supports retransmission to the multicast session in PTM mode; under semi-static scheduling, the number of hybrid automatic repeat request (HARQ) processes and the DRX mode can be configured according to whether the multicast session supports retransmission to the multicast session in PTM mode. The gNB sends the configuration information of the multicast session through dedicated signaling and multicast MBS control channel (MBS Control Channel, MCCH), and schedules the multicast session and sends the data of the multicast session according to the configuration information of the multicast session. The UE receives the configuration information of the multicast session, and receives the data of the multicast session according to the configuration information of the multicast session. Based on the above inventive concept, the sending method of multicast session in RRC inactive state in NR cell in this application is designed.

[0090] Below, the method for sending a multicast session in an RRC inactive state in the NR cell in the present application is described in detail through a specific embodiment.

[0091] Figure 1 A flow chart of a method for sending a multicast session in an RRC inactive state in an NR cell provided in this application is as follows: Figure 1 As shown, the method for sending a multicast session in an RRC inactive state in an NR cell in the present application specifically includes the following steps:

[0092] S101: The gNB configures a multicast SIB, a multicast MCCH and a multicast CFR for the NR cell.

[0093] In this step, when the gNB supports multicast sessions in RRC inactive state in an NR cell, the gNB configures a multicast system information block (SIB), a multicast MCCH and a multicast common frequency resource (CFR) for the NR cell. The multicast SIB carries the configuration information of the multicast MCCH. The multicast MCCH is used to transmit the configuration information of each multicast session in RRC inactive state. The multicast CFR is used to transmit the multicast session in RRC inactive state.

[0094] It should be noted that the multicast CFR is the control resource set (CORESET) 0, or the initial downlink (DL) bandwidth part (Bandwidth Part, BWP), or includes the initial DL BWP. When the multicast CFR includes the initial DL BWP, the subcarrier spacing (SCS) and cyclic prefix (CP) type used by the multicast CFR are the same as the initial DL BWP.

[0095] It should be noted that the multicast session in the RRC inactive state refers to a multicast session that allows all UEs or some UEs receiving the multicast session to receive the multicast session in the RRC inactive state.

[0096] S102: The gNB determines a scheduling method for the multicast session.

[0097] In this step, for a multicast session in an RRC inactive state, when the multicast session has the characteristic of periodically generating the same amount of data, the gNB adopts a semi-static scheduling method for the multicast session; otherwise, a dynamic scheduling method is adopted for the multicast session.

[0098] S103: The gNB allocates resources to the multicast session according to the scheduling method of the multicast session, and determines the configuration information of the multicast session.

[0099] In this step, the scheduling mode of the multicast session is divided into a dynamic scheduling mode and a semi-static scheduling mode, so for the two scheduling modes, resources are allocated to the multicast session respectively, and the configuration information of the multicast session is determined.

[0100] When the gNB uses dynamic scheduling to transmit a multicast session, that is, when the scheduling mode of the multicast session is dynamic scheduling, the gNB allocates resources to the multicast session according to the scheduling mode of the multicast session and determines the configuration information of the multicast session as follows:

[0101] (1) When the gNB transmits a multicast session only to RRC-inactive UEs, the gNB transmits the multicast session using PTM resources on the multicast CFR, and allocates a Group-Radio Network Temporary Identifier (G-RNTI) and a DRX mode to the multicast session. The multicast session does not support retransmission, and the DRX mode allocated to the multicast session does not support retransmission of the multicast session.

[0102] Specifically, when a multicast session is only transmitted to RRC-inactive UEs, since the RRC-inactive UEs cannot feedback the confirmation (Acknowledgement, ACK) / non-confirmation (Negative-Acknowledgment, NACK) information of the HARQ process, the gNB cannot retransmit the multicast session in PTM / PTP mode, and accordingly, the DRX mode configured for the multicast session does not support retransmission.

[0103] (2) When the gNB transmits a multicast session to all or part of the RRC connected UEs and RRC inactive UEs through the same PTM resources on the multicast CFR, the gNB allocates a G-RNTI and a DRX mode to the multicast session, where the G-RNTI is used to identify the multicast session on the air interface, and the DRX mode is used to transmit the multicast session through the same PTM resources on the multicast CFR. When the gNB does not retransmit the transport block (TB) of the multicast session in PTM mode, the DRX mode configured by the gNB for the multicast session does not support retransmission of the multicast session. When the gNB retransmits the TB of the multicast session in PTM mode, the DRX mode configured by the gNB for the multicast session supports retransmission of the multicast session.

[0104] Specifically, when the gNB transmits a multicast session to all or part of the RRC connected UEs and RRC inactive UEs through the same PTM resources on the multicast CFR, if the gNB configures HARQ ACK / NACK feedback resources for some RRC connected UEs, the gNB can retransmit in PTM mode according to the HARQ ACK / NACK feedback information of these UEs. When the gNB supports retransmission of the multicast session in PTM mode, the DRX mode configured by the gNB for the multicast session should support retransmission; otherwise, the DRX mode configured by the gNB for the multicast session does not support retransmission.

[0105] For RRC connected UEs, these UEs work on their own activated DL BWPs. When the activated DL BWP of an RRC connected UE contains a multicast CFR, the gNB can transmit the multicast session to the RRC inactive UE and the UE simultaneously through the same PTM resource on the multicast CFR; when the activated DL BWP of an RRC connected UE does not contain a multicast CFR, the gNB can only transmit the multicast session to the UE through the CFR configured on the activated DL BWP of the UE.

[0106] (3) When the gNB transmits a multicast session to an RRC connected UE and an RRC inactive UE through different PTM resources, the gNB allocates a G-RNTI to the multicast session for identifying the multicast session on the air interface. The gNB transmits the multicast session to the RRC inactive UE through the PTM resources on the multicast CFR. The gNB configures a DRX mode for the multicast session. The DRX mode is used to send the multicast session to the RRC inactive UE on the multicast CFR. The DRX mode does not support retransmission of the multicast session.

[0107] Specifically, when the gNB transmits a multicast session to RRC connected UEs and RRC inactive UEs through different PTM resources, for RRC inactive UEs, the gNB can only transmit the multicast session to these UEs through multicast CFR. Since the RRC inactive UE cannot feedback the HARQ ACK / NACK information, the gNB cannot perform retransmission when transmitting the multicast session on the multicast CFR. Accordingly, the DRX mode configured by the gNB for the multicast session does not support retransmission.

[0108] How the gNB transmits a multicast session to an RRC connected UE through additionally allocated PTM resources is not the content of the present invention and will not be elaborated on herein.

[0109] (4) The gNB determines the configuration information of the multicast session. The configuration information of the multicast session includes: G-RNTI, DRX mode configuration information, and other necessary information.

[0110] When the gNB uses semi-persistent scheduling to transmit a multicast session, that is, when the scheduling mode of the multicast session is semi-persistent scheduling, the gNB allocates resources to the multicast session according to the scheduling mode of the multicast session and determines the configuration information of the multicast session as follows:

[0111] (1) When the gNB transmits a multicast session only to RRC-inactive UEs, the gNB transmits the multicast session using semi-static PTM resources on the multicast CFR, allocates a Group-Configured Scheduling-Radio Network Temporary Identifier (G-CS-RNTI) and a DRX mode to the multicast session, and allocates at least one Semi-Persistent Scheduling (SPS) resource to the multicast session. The multicast session uses only one HARQ process, and the multicast session does not support retransmission. The DRX mode of the multicast session does not support retransmission.

[0112] Specifically, when a multicast session is transmitted only to RRC inactive UEs, since the RRC inactive UEs cannot feedback ACK / NACK information of the HARQ process, the multicast session does not support retransmission, the DRX mode of the multicast session does not support retransmission, and the multicast session uses only one HARQ process.

[0113] It should be noted that the parameters contained in each SPS resource allocated to the multicast session refer to the IE "SPS-Config" in the 3GPP TS38.331 protocol.

[0114] (2) When the gNB transmits a multicast session to all or part of the RRC connected UEs and RRC inactive UEs through the same semi-static PTM resources on the multicast CFR, the gNB allocates a G-CS-RNTI and a DRX mode to the multicast session, where the G-CS-RNTI is used to identify the multicast session on the air interface, and the DRX mode is used to transmit the multicast session through the same semi-static PTM resources on the multicast CFR. At least one SPS resource is allocated to the multicast session. When the gNB does not retransmit the TB of the multicast session in PTM mode, the multicast session uses only one HARQ process, the multicast session does not support retransmission, and the DRX mode of the multicast session does not support retransmission. When the gNB retransmits the TB of the multicast session in PTM mode, the gNB allocates multiple HARQ processes to the multicast session, the multicast session supports retransmission, and the DRX mode of the multicast session supports retransmission.

[0115] Specifically, when the gNB transmits a multicast session to all or part of the RRC connected UEs and RRC inactive UEs through the same semi-static PTM resources on the multicast CFR, if the gNB configures HARQ ACK / NACK feedback resources for some RRC connected UEs, the gNB can retransmit in PTM mode according to the HARQ ACK / NACK feedback information of these UEs. When the gNB supports retransmission of the multicast session in PTM mode, the DRX mode configured by the gNB for the multicast session supports retransmission, and the gNB needs to configure multiple HARQ processes for the multicast session; otherwise, the DRX mode configured by the gNB for the multicast session does not support retransmission, and the multicast session uses only one HARQ process.

[0116] (3) When the gNB transmits a multicast session to an RRC connected UE and an RRC inactive UE through different semi-static PTM resources, the gNB transmits the multicast session to the RRC inactive UE through the semi-static PTM resources on the multicast CFR. The gNB allocates a G-CS-RNTI to the multicast session for identifying the multicast session on the air interface. The gNB allocates a DRX mode to the multicast session for transmitting the multicast session on the multicast CFR. At least one SPS resource is allocated to the multicast session. Each SPS resource is used to transmit the multicast session on the multicast CFR. The multicast session sent on the multicast CFR uses only one HARQ process. The multicast session does not support retransmission. The DRX mode of the multicast session does not support retransmission.

[0117] (4) Optionally, when the gNB adopts semi-static scheduling to transmit a multicast session, the gNB configures activated semi-static PTM resources for the multicast session on the multicast CFR.

[0118] Specifically, the gNB selects an SPS resource from the SPS resources allocated to the multicast session and determines the frequency domain resources, time domain resources, mapping method of virtual resource blocks (VRB) to physical resource blocks (PRB) and coding modulation method used when transmitting the multicast session through the selected SPS resource, generates an activated semi-static PTM resource, and the gNB periodically sends a physical downlink shared channel (PDSCH) through the activated semi-static PTM resource. The PDSCH carries the TB of the multicast session.

[0119] (5) The gNB determines the configuration information of the multicast session. The configuration information of the multicast session includes: G-CS-RNTI, configuration information of the DRX mode, and configuration information of each SPS resource; or includes: G-CS-RNTI, configuration information of the DRX mode, configuration information of each SPS resource, and configuration information of the activated semi-static PTM resources.

[0120] It should be noted that the configuration information of each SPS resource can be found in IE "SPS-Config" in the 3GPP TS38.331 protocol.

[0121] In addition, when the gNB adopts the semi-static scheduling mode or the dynamic scheduling mode to transmit the multicast session, when the DRX mode does not support the retransmission of the multicast session, the configuration information of the DRX mode does not include the retransmission related parameters. Specifically, when the DRX mode does not support the retransmission of the multicast session, the configuration information of the DRX mode includes the following parameters, and the meanings of these parameters are shown in Section 5.7a of the 3GPP TS 38.321 protocol.

[0122] The configuration information of DRX mode includes:

[0123] The first timer drx-onDurationTimerPTM;

[0124] Slot offset drx-SlotOffsetPTM;

[0125] The second timer drx-InactivityTimerPTM;

[0126] DRX cycle and start subframe offset drx-LongCycleStartOffsetPTM: used to define the DRX cycle drx-LongCycle-PTM and start subframe offset drx-StartOffset-PTM.

[0127] When the DRX mode supports retransmission of multicast sessions, the configuration information of the DRX mode includes retransmission related parameters. Specifically, when the DRX mode supports retransmission of multicast sessions, the configuration information of the DRX mode includes the following parameters, and the meanings of these parameters are shown in Section 5.7b of the 3GPP TS38.321 protocol.

[0128] The configuration information of DRX mode includes:

[0129] The first timer drx-onDurationTimerPTM;

[0130] Slot offset drx-SlotOffsetPTM;

[0131] The second timer drx-InactivityTimerPTM;

[0132] DRX cycle and start subframe offset drx-LongCycleStartOffsetPTM: used to define the DRX cycle drx-LongCycle-PTM and the start subframe offset drx-StartOffset-PTM; the third timer drx-RetransmissionTimerDL-PTM;

[0133] The fourth timer drx-HARQ-RTT-TimerDL-PTM;

[0134] S104: The gNB sends the configuration information of the multicast session to the RRC inactive UE receiving the multicast session through dedicated signaling and multicast MCCH.

[0135] In this step, before the UE joins the multicast session and enters the RRC inactive state, the gNB sends the configuration information of the multicast session to the UE through dedicated signaling.

[0136] The gNB sends a multicast SIB in the NR cell, and the multicast SIB carries the configuration information of the multicast MCCH. The gNB sends a multicast MCCH in the NR cell, and the multicast MCCH carries the configuration information of the multicast session.

[0137] S105: The gNB schedules the multicast session and sends the data of the multicast session.

[0138] When a multicast session adopts dynamic scheduling, that is, when the scheduling mode of the multicast session is dynamic scheduling, whenever the gNB schedules a multicast session, the gNB sends the Physical Downlink Control Channel (PDCCH) and PDSCH of the multicast session. The cyclic redundancy check (CRC) of the PDCCH is scrambled with the G-RNTI. The format of the downlink control information (DCI) on the PDCCH is the scheduling information of the PDSCH of the multicast session. The PDSCH of the multicast session adopts G-RNTI in bit scrambling, and the PDSCH of the multicast session carries the TB of the multicast session.

[0139] When a multicast session sent on a multicast CFR does not support retransmission, the DCI format on the PDCCH of the multicast session needs to provide the following fields:

[0140] Frequency domain resource allocation: bits, of which is the number of PRBs included in the multicast CFR, Indicates a round-up operation.

[0141] Time domain resource allocation: 4 bits.

[0142] VRB to PRB mapping: 1 bit.

[0143] Modulation and coding method: 5 bits.

[0144] Redundancy version: 2 bits.

[0145] When a multicast session sent on a multicast CFR supports retransmission, the DCI format on the PDCCH of the multicast session needs to provide the following fields:

[0146] Frequency domain resource allocation: bits, is the number of PRBs included in the multicast CFR.

[0147] Time domain resource allocation: 4 bits.

[0148] VRB to PRB mapping: 1 bit.

[0149] Modulation and coding method: 5 bits.

[0150] New data indication: 1 bit.

[0151] Redundancy version: 2 bits.

[0152] HARQ process number: 4 bits.

[0153] Downlink allocation index: 2 bits.

[0154] Physical Uplink Control Channel (PUCCH) resource indication: 3 bits.

[0155] PDSCH to HARQ feedback timing indication: 3 bits

[0156] Optionally, the gNB uses DCI format 4-1 to schedule multicast sessions with or without retransmission support. DCI format 4-1 provides the following fields:

[0157] Frequency domain resource allocation: bits, is the number of PRBs included in the multicast CFR.

[0158] Time domain resource allocation: 4 bits.

[0159] VRB to PRB mapping: 1 bit.

[0160] Modulation and coding method: 5 bits.

[0161] New data indication: 1 bit.

[0162] Redundancy version: 2 bits.

[0163] HARQ process number: 4 bits.

[0164] Downlink allocation index: 2 bits.

[0165] PUCCH resource indication: 3 bits.

[0166] PDSCH to HARQ feedback timing indication: 3 bits.

[0167] Reserved bits: 3 bits.

[0168] When DCI format 4-1 is used to schedule a multicast session, if the multicast session supports retransmission, the gNB sets the fields in DCI format 4-1 except the reserved bit field according to the scheduling information carried on the PDCCH of the multicast session; if the multicast session does not support retransmission, the gNB sets the following fields in DCI format 4-1 according to the scheduling information carried on the PDCCH of the multicast session, and the other fields have no effect:

[0169] Frequency domain resource allocation: bits, is the number of PRBs included in the multicast CFR.

[0170] Time domain resource allocation: 4 bits.

[0171] VRB to PRB mapping: 1 bit.

[0172] Modulation and coding method: 5 bits.

[0173] Redundancy version: 2 bits.

[0174] When a multicast session adopts semi-static scheduling, that is, when the scheduling mode of the multicast session is semi-static scheduling, whenever the gNB schedules a multicast session, the gNB allocates semi-static PTM resources to the multicast session, and notifies the configuration information of the semi-static PTM resources allocated to the multicast session to the RRC inactive UE receiving the multicast session through method 1 or method 2. Then, the gNB sends PDSCH through the semi-static PTM resources allocated to the multicast session. The PDSCH uses G-CS-RNTI for bit scrambling, and the PDSCH carries the TB of the multicast session.

[0175] Method 1: The gNB activates the semi-static PTM resources of the multicast session through the PDCCH scrambled with G-CS-RNTI via CRC.

[0176] Specifically, the gNB sends a PDCCH scrambled with a CRC using the G-CS-RNTI, and the DCI format on the PDCCH is used to activate the semi-static PTM resources of the multicast session. Preferably, the DCI format on the PDCCH is DCI format 4-1.

[0177] Specifically, the gNB sends the PDCCH scrambled with CRC using -G-CS-RNTI in a beam scanning manner to activate the semi-static PTM resources of the multicast session in each SSB beam direction.

[0178] Method 2: The gNB sends the configuration information of the multicast session through the multicast MCCH, and the configuration information of the multicast session provides the semi-static PTM resource configuration information of the multicast session. When the gNB sends the configuration information of the multicast session on the multicast MCCH for the first time or whenever the configuration information of the multicast session is updated, the gNB sends a multicast MCCH change notification. Preferably, the multicast MCCH change notification is sent through 2 bits in the DCI format on the PDCCH that schedules the multicast MCCH: when the configuration information of a multicast session is sent for the first time on the multicast MCCH, the first bit is set to 1, otherwise the first bit is set to 0; when the configuration information of the existing multicast session on the multicast MCCH is updated, the second bit is set to 1, otherwise the second bit is set to 0. The multicast MCCH uses a fixed RNTI to identify the multicast MCCH on the air interface, and the CRC of the PDCCH of the multicast MCCH is scrambled with the RNTI.

[0179] Specifically, when multicast MCCH is used to send the configuration information of the semi-static PTM resources for the multicast session, the configuration information of the semi-static PTM resources for the multicast session provides all the relevant information indicated by the DCI format on the PDCCH in method one, that is, the semi-static PTM resources determined by the UE according to the DCI format on the PDCCH scrambled by CRC with G-CS-RNTI are the same as the semi-static PTM resources determined by the UE according to the configuration information of the semi-static PTM resources for the multicast session on the multicast MCCH.

[0180] S106: The RRC inactive UE receives configuration information of the multicast session, and receives data of the multicast session according to the configuration information of the multicast session.

[0181] When a multicast session adopts dynamic scheduling, the UE obtains configuration information of the multicast session through dedicated signaling and the multicast MCCH, and the UE receives the multicast session according to the configuration information of the multicast session.

[0182] When the multicast session adopts semi-static scheduling, the UE obtains the configuration information of the multicast session through dedicated signaling, the PDCCH scrambled by the CRC with the G-CS-RNTI, and the multicast MCCH, and the UE receives the multicast session according to the configuration information of the multicast session.

[0183] When the multicast session does not support retransmission, the UE receives the multicast session in the following manner according to the configuration information of the DRX mode in the configuration information of the multicast session:

[0184] When the gNB configures DRX mode for a multicast session, the activation time includes the time when the following two timers run:

[0185] The first timer drx-onDurationTimerPTM;

[0186] The second timer drx-InactivityTimerPTM.

[0187] The UE performs the following processing:

[0188] If the preset formula "[(SFN×10)+subframe number]modulo(drx-LongCycle-PTM)=drx-StartOffset-PTM" holds, starting from the subframe that satisfies the preset formula, the RRC inactive UE starts the first timer drx-onDurationTimerPTM after drx-SlotOffsetPTM time slots, where modulo represents modulo operation, SFN represents the radio frame number, subframe number represents the subframe number, drx-LongCycle-PTM represents the DRX cycle, drx-StartOffset-PTM represents the starting subframe offset, and drx-SlotOffsetPTM represents the time slot offset;

[0189] During the activation time, the RRC inactive UE monitors the PDCCH whose CRC is scrambled with G-RNTI / G-CS-RNTI; if the PDCCH indicates a downlink transmission, the RRC inactive UE starts or restarts the second timer drx-InactivityTimerPTM within the first symbol after the end of PDCCH reception.

[0190] When the multicast session supports retransmission, the UE receives the multicast session in the following manner according to the configuration information of the DRX mode in the configuration information of the multicast session:

[0191] When the gNB configures DRX mode for a multicast session, the activation time includes the time when the following three timers run:

[0192] The first timer drx-onDurationTimerPTM;

[0193] The second timer drx-InactivityTimerPTM;

[0194] The third timer drx-RetransmissionTimerDL-PTM.

[0195] The UE performs the following processing: when a Media Access Control (MAC) Protocol Data Unit (PDU) is received on the configured semi-static resource, if HARQ feedback is triggered (in this case, some RRC connected UEs are triggered to provide HARQ feedback), the RRC inactive UE does not need to provide HARQ feedback, but the RRC inactive UE needs to determine the position of sending downlink HARQ feedback, and start the fourth timer drx-HARQ-RTT-TimerDL-PTM of the corresponding HARQ process within the first symbol after the end of sending the downlink HARQ feedback;

[0196] The RRC inactive UE stops the third timer drx-RetransmissionTimerDL-PTM of the corresponding HARQ process;

[0197] When a fourth timer drx-HARQ-RTT-TimerDL-PTM times out, if the data of the corresponding HARQ process is not successfully decoded, the RRC inactive UE starts the third timer drx-RetransmissionTimerDL-PTM of the corresponding HARQ process within the first symbol after the fourth timer drx-HARQ-RTT-TimerDL-PTM times out;

[0198] When the RRC inactive UE receives a DRX Command MACCE in a DCI format scrambled by G-RNTI via CRC, the RRC inactive UE stops the first timer drx-onDurationTimerPTM and the second timer drx-InactivityTimerPTM;

[0199] When the preset formula "[(SFN×10)+subframe number]modulo(drx-LongCycle-PTM)=drx-StartOffset-PTM" holds true, starting from the subframe that satisfies the preset formula, the RRC inactive UE starts the first timer drx-onDurationTimerPTM after drx-SlotOffsetPTM time slots, where modulo represents a modulo operation, SFN represents a radio frame number, subframe number represents a subframe number, drx-LongCycle-PTM represents a DRX cycle, drx-StartOffset-PTM represents a starting subframe offset, and drx-SlotOffsetPTM represents a time slot offset; within the activation time, the RRC inactive UE monitors the PDCCH scrambled by the CRC using the G-RNTI / G-CS-RNTI;

[0200] If the received PDCCH indicates a downlink transmission, if HARQ feedback is triggered (in this case, some RRC connected UEs are triggered to provide HARQ feedback), the RRC inactive UE does not need to provide HARQ feedback, but the RRC inactive UE needs to determine the position of sending downlink HARQ feedback, and start the fourth timer drx-HARQ-RTT-TimerDL-PTM of the corresponding HARQ process within the first symbol after the end of the transmission carrying the downlink HARQ feedback, and the RRC inactive UE stops the third timer drx-RetransmissionTimerDL-PTM of the corresponding HARQ process;

[0201] If the PDCCH indicates a new downlink transmission, the RRC inactive UE starts or restarts the second timer drx-InactivityTimerPTM in the first symbol after the PDCCH reception ends.

[0202] In the method for sending a multicast session in an RRC inactive state in an NR cell provided in this embodiment, under dynamic scheduling, the gNB configures the DRX mode according to whether the multicast session supports retransmission to the multicast session in PTM mode; under semi-static scheduling, the gNB configures the number of HARQ processes and the DRX mode according to whether the multicast session supports retransmission to the multicast session in PTM mode; the gNB sends the configuration information of the multicast session through dedicated signaling and multicast MCCH, and schedules the multicast session and sends the data of the multicast session according to the configuration information of the multicast session; the RRC inactive UE receives the configuration information of the multicast session, and receives the data of the multicast session according to the configuration information of the multicast session. Therefore, the method for sending a multicast session in an RRC inactive state in an NR cell provided in this embodiment achieves the purpose of the UE receiving the multicast session in the RRC inactive state.

[0203] An embodiment of the present application also provides a gNB for implementing the method for sending a multicast session in the RRC inactive state in the above-mentioned NR cell.

[0204] An embodiment of the present application also provides a UE for implementing a method for sending a multicast session in an RRC inactive state in the above-mentioned NR cell.

[0205] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for sending a multicast session in an RRC inactive state in an NR cell, characterized in that: include: The gNB configures a multicast SIB, a multicast MCCH and a multicast CFR for the NR cell, wherein the multicast SIB carries the configuration information of the multicast MCCH, the multicast MCCH is used to transmit the configuration information of the multicast session in the RRC inactive state, and the multicast CFR is used to transmit the multicast session in the RRC inactive state; The gNB determines, for a multicast session in an RRC inactive state, a scheduling mode of the multicast session, where the scheduling mode of the multicast session is dynamic scheduling or semi-static scheduling; The gNB allocates resources to the multicast session according to the scheduling mode of the multicast session, and determines configuration information of the multicast session; The gNB sends the configuration information of the multicast session to the RRC inactive UE receiving the multicast session through dedicated signaling and the multicast MCCH; The gNB schedules the multicast session and sends data of the multicast session; The RRC inactive UE receives configuration information of the multicast session, and receives data of the multicast session according to the configuration information of the multicast session.

2. The method according to claim 1, characterized in that When the scheduling mode of the multicast session is dynamic scheduling, the gNB allocates resources to the multicast session according to the scheduling mode of the multicast session, including: When the gNB transmits the multicast session only to the RRC inactive UE, the gNB allocates a G-RNTI and a DRX mode to the multicast session, and the DRX mode allocated to the multicast session does not support retransmission of the multicast session; When the gNB transmits the multicast session to all or part of the RRC connected UEs and RRC inactive UEs through the same PTM resources on the multicast CFR, the gNB allocates a G-RNTI and a DRX mode to the multicast session, where the G-RNTI is used to identify the multicast session on the air interface, and the DRX mode is used to transmit the multicast session through the same PTM resources on the multicast CFR; when the gNB does not retransmit the TB of the multicast session in PTM mode, the DRX mode configured by the gNB for the multicast session does not support retransmission of the multicast session; when the gNB retransmits the TB of the multicast session in PTM mode, the DRX mode configured by the gNB for the multicast session supports retransmission of the multicast session; When the gNB transmits the multicast session to the RRC connected UE and the RRC inactive UE through different PTM resources, the gNB allocates a G-RNTI to the multicast session for identifying the multicast session on the air interface, the gNB transmits the multicast session to the RRC inactive UE through the PTM resources on the multicast CFR, the gNB configures a DRX mode for the multicast session, the DRX mode is used to send the multicast session to the RRC inactive UE on the multicast CFR, and the DRX mode does not support retransmission of the multicast session.

3. The method according to claim 2, characterized in that The configuration information of the multicast session includes: G-RNTI, DRX mode configuration information.

4. The method according to claim 1, characterized in that When the scheduling mode of the multicast session is semi-persistent scheduling, the gNB allocates resources to the multicast session according to the scheduling mode of the multicast session, including: When the gNB transmits the multicast session only to the RRC inactive UE, the gNB allocates a G-CS-RNTI and a DRX mode to the multicast session, allocates at least one SPS resource to the multicast session, the multicast session uses only one HARQ process, and the DRX mode of the multicast session does not support retransmission; When the gNB transmits the multicast session to all or part of the RRC connected UEs and RRC inactive UEs through the same semi-static PTM resources on the multicast CFR, the gNB allocates a G-CS-RNTI and a DRX mode to the multicast session, and allocates at least one SPS resource to the multicast session, the G-CS-RNTI is used to identify the multicast session on the air interface, and the DRX mode is used to transmit the multicast session through the same semi-static PTM resources on the multicast CFR; when the gNB does not retransmit the TB of the multicast session in PTM mode, the multicast session uses only one HARQ process, and the DRX mode of the multicast session does not support retransmission; when the gNB retransmits the TB of the multicast session in PTM mode, multiple HARQ processes are allocated to the multicast session, and the DRX mode of the multicast session supports retransmission; When the gNB transmits the multicast session to the RRC connected UE and the RRC inactive UE through different semi-static PTM resources, the gNB transmits the multicast session to the RRC inactive UE through the semi-static PTM resources on the multicast CFR, the gNB allocates a G-CS-RNTI to the multicast session for identifying the multicast session on the air interface, allocates a DRX mode to the multicast session for transmitting the multicast session on the multicast CFR, allocates at least one SPS resource to the multicast session, the SPS resource is used to transmit the multicast session on the multicast CFR, the multicast session uses only one HARQ process on the multicast CFR, and the DRX mode of the multicast session does not support retransmission.

5. The method according to claim 4, characterized in that The method further comprises: The gNB configures activated semi-static PTM resources for the multicast session on the multicast CFR: the gNB selects an SPS resource from the SPS resources allocated to the multicast session and determines the frequency domain resources, time domain resources, VRB to PRB mapping method and coding modulation method used when transmitting the multicast session through the selected SPS resource, and generates activated semi-static PTM resources.

6. The method according to claim 4 or 5, characterized in that: When the gNB adopts a semi-static scheduling method to transmit the multicast session, the configuration information of the multicast session includes: G-CS-RNTI, DRX mode configuration information, and configuration information of multiple SPS resources; or includes: G-CS-RNTI, DRX mode configuration information, configuration information of multiple SPS resources, and configuration information of activated semi-static PTM resources.

7. The method according to claim 2 or 4, characterized in that: When the DRX mode does not support retransmission of the multicast session, the parameters in the configuration information of the DRX mode include: a first timer drx-onDurationTimerPTM, a time slot offset drx-SlotOffsetPTM, a second timer drx-InactivityTimerPTM, and a DRX cycle and a start subframe offset drx-LongCycleStartOffsetPTM.

8. The method according to claim 2 or 4, characterized in that: When the DRX mode supports retransmission of the multicast session, the parameters in the configuration information of the DRX mode include: a first timer drx-onDurationTimerPTM, a time slot offset drx-SlotOffsetPTM, a second timer drx-InactivityTimerPTM, a DRX cycle and a start subframe offset drx-LongCycleStartOffsetPTM, a third timer drx-RetransmissionTimerDL-PTM, and a fourth timer drx-HARQ-RTT-TimerDL-PTM.

9. The method according to claim 1, characterized in that: The gNB sends the configuration information of the multicast session to an RRC inactive UE receiving the multicast session through dedicated signaling and the multicast MCCH, including: Before the UE joins the multicast session and enters the RRC inactive state, the gNB sends configuration information of the multicast session to the UE through dedicated signaling; The gNB sends the multicast SIB and the multicast MCCH in the NR cell, the multicast SIB carries the configuration information of the multicast MCCH, and the multicast MCCH carries the configuration information of the multicast session.

10. The method according to claim 1, characterized in that When the scheduling mode of the multicast session is dynamic scheduling, the gNB schedules the multicast session and sends data of the multicast session, including: Whenever the gNB schedules the multicast session, the gNB sends the PDCCH and PDSCH of the multicast session, the CRC of the PDCCH is scrambled with the G-RNTI, the DCI format on the PDCCH is the scheduling information of the PDSCH of the multicast session, the PDSCH of the multicast session uses the G-RNTI during bit scrambling, and the PDSCH of the multicast session carries the TB of the multicast session; When the multicast session sent on the multicast CFR does not support retransmission, the fields in the DCI format on the PDCCH of the multicast session include: frequency domain resource allocation, time domain resource allocation, VRB to PRB mapping, modulation and coding method, and redundancy version.

11. The method according to claim 1, characterized in that: When the scheduling mode of the multicast session is dynamic scheduling, the gNB schedules the multicast session and sends data of the multicast session, including: Whenever the gNB schedules the multicast session, the gNB sends the PDCCH and PDSCH of the multicast session, the CRC of the PDCCH is scrambled with the G-RNTI, the DCI format on the PDCCH is the scheduling information of the PDSCH of the multicast session, the PDSCH of the multicast session uses the G-RNTI during bit scrambling, and the PDSCH of the multicast session carries the TB of the multicast session; When the multicast session sent on the multicast CFR supports retransmission, the fields in the DCI format on the PDCCH of the multicast session include: frequency domain resource allocation, time domain resource allocation, VRB to PRB mapping, modulation and coding method, redundancy version, HARQ process number, downlink allocation subscript, PUCCH resource indication, and PDSCH to HARQ feedback timing indication.

12. The method according to claim 10 or 11, characterized in that: The gNB scheduling the multicast session includes: The gNB schedules the multicast session supporting retransmission or not supporting retransmission using DCI format 4-1; If the multicast session supports retransmission, the gNB sets each field in DCI format 4-1 except the reserved bit field according to the scheduling information carried on the PDCCH of the multicast session; If the multicast session does not support retransmission, the gNB sets the frequency domain resource allocation, time domain resource allocation, VRB to PRB mapping, modulation and coding method, and redundancy version in DCI format 4-1 according to the scheduling information carried on the PDCCH of the multicast session.

13. The method according to claim 1, characterized in that When the scheduling mode of the multicast session is semi-persistent scheduling, the gNB schedules the multicast session and sends data of the multicast session, including: The gNB allocates a semi-static PTM resource to the multicast session, and sends configuration information of the semi-static PTM resource allocated to the multicast session to an RRC inactive UE receiving the multicast session through mode 1; The gNB sends a PDSCH through a semi-static PTM resource allocated to the multicast session, the PDSCH uses a G-CS-RNTI during bit scrambling, and the PDSCH carries a TB of the multicast session; Among them, method 1: the gNB activates the semi-static PTM resources of the multicast session through the PDCCH encrypted with G-CS-RNTI by CRC, and the DCI format on the PDCCH is DCI format 4-1.

14. The method according to claim 1, characterized in that When the scheduling mode of the multicast session is semi-persistent scheduling, the gNB schedules the multicast session and sends data of the multicast session, including: The gNB allocates a semi-static PTM resource to the multicast session, and sends configuration information of the semi-static PTM resource allocated to the multicast session to an RRC inactive UE receiving the multicast session through mode 2; The gNB sends a PDSCH through a semi-static PTM resource allocated to the multicast session, the PDSCH uses a G-CS-RNTI during bit scrambling, and the PDSCH carries a TB of the multicast session; Among them, method 2: the gNB sends the configuration information of the multicast session through the multicast MCCH, and the configuration information of the multicast session provides the semi-static PTM resource configuration information of the multicast session; when the gNB sends the configuration information of the multicast session on the multicast MCCH for the first time or whenever the configuration information of the multicast session is updated, the gNB sends a multicast MCCH change notification; The multicast MCCH change notification is sent through 2 bits in the DCI format on the PDCCH that schedules the multicast MCCH: when the configuration information of a multicast session is sent for the first time on the multicast MCCH, the first bit is set to 1, otherwise the first bit is set to 0; when the configuration information of an existing multicast session on the multicast MCCH is updated, the second bit is set to 1, otherwise the second bit is set to 0.

15. The method according to claim 1, characterized in that The RRC inactive UE receives the configuration information of the multicast session, and receives the data of the multicast session according to the configuration information of the multicast session, including: When the multicast session adopts dynamic scheduling, the RRC inactive UE obtains the configuration information of the multicast session through dedicated signaling and the multicast MCCH; When the multicast session adopts semi-persistent scheduling, the RRC inactive UE obtains the configuration information of the multicast session through dedicated signaling, the PDCCH scrambled by the CRC using the G-CS-RNTI, and the multicast MCCH; When the multicast session does not support retransmission, the RRC inactive UE receives data of the multicast session according to configuration information of the DRX mode in the configuration information of the multicast session; The RRC inactive UE receives data of the multicast session according to the configuration information of the DRX mode in the configuration information of the multicast session, including: When the gNB configures DRX mode for a multicast session, the activation time includes the time when the following two timers run: The first timer drx-onDurationTimerPTM; The second timer drx-InactivityTimerPTM; The RRC inactive UE performs the following processing: If the preset formula "[(SFN×10)+subframe number]modulo(drx-LongCycle-PTM)=drx-StartOffset-PTM" holds, starting from the subframe that satisfies the preset formula, the RRC inactive UE starts the first timer drx-onDurationTimerPTM after drx-SlotOffsetPTM time slots, where modulo represents a modulo operation, SFN represents a radio frame number, subframe number represents a subframe number, drx-LongCycle-PTM represents a DRX cycle, drx-StartOffset-PTM represents a start subframe offset, and drx-SlotOffsetPTM represents a time slot offset; During the activation time, the RRC inactive UE monitors the PDCCH scrambled by G-RNTI / G-CS-RNTI for CRC; if the PDCCH indicates a downlink transmission, the RRC inactive UE starts or restarts the second timer drx-InactivityTimerPTM within the first symbol after the PDCCH reception ends.

16. The method according to claim 1, characterized in that The RRC inactive UE receives the configuration information of the multicast session, and receives the data of the multicast session according to the configuration information of the multicast session, including: When the multicast session adopts dynamic scheduling, the RRC inactive UE obtains the configuration information of the multicast session through dedicated signaling and the multicast MCCH; When the multicast session adopts semi-persistent scheduling, the RRC inactive UE obtains the configuration information of the multicast session through dedicated signaling, the PDCCH scrambled by the CRC using the G-CS-RNTI, and the multicast MCCH; When the multicast session supports retransmission, the RRC inactive UE receives data of the multicast session according to configuration information of the DRX mode in the configuration information of the multicast session; The RRC inactive UE receives data of the multicast session according to the configuration information of the DRX mode in the configuration information of the multicast session, including: When the gNB configures DRX mode for a multicast session, the activation time includes the time when the following three timers run: The first timer drx-onDurationTimerPTM; The second timer drx-InactivityTimerPTM; The third timer drx-RetransmissionTimerDL-PTM; The RRC inactive UE performs the following processing: when a MAC PDU is received on the configured semi-static resource, if HARQ feedback is triggered, the RRC inactive UE does not need to provide HARQ feedback, the RRC inactive UE determines the position for sending downlink HARQ feedback, and starts the fourth timer drx-HARQ-RTT-TimerDL-PTM of the corresponding HARQ process within the first symbol after the end of sending the downlink HARQ feedback; The RRC inactive UE stops the third timer drx-RetransmissionTimerDL-PTM of the corresponding HARQ process; When a fourth timer drx-HARQ-RTT-TimerDL-PTM times out, if data of the corresponding HARQ process is not successfully decoded, the RRC inactive UE starts the third timer drx-RetransmissionTimerDL-PTM of the corresponding HARQ process within the first symbol after the fourth timer drx-HARQ-RTT-TimerDL-PTM times out; When the RRC inactive UE receives a DRX Command MACCE in a DCI format scrambled by the CRC using the G-RNTI, the RRC inactive UE stops the first timer drx-onDurationTimerPTM and the second timer drx-InactivityTimerPTM; When the preset formula "[(SFN×10)+subframe number]modulo(drx-LongCycle-PTM)=drx-StartOffset-PTM" holds, starting from the subframe that satisfies the preset formula, the RRC inactive UE starts the first timer drx-onDurationTimerPTM after drx-SlotOffsetPTM time slots, where modulo represents a modulo operation, SFN represents a radio frame number, subframe number represents a subframe number, drx-LongCycle-PTM represents a DRX cycle, drx-StartOffset-PTM represents a start subframe offset, and drx-SlotOffsetPTM represents a time slot offset; During the activation time, the RRC inactive UE monitors the PDCCH scrambled by the CRC using the G-RNTI / G-CS-RNTI; If the received PDCCH indicates a downlink transmission, if the HARQ feedback is triggered, the RRC inactive UE does not need to provide HARQ feedback, the RRC inactive UE determines the position for sending the downlink HARQ feedback, starts the fourth timer drx-HARQ-RTT-TimerDL-PTM of the corresponding HARQ process within the first symbol after the end of the transmission carrying the downlink HARQ feedback, and stops the third timer drx-RetransmissionTimerDL-PTM of the corresponding HARQ process; If the PDCCH indicates a new downlink transmission, the RRC inactive UE starts or restarts the second timer drx-InactivityTimerPTM in the first symbol after the PDCCH reception ends.