WO2024067602A1 - Procédé éxécuté par un équipement utilisateur, et équipement utilisateur - Google Patents

Procédé éxécuté par un équipement utilisateur, et équipement utilisateur Download PDF

Info

Publication number
WO2024067602A1
WO2024067602A1 PCT/CN2023/121616 CN2023121616W WO2024067602A1 WO 2024067602 A1 WO2024067602 A1 WO 2024067602A1 CN 2023121616 W CN2023121616 W CN 2023121616W WO 2024067602 A1 WO2024067602 A1 WO 2024067602A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast session
paging message
ptm configuration
base station
rrc
Prior art date
Application number
PCT/CN2023/121616
Other languages
English (en)
Chinese (zh)
Inventor
肖芳英
刘仁茂
Original Assignee
夏普株式会社
肖芳英
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 夏普株式会社, 肖芳英 filed Critical 夏普株式会社
Publication of WO2024067602A1 publication Critical patent/WO2024067602A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • the present invention relates to the technical field of wireless communications, and more particularly, to a method executed by a user equipment and the user equipment.
  • Enhanced NR Broadcast Multicast was approved (see non-patent literature: RP-213568: New WID: Enhancements of NR Multicast and Broadcast Services), which aims to further enhance the MBS broadcast multicast of Release 17.
  • RP-213568 New WID: Enhancements of NR Multicast and Broadcast Services
  • One of the goals of this work item is to support user equipment in RRC inactive state to receive multicast services.
  • the present invention discusses the related issues involved in RAN supporting RRC inactive state user equipment to receive multicast services.
  • the object of the present invention is to provide a method executed by a user equipment and the user equipment.
  • a method performed by a user equipment comprises: receiving a first indication identifier associated with each point-to-multipoint PTM configuration contained in a paging message from a base station; comparing a value of the first indication identifier with a value corresponding to the first indication identifier stored locally by the UE; and when the comparison result is different, the UE initiates an RRC connection recovery process, To update the PTM configuration or obtain the updated PTM configuration.
  • the first indicator is a version number list carried in the paging message, the elements in the version number list correspond one-to-one to the temporary mobile group identifier TMGI in the paging group list PagingGroupList, indicating the current version of the PTM configuration of the multicast session corresponding to the TMGI; or the first indicator is a temporary mobile group identifier TMGI carried in the paging message and its corresponding version number list, each element in the version number list is the TMGI and its corresponding version number, indicating the current version of the PTM configuration of the multicast session corresponding to the TMGI.
  • the UE when the PTM configuration of one or more multicast sessions configured to be received in the RRC inactive state is updated, the UE also needs to meet the following conditions to initiate the RRC connection recovery request process, which is: the received paging message does not contain the activation of a multicast session that the UE has joined but is not configured to be receivable in the RRC inactive state; and/or the UE identifier contained in the paging record PagingRecord field in the received paging message does not match the UE identifier assigned by the UE upper layer.
  • the method executed by the user equipment includes: receiving a second indication identifier corresponding to a multicast session in which a point-to-multipoint PTM configuration has been changed, contained in a paging message from a base station; determining whether a prohibition timer defined for each multicast session or its corresponding PTM configuration is running; and when it is determined that the prohibition timer is not running, the UE initiates an RRC connection recovery process to update the PTM configuration.
  • the corresponding prohibition timer when the UE receives the PTM configuration or the updated PTM configuration from the base station, the corresponding prohibition timer is started; or when the UE initiates the RRC connection recovery process to update the PTM configuration of one or more multicast sessions, the corresponding prohibition timer is started.
  • the second indication identifier corresponds to a bit in a bitmap carried in the paging message, and the bits in the bitmap correspond one-to-one to the temporary mobile group identifier TMGI in the paging group list PagingGroupList; or the second indication identifier is a temporary mobile group identifier TMGI list, which is used to indicate the multicast and broadcast service MBS multicast session in which the PTM configuration has changed.
  • the UE in the case where the reception of the paging message from the base station conflicts with the reception of the multicast session, the UE receives the paging message.
  • the base station carries a third indication identifier in an RRC reset message or an RRC release message, where the third indication identifier is used to indicate whether the UE receives the paging message or the multicast session when the conflict occurs.
  • the UE in the case that the reception of the paging message from the base station conflicts with the reception of the multicast session, it is predefined whether the UE receives the paging message or the multicast session; or it is predefined that the paging message and the multicast session are always transmitted in the same cell.
  • the UE when the reception of the paging message from the base station conflicts with the reception of the multicast session, when the UE is in an RRC connected state, the UE receives a fourth indication identifier from the base station, and the fourth indication identifier is used to indicate whether the UE prioritizes receiving the multicast session or the paging message.
  • a user equipment comprises: a processor; and a memory storing instructions; wherein the instructions, when executed by the processor, execute the method according to any one of the first aspect or the second aspect.
  • the present invention it is possible to avoid the UE from unnecessarily initiating the RRC connection recovery process, thereby avoiding unnecessary signaling overhead.
  • the UE in the RRC inactive state maintains a consistent understanding with the base station as to whether to receive the multicast session first.
  • FIG. 1 ( a ) to ( c ) are schematic diagrams showing specific configurations of a radio bearer for receiving an MBS service according to the present invention.
  • FIG2 is a schematic diagram showing a basic process of a method executed by a user equipment according to Embodiment 1 of the present invention.
  • FIG3 is a schematic diagram showing a basic process of a method executed by a user equipment according to Embodiment 2 of the present invention.
  • FIG. 4 is a block diagram showing a user equipment according to an embodiment of the present invention.
  • RRC Radio Resource Control, wireless resource control.
  • RRC_CONNECTED RRC connected state.
  • RRC_INACTIVE RRC inactive state.
  • RRC_IDLE RRC idle state.
  • RAN Radio Access Network, wireless access network.
  • New RAT new radio access technology.
  • MBS Multicast/Broadcast Services.
  • PDCP Packet Data Convergence Protocol, packet data convergence protocol.
  • RLC Radio Link Control, wireless link control.
  • SDU Service Data Unit. The data packet received by this layer from the upper layer or delivered to the upper layer is called SDU.
  • PDU Protocol Data Unit.
  • the data packet received by this layer from the lower layer or delivered to the lower layer is called PDU.
  • PDCP data PDU is the data packet obtained by adding PDCP header to PDCP SDU.
  • RB Radio Bearer, wireless bearer.
  • MRB MBS radio bearer, a radio bearer that is configured for MBS delivery.
  • TMGI Temporary Mobile Group Identity, used to identify One MBS session.
  • RNTI Radio Network Temporary Identifier, wireless network temporary identifier.
  • PTM Point to Multipoint, a delivery method for MBS services.
  • the gNB delivers a single copy of MBS data packets to a set of UEs.
  • the gNB uses the G-RNTI-scrambled group common physical downlink control channel PDCCH to schedule the same G-RNTI-scrambled group common physical downlink shared channel PDSCH.
  • PTP Point to Point, a delivery method for MBS services.
  • the RAN node delivers separate copies of multiple MBS data packets to each UE (gNB individually delivers separate copies of MBS data packets to each UEs independently), that is, the base station uses the UE-specific PDCCH scrambled by the UE-specific RNTI to schedule the UE-specific PDSCH scrambled by the same UE-specific RNTI.
  • G-RNTI Group RNTI, group RNTI, used to scramble the scheduling and transmission of PTM for one or more MBS multicast services.
  • 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.
  • NR MBS services include MBS broadcast (or MBS broadcast session) and MBS multicast (or MBS multicast session).
  • 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 services, and the UE receives the MBS configuration of the MBS broadcast through the broadcast control channel MCCH.
  • MBS multicast requires the UE to establish an RRC connection with the base station, and then the base station configures the UE through dedicated RRC signaling (also called RRC message), and the radio bearer MRB for receiving these MBS services (or MBS multicast sessions) can also be configured by the base station through dedicated RRC signaling (such as RRC reconfiguration message) for the UE. Only UEs in RRC connected state and configured with MRB can receive the corresponding MBS services.
  • MBS sessions include MBS broadcast sessions and MBS multicast sessions. If not specifically stated, the MBS session described in the embodiments of the present disclosure is an MBS multicast session.
  • FIG1 (a) to (c) show the specific configuration of the radio bearer receiving the MBS multicast session.
  • the wireless bearer may be an MRB configured with only PTM transmission (as shown in (a) of FIG. 1 ), or a split MRB configured with both PTM and PTP (as shown in (b) of FIG. 1 ), or an MRB configured with only PTP transmission (as shown in (c) of FIG. 1 ).
  • (a)-(c) of FIG. 1 only show the PDCP entity and RLC entity corresponding to the bearer and the relationship between the two. In the downlink direction, the PDCP PDU encapsulated by the PDCP entity is delivered to the RLC entity.
  • the network supporting MBS 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 notifies the UE in the RRC idle state or the RRC inactive state through the group notification mechanism.
  • the UE that has joined the MBS multicast session reconnects to 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 the RRC idle state or the RRC inactive state. In other words, the base station does not page the UE individually.
  • the network initiates the paging process by transmitting a paging message at the UE's paging occasion.
  • One paging message can address multiple UEs.
  • the paging message may include a pagingRecordList field (indicating a list of identities of the UEs to be paged) containing a pagingRecord field for each UE (indicating the identity of the UE to be paged) and/or a pagingGroupList field (indicating a list of TMGIs of the MBS multicast session's identity) containing one or more TMGIs to page the UE for a specific MBS multicast session.
  • the pagingRecord field includes a user UE identity ue-Identity field, and may also include an accessType field for indicating whether the paging message is generated by a PDU session accessed by non-3gpp.
  • the value of the ue-Identity field can be ng-5G-S-TMSI or fullI-RNTI, where ng-5G-S-TMSI contains 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier), which is a temporary UE identifier provided by the 5GC (5G Core Network) to uniquely identify the UE (terminal) within the tracking area.
  • the fullI-RNTI is the identifier assigned to the UE by the base station in the RRCRelease message used to suspend the RRC connection.
  • the UE When the UE receives a paging message from the network, it performs at least one of the following operations:
  • the RRC connection resumption procedure is initiated; otherwise, if the ue-Identity contained in the PagingRecord field contained in the paging message matches the UE identity (i.e., 5G-S-TMSI) assigned (or indicated) by the upper layer (e.g., NAS layer), the ue-Identity and accessType (if any) are forwarded to the upper layer, and the UE performs an operation to enter the RRC idle state.
  • the operation includes at least: resetting the media access control MAC entity, deleting the UE inactive access layer AS (Access Stratum) context (if any), and indicating to the upper layer that the RRC connection has been released and the reason for the release.
  • the TMGI For each TMGI contained in the PagingGroupList field of the paging message, if the UE has joined the MBS session indicated by the TMGI, the TMGI is forwarded to the upper layer.
  • the upper layer For a UE in the RRC idle state, the upper layer can determine whether to trigger the establishment of an RRC connection after receiving the TMGI; for a UE in the RRC inactive state, the upper layer can prepare to receive the corresponding MBS session after receiving the TMGI.
  • the RRC connection recovery process is initiated.
  • the purpose of the RRC connection recovery process is to recover a suspended RRC connection, including recovering SRB, DRB and multicast MRB or performing RAN-based notification area RNA update, etc.
  • the RRC release message RRCRelease is used to command the release of an RRC connection or to suspend an RRC connection.
  • 3GPP has reached an agreement to support UEs in RRC inactive state to receive MBS multicast sessions.
  • the base station can indicate through a paging message which multicast session's PTM configuration has changed.
  • the UE receives a paging message containing an indication that the PTM configuration corresponding to the MBS multicast session that the UE has joined has been updated, the UE Initiate an RRC connection recovery process to obtain an updated PTM configuration (or update the PTM configuration).
  • the base station may configure the updated PTM configuration to the UE through an RRCRelease message. If the UE initiates the RRC connection recovery process only to obtain an updated PTM configuration (or update the PTM configuration), after obtaining the updated PTM configuration, the UE may enter an RRC inactive state. Since the paging message indicating a multicast session update may be sent repeatedly multiple times, a UE that has obtained an updated PTM configuration may receive repeatedly sent paging messages, which will cause the UE to initiate an RRC connection recovery process again to update the PTM configuration. This will increase UE energy consumption, cause unnecessary signaling overhead, and waste radio resources. How to prevent a UE that has obtained the latest PTM configuration from initiating an RRC connection recovery process solely for the purpose of updating the PTM configuration is a problem that needs to be solved.
  • a first indicator is set or associated for each PTM configuration or multicast session, which can be used to indicate that the corresponding PTM configuration has changed or updated.
  • the first indicator can be called a version number, and its value can be an integer.
  • the value of the indicator also changes accordingly. For example, each time the PTM configuration is updated, the value of the corresponding indicator increases by 1.
  • FIG2 is a schematic diagram showing a basic process of a method executed by a user equipment according to Embodiment 1 of the present invention.
  • the base station configures the UE to receive one or more multicast sessions in the RRC inactive state
  • the base station sends a paging message and carries the multicast session identifier TMGI of the changed PTM configuration and/or the first indication identifier associated with the multicast session of the changed PTM configuration (or the TMGI of the multicast session of the changed PTM configuration and/or the first indication identifier associated with the PTM configuration of the multicast session) in the paging message to notify the UE in the RRC inactive state that the PTM configuration of the multicast session configured to receive in the RRC inactive state has been updated.
  • step S101 after receiving the first indication identifier, the UE in the RRC inactive state compares the value of the first indication identifier with the value of the corresponding first indication identifier stored locally in step S102 (the UE may only compare the PTM configuration of the multicast session configured to receive in the RRC inactive state).
  • the value of the first indicator associated with the multicast session is compared with the locally stored value), and in step S103, if they are different, the UE initiates an RRC connection recovery process (that is, the UE believes that the PTM configuration of the corresponding multicast session has changed or needs to be updated) to obtain the updated PTM configuration (or to update the PTM configuration); in step S104, if they are the same, the UE ignores the first indicator, that is, does not initiate the RRC connection recovery process for the purpose of updating the PTM configuration or believes that the PTM configuration of the corresponding multicast session has not changed or does not need to be updated.
  • step S102 if the UE has joined an MBS multicast session but the PTM configuration of the multicast session is not saved locally, the UE performs an RRC connection recovery process to obtain the PTM configuration of the corresponding MBS multicast session.
  • step S102 if the UE has joined an MBS multicast session but the PTM configuration of the multicast session is not saved locally, the UE does not perform the RRC connection recovery process (i.e., the UE does not obtain the PTM configuration of the corresponding MBS multicast session). In other words, the UE only performs step 102 for the MBS multicast session that it has joined and is configured to be receivable in the RRC inactive state.
  • the UE initiating the RRC connection recovery process includes the UE sending an RRC recovery request RRCResumeRequest or RRCResumeRequest1 message to the base station.
  • the RRC recovery request message carries the TMGI of the multicast session whose PTM configuration needs to be updated.
  • the first indication identifier may be a version number list carried in the paging message, and the elements in the list correspond one-to-one to the TMGI in the PagingGroupList, indicating the current version of the PTM configuration of the multicast session corresponding to the TMGI.
  • the first indicator may also be a list of TMGIs and their corresponding version numbers carried in a paging message, where each element in the list is a TMGI and its corresponding version number, indicating the current version of the PTM configuration of the multicast session corresponding to the TMGI.
  • the TMGI and its version number of the multicast session are included in the paging message to notify the UE.
  • the comparison of the first indicator with the locally stored value refers to comparing the version number corresponding to the TMGI carried in the paging message with the version number of the TMGI stored locally.
  • the UE in order to prevent the UE in the RRC inactive state from initiating the RRC connection recovery request process multiple times due to meeting different conditions, it can be specified that when the PTM configuration of one or more MBS sessions configured to be received by the UE in the RRC inactive state is updated, In addition to meeting other conditions defined in the embodiment, the UE initiates the RRC connection recovery request process only when the received paging message does not contain a multicast session that the UE has joined but is not configured to be receivable in the RRC inactive state and/or the ue_Identity contained in the PagingRecord field in the received paging message does not match the UE identifier assigned by the UE upper layer.
  • the PTM configuration described in the embodiment of the present disclosure is a configuration of a multicast session received in an RRC inactive state.
  • the first indicator (or version number) may also be included in the RRC release message or the RRC reconfiguration message, and is used to indicate the version information of the current PTM configuration when configuring the PTM configuration corresponding to the multicast session. It may be provided that the first indicator or version number is associated with the PTM configuration only when the MBS multicast session corresponding to the PTM configuration is configured to be receivable in the RRC inactive state.
  • An inhibit timer is defined, and each multicast session or its corresponding PTM configuration maintains an inhibit timer.
  • the timer is running, even if the UE receives a PTM configuration update indication (recorded as the second indication identifier), it does not initiate an RRC connection recovery process for the purpose of updating the PTM configuration.
  • the UE receives a PTM configuration update indication, if the corresponding inhibit timer is not running, an RRC connection recovery process is initiated for the purpose of updating the PTM configuration.
  • the multicast session corresponding to the PTM configuration is a multicast session configured by the base station for the UE to be received in the RRC inactive state; the second indication identifier is used to indicate that the PTM configuration of the corresponding MBS multicast session configured to be receivable in the RRC inactive state has changed.
  • FIG3 is a schematic diagram showing a basic process of a method executed by a user equipment according to Embodiment 2 of the present invention.
  • step S201 the UE receives a paging message from the base station, and the paging message includes a second indication identifier corresponding to the multicast session in which the PTM configuration has changed.
  • step S202 if the corresponding prohibition timer is not running, then: in step S203, the UE initiates an RRC connection recovery process for the purpose of updating the PTM configuration.
  • the corresponding prohibition timer is started or restarted.
  • the UE initiates an RRC connection recovery process to update the PTM configuration of one or more multicast sessions the corresponding prohibition timer is started or restarted. Disable the timer.
  • the prohibition timer corresponding to the multicast session is stopped (this operation is performed only when the timer is running).
  • the second indicator corresponding to each multicast session may correspond to a certain bit in a bitmap carried in the paging message (the second indicator may also be defined as a bitmap, each bit in the bitmap corresponds to an MBS multicast session), and the bits in the bitmap correspond one-to-one to the TMGI in the PagingGroupList. If the bit corresponding to the TMGI is set to 1, it indicates that the PTM configuration of the multicast session indicated by the TMGI is updated; if the bit corresponding to the TMGI is set to 0, it indicates that the PTM configuration of the multicast session indicated by the TMGI is not updated, and vice versa. It may be specified that the paging message carries the bitmap only when it carries the PagingGroupList.
  • the second indication identifier may also be a TMGI list, denoted as MBSUpdateInidcationlist, which is used to indicate the MBS multicast sessions whose PTM configurations have been changed. If the TMGI is included in the list, it indicates that the corresponding PTM configuration has been updated.
  • the valid area of the PTM configuration may be part of the PTM configuration, and may be configured by the base station for the UE in an RRC reconfiguration message or an RRC release message or as part of the PTM configuration.
  • the base station may configure a corresponding cell list for one or a group of MBS multicast sessions. When the UE moves between cells specified in the list (i.e., cell selection or reselection), the corresponding PTM configuration is considered to be valid. When the UE moves to a cell outside the cell specified in the cell list, the UE considers that the corresponding PTM configuration is no longer valid.
  • the cell list may contain only one cell.
  • the base station may not configure the cell list for the UE.
  • the base station may also indicate to the UE that the valid area of the PTM configuration is the same as the RAN-based notification area RNA.
  • the base station configures the UE to receive one or more multicast sessions in the RRC inactive state
  • 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 ability 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 reception conflict, for example, because the paging message (or system information) and the multicast session are transmitted on different cells, how can the UE Dealing with this conflict is the problem that needs to be solved.
  • the UE in an RRC inactive state maintains a consistent understanding with the base station as to whether to give priority to receiving the multicast session. If the UE gives priority to receiving the multicast session, the base station may send the paging message multiple times when a conflict occurs between receiving paging and receiving the multicast session, so that the UE can receive the paging message after receiving the MBS multicast session.
  • the base station configures for the UE whether the UE receives the paging message (or system information) or the multicast session when a conflict occurs between the paging message (or system information) and the multicast session reception.
  • the base station carries a third indication identifier in an RRC reconfiguration message or an RRC release RRCRelease message to indicate whether the UE receives the paging message (or system information) or the multicast session when a conflict occurs between the paging message (or system information) and the multicast session reception.
  • the base station configures the UE when the UE is in an RRC connected state or the UE wishes to restore the RRC connection (for example, when the base station receives an RRCResumeRequest or RRCResumeRequest1 message from the UE, it configures the UE in the RRCRelease message).
  • the base station can configure the UE through an RRC reconfiguration message RRCReconfiguration or an RRC release message RRCRelease.
  • a paging message (or system information) and a multicast session reception conflict it is predefined whether the UE receives the paging message (or system information) or the multicast session.
  • the predefined paging message (or system information) and the multicast session are always transmitted in the same cell.
  • the multicast session configured for the UE in the RRC inactive state is always transmitted on the initial part of the bandwidth.
  • the UE When the UE is in the RRC connected state, the UE indicates to the base station that when a conflict occurs between the multicast session received in the RRC inactive state and the paging message (or system information) received, the UE should give priority to receiving information related to the multicast session or the paging message (or system information) (recorded as the fourth indication identifier).
  • the fourth indication identifier can be carried in the UE auxiliary information message or in the In the MBSInterestIndication message, a message may also be redefined to carry the information.
  • the fourth indication identifier may be used to indicate whether the UE preferentially receives the multicast session instead of the paging message (or system information). It may be specified that if the UE preferentially receives the multicast session, the field is carried or exists (for example, the value is true), otherwise, the field is not carried or does not exist.
  • the indication flag or prohibition timer associated with the multicast session is the indication flag or prohibition timer associated with the PTM configuration, and the two can be used interchangeably.
  • FIG4 is a simplified block diagram of the structure of the user equipment UE according to the present invention.
  • the user equipment UE80 includes a processor 801 and a memory 802.
  • the processor 801 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc.
  • the memory 802 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memories, etc.
  • the memory 802 stores program instructions. When the instructions are executed by the processor 801, the above method performed by the user equipment described in detail in the present invention may be executed.
  • the computer executable instructions or programs running on the device according to the present invention can be programs that enable the computer to implement the functions of the embodiments of the present invention by controlling the central processing unit (CPU).
  • the program or the information processed by the program can be temporarily stored in a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory systems.
  • 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.
  • the various features or functional modules of the devices used in the above embodiments may be implemented or executed by circuits (e.g., single-chip or multi-chip integrated circuits).
  • the circuits capable of performing the above functions may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above devices.
  • the general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine.
  • the above circuits may be digital circuits or analog circuits. In the case where new integrated circuit technologies that replace existing integrated circuits have emerged due to advances in semiconductor technology, one or more embodiments of the present invention may also be implemented using these new integrated circuit technologies.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention propose un procédé exécuté par un équipement utilisateur, et un équipement utilisateur. Le procédé comprend : la réception d'un premier identifiant d'indication, qui est associé à chaque configuration point à multipoint (PTM) et est inclus dans un message de recherche provenant d'une station de base ; la comparaison de la valeur du premier identifiant d'indication avec une valeur qui est stockée localement dans un équipement utilisateur et correspond au premier identifiant d'indication ; et lorsque le résultat de comparaison est que la valeur du premier identifiant d'indication est différente de la valeur qui est stockée localement dans l'équipement utilisateur et correspond au premier identifiant d'indication, l'équipement utilisateur initie un processus de récupération de connexion RRC, de façon à mettre à jour la configuration PTM ou à acquérir la configuration PTM mise à jour.
PCT/CN2023/121616 2022-09-28 2023-09-26 Procédé éxécuté par un équipement utilisateur, et équipement utilisateur WO2024067602A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211204920.6A CN117835461A (zh) 2022-09-28 2022-09-28 由用户设备执行的方法以及用户设备
CN202211204920.6 2022-09-28

Publications (1)

Publication Number Publication Date
WO2024067602A1 true WO2024067602A1 (fr) 2024-04-04

Family

ID=90476373

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/121616 WO2024067602A1 (fr) 2022-09-28 2023-09-26 Procédé éxécuté par un équipement utilisateur, et équipement utilisateur

Country Status (2)

Country Link
CN (1) CN117835461A (fr)
WO (1) WO2024067602A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022073226A1 (fr) * 2020-10-10 2022-04-14 Lenovo (Beijing) Limited Procédé et appareil de transmission de signaux de commande
WO2022082588A1 (fr) * 2020-10-22 2022-04-28 Zte Corporation Configuration et mise à jour de ressources de service de diffusion multidiffusion

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022073226A1 (fr) * 2020-10-10 2022-04-14 Lenovo (Beijing) Limited Procédé et appareil de transmission de signaux de commande
WO2022082588A1 (fr) * 2020-10-22 2022-04-28 Zte Corporation Configuration et mise à jour de ressources de service de diffusion multidiffusion

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LENOVO: "Mobility and state transition for multicast reception in RRC_INACTIVE", 3GPP DRAFT; R3-224439, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. E-meeting; 20220815 - 20220824, 9 August 2022 (2022-08-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052264606 *
LENOVO: "PTM configuration for multicast reception in RRC_INACTIVE", 3GPP DRAFT; R3-224438, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. E-meeting; 20220815 - 20220824, 9 August 2022 (2022-08-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052264605 *

Also Published As

Publication number Publication date
CN117835461A (zh) 2024-04-05

Similar Documents

Publication Publication Date Title
WO2021077434A1 (fr) Procédé et appareil de communication
US11395256B2 (en) Communication method, device, and system
JP2020504530A (ja) データ伝送方法及び装置
JP2007518306A (ja) 無線通信システム及び方法
JP7545500B2 (ja) 状態切替方法、接続状態ｍｔｃｈの指示方法および装置、ならびに記憶媒体、端末および基地局
WO2022078256A1 (fr) Procédé de commande de connexion sans fil et équipement utilisateur
WO2012108358A1 (fr) Système et station de base de remise de messages, et procédé de remise de messages
WO2021109824A1 (fr) Procédé et dispositif de création de session, procédé et dispositif de commande de création de session, système de création de session, élément de réseau et support de stockage
WO2022078384A1 (fr) Procédé de transmission exécuté par un équipement utilisateur, équipement utilisateur, station de base et procédé de transmission exécuté par une station de base
WO2022237602A1 (fr) Procédé pour rapporter un rapport de mesure de qoe, dispositif, appareil et support de stockage
WO2022078328A1 (fr) Procédé de transmission exécuté par un équipement utilisateur, équipement utilisateur, station de base et procédé de transmission exécuté par une station de base
WO2022057857A1 (fr) Équipement utilisateur et procédé associé, station de base et procédé associé
EP3509337B1 (fr) Noeud et procédé de gestion d'une connexion de données par paquets
WO2024067602A1 (fr) Procédé éxécuté par un équipement utilisateur, et équipement utilisateur
WO2023125201A1 (fr) Procédé et appareil de communication
WO2024160226A1 (fr) Équipement utilisateur, station de base et procédé associé
WO2024193433A1 (fr) Procédé de traitement pour des informations de configuration de mcch, équipement utilisateur
WO2024120475A1 (fr) Procédé de récupération de connexion rrc, et équipement utilisateur
WO2024169733A1 (fr) Équipement utilisateur, station de base et procédé associé
WO2024120476A1 (fr) Procédé exécuté par un équipement utilisateur, et équipement utilisateur
WO2023040969A1 (fr) Procédé d'interaction de capacité d'équipement utilisateur et équipement utilisateur
WO2024032544A1 (fr) Procédé exécuté par un équipement utilisateur pour traiter un message de radiomessagerie, et équipement utilisateur
WO2024193650A1 (fr) Équipement utilisateur et procédé exécuté par l'équipement utilisateur
WO2023098865A1 (fr) Procédé executé par un équipement utilisateur et équipement utilisateur
WO2023280205A1 (fr) Procédé exécuté par un équipement d'utilisateur, et équipement d'utilisateur

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23870830

Country of ref document: EP

Kind code of ref document: A1