User equipment, base station and method thereof

Abstract

According to the present invention, a user equipment, a base station and a method thereof are provided. The method executed by user equipment UE comprises the following steps: receiving an RRC release message; and under the condition that the received RRC release message carries the first information used for indicating the configuration in the RRC inactive state, releasing the configuration information of all the configured MBS multicast sessions received in the RRC inactive state.

Description

Technical Field

[0001] The present invention relates to the field of wireless communication technology, and more particularly, to user equipment, a base station and a method thereof. Background Art

[0002] A research project SI (see SP-190625 for details) on the improvement of the 5G multicast broadcast service architecture has been approved. One of the goals of this SI (called Goal A) is to support universal MBS services in 5GS. Use cases that can benefit from this feature include (but are not limited to) public safety, V2X applications, transparent IPv4 / IPv6 multicast transmission, IPTV, wireless software transmission, group communication 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 literature: RP-193248: New WID: NR Multicast and Broadcast Service). This work item aims to provide support for Goal A in RAN. The goals of this work item have been basically achieved, and the specific description of the relevant solutions can be found in 3GPP Release 17 technical documents, such as TS38.300-h30, TS38.331-h30, TS38.321-h30, etc. At the 3GPP RAN#94 plenary meeting, a work item named Enhanced NR Broadcast Multicast was approved (see non-patent document: RP-213568: New WID: Enhancements of NR Multicast and Broadcast Services). This work item aims to further enhance the MBS broadcast multicast of Release 17, one of its goals is to support user equipment to receive MBS multicast services / sessions in the RRC inactive state.

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

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

[0005] In order to achieve the above-mentioned purpose, 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 the configuration in the RRC inactive state, releasing the configuration information of all configured MBS multicast sessions received in the RRC inactive state.

[0006] 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 and / or second information for indicating a configuration of MBS multicast reception in an RRC inactive state, reconfiguring configuration information of an MBS multicast session received in an RRC inactive state according to the second information.

[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 in a case where the received RRC release message carries first information for indicating a configuration in an RRC non-activated state, second information for indicating a configuration of MBS multicast reception in an RRC non-activated state, and / or third information for indicating whether the UE releases or reconfigures the configuration information of the MBS multicast session currently configured for reception in an RRC non-activated state, performing at least one of the following operations: reconfiguring the configuration information of the MBS multicast session received in an RRC non-activated state according to the second information; and releasing the currently configured MBS multicast session received in an RRC non-activated state and configuring the MBS multicast session received in an RRC non-activated 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 releasing the configuration information of the currently configured MBS multicast session received in the RRC inactive state when the received RRC release message carries first information indicating the configuration in the RRC inactive state, second information indicating the configuration of the 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 received in the RRC inactive state.

[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 replacing a currently retained MBS multicast session reference configuration with the MBS multicast session reference configuration in the received RRC release message, when the received RRC release message carries first information indicating a configuration in an RRC inactive state, second information indicating a configuration for MBS multicast reception in an RRC inactive state, and / or an MBS multicast session reference configuration.

[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 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 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 whether to replace a currently retained MBS multicast session reference configuration with the MBS configuration carried in the second information according to the fifth information.

[0011] Preferably, the MBS multicast session reference configuration is a 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.

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

[0013] 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 comprises: sending an RRC release message, wherein the RRC release message comprises at least one of the following information: first information for indicating a configuration in an RRC non-activated state; second information for indicating a configuration of MBS multicast reception in an RRC non-activated state; third information for indicating whether the UE releases or reconfigures the configuration information of the MBS multicast session currently configured for reception in an RRC non-activated state; fourth information for indicating whether the UE releases or retains the configuration information of the MBS multicast session currently configured for reception in an RRC non-activated 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.

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

[0015] Effects of the Invention

[0016] 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 state reception. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0018] Figure 1 is a flowchart showing a method executed by a user equipment according to embodiment 1 of the present invention.

[0019] Figure 2 is a flowchart showing a method executed by a user equipment according to embodiment 2 of the present invention.

[0020] Figure 3 is a flowchart showing a method executed by a user equipment according to embodiment 3 of the present invention.

[0021] Figure 4 is a flowchart showing a method executed by a user equipment according to embodiment 4 of the present invention.

[0022] Figure 5 is a flowchart showing a method executed by a user equipment according to embodiment 5 of the present invention.

[0023] Figure 6 is a flowchart showing a method executed by a user equipment according to embodiment 6 of the present invention.

[0024] Figure 7 is a block diagram schematically showing a user equipment involved in the present invention.

[0025] Figure 8 is a block diagram schematically showing a base station involved in the present invention. DETAILED DESCRIPTION

[0026] The present invention is described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be noted that the present invention should not be 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.

[0027] The following describes some terms involved in the present invention. For specific meanings of the terms, refer to the latest relevant 3GPP documents, such as TS38.300-h30, TS38.321-h30, TS38.323-h30, TS38.331-h30, etc. In addition, the embodiments of the present invention are described by taking broadcast / multicast services as an example, but the embodiments of the present invention are not limited to broadcast / multicast services and can also be applied to other application scenarios.

[0028] UE: User Equipment.

[0029] RRC: Radio Resource Control.

[0030] RRC_CONNECTED: RRC connected state.

[0031] RRC_INACTIVE: RRC inactive state.

[0032] RRC IDLE: RRC idle state.

[0033] RAN: Radio Access Network.

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

[0035] MBS: Multicast / Broadcast Services. Multicast can also be called groupcast.

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

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

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

[0039] MRB: MBS radio bearer, i.e. a radio bearer that is configured for MBS delivery. MRB is divided into multicast MRB and broadcast MRB. Multicast MRB is a radio bearer configured for MBS multicast transmission, while broadcast MRB is a radio bearer configured for MBS broadcast transmission.

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

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

[0042] PTM: Point to Multipoint, a delivery method for MBS services. In the PTM delivery method, the base station sends a single copy of MBS data packets to a set of UEs (gNB delivers a single copy of MB Sdata packets to a set of UEs). UE uses G-RNTI or G-CS-RNTI to receive PTM transmissions. For example, the base station uses the group common physical downlink control channel PDCCH using G-RNTI to schedule the same group common physical downlink shared channel PDSCH using G-RNTI.

[0043] PTP: Point to Point, a delivery method for MBS services. In the PTP delivery method, the RAN node delivers separate copies of multiple MBS data packets to each UE individually (gNB individually deliversseparate copies of MB S data packets to each UEs independently). For example, the base station schedules the UE-specific PDCCH scrambled by the UE-specific RNTI and the UE-specific PDSCH scrambled by the same UE-specific RNTI.

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

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

[0046] The RRC recovery request message RRCResumeRequest or RRCResumeRequestl is used to request the recovery 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 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 to suspend 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 recover a suspended RRC connection. In the present disclosure, the useFullResumeID field indicates the resume identifier and resume request message used. When the field is included in SIB1, fullI-RNTI and RRCResumeRequestl message are used. When the field is not included in SIB1, shortI-RNTI and RRCResumeRequest message are used. ShortI-RNTI uses fewer bits than I-RNTI-Value to identify the suspended UE context of a UE in an RRC inactive state.

[0047] In the present invention, network, base station and RAN can be used interchangeably, and 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.

[0048] At present, 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 version 17, the UE needs to establish an RRC connection with the base station before receiving the MBS multicast service (i.e., MBS multicast session), and then the base station configures the 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 configured with MRB can receive the corresponding MBS multicast service.

[0049] In version 17, it is not supported for UE 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 supporting MBS multicast notifies the UE in RRC idle state or RRC inactive state through a group notification mechanism. Upon receiving the group notification, the UE that has joined or is interested in the MBS multicast session establishes or restores an RRC connection with the network to receive the corresponding MBS multicast session. The group notification is addressed with 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 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).

[0050] In version 18, UE is supported to receive MBS multicast sessions in RRC inactive state. For MBS multicast sessions received in RRC inactive state, the base station can provide or configure PTM configuration information (also called configuration information of MBS multicast session or PTM configuration of MBS multicast session) for UE to receive the MBS multicast session through dedicated RRC signaling (e.g., RRCRelease message) or through multicast MBS control channel MCCH (i.e., multicast MCCH). The information required to obtain multicast MCCH (or multicast MCCH configuration) can be configured for 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 MBS multicast received in 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 sessions associated to one or several MTCH(s)from the network to the UE inRRC_INACTIVE state.

[0051] 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 MACentity′s G-RNTI(s)and G-CS-RNTI(s) respectively.

[0052] Version 18 supports UEs in an 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 an 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 an 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 a PTM configuration or MRB) for an MBS multicast session that is configured for reception in the RRC_INACTIVE state. 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.

[0053] In order to solve at least part of the above problems, the present disclosure provides corresponding embodiments. Specific embodiments are listed below to illustrate the processing method of the present invention. In addition, the embodiments listed below are only examples and are not intended to limit the present invention.

[0054] Example 1

[0055] Figure 1 is a flowchart showing a method executed by a user equipment according to embodiment 1 of the present invention.

[0056] like Figure 1 As shown, in step 101, the UE receives an RRC release message from a base station.

[0057] 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, the configuration information of all configured MBS multicast sessions received in the RRC inactive state is released.

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

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

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

[0061] 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, the radio link control (Radio Link Comrol, RLC) entity, and the MAC and physical layer configurations corresponding to the MRB, and / or if the service data adaptation protocol (Service Data Adaptation Protocol, SDAP) entity associated with the mbs-SessionId corresponding to the MRB has no other associated MRBs (or further restricting the MRB without other associations to mean that there are 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.

[0062] In the disclosed embodiment, 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).

[0063] Example 2

[0064] Figure 2 is a flowchart showing a method executed by a user equipment according to embodiment 2 of the present invention.

[0065] like Figure 2 As shown, in step 201, the UE receives an RRC release message from a base station.

[0066] In step 203, when an RRC release message is received from a base station, if the RRC release message carries a suspendConfig field for indicating a configuration in an RRC inactive state and / or a field (referred to as a multicastConfigInactive field) for indicating a configuration of 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 an RRC inactive state is reconfigured according to the received multicastConfigInactive field. The multicastConfigInactive field may be used to indicate a configuration of receiving MBS multicast in an RRC inactive state of a current serving cell (i.e., a cell receiving an RRC release message), and the multicastConfigInactive field may include an inactivePTM-Config field for indicating a PTM configuration of MBS multicast reception in an RRC inactive state of the current serving cell and / or a multicastMCCH-Config field for indicating an MCCH configuration of MBS multicast reception in an RRC inactive state of the current serving cell.

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

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

[0069] 2-a: If the multicastConfigInactive field also contains 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 the multicast MRB needs to be changed, the mrb-IdentityNew is used to indicate the new identifier of the multicast MRB. The mrb-Identity change may occur when the mrb-Identity of the MRB of the MBS multicast session configured for RRC inactive reception needs to be changed.

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

[0071] 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 configurable PDCP parameters for 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.

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

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

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

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

[0076] 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 (RadioLink Control, RLC) entity and / or its corresponding MAC layer and physical layer configuration corresponding to the MRB.

[0077] Example 3

[0078] Figure 3 is a flowchart showing a method executed by a user equipment according to embodiment 3 of the present invention.

[0079] like Figure 3 As shown, in step 301, the UE receives an RRC release message from a base station.

[0080] In step 303, when an RRC release message is received from a 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 of MBS multicast reception in an RRC inactive state and / or a field for indicating whether the UE releases or reconfigures the configuration information of the currently configured MBS multicast session received in an RRC inactive state, the configuration of the MBS multicast session received in an RRC inactive state is reconfigured according to the received multicastConfigInactive field, or the currently configured MBS multicast session received in an RRC inactive state is released and the MBS multicast session received in an RRC inactive state is configured according to the received multicastConfigInactive field.

[0081] 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 of MBS multicast reception in an RRC inactive state, then:

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

[0083] Otherwise (the RRC release message does not contain 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).

[0084] [Variation of Embodiment 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 contain 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 contains 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.

[0085] Example 4

[0086] Figure 4 is a flowchart showing a method executed by a user equipment according to embodiment 4 of the present invention.

[0087] like Figure 4As shown, in step 401, the UE receives an RRC release message from a base station.

[0088] In step 403, 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 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 received in the RRC inactive state, the UE releases the configuration information of the currently configured MBS multicast session received in the RRC inactive state.

[0089] 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 of 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 received in an RRC inactive state, the UE releases the configuration information of the currently configured MBS multicast session received in an RRC inactive state.

[0090] [Variation of Example 4] If the RRC release message carries the suspendConfig field for indicating the configuration in the RRC inactive state and / or the 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 MBS multicast session currently configured for RRC inactive state reception, the UE releases the configuration information of the MBS multicast session currently configured for RRC inactive state reception.

[0091] Example 5

[0092] Figure 5 is a flowchart showing a method executed by a user equipment according to embodiment 5 of the present invention.

[0093] like Figure 5 As shown, in step 501, the UE receives an RRC release message from a base station.

[0094] In step 503, 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 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).

[0095] 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 of 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:

[0096] 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 received MBS multicast session reference configuration is directly saved).

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

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

[0099] Example 6

[0100] Figure 6 is a flowchart showing a method executed by a user equipment according to embodiment 6 of the present invention.

[0101] like Figure 6 As shown, in step 601, the UE receives an RRC release message from a base station.

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

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

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

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

[0106] [Variation of Embodiment 6]

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

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

[0109] In the disclosed embodiment, 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, that is, the UE applies the received MBS multicast session configuration information to the MBS multicast session reference configuration to obtain the MBS multicast session configuration.

[0110] [Modifications]

[0111] Next, use Figure 7 A user equipment as a variation example that can execute the method executed by the user equipment described in detail above of the present invention is described.

[0112] Figure 7 It is a block diagram showing a user equipment UE involved in the present invention.

[0113] like Figure 7 As shown, 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 memories, etc. Program instructions are stored on the memory 702. When the instructions are executed by the processor 701, the above method performed by the user equipment described in detail in the present invention may be executed.

[0114] Next, use Figure 8 A base station that can execute the method executed by the base station described above of the present invention is described as a variation example.

[0115] Figure 8 It is a block diagram showing a base station involved in the present invention.

[0116] like Figure 8 As shown, the base station 80 includes a processor 801 and a memory 802. The processor 801 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The 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 memories, etc. The memory 802 stores program instructions. When the instructions are executed by the processor 801, the above method performed by the base station described in detail in the present invention may be executed.

[0117] Specifically, the base station according to the present invention communicates with the user equipment UE. The base station sends an RRC release message to the UE, and the RRC release message includes at least one of the following information: first information for indicating the configuration in the RRC inactive state; second information for indicating the configuration of the MBS multicast reception in the 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; MBS multicast session reference configuration; and fifth information for indicating whether the MBS configuration carried in the second information is used as the reference configuration of the MBS multicast session. For details, please refer to the above description.

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

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

[0120] The computer executable instructions or programs for realizing the functions of various embodiments of the present invention can be recorded on a computer readable storage medium. The corresponding functions can be realized by making a computer system read the programs 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 recording medium of a short-term dynamic storage program, or any other recording medium readable by a computer.

[0121] 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). Circuits designed to perform the functions described in this specification may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above 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 case where 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.

[0122] In addition, the present invention is not limited to the above-mentioned 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.

[0123] As mentioned 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 embodiments, and the present invention also includes any design changes that do not deviate from the main purpose of the present invention. In addition, the present invention can be modified in various ways within the scope of the claims, and the 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, the components with the same effect described in the above embodiments can be replaced by 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 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 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, the configuration information of the currently configured MBS multicast session received in the 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