WO2023066188A1 - 进行小区切换的方法及用户设备 - Google Patents
进行小区切换的方法及用户设备 Download PDFInfo
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 238000013507 mapping Methods 0.000 claims description 34
- 230000005540 biological transmission Effects 0.000 claims description 22
- 102100022734 Acyl carrier protein, mitochondrial Human genes 0.000 claims description 21
- 101000678845 Homo sapiens Acyl carrier protein, mitochondrial Proteins 0.000 claims description 21
- 230000008859 change Effects 0.000 claims description 21
- 230000004044 response Effects 0.000 claims description 9
- 238000011084 recovery Methods 0.000 claims description 7
- XHSQDZXAVJRBMX-UHFFFAOYSA-N 2-(5,6-dichlorobenzimidazol-1-yl)-5-(hydroxymethyl)oxolane-3,4-diol Chemical compound OC1C(O)C(CO)OC1N1C2=CC(Cl)=C(Cl)C=C2N=C1 XHSQDZXAVJRBMX-UHFFFAOYSA-N 0.000 claims description 6
- 238000003672 processing method Methods 0.000 claims 1
- 238000012790 confirmation Methods 0.000 description 8
- 238000002716 delivery method Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 230000006835 compression Effects 0.000 description 3
- 238000007906 compression Methods 0.000 description 3
- 230000007774 longterm Effects 0.000 description 3
- 230000011664 signaling Effects 0.000 description 3
- 238000007792 addition Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
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
本发明提供了一种由源基站执行的进行小区切换的方法,包括:所述源基站在向目标基站发送所述小区切换请求消息时,基于所述源基站与所述目标基站之间所建立的网络接口的接口参数信息来确定所述目标基站是否支持MBS会话,所述小区切换请求消息用于请求所述目标基站为用户设备准备RRC资源;如果所述目标基站不支持MBS会话,则不在所述小区切换请求消息中携带所述源基站针对所述用户设备而配置的与MBS会话相关的RRC配置信息;以及将与MBS会话相关的RRC配置信息变更为与所述目标基站所支持的PDU会话相关的RRC配置信息,并将变更后的RRC配置信息携带在所述小区切换请求消息中发送给所述目标基站。
Description
本发明涉及无线通信技术领域,更具体地,本发明涉及由源用户设备执行的进行小区切换的方法、由源基站执行的进行小区切换的方法以及用户设备。
一项关于5G组播广播服务架构改进的研究项目SI(具体见SP-190625)已获得批准,并正在进行中。此SI的目标之一(称为目标A)是在5GS中支持通用MBS服务,已经确定的可以受益于此特性的用例包括(但不限于)公共安全、V2X应用,透明IPv4/IPv6组播传输,IPTV,无线软件传输,群组通信和物联网应用。相应的,在第三代合作伙伴计划(3rd Generation Partnership Project:3GPP)RAN#86次全会上,华为提出了NR多播和广播服务(NR MBS)的工作项目(参见非专利文献:RP-193248:New WID:NR Multicast and Broadcast Service)获得批准。该工作项目旨在RAN中提供对目标A的支持。
本发明讨论RAN达成上述工作目标所涉及的相关问题。
发明内容
本发明的目的在于提供能够保证MBS业务的连续性、减少数据丢失的进行小区切换的方法。
为了解决上述问题,本发明提供了一种由源基站执行的进行小区切换的方法,包括:所述源基站在向目标基站发送所述小区切换请求消息时,基于所述源基站与所述目标基站之间所建立的网络接口的接口参数信息来确定所述目标基站是否支持MBS会话,所述小区切换请求消息用于请求所述目标基站为用户设备准备RRC资源;如果所述目标基站不支持MBS会话,则不在所述小区切换请求消息中携带所述源基站针对所述用户设备而配置的与MBS会话相关的RRC配置信息;以及将与MBS会话 相关的RRC配置信息变更为与所述目标基站所支持的PDU会话相关的RRC配置信息,并将变更后的RRC配置信息携带在所述小区切换请求消息中发送给所述目标基站。
根据本发明的另一方面,还提供一种由用户设备执行的进行小区切换的方法,包括:从源基站接收由所述源基站生成的针对所述用户设备的第一RRC重配置消息,所述第一RRC重配置消息中携带有由目标基站生成的第二RRC重配置消息,所述第一RRC重配置消息还包括针对多播广播业务会话即MBS会话的MRB与针对PDU会话的DRB之间的映射关系信息;以及基于所述第二RRC重配置消息和/或所述映射关系信息,将所述用户设备的与MBS会话相关的RRC配置,重配置为与所述目标基站支持的PDU会话相关的RRC配置,所述第二RRC重配置消息是所述目标基站响应于所述源基站发送的小区切换请求消息而生成并发送给所述源基站的。
根据本发明的另一方面,还提供一种用户设备,包括:处理器;以及存储器,存储有指令,其中,所述指令在由所述处理器运行时执行如上所述的由用户设备执行的方法。
发明效果
根据本发明,能够在目标基站不支持MBS会话时,保证MBS业务的连续性、减少数据丢失。
通过下文结合附图的详细描述,本发明的上述和其它特征将会变得更加明显,其中:
图1的(a)~(c)是表示本发明涉及的接收MBS业务的无线承载的具体配置的示意图。
图2是根据本发明的实施方式的由基站执行的进行小区切换的方法的流程图。
图3是根据本发明的实施方式的由用户设备执行的进行小区切换的方法的流程图。
图4是根据本发明的实施方式的由用户设备执行的进行小区切换的方 法中的解析出第二RRC重配置消息过程的流程图。
图5是根据本发明的实施方式的由用户设备执行的进行小区切换的方法中的重配置过程的具体示例的流程图。
图6是根据本发明的实施方式的用于执行进行小区切换的方法的用户设备的结构框图。
下面结合附图和具体实施方式对本发明进行详细阐述。应当注意,本发明不应局限于下文所述的具体实施方式。另外,为了简便起见,省略了对与本发明没有直接关联的公知技术的详细描述,以防止对本发明的理解造成混淆。
下面描述本发明涉及的部分术语,术语的具体含义可参见3GPP最新相关文档,例如TS38.300、TS38.321、TS38.323、TS38.331等。此外,本发明实施例不限于广播/组播业务,也可以应用于其他应用场景。
UE:User Equipment,用户设备。
RRC:Radio Resource Control,无线资源控制。
RRC_CONNECTED:RRC连接态。
RRC_INACTIVE:RRC非激活态。
RRC_IDLE:RRC空闲态。
RAN:Radio Access Network,无线接入网。
NR:New RAT,新无线访问技术。
MBMS:Multimedia Broadcast/Multicast Service,多媒体广播多播业务。
MBS:Multicast/Broadcast Services,多播/广播业务。
PDCP:Packet Data Convergence Protocol,分组数据汇聚协议。
RLC:Radio Link Control,无线链路控制。
SDU:Service Data Unit,服务数据单元。将本层从上层接收或递交上层的数据包称为SDU。
PDU:Protocol Data Unit,协议数据单元。将本层从下层接收或递交下层的数据包称为PDU。例如,PDCP数据PDU是PDCP SDU增加PDCP 报头后得到的数据包。
RB:Radio Bearer,无线承载。
MRB:MBS无线承载,即一个配置用于MBS传输的无线承载(Aradio bearer that is configured for MBS delivery)。
MCCH:Multicast Control Channel,多播控制信道。MBS-MCCH用于传输与接收MBS服务相关的控制信息。
SC-MCCH:Single Cell Multicast Control Channel,单小区多播控制信道。
TMGI:Temporary Mobile Group Identity,临时移动组标识。
PLMN:Public Land Mobile Network,公众陆地移动网。
RNTI:Radio Network Temporary Identifier,无线网络临时标识。
PTM:Point to Multipoint,点到多点,一种MBS业务的递送(deliver)方式。在PTM递送方式中,RAN节点将一份MBS数据包通过无线电递送给一组UE(a RAN node delivers a single copy of MBS data packets over radio to a set of UEs)。
PTP:Point to Point,点到点,一种MBS业务的递送方式。在PTP递送方式中,RAN节点将多个MBS数据包的副本通过无线电分别递送给每个UE(a RAN node delivers separate copies of MBS data packet over radio to individual UE)。
LTE SC-PTM:LTE Single Cell Point to Multipoint,长期演进单小区点到多点。
MTCH:Multicast Traffic Channel,多播业务信道。MBS组播(或组播通信业务)是指相同的服务和相同的特定内容被同时提供给一组特定的UE。使用组播会话将一个组播通信业务递送给UE。
一个处于RRC_CONNECTED的UE可以采用PTP和/或PTM来接收一个组播通信业务。
G-RNTI:Group RNTI,群组RNTI,用于加扰MTCH的调度和传输(used to scramble the scheduling and transmission of MTCH)。NR MBS支持G-RNTI和MBS会话之间1-1映射关系(One-to-one mapping between G-RNTI and MBS session is supported in NR MBS)。
关联的PDU会话:一个关联到多播会话(也称MBS会话)的PDU会话,所述PDU会话用于5G核心网5GC单播MBS流量传递方法(5GC Individual MBS traffic delivery method)和用于与用户参与多播会话(如加入和离开请求)相关的信令。
关联的QoS流:属于关联的PDU会话的单播QoS流,用于5GC单播MBS流量传递方法,关联的QoS流是从组播MBS会话中的组播QoS流映射而来。
本发明中,网络、基站和RAN可互换使用,所述网络可以是长期演进LTE网络、NR网络、增强的长期演进eLTE网络,也可以是3GPP后续演进版本中定义的其他网络。
在LTE SC-PTM中,基站通过***信息及SC-MCCH信道上传输的消息广播其支持的多媒体广播多播服务MBMS业务及其调度信息,用于传输MBMS业务的无线承载配置信息是预定义的。UE通过接收对应的***信息和SC-MCCH上传输的消息就可以知道当前小区或基站支持或正在进行的MBMS业务。当UE需要接收某个MBMS业务时,按照预定义的参数建立无线承载并接收数据。在这种情况下,UE不需要建立RRC连接就可以接收MBMS业务。
在NR MBS中,一部分MBS业务(service)也可采用与SC-PTM类似的方式调度,使得处于RRC空闲态和RRC非激活态的UE也可以接收所述MBS业务。但是,还存在另一部分MBS业务需要UE与基站建立RRC连接,然后基站通过专用RRC信令(也称为专用RRC消息)为UE配置,并且接收这些MBS业务的无线承载也可由基站通过专用RRC信令为UE配置。图1的(a)~(c)是表示接收MBS业务的无线承载的具体配置的示意图。所述无线承载可以是仅配置了PTM传输的MRB(如图1的(a)所示),或者同时配置了PTM和PTP的分离MRB(split MRB)(如图1的(b)所示)或者仅配置了PTP传输的MRB(如图1的(c)所示)。需要说明的是,图1的(a)-(c)仅示出了承载对应的PDCP实体和RLC实体以及两者间的关系。在下行方向上,经PDCP实体封装后的PDCP PDU递交给RLC实体。
对于UE需要与基站建立RRC连接才能进行的MBS业务,当UE从 一个支持MBS的基站(源基站)切换到不支持MBS的基站(目标基站),如何保证MBS业务的连续性、减少数据丢失是需要解决的问题。
在现有基于Xn接口的切换中,源基站(或称源NG-RAN节点)向目标基站(或称目标NG-RAN节点)发送切换请求(HANDOVER REQUEST)消息,用于在目标基站中建立必要的资源。切换请求消息中包含RRC Context字段,所述字段用于包含HandoverPreparationInformation消息。在切换准备中,HandoverPreparationInformation消息被用来传输目标基站在切换准备期间所使用的NR RRC信息(is used to transfer the NR RRC information used by the target gNB)。所述HandoverPreparationInformation消息中包含完全由源基站生成的RRCReconfiguration配置(Contains the RRCReconfiguration configuration as generated entirely by the source gNB)。目标基站向源基站发送切换请求确认(HANDOVER REQUEST ACKNOWLEDGE)消息作为应答消息,其中包含目标基站(即目标NG-RAN节点)到源基站(即源NG-RAN节点)透明容器(Target NG-RAN node to Source NG-RAN node Transparent Container)字段,所述字段用于携带HandoverCommand消息,而所述HandoverCommand消息携带由目标基站生成的RRCReconfiguration(RRC重配置)消息,源基站在接收到所述切换请求确认消息后将由目标基站生成的RRCReconfiguration消息转发给UE。所述切换请求消息由源基站发送到目标基站,以请求为切换准备资源;所述切换请求确认消息由目标基站发送,以通知源基站目标上已准备好的资源。将处于RRC连接态的UE从支持MBS的源基站切换到不支持MBS的目标基站时,由于目标基站不能识别MBS相关的配置信息,由目标基站生成的RRCReconfiguration消息中将包含fullConfig字段,所述fullConfig字段用于指示将完整配置选项应用于RRCReconfiguration消息。在完整配置中,UE将释放所有的DRB和MRB,这将无法实现服务连续性和/或导致数据丢失。
图2是根据本发明的实施方式的由基站执行的进行小区切换的方法的流程图。
如图2所示,在S202,源基站可以基于源基站与所述目标基站之间所建立的网络接口的接口参数信息来确定目标基站是否支持MBS会话,小区切换请求消息用于请求目标基站为用户设备准备RRC资源。该网络接口例如是Xn接口。
如果目标基站不支持MBS会话,则在S204,源基站不在小区切换请求消息中携带源基站针对用户设备而配置的与MBS会话相关的RRC配置信息。
在S206,源基站可以将与MBS会话相关的RRC配置信息变更为与目标基站所支持的PDU会话相关的RRC配置信息,并将变更后的RRC配置信息携带在小区切换请求消息中发送给目标基站。作为示例,源基站可以将针对MBS会话而配置的MRB的信息修改为映射到该MRB的DRB的信息,并携带在小区切换请求消息中发送给目标基站。
目标基站可以在接收到小区切换请求消息之后,基于携带在小区切换请求消息中的RRC重配置信息而生成第二RRC重配置信息,并将该第二RRC重配置信息携带在作为应答消息的切换请求确认消息中发送给源基站。在一个示例中,在接收到目标基站响应于小区切换请求消息而发送的切换请求确认消息时,源基站可以基于切换请求确认消息中携带的第二RRC重配置信息,来生成用于用户设备切换到目标基站的第一RRC重配置信息,并将所生成的第一RRC重配置信息发送给用户设备。
如果目标基站支持MBS会话,则源基站可以在S208,向目标基站发送携带与MBS会话相关的RRC配置信息的小区切换请求消息。在接收到来自目标基站的切换请求确认消息时,可以不生成第一RRC重配置消息而是将切换请求确认消息中携带的第二RRC配置消息直接发送给UE。
以下描述源基站和目标基站所执行的操作的实施例。
当目标基站不支持MBS时,为了实现服务连续性和/或减少数据丢失,源基站在提供给目标基站的HandoverPreparationInformation消息中包含的RRCReconfiguration配置中就不应提供MBS的配置信息,例如MBS会话的信息和MRB的配置信息等。
在一个实施例中,源基站将MBS会话关联的PDU会话相关信息包含在切换请求消息中,例如包含在待建立的PDU会话资源列表(PDU Session Resources To Be Setup List)字段中,所述字段包含PDU会话资源相关的信息,例如包含PDU会话ID(为UE标识一个PDU会话)、PDU会话类型、待建立的QoS流列表等,所述待建立的QoS流列表中包含待建立的QoS流的相关信息,所述QoS流的相关信息可包含QoS流标识(在一个PDU会话中标识一个QoS流)、QoS流级别的QoS参数等。在提供给目标基站的RRCReconfiguration配置中将MBS会话相关的配置信息删除,例如将mrb-ToAddModList(新增修改MRB列表)和/或关联到MRB的RLC-BearerConfig等相关信息删除。目标基站为包含在待建立的PDU会话资源列表中的MBS会话所关联的PDU会话配置对应的DRB,并将所配置的DRB信息通过包含在目标基站生成的RRCReconfiguration消息(称为第二RRCReconfiguration消息或第二RRC重配置消息)中,经源基站转发给UE。可选的,源基站在接收到切换请求确认消息时,生成RRCReconfiguration消息(称为第一RRCReconfiguration消息或第一RRC重配置消息),所述第一RRC重配置消息中包含用于携带第二RRC重配置消息的字段mbsToNonMBSNode(通过该字段来指示将要执行的小区切换是从支持MBS会话的基站向不支持MBS会话的基站切换)和用于指示释放MRB的字段mrb-ToReleaseList(即,要释放的MRB信息),mrb-ToReleaseList中包含所有需要释放的MRB的MRB-Identity。可以规定mbsToNonMBSNode是配置mrb-ToReleaseList的条件,即只有mbsToNonMBSNode出现,才可以配置mrb-ToReleaseList,反之亦然。
在一个实施例中,源基站将MBS会话关联的PDU会话相关信息包含在切换请求消息中,例如包含在待建立的PDU会话资源列表(PDU Session Resources To Be Setup List)字段中,所述字段包含PDU会话资源相关的信息,例如包含PDU会话ID(为UE标识一个PDU会话)、PDU会话类型、待建立的QoS流列表,源基站QoS流到DRB的映射等,所述待建立的QoS流列表中包含待建立的QoS流的相关信息,所述QoS流的相关信息可包含QoS流标识(在一个PDU会话中标识一个QoS流)、QoS流 级别的QoS参数等。在提供给目标基站的RRCReconfiguration配置中将MBS会话相关的配置信息删除和/或将MRB相关的配置信息修改为对应的DRB,使得目标基站能将所述DRB当作源基站已经为UE配置的DRB来处理。例如,为每个MRB分配一个DRB ID(即drb-Identity,DRB标识),将MRB ID(即mrb-Identity,MRB标识)修改为对应的DRB ID;和/或将MRB关联的MBS会话标识修改为所述MBS会话关联的PDU会话标识;和/或对于仅关联PTM RLC的MRB,将MRB ID修改为DRB ID和/或删除对应的G-RNTI和/或删除PTM传输的指示标识(即所述指示标识指示对应的RLC实体是为PTM传输配置的);和/或对于同时关联的PTM RLC和PTP RLC的MRB,删除PTM RLC相关的配置信息和/或删除对应的G-RNTI;和/或存储MRB与DRB之间的映射关系。对于关联到一个MBS会话的PDU会话,其对应的源基站QoS流到DRB的映射是指关联的PDU会话的关联的QoS流到DRB的映射。目标基站向源基站发送切换请求确认消息作为应答消息。其中,源基站提供给目标基站的RRCReconfiguration配置消息包含在切换请求消息携带的HandoverPreparationInformation消息中。
以下参考图3~5来说明本发明的实施例涉及的由用户设备执行的进行小区切换的方法。
图3是根据本发明的实施方式的由用户设备执行的进行小区切换的方法的流程图。
如图3所示,在S302,用户设备从源基站接收由源基站生成的针对该用户设备的第一RRC重配置消息。第一RRC重配置消息中携带有由目标基站生成的第二RRC重配置消息,第一RRC重配置消息还可以包括针对多播广播业务会话即MBS会话的MRB与针对PDU会话的DRB之间的映射关系信息。作为示例,该映射关系信息可以是是DRB标识与MRB标识之间的映射,也可以是MBS会话标识与PDU会话标识之间的映射,还可以是DRB标识与MRB标识之间的映射以及MBS会话标识与PDU会话标识之间的映射。第二RRC重配置消息是如前述那样,由目标基站响应于源基站发送的小区切换请求消息而生成并发送给源基站的。
在S304,用户设备可以基于第二RRC重配置消息和/或映射关系信息,将用户设备的与MBS会话相关的RRC配置,重配置为与目标基站支持的PDU会话相关的RRC配置。
在本发明的实施方式中,该重配置操作可以包括以下中的至少一项:基于第二RRC重配置消息和/或所述映射关系信息,将所述用户设备的与MBS会话相关的RRC配置,重配置为与所述目标基站支持的PDU会话相关的RRC配置包括以下中的至少一项:基于所述映射关系信息,将针对MBS会话的MRB标识替换为映射到该MRB的DRB标识;基于所述映射关系信息,将MRB映射到的DRB关联到与该MRB关联的SDAP实体;基于所述映射关系信息,将MBS会话标识修改为关联到所述MBS会话的PDU会话的PDU会话标识;向上层指示释放MBS会话的用户面资源;向上层指示建立PDU会话的用户面资源;向上层指示将与MBS会话相关的用户面资源修改为与映射到针对所述MBS会话的MRB的DRB关联的PDU会话的用户面资源;对于被配置了PTM RLC实体的MRB,指示该PTM RLC实体释放PTM传输指示标识。
用户设备可以基于映射关系信息来执行重配置,例如,可以针对映射关系信息所指示的各个DRB,执行以下中的至少一项:如果映射到该DRB的MRB是被配置了PTM RLC实体和PTP RLC的分离MRB,则释放该PTM RLC实体对应的PTM RLC承载;如果映射到该DRB的MRB是仅被配置了PTM RLC实体的PTM MRB,则释放该PTM RLC实体的PTM传输指示标识;如果映射到该DRB的MRB是仅被配置了PTM RLC实体的PTM MRB或仅被配置了PTP RLC实体的PTP MRB,则将与映射到该DRB的MRB关联的PTM RLC或PTP RLC实体关联到该DRB。
对于基于MRB和DRB之间的映射关系而确定出的未映射到任何DRB的MRB,用户设备可以释放与该MRB相关的信息。
在另一示例中,在目标基站不支持MBS会时,源基站可以在第一RRC重配置消息中携带用于指示目标基站不支持MBS会话的字段。在该示例中,用户设备也可以确定第一RRC重配置包括该字段时,解析出第二RRC重配置,并进行重配置。以下参照图4来对该示例进行说明。
图4是根据本发明的实施方式的由用户设备执行的进行小区切换的方 法中的解析出第二RRC重配置消息过程的流程图。
在S402,用户设备可以在接收到所述第一RRC重配置消息时,判断第一RRC重配置消息是否包括用于指示目标基站不支持MBS会话的字段。
如果第一RRC重配置消息包括该字段,则用户设备可以在S404,对该字段进行解析,从该字段中解析出第二RRC重配置消息。然而,用户设备可以执行重配置操作。如果第一RRC重配置不包括上述字段,也可以不执行进一步的操作。
第二RRC重配置消息可以包括DRB变更信息,DRB变更信息包括目标基站指示需要变更的DRB的信息。此处所说的“变更”可以包括删除、修改、新增、释放等各种变更操作。相应地,DRB变更信息可以包括表示要修改的DRB的信息的DRB修改信息,也可以包括表示要新增的DRB的信息的要新增DRB信息,还可以包括表示要释放的DRB的信息的要释放DRB信息。这样的信息可以是列表形式,例如可以相应DRB的DRB标识的列表。此时,可以按照图5的流程来执行重配置。图5是根据本发明的实施方式的由用户设备执行的进行小区切换的方法中的重配置过程的具体示例的流程图。
在S502~S504,用户设备可以针对DRB变更信息所指示的各个DRB,确定该DRB是否被包括在用户设备的既有RRC配置中。
如果该DRB未被包括在用户设备的既有RRC配置中,则用户设备可以在S506,基于映射关系信息,确定是否存在映射到该DRB的MRB;
如果不存在映射到该DRB的MRB,则用户设备可以在S506,建立该DRB。如果存在映射到该DRB的MRB,则用户设备可以在S508,针对映射到该DRB的MRB进行重配置。
如上所述,DRB变更信息包括新增修改DRB列表,新增修改DRB列表包括目标基站要求新增或修改的DRB的信息。此时,上述S508中所述的针对映射到该DRB的MRB进行重配置包括如果该DRB被包括在所述新增修改DRB列表中,则执行以下中的至少一项:如果映射到该DRB的MRB与PTM RLC实体关联,则指示该PTM RLC实体释放PTM传输指示标识和/或对应的群组无线网络临时标识;如果所述RRC重配置信息包括PDCP重建指示,则重建映射到该DRB的MRB的PDCP实体;如果 所述RRC重配置信息包括PDCP恢复指示,则使映射到该DRB的MRB的PDCP实体执行数据恢复;如果所述RRC重配置信息包括PDCP重配置信息,则根据所述PDCP重配置信息,对映射到DRB的MRB的PDCP实体进行重配置;如果所述RRC重配置信息包括SDAP重配置信息,则根据所述SDAP配置信息对映射到该DRB的MRB的SDAP实体进行重配置;对于与映射到该DRB的MRB所对应的MBS会话,则将该MBS会话标识修改为对应于该DRB的PDU会话标识;释放或丢弃所述用户设备的既有RRC配置中的MRB标识。
DRB变更信息还可以包括要释放DRB列表,要释放DRB列表包括目标基站要求释放的DRB的信息。此时,S508中的操作可以通过以下来执行。如果该DRB被包括在所述要释放DRB列表中,则释放映射到该DRB的MRB的PDCP实体的MRB标识。如果映射到该DRB的MRB被配置有对应的SDAP实体,用户设备还可以指示SDAP实体释放映射到该DRB的MRB。
以下描述UE执行切换时的操作的实施例
在一个实施例中,UE从基站(即源基站)接收第一RRCReconfiguration消息(第一RRC重配置消息),第一RRCReconfiguration消息可以包括MRB变更信息。此处所说的“变更”可以包括删除、修改、新增、释放等各种变更操作。MRB变更信息可以包括要释放MRB的信息,还可以包括要新增或修改的新增修改MRB信息。这些信息可以是包括MRB标识的列表形式。如果所述消息中包含mrb-ToReleaseList(要释放MRB列表信息),则对于每个包含在mrb-ToReleaseList中的mrb-Identity(MRB标识),如果所述mrb-Identity是当前UE配置的一部分,则释放对应的PDCP实体和mrb-Identity,和/或向上层指示这个MRB被释放和被释放的MRB的字段tmgi。其中,字段tmgi用于指示承载关联的MBS会话,其取值为TMGI。
在一个实施例中,UE从基站(即源基站)接收RRCReconfiguration消息,如果所述RRCReconfiguration消息中包含reconfigurationWithSync字段并且目标基站不支持MBS,对于当前配置的每个mrb-Identity,释放 对应的PDCP实体和mrb-Identity,和/或向上层指示这个MRB被释放和被释放的MRB的tmgi,和/或释放关联到MRB的RLC实体或RLC承载。其中,reconfigurationWithSync字段包含同步重配置到目标SpCell的相关参数,tmgi用于指示承载关联的MBS会话。所述“目标基站不支持MBS”可以替换为“UE接收到的包含reconfigurationWithSync字段的RRCReconfiguration消息中不包含任何MRB的配置”或者“在接收到的RRCReconfiguration消息中不包含用于指示基站支持MBS的字段mbsSupporting”。可选的,在切换的过程中,如果目标基站支持MBS,则在由目标基站生成的RRCReconfiguration消息中包含mbsSupporting(MBS支持)字段。可选的,在RRCReconfiguration消息中包含一个字段keepMBS用于指示UE保留已配置的MBS,如果接收到的RRCReconfiguration消息中不包含所述字段,对当前配置的每个mrb-Identity或MRB,如果所述mrb-Identity或MRB不包含在接收到的RRCReconfiguration消息,则释放对应的PDCP实体和mrb-Identity,和/或向上层指示这个MRB被释放和被释放的MRB的tmgi,和/或释放关联到MRB的RLC实体或RLC承载。此外,释放RLC承载的具体操作可包括释放RLC实体和释放对应的逻辑信道。
在本发明中向上层指示释放MBS会话的用户面资源和向上层指示被释放的MRB的tmgi可替换使用,得到的实施例也是本发明保护的范围。
在一个实施例中,UE对映射到DRB的每个MRB按照包含在第二RRCReconfiguration消息中的配置信息进行重配置,例如,将MRB的mrb-Identity替换为其映射到的DRB的drb-Identity,和/或将MRB关联的MBS会话标识修改为所述MBS会话关联的PDU会话标识,和/或将映射到该DRB的MRB关联的SDAP实体(或PDCP实体或RLC实体)关联到所述DRB(也可表述为将所述DRB关联到映射到该DRB的MRB关联的SDAP实体(或PDCP实体或RLC实体)),和/或向上层指示释放MBS会话的用户面资源,和/或向上层指示建立PDU会话的用户面资源,和/或向上层指示改变MBS会话的用户面资源为关联的PDU会话的用户面资源,和/或对于同时关联了PTM传输和PTP传输的分离MRB,释放PTM RLC实 体(或释放PTM RLC承载),对于仅配置了PTM传输的MRB,释放PTM传输指示标识。以下具体描述:
UE从基站(即源基站)接收第一RRCReconfiguration消息,所述第一RRCReconfiguration消息中包含MBS会话和关联的PDU会话间的映射关系和/或MRB ID(即MRB-Identity)和DRB ID(即DRB-Identity)间的映射关系的mrbToDrbMappingList字段,所述第一RRCReconfiguration消息中还包含mbsToPduRRCReconfig字段,所述字段用于携带由目标基站生成的第二RRCReconfiguration消息。
对于包含在第二RRCReconfiguration消息中的drb-ToAddModList(新增修改DRB列表)中的每个drb-Identity,如果所述drb-Identity不是当前UE配置的一部分,也没有映射到一个MRB(即drb-Identity没有包含在mrbToDrbMappingList字段中),则建立对应的DRB(具体按照3GPP技术规范TS38.331中定义的建立DRB的方法建立)。
对于包含在第二RRCReconfiguration消息中的drb-ToAddModList中的每个drrb-Identity,如果所述drb-Identity不是当前UE配置的一部分,但该drb-Identity映射到一个MRB(即drb-Idntity包含在mrbToDrbMappingList字段中),则执行以下操作(1-8)至少一项:
1)如果映射到该DRB的MRB是一个分离MRB(即同时关联了一个PTM RLC和一个PTP RLC),则释放PTM RLC承载,具体包括按时TS38.322中5.1.3节定义的操作释放RLC实体并释放对应的逻辑信道。
2)如果映射到该DRB的MRB关联(即仅关联)一个PTM RLC实体,释放PTM传输指示标识和/或对应的G-RNTI或指示PTM RLC实体(或PTM RLC承载)释放PTM传输指示标识和/或对应的G-RNTI。该操作的目的是使UE不再监测MBS的PTM传输。
3)如果reestablishPDCP被设置,则执行(1a-1f)至少一项:
(1a)如果映射到这个DRB的MRB的PDCP实体没有被配置cipheringDisabled,使用与主密钥(K
eNB/K
gNB)或辅密钥(S-K
gNB/S-K
eNB)相关联的加密算法和K
UPenc密钥配置PDCP实体, 如keyToUse中所指示的,即加密配置将应用于终端接收和发送的所有后续PDCP PDU;
(1b)如果映射到这个DRB的MRB的PDCP实体被配置了integrityProtection,根据securityConfig配置PDCP实体的完整性保护算法,并应用keyToUse中指示的主密钥(K
gNB)或辅密钥(S-K
gNB)关联的K
UPint密钥;
(1c)如果drb-ContinueROHC包含在pdcp-Config中,指示下层被配置了drb-ContinueROHC;
(1d)如果drb-ContinueEHC-DL包含在pdcp-Config中,指示下层被配置了drb-ContinueEHC-DL;
(1e)如果drb-ContinueEHC-UL包含在pdcp-Config中,指示下层被配置了drb-ContinueEHC-UL;可规定此配置不用于MRB映射到的DRB。
(1f)重建映射到这个DRB的MRB的PDCP实体,具体操作见3GPP技术规范TS 38.323中5.1.2节所述。当加密算法或密钥发生改变和/或完整性保护算法或密钥发生改变等,基站将指示UE重建PDCP实体。
4)如果recoverPDCP被设置,触发映射到这个DRB的MRB的PDCP实体执行数据恢复,具体操作见3GPP技术规范TS 38.323所述。注,本操作步骤可不应用于关联的PDU对应的DRB。当加密算法或密钥未发生改变和/或完整性保护算法或密钥未发生改变等,为了减少数据丢失,需要重传已经发送但尚未确认发送成功的数据时,可以指示PDCP实体执行数据恢复。
5)如果其中包含pdcp-Config,根据接收到的pdcp-Config重配置映射到这个DRB的MRB的PDCP实体。当目标基站不能支持或需要修改当前pdcp-Config中的部分参数的配置时,可以发送包含新的PDCP实体配置信息的pdcp-Config,以重配置PDCP实体。
6)如果其中包含sdap-Config,则执行以下操作(4a-4b)至少一项:
(4a)如果接收到的PDU会话的SDAP实体在接收到这个重配置消息前尚未建立,向上层指示建立的PDU会话的用户面资源。
(4b)根据接收到的sdap-Config,重配置映射到这个DRB的MRB的SDAP实体,具体根据TS37.324定义的操作执行。当目标基站不能支持或需要修改当前sdap-Config中的部分参数的配置时,可以发送包含新的SDAP实体配置信息的sdap-Config,以重配置SDAP实体。
7)如果映射到这个DRB的MRB关联的SDAP实体关联一个MBS会话,则设置pdu-session为关联的PDU会话的PDU-SessionID,和/或释放mbs-Session(或MBS-SessionID),和/或向上层指示释放这个mbs-Session的用户面资源。此操作的目的是将MBS会话标识修改为关联的PDU会话标识。
8)释放/丢弃MRB-Identity。
需要说明的是,交换上述各操作的执行顺序得到的实施例也是本发明保护的范围。此外,操作1和2可以不包含在上述针对无线承载配置的描述中。操作1可以在RLC承载释放的相关描述中描述,操作2可以放在RLC承载增加/修改相关描述中描述。
对于包含在mrbToDrbMappingList中的每个drb-Identity对应的DRB,执行以下操作A-C至少一项:
A)如果映射到该DRB的MRB是一个分离MRB(即同时关联了一个PTM RLC和一个PTP RLC),则释放PTM RLC承载。具体包括按TS38.322中5.1.3节定义的操作释放RLC实体并释放对应的逻辑信道。
B)如果映射到该DRB的MRB关联(即仅关联)一个PTM RLC实体,释放(或指示PTM RLC实体释放)PTM传输指示标识和/或对应的G-RNTI。
C)将映射到该DRB的MRB关联的RLC实体关联到所述DRB。对于仅配置了PTP RLC实体的PTP MRB,该RLC是指PTP RLC,对于仅配置了PTM RLC实体的PTM MRB,该RLC是指PTM RLC。
需要说明的是,交换上述各操作的执行顺序得到的实施例也是本发明保护的范围。
对于没有映射到任何DRB的MRB(即不包含在mrbToDrbMappingList中的每个mrb-Identity对应的MRB),释放所述MRB,具体包括释放PDCP实体和mrb-Identity,向上层指示MRB的释放和所释放的MRB的tmgi。
对于包含在第二RRCReconfiguration消息中的drb-ToReleaseList(要释放DRB信息)中的每个drb-Identity,如果所述drb-Identity不是当前UE配置的一部分,但该drb-Identity映射到一个MRB(即drb-Idntity包含在mrbToDrbMappingList字段中),则执行以下操作I-II至少一项:
I:释放映射到此DRB和MRB的PDCP实体的mrb-Identity。
II:如果为映射到此DRB的MRB配置了关联的SDAP实体,向所述SDAP实体指示释放映射到此DRB的MRB。
需要说明的是,交换上述各操作的执行顺序得到的实施例也是本发明保护的范围。
以下对本发明所涉及的部分字段描述如下:drb-ToAddModList用于指示一组增加或修改的DRB的配置信息;mrbToDrbMappingList用于指示每个MRB所映射到的DRB或者mrb-Identity与drb-Identity间的映射关系,所述DRB的PDU会话是所述MRB的MBS会话的关联的PDU会话,如果UE事先(例如在配置MEB时)已经被配置了MBS会话和关联的PDU会话,则mrbToDrbMappingList中不需要包含MBS会话和关联的PDU会话,否则需要包含,MBS会话和关联的PDU会话的信息也可以包含在另一个不同于mrbToDrbMappingList的字段mbsSessionToPduSessionMappinglist中,用于指示MBS会话和关联的PDU会话之间的关联关系;drb-Identity被用于标识UE使用的DRB;mrb-Identity被用于标识UE使用的MRB;reestablishPDCP用于指示应重建PDCP实体;cipheringDisabled用于指示无论为无线承载配置了哪种加密算法,此无线承载都禁用加密;integrityProtection指示是否为此无线承载配置了完整性保护;securityConfig指示RadioBearerConfig中配置的无线承载所使用的安全算法和密钥;keyToUse指示在RadioBearerConfig中配置的承载使用主密钥或辅密钥来派生加密和完整性保护的密钥;drb-ContinueROHC用于指示PDCP实体在PDCP重建期间是继续还是重置ROHC报头压缩协议; drb-ContinueEHC-DL用于指示PDCP实体在PDCP重建期间是继续还是重置下行EHC报头压缩协议;drb-ContinueEHC-UL用于指示PDCP实体在PDCP重建期间是继续还是重置上行EHC报头压缩协议;recoverPDCP用于指示PDCP应按照TS38.323定义的操作执行恢复;pdcp-Config用于为DRB或MRB设置可配置的PDCP参数;sdap-Config用于为DRB或MRB设置可配置的SDAP参数;pdu-session是QoS流映射到这个DRB的关联的PDU会话的标识;mbs-Session是QoS流映射到这个MRB的PDU会话的标识。
本发明中,MRB和DRB之间是一一映射。drb-Identity映射到MRB、drb-Identity映射到mrb-Identity、DRB映射到MRB均表示将这个DRB是由MRB映射得到的,即drb-Idntity包含在mrbToDrbMappingList字段中。
本发明中,字段也可称为信息元素IE。
本发明实施例中PTM RLC实体也称为PTM关联的RLC实体或配置了G-RNTI的RLC实体或关联了G-RNTI的RLC实体或用于PTM传输的RLC实体;PTP RLC实体也称为PTP关联的RLC实体或用于PTP传输的RLC实体。
需要说明的是,一个MBS业务(或称为MBS会话)可通过一个MBS标识来标识,所述MBS标识可以是TMGI和/或会话标识sessionId,其中TMGI可以包括PLMN标识和/或服务标识,所述服务标识在一个PLMN内唯一标识一个MBS业务。
图6是根据本发明的实施方式的用于执行进行小区切换的方法的用户设备的结构框图。
如图6所示,该用户设备600至少包括处理器601和存储器602。处理器601例如可以包括微处理器、微控制器、嵌入式处理器等。存储器602例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器***等。存储器602上存储有程序指令。该指令在由处理器601运行时,可以执行本发明的上述图3~5所描述的方法中的一个或几个步骤。
另外,运行在根据本发明的设备上的计算机可执行指令或者程序可以 是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器***中。
用于实现本发明各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机***读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机***”可以是嵌入在该设备中的计算机***,可以包括操作***或硬件(如***设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如,单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器,也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路,也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下,本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外,本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例,但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备,如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上,已经参考附图对本发明的实施例进行了详细描述。但是,具体的结构并不局限于上述实施例,本发明也包括不偏离本发明主旨的任何设计改动。另外,可以在权利要求的范围内对本发明进行多种改动,通过适当地组合不同实施例所发明的技术手段所得到的实施例也包含在本发明的技术范围内。此外,上述实施例中所描述的具有相同效果的组件可以相互替代。
Claims (10)
- 一种由用户设备执行的进行小区切换的方法,包括:从源基站接收由所述源基站生成的针对所述用户设备的第一RRC重配置消息,所述第一RRC重配置消息中携带有由目标基站生成的第二RRC重配置消息,所述第一RRC重配置消息还包括针对多播广播业务会话即MBS会话的MRB与针对PDU会话的DRB之间的映射关系信息;以及基于所述第二RRC重配置消息和/或所述映射关系信息,将所述用户设备的与MBS会话相关的RRC配置,重配置为与所述目标基站支持的PDU会话相关的RRC配置,所述第二RRC重配置消息是所述目标基站响应于所述源基站发送的小区切换请求消息而生成并发送给所述源基站的。
- 根据权利要求1所述的方法,其中,在执行重配置操作之前,所述方法还包括:在接收到所述第一RRC重配置消息时,判断所述第一RRC重配置消息是否包括用于指示所述目标基站不支持MBS会话的字段;以及如果所述第一RRC重配置消息包括所述字段,则对所述字段进行解析,从所述字段中解析出所述第二RRC重配置消息。
- 根据权利要求1所述的方法,其中,基于所述第二RRC重配置消息和/或所述映射关系信息,将所述用户设备的与MBS会话相关的RRC配置,重配置为与所述目标基站支持的PDU会话相关的RRC配置包括:针对所述映射关系信息所指示的各个DRB,执行以下中的至少一项:如果映射到该DRB的MRB是被配置了PTM RLC实体和PTP RLC实体的分离MRB,则释放该PTM RLC实体对应的PTM RLC承载;如果映射到该DRB的MRB是仅被配置了PTM RLC实体的PTM MRB,则释放该PTM RLC实体的PTM传输指示标识;如果映射到该DRB的MRB是仅被配置了PTM RLC实体的PTM MRB 或仅被配置了PTP RLC实体的PTP MRB,则将与映射到该DRB的MRB关联的PTM RLC或PTP RLC实体关联到该DRB。
- 根据权利要求1-3中任一项所述的方法,其中,所述第二RRC重配置消息包括DRB变更信息,所述DRB变更信息包括所述目标基站指示需要变更的DRB的信息,基于所述第二RRC重配置消息和/或所述映射关系信息,将所述用户设备的与MBS会话相关的RRC配置,重配置为与所述目标基站支持的PDU会话相关的RRC配置包括:针对所述DRB变更信息所指示的各个DRB,确定该DRB是否被包括在所述用户设备的既有RRC配置中;如果该DRB未被包括在所述用户设备的既有RRC配置中,则基于所述映射关系信息,确定是否存在映射到该DRB的MRB;如果不存在映射到该DRB的MRB,则建立该DRB;如果存在映射到该DRB的MRB,则针对映射到该DRB的MRB进行重配置。
- 根据权利要求4所述的方法,其中,所述DRB变更信息包括新增修改DRB列表,新增修改DRB列表包括所述目标基站要求新增或修改的DRB的信息,针对映射到该DRB的MRB进行重配置包括:如果该DRB被包括在所述新增修改DRB列表中,则执行以下中的至少一项:如果映射到该DRB的MRB与PTM RLC实体关联,则指示该PTM RLC实体释放PTM传输指示标识和/或对应的群组无线网络临时标识;如果所述RRC重配置信息包括PDCP重建指示,则重建映射到该DRB的MRB的PDCP实体;如果所述RRC重配置信息包括PDCP恢复指示,则使映射到该DRB的MRB的PDCP实体执行数据恢复;如果所述RRC重配置信息包括PDCP重配置信息,则根据所述PDCP重配置信息,对映射到DRB的MRB的PDCP实体进行重配置;如果所述RRC重配置信息包括SDAP重配置信息,则根据所述SDAP 配置信息对映射到该DRB的MRB的SDAP实体进行重配置;对于与映射到该DRB的MRB所对应的MBS会话,则将该MBS会话标识修改为对应于该DRB的PDU会话标识;释放或丢弃所述用户设备的既有RRC配置中的MRB标识。
- 根据权利要求4所述的方法,其中,所述DRB变更信息包括要释放DRB列表,所述要释放DRB列表包括所述目标基站要求释放的DRB的信息,针对映射到该DRB的MRB进行重配置包括:如果该DRB被包括在所述要释放DRB列表中,则执行:释放映射到该DRB的MRB的PDCP实体的MRB标识;和/或如果映射到该DRB的MRB被配置有对应的SDAP实体,则指示所述SDAP实体释放映射到该DRB的MRB。
- 根据权利要求1-3中任一项所述的方法,其中,基于所述第二RRC重配置消息和/或所述映射关系信息,将所述用户设备的与MBS会话相关的RRC配置,重配置为与所述目标基站支持的PDU会话相关的RRC配置还包括:对于基于MRB和DRB之间的映射关系而确定出的未映射到任何DRB的MRB,释放与该MRB相关的信息。
- 一种由源基站执行的进行小区切换的方法,包括:所述源基站在向目标基站发送所述小区切换请求消息时,基于所述源基站与所述目标基站之间所建立的网络接口的接口参数信息来确定所述目标基站是否支持MBS会话,所述小区切换请求消息用于请求所述目标基站为用户设备准备RRC资源;如果所述目标基站不支持MBS会话,则不在所述小区切换请求消息中携带所述源基站针对所述用户设备而配置的与MBS会话相关的RRC配置信息;以及将与MBS会话相关的RRC配置信息变更为与所述目标基站所支持的PDU会话相关的RRC配置信息,并将变更后的RRC配置信息携带在所述 小区切换请求消息中发送给所述目标基站。
- 根据权利要求8所述的方法,还包括:将针对MBS会话而配置的MRB的信息修改为映射到该MRB的DRB的信息,并携带在所述小区切换请求消息中发送给所述目标基站;和/或在接收到所述目标基站响应于所述小区切换请求消息而发送的切换请求确认消息时,基于所述切换请求确认消息中携带的第二RRC重配置信息,来生成用于所述用户设备切换到所述目标基站的第一RRC重配置信息,并将所生成的第一RRC重配置信息发送给所述用户设备,所述第二RRC重配置信息由所述目标基站基于携带在所述小区切换请求消息中的RRC重配置信息而生成。
- 一种用户设备,包括:处理器;以及存储器,存储有指令,其中,所述指令在由所述处理器运行时执行根据权利要求1至7中任一项所述的处理方法。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202111215299.9A CN115996359A (zh) | 2021-10-19 | 2021-10-19 | 进行小区切换的方法及用户设备 |
CN202111215299.9 | 2021-10-19 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023066188A1 true WO2023066188A1 (zh) | 2023-04-27 |
Family
ID=85990729
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/125624 WO2023066188A1 (zh) | 2021-10-19 | 2022-10-17 | 进行小区切换的方法及用户设备 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN115996359A (zh) |
WO (1) | WO2023066188A1 (zh) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111866975A (zh) * | 2020-05-18 | 2020-10-30 | 中兴通讯股份有限公司 | 切换方法及装置、信息发送方法及装置 |
WO2021162315A1 (ko) * | 2020-02-14 | 2021-08-19 | 주식회사 케이티 | Mbs 데이터를 처리하는 방법 및 그 장치 |
WO2021162333A1 (ko) * | 2020-02-14 | 2021-08-19 | 주식회사 케이티 | Mbs 데이터를 처리하는 방법 및 그 장치 |
-
2021
- 2021-10-19 CN CN202111215299.9A patent/CN115996359A/zh active Pending
-
2022
- 2022-10-17 WO PCT/CN2022/125624 patent/WO2023066188A1/zh unknown
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2021162315A1 (ko) * | 2020-02-14 | 2021-08-19 | 주식회사 케이티 | Mbs 데이터를 처리하는 방법 및 그 장치 |
WO2021162333A1 (ko) * | 2020-02-14 | 2021-08-19 | 주식회사 케이티 | Mbs 데이터를 처리하는 방법 및 그 장치 |
CN111866975A (zh) * | 2020-05-18 | 2020-10-30 | 中兴通讯股份有限公司 | 切换方法及装置、信息发送方法及装置 |
Non-Patent Citations (2)
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 |
---|---|---|
CN111406415A (zh) | 多播和广播服务的方法和*** | |
US20220408162A1 (en) | Multicast service transmission method and apparatus | |
JP6321830B2 (ja) | 基地局、ユーザ端末及び装置 | |
WO2015100733A1 (zh) | 一种用户设备切换方法及基站 | |
GB2444998A (en) | Dedicated radio resource control | |
JP2023533342A (ja) | 通信方法及び通信装置 | |
WO2023066188A1 (zh) | 进行小区切换的方法及用户设备 | |
WO2023029590A1 (zh) | 一种组播/广播会话管理方法及通信装置 | |
US20230309185A1 (en) | Terminal apparatus, base station apparatus, and method | |
WO2022030456A1 (ja) | 端末装置、基地局装置、および、方法 | |
EP4145937A1 (en) | Terminal device, method, and integrated circuit | |
WO2023036287A1 (zh) | 用户设备执行的方法、基站的传输方法及用户设备 | |
WO2023001240A1 (zh) | 由用户设备ue执行的方法及用户设备 | |
WO2024120475A1 (zh) | 恢复rrc连接的方法以及用户设备 | |
JP7481588B2 (ja) | 通信方法、ユーザ装置、移動通信システム、チップセット、及びプログラム | |
WO2023036173A1 (zh) | 状态报告发送方法、无线承载重传执行方法及用户设备 | |
JP7508634B2 (ja) | 通信制御方法、基地局、ユーザ装置及びプロセッサ | |
JP7494064B2 (ja) | 端末装置、基地局装置、方法、および、集積回路 | |
US20230171565A1 (en) | Terminal apparatus, method, and integrated circuit | |
US20240260118A1 (en) | Terminal apparatus, base station apparatus, and method | |
WO2008052420A1 (fr) | Procédé pour établir, réétablir et supprimer la porteuse d'accès radio d'un service sélectionné | |
CN118175665A (zh) | 由用户设备执行的方法以及用户设备 | |
JP2024102387A (ja) | 端末装置、基地局装置、および方法 | |
JP2024102389A (ja) | 端末装置、基地局装置、および方法 | |
JP2024102386A (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 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |