WO2021233279A1 - 切换方法及装置、信息发送方法及装置 - Google Patents

切换方法及装置、信息发送方法及装置 Download PDF

Info

Publication number
WO2021233279A1
WO2021233279A1 PCT/CN2021/094322 CN2021094322W WO2021233279A1 WO 2021233279 A1 WO2021233279 A1 WO 2021233279A1 CN 2021094322 W CN2021094322 W CN 2021094322W WO 2021233279 A1 WO2021233279 A1 WO 2021233279A1
Authority
WO
WIPO (PCT)
Prior art keywords
mbs
information
bearer
network device
session
Prior art date
Application number
PCT/CN2021/094322
Other languages
English (en)
French (fr)
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 中兴通讯股份有限公司
Priority to KR1020227043470A priority Critical patent/KR20230011340A/ko
Priority to EP21809000.9A priority patent/EP4156727A4/en
Priority to US17/926,231 priority patent/US20230199569A1/en
Publication of WO2021233279A1 publication Critical patent/WO2021233279A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0007—Control or signalling for completing the hand-off for multicast or broadcast services, e.g. MBMS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
    • 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
    • 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

Definitions

  • This application relates to the field of communications, for example, to a switching method and device, and an information sending method and device.
  • Multicast Broadcast Service (MBS) technology as an important implementation of mobile TV, will play an important role in the 5G system and has a great development prospect.
  • Enhanced Multicast Broadcast Multimedia Service (evolved Multicast Broadcast Multimedia Service, eMBMS for short) is a key technology that provides users with real-time/non-real-time multimedia services through multicast/broadcast at the air interface layer.
  • eMBMS can realize the broadcast transmission of high-speed multimedia services, that is, Point to Multipoint (PTM, or broadcast/multicast), and provide rich video, audio, and multimedia services.
  • PTM Point to Multipoint
  • eMBMS in the 5G system can improve the capabilities of the entire broadcasting system, which can support higher speed and more effective 5G broadcasting application scenarios, such as 4K/8K ultra-high-definition video, three-dimensional video, and virtual reality (Virtual Reality, VR)/Augmented Reality (AR) and other high-quality multimedia services.
  • 5G broadcasting application scenarios such as 4K/8K ultra-high-definition video, three-dimensional video, and virtual reality (Virtual Reality, VR)/Augmented Reality (AR) and other high-quality multimedia services.
  • the embodiments of the present invention provide a handover method and device, and an information sending method and device, so as to at least solve the problem of how to implement a handover process across base stations in related technologies.
  • a handover method applied to a first network device includes:
  • the handover request carries broadcast multicast service MBS session/bearer information
  • MBS session/bearer information that the second network device can accept MBS session/bearer information that the second network device cannot accept
  • UE scheduling configuration information of the second network device UE scheduling configuration information of the second network device
  • bearer information of the second network device Configuration information UE scheduling configuration information of the second network device
  • an information sending method is also provided, which is applied to a UE, and the method includes:
  • a handover method applied to a second network device includes:
  • the handover request carries MBS session/bearer information
  • the MBS session information is used to indicate the MBS session
  • the MBS bearer information is used to indicate the MBS bearer
  • the handover response is used to indicate at least one of the following: MBS session/bearer information that can be accommodated by the second network device, and the second network device MBS session/bearer information that the device cannot accept, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.
  • a switching device which is provided in a first network device, and the device includes:
  • the first sending module is configured to send a handover request to the second network device; wherein the handover request carries broadcast multicast service MBS session/bearer information;
  • the first receiving module is configured to receive a handover request response sent by the second network device, where the handover request response includes at least one of the following:
  • MBS session/bearer information that the second network device can accept MBS session/bearer information that the second network device cannot accept
  • UE scheduling configuration information of the second network device UE scheduling configuration information of the second network device
  • bearer information of the second network device Configuration information UE scheduling configuration information of the second network device
  • an information sending device which is set in a UE, and the device includes:
  • the second sending module is configured to send the MBS indication information that the UE is interested in and the MBS indication information that the UE is receiving to the first network device;
  • the second receiving module is configured to receive the RRC reconfiguration information returned by the first network device according to the MBS indication information that the UE is interested in.
  • a switching device which is provided in a second network device, and the device includes:
  • the third receiving module is configured to receive a handover request sent by the first network device; wherein the handover request carries MBS session/bearer information, the MBS session information is used to indicate an MBS session, and the MBS bearer information is used to Indicate MBS bearer;
  • the return module is configured to return a switching response to the first network device according to the switching request, wherein the switching response is used to indicate at least one of the following: MBS session/bearer information that the second network device can accept, MBS session/bearer information that the second network device cannot accept, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.
  • a computer-readable storage medium and a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute any one of the foregoing when running. The steps in the method embodiment.
  • an electronic device including a memory and a processor, the memory is stored with a computer program, and the processor is configured to run the computer program to execute any of the above Steps in the method embodiment.
  • the first network device can be made to send a switching request to the second network device; wherein, the switching request carries MBS session/bearer information, and MBS session information Used to indicate MBS sessions, MBS bearer information is used to indicate MBS bearers; and to make the first network device receive a handover request response sent by the second network device, the handover request response includes at least one of the following: MBS sessions that can be accommodated by the second network device /Bearer information, MBS sessions/bearer information that the second network device cannot accept, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.
  • the handover method and device, and the information sending method and device in the embodiments of the present invention can solve the problem of how to realize the handover process across base stations in the related technology, so as to realize the effective guarantee of broadcast/multiple transmission during the handover process between the base stations.
  • Figure 1 is a schematic diagram of the architecture of a wireless network system according to an embodiment of the present invention
  • FIG. 2 is a block diagram of the hardware structure of a mobile terminal according to an embodiment of the present invention.
  • Fig. 3 is a flowchart of a handover method according to an embodiment of the present invention.
  • Fig. 4 is a flowchart of an information sending method according to an embodiment of the present invention.
  • Fig. 5 is a flowchart of a handover method according to an embodiment of the present invention.
  • Fig. 6 is an interactive flowchart of MBS session establishment according to an exemplary embodiment of the present invention.
  • Fig. 7 is an interactive flowchart of MBS session establishment according to an exemplary embodiment of the present invention.
  • FIG. 8 is an interactive flowchart of UE interest reporting according to an exemplary embodiment of the present invention.
  • Fig. 9 is an interactive flowchart of UE interest reporting according to an exemplary embodiment of the present invention.
  • Fig. 10 is an interactive flowchart of a handover method provided according to an exemplary embodiment of the present invention.
  • Fig. 11 is a structural block diagram of a switching device according to an embodiment of the present invention.
  • Figure 12 is a structural block diagram of an information sending device according to an embodiment of the present invention.
  • Fig. 13 is a structural block diagram of a switching device according to an embodiment of the present invention.
  • the following describes the application scenarios of the switching method and device, and the information sending method and device in the embodiment of the present invention:
  • the embodiments of the present invention can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (Wideband Code) Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE-A (Advanced long term evolution) system, General Mobile Communication systems (Universal Mobile Telecommunication System, UMTS), and fifth generation wireless systems (5G) systems, etc., are not limited in the embodiment of the present invention.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced long term evolution
  • Universal Mobile Telecommunication System Universal Mobile Telecommunication System
  • UMTS Universal Mobile Telecommunication System
  • 5G fifth generation wireless systems
  • FIG. 1 is a schematic diagram of the architecture of a wireless network system according to an embodiment of the present invention.
  • the wireless network system under the network architecture includes a base station 101, a base station 102, a terminal 110, a terminal 120, and a terminal 130; the base station 101 and The base station 102 may be a base station of a neighboring cell.
  • the base station 101 and the base station 102 may perform wireless communication with the terminal 110, the terminal 120, and the terminal 130, respectively, and the terminal 110, the terminal 120, and the terminal 130 may be located between the base station 101 and the base station 102. Switch between.
  • the network device may be a device that can communicate with a user terminal.
  • the network device can be any device with wireless transceiver functions, including but not limited to: base station NodeB, evolved base station eNodeB, base station in 5G communication system, base station in future communication system, wireless fidelity (Wireless Fidelity, WiFi) The access node, wireless relay node, wireless backhaul node, etc. in the system.
  • the network device can also be a wireless controller in a cloud radio access network (cloud radio access network, CRAN) scenario; the network device can also be a small station, a transmission reference point (TRP), etc., as in the embodiment of the present invention. Not limited.
  • the terminal is a device with wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed on In the air (for example, airplanes, balloons, satellites, etc.).
  • User terminals can be mobile phones, tablets, computers with wireless transceiver functions, virtual reality (VR) terminals, augmented reality (AR) terminals, industrial control (industrial control)
  • the embodiments of the present invention do not limit the foregoing specific application scenarios or application objects.
  • a terminal may also be called a terminal, an access terminal, a UE unit, a UE station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a UE terminal, a wireless communication device, a UE agent or a UE device, etc.
  • a terminal may also be called a terminal, an access terminal, a UE unit, a UE station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a UE terminal, a wireless communication device, a UE agent or a UE device, etc.
  • the implementation of the present invention The example does not limit this.
  • FIG. 2 is a hardware structural block diagram of a mobile terminal provided according to an embodiment of the present invention.
  • the mobile terminal may include one or more (only one is shown in FIG. 2) processor 202 (the processor 202 may include, but is not limited to, a microprocessor (Microprocessor Control Unit, MCU) or programmable logic device). (Field Programmable Gate Array, FPGA) and other processing devices) and a memory 204 for storing data.
  • the above-mentioned mobile terminal may also include a transmission device 206 and an input/output device 208 for communication functions.
  • FIG. 2 is only for illustration, and does not limit the structure of the above-mentioned mobile terminal.
  • the mobile terminal may also include more or fewer components than shown in FIG. 2 or have a different configuration from that shown in FIG. 2.
  • the memory 204 may be used to store computer programs, for example, software programs and modules of application software, such as the computer programs corresponding to the information sending method in the embodiment of the present invention.
  • the processor 202 executes the computer programs stored in the memory 204 by running the computer programs stored in the memory 204.
  • the memory 204 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the memory 204 may further include a memory remotely provided with respect to the processor 202, and these remote memories may be connected to the mobile terminal through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • the transmission device 206 is used to receive or transmit data via a network.
  • the above-mentioned specific examples of the network may include a wireless network provided by a communication provider of a mobile terminal.
  • the transmission device 206 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet.
  • the transmission device 206 may be a radio frequency (RF) module, which is used to communicate with the Internet in a wireless manner.
  • RF radio frequency
  • the embodiments of the present invention involve information exchange between the three entities of the terminal, the first network device, and the second network device, and mainly involve the signaling transmission of the Uu port and the Xn port; among them, the first network device is the source network device,
  • the source base station and the second network equipment are the target network equipment in the handover process, for example, the target base station.
  • the second network equipment may specifically be the network equipment in the adjacent cell of the first network equipment;
  • the terminal in the embodiment of the present invention is the connection State of the terminal.
  • the foregoing terminal, the first network device, and the second network device may respectively correspond to the terminal 110, the base station 101, and the base station 102 in the network architecture shown in FIG. 1.
  • FIG. 3 is a flowchart of a handover method according to an embodiment of the present invention. As shown in FIG. 3, the handover method in this embodiment includes:
  • the first network device sends a handover request to the second network device; where the handover request carries broadcast-multicast service MBS session/bearer information.
  • the first network device receives a handover request response sent by the second network device.
  • the handover request response includes at least one of the following: MBS sessions/bearer information that the second network device can accept, and MBS sessions/bearers that the second network device cannot accept Information, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.
  • the MBS session information is used to indicate the MBS session
  • the MBS bearer information is used to indicate the MBS bearer
  • the UE scheduling configuration information of the second network device and the bearer configuration information of the second network device contained in the handover request response can be further sent to the UE in a transparent transmission manner for the first network device.
  • the handover request response includes at least one of the following: MBS session/bearer information that the second network device can accept, and the second network device cannot Admitted MBS session/bearer information, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.
  • the handover method and device, and the information sending method and device in the embodiments of the present invention can solve the problem of how to realize the handover process across base stations in the related technology, so as to realize the effective guarantee of broadcast/multiple transmission during the handover process between the base stations.
  • a specific method for performing cross-gNB handover procedures can be established in a 5G NR scenario, and during the handover process, the mobility and mobility of connected UEs can be guaranteed. Continuity of broadcast/multicast services.
  • the MBS session information is also used to indicate the MBS service corresponding to the MBS session; the MBS session and the MBS service have a one-to-one correspondence, so the MBS indicated by the MBS session information The session can correspond to the corresponding MBS service.
  • the MBS session/bearer information includes at least one of the following:
  • the MBS session information that the terminal is interested in the MBS session/bearer information currently received by the terminal, and the terminal capability information.
  • the MBS session information that the terminal is interested in includes at least one of the following:
  • the identification information of the MBS session that the terminal is interested in the MBS area identifier, the reception priority information, and the MBS session reception mode information that the terminal expects.
  • the receiving priority information includes at least one of the following:
  • Priority unicast reception priority broadcast/multicast reception, priority level for receiving MBS sessions.
  • the MBS session/bearer information currently received by the terminal includes at least one of the following:
  • the identification information of the MBS session/bearer currently received by the terminal the receiving mode information of the MBS session/bearer currently received by the terminal, the radio bearer configuration information of the MBS bearer currently received by the terminal, and the quality of service of the MBS session/bearer currently received by the terminal.
  • Service QoS
  • the MBS session reception mode information expected by the terminal includes at least one of the following: Point-To-Point (PTP) reception, Point-To-Multipoint (PTM) reception, PTP and PTM Receive at the same time;
  • PTP Point-To-Point
  • PTM Point-To-Multipoint
  • PTP and PTM Receive at the same time;
  • the receiving mode information of the MBS session/bearer currently received by the terminal includes at least one of the following: PTP receiving, PTM receiving, and PTP and PTM receiving at the same time.
  • the terminal capability information is used to indicate: the terminal supports receiving unicast services and MBS sessions in the same time slot; or, the terminal does not support receiving unicast services and MBS sessions in the same time slot.
  • the radio bearer configuration information includes: PTP bearer configuration information, and/or, PTM bearer configuration information;
  • the PTP bearer configuration information is used to configure the PTP bearer, and the PTP bearer configuration information includes at least one of the following:
  • PTP radio bearer identification Service Data Adaptation Protocol (SDAP) configuration information, Packet Data Convergence Protocol (PDCP) configuration information, Radio Link Control (RLC) bearer configuration information ;
  • SDAP Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • the PTM bearer configuration information is used to configure the PTM bearer, and the PTM bearer configuration information includes at least one of the following:
  • PTM radio bearer ID logical channel ID
  • SDAP configuration information PDCP configuration information
  • RLC bearer configuration information PDCP configuration information
  • the identification information of the MBS session that the terminal is interested in includes at least one of the following: the MBS session identifier, the temporary mobile group identity (TMGI) of the MBS session, and the protocol data unit indicating the broadcast/multicast session ( Protocol Data Unit, PDU) session identifier.
  • the MBS session identifier the temporary mobile group identity (TMGI) of the MBS session
  • TMGI temporary mobile group identity
  • PDU Protocol Data Unit
  • the admissible MBS session/bearer information indicated in the handover request response includes at least one of the following:
  • the MBS session/bearer identifier that the second network device can accept the reception mode of the broadcast/multicast service session, and the QoS configuration information of the acceptable service session/bearer.
  • the unacceptable MBS session/bearer information indicated in the handover request response includes at least one of the following:
  • the bearer configuration information of the second network device includes at least one of the following:
  • PTM radio bearer ID logical channel ID
  • SDAP configuration information PDCP configuration information
  • RLC bearer configuration information PDCP configuration information
  • the UE scheduling configuration information of the second network device indicated in the handover request response includes at least one of the following:
  • the scheduling information of the multicast service channel, and the physical layer parameters required by the multicast service channel are configured.
  • the handover request response further includes at least one of the following: system information block configuration information of the second network device, multicast control channel configuration information, and multicast service channel configuration information.
  • sending a handover request to the second network device includes:
  • AMF Access and Mobility Management Function
  • AMF may indicate access to the mobility management function or gateway in the core network.
  • the method before sending the handover request to the second network device, the method further includes:
  • this application can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes several instructions to enable a terminal device (which can It is a mobile phone, a computer, a server, or a network device, etc.) to execute the method described in each embodiment of the present invention.
  • FIG. 4 is a flowchart of the information sending method according to an embodiment of the present invention. As shown in FIG. 4, the information sending method in this embodiment includes:
  • the UE sends the MBS indication information that the UE is interested in and the MBS indication information that the UE is receiving to the first network device.
  • the UE receives radio resource control (Radio Resource Control, RRC) reconfiguration information returned by the first network device according to the MBS indication information that the UE is interested in.
  • RRC Radio Resource Control
  • the MBS indication information that the UE is interested in further includes:
  • the service identification information of MBS also includes at least one of the following: MBS service/session identification, temporary mobility group identification TMGI of MBS, MBS identification, and PDU session identification indicating the MBS session.
  • the MBS indication information that the UE is interested in further includes:
  • the receiving mode of the MBS that the UE is interested in
  • the reception mode includes at least one of the following: unicast reception, broadcast/multicast reception, and simultaneous unicast and multicast reception.
  • the MBS indication information that the UE is interested in further includes:
  • the service area of the MBS that the UE is interested in is not limited.
  • the RRC reconfiguration information includes:
  • Target cell identification list of acceptable MBS, configuration information of acceptable MBS, and reception mode information of acceptable MBS.
  • the configuration information of the acceptable MBS includes at least one of the following:
  • PTM radio bearer ID logical channel ID
  • SDAP configuration information PDCP configuration information
  • RLC bearer configuration information PDCP configuration information
  • the configuration information of the acceptable MBS includes at least one of the following:
  • the scheduling information of the multicast service channel, and the physical layer parameters required by the multicast service channel are configured.
  • the receiving mode information of the acceptable MBS includes at least one of the following:
  • the method further includes:
  • this application can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes several instructions to enable a terminal device (which can It is a mobile phone, a computer, a server, or a network device, etc.) to execute the method described in each embodiment of the present invention.
  • FIG. 5 is a flowchart of the handover method according to an embodiment of the present invention. As shown in FIG. 5, the handover method in this embodiment includes:
  • the second network device receives a handover request sent by the first network device; where the handover request carries MBS session/bearer information, the MBS session information is used to indicate the MBS session, and the MBS bearer information is used to indicate the MBS bearer.
  • the second network device returns a handover response to the first network device according to the handover request, where the handover response is used to indicate at least one of the following: MBS session/bearer information that the second network device can accept, and the information that the second network device cannot accept MBS session/bearer information, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.
  • the MBS session/bearer information includes at least one of the following:
  • the MBS session information that the terminal is interested in the MBS session/bearer information currently received by the terminal, and the terminal capability information.
  • the MBS session information that the terminal is interested in includes at least one of the following:
  • the identification information of the MBS session that the terminal is interested in the MBS area identifier, the reception priority information, and the MBS session reception mode information that the terminal expects.
  • the receiving priority information includes at least one of the following:
  • Priority unicast reception priority broadcast/multicast reception, priority level for receiving MBS sessions.
  • the MBS session/bearer information currently received by the terminal includes at least one of the following:
  • the terminal currently receives the MBS session/bearer identification information, the terminal currently receives the MBS session/bearer receiving mode information, the MBS bearer radio bearer configuration information currently received by the terminal, and the MBS session/bearer service quality QoS configuration information currently received by the terminal.
  • the MBS session reception mode information expected by the terminal includes at least one of the following: point-to-point PTP reception, point-to-multipoint PTM reception, and simultaneous reception of PTP and PTM;
  • the receiving mode information of the MBS session/bearer currently received by the terminal includes at least one of the following: PTP receiving, PTM receiving, and PTP and PTM receiving at the same time.
  • the terminal capability information is used to indicate: the terminal supports receiving unicast services and MBS sessions in the same time slot; or, the terminal does not support receiving unicast services and MBS sessions in the same time slot.
  • the radio bearer configuration information includes: PTP bearer configuration information, and/or, PTM bearer configuration information;
  • the PTP bearer configuration information is used to configure the PTP bearer, and the PTP bearer configuration information includes at least one of the following:
  • PTP radio bearer identification service data adaptation protocol SDAP configuration information, packet data convergence protocol PDCP configuration information, radio link control RLC bearer configuration information;
  • the PTM bearer configuration information is used to configure the PTM bearer, and the PTM bearer configuration information includes at least one of the following:
  • PTM radio bearer ID logical channel ID
  • SDAP configuration information PDCP configuration information
  • RLC bearer configuration information PDCP configuration information
  • the identification information of the MBS session that the terminal is interested in includes at least one of the following: an MBS session identifier, a temporary mobility group identifier TMGI of the MBS session, and a PDU session identifier indicating a broadcast/multicast session;
  • the admissible MBS session/bearer information indicated in the handover request response includes at least one of the following:
  • the MBS session/bearer identifier that the second network device can accept the reception mode of the broadcast/multicast service session, and the QoS configuration information of the acceptable service session/bearer.
  • the unacceptable MBS session/bearer information indicated in the handover request response includes at least one of the following:
  • the bearer configuration information of the second network device includes at least one of the following:
  • PTM radio bearer ID logical channel ID
  • SDAP configuration information PDCP configuration information
  • RLC bearer configuration information PDCP configuration information
  • the UE scheduling configuration information of the second network device indicated in the handover request response includes at least one of the following:
  • the scheduling information of the multicast service channel, and the physical layer parameters required by the multicast service channel are configured.
  • the handover request response further includes at least one of the following: system information block configuration information of the second network device, multicast control channel configuration information, and multicast service channel configuration information.
  • sending a handover request to the second network device includes:
  • the MBS session information is also used to indicate the MBS service corresponding to the MBS session;
  • the MBS session corresponds to the MBS service on a one-to-one basis.
  • the following exemplary embodiments are used to further explain the terminal, the first network device, and the second network indicated by the foregoing switching method and the information sending method.
  • This example embodiment explains the MBS session establishment process in the embodiment of the present invention.
  • the terminal, the source base station, and the neighboring cell base station can establish an MBS session in one of the following ways: Xn Setup process, gNB Configuration Update process, Operation Administration and Maintenance (OAM); it should be further explained that the source base station in this example embodiment is equivalent to the source network equipment in the embodiment of the present invention, and the neighboring cell base station in this example embodiment is equivalent to this The target network device in the embodiment of the invention.
  • OAM Operation Administration and Maintenance
  • Fig. 6 is an interactive flowchart of MBS session establishment according to an exemplary embodiment of the present invention. As shown in Fig. 6, the procedure of establishing an MBS session based on the Xn Setup procedure in this example is as follows:
  • the source base station sends an Xn establishment request message to the neighboring cell base station (gNB), which carries an Information Element (IE) for obtaining the MBS service information of the neighboring cell, which is used to request the neighboring cell base station to respond to each cell What MBS services are there and the cell identity to which it belongs (the cell identity is unique in the network, such as the NR cell global identifier (CGI)).
  • IE Information Element
  • the base station of the neighboring cell receives the Xn establishment request message from the source base station, and carries the IE for obtaining the MBS service information of the neighboring cell.
  • the base station of the neighboring cell will inform the source base station of the MBS services in the cell it serves and the identity of the cell to which it belongs together through an Xn establishment response message.
  • the source base station After the source base station receives the Xn establishment response message with the MBS service information of the neighboring cell and the identity of the cell to which it belongs, it will notify the UE through a System Information Block (SIB) message or a dedicated RRC message.
  • SIB System Information Block
  • Fig. 7 is an interactive flowchart of MBS session establishment according to an exemplary embodiment of the present invention. As shown in Fig. 7, the procedure of establishing an MBS session based on the gNB Configuration Update procedure in this example is as follows:
  • Source base station sends a gNB Configuration Update message to the neighboring cell base station (gNB), which will carry the IE for obtaining the MBS service information of the neighboring cell, and is used to request the neighboring cell base station to respond to which MBS services each cell belongs to Cell ID (The cell ID is unique in the network, such as NR CGI).
  • the base station of the neighboring cell receives the gNB Configuration Update message from the source base station, and it carries the IE for obtaining the MBS service information of the neighboring cell.
  • the neighboring cell base station will inform the source base station of the MBS services in the cell it serves and the cell identity to which it belongs together through gNB Configuration Update ACK.
  • the source base station After the source base station receives the Xn establishment response message with the MBS service information of the neighboring cell and the identity of the cell to which it belongs, it will notify the UE through a SIB message or a dedicated RRC message.
  • the MBS service owned by the neighboring cell and the cell to which it belongs can be pre-configured with the source base station through OAM, and the source base station can directly notify the UE through a SIB message or a dedicated RRC message.
  • This example embodiment explains the procedure for the UE to switch between the source base station and the target base station on the premise that the MBS session is established between the UE and the source base station in example embodiment 1.
  • the switching process is as follows:
  • the UE directly obtains user service information from the service/application layer.
  • FIG. 8 is an interactive flowchart of UE interest reporting according to an exemplary embodiment of the present invention. The process of UE interest reporting in the above steps is shown in FIG. 8.
  • the UE obtains the MBS services that can be provided by the service/application layer and the relevant information of each MBS service, such as frequency point information, MBS service area identifier, MBS service identifier, service start and end time, etc.; UE receives After business-related information, it will report the MBS services that it is interested in receiving and receiving based on the business and its own interests of the application/business layer to assist the source gNB to choose as much as possible the MBS that the UE is receiving or interested in receiving.
  • the target cell of the business is the MBS services that can be provided by the service/application layer and the relevant information of each MBS service, such as frequency point information, MBS service area identifier, MBS service identifier, service start and end time, etc.
  • the service in the MBS interest indication information message reported by the UE is completely based on its own interest.
  • the UE's interest reporting in the service is an autonomous behavior, and it is not limited to whether there is a service of interest in the neighboring area.
  • the gNB selects the target cell for handover for the UE, it tries its best to select a cell that can support the MBS transmission that the UE is receiving or is interested in receiving. If there is no target cell that can satisfy all the MBS services that the UE is receiving or is interested in receiving, the cell that supports the high-priority or the MBS services that is being received is preferentially selected. Therefore, the above steps have better business flexibility.
  • updates or changes in service-related information at the application/service layer will be notified to the UE, and the UE will be triggered to report the service that it is interested in.
  • the UE can not only obtain the available MBS service and its MBS service related information from the application/service layer.
  • the reporting process can also be shown in Figure 9.
  • the UE can also read the SIB message to obtain which MBS services the cell provides, and the service area each service belongs to, and which MBS services can be provided by the neighboring cell and which MBS each service belongs to. Business area.
  • handover is a network-controlled handover, that is, the UE is handed over to a suitable target cell.
  • the serving cell needs to know the MBS service that the UE is receiving or is interested in receiving, so that it is possible to switch the UE to the cell of interest.
  • UE interest reporting can also assist base station scheduling. When the target base station learns which broadcast and multicast services the UE is interested in through the MBS interest indication information, it will try to avoid scheduling its interested broadcast and multicast transmissions and unicasts in the same time slot according to the UE's capabilities during scheduling. transmission.
  • the UE needs to send MBS interest indication information to the source gNB.
  • the MBS interest indication information is used to tell the base station that the UE is receiving or is interested in receiving Broadcast and multicast services.
  • the MBS interest indication information in this example embodiment specifically includes the following information:
  • MBS service identifier list a list of MBS services that the UE is receiving or is interested in receiving.
  • the service identifier is used to mark each broadcast and multicast service.
  • the MBS service list is sorted according to the UE's interest priority of the MBS service being received or interested in receiving. That is, the UE's interest in the broadcast and multicast services ranked first in the list is higher than that of the broadcast and multicast services ranked lower.
  • MBS reception priority indicates whether the UE preferentially receives MBS services compared to unicast. If the received information is "true”, then yes, the UE prefers to receive the MBS service in the target cell over the unicast service transmission. This information may be used when the network is congested. When the target base station receives this information, it may release the unicast bearer and give priority to receiving broadcast and multicast transmissions.
  • the MBS interest indication information may further include:
  • Receiving mode cast mode which type of MBS service data the UE expects to adopt; specifically, the optional receiving modes are: which is expected to be adopted for the MBS service that the UE is receiving or interested in receiving reported in the MBS interest indication message by the UE Kind of receiving mode.
  • the MBS service that the UE is receiving or is interested in receiving reported by the UE comes from: 1) the available MBS services notified by the application/service layer, and The relevant information of the MBS service; it should be noted that the MBS service that can be provided by the above application/service layer notification, and the relevant information of the MBS service is available or unavailable on the air interface, such as not available on the air interface
  • the broadcast and multicast service reported by MBS (will trigger the UE to request the establishment of the service from the core network); 2) Inform the source base station which MBS services are available in the neighborhood of the source base station through the Xn interface, and notify the UE through SIB messages or proprietary RRC messages, based on the neighborhood If there are MBS services in the area, the UE will report the MBS services that it is interested in or are receiving, and this service must be available on the air interface.
  • the MBS services that the UE is receiving or are interested in receiving reported by the UE are reported according to the priority order of the UE's interest in the MBS services.
  • the base station can decide to release the unicast bearer, and preferentially receive the data transmitted by the broadcast and multicast.
  • the source gNB can configure the UE to measure the MBS frequency points that the UE is interested in receiving, and the UE measures the corresponding frequency points and reports the measurement results. If the source gNB If it is found that the measurement result reported by the UE includes the frequency corresponding to the high-priority MBS service, the source gNB can switch the UE to the cell where the frequency corresponding to the high-priority MBS service is located.
  • the gNB When the gNB selects the target cell for handover for the UE, it tries its best to select a cell that can support the MBS transmission that the UE is receiving or is interested in receiving. Even if there is no target cell that can satisfy the MBS service that the UE is receiving or is interested in receiving, the cell that supports the high-priority or the MBS service being received is preferred.
  • the source base station can send a handover request message to the target base station.
  • the handover request message may contain at least one of the following information:
  • the MBS interest indication information of the UE is used to assist the source base station to select the target cell and the flexible scheduling of the target base station.
  • the MBS interest indication information of the aforementioned UE may include: 1.1) MBS service list; 1.2) MBS reception priority.
  • the aforementioned handover request message may also include the reception mode that the UE expects to adopt for the service of interest.
  • the aforementioned MBS interest indication information can assist the source base station to select as much as possible the cell that can support the MBS service that the UE is interested in or is receiving when performing target cell selection, thereby ensuring a certain service continuity and the target base station knowing which UE is interested in.
  • Flexible scheduling after the MBS service is interested avoids scheduling the same MBS service in the same time slot at the same time.
  • the MBS service information currently received by the UE such as the MBS session identification information corresponding to the received MBS service, and the MBS session bearer configuration information, such as PTM bearer configuration information and/or PTP bearer configuration information.
  • the aforementioned MBS service information may include: 2.1) MBS session identification information, which indicates the MBS session identification information of the MBS session corresponding to the MBS service currently received by the UE, and may include one or more MBS session identifications, broadcast The temporary mobile group identifier TMGI of the multicast service, the broadcast multicast service identifier, the PDU session identifier indicating the MBS session, and the IP multicast address; 2.2) Radio bearer configuration information, which configures the radio bearer of the MBS session and indicates The MBS session bearer configuration information currently received by the UE, the radio bearer configuration information may specifically further include: PTP bearer configuration information and/or PTM bearer configuration information.
  • PTP bearer configuration information specifically includes: PTP radio bearer identification, service data adaptation protocol SDAP configuration, packet data aggregation protocol PDCP configuration, radio link control RLC configuration;
  • PTM configuration information includes: PTM radio bearer identification, SDAP configuration, PDCP configuration And RLC configuration.
  • the air interface resource configuration includes receiving the scheduling information of the current MBS service, the scheduling information of the multicast service channel, and receiving the physical layer parameters of the current MBS service.
  • the target base station can use the same set of bearer configuration information as the source base station, that is, the radio bearer configuration, and more Broadcast the scheduling information of the service channel and receive the physical layer parameters of the current MBS service to receive the MBS service.
  • the underlying configuration such as the scheduling information of the multicast service channel and the physical layer parameters for receiving the current MBS service, it changes in real time. Therefore, this part of the information source base station may not be sent to the target base station, but by the target base station.
  • the base station configures and then informs the UE.
  • the MBS service information may also include: the receiving mode adopted by the MBS session currently received by the UE, which may include the MBS service identifier and the service area identifier corresponding to the MBS service.
  • the QoS configuration information of the QoS flow in the MBS session corresponds to the QoS parameters of the QoS flow class of each QoS flow identification.
  • the QoS configuration information indicates each QoS flow in the QoS flow list mapped to the radio bearer corresponding to the MBS service currently being received by the UE, including one or more QoS flow identifiers, QoS flow level QoS parameters, and MBS Session identification information.
  • the UE's MBS receiving capability indicates whether the terminal supports the ability to simultaneously receive unicast transmission and broadcast multicast transmission in the same time slot.
  • the MBS receiving capability of the UE can allow the target network device to take its terminal capability into consideration during scheduling, thereby avoiding the conflict between the scheduling result and the terminal capability.
  • the target base station can return a handover request response message, and the target base station may include at least one of the following information in the handover request response message:
  • the target base station after receiving the handover request message, the target base station needs to determine which MBS service resources can be accepted and which cannot be accepted, and include the MBS service resource admission list and the MBS service resource unacceptable list in the handover request response message.
  • each MBS session resource that is of interest to the admissible UE includes a list of admissible QoS flows and a list of unacceptable QoS flows, and the indication of the PTP/PTM reception mode corresponding to the MBS session, and the PTP/PTM bearer configuration.
  • the target base station may also give the corresponding MBS session reception mode adopted by the target base station in the handover request response message, such as PTP and/or PTM mode reception, and give the corresponding radio bearer configuration in the two modes.
  • the QoS configuration of the radio bearer in the corresponding receiving mode can also be given.
  • the target base station may also include SIB information of the target cell, MBS control channel and MBS service channel configuration information in the handover response message.
  • the target base station may have established a corresponding MBS session with the Multi-cell/Multicast Coordination Entity (MCE)/AMF.
  • MCE Multi-cell/Multicast Coordination Entity
  • the target base station only needs to consider configuring PTP and/or PTM for the UE for MBS reception.
  • the target base station can initiate an MBS session establishment request to the MCE/AMF.
  • the handover request response message may also include the MBS session identifier and the reason for not accepting the MBS session resource.
  • the handover request response message may also include SIB information and MBS control channel and traffic channel configuration information of the target cell.
  • the target base station can also send a handover command message to the UE at the same time/after returning the handover request response message to the source base station.
  • the handover command message contains the RRC reconfiguration message, and the RRC reconfiguration message specifically includes: the corresponding MBS The reception method through which the session is received, and the radio bearer (RB) configuration corresponding to the reception mode (Data Radio Bearer/Multicast Radio Bearer (DRB/MRB)).
  • RB radio bearer
  • the target base station also needs to indicate which MBS service resources need to be transmitted in the PTM way and the corresponding MRB configuration in the handover response/command message.
  • the target base station also needs to indicate in the handover response message to accept the MBS service resources through the PTM and PTP methods, and at the same time provide the corresponding configuration in the RRC reconfiguration message.
  • the handover command message also includes an indication of the QoS profile of the MBS service that can be supported.
  • the UE may also return a confirmation message to the target base station to confirm that the RRC connection reconfiguration is completed.
  • Fig. 10 is an interactive flowchart of a handover method provided according to an exemplary embodiment of the present invention.
  • the UE implements a handover process between a source base station and a target base station as shown in Fig. 10, and the specific process of the handover is as follows:
  • the UE obtains from the service/application layer which MBS services can be provided, and the relevant information of each MBS service; specifically including: the MBS service ID (for example, TMGI, MBS service ID), frequency point information, and MBS service Region and the start and end time of this MBS service.
  • the UE will read system messages to know which MBS services are available in the current cell and neighboring cells and the MBS service area to which each service belongs.
  • the UE After the UE receives the relevant information about the MBS service at the service/application layer and the MBS services that can be provided by the neighboring cell, based on this information, the UE reports the MBS service it is receiving or is interested in receiving through the MBS interest indication information message.
  • Source base station The MBS services reported by the UE are reported after being sorted according to the priority of their interest in the service.
  • the MBS interest indication information message may also include any combination of the following information: a list of MBS services that the UE is interested in and receiving, and the priority of MBS transmission relative to unicast reception .
  • the MBS interest indication information message also includes the currently received MBS service reception mode and UE capability.
  • the UE measures the frequency points that the UE is interested in receiving configured by the network, and reports the measurement result to the source base station through a measurement report message.
  • the base station will try its best to select a cell that can support the broadcast and multicast services that the UE is receiving or is interested in receiving.
  • the source base station sends a handover request message to the target base station through the Xn interface, the purpose of which is to request resources for handover (Handover) and inform the target base station of the UE context on the source base station side;
  • the handover request message may specifically include at least one of the following information One: Interest indication information reported by the UE, the current MBS service information received by the UE (for example, the MBS session identification information corresponding to the received MBS service), and the MBS session bearer configuration information (for example, PTM bearer configuration information and/or PTP bearer configuration information), the QoS configuration information of the QoS flow in the MBS session (for example, the QoS flow identification list in the session, corresponding to the QoS parameters of the QoS flow class of each QoS flow identification), the UE receives the current MBS service
  • the indication information that identifies whether the corresponding MBS data uses the PTP radio bearer or the PTM radio bearer, and the MBS receiving capability information of the UE.
  • the target base station After receiving the handover request message, the target base station will perform admission control, determine which MBS session resources can be accepted and which MBS session resources cannot be accepted, and return a handover request response message to the source base station.
  • the admissible MBS session will also include an admissible QoS flow list and an unacceptable QoS flow list, as well as an indication of the PTP/PTM receiving mode corresponding to the MBS session, and the PTP/PTM bearer configuration.
  • the MBS session identifier and the reason for not accepting the MBS session resource will be included.
  • the handover response message may also include SIB information of the target cell, MBS control channel and MBS service channel configuration information.
  • the target base station may include an RRC reconfiguration message in the handover command to be sent to the UE, which mainly includes: which reception mode the MBS service is received through, and the radio bearer configuration of the corresponding reception mode.
  • the UE will respond to an RRC reconfiguration complete message to the target base station, the purpose of which is to determine that an RRC connection configuration has been successfully connected.
  • the target base station can receive the corresponding broadcast multicast service in the PTP and/or PTM reception mode.
  • the method according to the foregoing embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware.
  • the technical solution of the present application can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), and includes several instructions to make a terminal
  • a device which may be a mobile phone, a computer, a server, or a network device, etc.) executes the methods described in the various embodiments of the present invention.
  • the embodiment of the present invention provides a handover device, which is applied to a first network device, and the device is used to implement the above-mentioned embodiments and optional implementation manners, and those that have been described will not be repeated.
  • the term "module” can implement a combination of software and/or hardware with predetermined functions.
  • the devices described in the following embodiments are implemented by software, implementation by hardware or a combination of software and hardware is also possible and conceived.
  • Fig. 11 is a structural block diagram of a handover device according to an embodiment of the present invention. As shown in Fig. 11, the handover device in this embodiment includes:
  • the first sending module 402 is configured to send a handover request to the second network device; wherein the handover request carries broadcast multicast service MBS session/bearer information;
  • the first receiving module 404 is configured to receive a handover request response sent by the second network device, and the handover request response includes at least one of the following:
  • the MBS session/bearer information that the second network device can accept the MBS session/bearer information that the second network device cannot accept, the UE scheduling configuration information of the second network device, and the bearer configuration information of the second network device.
  • the MBS session/bearer information includes at least one of the following:
  • the MBS session information that the terminal is interested in the MBS session/bearer information currently received by the terminal, and the terminal capability information.
  • the MBS session information that the terminal is interested in includes at least one of the following:
  • the identification information of the MBS session that the terminal is interested in the MBS area identifier, the reception priority information, and the MBS session reception mode information that the terminal expects.
  • the receiving priority information includes at least one of the following:
  • Priority unicast reception priority broadcast/multicast reception, priority level for receiving MBS sessions.
  • the MBS session/bearer information currently received by the terminal includes at least one of the following:
  • the terminal currently receives the MBS session/bearer identification information, the terminal currently receives the MBS session/bearer receiving mode information, the MBS bearer radio bearer configuration information currently received by the terminal, and the MBS session/bearer service quality QoS configuration information currently received by the terminal.
  • the MBS session reception mode information expected by the terminal includes at least one of the following: point-to-point PTP reception, point-to-multipoint PTM reception, and simultaneous reception of PTP and PTM;
  • the receiving mode information of the MBS session/bearer currently received by the terminal includes at least one of the following: PTP receiving, PTM receiving, and PTP and PTM receiving at the same time.
  • the terminal capability information is used to indicate: the terminal supports receiving unicast services and MBS sessions in the same time slot; or, the terminal does not support receiving unicast services and MBS sessions in the same time slot.
  • the radio bearer configuration information includes: PTP bearer configuration information, and/or, PTM bearer configuration information;
  • the PTP bearer configuration information is used to configure the PTP bearer, and the PTP bearer configuration information includes at least one of the following:
  • PTP radio bearer identification service data adaptation protocol SDAP configuration information, packet data aggregation protocol PDCP configuration information, radio link control RLC bearer configuration information;
  • the PTM bearer configuration information is used to configure the PTM bearer, and the PTM bearer configuration information includes at least one of the following:
  • PTM radio bearer ID logical channel ID
  • SDAP configuration information PDCP configuration information
  • RLC bearer configuration information PDCP configuration information
  • the identification information of the MBS session that the terminal is interested in includes at least one of the following: an MBS session identifier, a temporary mobility group identifier TMGI of the MBS session, and a PDU session identifier indicating a broadcast/multicast session.
  • the admissible MBS session/bearer information indicated in the handover request response includes at least one of the following:
  • the MBS session/bearer identifier that the second network device can accept the reception mode of the broadcast/multicast service session, and the QoS configuration information of the acceptable service session/bearer.
  • the unacceptable MBS session/bearer information indicated in the handover request response includes at least one of the following:
  • the bearer configuration information of the second network device includes at least one of the following:
  • PTM radio bearer ID logical channel ID
  • SDAP configuration information PDCP configuration information
  • RLC bearer configuration information PDCP configuration information
  • the UE scheduling configuration information of the second network device indicated in the handover request response includes at least one of the following:
  • the scheduling information of the multicast service channel, and the physical layer parameters required by the multicast service channel are configured.
  • the handover request response further includes at least one of the following: system information block configuration information of the second network device, multicast control channel configuration information, and multicast service channel configuration information.
  • sending a handover request to the second network device includes:
  • the method before sending the handover request to the second network device, the method further includes:
  • each of the above modules can be implemented by software or hardware.
  • it can be implemented in the following manner, but not limited to this: the above modules are all located in the same processor; or, the above modules can be combined in any combination.
  • the forms are located in different processors.
  • the embodiment of the present invention provides an information sending device, which is applied to a terminal, and the device is used to implement the above-mentioned embodiments and optional implementation manners, and those that have been explained will not be repeated.
  • the term "module” can implement a combination of software and/or hardware with predetermined functions.
  • the devices described in the following embodiments are implemented by software, implementation by hardware or a combination of software and hardware is also possible and conceived.
  • Fig. 12 is a structural block diagram of an information sending device according to an embodiment of the present invention. As shown in Fig. 12, the information sending device in this embodiment includes:
  • the second sending module 502 is configured to send the MBS indication information that the UE is interested in and the MBS indication information that the UE is receiving to the first network device;
  • the second receiving module 504 is configured to receive the RRC reconfiguration information returned by the first network device according to the MBS indication information that the UE is interested in.
  • the MBS indication information that the UE is interested in further includes:
  • the service identification information of MBS also includes at least one of the following: MBS service/session identification, temporary mobility group identification TMGI of MBS, MBS identification, and PDU session identification indicating the MBS session.
  • the MBS indication information that the UE is interested in further includes:
  • the receiving mode of the MBS that the UE is interested in
  • the reception mode includes at least one of the following: unicast reception, broadcast/multicast reception, and simultaneous unicast and multicast reception.
  • the MBS indication information that the UE is interested in further includes:
  • the service area of the MBS that the UE is interested in is not limited.
  • the RRC reconfiguration information includes:
  • Target cell identification list of acceptable MBS, configuration information of acceptable MBS, and reception mode information of acceptable MBS.
  • the configuration information of the acceptable MBS includes at least one of the following:
  • PTM radio bearer ID logical channel ID
  • SDAP configuration information PDCP configuration information
  • RLC bearer configuration information PDCP configuration information
  • the configuration information of the acceptable MBS includes at least one of the following:
  • the scheduling information of the multicast service channel, and the physical layer parameters required by the multicast service channel are configured.
  • the receiving mode information of the acceptable MBS includes at least one of the following:
  • the method further includes:
  • each of the above modules can be implemented by software or hardware.
  • it can be implemented in the following manner, but not limited to this: the above modules are all located in the same processor; or, the above modules can be combined in any combination.
  • the forms are located in different processors.
  • the embodiment of the present invention provides a handover device, which is applied to a second network device, and the device is used to implement the above-mentioned embodiments and optional implementation manners, and those that have been described will not be repeated.
  • the term "module” can implement a combination of software and/or hardware with predetermined functions.
  • FIG. 13 is a structural block diagram of a switching device according to an embodiment of the present invention. As shown in FIG. 13, the switching device in this embodiment includes:
  • the third receiving module 602 is configured to receive a handover request sent by the first network device; where the handover request carries MBS session/bearer information, the MBS session information is used to indicate the MBS session, and the MBS bearer information is used to indicate the MBS bearer;
  • the return module 604 is configured to return a handover response to the first network device according to the handover request, where the handover response is used to indicate at least one of the following: MBS session/bearer information that the second network device can accept, and the information that the second network device cannot accept MBS session/bearer information, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.
  • the MBS session/bearer information includes at least one of the following:
  • the MBS session information that the terminal is interested in the MBS session/bearer information currently received by the terminal, and the terminal capability information.
  • the MBS session information that the terminal is interested in includes at least one of the following:
  • the identification information of the MBS session that the terminal is interested in the MBS area identifier, the reception priority information, and the MBS session reception mode information that the terminal expects.
  • the receiving priority information includes at least one of the following:
  • Priority unicast reception priority broadcast/multicast reception, priority level for receiving MBS sessions.
  • the MBS session/bearer information currently received by the terminal includes at least one of the following:
  • the terminal currently receives the MBS session/bearer identification information, the terminal currently receives the MBS session/bearer receiving mode information, the MBS bearer radio bearer configuration information currently received by the terminal, and the MBS session/bearer service quality QoS configuration information currently received by the terminal.
  • the MBS session reception mode information expected by the terminal includes at least one of the following: point-to-point PTP reception, point-to-multipoint PTM reception, and simultaneous reception of PTP and PTM;
  • the receiving mode information of the MBS session/bearer currently received by the terminal includes at least one of the following: PTP receiving, PTM receiving, and PTP and PTM receiving at the same time.
  • the terminal capability information is used to indicate: the terminal supports receiving unicast services and MBS sessions in the same time slot; or, the terminal does not support receiving unicast services and MBS sessions in the same time slot.
  • the radio bearer configuration information includes: PTP bearer configuration information, and/or, PTM bearer configuration information;
  • the PTP bearer configuration information is used to configure the PTP bearer, and the PTP bearer configuration information includes at least one of the following:
  • PTP radio bearer identification service data adaptation protocol SDAP configuration information, packet data aggregation protocol PDCP configuration information, radio link control RLC bearer configuration information;
  • the PTM bearer configuration information is used to configure the PTM bearer, and the PTM bearer configuration information includes at least one of the following:
  • PTM radio bearer ID logical channel ID
  • SDAP configuration information PDCP configuration information
  • RLC bearer configuration information PDCP configuration information
  • the identification information of the MBS session that the terminal is interested in includes at least one of the following: an MBS session identifier, a temporary mobile group identifier TMGI of the MBS session, and a PDU session identifier indicating a broadcast/multicast session.
  • the admissible MBS session/bearer information indicated in the handover request response includes at least one of the following:
  • the MBS session/bearer identifier that the second network device can accept the reception mode of the broadcast/multicast service session, and the QoS configuration information of the acceptable service session/bearer.
  • the unacceptable MBS session/bearer information indicated in the handover request response includes at least one of the following:
  • the bearer configuration information of the second network device includes at least one of the following:
  • PTM radio bearer ID logical channel ID
  • SDAP configuration information PDCP configuration information
  • RLC bearer configuration information PDCP configuration information
  • the UE scheduling configuration information of the second network device indicated in the handover request response includes at least one of the following:
  • the scheduling information of the multicast service channel, and the physical layer parameters required by the multicast service channel are configured.
  • the handover request response further includes at least one of the following: system information block configuration information of the second network device, multicast control channel configuration information, and multicast service channel configuration information.
  • sending a handover request to the second network device includes:
  • the method before sending the handover request to the second network device, the method further includes:
  • each of the above modules can be implemented by software or hardware.
  • it can be implemented in the following manner, but not limited to this: the above modules are all located in the same processor; or, the above modules can be combined in any combination.
  • the forms are located in different processors.
  • the embodiment of the present invention also provides a computer-readable storage medium, and a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute any of the foregoing method embodiments when running. step.
  • the foregoing computer-readable storage medium may be configured to store the computer program used in the foregoing embodiment.
  • the foregoing computer-readable storage medium may include, but is not limited to: U disk, Read-Only Memory (Read-Only Memory, ROM for short), Random Access Memory (Random Access Memory, for short) It is a variety of media that can store computer programs such as RAM), mobile hard disks, magnetic disks, or optical disks.
  • An embodiment of the present invention also provides an electronic device, including a memory and a processor, the memory is stored with a computer program, and the processor is configured to run the computer program to execute the steps in any of the foregoing method embodiments.
  • the aforementioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the aforementioned processor, and the input-output device is connected to the aforementioned processor.
  • the above-mentioned processor may be configured to execute the steps in the above-mentioned embodiment through a computer program.
  • modules or steps of this application can be implemented by a general computing device, and they can be concentrated on a single computing device or distributed on a network composed of multiple computing devices.
  • they can be implemented with program codes executable by a computing device, so that they can be stored in a storage device for execution by the computing device, and in some cases, they can be executed in a different order than here.
  • the steps shown or described can be implemented by making them into individual integrated circuit modules, or making multiple modules or steps of them into a single integrated circuit module. In this way, this application is not limited to any specific combination of hardware and software.

Landscapes

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

Abstract

本申请提供了一种切换方法及装置、信息发送方法及装置，其中，切换方法包括：向第二网络设备发送切换请求，其中，所述切换请求中携带了广播多播业务MBS会话/承载信息；接收所述第二网络设备发送的切换请求响应，所述切换请求响应包括以下至少之一：所述第二网络设备可接纳的MBS会话/承载信息，所述第二网络设备无法接纳的MBS会话/承载信息，所述第二网络设备的UE调度配置信息，所述第二网络设备的承载配置信息。

Description

切换方法及装置、信息发送方法及装置 技术领域
本申请涉及通信领域，例如，涉及一种切换方法及装置、信息发送方法及装置。
背景技术
随着移动终端用户数量的不断攀升所带来的视频业务需求的增加，以及数字电视技术和网络通信技术的飞速发展，无线广播业务成为无线应用领域关注的一大热点。其中，多媒体广播多播业务(Multicast Broadcast Service，MBS)技术，作为手机电视的一种重要实现方式，将在5G***中扮演重要角色，具有较大的发展前景。
增强型多媒体广播多播业务(evolved Multicast Broadcast Multimedia Service，简称eMBMS)是在空口层通过多播/广播的方式为用户提供实时/非实时多媒体业务的一种关键技术。eMBMS能实现高速多媒体业务的广播传输，即点到多点传输(Point to Multipoint，PTM，即广播/多播)，提供丰富的视频、音频和多媒体业务。因此，在5G***中进一步发展eMBMS，可提升整个广播***的能力，从而可以支持更高速更有效的5G广播的应用场景，例如4K/8K超高清视频、三维立体视频、虚拟现实(Virtual Reality，VR)/增强现实(Augmented Reality，AR)等高质量多媒体业务。
相关技术中关于如何在5G新空口(5G New Radio，5G-NR)技术下合理并有效实现广播/多播业务，尤其对于提供服务的网络设备在发生切换过程中，连接态的终端(User Equipment，UE)的移动性以及广播/多播业务的连续性，并未有明确的方案。
针对上述相关技术中，如何实现跨基站的切换流程的问题，相关技术中尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种切换方法及装置、信息发送方法及装置，以至少解决相关技术中如何实现跨基站的切换流程的问题。
根据本发明的一个实施例，提供了一种切换方法，应用于第一网络设备，所述方法包括：
向第二网络设备发送切换请求；其中，所述切换请求中携带了广播多播业务MBS会话/承载信息；
接收所述第二网络设备发送的切换请求响应，所述切换请求响应包含以下至少之一：
所述第二网络设备可接纳的MBS会话/承载信息，所述第二网络设备无法接纳的MBS会话/承载信息，所述第二网络设备的UE调度配置信息，所述第二网络设备的承载配置信息。
根据本发明的另一个实施例，还提供了一种信息发送方法，应用于UE，所述方法包括：
向第一网络设备发送UE感兴趣的MBS指示信息与UE正在接收的MBS指示信息；
接收所述第一网络设备根据所述UE感兴趣的MBS指示信息返回的RRC重配置信息。
根据本发明的另一个实施例，还提供了一种切换方法，应用于第二网络设备，所述方法包括：
接收第一网络设备发送的切换请求；其中，所述切换请求中携带了MBS会话/承载信息，所述MBS会话信息用于指示MBS会话，所述MBS承载信息用于指示MBS承载；
根据所述切换请求返回切换响应至所述第一网络设备，其中，所述切换响应用于指示以下至少之一：所述第二网络设备可接纳的MBS会话/承载信息，所述第二网络设备无法接纳的MBS会话/承载信息，所述第二网络设备的UE调度配置信息，所述第二网络设备的承载配置信息。
根据本发明的另一个实施例，还提供了一种切换装置，设置于第一网络设备，所述装置包括：
第一发送模块，用于向第二网络设备发送切换请求；其中，所述切换请求中携带了广播多播业务MBS会话/承载信息；
第一接收模块，用于接收所述第二网络设备发送的切换请求响应，所述切换请求响应包含以下至少之一：
所述第二网络设备可接纳的MBS会话/承载信息，所述第二网络设备无法接纳的MBS会话/承载信息，所述第二网络设备的UE调度配置信息，所述第二网络设备的承载配置信息。
根据本发明的另一个实施例，还提供了一种信息发送装置，设置于UE，所 述装置包括：
第二发送模块，用于向第一网络设备发送UE感兴趣的MBS指示信息与UE正在接收的MBS指示信息；
第二接收模块，用于接收所述第一网络设备根据所述UE感兴趣的MBS指示信息返回的RRC重配置信息。
根据本发明的另一个实施例，还提供了一种切换装置，设置于第二网络设备，所述装置包括：
第三接收模块，用于接收第一网络设备发送的切换请求；其中，所述切换请求中携带了MBS会话/承载信息，所述MBS会话信息用于指示MBS会话，所述MBS承载信息用于指示MBS承载；
返回模块，用于根据所述切换请求返回切换响应至所述第一网络设备，其中，所述切换响应用于指示以下至少之一：所述第二网络设备可接纳的MBS会话/承载信息，所述第二网络设备无法接纳的MBS会话/承载信息，所述第二网络设备的UE调度配置信息，所述第二网络设备的承载配置信息。
根据本发明的另一个实施例，还提供了一种计算机可读的存储介质，所述计算机可读的存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本发明的另一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
通过本发明实施例中的切换方法及装置、信息发送方法及装置，由于可以令第一网络设备向第二网络设备发送切换请求；其中，切换请求中携带了MBS会话/承载信息，MBS会话信息用于指示MBS会话，MBS承载信息用于指示MBS承载；并令第一网络设备接收第二网络设备发送的切换请求响应，切换请求响应包括以下至少之一：第二网络设备可接纳的MBS会话/承载信息，第二网络设备无法接纳的MBS会话/承载信息，第二网络设备的UE调度配置信息，第二网络设备的承载配置信息。因此，通过本发明实施例中的切换方法及装置、信息发送方法及装置，可以解决相关技术中如何实现跨基站的切换流程的问题，以达到可实现跨基站的切换过程中有效保障广播/多播业务的连续性的效果。
附图说明
图1是根据本发明实施例提供的无线网络***的构架示意图；
图2是根据本发明实施例提供的移动终端的硬件结构框图；
图3是根据本发明实施例提供的切换方法的流程图；
图4是根据本发明实施例提供的信息发送方法的流程图；
图5是根据本发明实施例提供的切换方法的流程图；
图6是根据本发明示例性实施例提供的MBS会话建立的交互流程图；
图7是根据本发明示例性实施例提供的MBS会话建立的交互流程图；
图8是根据本发明示例性实施例提供的UE兴趣上报的交互流程图；
图9是根据本发明示例性实施例提供的UE兴趣上报的交互流程图；
图10是根据本发明示例性实施例提供的切换方法的交互流程图；
图11是根据本发明实施例提供的切换装置的结构框图；
图12是根据本发明实施例提供的信息发送装置的结构框图；
图13是根据本发明实施例提供的切换装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本申请。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
为进一步说明本发明实施例中的切换方法及装置、信息发送方法及装置的工作方式，以下对于本发明实施例中的切换方法及装置、信息发送方法及装置的应用场景进行阐述：
本发明实施例可以应用于各种通信***，例如：全球移动通讯(Global System of Mobile communication，GSM)***、码分多址(Code Division Multiple Access，CDMA)***、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)***、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)***、LTE-A(Advanced long term evolution，先进的长期演进)***、通用移动通信***(Universal Mobile Telecommunication System，UMTS)、以及第五代移动通信技术(5th generation wireless systems，5G)***等，本发明实施例对此并不限定。在本发明实施例中以5G***为例进行说明。
本发明实施例可以用于不同的制式的无线网络。无线接入网络在不同的***中可包括不同的通信节点。图1是根据本发明实施例提供的无线网络***的构架示意图，如图1所示，该网络构架下的无线网络***包括基站101，基站102，终端110，终端120，终端130；基站101和基站102可以是相邻小区的基站，基站101和基站102可分别与终端110、终端120和终端130之间进行无线通信，并且，终端110、终端120和终端130可在基站101和基站102之间进行切换。
本发明实施例中，网络设备可以是能和用户终端进行通信的设备。网络设备可以是任意一种具有无线收发功能的设备，包括但不限于：基站NodeB、演进型基站eNodeB、5G通信***中的基站、未来通信***中的基站、无线保真(Wireless Fidelity，WiFi)***中的接入节点、无线中继节点、无线回传节点等。网络设备还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器；网络设备还可以是小站，传输节点(transmission reference point，TRP)等，本发明实施例对此不做限定。
本发明实施例中，终端是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。用户终端可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality，VR)终端、增强现实(Augmented Reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等，本发明实施例对上述具体应用场景或应用对象不做限定。终端有时也可以称为终端、接入终端、UE单元、UE站、移动站、移动台、远方站、远程终端、移动设备、UE终端、无线通信设备、UE代理或UE装置等，本发明实施例对此不做限定。
以上述终端为移动终端(如手机)为例进行说明，图2是根据本发明实施例提供的移动终端的硬件结构框图。如图2所示，移动终端可以包括一个或多个(图2中仅示出一个)处理器202(处理器202可以包括但不限于微处理器(Microprocessor Control Unit，MCU)或可编程逻辑器件(Field Programmable Gate Array，FPGA)等的处理装置)和用于存储数据的存储器204，可选地，上述移动终端还可以包括用于通信功能的传输设备206以及输入输出设备208。本领域普通技术人员可以理解，图2所示的结构仅为示意，其并不对上述移动终端的结构造成限定。例如，移动终端还可包括比图2中所示更多或者更少的组件，或者具有与图2所示不同的配置。
存储器204可用于存储计算机程序，例如，应用软件的软件程序以及模块，如本发明实施例中的信息发送方法对应的计算机程序，处理器202通过运行存储在存储器204内的计算机程序，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器204可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些示例中，存储器204可进一步包括相对于处理器202远程设置的存储器，这些远程存储器可以通过网络连接至移动终端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输设备206用于经由一个网络接收或者发送数据。上述的网络具体实例可包括移动终端的通信供应商提供的无线网络。在一示例中，传输设备206包括一个网络适配器(Network Interface Controller，NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一示例中，传输设备206可以为射频(Radio Frequency，RF)模块，其用于通过无线方式与互联网进行通讯。
本发明实施例中涉及终端、第一网络设备、第二网络设备三个实体之间的信息交互，并主要涉及Uu口和Xn口的信令传输；其中，第一网络设备为源网络设备，例如，源基站，第二网络设备为切换流程中的目标网络设备，例如，目标基站，第二网络设备具体可为第一网络设备相邻小区的网络设备；本发明实施例中的终端为连接态的终端。上述终端、第一网络设备、第二网络设备可分别对应上述图1所示的网络构架中的终端110、基站101以及基站102。
以下对于本发明实施例中的切换方法及装置、信息发送方法及装置的工作方式进行阐述：
实施例1
本发明实施例提供了一种切换方法，应用于第一网络设备，图3是根据本发明实施例提供的切换方法的流程图，如图3所示，本实施例中的切换方法包括：
S102，第一网络设备向第二网络设备发送切换请求；其中，切换请求中携带了广播多播业务MBS会话/承载信息。
S104，第一网络设备接收第二网络设备发送的切换请求响应，切换请求响应包含以下至少之一：第二网络设备可接纳的MBS会话/承载信息，第二网络设备无法接纳的MBS会话/承载信息，第二网络设备的UE调度配置信息，第二网络设备的承载配置信息。
需要进一步说明的是，上述MBS会话/承载信息中，MBS会话信息用于指示MBS会话，MBS承载信息用于指示MBS承载。
需要进一步说明的是，上述切换请求响应中包含的第二网络设备的UE调度配置信息与第二网络设备的承载配置信息，对于第一网络设备而言可采用透传的方式进一步发送至UE。
通过本实施例中的切换方法，由于可以令第一网络设备向第二网络设备发送切换请求；其中，切换请求中携带了MBS会话/承载信息，MBS会话信息用于指示MBS会话，MBS承载信息用于指示MBS承载；并令第一网络设备接收第二网络设备发送的切换请求响应，切换请求响应包括以下至少之一：第二网络设备可接纳的MBS会话/承载信息，第二网络设备无法接纳的MBS会话/承载信息，第二网络设备的UE调度配置信息，第二网络设备的承载配置信息。因此，通过本发明实施例中的切换方法及装置、信息发送方法及装置，可以解决相关技术中如何实现跨基站的切换流程的问题，以达到可实现跨基站的切换过程中有效保障广播/多播业务的连续性的效果。
具体而言，通过本发明实施例中的切换方法，可以在5G NR的场景下，建立了跨gNB的切换流程执行的具体方式，并在切换过程中，可保障连接态的UE的移动性以及广播/多播业务的连续性。
需要进一步说明的是，上述实施例中，可选地，MBS会话信息还用于指示，MBS会话所对应的MBS业务；MBS会话与MBS业务是一一对应的，故MBS会话信息所指示的MBS会话即可对应至相应的MBS业务。
可选地，MBS会话/承载信息包括以下至少之一：
终端感兴趣的MBS会话信息，终端当前接收的MBS会话/承载信息，终端能力信息。
可选地，终端感兴趣的MBS会话信息包括以下至少之一：
终端感兴趣的MBS会话的标识信息，MBS区域标识，接收优先级信息，终端期望的MBS会话接收模式信息。
可选地，接收优先级信息包括以下至少之一：
优先单播接收，优先广播/多播接收，接收MBS会话的优先级别。
可选地，终端当前接收的MBS会话/承载信息包括以下至少之一：
终端当前接收MBS会话/承载的标识信息，终端当前接收MBS会话/承载的接收模式信息，终端当前接收的MBS承载的无线承载配置信息，终端当前接收的MBS会话/承载的服务质量服务质量(Quality of Service，QoS)配置信息。
可选地，终端期望的MBS会话接收模式信息包括以下至少之一：点到点(Point-To-Point，PTP)接收，点到多点(Point-To-Multipoint，PTM)接收，PTP 和PTM同时接收；
终端当前接收MBS会话/承载的接收模式信息包括以下至少之一：PTP接收，PTM接收，PTP和PTM同时接收。
可选地，终端能力信息用于指示：终端支持在同一个时隙中接收单播业务和MBS会话；或者，终端不支持在同一个时隙中接收单播业务和MBS会话。
可选地，无线承载配置信息包括：PTP承载配置信息，和/或，PTM承载配置信息；
其中，PTP承载配置信息用于配置PTP承载，PTP承载配置信息包括以下至少之一：
PTP无线承载标识，服务数据适配协议(Service Data Adaptation Protocol，SDAP)配置信息，分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)配置信息，无线链路控制(Radio Link Control，RLC)承载配置信息；
PTM承载配置信息用于配置PTM承载，PTM承载配置信息包括以下至少之一：
PTM无线承载标识，逻辑信道标识，SDAP配置信息，PDCP配置信息，RLC承载配置信息。
可选地，终端感兴趣的MBS会话的标识信息包括以下至少之一：MBS会话标识，MBS会话的临时移动组标识(Temporary Mobile Group Identity，TMGI)，指示广播/多播会话的协议数据单元(Protocol Data Unit，PDU)会话标识。
可选地，切换请求响应中所指示的可接纳的MBS会话/承载信息包括以下至少之一：
第二网络设备可接纳的MBS会话/承载标识，广播/多播业务会话的接收模式，可接纳的业务会话/承载QoS配置信息。
可选地，切换请求响应中所指示的无法接纳的MBS会话/承载信息包括以下至少之一：
第二网络设备无法接纳的MBS会话/承载标识，第二网络设备无法接纳MBS会话/承载标识对应的MBS会话/承载的原因。
可选地，第二网络设备的承载配置信息包括以下至少之一：
PTM无线承载标识，逻辑信道标识，SDAP配置信息，PDCP配置信息，RLC承载配置信息。
可选地，切换请求响应中所指示的第二网络设备的UE调度配置信息包括以 下至少之一：
多播业务信道的调度信息，配置多播业务信道所需的物理层参数。
可选地，切换请求响应还包含以下至少之一：第二网络设备的***信息块配置信息、多播控制信道配置信息、多播业务信道配置信息。
可选地，向第二网络设备发送切换请求，包括：
发送切换请求至接入移动性管理功能(Access and Mobility Management Function，AMF)，并通过AMF将切换请求转发至第二网络设备；其中，第二网络设备接收的切换请求中携带有MBS会话承载信息。
需要进一步说明的是，上述AMF可指示核心网中接入移动性管理功能或网关。
可选地，在向第二网络设备发送切换请求之前，方法还包括：
接收终端发送的广播/多播业务频点的测量结果。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件实现。基于这样的理解，本申请可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
实施例2
本发明实施例提供了一种信息发送方法，应用于UE，图4是根据本发明实施例提供的信息发送方法的流程图，如图4所示，本实施例中的信息发送方法包括：
S202，UE向第一网络设备发送UE感兴趣的MBS指示信息与UE正在接收的MBS指示信息。
S204，UE接收第一网络设备根据UE感兴趣的MBS指示信息返回的无线资源控制(Radio Resource Control，RRC)重配置信息。
可选地，UE感兴趣的MBS指示信息还包括：
UE感兴趣的MBS的业务标识信息；
其中，MBS的业务标识信息还包括以下至少之一：MBS业务/会话标识，MBS的临时移动组标识TMGI，MBS标识，指示MBS会话的PDU会话标识。
可选地，UE感兴趣的MBS指示信息还包括：
UE感兴趣的MBS的接收模式；
其中，接收模式包括以下至少之一：单播接收，广播/多播接收，单播和多播同时接收。
可选地，UE感兴趣的MBS指示信息还包括：
UE感兴趣的MBS的所属服务区域。
可选地，RRC重配置信息包括：
目标小区标识，可接纳的MBS列表，可接纳的MBS的配置信息，可接纳的MBS的接收模式信息。
可选地，可接纳的MBS的配置信息包含以下至少之一：
PTM无线承载标识，逻辑信道标识，SDAP配置信息，PDCP配置信息，RLC承载配置信息。
可选地，可接纳的MBS的配置信息包含以下至少之一：
多播业务信道的调度信息，配置多播业务信道所需的物理层参数。
可选地，可接纳的MBS的接收模式信息包含以下至少之一：
单播接收，广播/多播接收，单播和多播同时接收。
可选地，接收第一网络设备根据MBS指示信息返回的RRC重配置信息之后，还包括：
释放第一网络设备的资源，并根据来自第二网络设备的无线承载配置信息进行PDCP和RLC的重建，以及媒体接入控制(Media Access Control，MAC)的重设置，进而建立PTM承载，基于PTM承载进行业务接收。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件实现。基于这样的理解，本申请可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
实施例3
本发明实施例提供了一种切换方法，应用于第二网络设备，图5是根据本发明实施例提供的切换方法的流程图，如图5所示，本实施例中的切换方法包括：
S302，第二网络设备接收第一网络设备发送的切换请求；其中，切换请求 中携带了MBS会话/承载信息，MBS会话信息用于指示MBS会话，MBS承载信息用于指示MBS承载。
S304，第二网络设备根据切换请求返回切换响应至第一网络设备，其中，切换响应用于指示以下至少之一：第二网络设备可接纳的MBS会话/承载信息，第二网络设备无法接纳的MBS会话/承载信息，第二网络设备的UE调度配置信息，第二网络设备的承载配置信息。
需要进一步说明的是，本实施例中的切换方法的其余可选实施例及技术效果均与实施例1中的切换方法相对应，故在此不再赘述。
可选地，MBS会话/承载信息包括以下至少之一：
终端感兴趣的MBS会话信息，终端当前接收的MBS会话/承载信息，终端能力信息。
可选地，终端感兴趣的MBS会话信息包括以下至少之一：
终端感兴趣的MBS会话的标识信息，MBS区域标识，接收优先级信息，终端期望的MBS会话接收模式信息。
可选地，接收优先级信息包括以下至少之一：
优先单播接收，优先广播/多播接收，接收MBS会话的优先级别。
可选地，终端当前接收的MBS会话/承载信息包括以下至少之一：
终端当前接收MBS会话/承载的标识信息，终端当前接收MBS会话/承载的接收模式信息，终端当前接收的MBS承载的无线承载配置信息，终端当前接收的MBS会话/承载的服务质量QoS配置信息。
可选地，终端期望的MBS会话接收模式信息包括以下至少之一：点到点PTP接收，点到多点PTM接收，PTP和PTM同时接收；
终端当前接收MBS会话/承载的接收模式信息包括以下至少之一：PTP接收，PTM接收，PTP和PTM同时接收。
可选地，终端能力信息用于指示：终端支持在同一个时隙中接收单播业务和MBS会话；或者，终端不支持在同一个时隙中接收单播业务和MBS会话。
可选地，无线承载配置信息包括：PTP承载配置信息，和/或，PTM承载配置信息；
其中，PTP承载配置信息用于配置PTP承载，PTP承载配置信息包括以下至少之一：
PTP无线承载标识，服务数据适配协议SDAP配置信息，分组数据聚汇协 议PDCP配置信息，无线链路控制RLC承载配置信息；
PTM承载配置信息用于配置PTM承载，PTM承载配置信息包括以下至少之一：
PTM无线承载标识，逻辑信道标识，SDAP配置信息，PDCP配置信息，RLC承载配置信息。
可选地，终端感兴趣的MBS会话的标识信息包括以下至少之一：MBS会话标识，MBS会话的临时移动组标识TMGI，指示广播/多播会话的PDU会话标识；
可选地，切换请求响应中所指示的可接纳的MBS会话/承载信息包括以下至少之一：
第二网络设备可接纳的MBS会话/承载标识，广播/多播业务会话的接收模式，可接纳的业务会话/承载QoS配置信息。
可选地，切换请求响应中所指示的无法接纳的MBS会话/承载信息包括以下至少之一：
第二网络设备无法接纳的MBS会话/承载标识，第二网络设备无法接纳MBS会话/承载标识对应的MBS会话/承载的原因。
可选地，第二网络设备的承载配置信息包括以下至少之一：
PTM无线承载标识，逻辑信道标识，SDAP配置信息，PDCP配置信息，RLC承载配置信息。
可选地，切换请求响应中所指示的第二网络设备的UE调度配置信息包括以下至少之一：
多播业务信道的调度信息，配置多播业务信道所需的物理层参数。
可选地，切换请求响应还包含以下至少之一：第二网络设备的***信息块配置信息、多播控制信道配置信息、多播业务信道配置信息。
可选地，向第二网络设备发送切换请求，包括：
发送切换请求至接入移动性管理功能AMF，并通过AMF将切换请求转发至第二网络设备；其中，第二网络设备接收的切换请求中携带有MBS会话承载信息。
可选地，MBS会话信息还用于指示，MBS会话所对应的MBS业务；
其中，MBS会话与MBS业务一一对应。
为进一步说明上述实施例1至实施例3中记载的切换方法与信息发送方法， 以下通过示例性的实施例进一步阐述上述切换方法与信息发送方法所指示的终端、第一网络设备与第二网络设备之间的交互过程。
示例实施例1
本示例实施例阐述了本发明实施例中MBS会话建立的过程，具体而言，终端、源基站、邻小区基站之间可通过以下方式之一建立MBS会话：Xn Setup流程、gNB Configuration Update流程、操作维护管理(Operation Administration and Maintenance，OAM)；需要进一步说明的是，本示例实施例中的源基站等同于本发明实施例中的源网络设备，本示例实施例中的邻小区基站等同于本发明实施例中的目标网络设备。以下通过三个示例对上述三种建立方式进行说明。
示例一：Xn Setup流程
图6是根据本发明示例性实施例提供的MBS会话建立的交互流程图，如图6所示，本示例中基于Xn Setup流程建立MBS会话的流程如下：
S1，源基站(Source gNB)向邻小区基站(Neighbouring gNB)发送Xn建立请求消息，其中携带了获取邻区MBS业务信息的信元(Information Element，IE)，用来请求邻小区基站响应各小区有哪些MBS业务以及所属的小区标识(该小区标识是网络内唯一，如NR小区全局标识符(Cell Global Identifier，CGI))。
S2，邻小区基站收到来自源基站的Xn建立请求消息，并携带了获取邻区MBS业务信息的IE。邻小区基站就会将其服务的小区中有哪些MBS业务以及所属的小区标识一同通过Xn建立响应消息告知给源基站。
S3，源基站收到带有邻区的MBS业务信息及其所属小区标识的Xn建立响应消息后，会通过***消息块(System Information Block，SIB)消息或专用RRC消息通知到UE。
S4，UE收到源基站发来的邻区有哪些MBS业务信息及其所属小区标识后，就会触发UE的MBS兴趣指示信息的上报。
示例二：gNB Configuration Update流程
图7是根据本发明示例性实施例提供的MBS会话建立的交互流程图，如图7所示，本示例中基于gNB Configuration Update流程建立MBS会话的流程如下：
S1，源基站(Source gNB)向邻小区基站(Neighbouring gNB)发送gNB Configuration Update消息，其中会携带获取邻区MBS业务信息的IE，用来请求邻小区基站响应各小区有哪些MBS业务以及所属的小区标识(该小区标识是网络内唯一，如NR CGI)。
S2，邻小区基站收到来自源基站的gNB Configuration Update消息，并携带 了获取邻区MBS业务信息的IE。邻小区基站就会将其服务的小区中有哪些MBS业务以及所属的小区标识一同通过gNB Configuration Update ACK告知给源基站。
S3，源基站收到带有邻区的MBS业务信息及其所属小区标识的Xn建立响应消息后，会通过SIB消息或专用RRC消息通知到UE。
S4，UE收到源基站发来的邻区有哪些MBS业务信息及其所属小区标识后，就会触发UE的MBS兴趣指示信息的上报。
示例三：OAM
本示例中，相邻小区所拥有的MBS业务及其所属小区可通过OAM以预先为源基站进行配置，源基站直接可以通过SIB消息或专有RRC消息通知到UE。
示例实施例2
本示例实施例阐述了在示例实施例1中UE与源基站之间建立MBS会话的前提下，UE在源基站与目标基站之间进行切换的流程，上述UE在源基站与目标基站之间进行切换的流程如下：
首先，UE从业务/应用层直接拿到用户业务信息。
上述步骤用于UE进行兴趣上报，图8是根据本发明示例性实施例提供的UE兴趣上报的交互流程图，上述步骤中UE兴趣上报的过程如图8所示。
具体而言，UE获取业务/应用层可提供的MBS业务，及每个MBS业务的相关信息，如频点信息，MBS业务区域标识，MBS业务标识，业务的开始与结束时间等；UE收到业务相关信息后，会基于应用/业务层有的业务和自身的兴趣，去上报其感兴趣接收和正在接收的MBS业务，来辅助源gNB尽可能选择可以支持UE正在接收或感兴趣接收的MBS业务的目标小区。
需要说明的是，上述UE上报的MBS兴趣指示信息消息中的业务完全基于自身的兴趣。
上述步骤记载的技术方案中，UE对业务的兴趣上报是自主的行为，不受限于邻区是否存在其感兴趣的业务。gNB在为UE选择切换的目标小区时，尽可能选择能支持UE正在接收或感兴趣接收的MBS传输的小区。如果找不到一个目标小区能满足UE所有正在接收或感兴趣接收的MBS业务，则优先选择支持高优先级的或是正在接收的MBS业务的小区。因此，上述步骤具有更好的业务的灵活性。同时，应用/业务层的业务相关信息更新或变化都会通知到UE，随即就会触发UE上报其感兴趣的业务。
本示例实施例中，UE不仅可以从应用/业务层获得可提供的MBS业务，及 其MBS业务相关信息，图9是根据本发明示例性实施例提供的UE兴趣上报的交互流程图，UE兴趣上报的过程还可如图9所示，UE还可以通过读SIB消息获得本小区提供哪些MBS业务，及每个业务属于的业务区域，和邻区可提供哪些MBS业务及每个业务属于哪个MBS业务区域。
上述UE兴趣上报的目的其一是服务于业务的连续性。具体而言，对于连接态的UE，切换是基站主导行为(network-controlled handover)，即将UE切换到合适的目标小区。为了保证MBS业务的连续性，服务小区需要知道UE正在接收或感兴趣接收的MBS业务，这样才有可能将UE切换到其感兴趣的小区。同时，UE兴趣上报还可辅助基站调度。当目标基站通过MBS兴趣指示信息了解到UE对哪些广播多播业务感兴趣，因此在调度时会根据UE的能力尽量避免在同一个时隙中同时调度其感兴趣的广播多播传输和单播传输。
为实现上述技术目的，如图8或图9所示，本示例性实施例中，UE需发送MBS兴趣指示信息至源gNB，该MBS兴趣指示信息用于告诉基站UE正在接收或感兴趣接收的广播多播业务。本示例实施例中的MBS兴趣指示信息具体包含以下信息：
MBS业务标识列表：UE正在接收或感兴趣接收的MBS业务列表。业务标识用来标记每个广播多播业务。MBS业务列表按照UE对正在接收或感兴趣接收的MBS业务的兴趣优先级进行排序。即UE对于该表中排序在前的广播多播业务的兴趣要高于排序靠后的广播多播业务。
MBS接收优先级：指示相对于单播，UE是否优先接收MBS业务。如果收到的此信息为“true”，则有，UE在目标小区相对于单播业务传输优先接收MBS业务。此信息可能用于网络拥塞时，当目标基站收到此信息时，可能会释放掉单播承载，而优先接收广播多播传输。
可选地，上述MBS兴趣指示信息中还可以包括：
接收模式cast mode：UE期望采用哪种接收对应MBS业务数据；具体而言，可选的接收模式有：对于UE在MBS兴趣指示消息中上报的其正在接收或感兴趣接收的MBS业务期望采用哪种接收模式。
需要说明的是，UE上报的UE正在接收或感兴趣接收的MBS业务，即MBS兴趣指示信息中MBS业务标识列表，是来自于：1)应用/业务层通知下来的可提供的MBS业务，及该MBS业务其相关信息；需要说明的是，上述应用/业务层通知下来的可提供的MBS业务，及该MBS业务其相关信息在空口上是可提供的也是不可提供的，如空口上不可提供MBS上报的广播多播业务(将会触发UE向核心网请求该业务的建立)；2)通过Xn接口告知源基站邻区有哪些MBS 业务，通过SIB消息或专有RRC消息告知UE，基于邻区有的MBS业务，UE会上报其感兴趣或正在接收的MBS业务，此业务在空口上一定可提供。
上述UE上报的其自身正在接收或感兴趣接收的MBS业务，是按照UE对MBS业务的兴趣优先级的顺序排序进行上报的。对于MBS接收优先级，其可具体用于，当网络拥塞时，基站可以决定释放掉单播承载，而优先接收广播多播传输的数据。
进一步地，对于正在进行MBS接收或对MBS感兴趣的UE，源gNB可以为UE配置对UE感兴趣接收的MBS频点进行测量，UE对相应的频点进行测量并上报测量结果，如果源gNB发现UE上报的测量结果包含高优先级MBS业务对应的频点，则源gNB可将UE切换到高优先级MBS业务对应的频点所在的小区。
gNB在为UE选择切换的目标小区时，尽可能选择能支持UE正在接收或感兴趣接收的MBS传输的小区。即使找不到一个目标小区能满足UE所正在接收或感兴趣接收的MBS业务，则优先选择支持高优先级的或是正在接收的MBS业务的小区。
进一步地，当源gNB为UE选择了目标小区后，源基站即可向目标基站发送切换请求消息，为实现MBS业务的连续性，切换请求消息中可包含以下信息中的至少之一：
1)UE的MBS兴趣指示信息，用来辅助源基站选择目标小区及目标基站的灵活调度。
具体而言，上述UE的MBS兴趣指示信息可包括：1.1)MBS业务列表；1.2)MBS接收优先级。可选地，上述切换请求消息中还可以包括UE对感兴趣的业务期望采用的接收模式。
上述MBS兴趣指示信息可辅助源基站在执行目标小区选择时，尽可能的选择可以支持UE感兴趣或正在接收的MBS业务的小区进而保证了一定的业务连续性以及目标基站在了解到UE对哪些MBS业务感兴趣后的灵活调度，避免同一时隙同时调度同一MBS业务。
2)UE当前接收的MBS业务信息，如所接收的MBS业务所对应的MBS会话标识信息，该MBS会话承载配置信息，如PTM承载配置信息和/或PTP承载配置信息。
具体而言，上述MBS业务信息可包括：2.1)MBS会话标识信息，该信息指示了UE当前所接收的MBS业务对应的MBS会话的MBS会话标识信息，可能包含一个或多个MBS会话标识，广播多播业务的临时移动组标识TMGI，广 播多播业务标识，指示MBS会话的PDU会话标识，IP多播地址；2.2)无线承载配置信息，该无线承载配置信息配置MBS会话的无线承载，指示了UE当前所接收的MBS会话承载配置信息，无线承载配置信息具体可进一步包括：PTP承载配置信息和/或PTM承载配置信息。PTP承载配置信息具体包括：PTP无线承载标识，服务数据适配协议SDAP配置，分组数据聚汇协议PDCP配置，无线链路控制RLC配置；PTM配置信息包括：PTM无线承载标识，SDAP配置，PDCP配置和RLC配置。可选地，空口资源配置如接收当前MBS业务的调度信息，多播业务信道的调度信息，接收当前MBS业务的物理层参数。
通过上述无线承载配置信息，如当UE在目标小区接收的MBS业务和在源小区接收的MBS业务相同时，目标基站可以采用与源基站相同的一套承载配置信息，即无线承载配置，以及多播业务信道的调度信息和接收当前MBS业务的物理层参数，去接收MBS业务。另一种方案是，对于底层的配置，如多播业务信道的调度信息和接收当前MBS业务的物理层参数是实时变化的，因此这部分信息源基站可以不发送给目标基站，而是由目标基站进行配置，然后通知到UE。
可选地，MBS业务信息中还可以包括：UE当前接收的MBS会话所采用的接收模式，可包含该MBS业务对应的MBS业务标识、业务区域标识。
3)该MBS会话内的QoS流的QoS配置信息，如该会话内的QoS流标识列表，对应于每个QoS流标识的QoS流等级的QoS参数。
具体而言，QoS配置信息指示了映射到UE当前正在接收的MBS业务对应的无线承载的QoS流列表中的每个QoS流，包括一个或多个QoS流标识，QoS流等级的QoS参数，MBS会话标识信息。
4)UE接收当前MBS业务标识所对应的MBS数据时使用PTP无线承载还是PTM无线承载的指示信息。
5)UE的MBS接收能力，指示了所述终端是否支持在同一个时隙内同时接收单播传输和广播多播传输的能力。上述UE的MBS接收能力可让目标网络设备在调度时将其终端能力考虑进去，进而避免调度结果与所述终端能力产生冲突。
进一步地，目标基站接收到切换请求消息后，即可返回切换请求响应消息，目标基站在切换请求响应消息中可包含以下信息的至少之一：
1)可接纳/可支持的UE感兴趣的MBS会话资源以及无法接纳/无法支持的UE感兴趣的MBS会话资源；
具体而言，目标基站收到上述切换请求消息后，需判断哪些MBS业务资源能接纳，哪些不能接纳，并在切换请求响应消息中包含MBS业务资源的接纳列 表以及MBS业务资源的无法接纳列表。
2)对于每一个可接纳的UE感兴趣的MBS会话资源，包含可接纳的QoS流列表和不可接纳的QoS流列表，及该MBS会话对应的PTP/PTM接收方式指示，PTP/PTM承载配置。
具体而言，目标基站还可以在切换请求响应消息中给出对应的MBS会话在目标基站采用的接收方式，如PTP和/或PTM方式接收，并给出两种方式下对应的无线承载配置。此外，还可以给出相应的接收方式的无线承载的QoS配置。
可选地，目标基站还可以在切换响应消息中包含目标小区的SIB信息，MBS控制信道及MBS业务信道配置信息。
此外，对于UE感兴趣的或正在接收的MBS业务，目标基站有可能已经与多小区/多播协调实体(Multi-cell/Multicast Coordination Entity，MCE)/AMF建立了对应的MBS会话，对于上述MBS业务，目标基站仅需要考虑为UE配置PTP和/或PTM方式进行MBS接收。对于能支持MBS的目标基站，但尚未与MCE/AMF建立MBS会话的MBS业务，目标基站可向MCE/AMF发起MBS会话的建立请求。
可选地，对于每一个无法接纳的UE感兴趣的MBS会话资源，切换请求响应消息中还可包括MBS会话标识以及不接纳该MBS会话资源的原因。
可选地，切换请求响应消息还可以包含目标小区的SIB信息及MBS控制信道及业务信道配置信息。
进一步地，目标基站在向源基站返回切换请求响应消息的同时/之后，还可发送切换命令消息至UE，该切换命令消息中包含了RRC重配消息，RRC重配消息具体包含：对应的MBS会话通过哪种接收方式来接收，以及对应接收模式的无线承载(Radio Bearer，RB)配置(数据无线承载/多播无线承载(Data Radio Bearer/Multicast Radio Bearer，DRB/MRB))。
具体而言，对于通过PTM接收的方式，目标基站在切换响应/命令消息中还需指示哪些MBS业务资源需要用PTM方式进行传输以及对应的MRB配置。对于PTP与PTM接收的方式，目标基站在切换响应消息中还需指示通过PTM以及PTP方式接纳该MBS业务资源，同时在RRC重配消息中给出对应的配置。
可选地，上述切换命令消息中还包括能支持的MBS业务的QoS profile指示。
进一步地，UE在接收上述目标基站发送的切换命令消息后，还可向目标基站返回确认消息，以确认RRC连接重新配置完成。
以下通过一示例具体阐述上述UE在源基站与目标基站之间实现切换的过 程：
示例四：
图10是根据本发明示例性实施例提供的切换方法的交互流程图，本示例中UE在源基站与目标基站之间实现切换的流程如图10所示，上述切换的具体流程如下：
S1，UE从业务/应用层获得可提供哪些MBS业务，及每个MBS业务的相关信息；具体包括：该MBS业务标识(例如，TMGI、MBS service ID)，所在频点信息，所在的MBS业务区域和该MBS业务的开始和结束时间。此外，UE会读取***消息，从而知道当前小区和邻区有哪些MBS业务以及每个业务所属的MBS业务区域。
S2，UE收到业务/应用层关于MBS业务的相关信息，以及邻区可提供的MBS业务后，基于这些信息，UE会通过MBS兴趣指示信息消息上报其正在接收或感兴趣接收的MBS业务给源基站。UE上报的MBS业务是按照其对业务感兴趣的优先级进行排序后上报的。此外，为了服务于MBS的业务连续性和支持灵活调度，MBS兴趣指示信息消息中还可能包括以下信息任意组合：UE感兴趣和正在接收的MBS业务列表，MBS传输相对于单播接收的优先级。可选的，MBS兴趣指示信息消息中还包括当前接收的MBS业务的接收模式以及UE能力。
S3，UE会对网络为其配置的UE感兴趣接收的频点进行测量，并通过测量报告消息将测量结果上报给源基站。基站会尽量选择可以支持UE正在接收的或感兴趣接收的广播多播业务的小区。
S4，源基站通过Xn接口向目标基站发送切换请求消息，其目的是为切换(Handover)请求资源，并将源基站侧的UE上下文告知目标基站；切换请求消息具体可以包含下列信息中的至少之一：UE上报的兴趣指示信息，UE当前的接收的MBS业务信息(例如，所接收的MBS业务所对应的MBS会话标识信息)，该MBS会话承载配置信息(例如，PTM承载配置信息和/或PTP承载配置信息)，该MBS会话内的QoS流的QoS配置信息(例如，该会话内的QoS流标识列表，对应于每个QoS流标识的QoS流等级的QoS参数)，UE接收当前MBS业务标识所对应的MBS数据是使用PTP无线承载还是PTM无线承载的指示信息，UE的MBS接收能力信息。
S5，目标基站收到切换请求消息后，会执行接纳控制，判断哪些MBS会话资源能接纳，哪些MBS会话资源不能接纳，并返回切换请求响应消息至源基站。其中，在可接纳的MBS会话中还会包含可接纳的QoS流列表和不可接纳的QoS 流列表，及该MBS会话对应的PTP/PTM接收方式指示，PTP/PTM承载配置。
其中，对于不可接纳的MBS会话资源会包含该MBS会话标识以及不接纳MBS会话资源的原因。
可选的，还可以在切换响应消息中包含目标小区的SIB信息，MBS控制信道及MBS业务信道配置信息。
S6，目标基站可在要发送给UE的切换命令中包含RRC重配消息，其中主要包含：MBS业务通过哪种接收模式来接收，对应的接收的模式的无线承载配置。
S7，UE会向目标基站响应一个RRC重配完成消息，其目的是用来确定已经成功连接一个RRC连接配置。以此，就可以通过目标基站以PTP和/或PTM的接收方式来接收相应的广播多播业务。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件实现。基于这样的理解，本申请的技术方案可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
实施例4
本发明实施例提供了一种切换装置，应用于第一网络设备，该装置用于实现上述实施例及可选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图11是根据本发明实施例提供的切换装置的结构框图，如图11所示，本实施例中的切换装置包括：
第一发送模块402，用于向第二网络设备发送切换请求；其中，切换请求中携带了广播多播业务MBS会话/承载信息；
第一接收模块404，用于接收第二网络设备发送的切换请求响应，切换请求响应包含以下至少之一：
第二网络设备可接纳的MBS会话/承载信息，第二网络设备无法接纳的MBS会话/承载信息，第二网络设备的UE调度配置信息，第二网络设备的承载配置信息。
需要进一步说明的是，本实施例中的切换装置的其余可选实施例及技术效果均与实施例1中记载的切换方法相对应，故在此不再赘述。
可选地，MBS会话/承载信息包括以下至少之一：
终端感兴趣的MBS会话信息，终端当前接收的MBS会话/承载信息，终端能力信息。
可选地，终端感兴趣的MBS会话信息包括以下至少之一：
终端感兴趣的MBS会话的标识信息，MBS区域标识，接收优先级信息，终端期望的MBS会话接收模式信息。
可选地，接收优先级信息包括以下至少之一：
优先单播接收，优先广播/多播接收，接收MBS会话的优先级别。
可选地，终端当前接收的MBS会话/承载信息包括以下至少之一：
终端当前接收MBS会话/承载的标识信息，终端当前接收MBS会话/承载的接收模式信息，终端当前接收的MBS承载的无线承载配置信息，终端当前接收的MBS会话/承载的服务质量QoS配置信息。
可选地，终端期望的MBS会话接收模式信息包括以下至少之一：点到点PTP接收，点到多点PTM接收，PTP和PTM同时接收；
终端当前接收MBS会话/承载的接收模式信息包括以下至少之一：PTP接收，PTM接收，PTP和PTM同时接收。
可选地，终端能力信息用于指示：终端支持在同一个时隙中接收单播业务和MBS会话；或者，终端不支持在同一个时隙中接收单播业务和MBS会话。
可选地，无线承载配置信息包括：PTP承载配置信息，和/或，PTM承载配置信息；
其中，PTP承载配置信息用于配置PTP承载，PTP承载配置信息包括以下至少之一：
PTP无线承载标识，服务数据适配协议SDAP配置信息，分组数据聚汇协议PDCP配置信息，无线链路控制RLC承载配置信息；
PTM承载配置信息用于配置PTM承载，PTM承载配置信息包括以下至少之一：
PTM无线承载标识，逻辑信道标识，SDAP配置信息，PDCP配置信息，RLC承载配置信息。
可选地，终端感兴趣的MBS会话的标识信息包括以下至少之一：MBS会 话标识，MBS会话的临时移动组标识TMGI，指示广播/多播会话的PDU会话标识。
可选地，切换请求响应中所指示的可接纳的MBS会话/承载信息包括以下至少之一：
第二网络设备可接纳的MBS会话/承载标识，广播/多播业务会话的接收模式，可接纳的业务会话/承载QoS配置信息。
可选地，切换请求响应中所指示的无法接纳的MBS会话/承载信息包括以下至少之一：
第二网络设备无法接纳的MBS会话/承载标识，第二网络设备无法接纳MBS会话/承载标识对应的MBS会话/承载的原因。
可选地，第二网络设备的承载配置信息包括以下至少之一：
PTM无线承载标识，逻辑信道标识，SDAP配置信息，PDCP配置信息，RLC承载配置信息。
可选地，切换请求响应中所指示的第二网络设备的UE调度配置信息包括以下至少之一：
多播业务信道的调度信息，配置多播业务信道所需的物理层参数。
可选地，切换请求响应还包含以下至少之一：第二网络设备的***信息块配置信息、多播控制信道配置信息、多播业务信道配置信息。
可选地，向第二网络设备发送切换请求，包括：
发送切换请求至接入移动性管理功能AMF，并通过AMF将切换请求转发至第二网络设备；其中，第二网络设备接收的切换请求中携带有MBS会话承载信息。
可选地，向第二网络设备发送切换请求之前，方法还包括：
接收终端发送的广播/多播业务频点的测量结果。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例5
本发明实施例提供了一种信息发送装置，应用于终端，该装置用于实现上述实施例及可选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的 装置以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图12是根据本发明实施例提供的信息发送装置的结构框图，如图12所示，本实施例中的信息发送装置包括：
第二发送模块502，用于向第一网络设备发送UE感兴趣的MBS指示信息与UE正在接收的MBS指示信息；
第二接收模块504，用于接收第一网络设备根据UE感兴趣的MBS指示信息返回的RRC重配置信息。
需要进一步说明的是，本实施例中的信息发送装置的其余可选实施例及技术效果均与实施例2中记载的信息发送方法相对应，故在此不再赘述。
可选地，UE感兴趣的MBS指示信息还包括：
UE感兴趣的MBS的业务标识信息；
其中，MBS的业务标识信息还包括以下至少之一：MBS业务/会话标识，MBS的临时移动组标识TMGI，MBS标识，指示MBS会话的PDU会话标识。
可选地，UE感兴趣的MBS指示信息还包括：
UE感兴趣的MBS的接收模式；
其中，接收模式包括以下至少之一：单播接收，广播/多播接收，单播和多播同时接收。
可选地，UE感兴趣的MBS指示信息还包括：
UE感兴趣的MBS的所属服务区域。
可选地，RRC重配置信息包括：
目标小区标识，可接纳的MBS列表，可接纳的MBS的配置信息，可接纳的MBS的接收模式信息。
可选地，可接纳的MBS的配置信息包含以下至少之一：
PTM无线承载标识，逻辑信道标识，SDAP配置信息，PDCP配置信息，RLC承载配置信息。
可选地，可接纳的MBS的配置信息包含以下至少之一：
多播业务信道的调度信息，配置多播业务信道所需的物理层参数。
可选地，可接纳的MBS的接收模式信息包含以下至少之一：
单播接收，广播/多播接收，单播和多播同时接收。
可选地，接收第一网络设备根据MBS指示信息返回的RRC重配置信息之后，还包括：
释放第一网络设备的资源，并根据来自第二网络设备的无线承载配置信息进行PDCP和RLC的重建，以及MAC的重设置，进而建立PTM承载，基于PTM承载进行业务接收。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例6
本发明实施例提供了一种切换装置，应用于第二网络设备，该装置用于实现上述实施例及可选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图13是根据本发明实施例提供的切换装置的结构框图，如图13所示，本实施例中的切换装置包括：
第三接收模块602，用于接收第一网络设备发送的切换请求；其中，切换请求中携带了MBS会话/承载信息，MBS会话信息用于指示MBS会话，MBS承载信息用于指示MBS承载；
返回模块604，用于根据切换请求返回切换响应至第一网络设备，其中，切换响应用于指示以下至少之一：第二网络设备可接纳的MBS会话/承载信息，第二网络设备无法接纳的MBS会话/承载信息，第二网络设备的UE调度配置信息，第二网络设备的承载配置信息。
需要进一步说明的是，本实施例中的切换装置的其余可选实施例及技术效果均与实施例3中的切换方法相对应，故在此不再赘述。
可选地，MBS会话/承载信息包括以下至少之一：
终端感兴趣的MBS会话信息，终端当前接收的MBS会话/承载信息，终端能力信息。
可选地，终端感兴趣的MBS会话信息包括以下至少之一：
终端感兴趣的MBS会话的标识信息，MBS区域标识，接收优先级信息，终端期望的MBS会话接收模式信息。
可选地，接收优先级信息包括以下至少之一：
优先单播接收，优先广播/多播接收，接收MBS会话的优先级别。
可选地，终端当前接收的MBS会话/承载信息包括以下至少之一：
终端当前接收MBS会话/承载的标识信息，终端当前接收MBS会话/承载的接收模式信息，终端当前接收的MBS承载的无线承载配置信息，终端当前接收的MBS会话/承载的服务质量QoS配置信息。
可选地，终端期望的MBS会话接收模式信息包括以下至少之一：点到点PTP接收，点到多点PTM接收，PTP和PTM同时接收；
终端当前接收MBS会话/承载的接收模式信息包括以下至少之一：PTP接收，PTM接收，PTP和PTM同时接收。
可选地，终端能力信息用于指示：终端支持在同一个时隙中接收单播业务和MBS会话；或者，终端不支持在同一个时隙中接收单播业务和MBS会话。
可选地，无线承载配置信息包括：PTP承载配置信息，和/或，PTM承载配置信息；
其中，PTP承载配置信息用于配置PTP承载，PTP承载配置信息包括以下至少之一：
PTP无线承载标识，服务数据适配协议SDAP配置信息，分组数据聚汇协议PDCP配置信息，无线链路控制RLC承载配置信息；
PTM承载配置信息用于配置PTM承载，PTM承载配置信息包括以下至少之一：
PTM无线承载标识，逻辑信道标识，SDAP配置信息，PDCP配置信息，RLC承载配置信息。
可选地，终端感兴趣的MBS会话的标识信息包括以下至少之一：MBS会话标识，MBS会话的临时移动组标识TMGI，指示广播/多播会话的PDU会话标识。
可选地，切换请求响应中所指示的可接纳的MBS会话/承载信息包括以下至少之一：
第二网络设备可接纳的MBS会话/承载标识，广播/多播业务会话的接收模式，可接纳的业务会话/承载QoS配置信息。
可选地，切换请求响应中所指示的无法接纳的MBS会话/承载信息包括以下至少之一：
第二网络设备无法接纳的MBS会话/承载标识，第二网络设备无法接纳MBS 会话/承载标识对应的MBS会话/承载的原因。
可选地，第二网络设备的承载配置信息包括以下至少之一：
PTM无线承载标识，逻辑信道标识，SDAP配置信息，PDCP配置信息，RLC承载配置信息。
可选地，切换请求响应中所指示的第二网络设备的UE调度配置信息包括以下至少之一：
多播业务信道的调度信息，配置多播业务信道所需的物理层参数。
可选地，切换请求响应还包含以下至少之一：第二网络设备的***信息块配置信息、多播控制信道配置信息、多播业务信道配置信息。
可选地，向第二网络设备发送切换请求，包括：
发送切换请求至接入移动性管理功能AMF，并通过AMF将切换请求转发至第二网络设备；其中，第二网络设备接收的切换请求中携带有MBS会话承载信息。
可选地，向第二网络设备发送切换请求之前，方法还包括：
接收终端发送的广播/多播业务频点的测量结果。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例7
本发明的实施例还提供了一种计算机可读的存储介质，该计算机可读的存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
可选地，在本实施例中，上述计算机可读的存储介质可以被设置为存储用于执行上述实施例中的计算机程序。
可选地，在本实施例中，上述计算机可读的存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
实施例8
本发明的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方 法实施例中的步骤。
可选地，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
可选地，在本实施例中，上述处理器可以被设置为通过计算机程序执行上述实施例中的步骤。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
本领域的技术人员应该明白，上述的本申请的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本申请不限制于任何特定的硬件和软件结合。

Claims (35)

  1. 一种切换方法，应用于第一网络设备，所述方法包括：
    向第二网络设备发送切换请求，其中，所述切换请求中携带了广播多播业务MBS会话/承载信息；
    接收所述第二网络设备发送的切换请求响应，所述切换请求响应包括以下至少之一：
    所述第二网络设备可接纳的MBS会话/承载信息，所述第二网络设备无法接纳的MBS会话/承载信息，所述第二网络设备的终端UE调度配置信息，所述第二网络设备的承载配置信息。
  2. 根据权利要求1所述的方法，其中，所述MBS会话/承载信息包括以下至少之一：
    终端感兴趣的MBS会话/承载信息，终端当前接收的MBS会话/承载信息，终端能力信息。
  3. 根据权利要求2所述的方法，其中，所述终端感兴趣的MBS会话信息包括以下至少之一：
    所述终端感兴趣的MBS会话的标识信息，MBS区域标识，接收优先级信息，所述终端期望的MBS会话接收模式信息。
  4. 根据权利要求3所述的方法，其中，所述接收优先级信息包括以下至少之一：
    优先单播接收，优先广播/多播接收，接收MBS会话的优先级别。
  5. 根据权利要求2或3所述的方法，其中，所述终端当前接收的MBS会话/承载信息包括以下至少之一：
    所述终端当前接收的MBS会话/承载的标识信息，所述终端当前接收的MBS会话/承载的接收模式信息，所述终端当前接收的MBS承载的无线承载配置信息，所述终端当前接收的MBS会话/承载的服务质量QoS配置信息。
  6. 根据权利要求5所述的方法，其中，所述终端期望的MBS会话接收模式信息包括以下至少之一：点到点PTP接收，点到多点PTM接收，PTP和PTM同时接收；
    所述终端当前接收的MBS会话/承载的接收模式信息包括以下至少之一：PTP接收，PTM接收，PTP和PTM同时接收。
  7. 根据权利要求2所述的方法，其中，所述终端能力信息用于指示：所述终端支持在同一个时隙中接收单播业务和MBS会话；或者，所述终端不支持在 同一个时隙中接收单播业务和MBS会话。
  8. 根据权利要求5所述的方法，其中，所述无线承载配置信息包括以下至少之一：PTP承载配置信息，PTM承载配置信息；
    其中，所述PTP承载配置信息用于配置PTP承载，所述PTP承载配置信息包括以下至少之一：
    PTP无线承载标识，服务数据适配协议SDAP配置信息，分组数据汇聚协议PDCP配置信息，无线链路控制RLC承载配置信息；
    所述PTM承载配置信息用于配置PTM承载，所述PTM承载配置信息包括以下至少之一：
    PTM无线承载标识，逻辑信道标识，SDAP配置信息，PDCP配置信息，RLC承载配置信息。
  9. 根据权利要求3所述的方法，其中，所述终端感兴趣的MBS会话的标识信息包括以下至少之一：MBS会话标识，MBS会话的临时移动组标识TMGI，指示广播/多播会话的协议数据单元PDU会话标识。
  10. 根据权利要求1所述的方法，其中，所述切换请求响应中所指示的所述可接纳的MBS会话/承载信息包括以下至少之一：
    所述第二网络设备可接纳的MBS会话/承载标识，所述广播/多播业务会话的接收模式，可接纳的业务会话/承载QoS配置信息。
  11. 根据权利要求1所述的方法，其中，所述切换请求响应中所指示的所述无法接纳的MBS会话/承载信息包括以下至少之一：
    所述第二网络设备无法接纳的MBS会话/承载标识，所述第二网络设备无法接纳所述MBS会话/承载标识对应的MBS会话/承载的原因。
  12. 根据权利要求1所述的方法，其中，所述第二网络设备的承载配置信息包括以下至少之一：
    PTM无线承载标识，逻辑信道标识，SDAP配置信息，PDCP配置信息，RLC承载配置信息。
  13. 根据权利要求1所述的方法，其中，所述切换请求响应中所指示的所述第二网络设备的UE调度配置信息包括以下至少之一：
    多播业务信道的调度信息，配置多播业务信道所需的物理层参数。
  14. 根据权利要求1所述的方法，其中，所述切换请求响应还包括以下至少之一：所述第二网络设备的***信息块配置信息、多播控制信道配置信息、 多播业务信道配置信息。
  15. 根据权利要求1所述的方法，其中，所述向第二网络设备发送切换请求，包括：
    发送所述切换请求至接入移动性管理功能AMF，并通过所述AMF将所述切换请求转发至所述第二网络设备，其中，所述第二网络设备接收的所述切换请求中携带有所述MBS会话/承载信息。
  16. 根据权利要求1所述的方法，其中，所述MBS会话信息还用于指示：MBS会话所对应的MBS业务；
    其中，所述MBS会话与所述MBS业务一一对应。
  17. 一种信息发送方法，应用于终端UE，所述方法包括：
    向第一网络设备发送UE感兴趣的广播多播业务MBS指示信息与UE正在接收的MBS指示信息；
    接收所述第一网络设备根据所述UE感兴趣的MBS指示信息返回的无线资源控制RRC重配置信息。
  18. 根据权利要求17所述的方法，其中，所述UE感兴趣的MBS指示信息包括：
    所述UE感兴趣的MBS的业务标识信息；
    其中，所述MBS的业务标识信息包括以下至少之一：MBS业务/会话标识，MBS的临时移动组标识TMGI，MBS标识，指示MBS会话的协议数据单元PDU会话标识。
  19. 根据权利要求17所述的方法，其中，所述UE感兴趣的MBS指示信息还包括：
    所述UE感兴趣的MBS的接收模式；
    其中，所述接收模式包括以下至少之一：单播接收，广播/多播接收，单播和多播同时接收。
  20. 根据权利要求17所述的方法，其中，所述UE感兴趣的MBS指示信息还包括：
    所述UE感兴趣的MBS的所属服务区域。
  21. 根据权利要求17所述的方法，其中，所述RRC重配置信息包括：
    目标小区标识，可接纳的MBS列表，可接纳的MBS的配置信息，可接纳的MBS的接收模式信息。
  22. 根据权利要求21所述的方法，其中，所述可接纳的MBS的配置信息包括以下至少之一：
    点到多点PTM无线承载标识，逻辑信道标识，服务数据适配协议SDAP配置信息，分组数据汇聚协议PDCP配置信息，无线链路控制RLC承载配置信息。
  23. 根据权利要求21所述的方法，其中，所述可接纳的MBS的配置信息包括以下至少之一：
    多播业务信道的调度信息，配置多播业务信道所需的物理层参数。
  24. 根据权利要求21所述的方法，其中，所述可接纳的MBS的接收模式信息包括以下至少之一：
    单播接收，广播/多播接收，单播和多播同时接收。
  25. 根据权利要求21所述的方法，其中，在所述接收所述第一网络设备根据所述MBS指示信息返回的RRC重配置信息之后，还包括：
    释放所述第一网络设备的资源，并根据来自第二网络设备的无线承载配置信息进行PDCP和RLC的重建，以及媒体接入控制MAC的重设置，进而建立PTM承载，基于所述PTM承载进行业务接收。
  26. 一种切换方法，应用于第二网络设备，所述方法包括：
    接收第一网络设备发送的切换请求，其中，所述切换请求中携带了广播多播业务MBS会话/承载信息，所述MBS会话信息用于指示MBS会话，所述MBS承载信息用于指示MBS承载；
    根据所述切换请求返回切换响应至所述第一网络设备，其中，所述切换响应用于指示以下至少之一：所述第二网络设备可接纳的MBS会话/承载信息，所述第二网络设备无法接纳的MBS会话/承载信息，所述第二网络设备的终端UE调度配置信息，所述第二网络设备的承载配置信息。
  27. 根据权利要求26所述的方法，其中，所述MBS会话/承载信息包括以下至少之一：
    终端感兴趣的MBS会话/承载信息，终端当前接收的MBS会话/承载信息，终端能力信息。
  28. 根据权利要求27所述的方法，其中，所述终端感兴趣的MBS会话/承载信息包括以下至少之一：
    所述终端感兴趣的MBS会话的标识信息，MBS区域标识，接收优先级信息，所述终端期望的MBS会话/承载接收模式信息。
  29. 根据权利要求28所述的方法，其中，所述接收优先级信息包括以下至少之一：
    优先单播接收，优先广播/多播接收，接收MBS会话的优先级别。
  30. 根据权利要求27或28所述的方法，其中，所述终端当前接收的MBS会话/承载信息包括以下至少之一：
    所述终端当前接收的MBS会话/承载的标识信息，所述终端当前接收的MBS会话/承载的接收模式信息，所述终端当前接收的MBS承载的无线承载配置信息，所述终端当前接收的MBS会话/承载的服务质量QoS配置信息。
  31. 一种切换装置，设置于第一网络设备，所述装置包括：
    第一发送模块，设置为向第二网络设备发送切换请求，其中，所述切换请求中携带了广播多播业务MBS会话/承载信息；
    第一接收模块，设置为接收所述第二网络设备发送的切换请求响应，所述切换请求响应包括以下至少之一：
    所述第二网络设备可接纳的MBS会话/承载信息，所述第二网络设备无法接纳的MBS会话/承载信息，所述第二网络设备的终端UE调度配置信息，所述第二网络设备的承载配置信息。
  32. 一种信息发送装置，设置于终端UE，所述装置包括：
    第二发送模块，设置为向第一网络设备发送UE感兴趣的广播多播业务MBS指示信息与UE正在接收的MBS指示信息；
    第二接收模块，设置为接收所述第一网络设备根据所述UE感兴趣的MBS指示信息返回的无线资源控制RRC重配置信息。
  33. 一种切换装置，设置于第二网络设备，所述装置包括：
    第三接收模块，设置为接收第一网络设备发送的切换请求，其中，所述切换请求中携带了广播多播业务MBS会话/承载信息，所述MBS会话信息用于指示MBS会话，所述MBS承载信息用于指示MBS承载；
    返回模块，设置为根据所述切换请求返回切换响应至所述第一网络设备，其中，所述切换响应用于指示以下至少之一：所述第二网络设备可接纳的MBS会话/承载信息，所述第二网络设备无法接纳的MBS会话/承载信息，所述第二网络设备的终端UE调度配置信息，所述第二网络设备的承载配置信息。
  34. 一种计算机可读的存储介质，所述计算机可读的存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至16、权利要求17至25、权利要求26至30中任一项所述的方法。
  35. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至16、权利要求17至25、权利要求26至30中任一项所述的方法。
PCT/CN2021/094322 2020-05-18 2021-05-18 切换方法及装置、信息发送方法及装置 WO2021233279A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
KR1020227043470A KR20230011340A (ko) 2020-05-18 2021-05-18 핸드오버 방법 및 장치, 정보 송신 방법 및 장치
EP21809000.9A EP4156727A4 (en) 2020-05-18 2021-05-18 HANDOVER METHOD AND DEVICE AND INFORMATION TRANSMITTING METHOD AND DEVICE
US17/926,231 US20230199569A1 (en) 2020-05-18 2021-05-18 Handover method and apparatus, and information transmitting method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010421335.6A CN111866975A (zh) 2020-05-18 2020-05-18 切换方法及装置、信息发送方法及装置
CN202010421335.6 2020-05-18

Publications (1)

Publication Number Publication Date
WO2021233279A1 true WO2021233279A1 (zh) 2021-11-25

Family

ID=72985790

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/094322 WO2021233279A1 (zh) 2020-05-18 2021-05-18 切换方法及装置、信息发送方法及装置

Country Status (5)

Country Link
US (1) US20230199569A1 (zh)
EP (1) EP4156727A4 (zh)
KR (1) KR20230011340A (zh)
CN (1) CN111866975A (zh)
WO (1) WO2021233279A1 (zh)

Families Citing this family (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113498132B (zh) * 2020-04-03 2022-09-20 维沃移动通信有限公司 移动性管理方法、源基站、目标基站及终端设备
CN111866975A (zh) * 2020-05-18 2020-10-30 中兴通讯股份有限公司 切换方法及装置、信息发送方法及装置
CN116097820A (zh) 2020-08-06 2023-05-09 中兴通讯股份有限公司 用于管理多播和广播服务的技术
WO2022086240A1 (en) * 2020-10-22 2022-04-28 Samsung Electronics Co., Ltd. Method and system for handling service notification and configuration for mbs in 5g communication network
WO2022141255A1 (zh) * 2020-12-30 2022-07-07 Oppo广东移动通信有限公司 一种mbs业务的配置方法及装置、网络设备、终端设备
CN114696977A (zh) * 2020-12-30 2022-07-01 上海朗帛通信技术有限公司 一种被用于无线通信的通信节点中的方法和装置
WO2022141548A1 (zh) * 2020-12-31 2022-07-07 华为技术有限公司 一种数据传输方法及装置
CN114745677B (zh) * 2021-01-08 2023-05-16 维沃移动通信有限公司 路径处理方法、装置、终端、网络设备和存储介质
US20240056902A1 (en) * 2021-01-08 2024-02-15 Lenovo (Beijing) Limited Methods and apparatuses for handling a mbs at a ran node
EP4277348A4 (en) * 2021-01-14 2024-03-20 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND APPARATUS
CN114765816B (zh) * 2021-01-14 2024-05-17 大唐移动通信设备有限公司 小区重选方法、装置、网络设备、终端设备、介质及产品
US20240098761A1 (en) * 2021-01-14 2024-03-21 Lenovo (Beijing) Limited Mechanism for multicast and broadcast service
CN112954617B (zh) * 2021-02-10 2023-05-02 腾讯科技（深圳）有限公司 用于实现多播广播业务切换的方法及相关设备
CN114915917B (zh) * 2021-02-10 2024-06-28 华为技术有限公司 传输多播业务的方法及装置
CN112954614B (zh) * 2021-02-10 2023-05-12 腾讯科技（深圳）有限公司 用于实现多播广播业务切换的方法及相关设备
CN115038049B (zh) * 2021-03-05 2024-01-23 维沃移动通信有限公司 多播业务的接收方法、配置方法、终端及网络侧设备
CN115038048B (zh) * 2021-03-05 2023-07-07 维沃移动通信有限公司 多播业务的接收方法、配置方法、终端及网络侧设备
WO2022194272A1 (en) * 2021-03-18 2022-09-22 FG Innovation Company Limited User equipment and method for mbs service management
WO2022198451A1 (zh) * 2021-03-23 2022-09-29 北京小米移动软件有限公司 接收模式的确定方法、装置及通信设备
CN115134761A (zh) * 2021-03-29 2022-09-30 维沃移动通信有限公司 切换方法、装置、网络侧设备及终端
CN115150751A (zh) * 2021-03-30 2022-10-04 维沃移动通信有限公司 业务数据处理方法、装置及设备
CN115150045A (zh) * 2021-03-31 2022-10-04 展讯通信（上海）有限公司 无线通信方法与装置、终端和网络设备
CN117751615A (zh) * 2021-05-07 2024-03-22 中兴通讯股份有限公司 Mbs会话切换的方法和其***及装置
WO2022236592A1 (en) * 2021-05-10 2022-11-17 Nec Corporation Method, device and computer readable medium for communication
US20240154834A1 (en) * 2021-05-10 2024-05-09 Apple Inc. MRB Deactivation and Activation
CN117063495A (zh) * 2021-06-30 2023-11-14 Oppo广东移动通信有限公司 一种传输方式的确定方法及装置、终端设备、网络设备
WO2023283828A1 (en) * 2021-07-14 2023-01-19 Lenovo (Beijing) Limited Methods and apparatuses for handover
WO2023283942A1 (zh) * 2021-07-16 2023-01-19 Oppo广东移动通信有限公司 无线通信的方法、终端设备和网络设备
WO2023013607A1 (ja) * 2021-08-02 2023-02-09 京セラ株式会社 通信方法
CN115996359A (zh) * 2021-10-19 2023-04-21 夏普株式会社 进行小区切换的方法及用户设备
CN116017583A (zh) * 2021-10-21 2023-04-25 华为技术有限公司 业务优先级确定方法以及相关装置
CN116017555A (zh) * 2021-10-21 2023-04-25 大唐移动通信设备有限公司 报告发送方法、终端、基站、装置、和存储介质
WO2023197149A1 (en) * 2022-04-12 2023-10-19 Apple Inc. Broadcast mbs reception in connected state
CN117082578A (zh) * 2022-05-09 2023-11-17 大唐移动通信设备有限公司 广播会话接收方法、配置方法、装置、终端及网络侧设备
WO2024000206A1 (zh) * 2022-06-28 2024-01-04 北京小米移动软件有限公司 一种mbs接收状态信息的发送/接收方法及其装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102291688A (zh) * 2011-09-23 2011-12-21 电信科学技术研究院 一种基于mbms业务的切换方法和设备
US20130003577A1 (en) * 2011-07-01 2013-01-03 Maruti Gupta Communication state transitioning control
WO2015109475A1 (zh) * 2014-01-23 2015-07-30 华为技术有限公司 一种集群通信方法、基站、用户设备及***
CN106341848A (zh) * 2015-07-07 2017-01-18 电信科学技术研究院 一种切换方法及装置
CN107005820A (zh) * 2015-01-08 2017-08-01 株式会社Kt 用于发送和接收单小区多传输数据的方法及其装置
CN111866975A (zh) * 2020-05-18 2020-10-30 中兴通讯股份有限公司 切换方法及装置、信息发送方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20120123914A (ko) * 2011-05-02 2012-11-12 주식회사 팬택 Ｍｂｍｓ 서비스의 연속성을 위한 제어정보의 전송장치 및 방법
WO2018012810A1 (ko) * 2016-07-11 2018-01-18 엘지전자 주식회사 단말이 mbms 관심 지시 메시지를 전송하는 방법 및 이를 지원하는 장치
US20180139665A1 (en) * 2016-11-17 2018-05-17 Ofinno Technologies, Llc Handover of user equipment with multimedia broadcast multicast services

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130003577A1 (en) * 2011-07-01 2013-01-03 Maruti Gupta Communication state transitioning control
CN102291688A (zh) * 2011-09-23 2011-12-21 电信科学技术研究院 一种基于mbms业务的切换方法和设备
WO2015109475A1 (zh) * 2014-01-23 2015-07-30 华为技术有限公司 一种集群通信方法、基站、用户设备及***
CN107005820A (zh) * 2015-01-08 2017-08-01 株式会社Kt 用于发送和接收单小区多传输数据的方法及其装置
CN106341848A (zh) * 2015-07-07 2017-01-18 电信科学技术研究院 一种切换方法及装置
CN111866975A (zh) * 2020-05-18 2020-10-30 中兴通讯股份有限公司 切换方法及装置、信息发送方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4156727A4 *

Also Published As

Publication number Publication date
EP4156727A4 (en) 2024-02-14
US20230199569A1 (en) 2023-06-22
CN111866975A (zh) 2020-10-30
EP4156727A1 (en) 2023-03-29
KR20230011340A (ko) 2023-01-20

Similar Documents

Publication Publication Date Title
WO2021233279A1 (zh) 切换方法及装置、信息发送方法及装置
CN104871570B (zh) 基于lte增强型多媒体广播多播业务的群组通信的业务连续性方法以及用户设备
WO2017118199A1 (zh) 一种数据调度方法、基站及***
US20050041681A1 (en) Method and apparatus for transmitting and receiving MBMS packet data and control information
CN106162565B (zh) 传输组通信业务数据的方法、***及装置
WO2017131690A1 (en) Dynamic switching of streaming service between broadcast and unicast delivery
CN108781479B (zh) 多播传输方法、基站和用户设备
US20230371098A1 (en) Communication method, apparatus, and system
KR20230004776A (ko) 브로드캐스트/멀티캐스트 서비스 관리 방법, 장치, 전자 설비, 저장 매체
WO2017201725A1 (zh) 一种小区切换方法，终端以及核心网设备
KR101910459B1 (ko) 이동통신시스템에서 멀티캐스트 서비스 제공을 위한 방법 및 장치
WO2023029590A1 (zh) 一种组播/广播会话管理方法及通信装置
US20230300681A1 (en) Handover method, processing method, devices, network device and core network device
WO2020078288A1 (zh) 一种直接通信的方法和设备
JP7508634B2 (ja) 通信制御方法、基地局、ユーザ装置及びプロセッサ
WO2024140299A1 (zh) 通信方法及装置
US20230199439A1 (en) Multicast and broadcast service session reception mode switching in wireless communication networks
US20240057217A1 (en) Request to join mbs session during establishment procedure
US20240057194A1 (en) Pdu session status ie handling for mbs
EP4240030A1 (en) Communication method and apparatus
CN116939510A (zh) 多播广播服务兴趣指示消息传输方法及相关装置
AU2004301058B2 (en) Method and apparatus for transmitting and receiving MBMS packet data and control information

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20227043470

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021809000

Country of ref document: EP

Effective date: 20221219