Execution method of user equipment and user equipment

Abstract

The invention provides an execution method of user equipment and the user equipment. According to the execution method of the UE, the UE is configured or allowed to receive an MBS multicast session in an RRCINACTIVE state, and the execution method comprises the following steps that the UE triggers an RRC connection recovery process and determines an access type and / or an access identifier corresponding to the access attempt due to the fact that the MBS multicast session receives or obtains PTM configuration; the UE executes a unified access control (UAC) process by using the determined access type and / or access identifier, and when the access attempt is prohibited, the UE starts T390 corresponding to the access type, and sets the value of the indication identifier as a value representing that the MBS multicast receiving request to be processed exists; during T390 operation, the UE decides whether to set the value of the indication mark as a value indicating that the MBS multicast receiving request to be processed does not exist; and when the T390 expires, under the condition that the upper layer does not request the RRC to recover the RRC connection, and under the condition that the value of the indication identifier indicates that the value of the MBS multicast receiving request to be processed exists, the UE starts an RRC connection recovery process.

Description

Technical Field

[0001] The present invention relates to the field of wireless communication technology, and more specifically, to an execution method of 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 improvements has been approved. One of the goals of this SI (called goal A) is to support generic MBS services in 5GS. Use cases that can benefit from this feature include (but are not limited to) public safety, V2X applications, transparent IPv4 / IPv6 multicast transmission, IPTV, wireless software transmission, group communication and IoT applications. Accordingly, at the 3rd Generation Partnership Project (3GPP) RAN#86 plenary meeting, a work item on NR multicast and broadcast service (NR MBS) was proposed and approved (see non-patent literature: RP-193248: New WID: NR Multicast and Broadcast Service). This work item aims to provide support for goal A in RAN. The goals of this work item have been basically achieved, and the specific description of the relevant solutions can be found in 3GPP Release 17 technical documents, such as TS38.300-h50, TS38.331-h50, TS38.321-h50, etc. At the 3GPP RAN#94 plenary meeting, a work item named 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 the MBS Multicast and Broadcast Services 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] The present invention provides an execution method of UE and UE, which are used to solve the related problems involved in RAN supporting user equipment to receive MBS multicast service / session in RRC inactive state.

[0005] According to one aspect of the present invention, there is provided an execution method of a UE, wherein the UE is configured or allowed to receive an MBS multicast session in an RRC_INACTIVE state, and the execution method comprises the following steps: the UE triggers an RRC connection recovery process due to receiving or acquiring a PTM configuration for the MBS multicast session and determines an access type and / or access identifier corresponding to the access attempt; the UE uses the determined access type and / or access identifier to perform a unified access control UAC process, and when the access attempt is prohibited, the UE starts a T390 corresponding to the access type, and sets the value of an indication identifier to a value indicating that there is a pending MBS multicast reception request; during the operation of the T390, the UE decides whether to set the value of the indication flag to a value indicating that there is no pending MBS multicast reception request; and when the T390 expires, when the upper layer does not request the RRC to restore the RRC connection, when the value of the indication identifier indicates that there is a pending MBS multicast reception request, the UE starts the RRC connection recovery process.

[0006] In the execution method of the above-mentioned UE, preferably, during the operation of T390, the UE decides whether to set the value of the indication flag to a value indicating that there is no pending MBS multicast reception request based on the reception quality of the MBS multicast session data, the status of all MBS multicast sessions that the UE has joined, and whether the UE has obtained or has the PTM configuration of all activated MBS multicast sessions.

[0007] In the above-mentioned UE execution method, it is preferred that, when the RRC connection recovery process is triggered by receiving or obtaining relevant information of the PTM configuration of the MBS multicast session, an access type corresponding to receiving or obtaining relevant information of the PTM configuration of the MBS multicast session is selected, and the UAC process is executed according to the selected access type and the applicable access identifier.

[0008] In the execution method of the above-mentioned UE, preferably, the indication identifier is a first indication identifier, the MBS multicast reception request is a first type of MBS multicast reception request, and when the access attempt is prohibited, when the RRC connection recovery process is triggered by the reception quality of the MBS multicast session data being less than or equal to the configured threshold value, the RRC connection recovery process is terminated after the first indication identifier is set to a value indicating that there is a pending first type of MBS multicast reception request.

[0009] In the execution method of the above-mentioned UE, preferably, the indication identifier is a second indication identifier, the MBS multicast reception request is a second type of MBS multicast reception request, and when the access attempt is prohibited, when the RRC connection recovery process is triggered by obtaining the PTM configuration, the RRC connection recovery process is ended after the second indication identifier is set to a value indicating that there is a pending second type of MBS multicast reception request.

[0010] In the above-mentioned UE execution method, preferably, the indicator identifier is a third indicator identifier, and when the access attempt is prohibited, the RRC connection recovery process is ended after the third indicator identifier is set to a value indicating that there is a pending MBS multicast reception request.

[0011] In the execution method of the above-mentioned UE, it is preferred that, during the operation of the T390, in any of the following circumstances, the value of the first indication identifier is set to a value indicating that there is no pending first-type MBS multicast reception request: the reception quality of the MBS multicast session data is greater than a threshold value; and all MBS multicast sessions to which the UE has joined are in a deactivated state or are deactivated.

[0012] In the execution method of the above-mentioned UE, it is preferred that, during the operation of the T390, in any of the following cases, the value of the second indication identifier is set to a value indicating that there is no pending second-type MBS multicast reception request: the UE has obtained or has the PTM configuration of all activated MBS multicast sessions; and all MBS multicast sessions to which the UE has joined are in a deactivated state or are deactivated.

[0013] According to another aspect of the present invention, a UE is provided, comprising: a processor; and a memory storing instructions; wherein the instructions, when executed by the processor, execute the UE execution method according to any of the above aspects.

[0014] Effects of the Invention

[0015] According to the UE execution method and UE involved in the present invention, it is possible to solve the related problems involved in RAN supporting user equipment to receive MBS multicast services / sessions in an RRC inactive state. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0017] Figure 1 It is a flowchart showing the execution method of the UE involved in the present invention.

[0018] Figure 2 It is a block diagram showing a brief structure of the UE involved in the present invention. DETAILED DESCRIPTION

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

[0020] 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-h50, TS38.321-h50, TS38.323-h50, TS38.331-h50, 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.

[0021] UE: User Equipment.

[0022] RRC: Radio Resource Control.

[0023] RRC_CONNECTED: RRC connected state.

[0024] RRC_INACTIVE: RRC inactive state.

[0025] RRC_IDLE: RRC idle state.

[0026] RAN: Radio Access Network.

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

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

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

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

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

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

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

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

[0035] 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. UEs use 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.

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

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

[0038] SCell: Secondary Cell. For UEs configured with carrier aggregation, SCell is a cell that provides additional radio resources on top of a special cell. For dual connectivity operation, the term special cell refers to the PCell of an MCG or the PSCell of an SCG, otherwise the term special cell refers to the PCell. For dual connectivity operation, the PSCell is the secondary cell group SCG cell in which the UE performs random access when performing a synchronous reconfiguration procedure.

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

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

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

[0042] MCCH:MBS Control Channel, MBS control channel, is a PTM downlink channel used for transmitting MBS broadcast or MBS multicast control informationassociated to one or several MTCH(s)from the network to the UE. MCCH includes broadcast MCCH and multicast MCCH.

[0043] The RRC recovery request message RRCResumeRequest or RRCResumeRequest1 is used to request the recovery of a suspended RRC connection or to perform a RAN-based notification area RNA update. When the UE initiates an RRC connection recovery request, if SIB1 contains the useFullResumeID field, the RRCResumeRequest1 message is used and the resumeIdentity field in the RRCResumeRequest1 message is set to the fullI-RNTI stored by the UE, otherwise RRCResumeRequest is used and the resumeIdentity field in the RRCResumeRequest message is set to the stored shortI-RNTI. The RRC release message RRCRelease is used to command the release of an RRC connection or to suspend an RRC connection. The RRC reconfiguration message RRCReconfiguration is used to command the modification of the RRC connection. The RRC recovery message RRCResume is used to recover a suspended RRC connection. In the present disclosure, the useFullResumeID field indicates the recovery identifier and recovery request message used. When the field is included in SIB1, fullI-RNTI and RRCResumeRequest1 message are used. When the field is not included in SIB1, shortI-RNTI and RRCResumeRequest message are used. ShortI-RNTI uses fewer bits than I-RNTI-Value to identify the suspended UE context of a UE in an RRC inactive state. The RRC recovery process (i.e., the RRC connection recovery process) is used to restore the suspended RRC connection, including restoring SRB(s), DRB(s) and multicast MRB(s), or performing RNA updates, or implementing MBS multicast reception requests, or initiating small data transmission SDT in the RRC_INACTIVE state, etc. During the RRC recovery process, the UE sends an RRC recovery request message to the base station, and may receive an RRC recovery message RRCResume or an RRC establishment message RRCSetup or an RRC release message RRCRelease or an RRC rejection message RRCReject from the base station.

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

[0045] At present, NR MBS services include MBS broadcast (also called MBS broadcast session or broadcast MBS or MBS broadcast service or MBS broadcast service) and MBS multicast (also called MBS multicast session or multicast MBS or MBS multicast service 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, before receiving MBS multicast services (i.e., MBS multicast sessions), the UE needs to establish an RRC connection with the base station. The base station then configures resources for the UE to receive MBS multicast services through dedicated RRC signaling (also called RRC messages, such as RRC reconfiguration messages). The MBS radio bearer MRB for receiving these MBS multicast services is also configured by the base station for the UE through dedicated RRC signaling. Only UEs that are in an RRC connected state and have configured MRBs can receive the corresponding MBS multicast services.

[0046] In Release 17, it is not supported for UE to receive MBS multicast session in RRC inactive state. Therefore, when an MBS multicast session is activated by the core network or the base station has MBS multicast session data to send, the network supporting MBS multicast notifies the UE in RRC idle state or RRC inactive state through the group notification mechanism. Upon receiving the group notification, the UE that has joined the MBS multicast session or is interested in the MBS multicast session establishes or restores the RRC connection with the network to receive the corresponding MBS multicast session. The group notification is addressed with P-RNTI on the physical downlink control channel PDCCH, and the UE monitors the paging channel. The paging message used for group notification contains the MBS session identifier TMGI, which is used to page all UEs that have joined the relevant MBS multicast session and are in RRC idle state or RRC inactive state. In other words, the base station does not page the UE individually (for the purpose of the UE receiving the MBS multicast session).

[0047] In version 18, UE is supported to receive MBS multicast sessions in RRC inactive state. For MBS multicast sessions received in RRC inactive state, the base station can provide or configure PTM configuration information (also called configuration information of MBS multicast session or PTM configuration of MBS multicast session) for UE to receive the MBS multicast session through dedicated RRC signaling (e.g., RRCRelease message) or through multicast MBS control channel MCCH (i.e., multicast MCCH). The information required to obtain multicast MCCH (or multicast MCCH configuration) can be configured for UE through dedicated RRC signaling or system information block (denoted as SIBx), that is, SIBx contains the information required to obtain the multicast MCCH configuration of MBS multicast received in RRC inactive state. The PTM configuration information may include the configuration information of the MRB corresponding to the MBS multicast session and / or the identifier TMGI of the MBS multicast session and its corresponding G-RNTI / G-CS-RNTI and / or DRX and other configuration information fields. The multicast MCCH is a PTM downlink channel used for transmitting control information of MBS multicast session associated to one or several MTCH(s)from the network to the UE in RRC_INACTIVE state. For an MBS multicast session received in the RRC_INACTIVE state, the MBS multicast session being in an active state or being activated in the embodiment of the present disclosure means that the MBS multicast session is in progress or about to start or the UE starts to receive the MBS multicast session. The network can indicate to the UE that the MBS multicast is activated or data transmission is resumed through RRC signaling (e.g., RRC release message) or through a paging message (e.g., including the TMGI of the MBS multicast session in a paging message indicates that the MBS multicast session is activated or data transmission is resumed), and the UE starts to receive the MBS multicast session after receiving the indication. The MBS multicast being activated in the embodiment of the present disclosure is also applicable to the case of resuming data transmission, which will not be described in detail below. In the embodiment of the present disclosure, the MBS multicast session being in an inactive state or being deactivated means that the MBS multicast session has ended or data transmission has been suspended or the UE has stopped receiving the MBS multicast session.The network may notify the UE through a multicast MCCH message (for example, if the PTM configuration of the MBS multicast session does not appear in the multicast MCCH message, it indicates that the MBS multicast session is deactivated, and an indicator identifier may be associated with each MBS multicast session to explicitly indicate that the MBS multicast session is deactivated) or through a physical downlink control channel PDCCH (or downlink control information DCI) that schedules the multicast MCCH (or multicast MCCH message), for example, using 1 bit in the DCI of the PDCCH to indicate that the MBS multicast is deactivated or data transmission is suspended. The UE stops receiving the MBS multicast session after receiving the indication. The UE stopping receiving the MBS multicast session may be that the UE does not detect the G-RNTI or G-CS-RNTI corresponding to the MBS multicast session.

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

[0049] For an MBS multicast session configured to be received in an RRC inactive state, when the MBS multicast session is activated, if the MBS multicast session is configured and / or allowed to be received in an RRC_INACTIVE state and / or the UE has a (valid) PTM configuration for the MBS multicast session, the MBS multicast session can be directly received without establishing an RRC connection with the base station. However, if the MBS multicast session is not configured and / or allowed to be received in an RRC_INACTIVE state, or the UE does not have a PTM configuration (i.e., a valid PTM configuration) for the MBS multicast session, or when the UE in an RRC inactive state performs cell reselection and reselects to another cell, resulting in the UE's current configuration of the PTM configuration of the MBS multicast session received in an RRC inactive state being no longer valid, in these cases, the UE is triggered to perform an RRC recovery process in order to obtain relevant information about the MBS multicast session or its PTM configuration. In addition, the network may configure a threshold value of MBS multicast session data reception quality for the UE capable of receiving MBS multicast sessions in the RRC_INACTIVE state, and when the MBS multicast session data reception quality is lower than the threshold value, the UE initiates the RRC recovery process.

[0050] Based on the different purposes of establishing or restoring an RRC connection between the UE and the network or the different events that trigger the UE to establish or restore an RRC connection between the UE and the network, multiple access types (Access Category) are defined. When initiating (initiating) the process of restoring an RRC connection, the UE determines the access type and / or access identity (Access Identities) according to the triggering event, and performs a unified access control (UAC) process according to the determined access type and / or access identity. The purpose of this process is to perform an access prohibition check on the access attempt associated with the determined access category and one or more access identities (the event that triggers the UE to initiate the RRC recovery process is an access attempt). The UE maintains an access prohibition timer T390 for each access type. When performing an access prohibition check on the access type corresponding to a certain access attempt, if the access attempt is prohibited, the timer T390 corresponding to the access type is started. T390 is stopped when the UE performs cell selection or reselection, performs relay selection or reselection, enters the RRC connected state, receives an RRC reconfiguration message containing the synchronization reconfigurationWithSync field, changes the primary cell PCell in the RRC connected state, receives a MobilityFromNRCommand message, or receives an RRC release message. When T390 expires or stops, the operations performed when barring alleviation are performed. For example, when the T390 corresponding to a certain access type expires, the barring of the corresponding access type is considered to be alleviated. If the UE has an access attempt of the corresponding access type at this time, the UE will perform the corresponding access attempt. For example, if the corresponding T390 of access type 2 or 8 expires (that is, the barring is eliminated) and the UE has a pending radio notification area RNA update, the RRC recovery process is initiated. Among them, the MobilityFromNRCommand message is used to command switching from NR to E-UTRA / EPC, E-UTRA / 5GC or UTRA-FDD. It should be noted that during the UAC process, the UE first determines whether T390 corresponding to the access type is running. If T390 is running, the access attempt is considered to be prohibited. At this time, the UAC process ends and the UE does not need to perform an access prohibition check. For access attempts whose access types are not 2 and 0, if T390 corresponding to the access type is not running, the UE also determines whether T302 is running. If T302 is running, the access attempt is considered to be prohibited. At this time, the UAC process ends and the UE does not need to perform an access prohibition check.T302 is started when an RRC rejection message RRCReject or RRC release message RRCRelease is received, and is stopped when entering the RRC connected state or RRC idle state or cell reselection or receiving an RRC rejection message. When T302 expires, the upper layer is notified to cancel the prohibition. The RRC rejection message is used to reject an RRC connection establishment or RRC connection recovery.

[0051] When the reception quality of the MBS multicast session data is lower than (or less than or equal to) the configured threshold value, the UE triggers the RRC recovery process (i.e., access attempt) and determines the access type and / or access identifier corresponding to this access attempt. The determined access type and / or access identifier is used to perform the access prohibition check specified in the UAC process. If the access attempt is prohibited, the UE will start T390 corresponding to the access type and set the value of the variable first indication identifier, for example, its value is set to true. The first indication identifier is used to indicate whether there is a pending first-class MBS multicast reception request. It can be specified that the variable is of Boolean type. If the variable value is set to true or "true" (recorded as the first value), it indicates that there is a pending first-class MBS multicast reception request.

[0052] During the operation of T390 corresponding to the access type or when T390 expires, the MBS multicast session data reception quality changes and is no longer lower than (or higher than, or greater than or equal to) the configured threshold value or all MBS multicast sessions (i.e., all MBS multicast sessions that the UE has joined) are indicated as deactivated or data transmission is suspended. When T390 expires, if the upper layer does not request RRC to restore the RRC connection (this condition is optional), the UE checks the value of the first indication identifier (e.g., checks whether its value is true), and if its value is used to indicate that there is a waiting first-class MBS multicast reception request (e.g., if the value of the first indication identifier is true), the RRC recovery process is restarted. However, at this time, since the MBS multicast session data reception quality is no longer lower than (or higher than, or greater than or equal to) the configured threshold value or all MBS multicast sessions are indicated as deactivated (i.e., there is no activated MBS multicast session) or data transmission is suspended, the UE continues to perform the RRC recovery process, which will cause unnecessary energy consumption and signaling overhead.

[0053] It should be noted that, in the present disclosure, the MBS multicast session data reception quality may be the quality of the MBS multicast session transmission channel when the MBS multicast session is activated, or the quality of the channel for transmitting the MBS multicast session, or the reception quality of the MBS multicast session data when the MBS multicast session is activated. The threshold is a parameter that can be used to reflect the channel quality (i.e., the channel quality for transmitting the MBS multicast session), such as RSRP, RSRQ, SINR, or packet loss number, which can be used to determine the value related to the MBS multicast session data reception quality.

[0054] Similarly, when the UE receives an activation indication or a data transmission resumption indication for an MBS multicast session (or receives an activation indication or a data transmission resumption indication for an MBS multicast session, and the MBS multicast session is allowed and / or configured to be received in the RRCINACTIVE state), but the PTM configuration of the MBS session is not available (or the UE does not have a valid PTM configuration for the MBS multicast session), the RRC recovery process is triggered and the access type and / or access identifier is determined. When using the determined access type and / or access identifier to perform the access prohibition check specified in the UAC process, if the access attempt is prohibited, the UE will start T390 corresponding to the access type and set the value of the variable second indication identifier, for example, to true. The second indication identifier is used to indicate whether there is a pending second-type MBS multicast reception request. It can be specified that the variable is of Boolean type, and if the variable value is set to true or "true" (recorded as the first value), it indicates that there is a pending second-type MBS multicast reception request.

[0055] During the operation of T390 corresponding to the access type or when T390 expires, the UE obtains the PTM configuration of the MBS multicast session indicated as being activated (i.e., a valid PTM configuration) or all MBS multicast sessions (i.e., all MBS multicast sessions to which the UE has joined) are indicated as being deactivated. When T390 expires, the UE checks the value of the second indication identifier (e.g., checks whether the value of the second indication identifier is true), and if its value is used to indicate that there is a waiting second-type MBS multicast reception request (e.g., if the value of the second indication identifier is true), the RRC recovery process is initiated. However, at this time, since the UE has obtained the PTM configuration of the MBS multicast session indicated as being activated or all MBS multicast sessions (i.e., all MBS multicast sessions to which the UE has joined) are indicated as being deactivated, the UE continuing to perform the RRC recovery process will result in unnecessary energy consumption and signaling overhead.

[0056] It should be noted that, in the present disclosure, the indication of activating the MBS multicast session can be implemented by including the TMGI of the MBS multicast session in a paging message. When the UE receives the paging message from the base station, it is considered that the MBS multicast session indicated by the TMGI is activated or starts to receive the MBS multicast session indicated by the TMGI. The configuration of the MBS multicast session to be able to or allowed to be received in the RRC INACTIVE state can be configured or indicated by an RRC release message or a paging message. In one implementation, if the paging message carries the field inactiveReceptionAllowed, it is considered that the MBS multicast session is configured to be able to or allowed to be received in the RRC_INACTIVE state; in another implementation, if the MBS multicast session is configured to be able to be received in the RRC_INACTIVE state in the RRC release message and the paging message contains the inactiveReceptionAllowed field corresponding to the MBS multicast session, it is considered that the MBS multicast session is configured to be able to or allowed to be received in the RRC_INACTIVE state. Among them, the field inactiveReceptionAllowed indicates whether the UE with a valid PTM configuration (i.e., the valid PTM configuration of the MBS multicast session indicated by the TMGI) for the TMGI contained in the pagingGroupList (the UE has joined the MBS multicast session indicated by the TMGI) stays in RRC_INACTIVE to receive the corresponding MBS multicast session, and the pagingGroupList is a field included in the paging message, and the pagingGroupList is used to include an inactiveReceptionAllowed field.

[0057] It should be noted that, in the embodiment of the present disclosure, the first indication identifier and the second indication identifier may be the same or different identifiers, and accordingly, if the first indication identifier and the second indication identifier are the same identifier, the first type MBS multicast reception request and the second type MBS multicast reception request are also the same. If the first indication identifier and the second indication identifier are the same identifier, it is recorded as the third indication identifier, and accordingly, if the first type MBS multicast reception request and the second type MBS multicast reception request are the same, it is recorded as the third type MBS multicast reception request. In addition, only the second indication identifier may be supported, that is, only when the RRC recovery process is a valid PTM configuration of the MBS multicast session that the UE has not activated and / or the MBS multicast session is configured or allowed to be received in the RRC_INACTIVE state, the second indication identifier is set to a value corresponding to the second type MBS multicast reception request that is waiting (for example, if the value of the second indication identifier is set to true). When the reception quality of the MBS multicast session is lower than the configured threshold, the UE does not set the first indication identifier.

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

[0059] First, refer to Figure 1 The steps of triggering the RRC recovery process and starting the RRC recovery process of the present invention are described.

[0060] Step 1: The UE triggers the RRC connection recovery process (i.e., access attempt) due to MBS multicast session reception or acquisition of PTM configuration and determines the access type and / or access identifier corresponding to the access attempt;

[0061] Step 2: The UE uses the determined access type and / or access identifier to perform a unified access control UAC process. If the access attempt is prohibited, the UE starts T390 corresponding to the access type and sets the value of the indication identifier (the first indication identifier, the second indication identifier, or the third indication identifier) ​​to true (i.e., set to a value indicating that there is a pending MBS multicast reception request);

[0062] Step 3: During T390 operation, the UE decides whether to set the value of the indication flag to false (i.e., to a value indicating that there is no pending MBS multicast reception request);

[0063] Step 4: When T390 expires, if the upper layer (e.g., NAS layer) does not request RRC to resume the RRC connection, and the value of the indication flag is set to true (i.e., set to a value indicating that there is a pending MBS multicast reception request), the UE initiates the RRC connection resumption procedure.

[0064] In step 3, the UE decides whether to set the value of the indication flag to false (i.e., to a value indicating that there is no pending MBS multicast reception request) based on the reception quality of the MBS multicast session data, and / or the status of all MBS multicast sessions that the UE has joined, and / or whether the UE has obtained or has the PTM configuration of all activated MBS multicast sessions.

[0065] The inventive point of the present invention is that when the RRC connection recovery process is triggered, when the value of the indication identifier is set to true in step 2, during the operation of T390 in step 3, the UE decides whether to set the value of the indication identifier to false, and in step 4, determines whether to start the RRC connection recovery process based on the value of the indication identifier.

[0066] The following are detailed embodiments 1 to 3 of the present invention. Among them, embodiment 1 details the basis for judging whether to start the RRC connection recovery process when the prohibition of the access type corresponding to the RRC recovery process triggered by the MBS multicast session receiving or obtaining the PTM configuration is removed, embodiment 2 details the case of setting the first indication identifier, the second indication identifier, and the third indication identifier to false, and embodiment 3 details the operations involved in setting the indication identifier (the first indication identifier and / or the second indication identifier and / or the third indication identifier).

[0067] Example 1

[0068] For a UE in the RRC_INACTIVE state, if the UE is configured and / or allowed to receive an MBS multicast session in the RRC_INACTIVE state (optional), if the access type corresponding to the RRC recovery procedure triggered for the purpose of receiving the MBS multicast session (for example, the reception quality of the MBS multicast session is lower than the configured threshold) or obtaining the PTM configuration (for example, the MBS multicast session is activated but the UE does not have the corresponding valid PTM configuration) (for example, the RRC recovery procedure triggered by the MBS multicast session reception or the acquisition of the PTM configuration corresponds to the access type 8 or the access type 2) is prohibited from being eliminated (that is, T302 or the corresponding T390 expires), the UE performs at least one of the following operations:

[0069] Operation 1-1: This operation describes the case where the first indication flag is supported. If the upper layer (e.g., NAS layer) does not request RRC to restore the RRC connection, and / or the first indication flag is set to a value corresponding to the existence of a first type of MBS multicast reception request (e.g., the first indication flag is set to true), and / or if the reception quality of the MBS multicast session data is lower than (or less than or equal to) the configured threshold value (this condition can only be executed when the threshold value is configured), and / or if there is an MBS multicast session indicated as activated (i.e., there is an MBS multicast session to which the UE has joined and is in an activated state or has not been deactivated), the UE initiates the RRC connection recovery process.

[0070] Operation 1-2: This operation describes the case where the second indication flag is supported. If the upper layer (e.g., NAS layer) does not request RRC to restore the RRC connection, and / or the second indication flag is set to a value corresponding to the second type of MBS multicast reception request (e.g., the second indication flag is set to true), and / or if the reception quality of the MBS multicast session data is lower than (or less than or equal to) the configured threshold value (this condition can only be executed when the threshold value is configured), and / or if there is an MBS multicast session indicated as activated (i.e., there is an MBS multicast session that the UE has joined and is in an activated state or has not been deactivated), and / or there is a valid PTM configuration without at least one MBS multicast session (the MBS multicast session is an active MBS multicast session that is configured or allowed to be received in the RRC_INACTIVE state), the UE initiates the RRC connection recovery procedure.

[0071] Operation 1-3: This operation describes the case where the third indication flag is supported. If the upper layer (e.g., NAS layer) does not request RRC to restore the RRC connection, and / or the third indication flag is set to a value corresponding to the third type of MBS multicast reception request (e.g., the third indication flag is set to true), and / or if the reception quality of the MBS multicast session data is lower than (or less than or equal to) the configured threshold value (this condition can only be executed when the threshold value is configured), and / or if there is an MBS multicast session indicated as activated (i.e., there is an MBS multicast session that the UE has joined and is in an activated state or has not been deactivated), and / or there is a valid PTM configuration without at least one MBS multicast session (the MBS multicast session is an active MBS multicast session that is configured or allowed to be received in the RRC_INACTIVE state), the UE initiates the RRC connection recovery procedure.

[0072] Example 2

[0073] This embodiment describes operations related to the UE canceling a pending first-type MBS multicast reception request and / or a pending second-type MBS multicast reception request.

[0074] For a UE in the RRC INACTIVE state, if the UE is configured or allowed to receive an MBS multicast session in the RRC INACTIVE state or for a UE that has joined an MBS multicast session (these conditions are optional), the UE performs at least one of the following operations:

[0075] Operation 2-1: If the reception quality of the MBS multicast session data is not lower than (or greater than) the configured threshold value (this condition can only be executed when the threshold value is configured), the value of the first indication identifier is set to a value corresponding to no pending first-type MBS multicast reception request, for example, the value of the first indication identifier is set to false.

[0076] Operation 2-2: If all MBS multicast sessions to which the UE has joined are in a deactivated state or are deactivated, the value of the first indicator is set to a value corresponding to a non-existence of a pending first-type MBS multicast reception request (it may be specified that this operation is performed only when the first indicator exists and its value is true), for example, the value of the first indicator is set to false (even if the reception quality of the MBS multicast session data is lower than the configured threshold value), and / or the value of the second indicator is set to a value corresponding to a non-existence of a pending second-type MBS multicast reception request, for example, the value of the second indicator is set to false, and / or the value of the third indicator is set to a value corresponding to a non-existence of a pending third-type MBS multicast reception request, for example, the value of the third indicator is set to false. In the disclosed embodiment, the value of the first indicator is taken as true to indicate that the reception quality of the MBS multicast session data is lower than the configured threshold value, and other values ​​may also be used to indicate this, and the same is true for the second indicator and the third indicator, which will not be described in detail.

[0077] Operation 2-3: If the UE obtains or has the PTM configuration of all activated MBS multicast sessions, the value of the second indication flag is set to a value corresponding to no pending second-type MBS multicast reception request, for example, the value of the second indication flag is set to false.

[0078] Example 3

[0079] This embodiment describes operations involved in setting the first indication identifier and / or the second indication identifier when the UE starts the RRC recovery process.

[0080] In this embodiment, a new access type and / or access identifier different from the RNA update can be defined for requesting to restore the RRC connection for receiving an MBS multicast session (for example, the reception quality of the MBS multicast session is lower than the configured threshold) or obtaining information related to its PTM configuration (for example, the MBS multicast session is activated but the UE does not have a corresponding valid PTM configuration). The access type and / or access identifier different from the RNA update can also be set to the same access type and / or access identifier as the RNA update for requesting to restore the RRC connection for the purpose of obtaining the MBS multicast or its PTM configuration received in the RRC inactive state.

[0081] Upon initiation of the RRC connection resume procedure, the UE performs the following operations:

[0082] In step 301, if the restoration of the RRC connection is triggered by responding to NG-RAN paging, "0" is selected as the access type, and the UAC process (including access prohibition check) is performed using the selected access type and one or more access identifiers provided by the upper layer (e.g., NAS). If the access attempt is prohibited, the RRC connection restoration process ends.

[0083] Otherwise (i.e., the condition that the RRC connection restoration is triggered by responding to NG-RAN paging is not satisfied), execute step 302.

[0084] In step 302, if the restoration of the RRC connection is triggered by an upper layer (e.g., NAS), the following operations are further performed:

[0085] If the upper layer provides an access type and one or more access identifiers, the UAC process is performed using the access type and access identifier provided by the upper layer. If the access attempt is prohibited, the RRC connection recovery process ends.

[0086] If the resumption occurs after release with redirect with mpsPriorityIndication, set resumeCause to mps-PriorityAccess; otherwise, set resumeCause according to the information received from the upper layer. The field mpsPriorityIndication is used to indicate that for a new connection redirected to NR, the UE can set the establishment cause to mps-PriorityAccess.

[0087] Otherwise (that is, the restoration of the RRC connection is not triggered by responding to the NG-RAN paging and the restoration of the RRC connection is not triggered by the upper layer), execute step 303.

[0088] In step 303, if the restoration of the RRC connection is triggered by receiving an MBS multicast session (for example, the reception quality of the MBS multicast session is lower than the configured threshold) or obtaining relevant information of its PTM configuration (for example, the MBS multicast session is activated but the UE does not have a corresponding valid PTM configuration), the following operations are performed:

[0089] Select the access type corresponding to receiving or obtaining PTM configuration related information for the MBS multicast session, and perform the UAC process according to the selected access type and applicable access identifier. If the access attempt is prohibited, the RRC connection recovery process ends. Optionally, if the access attempt is prohibited, perform the following operations:

[0090] If the RRC connection restoration is triggered by the reception quality of the MBS multicast session data being lower than (or less than or equal to) a configured threshold value, the RRC connection restoration process ends after the first indication flag is set to true or "true".

[0091] Otherwise (the RRC connection restoration is triggered by obtaining the PTM configuration), the RRC connection restoration process ends after the second indication flag is set to true or "true".

[0092] [Variation of Embodiment 3]

[0093] The modified example of Example 3 is obtained by replacing step 303 of Example 3 with the following step 303a:

[0094] In step 303, if the restoration of the RRC connection is triggered by receiving the MBS multicast session or obtaining relevant information of its PTM configuration, the following operations are performed:

[0095] Select the access type corresponding to receiving or obtaining PTM configuration related information for the MBS multicast session, and perform the UAC process according to the selected access type and applicable access identifier. If the access attempt is prohibited, the RRC connection recovery process ends. Optionally, if the access attempt is prohibited, perform the following operations:

[0096] After the third indication flag is set to true or "true", the RRC connection recovery process ends.

[0097] The embodiments of the present invention are described in detail above. The user equipment of the present invention is described below.

[0098] Figure 2 1 is a simplified structural diagram of a user equipment UE according to the present invention. Figure 2As shown, the user equipment UE200 includes 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 memories, etc. The memory 202 stores program instructions. When the instructions are executed by the processor 201, the above method performed by the user equipment described in detail in the present invention may be executed.

[0099] The method and the related equipment of the present disclosure have been described above in conjunction with the preferred embodiments. It can be understood by those skilled in the art that the method shown above is only exemplary, and the embodiments described above can be combined with each other without contradiction. The method of the present invention is not limited to the steps and sequence shown above.

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

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

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

[0103] The computer executable instructions or programs running on the device according to the present invention can be programs that enable a computer to implement the functions of the embodiments of the present invention by controlling a 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.

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

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

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

[0107] 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 for executing a UE, wherein the UE is configured or allowed to receive an MBS multicast session in an RRC_INACTIVE state, the method comprising the following steps: The UE triggers an RRC connection recovery process due to receiving or acquiring a PTM configuration for an MBS multicast session and determines an access type and / or access identifier corresponding to the access attempt; The UE uses the determined access type and / or access identifier to perform a unified access control UAC process, and when the access attempt is prohibited, the UE starts T390 corresponding to the access type and sets the value of the indication identifier to a value indicating that there is a pending MBS multicast reception request; During the execution of T390, the UE determines whether to set the value of the indication flag to a value indicating that there is no pending MBS multicast reception request; as well as When T390 expires, in the case that the upper layer does not request RRC to restore the RRC connection, and in the case that the value of the indication identifier is set to a value indicating that there is a pending MBS multicast reception request, the UE initiates the RRC connection recovery process.

2. The execution method of the UE according to claim 1, wherein: During the operation of T390, the UE decides whether to set the value of the indication flag to a value indicating that there is no pending MBS multicast reception request based on the reception quality of the MBS multicast session data, the status of all MBS multicast sessions that the UE has joined, and whether the UE has obtained or has the PTM configuration of all activated MBS multicast sessions.

3. The execution method of the UE according to claim 1 or 2, wherein: In the case where the RRC connection recovery process is triggered by receiving or obtaining relevant information of the PTM configuration of the MBS multicast session, the access type corresponding to the receiving or obtaining relevant information of the PTM configuration of the MBS multicast session is selected, and the UAC process is performed according to the selected access type and the applicable access identifier.

4. The execution method of the UE according to claim 3, wherein: The indicator mark is a first indicator mark, The MBS multicast reception request is a first type of MBS multicast reception request, When the access attempt is prohibited, when the RRC connection recovery process is triggered by the reception quality of the MBS multicast session data being less than or equal to the configured threshold value, the RRC connection recovery process is terminated after the first indication flag is set to a value indicating that there is a pending first type MBS multicast reception request.

5. The execution method of UE according to claim 3, wherein: The indicator mark is a second indicator mark, The MBS multicast reception request is a second type of MBS multicast reception request, When the access attempt is prohibited, in the case where the RRC connection recovery process is triggered by obtaining the PTM configuration, the RRC connection recovery process is terminated after the second indication flag is set to a value indicating that there is a pending second-type MBS multicast reception request.

6. The execution method of the UE according to claim 3, wherein: The indicator mark is a third indicator mark, When the access attempt is prohibited, the RRC connection recovery process is ended after the third indication flag is set to a value indicating that there is a pending MBS multicast reception request.

7. The execution method of UE according to claim 4, wherein: During the execution of T390, in any of the following cases, the value of the first indication identifier is set to a value indicating that there is no pending first-type MBS multicast reception request: The reception quality of the MBS multicast session data is greater than a threshold value; and All MBS multicast sessions that the UE has joined are in a deactivated state or are deactivated.

8. The execution method of UE according to claim 5, wherein: During the execution of T390, in any of the following cases, the value of the second indication identifier is set to a value indicating that there is no pending second-type MBS multicast reception request: The UE obtains or has the PTM configuration of all activated MBS multicast sessions; and All MBS multicast sessions that the UE has joined are in a deactivated state or are deactivated.

9. A UE, comprising: processor; as well as A memory storing instructions; Wherein, when the instructions are executed by the processor, the execution method of the UE according to any one of claims 1 to 8 is executed.

Images