CN117835461A - Method performed by user equipment and user equipment - Google Patents

Abstract

The invention provides a method executed by user equipment and the user equipment, wherein the method comprises the following steps: receiving a first indication identifier associated with each point-to-multipoint PTM configuration contained in a paging message from a base station; comparing the value of the first indication identifier with a locally stored value corresponding to the first indication identifier of the UE; and under the condition that the comparison results are different, the UE initiates an RRC connection recovery process to update the PTM configuration or acquire the updated PTM configuration.

Description

Method performed by user equipment and user equipment

Technical Field

The present invention relates to the field of wireless communication technology, and more specifically, to a method performed by a user equipment and the user equipment.

Background

A research project SI (see in particular SP-190625) on the improvement of 5G multicast broadcast service architecture has been approved. One of the goals of this SI (referred to as goal a) is to support generic MBS services in 5GS, and examples of applications that may benefit from this feature include, but are not limited to, public security, V2X applications, transparent IPv4/IPv6 multicast transmissions, IPTV, wireless software transmissions, group communications, and internet of things applications. Accordingly, on the third generation partnership project (3rd Generaion Partnership Project:3GPP) RAN#86, it is proposed that a work item of NR multicast and broadcast service (NR MBS) (see non-patent document: RP-193248:New WID:NR Multicast and Broadcast Service) be approved. The work item is intended to provide support for target a in the RAN. The objectives of this work project have been met and specific descriptions of related schemes are found in related 3GPP release 17 technical documents, such as TS38.300-h10, TS38.331-h10, TS38.321-h10, etc. In the 3GPP RAN#94 concert, an NR broadcast multicast work item named enhanced is approved (see non-patent document: RP-213568:New WID:Enhancements of NR Multicast and Broadcast Services) for further enhancement of MBS broadcast multicast of release 17. One of the goals of the work item is for the user equipment supporting the RRC inactive state to receive multicast traffic.

The present invention discusses the problems associated with RAN achieving support for user equipment in RRC inactive state to receive multicast services.

Disclosure of Invention

The invention aims to provide a method executed by user equipment and the user equipment.

A method performed by a user equipment according to the first aspect of the invention comprises: receiving a first indication identifier associated with each point-to-multipoint PTM configuration contained in a paging message from a base station; comparing the value of the first indication identifier with a locally stored value corresponding to the first indication identifier of the UE; and under the condition that the comparison results are different, the UE initiates an RRC connection recovery process to update the PTM configuration or acquire the updated PTM configuration.

According to the method of the first aspect of the present invention, the first indication identifier is a version number list carried in the paging message, elements in the version number list correspond one-to-one to temporary mobile group identifiers TMGIs in a paging group list, representing a current version of the PTM configuration of the multicast session to which the TMGIs correspond; or the first indication identifier is a temporary mobile group identifier TMGI and a version number list corresponding to the TMGI carried in the paging message, and each element in the version number list is the TMGI and a version number corresponding to the TMGI, and represents a current version of the PTM configuration of the multicast session corresponding to the TMGI.

According to the method of the first aspect of the present invention, in the case that the PTM configuration of the one or more multicast sessions configured for RRC inactive state reception is updated, the UE further needs to satisfy the following condition to initiate the resume RRC connection request procedure: the received paging message does not contain that the multicast session which is added by the UE but is not configured to be receivable in the RRC inactive state is activated; and/or the UE identifications contained in the paging record PagingRecord field in the received paging message are not matched with the UE identifications distributed by the upper layer of the UE.

A method performed by a user equipment according to the second aspect of the invention comprises: receiving a second indication identifier corresponding to the multicast session with changed point-to-multipoint PTM configuration, which is contained in the paging message from the base station; determining whether a prohibit timer defined for each multicast session or its corresponding PTM configuration is running; and under the condition that the forbidden timer is not operated, the UE initiates an RRC connection recovery process to update the PTM configuration.

According to the method of the second aspect of the present invention, in case the UE receives the PTM configuration or updated PTM configuration from a base station, the corresponding prohibit timer is started; or in case the UE initiates an RRC connection recovery procedure for updating the PTM configuration of one or more multicast sessions, starting the corresponding prohibit timer.

According to the method of the second aspect of the present invention, the second indication identifier corresponds to a certain bit in a bitmap carried in the paging message, and the bit in the bitmap corresponds to a temporary mobile group identifier TMGI in a paging group list one-to-one; or said second indication identifier is a temporary mobile group identity TMGI list for indicating multicast and broadcast service MBS multicast sessions in which said PTM configuration is changed.

According to the method of the first or second aspect of the present invention, in the case that the reception of the paging message from a base station collides with the reception of the multicast session, the UE receives a third indication identifier carried in an RRC reset message or an RRC release message by the base station, the third indication identifier being used to indicate whether the UE receives the paging message or the multicast session when the collision occurs.

According to the method of the first or second aspect of the present invention, in case the reception of the paging message from a base station collides with the reception of the multicast session, it is predefined whether the UE receives the paging message or the multicast session; or predefining that the paging message and the multicast session are always transmitted in the same cell.

According to the method of the first or second aspect of the present invention, in a case where the reception of the paging message from a base station collides with the reception of the multicast session, when the UE is in an RRC connected state, the UE receives a fourth indication flag from the base station, the fourth indication flag being used to indicate whether the UE preferentially receives the multicast session or the paging message.

The user equipment according to the third aspect of the present invention comprises: a processor; and a memory storing instructions; wherein the instructions, when executed by the processor, perform the method according to any one of the first or second aspects.

Effects of the invention

According to the invention, the UE can be prevented from unnecessarily initiating the RRC connection recovery process, thereby avoiding unnecessary signaling overhead. According to the present invention, when the conflict of receiving paging and receiving MBS multicast session occurs, whether the UE in RRC inactive state preferentially receives the multicast session and the base station keeps consistent understanding.

Drawings

The foregoing and other features of the invention will become more apparent from the following detailed description, taken in conjunction with the accompanying drawings in which:

fig. 1 (a) - (c) are schematic diagrams showing specific configurations of radio bearers for receiving MBS services according to the present invention.

Fig. 2 is a schematic diagram showing the basic procedure of the method performed by the user equipment of embodiment 1 of the present invention.

Fig. 3 is a schematic diagram showing the basic procedure of the method performed by the user equipment of embodiment 2 of the present invention.

Fig. 4 is a block diagram illustrating a user equipment according to an embodiment of the present invention.

Detailed Description

The invention is described in detail below with reference to the drawings and the detailed description. It should be noted that the present invention should not be limited to the specific embodiments described below. In addition, for the sake of brevity, detailed descriptions of well-known techniques, which are not directly related to the present invention, are omitted to prevent confusion of the understanding of the present invention.

The following describes some terms related to the present invention, and specific meanings of the terms may be found in 3GPP related documents, such as TS38.300, TS38.321, TS38.323, TS38.331, etc. In addition, the embodiment of the invention is not limited to broadcast/multicast service, and can be applied to other application scenes.

UE: user Equipment, user Equipment.

RRC: radio Resource Control, radio resource control.

Rrc_connected: and an RRC connected state.

Rrc_inactive: and the RRC is inactive.

Rrc_idle: and RRC idle state.

RAN: radio Access Network, radio access network.

NR: new RAT, new radio access technology.

MBS: multicast/broadcast service.

PDCP: packet Data Convergence Protocol, packet data convergence protocol.

RLC: radio Link Control, radio link control.

SDU: service Data Unit, service data units. The data packet received or delivered from or to the upper layer by this layer is called an SDU.

PDU: protocol Data Unit, protocol data unit. The data packet received or submitted by the layer from or to the lower layer is called a PDU. For example, the PDCP data PDU is a data packet obtained by adding a PDCP header to a PDCP SDU.

RB: radio Bearer.

MRB: the MBS radio bearer, i.e. one radio bearer configured for MBS transmission (A radio bearer that is configured for MBS delivery).

TMGI: temporary Mobile Group Identity, temporary mobile group identity, for identifying an MBS session.

RNTI: radio Network Temporary Identifier, wireless network temporary identity.

PTM: point to Multipoint, point-to-multipoint, a delivery (delivery) mode of MBS services. In PTM delivery, the base station sends an MBS packet to a group UE (gNB delivers a single copy ofMBS data packets to a set ofUEs). For example, the base station adopts the group common physical downlink control channel PDCCH scrambled by the G-RNTI to schedule the group common physical downlink shared channel PDSCH scrambled by the same G-RNTI.

PTP: point-to-Point, a delivery method of MBS service. In PTP delivery, the RAN node delivers multiple copies of MBS data packets to each UE (gNB individually delivers separate copies of MBS data packets to each UEs independently) individually, i.e. the base station schedules the UE-specific PDCCH scrambled with the UE-specific RNTI for the UE-specific PDSCH scrambled with the same UE-specific RNTI.

G-RNTI: group RNTI, scheduling and transmission of one or more MBS multicast services for scrambling a PTM (Used to scramble the scheduling and transmission of PTM for one or more MBS multicast services).

In the present invention, the network, the base station and the RAN are used interchangeably, and the network may be a long term evolution LTE network, an NR network, an enhanced long term evolution LTE network, or other networks defined in a later evolution version of 3 GPP.

Currently, the NR MBS service includes MBS broadcasting (or MBS broadcasting session) and MBS multicasting (or MBS multicasting session). The MBS broadcast service facing low service quality QoS provides a downlink MBS transmission mode only, so that the UE in an RRC connection state, an RRC idle state and an RRC non-activated state can receive the MBS service, and the UE receives MBS configuration broadcasted by the MBS through a broadcast control channel MCCH. MBS multicasting requires the UE to establish an RRC connection with the base station, which then configures the UE with dedicated RRC signaling (also referred to as RRC messages), and radio bearers MRBs receiving these MBS services (or MBS multicast sessions) may also be configured by the base station with dedicated RRC signaling (e.g. RRC reconfiguration messages) for the UE, only the UE in RRC connected state and configured with MRBs may receive the corresponding MBS services. MBS sessions include MBS broadcast sessions and MBS multicast sessions, which are MBS multicast sessions in the embodiments of the present disclosure, as not specifically described.

Fig. 1 (a) to Cc) are schematic diagrams showing specific configurations of radio bearers receiving an MBS multicast session. The radio bearer may be an MRB configured with only PTM transmissions, as shown in fig. 1 (a), or a separate MRB (split MRB) of PTM and PTP, as shown in fig. 1 (b), or an MRB configured with only PTP transmissions, as shown in fig. 1 (c). Note that (a) - (c) of fig. 1 only show PDCP entities and RLC entities corresponding to bearers and relationships between the two. In the downlink direction, PDCP PDUs encapsulated by the PDCP entity are delivered to the RLC entity.

In the existing NR MBS, when one MBS multicast session is activated by a core network or a base station has MBS multicast session data to be transmitted, a network supporting the MBS notifies a UE in an RRC idle state or an RRC inactive state through a group notification mechanism. Upon receiving the group notification, the UE that has joined the MBS multicast session reconnects to the network to receive the corresponding MBS multicast session. The group notification uses P-RNTI addressing (the group notification is addressed with P-RNTI on PDCCH) on the physical downlink control channel PDCCH, the UE monitors the Paging (Paging) channel. The paging message for group notification contains an 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 UEs alone.

The network initiates the Paging procedure by transmitting a Paging message at the Paging occasion (Paging occasion) of the UE. One paging message may address multiple UEs. The paging message may include a pagerecord list field (indicating an identification list of the paged UE) containing a pagerecord field (indicating an identification of the paged UE) for each UE and/or a pagegroupvist field (indicating an identification TMGI list of the MBS multicast session) containing one or more TMGIs to page the UE for a particular MBS multicast session. Wherein the paging record field contains a user UE Identity field, and possibly an accessType field for indicating whether the paging message is generated by a PDU session accessed by a non-3 gpp. The value of the UE-Identity field may be ng-5G-S-TMSI or a fuse-RNTI, where the ng-5G-S-TMSI contains 5G-S-TMSI (5G S-temporary mobile subscription identifier) is a temporary UE Identity provided by 5GC (5G core network) to uniquely identify the UE (terminal) within the tracking area (tracking area). The fulll i-RNTI is an identity allocated by the base station for the UE in the RRCRelease message for suspending the RRC connection.

The UE performs at least one of the following operations upon receiving a paging (paging) message from the network:

I. if the UE is in an RRC inactive state and the UE-Identity contained in the paging message contained in the paging record field matches (match) with the fulll i-RNTI stored by the UE, initiating an RRC connection recovery procedure (RRC connection resumption procedure); otherwise, if the UE-Identity contained in the paging message PagingRecord field matches the UE Identity (i.e., 5G-S-TMSI) allocated (or indicated) by the upper layer (e.g., NAS layer), forwarding (forward) the UE-Identity and the accessType (if present) to the upper layer, and the UE performs the operation of entering the RRC idle state. The operations include at least: resetting the medium access control MAC entity, deleting the UE non-active access layer AS (Access Stratum) context (if present), indicating to the upper layer that the RRC connection was released and the release reason.

For each TMGI contained in the PagingGroupList field of the paging message, if the UE has joined (join) the MBS session indicated by the TMGI, the TMGI is forwarded to the upper layer. For the UE in the RRC idle state, the upper layer can determine whether to trigger establishment of RRC connection after receiving the TMGI; for the UE in the RRC inactive state, the upper layer may prepare to receive the corresponding MBS session after receiving the TMGI.

If the UE is in an RRC inactive state and the UE has joined one or more MBS sessions indicated by TMGIs of a PagingGroupList field contained in a paging message, and none of the ue_Identitycontained in the PagingRecord field in the paging message matches an upper layer allocated UE Identity, an RRC connection recovery procedure is initiated.

It should be noted that the purpose of the RRC connection restoration procedure is to restore a suspended RRC connection, including restoring SRBs, DRBs, and multicast MRBs, or performing a RAN-based notification area RNA update, etc. The RRC release message RRCRelease is used to command release of one RRC connection or suspension of one RRC connection.

The 3GPP has reached to support the UE in the RRC inactive state to receive the MBS multicast session, and for the UE configured with the MBS multicast session that can be received in the RRC inactive state, when the PTM configuration information corresponding to the MBS multicast session is changed (e.g., the configuration information of the corresponding MRB is changed or the MBS session is deactivated, etc.), the base station may indicate which PTM configurations of the multicast session are changed through the paging message, and the UE initiates the RRC connection recovery procedure to obtain the updated PTM configuration (or update PTM configuration) when the UE receives the paging message including the indication indicating that the PTM configuration corresponding to the MBS multicast session to which the UE has joined is updated. Upon receiving a request message rrcresemerequest or rrcresemerequest 1 from the UE to restore the RRC connection, the base station may configure the updated PTM configuration to the UE through a RRCRelease message. If the UE initiates the RRC connection recovery procedure only to obtain the updated PTM configuration (or to update the PTM configuration), the UE may enter the RRC inactive state after obtaining the updated PTM configuration. Since the paging message indicating the multicast session update may be repeatedly sent a plurality of times, the UE having obtained the updated PTM configuration may receive the repeatedly sent paging message, which will cause the UE to initiate the RRC connection recovery procedure again to update the PTM configuration. This will increase UE power consumption, cause unnecessary signaling overhead, waste radio resources. How to avoid that a UE that has obtained the latest PTM configuration initiates the RRC connection recovery procedure only for the purpose of updating the PTM configuration is a problem to be solved.

The following provides examples to address this problem.

Example 1

A first indication identifier is set or associated for each PTM configuration or multicast session, which may be used to indicate that the corresponding PTM configuration has been changed or updated. The first indicator may be referred to as a version number, and its value may be an integer, and when the PTM configuration (or a parameter related to the PTM configuration) changes, the value of the indicator also changes correspondingly, for example, when the PTM configuration is updated each time, the value of the corresponding indicator increases by 1.

Fig. 2 shows a schematic diagram of the basic procedure of the method performed by the user equipment of embodiment 1 of the present invention.

Specifically, as shown in fig. 2, if the base station configures one or more multicast sessions for the UE in the RRC inactive state, when the base station changes the PTM configuration corresponding to at least one multicast session configured for the UE, the base station sends a paging message, and carries, in the paging message, a first indication identifier associated with the multicast session whose PTM configuration is changed and/or a TMGI of the multicast session whose PTM configuration is changed (or a first indication identifier associated with the TMGI of the multicast session whose PTM configuration is changed and/or a PTM configuration of the multicast session), so as to notify the UE in the RRC inactive state that the PTM configuration of the multicast session configured for the reception in the RRC inactive state is updated. After receiving the first indication identifier, the UE in the RRC inactive state compares the value of the first indication identifier with a locally stored value of a corresponding first indication identifier in step S102 (the UE may only compare the value of the first indication identifier associated with MBS multicast sessions configured to be received in the RRC inactive state with the locally stored value), and if different, initiates an RRC connection recovery procedure in step S103 (i.e. the UE considers that the PTM configuration of the corresponding multicast session has changed or needs to be updated) to obtain an updated PTM configuration (or to update the PTM configuration); in step S104, if the same, the UE ignores the first indication identifier, i.e. does not initiate an RRC connection restoration procedure for the purpose of updating the PTM configuration or considers that the PTM configuration of its corresponding multicast session has not changed or does not need to be updated.

Preferably, in step S102, if the UE has joined an MBS multicast session but does not have a locally saved PTM configuration for the multicast session, the UE performs an RRC connection recovery procedure to obtain the PTM configuration for the corresponding MBS multicast session. Alternatively, in step S102, if the UE has joined an MBS multicast session but does not have a locally saved PTM configuration for the multicast session, the UE does not perform the RRC connection recovery procedure (i.e., the UE does not acquire the PTM configuration for the corresponding MBS multicast session). In other words, the UE performs step 102 only for MBS multicast sessions that have joined and are configured to be receivable in the RRC inactive state.

In the present disclosure, the UE initiating the RRC connection recovery procedure includes the UE transmitting an RRC recovery request rrcresemerequest or rrcresemerequest 1 message to the base station. Optionally, the RRC recovery request message carries a TMGI of the multicast session for which the PTM configuration needs to be updated.

An example implementation of the first indication identifier is described below:

the first indication identifier may be a version number list carried in the paging message, where elements in the list correspond to TMGIs in the paginggrouplst one-to-one, and indicate a current version of a PTM configuration of the multicast session to which the TMGIs correspond.

The first indication identifier may also be a list of TMGIs and corresponding version numbers thereof carried in the paging message, where each element in the list is a TMGI and a corresponding version number thereof, indicating a current PTM configuration version of the multicast session corresponding to the TMGI. When the PTM configuration of a multicast session changes, the TMGI of the multicast session and the version number thereof are contained in a paging message to inform the UE. For this implementation, in step 102, comparing the first indication identifier with the locally-saved value refers to comparing the version number corresponding to the TMGI carried in the paging message with the locally-saved version number of the TMGI.

In addition, in the embodiments of the present disclosure, in order to avoid that the UE in the RRC inactive state initiates the RRC connection restoration request procedure multiple times because different conditions are satisfied, it may be provided that when the PTM configuration of one or more MBS sessions that the UE is configured to receive in the RRC inactive state is updated, in addition to satisfying other conditions defined in the embodiments, it is also required that a multicast session that does not include that the UE has joined but is not configured to be receivable in the RRC inactive state is activated in the received paging message, and/or that none of the ue_identity included in the paging record field in the received paging message matches the UE identifier allocated by the UE upper layer, the UE initiates the RRC connection restoration request procedure.

The PTM configuration according to the embodiments of the present disclosure is a configuration of a multicast session received in an RRC inactive state.

In addition, the first indication identifier (or version number) may also be included in the RRC release message or the RRC reconfiguration message, and is used to indicate version information of the current PTM configuration when configuring the PTM configuration corresponding to the multicast session. It may be provided that the PTM configuration is associated with a first indication identifier or version number only if the PTM configuration corresponding MBS multicast session is configured to be receivable in an RRC inactive state.

Example 2

A prohibit timer is defined, one prohibit timer being maintained per multicast session or its corresponding PTM configuration. When the timer is running, the UE does not initiate an RRC connection recovery procedure for the purpose of updating the PTM configuration even if receiving a PTM configuration update indication (denoted as a second indication identifier), in other words, when the UE receives a PTM configuration update indication, if the corresponding prohibit timer is not running, an RRC connection recovery procedure is initiated for the purpose of updating the PTM configuration. It should be noted that, the multicast session corresponding to the PTM configuration is a multicast session configured by the base station for the UE and received in the RRC inactive state; the second indication identifier is used for indicating that the corresponding configuration of the PTM configured as the MBS multicast session receivable in the RRC inactive state is changed.

Fig. 3 shows a schematic diagram of the basic procedure of the method performed by the user equipment of embodiment 2 of the present invention.

Specifically, as shown in fig. 3, in step S201, the UE receives a paging message from the base station, where the paging message includes a second indication identifier corresponding to the multicast session with the PTM configuration changed, and in step S202, if the corresponding prohibit timer is not running, then: in step S203, the UE initiates an RRC connection recovery procedure for the purpose of updating the PTM configuration.

Preferably, when the UE receives the PTM configuration (i.e. updated PTM configuration) from the base station, the corresponding prohibit timer is started or restarted. Alternatively, when the UE initiates an RRC connection recovery procedure for updating the PTM configuration of one or more multicast sessions, the corresponding prohibit timer is started or restarted.

Preferably, when the UE reselects to (or resides in) a cell for which the locally stored PTM configuration of a certain multicast session is no longer valid, the corresponding prohibit timer for that multicast session is stopped (this is only performed when the timer is running).

The implementation of the second indication identifier is described below.

The second indication identifier corresponding to each multicast session may correspond to a bit in a bitmap carried in the paging message (the second indication identifier may also be defined as a bitmap, where each bit in the bitmap corresponds to one MBS multicast session), and the bits in the bitmap correspond to TMGIs in a PagingGroupList one to one. If the bit corresponding to the TMGI is set to 1, the PTM configuration of the multicast session indicated by the TMGI is updated, and if the bit corresponding to the TMGI is set to 0, the PTM configuration of the multicast session indicated by the TMGI is not updated, and vice versa. It may be provided that the paging message will only carry the bitmap if it carries a PagingGroupList.

The second indicator may also be a TMGI list, denoted as mbsudatelnidicationlist, for indicating MBS multicast sessions with changed PTM configuration, and if the TMGI is included in the list, it indicates that the corresponding PTM configuration is updated.

It should be noted that the effective area of the PTM configuration may be part of the PTM configuration, and may be configured by the base station in an RRC reconfiguration message or an RRC release message for the UE or as part of the PTM configuration for the UE. The base station may configure a corresponding one of the cell lists for one or a group of MBS multicast sessions, consider the corresponding PTM configuration to be valid when the UE moves (i.e., cell selection or reselection) between the cells specified by the list, and consider the corresponding PTM configuration to be no longer valid when the UE moves to a cell other than the cell specified by the cell list. The cell list may contain only one cell. Furthermore, if the PTM configuration of the UE is valid only in the cell in which the UE resides, the base station may not configure the cell list for the UE. The base station may also indicate to the UE that the effective area of the PTM configuration is the same as the RAN-based notification area RNA.

Furthermore, when the base station configures the UE to receive one or more multicast sessions in the RRC inactive state, when the UE in the RRC inactive state needs to receive the paging message (or system information) and the multicast session at the same time, but the UE does not have the capability to receive the paging message (or system information) and the multicast session at the same time, in other words, the paging message (or system information) and the multicast session are received in conflict, for example, because the paging message (or system information) and the multicast session are transmitted on different cells, how the UE handles the conflict is a problem to be solved.

The embodiments provided below solve this problem such that when a collision of receiving paging and receiving MBS multicast sessions occurs, it is understood that whether the UE in the RRC inactive state preferentially receives multicast sessions and the base station remain consistent, and if the UE preferentially receives multicast sessions, the base station may transmit paging messages multiple times when a collision of receiving paging and receiving multicast sessions occurs, so that the UE may receive paging messages after receiving MBS multicast sessions.

Example 3

The base station configures for the UE whether the UE receives the paging message (or system information) or the multicast session when the paging message (or system information) and the multicast session reception collide. For example, the base station carries a third indication identifier in the RRC reconfiguration message or the RRC release RRCRelease message, so as to indicate whether the UE receives the paging message (or the system information) or the multicast session when the paging message (or the system information) and the multicast session are in conflict.

In this embodiment, the base station configures the UE when the UE is in RRC connected state or the UE wants to restore RRC connection (for example, the base station configures the UE in an rrcrescenedequest message when receiving an rrcrescenedequest or rrcrescenedequest 1 message from the UE), and the base station may configure the UE through an RRC reconfiguration message rrcrescendo or an RRC release message rrcrescenedese.

Example 4

When a collision of paging message (or system information) and multicast session reception occurs, it is predefined whether the UE receives the paging message (or system information) or the multicast session.

Alternatively, the predefined paging message (or system information) and the multicast session are always transmitted in the same cell. A multicast session configured for e.g. a UE in RRC inactive state is always transmitted on the initial part of the bandwidth.

Example 5

When the UE is in the RRC connected state, the base station is indicated to preferentially receive information (denoted as a fourth indication identifier) related to the multicast session or the paging message (or the system information) when the multicast session it receives in the RRC inactive state collides with the reception of the paging message (or the system information). The fourth indication identifier may be carried in a UE assistance information message, or may be carried in an MBSInterestIndication message, or may redefine a message to carry the information. The fourth indication identity may be used to indicate whether the UE prefers to receive the multicast session over the paging message (or system information). It may be provided that this field is carried or present (e.g. value true) if the multicast session is preferentially received by the UE, otherwise this field is not carried or not present.

It should be noted that, one multicast session and one PTM configuration are in one-to-one correspondence, and the indication identifier or the prohibit timer associated with the multicast session is the indication identifier or the prohibit timer associated with the PTM configuration, which may be used alternatively.

Fig. 4 is a schematic block diagram of a user equipment UE according to the present invention. As shown in fig. 4, the user equipment UE80 comprises a processor 801 and a memory 802. The processor 801 may include, for example, a microprocessor, microcontroller, embedded processor, or the like. The memory 802 may include, for example, volatile memory (such as random access memory RAM), a Hard Disk Drive (HDD), non-volatile memory (such as flash memory), or other memory. The memory 802 has stored thereon program instructions. Which, when executed by the processor 801, may perform the above-described methods of the present invention, described in detail by a user equipment.

In addition, the computer-executable instructions or programs running on the apparatus according to the present invention may be programs that cause a computer to implement the functions of the embodiments of the present invention by controlling a Central Processing Unit (CPU). The program or information processed by the program may be temporarily stored in a volatile store such as a random access memory RAM, a Hard Disk Drive (HDD), a nonvolatile store such as a flash memory, or other memory system.

Computer-executable instructions or programs for implementing the functions of the embodiments of the present invention may be recorded on a computer-readable storage medium. The corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs. The term "computer system" as used herein may be a computer system embedded in the device and may include an operating system or hardware (e.g., peripheral devices). The "computer-readable storage medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium storing a program dynamically at a short time, or any other recording medium readable by a computer.

The various features or functional modules of the apparatus used in the embodiments described above may be implemented or performed by circuitry (e.g., single-chip or multi-chip integrated circuits). Circuits designed to perform the functions described herein 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 device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The circuit may be a digital circuit or an analog circuit. Where new integrated circuit technologies are presented as an alternative to 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.

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 may be used as terminal devices or communication devices such as AV devices, kitchen devices, cleaning devices, air conditioners, office devices, vending machines, and other home appliances, etc.

As 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 embodiment, and the present invention also includes any design modification without departing from the gist 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 the different embodiments are also included in the technical scope of the present invention. Further, the components having the same effects described in the above embodiments may be replaced with each other.

Claims (10)

1. A method performed by a user equipment, UE, comprising:

receiving a first indication identifier associated with each point-to-multipoint PTM configuration contained in a paging message from a base station;

comparing the value of the first indication identifier with a locally stored value corresponding to the first indication identifier of the UE;

and under the condition that the comparison results are different, the UE initiates an RRC connection recovery process to update the PTM configuration or acquire the updated PTM configuration.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the first indication identifier is a version number list carried in the paging message, elements in the version number list are in one-to-one correspondence with Temporary Mobile Group Identifiers (TMGIs) in a paging group list (PagingGroupList), and represent the current version of the PTM configuration of the multicast session corresponding to the TMGIs; or alternatively

The first indication identifier is a temporary mobile group identifier TMGI and a version number list corresponding to the temporary mobile group identifier TMGI carried in the paging message, and each element in the version number list is the TMGI and a version number corresponding to the TMGI, and represents a current version of the PTM configuration of the multicast session corresponding to the TMGI.

3. The method of claim 1, wherein the step of determining the position of the substrate comprises,

in the case that the PTM configuration of one or more multicast sessions received in the inactive state is updated, the UE needs to further satisfy the following conditions to initiate a RRC connection restoration request procedure, where the conditions are:

the received paging message does not contain that the multicast session which is added by the UE but is not configured to be receivable in the RRC inactive state is activated; and/or

And the UE identifications contained in the paging record PagingRecord field in the received paging message are not matched with the UE identifications distributed by the upper layer of the UE.

4. A method performed by a user equipment, UE, comprising:

receiving a second indication identifier corresponding to the multicast session with changed point-to-multipoint PTM configuration, which is contained in the paging message from the base station;

determining whether a prohibit timer defined for each multicast session or its corresponding PTM configuration is running;

and under the condition that the forbidden timer is not operated, the UE initiates an RRC connection recovery process to update the PTM configuration.

5. The method of claim 4, wherein the step of determining the position of the first electrode is performed,

starting the corresponding prohibit timer under the condition that the UE receives the PTM configuration or updated PTM configuration from a base station; or (b)

In case the UE initiates an RRC connection recovery procedure for updating the PTM configuration of one or more multicast sessions, starting the corresponding prohibit timer.

6. The method of claim 4, wherein the step of determining the position of the first electrode is performed,

the second indication identifier corresponds to a certain bit in a bitmap carried in the paging message, and the bit in the bitmap corresponds to a temporary mobile group identifier TMGI in a paging group list one to one; or alternatively

The second indication identifier is a temporary mobile group identifier TMGI list for indicating multicast and broadcast service MBS multicast sessions in which the PTM configuration is changed.

7. The method according to any one of claim 1 to 6, wherein,

in case the reception of the paging message from the base station collides with the reception of the multicast session, the UE receives the third indication identity carried in the base station through an RRC reset message or an RRC release message,

the third indication identity is used to indicate whether the UE receives the paging message or the multicast session when the collision occurs.

8. The method according to any one of claim 1 to 6, wherein,

in case the reception of the paging message from the base station collides with the reception of the multicast session,

predefining whether the UE receives the paging message or a multicast session; or alternatively

The paging message and the multicast session are predefined to be always transmitted in the same cell.

9. The method according to any one of claim 1 to 6, wherein,

in case the reception of the paging message from the base station collides with the reception of the multicast session,

when the UE is in an RRC connected state, the UE receives a fourth indication identity from the base station,

the fourth indication identifier is used to indicate whether the UE preferentially receives the multicast session or the paging message.

10. A user equipment, comprising:

a processor; and

a memory storing instructions;

wherein the instructions, when executed by the processor, perform the method according to any one of claims 1 to 9.