Method executed by user equipment, and user equipment
By determining whether to start the RRC connection recovery process after receiving the base station paging message, and starting or stopping the reception of the MBS multicast session according to the message instructions, the problem of 5G multicast broadcast service receiving in the RRC inactive state is solved, reducing the ability of the 5G multicast broadcast service to receive the RRC inactive state. Consumption and inter-layer interaction to improve reception efficiency and reliability.
Patent Information
- Application Number
- PCT/CN2024/091660
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-11
- Filing Date
- 2024-05-08
- Publication Date
- 2024-11-14
AI Technical Summary
The existing 5G multicast broadcast service cannot effectively support user equipment to receive MBS multicast sessions in the RRC inactive state, resulting in unnecessary energy consumption and inter-layer interactions.
When receiving a paging message from the base station, the user equipment determines whether it is necessary to start the RRC connection recovery process, and starts or stops receiving the MBS multicast session in the RRC inactive state according to the instructions in the message, by monitoring the associated G-RNTI or G-CS-RNTI to receive multicast sessions, optimize energy consumption and interactive operations.
It reduces unnecessary energy consumption and inter-layer interaction of user equipment, and improves the efficiency and reliability of MBS multicast session reception in RRC inactive state.
Smart Images

Figure CN2024091660_14112024_PF_FP_ABST
Abstract
Description
Method performed by user equipment and user equipment Technical Field
[0001] The present invention relates to the technical field of wireless communications, and more particularly, to a method executed by a user equipment and the user equipment. Background Art
[0002] A study item (SI) on improving the 5G multicast broadcast service architecture (see SP-190625) has been approved. One of the objectives of this SI (referred to as Objective A) is to support universal MBS services in the 5GS. Use cases that could benefit from this feature include (but are not limited to) public safety, vehicle-to-everything (V2X) applications, transparent IPv4 / IPv6 multicast transmission, IPTV, wireless software delivery, group communications, and IoT applications. Accordingly, at the 3rd Generation Partnership Project (3GPP) RAN#86 plenary meeting, a work item on NR multicast and broadcast service (NR MBS) was proposed and approved (see non-patent document RP-193248: New WID: NR Multicast and Broadcast Service). This work item aims to provide support for Objective A in the RAN. The objectives of this work item have been largely achieved, and the relevant solutions are described in 3GPP Release 17 technical documents such as TS 38.300-h30, TS 38.331-h30, and TS 38.321-h30. At the 3GPP RAN#94 plenary meeting, a work item titled "Enhanced NR Multicast and Broadcast Services" was approved (see non-patent document: RP-213568: New WID: Enhancements of NR Multicast and Broadcast Services). This work item aims to further enhance MBS Multicast and Broadcast Services in Release 17, with one of its goals being to support user equipment receiving MBS multicast services / sessions even when RRC is not active.
[0003] The present invention discusses related issues involved in RAN supporting user equipment to receive MBS multicast services / sessions in an RRC inactive state.
[0004] Summary of the Invention
[0005] In order to solve the above problem, the present invention provides a method performed by a user equipment and the user equipment.
[0006] 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 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 activated or resuming data transmission, starting to receive the MBS multicast session in the RRC inactive state.
[0007] In the method of the first aspect above, preferably, the TMGI of the MBS multicast session is forwarded to an upper layer.
[0008] 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.
[0009] 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 initiate 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 deactivated or stopping data transmission, the UE stops receiving the MBS multicast session in the RRC inactive state.
[0010] 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
[0011] If condition A or B is met,
[0012] 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 assigned by an upper layer;
[0013] 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 assigned by an upper layer;
[0014] The UE then starts the RRC connection recovery process.
[0015] In the method of the first aspect above, preferably, starting to receive the MBS multicast session in the RRC inactive state includes one of the following operations:
[0016] Operation 1: instruct the lower layer to monitor the G-RNTI or G-CS-RNTI associated with the MBS multicast session;
[0017] Operation 2: Indicate to the lower layer that the MBS multicast session is activated;
[0018] Operation 3: Indicate the MBS multicast session to the lower layer;
[0019] Operation 4: Instruct the lower layer to start or continue receiving the MBS multicast session.
[0020] 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.
[0021] Effects of the Invention
[0022] According to the present invention, a method executed by a user equipment (UE) and corresponding user equipment can be provided, which can reduce unnecessary energy consumption and inter-layer interaction of the user equipment (UE) in an MBS multicast session. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] 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:
[0024] FIG1 is a flowchart schematically illustrating a method executed by a user equipment UE according to an embodiment of the present invention.
[0025] FIG2 is a block diagram showing a schematic structure of a user equipment according to the present invention. DETAILED DESCRIPTION
[0026] The present invention is described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that the present invention is not limited to the specific embodiments described below. In addition, for the sake of simplicity, detailed descriptions of known technologies that are not directly related to the present invention are omitted to prevent confusion in understanding the present invention.
[0027] The following describes some of the terms involved in the present invention. For their specific meanings, please refer to the latest relevant 3GPP documents, such as TS38.300-h30, TS38.321-h30, TS38.323-h30, and TS38.331-h30. Furthermore, the embodiments of the present invention are described using broadcast / multicast services as an example. However, the embodiments of the present invention are not limited to broadcast / multicast services and can also be applied to other application scenarios.
[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 is also called multicast.
[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] MBS Radio Bearer (MRB): A radio bearer configured for MBS delivery. MRBs are classified into multicast MRBs and broadcast MRBs. A multicast MRB is a radio bearer configured for MBS multicast transmission, while a broadcast MRB is a radio bearer configured for MBS broadcast transmission.
[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) is a method for delivering MBS services. In PTM, the gNB delivers a single copy of MBS data packets to a group of UEs. UEs use a G-RNTI or G-CS-RNTI to receive PTM transmissions. For example, the gNB uses the G-RNTI-based group-common physical downlink control channel (PDCCH) to schedule the same G-RNTI-based group-common physical downlink shared channel (PDSCH).
[0043] PTP: Point to Point, a delivery method for MBS services. In PTP, the gNB individually delivers separate copies of MBS data packets to each UE independently. For example, the base station schedules a UE-specific PDCCH scrambled with a UE-specific RNTI and a UE-specific PDSCH scrambled with the same UE-specific RNTI.
[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 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 instruct the release of an RRC connection or the suspension of an RRC connection. The RRC reconfiguration message RRCReconfiguration is used to instruct the modification of an RRC connection. The RRC resume message RRCResume is used to resume a suspended RRC connection.
[0047] In the present invention, network, base station and RAN can be used interchangeably. The network can be a long-term evolution LTE network, a NR network, an enhanced long-term evolution eLTE network, or other networks defined in subsequent evolution versions of 3GPP.
[0048] Currently, NR MBS services include MBS broadcast (also known as MBS broadcast session or broadcast MBS or MBS broadcast service) and MBS multicast (also known as MBS multicast session or multicast MBS or MBS multicast service). MBS broadcast provides a downlink-only MBS transmission mode for services with low quality of service (QoS), so that UEs in RRC connected state, RRC idle state, and RRC inactive state can receive the MBS service. The UE obtains the MBS broadcast configuration information broadcast by the network through the MBS control channel MCCH. In 3GPP Release 17, before receiving the MBS multicast service (i.e., MBS multicast session), the UE needs to establish an RRC connection with the base station. The base station then configures resources for receiving the MBS multicast service for the UE through dedicated RRC signaling (also known as RRC message, such as RRC reconfiguration message). The MBS radio bearer (MRB) for receiving these MBS multicast services is also configured for the UE by the base station through dedicated RRC signaling. Only UEs in the RRC connected state and with the MRB configured can receive the corresponding MBS multicast service.
[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 that supports MBS multicast notifies the UE in RRC idle state or RRC inactive state through the group notification mechanism. Upon receiving the group notification, the UE that has joined or is interested in the MBS multicast session establishes 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 session).
[0050] In version 18, the UE is supported to receive MBS multicast sessions in the RRC inactive state. For MBS multicast sessions received in the RRC inactive state, the base station can provide the UE with PTM configuration information for receiving the MBS multicast session (also called MBS multicast session configuration information or MBS multicast session PTM configuration) through dedicated RRC signaling (such as 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 G-RNTI / G-CS-RNTI and DRX configuration information corresponding to the MBS multicast session. The MBS-RNTI-SpedificConfig field is included in the Mac-CellGroupConfig field.
[0051] Each MBS multicast session is identified by a TMGI and associated with a G-RNTI or G-CS-RNTI. The UE receives the MBS multicast session by monitoring the G-RNTI or G-CS-RNTI associated with the MBS multicast session. For MBS multicast, the MAC entity may be configured by RRC with a DRX functionality per G-RNTI or per G-CS-RNTI that controls the UE's PDCCH monitoring activity for the MAC entity's G-RNTI(s)and G-CS-RNTI(s).
[0052] Release 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, where 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 is resumed: if the PTM configuration of the MBS multicast session is available, the UE starts receiving the MBS multicast session 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 initiated.
[0053] When the MBS multicast sessions indicated in the received paging message to which multiple UEs have joined are activated or data transmission of the MBS multicast sessions indicated to be resumed, it is possible that only some of the PTM configurations of the MBS multicast sessions indicated as activated or resumed are available. In other words, if the PTM configuration of the MBS multicast session indicated as activated or resumed by at least one UE to which the UE has joined is unavailable, the UE will initiate the RRC connection recovery process, so that the UE will enter the RRC connected state. In this case, for those MBS multicast sessions indicated to be activated or resumed by the UE, if their PTM configurations are available, whether the UE starts receiving the MBS multicast sessions in the RRC inactive state is a problem that needs to be solved.
[0054] 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.
[0055] To address at least some of the above problems, the present disclosure provides corresponding embodiments. Specific embodiments are listed below to illustrate the processing method of the present invention. Furthermore, the embodiments listed below are merely illustrative and do not limit the present invention.
[0056] The following describes an embodiment of the present disclosure in detail. This embodiment aims to prevent the UE from triggering lower layer monitoring / stopping monitoring of an MBS multicast session indicated as activated / deactivated in a paging message and with available PTM configuration when initiating an RRC connection recovery procedure. Figure 1 is a flowchart schematically illustrating a method performed by a user equipment (UE) according to an embodiment of the present invention. As shown in Figure 1, this embodiment may include the following steps:
[0057] Step 101: The UE receives a paging message from a base station.
[0058] Step 102: 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 to which the UE has joined and indicated in the paging message as activated or resuming data transmission, the UE begins receiving the MBS multicast session in the RRC inactive state. Optionally, the TMGI of the MBS multicast session is forwarded to an upper layer (e.g., a NAS layer).
[0059] 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 conditions 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 that the UE has joined and is 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.
[0060] Optionally, if the paging message does not trigger the UE to initiate an RRC connection recovery procedure, for an MBS multicast session to which the UE has joined and which is indicated in the paging message as being deactivated or having data transmission stopped (i.e., temporarily having 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 initiate an RRC connection recovery procedure, for each MBS multicast session to which the UE has joined and which is indicated in the paging message as being deactivated or having data transmission stopped, the UE does not stop receiving the MBS multicast session in the RRC inactive state.
[0061] The UE initiates the RRC connection recovery process to resume a suspended RRC connection or initiate small data transmission in the 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 RRC release message from the base station.
[0062] As a variation of the above embodiment, it can be stipulated that, in step 102, the UE, when the conditions are satisfied that if the UE is in an RRC inactive state and the paging message does not trigger the UE to initiate an RRC connection recovery process, 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.) (i.e., there is no RRC connection recovery process that has been initiated or is in progress), then the UE executes: 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 receiving the MBS multicast session in the RRC inactive state.
[0063] It should be noted that, in the embodiments of the present disclosure, the paging message will trigger the UE to initiate the RRC connection recovery process in at least one of the following situations:
[0064] 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 by the UE, the UE initiates the RRC connection recovery procedure.
[0065] In the embodiment of the present disclosure, the PagingRecord field includes a ue-Identity field. 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 the 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.
[0066] Case 2: If the paging message contains a first field and a second field different from the first field, or the paging message contains the first field but does not contain the second field, or the paging message contains the second field but does not contain the first field, the UE initiates the RRC connection recovery procedure if one of the following conditions is met:
[0067] 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).
[0068] 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 PagingRecordList field is not included in the paging message (i.e., the paging message does not include a ue-Identity), or any ue-Identity in the paging message does not match a UE identifier assigned by an upper layer (for the case where the PagingRecordList field is included in the paging message). The one or more MBS multicast sessions to which the UE has joined and indicated by the TMGI contained in the second field are MBS multicast sessions indicated by the paging message as being activated or resuming data transmission.
[0069] It should be noted that in conditions A and B, the inclusion of a 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 absence of a 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 of the TMGI in the second field.
[0070] Preferably, in an embodiment of the present disclosure, the first field, denoted as pagingGroupList, 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 Release 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 TMGIs contained in the first field, and the PagingRecordList field is not included in the paging message (i.e., the paging message does not include a ue-Identity), or any ue-Identity in the paging message does not match a UE identifier assigned by an upper layer (for the case where the PagingRecordList field is included in the paging message), the UE always initiates an RRC connection recovery procedure. For a UE in an RRC-idle state, upon receiving the paging message including 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 an upper layer (e.g., a NAS layer).
[0071] Preferably, in an embodiment of the present disclosure, the second field is used to indicate whether an MBS multicast session has been activated or data transmission has 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, based on whether its PTM configuration is available. Specifically, the second field may include a TMGI list (denoted as a first TMGI list) to indicate the MBS multicast sessions that have been activated or data transmission has resumed. The MBS multicast sessions indicated by the TMGIs appearing in the list are activated or data transmission has resumed. In addition to the first TMGI list, the second field may also include an indicator (denoted as a first indicator) that corresponds one-to-one with the TMGI in the first field to indicate whether the MBS multicast session indicated by the TMGI included in the first field has been activated or data transmission has resumed. If the second field includes the first indicator, it may be specified that the first TMGI list only includes TMGIs not included in the first field. In other words, a TMGI cannot be included in both the first field and the first TMGI list. Furthermore, the embodiments of the present disclosure do not limit the inclusion relationship between the first field and the second field; the second field may or may not be included in the first field. The first indicator identifier may also be included in the first field or not in both the first and second fields, rather than in the second field. In this case, the situation in which the TMGI is included in the second field and indicated by the first indicator identifier in the embodiments of the present disclosure should be understood as the TMGI being indicated in the first indicator identifier.
[0072] Accordingly, in the embodiments of the present disclosure, the inclusion of the TMGI 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 inclusion of the 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.
[0073] Preferably, for an MBS multicast session that uses a paging message to indicate / notify deactivation or data transmission suspension, a TMGI list (referred to as a second TMGI list) may be used in the second field to indicate that the corresponding MBS multicast session has been deactivated or data transmission suspension has been suspended. It may be stipulated that a TMGI cannot be included in both the first field and the second TMGI list. It may also be stipulated that a TMGI cannot be included in both the first TMGI list and the second TMGI list.
[0074] 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.
[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, 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] 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.
[0077] The following is a detailed description through examples.
[0078] Example 1
[0079] The UE receives a paging message from a base station. If the paging message includes a first field, the UE performs the following operations:
[0080] For a UE in the RRC idle state, upon receiving the paging message containing the first field, the following operations are performed on each TMGI contained 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).
[0081] For a UE in an RRC inactive state, upon receiving the paging message containing the first field, 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 contained in the paging message (i.e., the paging message does not contain a UE-Identity), or any UE-Identity in the paging message does not match a UE identifier assigned by an upper layer (for the case where the PagingRecordList field is contained in the paging message), then a determination is made as to whether the paging message contains the second field. If any of the following conditions 1-4 is met, the UE initiates the RRC connection recovery procedure.
[0082] Condition 1: The paging message does not include the second field.
[0083] 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 indicated by the first field to which the UE has joined is contained 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.
[0084] Condition 3: The paging message includes the 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.
[0085] Condition 4: the paging message includes a second field, and the MBS multicast session indicated by the TMGI that the UE has joined as 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).
[0086] 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 allocated 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.
[0087] 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.
[0088] If the paging message contains the first field and the second field but does not meet conditions 2, 3, and 4, or if the paging message does not contain the first field but contains the second field but does not meet condition 1, 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:
[0089] Operation a: For an MBS multicast session that the UE has joined and that is indicated in the second field as being activated or continuing data transmission, start receiving the MBS multicast session in an RRC inactive state.
[0090] Operation b: Forward the TMGI to the upper layer.
[0091] 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 the RRC inactive state.
[0092] If the MBS multicast session that is deactivated or stops data transmission is indicated in the paging message, the second field can 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.
[0093] In the embodiments of the present disclosure, the PTM configuration of the MBS multicast session may be available and may include the following cases A and B:
[0094] 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 that its PTM configuration is 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.
[0095] Case B: The UE receives the PTM configuration for the corresponding MBS multicast session in a multicast MCCH message. This can include two cases: one is that the UE receives the PTM configuration for the corresponding MBS multicast session in a recently received or currently broadcast multicast MCCH message; the other is that the UE receives the PTM configuration for the multicast MBS from a multicast MCCH message after entering the RRC inactive state. That is, after the UE enters the RRC inactive state, although the recently received or currently broadcast multicast MCCH message does not contain the PTM configuration for the multicast MBS, the UE receives the PTM configuration for the multicast MBS in a previously broadcast multicast MCCH message. Specifically, when the UE receives a multicast MCCH message (i.e., an MCCH message for MBS multicast or an MCCH message for an MBS multicast session) from the base station, if the MCCH message contains the PTM configuration for the MBS multicast session that the UE has joined, the UE considers the PTM configuration for the MBS multicast session to be available. If a multicast MCCH message received by a UE does not contain the PTM configuration of an MBS multicast session that the UE has joined, but a previously received multicast MCCH message contained 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 an RRC release message or the UE has received the PTM configuration of the MBS multicast session in a multicast MCCH message, the UE considers the PTM configuration of the MBS multicast session to be available, regardless of whether the PTM configuration of the MBS multicast session is included in the most recently received or currently broadcast multicast MCCH message.
[0096] In the embodiment of the present disclosure, 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.
[0097] 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:
[0098] 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.
[0099] Operation 2: The UE (ie, the RRC layer of the UE) indicates to a lower layer (the lower layer may be a MAC layer) that the MBS multicast session is activated and / or the G-RNTI or G-CS-RNTI associated with the MBS multicast session.
[0100] Operation 3: Indicate the MBS multicast session to a lower layer (the lower layer may be a MAC layer).
[0101] Operation 4: Instruct a lower layer (the lower layer may be a MAC layer) to start / continue / resume receiving the MBS multicast session.
[0102] It should be noted that after receiving the indication, the MAC entity / layer starts monitoring 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
[0103] In addition, in the embodiment of the present disclosure, stopping receiving the MBS multicast session in the RRC inactive state may be one of the following operations:
[0104] 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.
[0105] Operation II: The UE (ie, the RRC layer of the UE) indicates to a lower layer (the lower layer may be a MAC layer) that the MBS multicast session is deactivated.
[0106] 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.
[0107] 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.
[0108] It should be noted that after receiving an indication 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.
[0109] 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.
[0110] In addition, the description of the functions of the fields involved in this disclosure, unless otherwise specified, is applicable to all embodiments of this disclosure. In the embodiments of this disclosure, monitoring and detecting are interchangeable.
[0111] FIG2 is a block diagram showing a schematic structure of a user equipment according to the present invention.
[0112] As shown in Figure 2, 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. The memory 202 stores program instructions. When executed by the processor 201, the instructions may perform one or more steps of the UE processing method disclosed herein.
[0113] In the embodiments of the present disclosure, when multiple operations are included, the execution order of each operation is exemplarily listed in the embodiments of the present disclosure. Embodiments obtained by changing the execution order of each operation are also within the scope of protection of the present disclosure. In addition, when multiple judgment conditions are included, embodiments obtained by changing the execution order of the judgment conditions are also within the scope of protection of the present disclosure.
[0114] 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.
[0115] The computer executable instructions or program for realizing each embodiment of the present invention function can be recorded on a computer-readable storage medium. The corresponding function can be realized by making a computer system read the program recorded on the recording medium and executing these programs. The so-called "computer system" herein can be a computer system embedded in the device, and can include an operating system or hardware (such as a peripheral device). "Computer-readable storage medium" can be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a short-term dynamic storage program recording medium or any other recording medium that is computer-readable.
[0116] The various features or functional modules of the devices used in the above embodiments can be implemented or executed by circuits (e.g., single-chip or multi-chip integrated circuits). The circuits designed to perform the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above devices. The general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine. The above circuits may be digital circuits or analog circuits. In the event that new integrated circuit technologies have emerged to replace existing integrated circuits due to advances in semiconductor technology, one or more embodiments of the present invention may also be implemented using these new integrated circuit technologies.
[0117] Furthermore, the present invention is not limited to the above-described embodiments. Although various examples of the embodiments have been described, the present invention is not limited thereto. Fixed or non-mobile electronic devices installed indoors or outdoors can be used as terminal devices or communication devices, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.
[0118] As described above, the embodiments of the present invention have been described in detail with reference to the accompanying drawings. However, the specific structure is not limited to the above-described embodiments, and the present invention also includes any design changes that do not deviate from the main purpose of the present invention. In addition, various modifications can be made to the present invention within the scope of the claims, and embodiments obtained by appropriately combining the technical means invented by different embodiments are also included in the technical scope of the present invention. In addition, components with the same effect described in the above embodiments can be replaced with each other.
Claims
1. A method performed by a user equipment UE, comprising: 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 received in the RRC inactive state, start receiving the MBS multicast session in the RRC inactive state.
2. The method according to claim 1, wherein: If the following conditions are met, the UE is triggered to start the RRC connection recovery process: The PagingRecordList field is not included in the paging message or any ue-Identity included in the paging message does not match the UE identity assigned by the upper layer, and The UE has joined one or more MBS multicast sessions indicated by the TMGI contained in the first field of the paging message, and there is at least one MBS multicast session that is not indicated by the second field contained in the paging message as being received in the RRC inactive state; The first field is a TMGI list, and the second field contains an indication identifier corresponding one-to-one to the TMGI contained in the first field, which is used to indicate whether the MBS multicast session indicated by the corresponding TMGI in the first field can be received in an RRC inactive state.
3. The method according to claim 1, wherein: If the following conditions are met, the UE is triggered to start the RRC connection recovery process: For each PagingRecord field contained in the paging message, the ue-Identity contained in the PagingRecord field matches the fullI-RNTI stored in the UE.
4. 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 3.
Citation Information
Patent Citations
Communication method, device and system
CN114071376A
Broadcast multicast service transmission method and device and storage medium
CN115443667A
Information receiving method and device, information sending method and device, and storage medium
CN115884375A
MBS data processing method and device
WO2022086109A1
