WO2023066188A1 - Procédé de transfert intercellulaire de cellule et équipement utilisateur - Google Patents

Procédé de transfert intercellulaire de cellule et équipement utilisateur Download PDF

Info

Publication number
WO2023066188A1
WO2023066188A1 PCT/CN2022/125624 CN2022125624W WO2023066188A1 WO 2023066188 A1 WO2023066188 A1 WO 2023066188A1 CN 2022125624 W CN2022125624 W CN 2022125624W WO 2023066188 A1 WO2023066188 A1 WO 2023066188A1
Authority
WO
WIPO (PCT)
Prior art keywords
drb
base station
mrb
information
target base
Prior art date
Application number
PCT/CN2022/125624
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 WO2023066188A1 publication Critical patent/WO2023066188A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • 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

Definitions

  • the present invention relates to the field of wireless communication technology, and more specifically, the present invention relates to a method for performing cell handover performed by a source user equipment, a method for performing cell handover performed by a source base station, and user equipment.
  • Goal A 5G Multicast Broadcast Service Architecture Improvement
  • 3rd Generation Partnership Project 3rd Generation Partnership Project: 3GPP
  • RAN#86 plenary meeting Huawei proposed the work item of NR Multicast and Broadcast Service (NR MBS) (see non-patent literature: RP-193248 : New WID: NR Multicast and Broadcast Service) was approved. This work item is intended to provide support for Objective A in the RAN.
  • the present invention discusses related issues involved in RAN achieving the above working goals.
  • the purpose of the present invention is to provide a cell switching method that can ensure the continuity of MBS services and reduce data loss.
  • the present invention provides a method for cell handover performed by a source base station, including: when the source base station sends the cell handover request message to the target base station, based on the source base station and the target base station
  • the interface parameter information of the network interface established between the base stations is used to determine whether the target base station supports MBS sessions, and the cell handover request message is used to request the target base station to prepare RRC resources for the user equipment; if the target base station does not support MBS session, then do not carry the RRC configuration information related to the MBS session configured by the source base station for the user equipment in the cell handover request message; and change the RRC configuration information related to the MBS session to be related to the target
  • the RRC configuration information related to the PDU session supported by the base station, and the changed RRC configuration information is carried in the cell handover request message and sent to the target base station.
  • a method for cell handover performed by user equipment including: receiving from a source base station a first RRC reconfiguration message for the user equipment generated by the source base station, the The first RRC reconfiguration message carries the second RRC reconfiguration message generated by the target base station, and the first RRC reconfiguration message also includes the difference between the MRB for the multicast broadcast service session, that is, the MBS session, and the DRB for the PDU session and based on the second RRC reconfiguration message and/or the mapping relationship information, reconfigure the RRC configuration related to the MBS session of the user equipment into a PDU supported by the target base station For session-related RRC configuration, the second RRC reconfiguration message is generated by the target base station in response to a cell switching request message sent by the source base station and sent to the source base station.
  • a user equipment including: a processor; and a memory storing instructions, wherein, when the instructions are executed by the processor, the instructions executed by the user equipment as described above are executed. method.
  • the continuity of the MBS service can be guaranteed and data loss can be reduced.
  • FIG. 1 are schematic diagrams showing specific configurations of radio bearers for receiving MBS services according to the present invention.
  • Fig. 2 is a flow chart of a method for cell handover performed by a base station according to an embodiment of the present invention.
  • Fig. 3 is a flowchart of a method for cell handover performed by a user equipment according to an embodiment of the present invention.
  • Fig. 4 is a flowchart of a process of parsing out a second RRC reconfiguration message in a method for cell handover performed by a user equipment according to an embodiment of the present invention.
  • Fig. 5 is a flow chart of a specific example of a reconfiguration process in a method for cell handover performed by a user equipment according to an embodiment of the present invention.
  • Fig. 6 is a structural block diagram of a user equipment for performing a method for performing cell handover according to an embodiment of the present invention.
  • UE User Equipment, user equipment.
  • RRC Radio Resource Control, radio resource control.
  • RRC_CONNECTED RRC connected state.
  • RRC_INACTIVE RRC is inactive.
  • RRC_IDLE RRC idle state.
  • RAN Radio Access Network, wireless access network.
  • New RAT new radio access technology.
  • MBMS Multimedia Broadcast/Multicast Service, multimedia broadcast multicast service.
  • MBS Multicast/Broadcast Services, multicast/broadcast services.
  • PDCP Packet Data Convergence Protocol, packet data convergence protocol.
  • RLC Radio Link Control, wireless link control.
  • SDU Service Data Unit, service data unit.
  • SDU Service Data Unit
  • PDU Protocol Data Unit, protocol data unit.
  • the data packet that this layer receives or delivers from the lower layer is called PDU.
  • a PDCP data PDU is a data packet obtained by adding a PDCP header to a PDCP SDU.
  • RB Radio Bearer, radio bearer.
  • MRB MBS radio bearer, that is, a radio bearer configured for MBS transmission (Aradio bearer that is configured for MBS delivery).
  • the MBS-MCCH Multicast Control Channel, multicast control channel.
  • the MBS-MCCH is used to transmit control information related to receiving MBS services.
  • SC-MCCH Single Cell Multicast Control Channel, single cell multicast control channel.
  • TMGI Temporary Mobile Group Identity, temporary mobile group identity.
  • PLMN Public Land Mobile Network, public land mobile network.
  • RNTI Radio Network Temporary Identifier, wireless network temporary identifier.
  • PTM Point to Multipoint, point to multipoint, a delivery method of MBS business.
  • the RAN node delivers a single copy of MBS data packets over radio to a set of UEs via radio (a RAN node delivers a single copy of MBS data packets over radio to a set of UEs).
  • PTP Point to Point, point to point, a delivery method of MBS business.
  • the RAN node delivers copies of multiple MBS data packets to each UE via radio (a RAN node delivers separate copies of MBS data packet over radio to individual UE).
  • LTE SC-PTM LTE Single Cell Point to Multipoint, long term evolution single cell point to multipoint.
  • MBS multicast or multicast communication service means that the same service and the same specific content are simultaneously provided to a group of specific UEs.
  • a multicast traffic is delivered to the UE using the multicast session.
  • a UE in RRC_CONNECTED can use PTP and/or PTM to receive a multicast communication service.
  • G-RNTI Group RNTI, group RNTI, used to scramble the scheduling and transmission of MTCH (used to scramble the scheduling and transmission of MTCH).
  • NR MBS supports 1-1 mapping between G-RNTI and MBS session (One-to-one mapping between G-RNTI and MBS session is supported in NR MBS).
  • Associated PDU session a PDU session associated to a multicast session (also called an MBS session), which is used for the 5GC unicast MBS traffic delivery method (5GC Individual MBS traffic delivery method) of the 5G core network and for communicating with users Signaling related to participating in a multicast session such as join and leave requests.
  • MBS session also called an MBS session
  • 5GC unicast MBS traffic delivery method 5GC Individual MBS traffic delivery method
  • the unicast QoS flow belonging to the associated PDU session is used for the 5GC unicast MBS traffic delivery method, and the associated QoS flow is mapped from the multicast QoS flow in the multicast MBS session.
  • network, base station and RAN can be used interchangeably, and the network can be a long-term evolution LTE network, an NR network, an enhanced long-term evolution eLTE network, or other networks defined in subsequent evolution versions of 3GPP.
  • the base station broadcasts the MBMS service and its scheduling information supported by the system information and the message transmitted on the SC-MCCH channel.
  • the radio bearer configuration information used to transmit the MBMS service is predefined .
  • the UE can know the MBMS service that the current cell or base station supports or is in progress by receiving the corresponding system information and the message transmitted on the SC-MCCH.
  • the UE needs to receive a certain MBMS service, it establishes a radio bearer according to predefined parameters and receives data. In this case, UE can receive MBMS service without establishing RRC connection.
  • MBS MBS services
  • some MBS services can also be scheduled in a manner similar to SC-PTM, so that UEs in the RRC idle state and RRC inactive state can also receive the MBS services.
  • MBS services there are another part of MBS services that require the UE to establish an RRC connection with the base station, and then the base station configures for the UE through dedicated RRC signaling (also called a dedicated RRC message), and the radio bearer for receiving these MBS services can also be configured by the base station through dedicated RRC signaling.
  • the order is UE configuration.
  • (a) to (c) of FIG. 1 are schematic diagrams showing specific configurations of radio bearers for receiving MBS services.
  • the radio bearer may be an MRB configured with only PTM transmission (as shown in (a) of Figure 1), or a separate MRB (split MRB) configured with PTM and PTP at the same time (as shown in (b) of Figure 1 ) Or only MRBs for PTP transmission are configured (as shown in (c) of FIG. 1 ). It should be noted that (a)-(c) of FIG. 1 only show the PDCP entity and RLC entity corresponding to the bearer and the relationship between them. In the downlink direction, the PDCP PDU encapsulated by the PDCP entity is delivered to the RLC entity.
  • the UE For the MBS service that the UE needs to establish an RRC connection with the base station, when the UE switches from a base station that supports MBS (source base station) to a base station that does not support MBS (target base station), how to ensure the continuity of the MBS service and reduce data loss is the key issues that need resolving.
  • MBS source base station
  • target base station target base station
  • the source base station (or source NG-RAN node) sends a handover request (HANDOVER REQUEST) message to the target base station (or target NG-RAN node) to establish the necessary H.
  • the handover request message includes an RRC Context field, and the field is used to include a HandoverPreparationInformation message.
  • the HandoverPreparationInformation message is used to transfer the NR RRC information used by the target base station during the handover preparation (is used to transfer the NR RRC information used by the target gNB).
  • the HandoverPreparationInformation message contains the RRCReconfiguration configuration completely generated by the source base station (Contains the RRCReconfiguration configuration as generated entirely by the source gNB).
  • the target base station sends a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message to the source base station as a response message, which includes the transparent container (Target NG-RAN node) from the target base station (ie, the target NG-RAN node) to the source base station (ie, the source NG-RAN node).
  • the field is used to carry the HandoverCommand message
  • the HandoverCommand message carries the RRCReconfiguration (RRC reconfiguration) message generated by the target base station
  • the source base station receives the handover request confirmation message Then forward the RRCReconfiguration message generated by the target base station to the UE.
  • the handover request message is sent by the source base station to the target base station to request to prepare resources for handover; the handover request confirmation message is sent by the target base station to notify the source base station of the prepared resources on the target.
  • the RRCReconfiguration message generated by the target base station will contain a fullConfig field, the fullConfig field is used to indicate that the full configuration options are applied to the RRCReconfiguration message.
  • the UE will release all DRBs and MRBs, which will fail to achieve service continuity and/or cause data loss.
  • Fig. 2 is a flow chart of a method for cell handover performed by a base station according to an embodiment of the present invention.
  • the source base station may determine whether the target base station supports MBS sessions based on the interface parameter information of the network interface established between the source base station and the target base station, and the cell handover request message is used to request the target base station to be
  • the user equipment prepares RRC resources.
  • This network interface is, for example, an Xn interface.
  • the source base station does not carry the RRC configuration information related to the MBS session configured by the source base station for the user equipment in the cell handover request message.
  • the source base station may change the RRC configuration information related to the MBS session to the RRC configuration information related to the PDU session supported by the target base station, and send the changed RRC configuration information to the target base station in a cell handover request message .
  • the source base station may modify the information of the MRB configured for the MBS session to the information of the DRB mapped to the MRB, and send it to the target base station in the cell handover request message.
  • the target base station may generate second RRC reconfiguration information based on the RRC reconfiguration information carried in the cell switching request message, and carry the second RRC reconfiguration information in the switching response message as the response message. Sent to the source base station in a request confirmation message.
  • the source base station may generate a user equipment handover request based on the second RRC reconfiguration information carried in the handover request confirmation message. and send the first RRC reconfiguration information to the target base station, and send the generated first RRC reconfiguration information to the user equipment.
  • the source base station may send a cell handover request message carrying RRC configuration information related to the MBS session to the target base station at S208.
  • the second RRC configuration message carried in the handover request acknowledgment message may be directly sent to the UE instead of generating the first RRC reconfiguration message.
  • Embodiments of operations performed by the source base station and the target base station are described below.
  • the source base station should not provide MBS configuration information, such as MBS session information, in the RRCReconfiguration configuration included in the HandoverPreparationInformation message provided to the target base station and MRB configuration information, etc.
  • MBS configuration information such as MBS session information, in the RRCReconfiguration configuration included in the HandoverPreparationInformation message provided to the target base station and MRB configuration information, etc.
  • the source base station includes the PDU session-related information associated with the MBS session in the handover request message, for example, in the PDU Session Resources To Be Setup List field to be established, and the field includes Information related to PDU session resources, such as including PDU session ID (identifying a PDU session for UE), PDU session type, list of QoS flows to be established, etc., the list of QoS flows to be established includes related Information, the relevant information of the QoS flow may include a QoS flow identifier (identifying a QoS flow in a PDU session), QoS parameters of the QoS flow level, and the like.
  • the configuration information related to the MBS session is deleted, for example, mrb-ToAddModList (adding and modifying the MRB list) and/or related information such as RLC-BearerConfig associated to the MRB is deleted.
  • the target base station configures the corresponding DRB for the PDU session associated with the MBS session included in the PDU session resource list to be established, and passes the configured DRB information through the RRCReconfiguration message generated by the target base station (referred to as the second RRCReconfiguration message or In the second RRC reconfiguration message), it is forwarded to the UE via the source base station.
  • the source base station when it receives the handover request confirmation message, it generates an RRCReconfiguration message (called the first RRCReconfiguration message or the first RRC reconfiguration message), and the first RRC reconfiguration message includes information for carrying the second RRC
  • the field mbsToNonMBSNode of the reconfiguration message this field is used to indicate that the cell handover to be performed is from the base station that supports MBS sessions to the base station that does not support MBS sessions
  • the field mrb-ToReleaseList that is used to indicate the release of MRBs (that is, the MRB information)
  • the mrb-ToReleaseList contains the MRB-Identities of all MRBs that need to be released.
  • mbsToNonMBSNode is the condition for configuring mrb-ToReleaseList, that is, only when mbsToNonMBSNode appears, can mrb-ToReleaseList be configured, and vice versa.
  • the source base station includes the PDU session-related information associated with the MBS session in the handover request message, for example, in the PDU Session Resources To Be Setup List field to be established, and the field includes Information related to PDU session resources, such as including PDU session ID (identifying a PDU session for UE), PDU session type, list of QoS flows to be established, mapping of source base station QoS flows to DRB, etc., the list of QoS flows to be established contains the relevant information of the QoS flow to be established, and the relevant information of the QoS flow may include a QoS flow identifier (identifying a QoS flow in a PDU session), QoS parameters of the QoS flow level, and the like.
  • PDU session ID identifying a PDU session for UE
  • PDU session type identifying a PDU session type
  • list of QoS flows to be established maps mapping of source base station QoS flows to DRB, etc.
  • the list of QoS flows to be established contains the
  • the target base station In the RRCReconfiguration configuration provided to the target base station, delete the configuration information related to the MBS session and/or modify the configuration information related to the MRB to the corresponding DRB, so that the target base station can use the DRB as the DRB that the source base station has configured for the UE to deal with.
  • a DRB ID that is, drb-Identity, DRB identification
  • modify the MRB ID that is, mrb-Identity, MRB identification
  • the PDU session identifier associated with the MBS session; and/or for the MRB only associated with the PTM RLC modify the MRB ID to the DRB ID and/or delete the corresponding G-RNTI and/or delete the PTM transmission indicator (that is, the The above indication indicates that the corresponding RLC entity is configured for PTM transmission); and/or for the MRBs of PTM RLC and PTP RLC associated at the same time, delete the configuration information related to PTM RLC and/or delete the corresponding G-RNTI; and/or Or store the mapping relationship between the MRB and the DRB.
  • the target base station sends a handover request confirmation message to the source base station as a response message.
  • the RRCReconfiguration configuration message provided by the source base station to the target base station is included in the HandoverPreparationInformation message carried in the handover request message.
  • Fig. 3 is a flowchart of a method for cell handover performed by a user equipment according to an embodiment of the present invention.
  • the user equipment receives from the source base station a first RRC reconfiguration message for the user equipment generated by the source base station.
  • the first RRC reconfiguration message carries the second RRC reconfiguration message generated by the target base station, and the first RRC reconfiguration message may also include the MRB for the multicast broadcast service session, that is, the MBS session, and the DRB for the PDU session. Mapping relationship information.
  • the mapping relationship information may be the mapping between the DRB ID and the MRB ID, or the mapping between the MBS session ID and the PDU session ID, or the mapping between the DRB ID and the MRB ID and the MBS session ID. Mapping between identifiers and PDU session identifiers.
  • the second RRC reconfiguration message is generated by the target base station in response to the cell switching request message sent by the source base station and sent to the source base station.
  • the user equipment may reconfigure the RRC configuration related to the MBS session of the user equipment to the RRC configuration related to the PDU session supported by the target base station based on the second RRC reconfiguration message and/or the mapping relationship information.
  • the reconfiguration operation may include at least one of the following: based on the second RRC reconfiguration message and/or the mapping relationship information, configuring the RRC related to the MBS session of the user equipment , reconfiguring the RRC configuration related to the PDU session supported by the target base station includes at least one of the following: based on the mapping relationship information, replacing the MRB identifier for the MBS session with the DRB identifier mapped to the MRB;
  • the mapping relationship information associates the DRB to which the MRB is mapped to the SDAP entity associated with the MRB; based on the mapping relationship information, modifies the MBS session identifier to the PDU session identifier of the PDU session associated to the MBS session; upward Instruct the layer to release the user plane resources of the MBS session; instruct the upper layer to establish the user plane resource of the PDU session; instruct the upper layer to modify the user plane resource related to the MBS session into a PDU associated with the DRB mapped to the MRB for the MBS session
  • the user equipment may perform reconfiguration based on the mapping relationship information. For example, for each DRB indicated by the mapping relationship information, at least one of the following may be performed: if the MRB mapped to the DRB is configured with a PTM RLC entity and a PTP RLC release the PTM RLC bearer corresponding to the PTM RLC entity; if the MRB mapped to the DRB is a PTM MRB that is only configured with a PTM RLC entity, release the PTM transmission indicator of the PTM RLC entity; if mapped to If the MRB of the DRB is a PTM MRB configured only with a PTM RLC entity or a PTP MRB configured only with a PTP RLC entity, then the PTM RLC or PTP RLC entity associated with the MRB mapped to the DRB is associated with the DRB.
  • the user equipment may release information related to the MRB.
  • the source base station may carry a field in the first RRC reconfiguration message indicating that the target base station does not support the MBS session.
  • the user equipment may parse out the second RRC reconfiguration and perform reconfiguration. This example will be described below with reference to FIG. 4 .
  • Fig. 4 is a flowchart of a process of parsing out a second RRC reconfiguration message in a method for cell handover performed by a user equipment according to an embodiment of the present invention.
  • the user equipment may, when receiving the first RRC reconfiguration message, determine whether the first RRC reconfiguration message includes a field for indicating that the target base station does not support the MBS session.
  • the user equipment may parse the field at S404, and parse out the second RRC reconfiguration message from the field. However, the user equipment may perform a reconfiguration operation. If the first RRC reconfiguration does not include the above fields, no further operations may be performed.
  • the second RRC reconfiguration message may include DRB change information, and the DRB change information includes information indicating the DRB that needs to be changed by the target base station.
  • the "change" mentioned here may include various change operations such as deletion, modification, addition, and release.
  • the DRB change information may include DRB modification information indicating the information of the DRB to be modified, may also include the information of the DRB to be added indicating the information of the DRB to be added, and may also include the requirements of the information indicating the DRB to be released. Release DRB information.
  • Such information may be in the form of a list, for example, a list of DRB identities of corresponding DRBs.
  • reconfiguration may be performed according to the flow in FIG. 5 .
  • Fig. 5 is a flow chart of a specific example of a reconfiguration process in a method for cell handover performed by a user equipment according to an embodiment of the present invention.
  • the user equipment may determine, for each DRB indicated by the DRB change information, whether the DRB is included in the existing RRC configuration of the user equipment.
  • the user equipment may determine whether there is an MRB mapped to the DRB at S506 based on the mapping relationship information;
  • the user equipment may establish the DRB at S506. If there is an MRB mapped to the DRB, the user equipment may reconfigure the MRB mapped to the DRB at S508.
  • the DRB change information includes the newly added and modified DRB list, and the newly added and modified DRB list includes the information of the newly added or modified DRB requested by the target base station.
  • the reconfiguration of the MRB mapped to the DRB described in S508 above includes performing at least one of the following if the DRB is included in the newly added modified DRB list: if the DRB mapped to the DRB The MRB is associated with the PTM RLC entity, and then instructs the PTM RLC entity to release the PTM transmission indication identifier and/or the corresponding group wireless network temporary identifier; if the RRC reconfiguration information includes a PDCP re-establishment indication, re-establish the MRB mapped to the DRB If the RRC reconfiguration information includes a PDCP recovery indication, make the PDCP entity of the MRB mapped to the DRB perform data recovery; if the RRC reconfiguration information includes PDCP reconfiguration information, then according to the PDCP reconfiguration Configuration information, recon
  • the DRB change information may also include a list of DRBs to be released, and the list of DRBs to be released includes the information of the DRBs required to be released by the target base station.
  • the operation in S508 can be performed as follows. If the DRB is included in the list of DRBs to be released, release the MRB identifier of the PDCP entity of the MRB mapped to the DRB. If the MRB mapped to the DRB is configured with a corresponding SDAP entity, the user equipment may also instruct the SDAP entity to release the MRB mapped to the DRB.
  • the UE receives a first RRCReconfiguration message (first RRC reconfiguration message) from the base station (ie, the source base station), and the first RRCReconfiguration message may include MRB change information.
  • the "change” mentioned here may include various change operations such as deletion, modification, addition, and release.
  • the MRB change information may include the information about the MRB to be released, and may also include the newly added or modified MRB information to be added or modified. These information may be in the form of a list including MRB identification.
  • the message contains mrb-ToReleaseList (to release MRB list information)
  • MRB identity mrb-Identity
  • the mrb-Identity is part of the current UE configuration, then Release the corresponding PDCP entity and mrb-Identity, and/or indicate to the upper layer that this MRB is released and the field tmgi of the released MRB.
  • the field tmgi is used to indicate the MBS session associated with the bearer, and its value is TMGI.
  • the UE receives the RRCReconfiguration message from the base station (namely the source base station), if the RRCReconfiguration message contains the reconfigurationWithSync field and the target base station does not support MBS, for each currently configured mrb-Identity, release the corresponding PDCP entity and mrb-Identity, and/or indicate to the upper layer that this MRB is released and the tmgi of the released MRB, and/or release the RLC entity or RLC bearer associated with the MRB.
  • the reconfigurationWithSync field includes related parameters of synchronous reconfiguration to the target SpCell, and tmgi is used to indicate the bearer associated MBS session.
  • the "target base station does not support MBS” can be replaced with "the RRCReconfiguration message received by the UE containing the reconfigurationWithSync field does not contain any MRB configuration" or "the received RRCReconfiguration message does not contain a field indicating that the base station supports MBS mbsSupporting".
  • an mbsSupporting (MBS support) field is included in the RRCReconfiguration message generated by the target base station.
  • a field keepMBS is included in the RRCReconfiguration message to instruct the UE to keep the configured MBS.
  • the received RRCReconfiguration message does not contain the field, for each mrb-Identity or MRB currently configured, if the mrb-Identity or MRB is not included in the received RRCReconfiguration message, then release the corresponding PDCP entity and mrb-Identity, and/or indicate to the upper layer that this MRB is released and the tmgi of the released MRB, and/or release the associated MRB RLC entity or RLC bearer.
  • the specific operation of releasing the RLC bearer may include releasing the RLC entity and releasing the corresponding logical channel.
  • the tmgi indicating to the upper layers to release the user plane resources of the MBS session and the released MRBs can be used alternatively, and the obtained embodiments are also within the protection scope of the present invention.
  • the UE reconfigures each MRB mapped to the DRB according to the configuration information contained in the second RRCReconfiguration message, for example, replacing the mrb-Identity of the MRB with the drb-Identity of the DRB to which it is mapped, And/or modify the MBS session identifier associated with the MBS to the PDU session identifier associated with the MBS session, and/or associate the SDAP entity (or PDCP entity or RLC entity) associated with the MRB mapped to the DRB to the DRB ( It can also be expressed as associating the DRB with the SDAP entity (or PDCP entity or RLC entity) associated with the MRB mapped to the DRB, and/or instructing the upper layer to release the user plane resources of the MBS session, and/or instructing the upper layer Establish the user plane resources of the PDU session, and/or indicate to the upper layer to change the user plane resources of the MBS session to the user plane resources of the associated PDU session, and/or release the PTM
  • the UE receives the first RRCReconfiguration message from the base station (that is, the source base station), and the first RRCReconfiguration message includes the mapping relationship between the MBS session and the associated PDU session and/or the MRB ID (that is, MRB-Identity) and the DRB ID (that is, the DRB - the mrbToDrbMappingList field of the mapping relationship between Identity), the first RRCReconfiguration message further includes the mbsToPduRRCReconfig field, and the field is used to carry the second RRCReconfiguration message generated by the target base station.
  • the base station that is, the source base station
  • the first RRCReconfiguration message includes the mapping relationship between the MBS session and the associated PDU session and/or the MRB ID (that is, MRB-Identity) and the DRB ID (that is, the DRB - the mrbToDrbMappingList field of the mapping relationship between Identity)
  • the first RRCReconfiguration message further includes the mbsToPduRR
  • the drb-Identity contained in the drb-ToAddModList (newly added and modified DRB list) contained in the second RRCReconfiguration message if the drb-Identity is not part of the current UE configuration and is not mapped to an MRB (ie drb- Identity is not included in the mrbToDrbMappingList field), then the corresponding DRB is established (according to the method for establishing a DRB defined in 3GPP technical specification TS38.331).
  • the MRB mapped to the DRB is associated (that is, only associated) with a PTM RLC entity, release the PTM transmission indicator and/or the corresponding G-RNTI or instruct the PTM RLC entity (or PTM RLC bearer) to release the PTM transmission indicator and /or the corresponding G-RNTI.
  • the purpose of this operation is to make the UE no longer monitor the PTM transmission of the MBS.
  • drb-ContinueEHC-UL is included in pdcp-Config, it indicates that the lower layer is configured with drb-ContinueEHC-UL; it can be stipulated that this configuration is not used for the DRB to which the MRB is mapped.
  • recoverPDCP If recoverPDCP is set, trigger the PDCP entity of the MRB mapped to this DRB to perform data recovery.
  • this operation step may not be applied to the DRB corresponding to the associated PDU.
  • the encryption algorithm or key has not changed and/or the integrity protection algorithm or key has not changed, etc., in order to reduce data loss, it is necessary to retransmit the data that has been sent but has not been confirmed to be sent successfully, and the PDCP entity can be instructed to perform data recovery .
  • the target base station cannot support or needs to modify the configuration of some parameters in the current pdcp-Config, it can send pdcp-Config containing new PDCP entity configuration information to reconfigure the PDCP entity.
  • the MRB mapped to the DRB is a separate MRB (that is, a PTM RLC and a PTP RLC are associated at the same time)
  • release the PTM RLC bearer includes releasing the RLC entity and releasing the corresponding logical channel according to the operations defined in Section 5.1.3 of TS38.322.
  • RLC Associating the RLC entity associated with the MRB mapped to the DRB to the DRB.
  • the RLC refers to the PTP RLC; for a PTM MRB configured only with a PTM RLC entity, the RLC refers to the PTM RLC.
  • MRB For an MRB that is not mapped to any DRB (that is, the MRB corresponding to each mrb-Identity not included in mrbToDrbMappingList), release the MRB, specifically including releasing the PDCP entity and mrb-Identity, and indicate to the upper layer the release of the MRB and the released MRB's tmgi.
  • drb-ToAddModList is used to indicate a group of added or modified DRB configuration information
  • mrbToDrbMappingList is used to indicate the DRB to which each MRB is mapped or the relationship between mrb-Identity and drb-Identity Mapping relationship, the PDU session of the DRB is the associated PDU session of the MBS session of the MRB.
  • mrbToDrbMappingList does not need to include MBS session and associated PDU session, otherwise it needs to be included, the information of MBS session and associated PDU session can also be included in another field mbsSessionToPduSessionMappinglist different from mrbToDrbMappingList, which is used to indicate the association relationship between MBS session and associated PDU session ;drb-Identity is used to identify the DRB used by the UE; mrb-Identity is used to identify the MRB used by the UE; reestablishPDCP is used to indicate that the PDCP entity should be reestablished; Encryption is disabled for all radio bearers; integrityProtection indicates whether integrity protection is configured for this radio bearer; securityConfig indicates the security algorithm and key used by the radio bearer configured in RadioBearerConfig; keyToUse indicates that the bearer
  • drb-ContinueROHC is used to indicate whether the PDCP entity continues or resets the ROHC header compression protocol during PDCP re-establishment
  • drb-ContinueEHC-DL is used to indicate that the PDCP entity is during PDCP re-establishment Continue or reset the downlink EHC header compression protocol
  • drb-ContinueEHC-UL is used to indicate whether the PDCP entity continues or resets the uplink EHC header compression protocol during PDCP re-establishment
  • recoverPDCP is used to indicate that PDCP should perform recovery according to the operation defined in TS38.323
  • pdcp-Config is used to set configurable PDCP parameters for DRB or MRB
  • sdap-Config is used to set configurable SDAP parameters for DRB or MRB
  • pdu-session is the identifier of the associated PDU session that QoS flow maps to this DRB ;mbs-Ses
  • Drb-Identity is mapped to MRB
  • drb-Identity is mapped to mrb-Identity
  • DRB is mapped to MRB, which means that the DRB is mapped from MRB, that is, drb-Idntity is included in the mrbToDrbMappingList field.
  • a field may also be called an information element IE.
  • the PTM RLC entity is also called the RLC entity associated with PTM or the RLC entity configured with G-RNTI or the RLC entity associated with G-RNTI or the RLC entity used for PTM transmission; the PTP RLC entity is also called PTP The associated RLC entity or the RLC entity used for PTP transport.
  • an MBS service (or MBS session) can be identified by an MBS identifier, and the MBS identifier can be a TMGI and/or a session identifier sessionId, where the TMGI can include a PLMN identifier and/or a service identifier, so The above service identifier uniquely identifies an MBS service within a PLMN.
  • Fig. 6 is a structural block diagram of a user equipment for performing a method for performing cell handover according to an embodiment of the present invention.
  • the user equipment 600 includes at least a processor 601 and a memory 602 .
  • the processor 601 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 602 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a nonvolatile memory (such as a flash memory), or other memory systems.
  • Memory 602 has program instructions stored thereon. When the instruction is executed by the processor 601, one or several steps in the method described above in FIGS. 3-5 of the present invention may be executed.
  • the computer-executable instructions or programs running on the device according to the present invention may be programs that cause the computer to realize 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 volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.
  • Computer-executable instructions or programs for realizing the functions of various embodiments of the present invention can be recorded on computer-readable storage media.
  • the corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs.
  • the so-called “computer system” here may be a computer system embedded in the device, which may include an operating system or hardware (such as peripheral devices).
  • the "computer-readable storage medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium that dynamically stores a program for a short period of time, or any other recording medium readable by a computer.
  • circuits for example, 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.
  • DSPs digital signal processors
  • ASICs application-specific integrated circuits
  • FPGAs field-programmable gate arrays
  • a general-purpose processor can be a microprocessor, or it can be any existing processor, controller, microcontroller, or state machine.
  • the above-mentioned circuits may be digital circuits or analog circuits. Where advances in semiconductor technology have resulted in new integrated circuit technologies that replace existing integrated circuits, one or more embodiments of the invention may also be implemented using these new integrated circuit technologies.
  • 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 equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, 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)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé de transfert intercellulaire de cellule exécuté par une station de base source, consistant à : lorsqu'une station de base source envoie un message de demande de transfert intercellulaire à une station de base cible, déterminer si la station de base cible prend en charge une session MBS, sur la base d'informations de paramètre d'interface d'une interface réseau établie entre la station de base source et la station de base cible, le message de demande de transfert intercellulaire de cellule étant utilisé pour demander à la station de base cible de préparer une ressource RRC pour un équipement utilisateur ; si la station de base cible ne prend pas en charge une session MBS, ne pas ajouter d'informations de configuration RRC associées à une session MBS configurée par la station de base source pour l'équipement utilisateur au message de demande de transfert intercellulaire de cellule ; modifier les informations de configuration RRC associées à la session MBS en informations de configuration RRC associées à une session PDU prise en charge par la station de base cible, ajouter les informations de configuration RRC modifiées au message de demande de transfert intercellulaire de cellule, et envoyer celui-ci à la station de base cible.
PCT/CN2022/125624 2021-10-19 2022-10-17 Procédé de transfert intercellulaire de cellule et équipement utilisateur WO2023066188A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111215299.9 2021-10-19
CN202111215299.9A CN115996359A (zh) 2021-10-19 2021-10-19 进行小区切换的方法及用户设备

Publications (1)

Publication Number Publication Date
WO2023066188A1 true WO2023066188A1 (fr) 2023-04-27

Family

ID=85990729

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/125624 WO2023066188A1 (fr) 2021-10-19 2022-10-17 Procédé de transfert intercellulaire de cellule et équipement utilisateur

Country Status (2)

Country Link
CN (1) CN115996359A (fr)
WO (1) WO2023066188A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111866975A (zh) * 2020-05-18 2020-10-30 中兴通讯股份有限公司 切换方法及装置、信息发送方法及装置
WO2021162315A1 (fr) * 2020-02-14 2021-08-19 주식회사 케이티 Procédé et dispositif de traitement de données de mbs
WO2021162333A1 (fr) * 2020-02-14 2021-08-19 주식회사 케이티 Procédé de traitement de données de mbs et appareil associé

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021162315A1 (fr) * 2020-02-14 2021-08-19 주식회사 케이티 Procédé et dispositif de traitement de données de mbs
WO2021162333A1 (fr) * 2020-02-14 2021-08-19 주식회사 케이티 Procédé de traitement de données de mbs et appareil associé
CN111866975A (zh) * 2020-05-18 2020-10-30 中兴通讯股份有限公司 切换方法及装置、信息发送方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Solution: Integrated MBS and Unicast Transport with Full Separation of MBS Service", 3GPP DRAFT; S2-1911371, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Reno, Nevada, USA; 20191118 - 20191122, 8 November 2019 (2019-11-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051821463 *
VIVO: "MBS Service Continuity for RRC Connected UE", 3GPP DRAFT; R2-2007035, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911883 *

Also Published As

Publication number Publication date
CN115996359A (zh) 2023-04-21

Similar Documents

Publication Publication Date Title
WO2021218375A1 (fr) Procédé et appareil de configuration de support, procédé et appareil de gestion d'informations de contexte, procédé et appareil de libération, et dispositif
CN111406415A (zh) 多播和广播服务的方法和系统
WO2018228326A1 (fr) Procédé, équipement utilisateur et station de base permettant de distribuer des paquets de données
US20220408162A1 (en) Multicast service transmission method and apparatus
JP6321830B2 (ja) 基地局、ユーザ端末及び装置
US10194472B2 (en) Group communication method, device and system
WO2015100733A1 (fr) Procédé de transfert d'équipement utilisateur et station de base
TW201947980A (zh) 用於在無線通信系統中使用區域資料網路的方法和裝置
GB2444998A (en) Dedicated radio resource control
EP3664570B1 (fr) Procédés et appareils d'établissement de session
JP2023533342A (ja) 通信方法及び通信装置
WO2023066188A1 (fr) Procédé de transfert intercellulaire de cellule et équipement utilisateur
WO2023029590A1 (fr) Procédé de gestion de session de diffusion/multidiffusion et appareil de communication
US20230309185A1 (en) Terminal apparatus, base station apparatus, and method
WO2022030456A1 (fr) Équipement terminal, dispositif de station de base et procédé
EP4145937A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023036287A1 (fr) Procédé mis en œuvre par un équipement utilisateur, procédé de transmission pour station de base et équipement utilisateur
WO2023001240A1 (fr) Procédé exécuté par un équipement utilisateur (ue), et équipement utilisateur
JP7481588B2 (ja) 通信方法、ユーザ装置、移動通信システム、チップセット、及びプログラム
WO2023036173A1 (fr) Procédé d'envoi de rapport d'état, procédé d'exécution de retransmission de support radio et équipement utilisateur
JP7494064B2 (ja) 端末装置、基地局装置、方法、および、集積回路
US20230171565A1 (en) Terminal apparatus, method, and integrated circuit
WO2008052420A1 (fr) Procédé pour établir, réétablir et supprimer la porteuse d'accès radio d'un service sélectionné
CN117377025A (zh) 由用户设备执行的方法及用户设备
JP2022046876A (ja) 端末装置、基地局装置、方法、および、集積回路

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: 22882794

Country of ref document: EP

Kind code of ref document: A1