Method executed by user equipment, and user equipment

Abstract

Provided in the present disclosure are a method executed by a user equipment, and a user equipment. The method executed by a user equipment (UE) comprises: the UE receives a radio resource control (RRC) release (RRCRelease) message from a base station; and, when the UE is configured by the RRCRelease message to receive in RRC_INACTIVE an MBS multicast session and the RRCRelease message does not comprise at least one mrb-ListMulticast which is not instructed to stop detecting the MBS multicast session of a G-RNTI, acquiring a MBS multicast configuration message from a multicast MCCH, wherein the RRCRelease message is used for commanding release of an RRC connection or suspension of the RRC connection, a mrb-ListMulticast field is a multicast MRB list to which the associated multicast MBS session is mapped, and the MBS multicast configuration message comprises control information used for the RRC_INACTIVE UE to receive, by means of a multicast MRB, an MBS multicast service.

Description

Method performed by user equipment and user equipment Technical Field

[0001] The present invention relates to the technical field of wireless communications, and more particularly, to a method executed by a user equipment and the user equipment. Background Art

[0002] A study item (SI) on improving the 5G multicast broadcast service architecture (see SP-190625) has been approved. One of the objectives of this SI (referred to as Objective A) is to support universal MBS services in the 5GS. Use cases that could benefit from this feature include (but are not limited to) public safety, vehicle-to-everything (V2X) applications, transparent IPv4 / IPv6 multicast transmission, IPTV, wireless software delivery, group communications, and IoT applications. Accordingly, at the 3rd Generation Partnership Project (3GPP) RAN#86 plenary meeting, a work item on NR multicast and broadcast service (NR MBS) was proposed and approved (see non-patent document RP-193248: New WID: NR Multicast and Broadcast Service). This work item aims to provide support for Objective A in the RAN. The objectives of this work item have been largely achieved, and the relevant solutions are described in 3GPP Release 17 technical documents such as TS 38.300-h70, TS 38.331-h70, and TS 38.321-h70. At the 3GPP RAN#94 plenary meeting, a work item titled Enhanced NR Multicast and Broadcast Services was approved (see non-patent literature: RP-213568: New WID: Enhancements of NR Multicast and Broadcast Services). This work item aims to further enhance MBS Multicast and Broadcast Services in Release 17, with one of its goals being to support user equipment receiving MBS multicast services / sessions even when RRC is not active.

[0003] The present invention discusses issues related to RAN supporting user equipment to receive MBS multicast services / sessions in an RRC inactive state. Summary of the Invention

[0004] In order to solve at least part of the above problems, the present invention provides a method performed by a user equipment and the user equipment.

[0005] According to a first aspect of the present invention, a method performed by a user equipment (UE) is provided, comprising: the UE receiving a radio resource control (RRC) message from a base station; and obtaining an MBS multicast configuration message from a multicast MCCH when the UE is configured to receive an MBS multicast session in RRC_INACTIVE and the RRC message does not include at least one multicast MRB for the MBS multicast session that is not indicated to stop detecting a G-RNTI.

[0006] In the above-mentioned method involved in the first aspect of the present invention, it also includes, when the UE is configured to receive the MBS multicast session in RRC_INACTIVE, if there is no multicast MRB in the UE for the MBS multicast session that is not instructed to stop detecting G-RNTI, obtaining the MBS multicast configuration message from the multicast MCCH.

[0007] Furthermore, according to a second aspect of the present invention, a method performed by a user equipment (UE) is provided, comprising: the UE receiving a paging message from a base station; if the UE is in RRC_INACTIVE mode and has joined one or more MBS sessions indicated by one or more TMGIs included in the paging message, performing the following operations:

[0008] Operation 2-1: If condition A1, A2, or A3 is met, and further, if at least one of the following conditions B1 to B5 is met, the RRC connection recovery process is initiated;

[0009] Operation 2-2: If the condition of operation 2-1 is not met, and it is not met: for all MBS multicast sessions that the UE has joined and is configured for RRC_INACTIVE reception, the UE is notified to stop detecting G-RNTI, and it is met: there is at least one MBS multicast session that has been notified to stop detecting G-RNTI, and its multicast MRB is not included in the RRC release message, then obtain the MBSMulticastConfiguration message from the multicast MCCH.

[0010] in,

[0011] Condition A1: The paging message does not contain the PagingRecordList field;

[0012] Condition A2: The ue-Identity contained in any pagingRecord in the PagingRecordList field of the paging message does not match the UE identity assigned by the upper layer and the fullI-RNTI stored in the UE;

[0013] Condition A3: The ue-identity contained in a pagingRecord in the PagingRecordList field of the paging message matches the fullI-RNTI stored in the UE, and the mt-SDT field is included in the paging message;

[0014] Condition B1: The UE is not configured to receive MBS multicast in RRC_INACTIVE mode;

[0015] Condition B2: There is at least one MBS multicast session that the UE has joined, indicated by the TMGI, which is not configured for reception in RRC_INACTIVE mode;

[0016] Condition B3: There is at least one MBS multicast session that the UE has joined, indicated by the TMGI included in the paging message, which is not configured for reception in RRC_INACTIVE;

[0017] Condition B4: There is at least one MBS multicast session that the UE has joined, as indicated by the TMGI, which is not indicated by the paging message as being receivable in RRC_INACTIVE;

[0018] Condition B5: There is at least one MBS multicast session that the UE has joined and that is indicated by the TMGI included in the paging message but is not indicated by the paging message as being receivable in RRC_INACTIVE.

[0019] In addition, according to a third aspect of the present invention, a method performed by a user equipment UE is provided, comprising: the UE receiving a radio resource control RRC release message from a base station; when the UE is configured to receive an MBS multicast session in RRC_INACTIVE, if the RRC release message does not include the mbs-SessionInfoListMulticast field, it is considered that all joined multicast sessions are configured to be received in RRC_INACTIVE.

[0020] In the method involved in the third aspect of the present invention, for all joined MBS multicast sessions, it is considered that the stopMonitoringRNTI field of the MBS multicast session has been received, or for all joined MBS multicast sessions, it is considered that the stopMonitoringRNTI field of the MBS multicast session has not been received.

[0021] In addition, according to the fourth aspect of the present invention, a method performed by a user equipment UE is provided, including: the UE obtains multicast MCCH information from the multicast MCCH using a multicast MCCH information acquisition process; the multicast MCCH information obtained from the multicast MCCH information acquisition process covers any stored multicast MCCH information and the configuration of the MBS multicast session configured by dedicated RRC signaling.

[0022] In the method involved in the fourth aspect of the present invention, the configuration of the MBS multicast session configured through dedicated RRC signaling is the configuration of the MBS multicast session configured by the UE when RRC_CONNECTED, or the configuration of the MBS multicast session obtained by the UE from the RRC release message.

[0023] In addition, according to a fifth aspect of the present invention, there is provided a user equipment, comprising: a processor; and a memory storing instructions, wherein the instructions execute the above method when executed by the processor.

[0024] According to the method performed by the user equipment and the user equipment involved in the present invention, the user equipment UE can correctly receive the MBS multicast session when in RRC_INACTIVE. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The above and other features of the present invention will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

[0026] FIG1 is a schematic flow chart showing a method executed by a user equipment in embodiment 1 of the present invention.

[0027] FIG2 is a schematic flowchart showing a method executed by a user equipment in embodiment 2 of the present invention.

[0028] FIG3 is a schematic flowchart showing a method executed by a user equipment in embodiment 4 of the present invention.

[0029] FIG4 is a block diagram showing a user equipment UE according to the present invention. DETAILED DESCRIPTION

[0030] The following describes some of the terms involved in the present invention. For specific meanings, please refer to the latest relevant 3GPP documents, such as TS38.300, TS38.321, TS38.323, and TS38.331. Furthermore, the embodiments of the present invention are described using broadcast / multicast services as an example. However, the embodiments of the present invention are not limited to broadcast / multicast services and can also be applied to other application scenarios.

[0031] UE: User Equipment.

[0032] RRC: Radio Resource Control.

[0033] RRC_CONNECTED: RRC connected state.

[0034] RRC_INACTIVE: RRC inactive state.

[0035] RRC_IDLE: RRC idle state.

[0036] RAN: Radio Access Network.

[0037] NR: New RAT, new radio access technology.

[0038] MBS: Multicast / Broadcast Services. Multicast can also be called multicast.

[0039] AS: Access Stratum, access layer or access layer.

[0040] NAS: Non Access Stratum, non-access layer or non-access layer.

[0041] RB: Radio Bearer. DRB is a data radio bearer.

[0042] MBS Radio Bearer (MRB): A radio bearer configured for MBS delivery. MRBs are classified into multicast MRBs and broadcast MRBs. A multicast MRB is a radio bearer configured for MBS multicast transmission, while a broadcast MRB is a radio bearer configured for MBS broadcast transmission.

[0043] TMGI: Temporary Mobile Group Identity, used to identify an MBS session.

[0044] RNTI: Radio Network Temporary Identifier, wireless network temporary identifier.

[0045] PTM (Point to Multipoint) is a method for delivering MBS services. In PTM, the gNB delivers a single copy of MBS data packets to a group of UEs. UEs use a G-RNTI or G-CS-RNTI to receive PTM transmissions. For example, the gNB uses the G-RNTI-based group-common physical downlink control channel (PDCCH) to schedule the same G-RNTI-based group-common physical downlink shared channel (PDSCH).

[0046] PCell: Primary Cell, MCG cell, operates on the primary frequency, in which the UE performs the initial connection establishment process or initiates the connection re-establishment process.

[0047] G-RNTI: Group RNTI, group RNTI, used to scramble the scheduling and transmission of PTM for one or more MBS multicast services.

[0048] G-CS-RNTI: Group configuration scheduling RNTI, used to scramble the semi-static scheduling SPS group common physical downlink shared channel PDSCH of one or more MBS multicast services and activate / deactivate the SPS group common PDSCH.

[0049] MTCH: MBS Traffic Channel, MBS traffic channel, is a PTM downlink channel used to transmit MBS data of a multicast session or broadcast session from the network to the UE. Unless otherwise specified, the MTCH involved in the embodiments of the present disclosure refers to the multicast MTCH used to transmit MBS multicast sessions.

[0050] MCCH: MBS Control Channel. A PTM downlink channel used for transmitting MBS broadcast or MBS multicast control information associated with one or several MTCH(s) from the network to the UE. MCCHs include broadcast MCCHs and multicast MCCHs. Unless otherwise specified, all MCCHs referred to in the present disclosure refer to multicast MCCHs.

[0051] RLC: Radio Link Control. An RLC entity can be configured in one of three modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). The corresponding RLC entities are referred to as TM RLC entities, UM RLC entities, and AM RLC entities. Typically, an AM RLC entity or UM RLC entity is associated or configured for a multicast MRB, or a UM RLC entity is associated or configured for a multicast MRB receiving an RRC_INACTIVE MBS multicast session.

[0052] The RRC recovery request message RRCResumeRequest or RRCResumeRequest1 is used to request the resumption of a suspended RRC connection or to perform a RAN-based notification area RNA update. When the UE initiates an RRC connection recovery request, if the SIB1 received from the resident cell or the serving cell or the cell performing the RRC recovery process contains the useFullResumeID field, the RRCResumeRequest1 message is used and the resumeIdentity field in the RRCResumeRequest1 message is set to the fullI-RNTI stored by the UE, otherwise RRCResumeRequest is used and the resumeIdentity field in the RRCResumeRequest message is set to the stored shortI-RNTI. The RRC release message RRCRelease is used to command the release of an RRC connection or the suspension of an RRC connection. The RRC reconfiguration message RRCReconfiguration is used to command the modification of the RRC connection. The RRC establishment message RRCSetup is used to establish an SRBI. SRB1 is used for RRC messages (the RRC messages may include piggybacked NAS messages) and NAS messages before establishing SRB2, all of which use the dedicated control channel DCCH logical channel. The RRC recovery message RRCResume is used to resume the suspended RRC connection. In the present disclosure, the useFullResumeID field indicates the recovery identifier and recovery request message used. When the field is included in SIB1, the fullI-RNTI and RRCResumeRequest1 message are used. When the field is not included in SIB1, the shortI-RNTI and RRCResumeRequest message are used. The shortI-RNTI uses fewer bits than the I-RNTI-Value (i.e., the fullI-RNTI) to identify the suspended UE context of the UE in the RRC inactive state. The RRC recovery process (i.e., the RRC connection recovery process) is used to recover a suspended RRC connection, including recovering SRB(s), DRB(s), and multicast MRB(s), or performing RNA updates, or implementing MBS multicast reception requests, or initiating small data transmission (SDT) in the RRC_INACTIVE state. During the RRC recovery process, the UE sends an RRC recovery request message to the base station and may receive an RRC recovery message (RRCResume), an RRC setup message (RRCSetup), an RRC release message (RRCRelease), or an RRC rejection message (RRCReject) from the base station.

[0053] In the present invention, network, base station and RAN 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.

[0054] Currently, NR MBS services include MBS broadcast (also known as MBS broadcast session, broadcast MBS, MBS broadcast service, or MBS broadcast service) and MBS multicast (also known as MBS multicast session, multicast MBS, MBS multicast service, or MBS multicast service). MBS broadcast provides a downlink-only MBS transmission mode for services with low quality of service (QoS), allowing UEs in RRC connected, RRC idle, and RRC inactive states to receive the MBS service. UEs obtain MBS broadcast configuration information broadcast by the network through the MBS control channel (MCCH).

[0055] Release 17 does not support UEs receiving MBS multicast sessions in the RRC inactive state. Therefore, before receiving MBS multicast services (i.e., MBS multicast sessions), the UE needs to establish an RRC connection with the base station. The base station (i.e., the network) then configures the resources or PTM configuration for the UE to receive MBS multicast services through dedicated RRC signaling (also known as RRC messages, such as RRC reconfiguration messages). The MBS radio bearer (MRB) for receiving these MBS multicast services is also configured for the UE by the base station through dedicated RRC signaling. Only UEs in the RRC connected state and configured with MRBs can receive the corresponding MBS multicast services. Therefore, when an MBS multicast session is activated by the core network or the base station has MBS multicast session data to send, the network that supports MBS multicast notifies UEs in the RRC idle state or RRC inactive state through a group notification mechanism. Upon receiving the group notification, UEs that have joined the MBS multicast session or are interested in the MBS multicast session establish or resume an RRC connection with the network to receive the corresponding MBS multicast session. The group notification is addressed using the P-RNTI on the Physical Downlink Control Channel (PDCCH), and the UE monitors the paging channel. The paging message used for group notification contains the MBS session identifier (TMGI), which is used to page all UEs that have joined the relevant MBS multicast session and are in RRC Idle or RRC Inactive state. In other words, the base station does not page UEs individually (for the purpose of UEs receiving the MBS multicast session).

[0056] Release 18 supports UEs receiving MBS multicast sessions in an RRC inactive state. For MBS multicast sessions configured for RRC inactive reception, the base station can provide or configure PTM configuration information (also known as MBS multicast session configuration information or MBS multicast session PTM configuration or MBS multicast configuration) for the UE to receive the MBS multicast session through dedicated RRC signaling (e.g., RRCRelease message) or through the multicast MBS control channel MCCH (i.e., multicast MCCH). The information required to obtain the multicast MCCH (or multicast MCCH configuration) can be configured for the UE through dedicated RRC signaling or system information block (denoted as SIB24), that is, SIB24 contains the information required to obtain the multicast MCCH / MTCH (i.e., MCCH and / or MTCH) configuration for MBS multicast reception in the RRC inactive state. The PTM configuration information may include configuration information of the MRB corresponding to the MBS multicast session and / or the identifier TMGI of the MBS multicast session and its corresponding G-RNTI / G-CS-RNTI and / or fields of DRX configuration information. For example, the PTM configuration of a certain MBS multicast session is information related to the reception of the MBS multicast session contained in the MBS multicast configuration MBSMulticastConfiguration message. The MBSMulticastConfiguration message contains the control information applicable for MBS multicast services transmitted via multicast MRBs for RRC_INACTIVE UEs. The MBSMulticastConfiguration message may be transmitted on the multicast MCCH or included in the RRC release message. The multicast MCCH is a PTM downlink channel used for transmitting control information of MBS multicast session associated to one or several MTCH(s) from the network to the UE in RRC_INACTIVE state.For an MBS multicast session received in the RRC_INACTIVE state, in the embodiment of the present disclosure, the MBS multicast session being in an active state or being activated means that the MBS multicast session is in progress or is about to start, the UE starts to receive (or is receiving) the MBS multicast session, or the UE starts to detect the G-RNTI corresponding to the MBS multicast session, or the UE starts to detect (monitor) the multicast MCCH-RNTI of the multicast MCCH. The network can instruct the UE that the MBS multicast is activated or data transmission is resumed through RRC signaling (such as an RRC release message) or through a paging message. For example, including the TMGI of the MBS multicast session in the paging message indicates that the MBS multicast session is activated or data transmission is resumed, and not including the stopMonitoringRNTI field of the MBS multicast session in the RRC release message indicates that the MBS multicast session is activated or data transmission is resumed, wherein the stopMonitoringRNTI field is used to instruct the UE to stop detecting the G-RNTI of the corresponding multicast session. After receiving the MBS multicast activation or data transmission resumption indication, the UE starts receiving the MBS multicast session (i.e., the UE starts detecting the G-RNTI corresponding to the MBS multicast session). The MBS multicast activation described in the embodiment of the present disclosure is also applicable to the case of resuming data transmission of the MBS multicast session, which will not be described in detail below. In the embodiment of the present disclosure, the MBS multicast session being in an inactive state or being deactivated means that the MBS multicast session has ended or suspended data transmission or the UE stops receiving the MBS multicast session (i.e., the UE stops detecting the G-RNTI corresponding to the MBS multicast session). The network associates a stopMonitoringRNTI field for each MBS multicast session in the multicast MCCH message to explicitly instruct the UE to stop detecting the G-RNTI corresponding to the MBS multicast session (i.e., indicating that the MBS multicast session is deactivated or data transmission is stopped). The UE stops receiving the MBS multicast session after receiving the indication. The UE stopping receiving the MBS multicast session may be that the UE stops detecting the G-RNTI or G-CS-RNTI corresponding to the MBS multicast session. Therefore, in the present disclosure, the indication of deactivating the MBS multicast session or stopping data transmission is an indication instructing the UE to stop detecting the G-RNTI or G-CS-RNTI associated with the MBS multicast session. Furthermore, the indication of activating the MBS multicast session or resuming data transmission is an indication to start detecting the G-RNTI corresponding to the MBS multicast session. Deactivating an MBS multicast session includes situations where the MBS multicast session is temporarily not transmitting data, and activating an MBS multicast session includes situations where the MBS multicast session resumes data transmission. In the present disclosure, a multicast session or service is an MBS multicast session or service.The following embodiments are described using G-RNTI as an example. Embodiments obtained by replacing G-RNTI with G-CS-RNTI are also within the scope of this disclosure.

[0057] Each MBS multicast session is identified by a TMGI and associated with a G-RNTI or G-CS-RNTI. The UE receives the MBS multicast session by detecting the G-RNTI or G-CS-RNTI associated with the MBS multicast session.

[0058] For a UE configured with an MBS multicast session that can be received in the RRC_INACTIVE state, when the MBS multicast session is activated or data transmission is resumed, if the MBS multicast session is configured and / or allowed to be received in the RRC_INACTIVE state and / or the UE has a (valid) PTM configuration for the MBS multicast session, the MBS multicast session can be directly received without establishing an RRC connection with the base station. The network can configure the PTM configuration information (for example, contained in an MBSMulticastConfiguration message) for the MBS multicast session received in the RRC_INACTIVE state for the UE via the multicast MCCH and / or dedicated RRC signaling (for example, an RRC release message, an RRC reconfiguration message). The MBS multicast configuration message MBSMulticastConfiguration can be transmitted on the multicast MCCH (in this case, the MBSMulticastConfiguration message can be called a multicast MCCH message) or included in an RRC release message. If the RRC release message is used to configure the PTM configuration information of the MBS multicast session received in the RRC_INACTIVE state for the UE, the network may include the MBSMulticastConfiguration message in the RRC release message sent to the UE.

[0059] In the disclosed embodiments, a multicast MCCH-RNTI (i.e., Multicast MCCH-RNTI) is used for dynamically scheduled multicast MCCH signaling and / or multicast MCCH change notification, or for dynamically scheduled MCCH signaling and / or MCCH change notification, or for scrambling a DCI or a CRC of a DCI format, or for scrambling a PDCCH for MBS multicast transmission, or for scrambling a DCI or a CRC of a DCI format for MBS multicast transmission, or for scheduling a PDSCH for transmission of an MBS multicast session. The DCI or DCI format may be DCI format 4_0 or DCI format 4_1.

[0060] When a UE in RRC_INACTIVE mode receives a paging message from a base station, if the paging message contains the TMGI of one or more MBS sessions to which the UE has joined (the TMGI is contained in the pagingGroupList field in the paging message), and further, if the following conditions are met (the order of execution of the following conditions may be interchanged):

[0061] (1) The UE is not configured to receive MBS multicast in RRC_INACTIVE (i.e., the most recently received RRC release message does not contain the multicastConfigInactive field), or there is at least one MBS multicast session to which the UE has joined, indicated by the TMGI contained in the paging message, that is not configured to be received in RRC_INACTIVE, or there is at least one MBS multicast session to which the UE has joined, indicated by the TMGI contained in the paging message, that is not indicated by the paging message as being received in RRC_INACTIVE (i.e., the paging message does not contain the inactiveReceptionAllowed field corresponding to at least one MBS session to which the UE has joined, indicated by the TMGI contained in the paging message);

[0062] (2) The paging message does not contain the PagingRecordList field or the ue-Identity contained in any pagingRecord in the PagingRecordList field contained in the paging message does not match the UE identity allocated by the upper layer and the fullI-RNTI stored in the UE;

[0063] The RRC connection recovery process is started.

[0064] In the embodiment of the present disclosure, the PagingRecordList domain is a pagingRecord list, and the pagingRecord domain includes the ue-Identity domain, the ue-Identity domain is used to indicate the ng-5G-S-TMSI or fullI-RNTI of the UE being paged, and the fullI_RNTI domain carries the suspended UE context allocated to the UE by the base station through the RRC release message for identifying the UE in RRC_INACTIVE, and the ng-5G-S-TMSI includes a 5G temporary mobile subscription identifier 5G-S-TMSI, which is a temporary UE identifier provided by 5GC and is used to uniquely identify a UE in a tracking area.

[0065] The UE receives an RRC release message from a base station, and the RRC release message includes a multicastConfigInactive field, which indicates that the UE can receive multicast sessions or services in the current serving cell (i.e., the cell receiving the RRC release message) when the UE is in RRC_INACTIVE. When the multicastConfigInactive field is included in the received RRC release message, it indicates that the UE has been configured to receive MBS multicast in RRC_INACTIVE.

[0066] In the present disclosure, embodiments in which the function of the multicastConfigInactive field is replaced by one of the following are also within the scope of the present disclosure:

[0067] The multicastConfigInactive field indicates the multicast session or service that the UE can receive in the current serving cell when it is in RRC_INACTIVE, or the multicastConfigInactive field is used to indicate the multicast session or service that the UE can receive when it is in RRC_INACTIVE, or the multicastConfigInactive field is used to indicate the multicast session or service that the UE can receive when the current serving cell is in RRC_INACTIVE before obtaining the multicast MCCH, or the multicastConfigInactive field is used to indicate the multicast session or service that the UE can receive when it is in RRC_INACTIVE before obtaining the multicast MCCH, or the multicastConfigInactive field is used to indicate the multicast session or service that the UE can receive in the serving cell when it is in RRC_INACTIVE, and the serving cell is the cell that receives the multicast session or service when it is RRC_CONNECTED.

[0068] Optionally, the multicastConfigInactive field also includes the corresponding configurations for these multicast sessions. The multicastConfigInactive field may include two fields: the inactivePTM-Config field and the inactiveMCCH-Config field. The inactivePTM-Config field indicates the PTM configuration for receiving MBS multicast in the serving cell in RRC_INACTIVE mode and carries the MBSMulticastConfiguration message. The inactiveMCCH-Config field carries system information SIB24.

[0069] For a UE configured to receive an MBS multicast session in RRC_INACTIVE, the UE receives a paging message to learn whether the MBS multicast session it has joined is activated and allowed to be received in the RRC_INACTIVE state. Specifically, if the paging message includes the TMGI of the MBS multicast session the UE has joined (in which case the UE considers the MBS multicast session to be activated) and its corresponding inactiveReceptionAllowed field, and / or the paging message includes that the MBS multicast session the UE has joined is configured to be received in RRC_INACTIVE, then the UE considers that the MBS multicast session is activated and allowed to be received in RRC_INACTIVE, or the UE can receive the MBS multicast session in RRC_INACTIVE, or the UE starts to detect the G-RNTI of the MBS multicast session in RRC_INACTIVE. It should be noted that whether the UE receives the MBS multicast session in RRC_INACTIVE also depends on whether, when the UE receives the paging message, all other MBS multicast sessions to which the UE has joined and indicated in the paging message are indicated as being receivable in RRC_INACTIVE. If, among the MBS multicast sessions to which the UE has joined and indicated by the TMGI contained in the paging message, there is at least one that is not indicated by the paging message as being receivable in RRC_INACTIVE (i.e., the paging message does not include the inactiveReceptionAllowed field corresponding to at least one MBS session indicated by the TMGI contained in the paging message to which the UE has joined), then for other MBS multicast sessions to which the UE has joined and indicated by the TMGI contained in the paging message, the UE will not receive the MBS session in RRC_INACTIVE either. In other words, the UE receives the MBS multicast session that the UE has joined indicated by the TMGI contained in the paging message in RRC_INACTIVE only if the inactiveReceptionAllowed fields corresponding to all MBS multicast sessions that the UE has joined indicated by the TMGI contained in the paging message are contained in the paging message and / or the MBS multicast session indicated by the TMGI is configured to be received in RRC_INACTIVE. The inactiveReceptionAllowed field is used to indicate whether a UE with a valid PTM configuration for the TMGI indicated in the pagingGroupList (i.e., pagingGroupList-r17) contained in the paging message stays in RRC_INACTIVE to receive the MBS multicast session indicated by the TMGI.

[0070] Currently, the UE can be instructed to start detecting the G-RNTI of the MBS multicast session by including the TMGI of the MBS multicast session in the paging message (that is, if the paging message received by the UE contains a TMGI of the MBS multicast session allowed / configured for reception in RRC_INACTIVE, it indicates that the UE has received an instruction to start detecting the G-RNTI of the MBS multicast session). Alternatively, whether to stop detecting the G-RNTI corresponding to the MBS multicast session can be indicated in the MBSMulticastConfiguration message. Specifically, for an MBS multicast session whose TMGI is included in the MBSMulticastConfiguration message, if the MBSMulticastConfiguration message also includes a stopMonitoringRNTI field for the MBS multicast session, this indicates that the UE has received an instruction to stop detecting the G-RNTI for the MBS multicast session (i.e., to stop detecting the G-RNTI for the MBS multicast session). Otherwise (i.e., the MBSMulticastConfiguration message does not include a stopMonitoringRNTI field for the MBS multicast session), this indicates that the UE has not received an instruction to stop detecting the G-RNTI for the MBS multicast session. The stopMonitoringRNTI field instructs the UE to stop detecting the G-RNTI for the corresponding MBS multicast session. Stopping detection of the G-RNTI for the MBS multicast session is indicated by associating / configuring a stopMonitoringRNTI field for each MBS multicast session. If an MBS multicast session is not associated / configured with a corresponding stopMonitoringRNTI field, this indicates that the MBS multicast session has not been instructed to stop detecting the G-RNTI. The MBSMulticastConfiguration message may be transmitted on the multicast MCCH, or may be included in an RRC release message for transmission. Specifically, the MBSMulticastConfiguration message may be included in the MulticastConfigInactive field in the suspendConfig field in the RRC release message.The suspendConfig field indicates the configuration of the RRC_INACTIVE state; the MulticastConfigInactive field is used to indicate one or more MBS multicast services that can be received in RRC_INACTIVE (or one or more MBS multicast services that can be received in RRC_INACTIVE for the current serving cell or one or more MBS multicast services that can be received in RRC_INACTIVE for the current serving cell before acquiring the multicast MCCH). Optionally, it also includes the configuration of the MBS multicast service (or the configuration of the MBS multicast service for the current serving cell or the configuration of the MBS multicast service that is valid for the current serving cell). The current serving cell refers to the cell in which the UE receives the RRC release message or the cell in which the UE receives the MBS multicast session when it is RRC_CONNECTED. The serving cell or the cell in which the UE last or previously received the RRC release message may refer to the cell in which the UE last or previously received the RRC release message or the primary cell PCell or the cell in which the UE receives the MBS multicast session when it is RRC_CONNECTED. If the RRC release message received by the UE contains the MBSMulticastConfiguration message or the MulticastConfigInactive field, the UE is considered to be configured to receive MBS multicast or multicast session in RRC_INACTIVE mode; or if the RRC release message received by the UE (or the MBSMulticastConfiguration message contained in the RRC release message) contains the TMGI, the UE is considered to be configured to receive MBS multicast in RRC_INACTIVE mode. It should be noted that the UE obtaining the multicast MCCH means that the UE obtains the MBSMulticastConfiguration message from the multicast MCCH.

[0071] When a UE receives an RRC release message from a base station, if the RRC release message configures the UE to receive an MBS multicast session in RRC_INACTIVE and the RRC release message does not include a PTM configuration for the multicast session that is not indicated to stop detecting G-RNTI, the UE obtains an MBSMulticastConfiguration message on the multicast MCCH. In other words, the UE obtains an MBSMulticastConfiguration message on the multicast MCCH starting from the next repetition period on the cell of interest. However, it is currently unclear how to determine whether the RRC release message includes a PTM configuration for the multicast session that is not indicated to stop detecting G-RNTI. Therefore, how the UE determines whether to obtain the MBSMulticastConfiguration message from the multicast MCCH when receiving an RRC release message or a paging message is a problem that needs to be solved, and how the UE determines whether to start the RRC connection recovery process when performing cell selection or reselection is also a problem that needs to be solved.

[0072] In response to the above-mentioned problems in the prior art, the present disclosure proposes the following embodiments, but the following embodiments are only for illustration and are not intended to limit the scope of protection of the present invention.

[0073] Example 1

[0074] Embodiment 1 of the present disclosure is described in detail below with reference to the accompanying drawings. FIG1 is a schematic diagram illustrating the basic process of a method performed by a user equipment UE in embodiment 1 of the present disclosure. As shown in FIG1 , the method performed by the user equipment in embodiment 1 may generally include the following steps:

[0075] Step 101: The UE receives a radio resource control RRC message from a base station, where the RRC message may be an RRC release message.

[0076] Step 103: If the UE is configured by the RRC message to receive the MBS multicast session in RRC_INACTIVE but the RRC message does not include at least one multicast MRB (or the configuration of the multicast MRB or the mrb-ListMulticast field) for the MBS multicast session that is not indicated to stop detecting the G-RNTI, then obtain the MBS multicast configuration (MBSMulticastConfiguration) message from the multicast MCCH or obtain the MBSMulticastConfiguration message in the next repetition period of the multicast MCCH of the cell of interest.

[0077] In the embodiment of the present disclosure, the cell of interest may be the cell in which the UE receives the RRC release message, or the cell in which the UE receives the MBS multicast session when in RRC_CONNECTED mode, or the PCell of the UE when in RRC_CONNECTED mode, or the cell selected by the UE when receiving the RRC release message, or the UE's current serving cell, or the cell in which the UE is currently camped, or the cell in which the UE receives a paging message. In different embodiments, the cell of interest may refer to different cells.

[0078] [Variation of Example 1]

[0079] Keeping other steps in Example 1 unchanged, replacing step 103 with one of the following steps 103a, 103b, 103c, 103d, 103e, and 103f to obtain the following embodiment:

[0080] Step 103a: If the UE is configured by the RRC message to receive the MBS multicast session in RRC_INACTIVE but the RRC message does not contain at least one multicast MRB (or configuration of a multicast MRB) for the MBS multicast session that is not instructed to stop detecting the G-RNTI and the UE is not configured with the MRB for the MBS multicast session in the RRC connected state (that is, the MRB for the MBS multicast session is not established or does not exist when the UE receives the RRC release message), then obtain the MBSMulticastConfiguration message from the multicast MCCH or obtain the MBSMulticastConfiguration message in the next repetition period of the multicast MCCH of the cell of interest.

[0081] Step 103b: If the UE is configured by the RRC message to receive the MBS multicast session in RRC_INACTIVE but the RRC message does not contain at least one multicast MRB (or configuration of a multicast MRB) for the MBS multicast session that is not instructed to stop detecting G-RNTI and the MRB for the MBS multicast session does not exist or is not configured (or an MRB that is not suspended) when the UE receives the RRC message, then the MBSMulticastConfiguration message is obtained from the multicast MCCH or the MBSMulticastConfiguration message is obtained in the next repetition period of the multicast MCCH of the cell of interest.

[0082] Step 103c: If the UE is configured by the RRC message to receive the MBS multicast session in RRC_INACTIVE but there is no multicast MRB (or a multicast MRB that is not suspended) for the MBS multicast session that is not instructed to stop detecting G-RNTI in the UE, then obtain the MBSMulticastConfiguration message from the multicast MCCH or obtain the MBSMulticastConfiguration message in the next repetition period of the multicast MCCH of the cell of interest.

[0083] Step 103d: If the UE is configured by the RRC message to receive the MBS multicast session in RRC_INACTIVE but the RRC message does not include the mbs-SessionInfoListMulticast field, then obtain the MBSMulticastConfiguration message from the multicast MCCH or obtain the MBSMulticastConfiguration message in the next repetition period of the multicast MCCH of the cell of interest. It can be specified that for the TMGI included in the mbs-SessionInfoListMulticast field (the TMGI is carried by the mbs-SessionId field), the base station must configure its corresponding mrb-ListMulticast field.

[0084] Step 103e: If the UE is configured by the RRC message to receive the MBS multicast session in RRC_INACTIVE but the RRC message does not include the inactivePTM-Config field, then the UE obtains the MBSMulticastConfiguration message from the multicast MCCH or obtains the MBSMulticastConfiguration message in the next repetition period of the multicast MCCH of the cell of interest. It can be stipulated that when the RRC message includes the inactivePTM-Config field, the inactivePTM-Config field must include the mbs-SessionInfoListMulticast field, and for the TMGI included in the mbs-SessionInfoListMulticast field (the TMGI is carried by the mbs-SessionId field), the base station must configure its corresponding mrb-ListMulticast field.

[0085] Step 103f: If the multicastConfigInactive field included in the RRC release message is set to "setup", and the RRC release message includes a multicast MRB (multicast MRB configuration) for the MBS multicast session that is not instructed to stop detecting G-RNTI, and the UE selects the same cell as the cell that received the multicast session (or received the RRC release message) when RRC_CONNECTED, then the multicast MRB configuration is applied. Optionally, if the cell selected by the UE supports multicast MCCH (or multicast MCCH is present), then the multicast MCCH-RNTI is detected.

[0086] In the embodiment of the present disclosure, the mbs-SessionInfoListMulticast field provides the configuration of MBS multicast session(s) in the current cell, or provides the MRB of the MBS multicast session in the current cell, or provides the PTM configuration of the MBS multicast session in the current cell. The mbs-SessionId field indicates the MBS session identifier received by the UE in RRC_INACTIVE.

[0087] In addition, the MBS multicast session (if any) that is not instructed to stop detecting G-RNTI in steps 103, 103a-103f can be replaced by an MBS multicast session that the UE has joined and is not instructed to stop detecting G-RNTI, or replaced by an MBS multicast session that is configured for RRC_INACTIVE reception of the RRC message and is not instructed to stop detecting G-RNTI, or replaced by an MBS multicast session that is configured for RRC_INACTIVE reception and is not instructed to stop detecting G-RNTI. In steps 103, 103a-103f, the multicast MRB (if any) can be replaced by a bearer that receives the multicast session or an mrb-ListMulticast field. The mrb-ListMulticast field is a list of multicast MRBs to which the associated MBS multicast session is mapped.

[0088] Example 2

[0089] Embodiment 2 of the present disclosure is described in detail below with reference to the accompanying drawings. FIG2 is a schematic diagram illustrating the basic process of a method performed by a user equipment UE in embodiment 2 of the present disclosure. As shown in FIG2 , the method performed by the user equipment in embodiment 2 may generally include the following steps:

[0090] Step 201: A UE receives a paging message from a base station, where the paging message is used to notify one or more UEs.

[0091] Step 203: If the UE is in RRC_INACTIVE and the UE has joined one or more MBS sessions indicated by the TMGI(s) (i.e., one or more TMGIs) included in the pagingGroupList field in one or more of the paging messages, the following operations are performed:

[0092] Operation 2-1: If condition A1 or A2 is met, and further, if at least one of the following conditions B1-B5 is also met, the RRC connection recovery process is started.

[0093] Condition A1: The paging message does not include the PagingRecordList field.

[0094] The ue-Identity contained in any pagingRecord in the PagingRecordList field of the paging message described in condition A2 does not match the UE identity assigned by the upper layer and the fullI-RNTI stored by the UE

[0095] Condition B1: The UE is not configured to receive MBS multicast in RRC_INACTIVE (ie, the RRC release message received most recently does not include the multicastConfigInactive field).

[0096] Condition B2: There is at least one MBS multicast session that the UE has joined and that is indicated by the TMGI and is not configured for RRC_INACTIVE reception.

[0097] Condition B3: There is at least one MBS multicast session that the UE has joined and that is indicated by the TMGI included in the paging message and is not configured for reception in RRC_INACTIVE.

[0098] Condition B4: There is at least one MBS multicast session that the UE has joined indicated by the TMGI but is not indicated by the paging message as being receivable in RRC_INACTIVE (i.e., the paging message does not include an inactiveReceptionAllowed field corresponding to at least one MBS multicast session that the UE has joined indicated by the TMGI).

[0099] Condition B5: There is at least one MBS multicast session that the UE has joined and that is indicated by the TMGI included in the paging message but is not indicated by the paging message as being receivable in RRC_INACTIVE.

[0100] Operation 2-2: If the UE does not meet the conditions of operation 2-1 (i.e., the conditions for initiating the RRC connection recovery procedure in operation 2-1 are not met), and the following conditions are not met: the UE was notified to stop monitoring the G-RNTI(s) for all the joined multicast sessions that are configured for reception in RRC_INACTIVE), and the following conditions are met: there is at least one MBS multicast session that is notified to stop monitoring the G-RNTI(s), whose multicast MRB (or multicast MRB configuration) is not included in the RRC release message (i.e., the most recently received RRC release message or the RRC release message received before receiving the paging message), or whose multicast MRB or multicast MRB configuration is not included in a dedicated RRC message, then

[0101] The MBSMulticastConfiguration message is obtained from the multicast MCCH or in the next repetition period of the multicast MCCH of the concerned cell.

[0102] It should be noted that in operation 2-1, embodiments obtained by removing some of the conditions B1-B5 are also within the scope of this disclosure. In addition, in the embodiments of this disclosure, embodiments obtained by exchanging the execution order of some conditions are also within the scope of this disclosure.

[0103] In the embodiment of the present disclosure, the multicastConfigInactive field included in the RRC release message means that the multicastConfigInactive field is set to "setup".

[0104] [Variation of Example 2]

[0105] The embodiment obtained by replacing operation 2-1 in embodiment 2 with operation 2-1a is as follows:

[0106] Operation 2-1a: If conditions A1, A2, or A3 are met, and further, if at least one of the following conditions B1-B5 is met, the RRC connection recovery process is started.

[0107] Condition A3: There is a pagingRecord in the PagingRecordList field contained in the paging message, and the ue-Identity contained in it matches the fullI-RNTI stored in the UE, and the mt-SDT field is contained in the paging message.

[0108] The mt-SDT field is a small data transmission indication (Mobile Terminated SDT indication) for the mobile terminal. The network includes the mt-SDT field in the paging message only when the paging message includes the UE's I-RNTI.

[0109] In addition, in condition A3, the mt-SDT field being included in the paging message may be replaced by one of the following: the mt-SDT field for the UE being included in the paging message, the mt-SDT being included in the paging message and the conditions for initiating SDT for a resume procedure initiated in response to RAN paging are fulfilled, or the mt-SDT for the UE being included in the paging message and the conditions for initiating SDT for a resume procedure initiated in response to RAN paging are fulfilled.

[0110] In the embodiment of the present disclosure, the TMGI included in the paging message refers to the TMGI included in the pagingGroupList-r17 field included in the paging message. When the TMGI is included in the pagingGroupList-r17 field, it means that the MBS multicast session indicated by the TMGI is activated or data transmission starts. The inactiveReceptionAllowed field is included in the pagingGroupList-v18xy field in the paging message, where x and y can be any natural numbers, for example, xy is "00". pagingGroupList-v18xy has the same number and order of elements as pagingGroupList-r17. The first element in pagingGroupList-v18xy corresponds to the first TMGI in pagingGroupList-r17, the second element in pagingGroupList-v18xy corresponds to the second TMGI in pagingGroupList-r17, and so on. The inactiveReceptionAllowed field is used to indicate whether a UE with a valid PTM configuration for the TMGI indicated in the pagingGroupList (ie, pagingGroupList-r17) should stay in RRC_INACTIVE to receive the MBS multicast session indicated by the TMGI.

[0111] In addition, in embodiment 2 and its variations, the UE may receive an RRC release message before receiving the paging message.

[0112] Example 3

[0113] A UE in RRC_INACTIVE mode, configured for RRC_INACTIVE reception of MBS multicast, initiates an RRC connection recovery procedure if, after performing cell selection or reselection, it cannot obtain a multicast MRB (or multicast MRB configuration or mrb-ListMulticast field) in the selected or reselected cell for an MBS multicast session to which the UE has joined and to which it has not been instructed to stop detecting G-RNTI. Optionally, the MBS multicast session is an MBS multicast session configured for RRC_INACTIVE reception.

[0114] Currently, when a UE receives an RRC release message from a base station, if the message contains the MulticastConfigInactive field but does not contain the mbs-SessionInfoListMulticast field, how the UE should operate is a problem that needs to be solved. To address the problems in the prior art, the present disclosure proposes the following embodiments, but the following embodiments are only for illustration and do not limit the scope of protection of the present invention.

[0115] Example 4

[0116] Embodiment 4 of the present disclosure is described in detail below with reference to the accompanying drawings. FIG3 is a schematic diagram illustrating the basic process of a method executed by a user equipment UE in embodiment 4 of the present disclosure. As shown in FIG3 , the method executed by the user equipment in embodiment 4 may generally include the following steps:

[0117] In step 301, the UE receives an RRC release message from a base station.

[0118] In step 303, if the UE is configured to receive the MBS multicast session in RRC_INACTIVE (i.e., the received RRC release message contains the MulticastConfigInactive field), but the RRC release message does not contain the mbs-SessionInfoListMulticast field, the UE considers that all joined multicast sessions (or all MBS multicast sessions received in RRC_CONNECTED or all configured MBS multicast sessions) are configured to be received in RRC_INACTIVE (or can all be received in RRC_INACTIVE).

[0119] Optionally, for all joined MBS multicast sessions (or all MBS multicast sessions received in RRC_CONNECTED or all configured MBS multicast sessions), the UE considers that the stopMonitoringRNTI field of the MBS multicast session has been received.

[0120] Optionally, for all joined MBS multicast sessions (or all MBS multicast sessions received in RRC_CONNECTED or all configured MBS multicast sessions), the UE considers that the stopMonitoringRNTI field of the MBS multicast session has not been received.

[0121] Since the mbs-SessionInfoListMulticast field is included in the inactivePTM-Config field, the RRC release message in step 303 does not include the mbs-SessionInfoListMulticast field, which includes two situations: one is that the RRC release message includes the inactivePTM-Config field, but the inactivePTM-Config field does not include the mbs-SessionInfoListMulticast field; the other is that the RRC release message does not include the inactivePTM-Config field.

[0122] In addition, the base station configures the UE to receive the MBS multicast session in RRC_INACTIVE mode using an RRC release message. However, upon receiving the RRC release message, how the UE performs configuration based on the received RRC release message remains a challenge. To address these issues in the prior art, the present disclosure proposes the following embodiments. However, these embodiments are intended for illustrative purposes only and are not intended to limit the scope of protection of the present invention.

[0123] Example 5: Full Configuration

[0124] The UE receives an RRC release message from the base station. If the RRC release message contains the MulticastConfigInactive field, the UE performs full configuration or performs full configuration for the MBS multicast session or performs full configuration for the MBS multicast session configured for RRC_INACTIVE reception according to the configuration information carried in the MulticastConfigInactive field in the RRC release message. During the full configuration process for an MBS multicast session, the UE releases the MRB and other related configuration information of the MBS multicast session and / or applies the configuration information carried in the MulticastConfigInactive field in the RRC release message.

[0125] Example 6: Delta Configuration

[0126] The UE receives an RRC release message from the base station. If the RRC release message contains a MulticastConfigInactive field, the UE performs incremental configuration based on the configuration information carried in the MulticastConfigInactive field in the RRC release message, or performs incremental configuration for the MBS multicast session, or performs incremental configuration for the MBS multicast session configured for RRC_INACTIVE reception. During the incremental configuration process, for an already configured MBS multicast session, the UE modifies the existing configuration based on the configuration information carried in the MulticastConfigInactive field in the received RRC release message.

[0127] The current multicast MCCH acquisition procedure stipulates that the multicast MCCH information acquired from the multicast MCCH information acquisition procedure overwrites any stored multicast MCCH information, i.e., the incremental configuration is not applicable for multicast MCCH information and the UE discontinues using a filed if it is absent in the multicast MCCH information. In existing protocols, multicast MCCH information refers to information transmitted in messages sent over the multicast MCCH. However, for a UE in RRC_INACTIVE mode, the configuration information for MBS multicast configured for RRC_INACTIVE reception may come from dedicated RRC signaling or the multicast MCCH.

[0128] When the UE is in RRC_INACTIVE, if the multicast MCCH information acquired from the multicast MCCH information acquisition process only covers the stored multicast MCCH information, how to process the configuration information of the MBS multicast session configured through dedicated RRC signaling is a problem that needs to be solved.

[0129] In response to the above-mentioned problems in the prior art, the present disclosure proposes the following embodiments, but the following embodiments are only for illustration and are not intended to limit the scope of protection of the present invention.

[0130] Example 7

[0131] In step 601, the UE obtains multicast MCCH information from the multicast MCCH using a multicast MCCH information acquisition process;

[0132] In step 603, the multicast MCCH information obtained from the multicast MCCH information acquisition process overwrites any stored multicast MCCH information and the configuration of the MBS multicast session configured (or obtained) through dedicated RRC signaling, that is, the incremental configuration is not applied to the multicast MCCH information and the UE does not continue to use the absent field in the multicast MCCH information. The configuration of the MBS multicast session configured (or obtained) through dedicated RRC signaling includes at least one of the following: the configuration of the MBS multicast session configured when the UE is RRC_CONNECTED (that is, the configuration of the MBS multicast session provided to the UE by the base station through an RRC reconfiguration message, an RRC resume message, or an RRC establishment message), and the configuration of the MBS multicast session obtained by the UE from an RRC release message (that is, the configuration of the MBS multicast session provided to the UE by the base station through an RRC release message when the UE is released from RRC_CONNECTED to RRC_INACTIVE). The configuration of the MBS multicast session configured when the UE is in RRC_CONNECTED may be further limited to the configuration of the MBS multicast session for RRC_INACTIVE reception configured when the UE is in RRC_CONNECTED.

[0133] In the present disclosure, MBS multicast or multicast session or service is an MBS multicast session or service.

[0134] Unless otherwise specified, the embodiments executed by the UE or base station in the present disclosure may be executed by the RRC entity in the UE or base station or executed at the RRC layer. In the present disclosure, fields, domains, and information elements may be used interchangeably. In the embodiments of the present disclosure, if multiple operations are included, the embodiments obtained by changing the execution order of the operations are also within the scope of protection of the present disclosure. When multiple parallel judgment conditions are included, the embodiments obtained by changing the order of the judgment conditions are also within the scope of protection of the present disclosure. The conditions involved in the embodiments of the present disclosure are used interchangeably with "and", "or", "and / or", "and", and "and", and the resulting embodiments are also within the scope of the present disclosure.

[0135] 4 is used to illustrate a user equipment as an embodiment that can execute the method executed by the user equipment described in detail above in the present invention.

[0136] FIG4 is a block diagram showing a user equipment UE according to the present invention.

[0137] As shown in Figure 4, the user equipment UE 400 includes a processor 401 and a memory 402. The processor 401 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 402 may include, for example, a volatile memory (such as a random access memory (RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory. The memory 402 stores program instructions. When executed by the processor 401, the instructions may execute the above-described method performed by the user equipment as described in detail in the present invention.

[0138] The method and user equipment executed by the user equipment involved in the present invention have been described in detail above based on Example 1, etc. However, the present invention is not limited to the method and user equipment executed by the user equipment, and can also be implemented in other ways as long as the main purpose of the present invention can be achieved.

[0139] The method and related apparatus of the present disclosure have been described above in conjunction with preferred embodiments. Those skilled in the art will appreciate that the methods described above are merely exemplary and that the various embodiments described above can be combined with one another unless conflicts arise. The method of the present disclosure is not limited to the steps and sequence described above.

[0140] In the embodiments of the present disclosure, when multiple operations are involved, the embodiments of the present disclosure exemplarily list the execution order of each operation, and the embodiments obtained by changing the execution order of each operation are also within the scope of protection of the present disclosure. In addition, when multiple judgment conditions are involved, the embodiments obtained by changing the execution order of each judgment condition are also within the scope of protection of the present disclosure. In addition, in the present disclosure, unless otherwise specified, the meaning of the domain defined in one embodiment can also be applied to the corresponding domain involved in other embodiments. In addition, in the embodiments of the present disclosure, "if...", "when...", "when...", "at...", "satisfy..." or "satisfy..." conditions" can be replaced with "under the condition of...". In the embodiments of the present disclosure, the embodiments obtained by replacing "and", "and", and "and" in some or all conditions with "or" are also within the scope of protection of the present disclosure; the embodiments obtained by replacing "or" in some or all conditions with "and" are also within the scope of protection of the present disclosure.

[0141] In addition, the user equipment shown above may include more modules, for example, modules that can be developed or will be developed in the future and can be used for a base station, MME, or UE, etc. The various identifiers shown above are merely exemplary and not restrictive, and the present disclosure is not limited to the specific information elements used as examples of these identifiers. Those skilled in the art may make many changes and modifications based on the teachings of the illustrated embodiments.

[0142] It should be understood that the above embodiments of the present disclosure can be implemented through software, hardware, or a combination of software and hardware. For example, the various components within the base station and user equipment in the above embodiments can be implemented through a variety of devices, including but not limited to: analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, programmable processors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), programmable logic devices (CPLDs), and the like.

[0143] In addition, the computer executable instructions or programs running on the device according to the present invention can be programs that enable the computer to implement the functions of the embodiments of the present invention by controlling the central processing unit (CPU). The program or the information processed by the program can be temporarily stored in a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory systems.

[0144] The computer executable instructions or program for realizing each embodiment of the present invention function can be recorded on a computer-readable storage medium. The corresponding function can be realized by making a computer system read the program recorded on the recording medium and executing these programs. The so-called "computer system" herein can be a computer system embedded in the device, and can include an operating system or hardware (such as a peripheral device). "Computer-readable storage medium" can be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a short-term dynamic storage program recording medium or any other recording medium that is computer-readable.

[0145] The various features or functional modules of the devices used in the above embodiments can be implemented or executed by circuits (e.g., single-chip or multi-chip integrated circuits). The circuits designed to perform the functions described in this specification may include general-purpose processors, digital signal processors (DSPs), proprietary integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above devices. The general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine. The above circuits may be digital circuits or analog circuits. In the event that new integrated circuit technologies have emerged to replace existing integrated circuits due to advances in semiconductor technology, one or more embodiments of the present invention may also be implemented using these new integrated circuit technologies.

[0146] Furthermore, the present invention is not limited to the above-described embodiments. Although various examples of the embodiments have been described, the present invention is not limited thereto. Fixed or non-mobile electronic devices installed indoors or outdoors can be used as terminal devices or communication devices, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

[0147] As described above, the embodiments of the present invention have been described in detail with reference to the accompanying drawings. However, the specific structure is not limited to the above-described embodiments, and the present invention also includes any design changes that do not deviate from the main purpose of the present invention. In addition, various modifications can be made to the present invention within the scope of the claims, and embodiments obtained by appropriately combining the technical means invented by different embodiments are also included in the technical scope of the present invention. In addition, components with the same effect described in the above embodiments can be replaced with each other.

Claims

1. A method performed by a user equipment (UE), comprising: The UE receives a radio resource control RRC release message RRCRelease from the base station; When the UE is configured by the RRCRelease message to receive the MBS multicast session in RRC_INACTIVE and the RRCRelease message does not include at least one mrb-ListMulticast of the MBS multicast session that is not indicated to stop detecting the G-RNTI, obtaining the MBS multicast configuration message from the multicast MCCH; The RRCRelease message is used to command the release of an RRC connection or the suspension of an RRC connection, the mrb-ListMulticast field is the multicast MRB list to which the associated multicast MBS session is mapped, and the MBS multicast configuration message includes control information applied to the RRC_INACTIVE UE receiving the MBS multicast service through the multicast MRB.

2. A user equipment (UE), comprising a processor, wherein the processor is configured to: Receive a radio resource control RRC release message RRCRelease from the base station; When the UE is configured by the RRCRelease message to receive the MBS multicast session in RRC_INACTIVE and the RRCRelease message does not include at least one mrb-ListMulticast of the MBS multicast session that is not indicated to stop detecting the G-RNTI, obtaining the MBS multicast configuration message from the multicast MCCH; in, The RRCRelease message is used to command the release of an RRC connection or the suspension of an RRC connection. The mrb-ListMulticast field is the multicast MRB list to which the associated multicast MBS session is mapped. The MBS multicast configuration message contains control information applied to the RRC_INACTIVE UE receiving the MBS multicast service through the multicast MRB.

Images