User equipment, base station, and method

Abstract

According to the present invention, provided are a user equipment, a base station, and a method. A method, which is executed by a user equipment (UE), comprises: receiving an RRC release message; and when the received RRC release message carries first information used for indicating a configuration in an RRC inactive state, releasing configuration information of MBS multicast sessions received in all configured RRC inactive states.

Description

User equipment, base station and method thereof Technical Field

[0001] The present invention relates to the field of wireless communication technology, and more particularly, to a user equipment, a base station and a method thereof. 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-h30, TS 38.331-h30, and TS 38.321-h30. 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 related issues involved in RAN supporting user equipment to receive MBS multicast services / sessions in an RRC inactive state.

[0004] Summary of the Invention

[0005] In order to solve the above problem, the present invention provides a user equipment, a base station and a method thereof, which can effectively process the configuration information of the MBS multicast session configured for RRC_INACTIVE reception when the UE receives the RRC release message.

[0006] To achieve the above-mentioned objective, according to the present invention, a method performed by a user equipment (UE) is proposed, comprising: receiving an RRC release message; and releasing configuration information of all configured MBS multicast sessions received in the RRC inactive state when the received RRC release message carries first information indicating the configuration in the RRC inactive state.

[0007] In addition, according to the present invention, a method performed by a user equipment UE is proposed, comprising: receiving an RRC release message; and when the received RRC release message carries first information for indicating a configuration in an RRC inactive state and / or second information for indicating a configuration for MBS multicast reception in an RRC inactive state, reconfiguring configuration information of an MBS multicast session received in the RRC inactive state according to the second information.

[0008] In addition, according to the present invention, a method performed by a user equipment UE is proposed, comprising: receiving an RRC release message; and in a case where the received RRC release message carries first information for indicating a configuration in an RRC inactive state, second information for indicating a configuration for MBS multicast reception in an RRC inactive state, and / or third information for indicating whether the UE releases or reconfigures configuration information of a currently configured MBS multicast session received in an RRC inactive state, performing at least one of the following operations: reconfiguring the configuration information of the MBS multicast session received in the RRC inactive state according to the second information; and releasing the currently configured MBS multicast session received in the RRC inactive state and configuring the MBS multicast session received in the RRC inactive state according to the second information.

[0009] In addition, according to the present invention, a method performed by a user equipment UE is proposed, comprising: receiving an RRC release message; and releasing the configuration information of the currently configured MBS multicast session for RRC inactive state reception when the received RRC release message carries first information indicating the configuration in the RRC inactive state, second information indicating the configuration of MBS multicast reception in the RRC inactive state, and / or fourth information indicating whether the UE releases or retains the configuration information of the currently configured MBS multicast session for RRC inactive state reception.

[0010] In addition, according to the present invention, a method performed by a user equipment UE is proposed, comprising: receiving an RRC release message; and when the received RRC release message carries first information for indicating a configuration in an RRC inactive state, second information for indicating a configuration for MBS multicast reception in an RRC inactive state, and / or an MBS multicast session reference configuration, replacing a currently retained MBS multicast session reference configuration with the MBS multicast session reference configuration in the received RRC release message.

[0011] In addition, according to the present invention, a method performed by a user equipment UE is proposed, comprising: receiving an RRC release message; and in a case where the received RRC release message carries first information for indicating a configuration in an RRC inactive state, second information for indicating a configuration for MBS multicast reception in an RRC inactive state, and / or fifth information for indicating whether the MBS configuration carried in the second information is used as a reference configuration for an MBS multicast session, determining, according to the fifth information, whether to replace a currently retained MBS multicast session reference configuration with the MBS configuration carried in the second information.

[0012] Preferably, the MBS multicast session reference configuration is a configuration of an MBS multicast session configured by a base station for a UE, and is used by the UE to generate a complete configuration of the MBS multicast session.

[0013] In addition, according to the present invention, a user equipment is proposed, comprising: a processor; and a memory storing instructions, wherein the instructions execute the above method when executed by the processor.

[0014] In addition, according to the present invention, a method performed by a base station is proposed, wherein the base station communicates with a user equipment UE, and the method includes: sending an RRC release message, wherein the RRC release message includes at least one item of the following information: first information for indicating a configuration in an RRC inactive state; second information for indicating a configuration of MBS multicast reception in an RRC inactive state; third information for indicating whether the UE releases or reconfigures the configuration information of the currently configured MBS multicast session received in the RRC inactive state; fourth information for indicating whether the UE releases or retains the configuration information of the currently configured MBS multicast session received in the RRC inactive state; an MBS multicast session reference configuration; and fifth information for indicating whether the MBS configuration carried in the second information is used as a reference configuration for the MBS multicast session.

[0015] In addition, according to the present invention, a base station is proposed, comprising: a processor; and a memory storing instructions, wherein the instructions execute the above method when executed by the processor.

[0016] Effects of the Invention

[0017] According to the present invention, when the UE receives the RRC release message, it can effectively process the configuration information of the MBS multicast session configured for RRC_INACTIVE reception. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] 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:

[0019] FIG1 is a flowchart illustrating a method executed by a user equipment according to embodiment 1 of the present invention.

[0020] FIG2 is a flowchart illustrating a method executed by a user equipment according to embodiment 2 of the present invention.

[0021] FIG3 is a flowchart illustrating a method executed by a user equipment according to embodiment 3 of the present invention.

[0022] FIG4 is a flowchart illustrating a method executed by a user equipment according to embodiment 4 of the present invention.

[0023] FIG5 is a flowchart illustrating a method executed by a user equipment according to embodiment 5 of the present invention.

[0024] FIG6 is a flowchart illustrating a method executed by a user equipment according to embodiment 6 of the present invention.

[0025] FIG7 is a block diagram schematically illustrating a user equipment involved in the present invention.

[0026] FIG8 is a block diagram schematically showing a base station involved in the present invention. DETAILED DESCRIPTION

[0027] The present invention is described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that the present invention is not limited to the specific embodiments described below. In addition, for the sake of simplicity, detailed descriptions of known technologies that are not directly related to the present invention are omitted to prevent confusion in understanding the present invention.

[0028] The following describes some of the terms involved in the present invention. For their specific meanings, please refer to the latest relevant 3GPP documents, such as TS38.300-h30, TS38.321-h30, TS38.323-h30, and TS38.331-h30. 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.

[0029] UE: User Equipment.

[0030] RRC: Radio Resource Control.

[0031] RRC_CONNECTED: RRC connected state.

[0032] RRC_INACTIVE: RRC inactive state.

[0033] RRC_IDLE: RRC idle state.

[0034] RAN: Radio Access Network.

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

[0036] MBS: Multicast / Broadcast Services. Multicast is also called multicast.

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

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

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

[0040] 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.

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

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

[0043] 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).

[0044] PTP: Point to Point, a delivery method for MBS services. In PTP, the gNB individually delivers separate copies of MBS data packets to each UE independently. For example, the base station schedules a UE-specific PDCCH scrambled with a UE-specific RNTI and a UE-specific PDSCH scrambled with the same UE-specific RNTI.

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

[0046] 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.

[0047] 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 resumption request, if the SIB1 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 recovery message RRCResume is used to resume a suspended RRC connection. In the present disclosure, the useFullResumeID field indicates the resume identifier and resume request message to be 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 to identify the suspended UE context of a UE in an RRC-inactive state.

[0048] 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.

[0049] Currently, NR MBS services include MBS broadcast (also known as MBS broadcast session or broadcast MBS or MBS broadcast service) and MBS multicast (also known as MBS multicast session or multicast MBS or MBS multicast service). MBS broadcast provides a downlink-only MBS transmission mode for services with low quality of service (QoS), so that UEs in RRC connected state, RRC idle state, and RRC inactive state can receive the MBS service. The UE obtains the MBS broadcast configuration information broadcast by the network through the MBS control channel MCCH. In 3GPP Release 17, before receiving the MBS multicast service (i.e., MBS multicast session), the UE needs to establish an RRC connection with the base station. The base station then configures resources for receiving the MBS multicast service for the UE through dedicated RRC signaling (also known as RRC message, such as RRC reconfiguration message). 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 with the MRB configured can receive the corresponding MBS multicast service.

[0050] In version 17, it is not supported for UEs to receive MBS multicast sessions in RRC inactive state. 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 the UEs in RRC idle state or RRC inactive state through a group notification mechanism. Upon receiving the group notification, the UEs that have joined 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 with P-RNTI on 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 state or RRC inactive state. In other words, the base station does not page the UE individually (for the purpose of the UE receiving the MBS multicast session).

[0051] Version 18 supports UEs receiving MBS multicast sessions in an RRC inactive state. For MBS multicast sessions received in an RRC inactive state, the base station can provide or configure the UE with PTM configuration information for receiving the MBS multicast session (also called MBS multicast session configuration information or MBS multicast session PTM configuration) 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 SIBx), that is, SIBx contains the information required to obtain the multicast MCCH configuration of the MBS multicast received in the RRC inactive state. The PTM configuration information may include the 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 DRX and other configuration information fields. 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.

[0052] Each MBS multicast session is identified by a TMGI and is associated with a G-RNTI or G-CS-RNTI. The UE receives the MBS multicast session by monitoring the G-RNTI or G-CS-RNTI associated with the MBS multicast session. For MBS multicast, the MAC entity may be configured by RRC with a DRX functionality per G-RNTI or per G-CS-RNTI that controls the UE's PDCCH monitoring activity for the MAC entity's G-RNTI(s)and G-CS-RNTI(s).

[0053] Version 18 supports UEs in RRC inactive state to receive MBS multicast sessions. The present disclosure considers how to handle the currently ongoing MBS multicast session and / or how to handle the MRB that has been configured for receiving MBS in RRC_INACTIVE when the UE receives an RRC release RRCRelease message. For example, when a UE in RRC inactive state receives a paging message from a base station instructing the UE to perform a mobile-terminated or user-oriented small data transmission SDT, the UE will initiate an RRC connection recovery process. During this process, the UE will remain in the RRC inactive state and receive data from the base station. When the SDT ends, the UE receives an RRC release message from the base station containing a suspendConfig field, and the suspendConfig field is used to indicate the configuration in the RRC inactive state. When the UE receives the RRC release message, the UE is receiving an MBS multicast session or there is configuration information (such as PTM configuration or MRB) for an MBS multicast session that is configured for RRC_INACTIVE state reception. At this time, how the UE processes the configuration information of the MBS multicast session configured for reception in the RRC_INACTIVE state is a problem that needs to be solved.

[0054] To address at least some of the above problems, the present disclosure provides corresponding embodiments. Specific embodiments are listed below to illustrate the processing method of the present invention. Furthermore, the embodiments listed below are merely illustrative and do not limit the present invention.

[0055] Example 1

[0056] FIG1 is a flowchart illustrating a method executed by a user equipment according to embodiment 1 of the present invention.

[0057] As shown in FIG1 , in step 101 , the UE receives an RRC release message from a base station.

[0058] In step 103, when an RRC release message is received from the base station, if the RRC release message carries a suspendConfig field for indicating the configuration in the RRC inactive state, all configured configuration information of the MBS multicast session received in the RRC inactive state is released.

[0059] Specifically, the UE receives an RRC release message from the base station. If the RRC release message carries a suspendConfig field for indicating a configuration in an RRC inactive state, the UE performs at least one of the following operations:

[0060] Operation 1-1: Reset the Media Access Control (MAC) entity.

[0061] Operation 1-2: For each MRB established for an MBS multicast session received in an RRC inactive state in the current UE configuration, release the Packet Data Convergence Protocol (PDCP) entity and mrb-Identity corresponding to the MRB, and / or if there is no other multicast MRB (configured for an MBS multicast session received in an RRC inactive state) configured with the same mbs-SessionId as the mbs-SessionId configured for the released multicast MRB (if there is no other multicast MRB configured with the same mbs-SessionId as configured for the released multicast MRB), indicate to the upper layer that the user plane resources of the mbs-SessionId have been released.

[0062] Operation 1-3: For each MRB established for an MBS multicast session received in an RRC inactive state in the current UE configuration, release the PDCP entity, radio link control (RLC) entity, and MAC and physical layer configurations corresponding to the MRB, and / or if the service data adaptation protocol (SDAP) entity associated with the mbs-SessionId corresponding to the MRB has no other associated MRBs (or further limit the MRB without other associations to mean no other associated MRBs configured for receiving MBS multicast sessions in an RRC inactive state), release the SDAP entity and / or indicate to the upper layer that the user plane resources of the mbs-SessionId have been released.

[0063] In the embodiment of the present disclosure, mrb-Identity is used to identify an MRB used by the UE, and mbs-SessionId is used to indicate a multicast MBS session associated with a bearer (MRB).

[0064] Example 2

[0065] FIG2 is a flowchart illustrating a method executed by a user equipment according to embodiment 2 of the present invention.

[0066] As shown in FIG2 , in step 201 , the UE receives an RRC release message from the base station.

[0067] In step 203, upon receiving an RRC release message from the base station, if the RRC release message carries a suspendConfig field for indicating a configuration in an RRC inactive state and / or a field (denoted as a multicastConfigInactive field) for indicating a configuration for MBS multicast reception (i.e., MBS multicast session reception) in an RRC inactive state, then the configuration information of the MBS multicast session received in the RRC inactive state is reconfigured based on the received multicastConfigInactive field. The multicastConfigInactive field may be used to indicate a configuration for MBS multicast reception in an RRC inactive state for the current serving cell (i.e., the cell receiving the RRC release message). The multicastConfigInactive field may include an inactivePTM-Config field for indicating a PTM configuration for MBS multicast reception in an RRC inactive state for the current serving cell and / or a multicastMCCH-Config field for indicating an MCCH configuration for MBS multicast reception in an RRC inactive state for the current serving cell.

[0068] Specifically, the UE receives an RRC release message from the base station. If the RRC release message carries a suspendConfig field for indicating a configuration in an RRC inactive state and / or a multicastConfigInactive field for indicating a configuration for MBS multicast reception in an RRC inactive state, the UE performs at least one of the following operations:

[0069] Operation 2-1: For each mrb-Identity contained in the multicastConfigInactive field and the mrb-Identity is part of the UE's current configuration, perform:

[0070] 2-a: If the multicastConfigInactive field also includes the mrb-IdentityNew corresponding to the mrb-Identity, the mrb-Identity is updated to the value indicated by the multicastConfigInactive. When the mrb-Identity of a multicast MRB needs to be changed, mrb-IdentityNew is used to indicate the new identifier of the multicast MRB. The mrb-Identity change may occur when the mrb-Identity of an MRB for an MBS multicast session configured for RRC inactive reception needs to be changed.

[0071] 2-b: If reestablishPDCP is set, execute at least one of 2-a, 2-b, and 2-c: if the pdcp-Config corresponding to the mrb-Identity carried in the multicastConfigInactive field includes drb-ContinueROHC, it indicates that the lower layer is configured with drb-ContinueROHC; if the pdcp-Config corresponding to the mrb-Identity carried in the multicastConfigInactive field includes drb-ContinueEHC-DL, it indicates that the lower layer is configured with drb-ContinueEHC-DL; rebuild the PDCP entity of the multicast MRB corresponding to the mrb-Identity.

[0072] Otherwise (i.e., reestablishPDCP is not set), if recoverPDCP is set, the PDCP entity of the multicast MRB corresponding to the mrb-Identity is triggered to perform data recovery. Among them, reestablishPDCP indicates that PDCP should be rebuilt, pdcp-Config is used to set the configurable PDCP parameters of SRB, MRB and DRB, drb-ContinueROHC is used to indicate whether the PDCP entity continues or resets the robust header compression ROHC header compression protocol when PDCP is rebuilt, drb-ContinueEHC-DL is used to indicate whether the PDCP entity continues or resets the downlink Ethernet header compression EHC header compression protocol when PDCP is rebuilt, and recoverPDCP indicates that PDCP performs recovery.

[0073] 2-c: If the multicastConfigInactive field carries the pdcp-Config corresponding to the mrb-Identity, reconfigure the corresponding PDCP entity according to the received pdcp-Config.

[0074] Operation 2-2: for each mrb-Identity contained in the multicastConfigInactive field and the mrb-Identity is not part of the UE's current configuration (i.e., establishing a multicast MRB), perform: establishing a PDCP entity and configuring the PDCP entity according to the received pdcp-Config; and / or associating the established multicast MRB (i.e., the MRB corresponding to the PDCP entity) to the corresponding mbs-SessionId (i.e., the mbs-SessionId corresponding to the mrb-Identity contained in the multicastConfigInactive field); and / or if the SDAP entity of the mbs-SessionId does not yet exist, then: establishing a corresponding SDAP entity, and / or if the SDAP entity of the mbs-SessionId does not exist before receiving this reconfiguration (i.e., before receiving the RRC release message), indicating to the upper layer (e.g., the NAS layer) that user plane resources have been established for the mbs-SessionId.

[0075] Operation 2-3: If the multicastConfigInactive field contains an mbs-NeighbourCellList indicating neighboring cells providing one or more MBS multicast services provided by the current cell, delete the mbs-NeighbourCellList stored locally on the UE and apply the received mbs-NeighbourCellList.

[0076] Operation 2-4: If the multicastConfigInactive field contains the DRX configuration of a certain MBS multicast session, release the current DRX configuration and / or apply the DRX configuration contained in the multicastConfigInactive field.

[0077] Operation 2-5: For each mrb-Identity contained in the multicastConfigInactive field and the mrb-Identity is indicated as released, release the PDCP entity, radio link control (RLC) entity and / or its corresponding MAC layer and physical layer configuration corresponding to the MRB.

[0078] Example 3

[0079] FIG3 is a flowchart illustrating a method executed by a user equipment according to embodiment 3 of the present invention.

[0080] As shown in FIG3 , in step 301 , the UE receives an RRC release message from the base station.

[0081] In step 303, when an RRC release message is received from the base station, if the RRC release message carries a suspendConfig field for indicating a configuration in an RRC inactive state and / or a multicastConfigInactive field for indicating a configuration for MBS multicast reception in an RRC inactive state and / or a field for indicating whether the UE releases or reconfigures configuration information of a currently configured MBS multicast session received in an RRC inactive state, the configuration of the MBS multicast session received in the RRC inactive state is reconfigured according to the received multicastConfigInactive field, or the currently configured MBS multicast session received in the RRC inactive state is released and the MBS multicast session received in the RRC inactive state is configured according to the received multicastConfigInactive field.

[0082] Specifically, if the RRC release message carries a suspendConfig field for indicating a configuration in an RRC inactive state and / or a multicastConfigInactive field for indicating a configuration for MBS multicast reception in an RRC inactive state, then:

[0083] If the RRC release message includes a field for instructing the UE to release the configuration information of the MBS multicast session currently configured for reception in the RRC inactive state, the MBS multicast session currently configured for reception in the RRC inactive state is released and / or the MBS multicast session received in the RRC inactive state is configured according to the received multicastConfigInactive field (for example, the MBS multicast session received in the RRC inactive state is configured in the manner described in Example 1).

[0084] Otherwise (the RRC release message does not include a field for instructing the UE to release the configuration information of the currently configured MBS multicast session received in the RRC inactive state), reconfigure the MBS multicast session received in the RRC inactive state according to the received multicastConfigInactive field (for example, reconfigure the MBS multicast session received in the RRC inactive state in the manner described in Example 2).

[0085] [Variation of Example 3] The field for instructing the UE to release the configuration information of the MBS multicast session currently configured for reception in the RRC inactive state may also be replaced by a field for instructing the UE not to release (or reconfigure) the configuration information of the MBS multicast session currently configured for reception in the RRC inactive state. Accordingly, when the RRC release message does not include the field for instructing the UE not to release (or reconfigure) the configuration information of the MBS multicast session currently configured for reception in the RRC inactive state, the currently configured MBS multicast session received in the RRC inactive state is released and the MBS multicast session received in the RRC inactive state is configured according to the received multicastConfigInactive field; when the RRC release message includes the field for instructing the UE not to release (or reconfigure) the configuration information of the MBS multicast session currently configured for reception in the RRC inactive state, the MBS multicast session received in the RRC inactive state is reconfigured according to the received multicastConfigInactive field.

[0086] Example 4

[0087] FIG4 is a flowchart illustrating a method executed by a user equipment according to embodiment 4 of the present invention.

[0088] As shown in FIG4 , in step 401 , the UE receives an RRC release message from the base station.

[0089] In step 403, upon receiving the RRC release message from the base station, if the RRC release message carries a suspendConfig field for indicating the configuration in the RRC inactive state and / or a multicastConfigInactive field for indicating the configuration of MBS multicast reception in the RRC inactive state and / or a field for indicating whether the UE releases or retains the configuration information of the currently configured MBS multicast session for RRC inactive state reception, the UE releases the configuration information of the currently configured MBS multicast session for RRC inactive state reception.

[0090] Specifically, the UE receives an RRC release message from the base station. If the RRC release message carries a suspendConfig field for indicating a configuration in an RRC inactive state and / or a multicastConfigInactive field for indicating a configuration for MBS multicast reception in an RRC inactive state and / or a field for instructing the UE to release configuration information of a currently configured MBS multicast session for RRC inactive reception, the UE releases the configuration information of the currently configured MBS multicast session for RRC inactive reception.

[0091] [Variation of Example 4] If the RRC release message carries a suspendConfig field for indicating the configuration in the RRC inactive state and / or a multicastConfigInactive field for indicating the configuration of MBS multicast reception in the RRC inactive state, and / or if the RRC release message does not include a field for instructing the UE to retain the configuration information of the currently configured MBS multicast session for RRC inactive state reception, the UE releases the configuration information of the currently configured MBS multicast session for RRC inactive state reception.

[0092] Example 5

[0093] FIG5 is a flowchart illustrating a method executed by a user equipment according to embodiment 5 of the present invention.

[0094] As shown in FIG5 , in step 501 , the UE receives an RRC release message from the base station.

[0095] In step 503, upon receiving the RRC release message from the base station, if the RRC release message carries a suspendConfig field for indicating the configuration in the RRC inactive state and / or a multicastConfigInactive field for indicating the configuration of MBS multicast reception in the RRC inactive state and / or an MBS multicast session reference configuration, the UE replaces the currently retained MBS multicast session reference configuration with the received MBS multicast session reference configuration (if there is no retained MBS multicast session reference configuration, the received MBS multicast session reference configuration is directly saved).

[0096] Specifically, the UE receives an RRC release message from the base station. If the RRC release message carries a suspendConfig field for indicating a configuration in an RRC inactive state and / or a multicastConfigInactive field for indicating a configuration for MBS multicast reception in an RRC inactive state and / or an MBS multicast session reference configuration, the UE performs at least one of the following operations:

[0097] Operation 5-a: The UE replaces the currently retained MBS multicast session reference configuration with the received MBS multicast session reference configuration (if there is no retained MBS multicast session reference configuration, the UE directly saves the received MBS multicast session reference configuration).

[0098] Operation 5-b: The UE applies the configuration information of the MBS multicast session included in the multicastConfigInactive field.

[0099] Operation 5-c: The UE applies the received MBS multicast session configuration information contained in the multicastConfigInactive field to the MBS multicast session reference configuration (thereby obtaining the MBS multicast session configuration).

[0100] Example 6

[0101] FIG6 is a flowchart illustrating a method executed by a user equipment according to embodiment 6 of the present invention.

[0102] As shown in FIG6 , in step 601 , the UE receives an RRC release message from the base station.

[0103] In step 603, upon receiving an RRC release message from the base station, if the RRC release message carries a suspendConfig field for indicating a configuration in an RRC inactive state and / or a multicastConfigInactive field for indicating a configuration for MBS multicast reception in an RRC inactive state and / or an indication of whether the MBS configuration carried in the multicastConfigInactive field is used as a reference configuration for the MBS multicast session, the UE determines whether to replace the currently retained MBS multicast session reference configuration with the MBS configuration carried in the multicastConfigInactive field according to whether the RRC release message contains the indication (if there is no retained MBS multicast session reference configuration, the MBS configuration carried in the multicastConfigInactive field is directly saved as the MBS multicast session reference configuration).

[0104] Specifically, the UE receives an RRC release message from the base station. If the RRC release message carries a suspendConfig field for indicating a configuration in an RRC inactive state and / or a multicastConfigInactive field for indicating a configuration for MBS multicast reception in an RRC inactive state, then:

[0105] If the RRC release message includes an indication identifier for indicating that the MBS configuration carried in the multicastConfigInactive field is used as the MBS multicast session reference configuration, the UE will replace the currently retained MBS multicast session reference configuration with the received MBS multicast session reference configuration (if there is no retained MBS multicast session reference configuration, the received MBS multicast session reference configuration will be directly saved).

[0106] Optionally, the UE applies the configuration information of the MBS multicast session contained in the multicastConfigInactive field.

[0107] [Variation of Example 6]

[0108] If the RRC release message does not include an indication identifier for indicating that the MBS configuration carried in the multicastConfigInactive field is not used as the MBS multicast session reference configuration, the UE will replace the currently retained MBS multicast session reference configuration with the received MBS multicast session reference configuration (if there is no retained MBS multicast session reference configuration, the received MBS multicast session reference configuration will be directly saved).

[0109] Optionally, the UE applies the configuration information of the MBS multicast session contained in the multicastConfigInactive field.

[0110] In the embodiment of the present disclosure, the MBS multicast session reference configuration is the configuration of the MBS multicast session configured by the base station for the UE, and is used by the UE to generate a complete configuration of the MBS multicast session, that is, the UE applies the received configuration information of the MBS multicast session to the MBS multicast session reference configuration to obtain the configuration of the MBS multicast session.

[0111] [Modification]

[0112] 7 is used to illustrate a user equipment as a modified example that can execute the method executed by the user equipment described in detail above in the present invention.

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

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

[0115] Next, FIG. 8 is used to illustrate a base station as a modified example that can execute the method executed by the base station described above in the present invention.

[0116] FIG8 is a block diagram showing a base station according to the present invention.

[0117] As shown in Figure 8 , the base station 80 includes a processor 801 and a memory 802. Processor 801 may include, for example, a microprocessor, a microcontroller, or an embedded processor. Memory 802 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. Memory 802 stores program instructions. When executed by processor 801, these instructions may execute the above-described method performed by the base station as described in detail in the present invention.

[0118] Specifically, a base station according to the present invention communicates with a user equipment (UE). The base station sends an RRC release message to the UE, the RRC release message including at least one of the following information: first information indicating a configuration in an RRC inactive state; second information indicating a configuration for MBS multicast reception in an RRC inactive state; third information indicating whether the UE should release or reconfigure the configuration information of the currently configured MBS multicast session for RRC inactive reception; fourth information indicating whether the UE should release or retain the configuration information of the currently configured MBS multicast session for RRC inactive reception; an MBS multicast session reference configuration; and fifth information indicating whether the MBS configuration carried in the second information should be used as the reference configuration for the MBS multicast session. For details, please refer to the above description.

[0119] In the embodiments of the present disclosure, when multiple operations are included, the embodiments of the present disclosure exemplarily list the execution order of each operation. 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 included, embodiments obtained by changing the execution order of the judgment conditions are also within the scope of protection of the present disclosure. In addition, in the present disclosure, unless otherwise specified, the meaning of a field defined in one embodiment may also apply to the corresponding fields involved in other embodiments.

[0120] 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.

[0121] 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.

[0122] 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 a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above 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.

[0123] 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.

[0124] 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: Receive an RRC release message; as well as In a case where the received RRC release message carries the first information indicating the configuration in the RRC inactive state, the configuration information of all configured MBS multicast sessions received in the RRC inactive state is released.

2. A method performed by a user equipment UE, comprising: Receive an RRC release message; as well as When the received RRC release message carries first information indicating configuration in the RRC inactive state and / or second information indicating configuration of MBS multicast reception in the RRC inactive state, configuration information of the MBS multicast session received in the RRC inactive state is reconfigured according to the second information.

3. A method performed by a user equipment UE, comprising: Receive an RRC release message; as well as In a case where the received RRC release message carries first information for indicating a configuration in an RRC inactive state, second information for indicating a configuration of MBS multicast reception in an RRC inactive state, and / or third information for indicating whether the UE releases or reconfigures configuration information of a currently configured MBS multicast session received in an RRC inactive state, performing at least one of the following operations: reconfiguring configuration information of the MBS multicast session received in the RRC inactive state according to the second information; and The currently configured MBS multicast session received in the RRC inactive state is released and the MBS multicast session received in the RRC inactive state is configured according to the second information.

4. A method performed by a user equipment UE, comprising: Receive an RRC release message; as well as The received RRC release message carries first information for indicating the configuration in the RRC inactive state, second information for indicating the configuration of MBS multicast reception in the RRC inactive state, and / or second information for indicating whether the UE releases or retains the currently configured RRC inactive state reception. In the case of the fourth information of the configuration information of the MBS multicast session received in the RRC inactive state, the configuration information of the MBS multicast session received in the currently configured RRC inactive state is released.

5. A method performed by a user equipment UE, comprising: Receive an RRC release message; as well as When the received RRC release message carries first information indicating the configuration in the RRC inactive state, second information indicating the configuration of MBS multicast reception in the RRC inactive state, and / or an MBS multicast session reference configuration, the currently retained MBS multicast session reference configuration is replaced with the MBS multicast session reference configuration in the received RRC release message.

6. A method performed by a user equipment UE, comprising: Receive an RRC release message; as well as When the received RRC release message carries first information for indicating the configuration in the RRC inactive state, second information for indicating the configuration of MBS multicast reception in the RRC inactive state, and / or fifth information for indicating whether the MBS configuration carried in the second information is used as the MBS multicast session reference configuration, it is determined according to the fifth information whether to replace the currently retained MBS multicast session reference configuration with the MBS configuration carried in the second information.

7. The method according to claim 5 or 6, wherein: The MBS multicast session reference configuration is the configuration of the MBS multicast session configured by the base station for the UE, and is used by the UE to generate a complete MBS multicast session configuration.

8. A user equipment, comprising: processor; as well as Memory, which stores instructions, Wherein, when the instructions are executed by the processor, the method according to any one of claims 1 to 7 is performed.

9. A method performed by a base station, the base station communicating with a user equipment UE, the method comprising: Send RRC release message, The RRC release message includes at least one of the following information: First information used to indicate the configuration in the RRC inactive state; Second information used to indicate configuration of MBS multicast reception in an RRC inactive state; third information used to instruct the UE whether to release or reconfigure the configuration information of the MBS multicast session currently configured for reception in the RRC inactive state; Fourth information used to indicate whether the UE releases or retains the configuration information of the currently configured MBS multicast session received in the RRC inactive state; MBS multicast session reference configuration; as well as Fifth information used to indicate whether the MBS configuration carried in the second information is used as a reference configuration for the MBS multicast session.

10. A base station, comprising: processor; as well as Memory, which stores instructions, Wherein, the instructions, when executed by the processor, perform the method according to claim 9.

Images