Method executed by user equipment and user equipment

By judging the paging message and PTM configuration in the user equipment, it is determined whether to receive the MBS multicast session in the RRC inactive state, which solves the problem of low efficiency in the RRC inactive state in the prior art, and reduces energy consumption and Inter-layer interaction improves service continuity.

CN118945601APending Publication Date: 2024-11-12SHARP KK
View PDF 0 Cites 0 Cited by

Patent Information

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

AI Technical Summary

Technical Problem

The existing 5G multicast broadcast service cannot effectively receive MBS multicast sessions in the RRC inactive state, resulting in user equipment requiring frequent start of RRC connection recovery process, increasing energy consumption and inter-layer interaction, affecting service continuity.

Method used

When the user equipment receives a paging message from the base station, it determines whether it is necessary to receive an MBS multicast session in the RRC inactive state. According to the instructions in the paging message and the PTM configuration, decide whether to start the RRC connection recovery process or continue to receive the session to avoid Unnecessary monitoring and energy consumption.

Benefits of technology

It reduces unnecessary energy consumption and inter-layer interaction of user equipment, and improves the MBS multicast session reception efficiency and service continuity in RRC inactive state.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945601A_ABST
    Figure CN118945601A_ABST
Patent Text Reader

Abstract

The invention provides a method executed by user equipment and the user equipment. A method performed by a user equipment (UE) comprises: a first step in which the UE receives a paging message from a base station; and a second step of, if the UE is in an RRC inactive state and the paging message does not trigger the UE to initiate an RRC connection recovery procedure, starting receiving the MBS multicast session in the RRC inactive state for each MBS multicast session in which the UE has joined and indicated in the paging message to be activated or resumed data transmission.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] A research project SI (see SP-190625 for details) on 5G multicast broadcast service architecture improvement 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. 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 method performed by a user equipment and the user equipment.

[0005] According to a first aspect of the present invention, a method performed by a user equipment UE is provided, comprising: a first step, the UE receiving a paging message from a base station; and a second step, if the UE is in an RRC inactive state and the paging message does not trigger the UE to start an RRC connection recovery process, then for each MBS multicast session that the UE has joined and is indicated in the paging message as being activated or resuming data transmission, starting to receive the MBS multicast session in the RRC inactive state.

[0006] In the method of the first aspect above, preferably, the TMGI of the MBS multicast session is forwarded to an upper layer.

[0007] In the method of the first aspect above, preferably, for each PagingRecord field contained in the paging message, if the ue-Identity contained in the PagingRecord field matches the fullI-RNTI stored in the UE, the RRC connection recovery process is started.

[0008] In the method of the first aspect above, preferably, if the UE is in an RRC inactive state and the paging message does not trigger the UE to start the RRC connection recovery process, then for each MBS multicast session that the UE has joined and is indicated in the paging message as being deactivated or stopping data transmission, the UE stops receiving the MBS multicast session in the RRC inactive state.

[0009] In the method of the first aspect above, preferably, if the paging message includes a first field and a second field different from the first field, or includes the first field but not the second field, or includes the second field but not the first field, and

[0010] If condition A or B is met,

[0011] Condition A. If there are one or more MBS sessions to which the UE has joined and indicated only by the TMGI contained in the first field, and the paging message does not contain a ue-Identity or any ue-Identity in the paging message does not match a UE identity allocated by an upper layer;

[0012] Condition B. If there are one or more MBS multicast sessions to which the UE has joined and indicated by the TMGI contained in the second field, but the PTM configuration of the MBS multicast session is not available, and the paging message does not contain a ue-Identity or any ue-Identity in the paging message does not match a UE identity allocated by an upper layer;

[0013] The UE then starts the RRC connection recovery process.

[0014] In the method of the first aspect above, preferably, starting to receive the MBS multicast session in the RRC inactive state comprises one of the following operations:

[0015] Operation 1: instructing the lower layer to monitor the G-RNTI or G-CS-RNTI associated with the MBS multicast session;

[0016] Operation 2: Indicate to the lower layer that the MBS multicast session is activated;

[0017] Operation 3: indicating the MBS multicast session to a lower layer;

[0018] Operation 4: Instruct the lower layer to start or continue receiving the MBS multicast session.

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

[0020] Effects of the Invention

[0021] According to the present invention, a method executed by a user equipment and corresponding user equipment capable of reducing unnecessary energy consumption and inter-layer interaction of the user equipment UE in an MBS multicast session can be provided. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0023] Figure 1 It is a flowchart schematically showing a method executed by a user equipment UE according to an embodiment of the present invention.

[0024] Figure 2 It is a block diagram showing a simplified structure of a user equipment involved in the present invention. DETAILED DESCRIPTION

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

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

[0027] UE: User Equipment.

[0028] RRC: Radio Resource Control.

[0029] RRC_CONNECTED: RRC connected state.

[0030] RRC_INACTIVE: RRC inactive state.

[0031] RRC_IDLE: RRC idle state.

[0032] RAN: Radio Access Network.

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

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

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

[0036] NAS: NonAccess Stratum, non-access layer or non-access layer.

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

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

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

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

[0041] PTM: Point to Multipoint, a delivery method for MBS services. In the PTM delivery method, the gNB delivers a single copy of MBS data packets to a set of UEs. The 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.

[0042] 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 MBS data packets to each UEs independently). For example, the base station schedules the UE-specific PDCCH scrambled by the UE-specific RNTI to schedule the UE-specific PDSCH scrambled by the same UE-specific RNTI.

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

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

[0045] The RRC resume 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. 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 an RRC connection. The RRC resume message RRCResume is used to resume a suspended RRC connection.

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

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

[0048] In Release 17, it is not supported for UEs to receive MBS multicast sessions in the 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 the 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 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. on PDCCH), the UE monitors the paging channel. The paging message 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 UE receiving MBS session).

[0049] 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 the UE with PTM configuration information for receiving the MBS multicast session (also called configuration information of the MBS multicast session or PTM configuration of the MBS multicast session) through dedicated RRC signaling (e.g., RRCRelease message) or through the multicast MBS control channel MCCH (i.e., multicast MCCH). The information required to obtain the multicast MCCH (or multicast MCCH configuration) can be configured for the UE through dedicated RRC signaling or system information block (denoted as SIBx), that is, SIBx contains information for obtaining the MCCH configuration of MBS multicast. The PTM configuration information may include the field MRB-ToAddMod of the configuration information of the MRB corresponding to the MBS multicast session and / or the field MBS-RNTI-SpedificConfig for configuring the configuration information such as G-RNTI / G-CS-RNTI and DRX corresponding to the MBS multicast session. The field MBS-RNTI-SpedificConfig is included in the Mac-CellGroupConfig field.

[0050] 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 RRC may configure a discontinuous reception DRX function for each G-RNTI and / or G-CS-RNTI of the MAC entity to control the UE's PDCCH monitoring activity for the MAC entity's G-RNTI(s) and G-CS-RNTI(s).

[0051] Version 18 supports a UE in an RRC inactive state to receive an MBS multicast session. When a UE in an RRC inactive state receives a paging message from a base station, and the paging message indicates that one or more MBS multicast sessions to which the UE has joined (i.e., is interested) are activated or indicates that data transmission of one or more MBS multicast sessions to which the UE has joined (joined) is resumed: if the PTM configuration of the MBS multicast session is available, the MBS multicast session is started to be received in the RRC inactive state; otherwise (i.e., the PTM configuration of the MBS multicast session is not available), the RRC connection recovery process is started.

[0052] The MBS multicast sessions to which multiple UEs have joined indicated in the received paging message are activated or the data transmission of the MBS multicast sessions to which multiple UEs have joined is indicated to be resumed, and the PTM configuration of only some of the MBS multicast sessions indicated as activated or resumed data transmission may be available. In other words, if there is at least one UE that has joined and the PTM configuration of the MBS multicast session indicated as activated or resumed data transmission in the paging message is not available, the UE will start the RRC connection recovery process so that the UE will enter the RRC connected state. In this case, for those MBS multicast sessions to which the UE has joined and indicated as activated or resumed data transmission, if their PTM configuration is available, whether the UE starts to receive the MBS multicast session in the RRC inactive state is a problem that needs to be solved.

[0053] In addition, if the paging message also indicates that one or more MBS multicast sessions to which the UE has joined are deactivated, or indicates that data transmission of one or more MBS multicast sessions to which the UE has joined is temporarily stopped, or indicates that there is temporarily no data transmission in one or more MBS multicast sessions to which the UE has joined, then whether the UE stops receiving the MBS multicast session in the RRC inactive state is also a problem that needs to be solved.

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

[0055] The embodiment of the present disclosure is described in detail below. The purpose of this embodiment is to prevent the UE from triggering the lower layer to monitor / stop monitoring the MBS multicast session indicated as activated / deactivated and PTM configuration available in the paging message when starting the RRC connection recovery process. Figure 11 is a flow chart schematically showing a method performed by a user equipment UE according to an embodiment of the present invention. Figure 1 As shown, this embodiment may include the following steps:

[0056] Step 101: UE receives a paging message from a base station.

[0057] Step 102: If the UE is in an RRC inactive state and the paging message does not trigger the UE to start an RRC connection recovery process, for each MBS multicast session that the UE has joined and indicated in the paging message as being activated or resuming data transmission, start receiving the MBS multicast session in the RRC inactive state. Optionally, forward the TMGI of the MBS multicast session to an upper layer (e.g., a NAS layer).

[0058] Correspondingly, if the paging message triggers the UE in the RRC inactive state to start the RRC connection recovery process, the RRC connection recovery process is started based on the condition satisfied by the paging message for triggering the UE to start the RRC connection recovery process; in this case, optionally, for the MBS multicast session to which the UE has joined and indicated in the paging message as being activated or resuming data transmission and the PTM configuration of the MBS multicast session is available, the UE does not instruct the lower layer to start receiving the MBS multicast session in the RRC inactive state.

[0059] Optionally, if the paging message does not trigger the UE to start the RRC connection recovery process, for the MBS multicast session that the UE has joined and is indicated in the paging message as being deactivated or stopping data transmission (i.e., temporarily no data transmission), the UE stops receiving the MBS multicast session in the RRC inactive state. Correspondingly, if the paging message triggers the UE to start the RRC connection recovery process, for each MBS multicast session that the UE has joined and is indicated in the paging message as being deactivated or stopping data transmission, the UE does not stop receiving the MBS multicast session in the RRC inactive state.

[0060] The UE initiates the RRC connection recovery process to recover a suspended RRC connection or to start small data transmission in an RRC inactive state. During this process, the UE will generate an RRC recovery request message and receive a response message such as an RRC recovery message or an RRC release message from the base station.

[0061] As a variation of the above embodiment, it can be stipulated that in step 102, if the UE is in an RRC inactive state and the paging message does not trigger the UE to start the RRC connection recovery process, and also satisfies that there is no RRC connection recovery process triggered by other events (such as the arrival of uplink data or the UE performing a RAN-based notification area RNA update, etc.) (that is, there is no RRC connection recovery process that has been initiated or is in progress), then the UE will execute: for each MBS multicast session that the UE has joined and is indicated in the paging message as being activated or resuming data transmission, start receiving the MBS multicast session in the RRC inactive state.

[0062] It should be noted that in the embodiments of the present disclosure, in at least one of the following cases, the paging message will trigger the UE to start the RRC connection recovery process:

[0063] Case 1: For each PagingRecord field contained in the paging message, if the ue-Identity contained in the PagingRecord field matches (ie is the same as) the fullI-RNTI stored in the UE, the UE initiates the RRC connection recovery procedure.

[0064] In the disclosed embodiment, the PagingRecord field includes a ue-Identity field, and optionally, it also includes an accessType field for indicating whether the paging message is initiated due to a PDU session from a non-3GPP access. The value indicated by the ue-Identity field is ng-5G-S-TMSI or fullI-RNTI. The ng-5G-S-TMSI includes a 5G S zero-time mobile identity, which is a temporary UE identity provided by the 5GC (5G core network) to uniquely identify the UE in the tracking area. The value I-RNTI-Value indicated by the fullI-RNTI is used to identify the suspended UE context of a UE in an RRC inactive state.

[0065] Case 2: For the paging message containing a first field and a second field different from the first field, or the paging message containing the first field but not the second field, or the paging message containing the second field but not the first field, if one of the following conditions is met, the UE initiates the RRC connection recovery procedure:

[0066] Condition A. If there are one or more MBS sessions to which the UE has joined and which are indicated only by the TMGI included in the first field (i.e., the paging message does not include the second field or includes the second field but the TMGI is not included in the second field), and the PagingRecordList field is not included in the paging message (i.e., the paging message does not include the ue-Identity) or any ue-Identity in the paging message does not match the UE identity allocated by the upper layer (for the case where the PagingRecordList field is included in the paging message).

[0067] Condition B. If there are one or more MBS multicast sessions that the UE has joined and indicated by the TMGI included in the second field, but the PTM configuration of the MBS multicast session is not available, and the PagingRecordList field is not included in the paging message (that is, the paging message does not include ue-Identity) or any ue-Identity in the paging message does not match the UE identity allocated by the upper layer (for the case where the PagingRecordList field is included in the paging message). The one or more MBS multicast sessions that the UE has joined and indicated by the TMGI included in the second field are MBS multicast sessions indicated by the paging message as being activated or resuming data transmission.

[0068] It should be noted that in conditions A and B, the inclusion of TMGI in the second field means that the MBS multicast session indicated by the TMGI is indicated in the second field as being activated or resuming data transmission. The non-inclusion of TMGI in the second field means that the MBS multicast session indicated by the TMGI is indicated in the second field as being deactivated or stopping data transmission or there is no indication information of the TMGI in the second field.

[0069] Preferably, in the embodiment of the present disclosure, the first field is denoted as pagingGroupList, which contains one or more TMGIs (i.e., a TMGI list), and the PagingRecordList field contains one or more PagingRecord fields (i.e., a PagingRecord list). For a UE supporting version 17, upon receiving the first field, for a UE in an RRC inactive state, if the UE has joined one or more MBS sessions indicated by the TMGI contained in the first field, and the PagingRecordList field is not included in the paging message (i.e., the paging message does not contain ue-Identity) or any ue-Identity in the paging message does not match the UE identifier assigned by the upper layer (for the case where the PagingRecordList field is included in the paging message), the UE always starts the RRC connection recovery process; for a UE in an RRC idle state, upon receiving the paging message containing the first field, the following operations are performed for each TMGI contained in the first field: if the UE has joined the MBS multicast session indicated by the TMGI, the TMGI is forwarded to the upper layer (e.g., the NAS layer).

[0070] Preferably, in the embodiment of the present disclosure, the second field is used to indicate whether an MBS multicast session is activated or data transmission is resumed (i.e., whether it can be received in an RRC inactive state). In other words, the UE determines whether to receive the MBS multicast session in an RRC inactive state only for the MBS multicast session whose TMGI is included in the second field, according to whether its PTM configuration is available. Specifically, the second field may include a TMGI list (recorded as a first TMGI list) to indicate the MBS multicast session for which data transmission is activated or resumed, and the MBS multicast session indicated by the TMGI appearing in the list is activated or data transmission is resumed. In addition to the first TMGI list, the second field may also include an indicator (recorded as a first indicator) that corresponds one-to-one to the TMGI in the first field to indicate whether the MBS multicast session indicated by the TMGI included in the first field is activated or data transmission is resumed. In the case where the second field includes the first indicator, it can be specified that the first TMGI list only includes the TMGI not included in the first field. In other words, a TMGI cannot be included in both the first field and the first TMGI list. In addition, the embodiment of the present disclosure does not limit the inclusion relationship between the first field and the second field, and the second field may be included in the first field or may not be included in the first field. The first indicator identifier may also not be included in the second field, but may be included in the first field or may not be included in the first field and the second field. In this case, the situation in which the TMGI described in the embodiment of the present disclosure is included in the second field and is indicated by the first indicator identifier should be understood as the TMGI being indicated in the first indicator identifier.

[0071] Accordingly, in the embodiment of the present disclosure, the TMGI included in the second field may mean that the TMGI itself is included in the second field (i.e., included in the first TMGI list), or may mean that the TMGI is included in the first field, and the second field includes the first indication identifier. The TMGI included in the second field means that the MBS multicast session indicated by the TMGI is indicated in the second field as being activated or resuming data transmission.

[0072] Preferably, for an MBS multicast session that is deactivated or data transmission is stopped using a paging message, a TMGI list may be used in the second field to indicate (recorded as a second TMGI list) that the corresponding MBS multicast session is deactivated or data transmission is stopped. It may be specified that a TMGI cannot be included in both the first field and the second TMGI list. It may also be specified that a TMGI cannot be included in both the first TMGI list and the second TMGI list.

[0073] Alternatively, an indication flag may be defined for each TMGI (or MBS multicast session) in the second field, and different values ​​of the indication flag may be used to indicate whether the corresponding MBS multicast session is activated or deactivated or whether data transmission is resumed or suspended.

[0074] As another variation of the above embodiment, in step 102, if the UE does not meet the conditions listed in the above situation 1-2, then for each MBS multicast session that the UE has joined and indicated in the paging message as being activated or resuming data transmission, the UE starts receiving the MBS multicast session in an RRC inactive state.

[0075] As another variation of the above embodiment, in step 102, if the UE does not meet the conditions listed in the above situation 1-2, and there is no RRC connection recovery process triggered by other events (such as the arrival of uplink data or the UE performing a RAN-based notification area RNA update, etc.) (that is, there is no triggered RRC connection recovery process or an ongoing RRC connection recovery process), then for each MBS multicast session that the UE has joined and is indicated in the paging message as being activated or resuming data transmission, the UE starts to receive the MBS multicast session in the RRC inactive state.

[0076] The following is a detailed description through examples.

[0077] Example 1

[0078] The UE receives a paging message from a base station. If the paging message includes a first field, the following operations are performed:

[0079] For a UE in the RRC idle state, upon receiving the paging message including the first field, the following operations are performed for each TMGI included in the first field: if the UE joins the MBS multicast session indicated by the TMGI, the TMGI is forwarded to an upper layer (eg, a NAS layer).

[0080] For a UE in an RRC inactive state, upon receiving the paging message containing the first field, if the UE joins one or more MBS sessions indicated by the TMGI contained in the first field, and the PagingRecordList field is not included in the paging message (i.e., the paging message does not contain ue-Identity) or any ue-Identity in the paging message does not match the UE identifier assigned by the upper layer (for the case where the PagingRecordList field is included in the paging message), it is further determined whether the paging message contains the second field. If one of the following conditions 1-4 is met, the UE initiates the RRC connection recovery process.

[0081] Condition 1: The paging message does not include the second field.

[0082] Condition 2: The paging message contains a second field, and there is an MBS multicast session indicated by the TMGI to which the UE indicated by the first field has joined, which is indicated by the second field as being activated or continuing data transmission (that is, the TMGI of the MBS multicast session to which the UE indicated by the first field has joined is included in the second field, and the second field is only used to indicate the MBS multicast session that is activated or continuing data transmission), but the PTM configuration of the MBS multicast session is not available.

[0083] Condition 3: The paging message includes a second field, and there is an MBS multicast session to which the UE has joined whose TMGI is not included in the first field and the MBS multicast session is indicated by the second field as being activated or continuing data transmission (i.e., the second field includes a TMGI not included in the first field), but the PTM configuration of the MBS multicast session is not available.

[0084] Condition 4: the paging message includes the second field, and the MBS multicast session indicated by the TMGI to which the UE has joined indicated by the first field is not indicated in the second field (ie, the TMGI of the multicast session is not included in the second field).

[0085] If the paging message does not contain the first field but contains the second field, and the PagingRecordList field is not included in the paging message (that is, the paging message does not contain ue-Identity) or any ue-Identity in the paging message does not match the UE identifier assigned by the upper layer (for the case where the PagingRecordList field is included in the paging message), further, if the following condition I is met, the UE initiates the RRC connection recovery process.

[0086] Condition I: If there is an MBS multicast session that the UE has joined and is indicated by the second field as being activated or continuing data transmission (ie, the TMGI of the MBS multicast session that the UE has joined is included in the second field), but the PTM configuration of the MBS multicast session is not available.

[0087] If the paging message includes the first field and the second field, but condition 2, condition 3, and condition 4 are not met, or if the paging message does not include the first field but includes the second field, but condition I is not met, and the PagingRecordList field is not included in the paging message (that is, the paging message does not include ue-Identity) or any ue-Identity in the paging message does not match the UE identifier allocated by the upper layer (for the case where the PagingRecordList field is included in the paging message), perform at least one of the following operations:

[0088] Operation a: For an MBS multicast session to which the UE has joined and which is indicated in the second field as being activated or continuing data transmission, start receiving the MBS multicast session in an RRC inactive state.

[0089] Operation b: Forward the TMGI to an upper layer.

[0090] Operation c: For an MBS multicast session to which the UE has joined and which is indicated in the second field as being deactivated or having stopped data transmission (temporarily having no data transmission), stop receiving the MBS multicast session in an RRC inactive state.

[0091] If the MBS multicast session that is deactivated or stops data transmission is indicated in the paging message, the second field may indicate both the MBS multicast session that is activated or resumes data transmission and the MBS multicast session that is deactivated or stops data transmission. For details, see the description / definition of the second field in this disclosure.

[0092] In the embodiments of the present disclosure, the PTM configuration of the MBS multicast session is available and may include the following cases A and B:

[0093] Case A. The UE includes the PTM configuration of the MBS multicast session in the (most recently) received RRCRelease message; or, the PTM configuration of the MBS multicast session is included in the RRCRelease message. Specifically, the UE receives an RRC release message from the base station, and for each MBS multicast session included in the RRC release message (or the PTM configuration of the MBS multicast session included in the RRC release message), considers its PTM configuration to be available. Optionally, for an MBS multicast session that the UE has joined but whose PTM configuration is not included in the RRC release message, its PTM configuration is considered to be unavailable. It can also be stipulated that when the UE receives an RRC release message, if the RRC release message does not include the PTM configuration of at least one MBS multicast session that the UE has joined, the UE obtains a multicast MCCH message to determine whether the PTM configuration of the MBS multicast session is available.

[0094] Case B. The UE receives the PTM configuration of the corresponding MBS multicast session in the multicast MCCH message. This may include two cases: one is that the UE receives the PTM configuration of the corresponding MBS multicast session in the multicast MCCH message that was recently received or currently being broadcast; the other is that the UE receives the PTM configuration of the multicast MBS from the multicast MCCH message after entering the RRC inactive state, that is, after the UE enters the RRC inactive state, although the multicast MCCH message that was recently received or currently being broadcast does not contain the PTM configuration of the multicast MBS, the PTM configuration of the multicast MBS was received in the multicast MCCH message that was previously broadcast. Specifically, when the UE receives a multicast MCCH message from the base station (that is, an MCCH message for MBS multicast or an MCCH message for an MBS multicast session), if the MCCH message contains the PTM configuration of the MBS multicast session that the UE has joined, the PTM configuration of the MBS multicast session is considered to be available. If the multicast MCCH message received by the UE does not contain the PTM configuration of an MBS multicast session that the UE has joined, but the multicast MCCH message received previously contains the PTM configuration of the MBS multicast session, the UE still considers the PTM configuration of the MBS multicast session to be available. In other words, as long as the PTM configuration of an MBS multicast session that the UE has joined is included in the RRC release message or the PTM configuration of the MBS multicast session has been received in the multicast MCCH message, the PTM configuration of the MBS multicast session is considered to be available, regardless of whether the PTM configuration of the MBS multicast session is included in the most recently received or broadcasted multicast MCCH message.

[0095] In the disclosed embodiment, the PTM configuration of the MBS multicast session is unavailable, which may mean that the UE cannot obtain the PTM configuration in situations A and B, that is, the PTM configuration of the MBS multicast session is neither included in the RRC release message nor obtained from the multicast MCCH message after entering the RRC inactive state or is not included in the multicast MCCH message being broadcast.

[0096] In addition, in the embodiment of the present disclosure, starting to receive the MBS multicast session in the RRC inactive state may be one of the following operations:

[0097] Operation 1: The UE (ie, the RRC layer of the UE) instructs a lower layer (the lower layer may be a MAC layer) to monitor the G-RNTI or G-CS-RNTI associated with the MBS multicast session.

[0098] Operation 2: The UE (ie, the RRC layer of the UE) indicates to the lower layer (the lower layer may be the MAC layer) that the MBS multicast session is activated and / or the G-RNTI or G-CS-RNTI associated with the MBS multicast session.

[0099] Operation 3: Indicate the MBS multicast session to a lower layer (the lower layer may be a MAC layer).

[0100] Operation 4: Instruct a lower layer (the lower layer may be a MAC layer) to start / continue / resume receiving the MBS multicast session.

[0101] It should be noted that after receiving the indication, the MAC entity / layer starts to monitor the G-RNTI or G-CS-RNTI or monitors the G-RNTI or G-CS-RNTI according to the configured discontinuous reception DRX, for example, starting the DRX-related timer drx-onDurationTimerPTM for the G-RNTI or G-CS-RNTI. During the operation of the timer, the UE is considered to be in the activation time of DRX. When the timer is running, the UE monitors the G-RNTI or G-CS-RNTI

[0102] In addition, in the implementation of the present disclosure, stopping receiving the MBS multicast session in the RRC inactive state may be one of the following operations:

[0103] Operation I: The UE (ie, the RRC layer of the UE) instructs a lower layer (the lower layer may be a MAC layer) to stop monitoring (ie, stop receiving) the MBS multicast session.

[0104] Operation II: The UE (ie, the RRC layer of the UE) indicates to the lower layer (the lower layer may be the MAC layer) that the MBS multicast session is deactivated.

[0105] Operation III: The UE (ie, the RRC layer of the UE) instructs a lower layer (the lower layer may be a MAC layer) to stop monitoring the G-RNTI or G-CS-RNTI associated with the MBS multicast session.

[0106] Operation IV: The UE (ie, the RRC layer of the UE) indicates to the lower layer (the lower layer may be the MAC layer) that the MBS multicast session is deactivated and indicates its associated G-RNTI or G-CS-RNTI to the lower layer.

[0107] It should be noted that after receiving an instruction from the upper layer (ie, the RRC layer / entity), the MAC entity / layer stops the DRX timer of the MBS multicast session and / or stops monitoring the G-RNTI and / or G-CS-RNTI corresponding to the MBS multicast session.

[0108] When the UE initiates the RRC connection recovery process, if the process is successfully completed, the UE will enter the RRC connected state. At this time, those MBS multicast sessions received in the RRC inactive state will also be configured to be received in the RRC connected state. However, if the UE initiates the RRC connection recovery process but does not cause the UE to enter the RRC connected state, the MBS multicast sessions received in the RRC inactive state need to be maintained to improve the reliability and service continuity of the MBS multicast sessions received in the RRC inactive state. Therefore, it can be stipulated that the UE will stop receiving the MBS multicast session only when it receives the RRC recovery message or the RRC establishment message RRCSetup. Stopping the reception of the MBS multicast session can be achieved by resetting the MAC, or by the above-mentioned operation performed when stopping the reception of the MBS multicast session in the RRC inactive state. The RRC establishment message RRCSetup is used to establish SRB1.

[0109] In addition, the description of the functions of the fields involved in the present disclosure, unless otherwise specified, is applicable to all embodiments of the present disclosure. In the embodiments of the present disclosure, monitoring and detecting (detect) are interchangeable.

[0110] Figure 2 It is a block diagram showing a simplified structure of a user equipment involved in the present invention.

[0111] like Figure 2 As shown, the user equipment 20 includes at least a processor 201 and a memory 202. The processor 201 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 202 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 systems, etc. The memory 202 stores program instructions. When the instructions are executed by the processor 201, one or more steps of the processing method of the UE of the present disclosure may be executed.

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

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

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

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

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

[0117] 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: Step 1: The UE receives a paging message from a base station; and Step 2: If the UE is in an RRC inactive state and the paging message does not trigger the UE to start the RRC connection recovery process, for each MBS multicast session that the UE has joined and is indicated in the paging message as being activated or resuming data transmission, start receiving the MBS multicast session in the RRC inactive state.

2. The method according to claim 1, comprising: The TMGI of the MBS multicast session is forwarded to an upper layer.

3. The method according to claim 1 or 2, wherein: For each PagingRecord field contained in the paging message, if the ue-Identity contained in the PagingRecord field matches the fullI-RNTI stored in the UE, the RRC connection recovery process is started.

4. The method according to claim 1 or 2, wherein: If the UE is in an RRC inactive state and the paging message does not trigger the UE to initiate an RRC connection recovery procedure, then for each MBS multicast session that the UE has joined and is indicated in the paging message as being deactivated or stopping data transmission, the UE stops receiving the MBS multicast session in the RRC inactive state.

5. The method according to claim 1 or 2, wherein If the paging message includes a first field and a second field different from the first field, or includes the first field but not the second field, or includes the second field but not the first field, and If condition A or B is met, Condition A. If there are one or more MBS sessions to which the UE has joined and indicated only by the TMGI contained in the first field, and the paging message does not contain a ue-Identity or any ue-Identity in the paging message does not match a UE identity allocated by an upper layer; Condition B. If there are one or more MBS multicast sessions to which the UE has joined and indicated by the TMGI contained in the second field, but the PTM configuration of the MBS multicast session is not available, and the paging message does not contain a ue-Identity or any ue-Identity in the paging message does not match a UE identity allocated by an upper layer; The UE then starts the RRC connection recovery process.

6. The method according to claim 1 or 2, wherein the starting to receive the MBS multicast session in the RRC inactive state comprises one of the following operations: Operation 1: instructing the lower layer to monitor the G-RNTI or G-CS-RNTI associated with the MBS multicast session; Operation 2: Indicate to the lower layer that the MBS multicast session is activated; Operation 3: indicating the MBS multicast session to a lower layer; Operation 4: Instruct the lower layer to start or continue receiving the MBS multicast session.

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