Switching method and device, information sending method and device

Abstract

The present invention provides a switching method and device, and an information sending method and device, wherein the switching method comprises: sending a switching request to a second network device; wherein the switching request carries broadcast multicast service MBS session / bearer information; receiving a switching request response sent by the second network device, wherein the switching 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, and bearer configuration information of the second network device. Through the present invention, the problem of how to implement the switching process across base stations in the related art is solved, so as to achieve the effect of effectively ensuring the continuity of broadcast / multicast services during the switching process across stations.

Description

Technical Field

[0001] The present invention relates to the field of communications, and in particular to a switching method and device, and an information sending method and device. Background Art

[0002] With the increasing demand for video services brought about by the continuous increase in the number of mobile terminal users, as well as the rapid development of digital TV technology and network communication technology, wireless broadcast services have become a hot topic in the field of wireless applications. Among them, Multicast Broadcast Service (MBS) technology, as an important implementation method of mobile TV, will play an important role in the 5G system and has great development prospects.

[0003] Evolved Multicast Broadcast Multimedia Service (eMBMS) 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, namely point to multipoint transmission (PTM, i.e. broadcast / multicast), and provide rich video, audio and multimedia services. Therefore, further developing eMBMS in the 5G system can enhance the capabilities of the entire broadcast system, thereby supporting faster and more efficient 5G broadcast application scenarios, such as 4K / 8K ultra-high-definition video, three-dimensional stereoscopic video, virtual reality (VR) / augmented reality (AR) and other high-quality multimedia services.

[0004] At present, there is no clear solution in the relevant technology on how to reasonably and effectively implement broadcast / multicast services under 5G-NR technology, especially for the mobility of connected UEs and the continuity of broadcast / multicast services during the switching process of network equipment providing services.

[0005] Regarding the problem of how to implement the switching process across base stations in the above-mentioned related technologies, no effective solution has been proposed in the related technologies. Summary of the invention

[0006] The embodiments of the present invention provide a switching method and device, and an information sending method and device, so as to at least solve the problem of how to implement a switching process across base stations in the related art.

[0007] According to an embodiment of the present invention, a switching method is provided, which is applied to a first network device, and the method includes:

[0008] Sending a handover request to the second network device; wherein the handover request carries broadcast multicast service MBS session / bearer information;

[0009] Receive a handover request response sent by the second network device, where the handover request response includes at least one of the following:

[0010] MBS session / bearer information that can be accommodated by the second network device, MBS session / bearer information that cannot be accommodated by the second network device, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.

[0011] According to another embodiment of the present invention, there is also provided an information sending method, which is applied to a UE, and the method includes:

[0012] Sending MBS indication information that the UE is interested in and MBS indication information that the UE is receiving to the first network device;

[0013] Receive RRC reconfiguration information returned by the first network device according to the MBS indication information of interest to the UE.

[0014] According to another embodiment of the present invention, a switching method is further provided, which is applied to a second network device, and the method includes:

[0015] receiving 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 an MBS bearer;

[0016] 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 can be accommodated by the second network device, MBS session / bearer information that cannot be accommodated by the second network device, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.

[0017] According to another embodiment of the present invention, there is further provided a switching device, which is arranged in a first network device, and the device comprises:

[0018] A first sending module, configured to send a switching request to a second network device; wherein the switching request carries broadcast multicast service MBS session / bearer information;

[0019] The first receiving module is configured to receive a handover request response sent by the second network device, wherein the handover request response includes at least one of the following:

[0020] MBS session / bearer information that can be accommodated by the second network device, MBS session / bearer information that cannot be accommodated by the second network device, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.

[0021] According to another embodiment of the present invention, there is also provided an information sending device, which is arranged in a UE, and the device includes:

[0022] A second sending module, configured to send MBS indication information of interest to the UE and MBS indication information being received by the UE to the first network device;

[0023] The second receiving module is used to receive the RRC reconfiguration information returned by the first network device according to the MBS indication information of interest to the UE.

[0024] According to another embodiment of the present invention, there is further provided a switching device, which is arranged in a second network device, and the device comprises:

[0025] A 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 an MBS bearer;

[0026] A return module is used 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 can be accommodated by the second network device, MBS session / bearer information that cannot be accommodated by the second network device, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.

[0027] According to another embodiment of the present invention, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0028] According to another embodiment of the present invention, there is further provided an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0029] Through the switching method and device, and the information sending method and device in the embodiments of the present invention, the first network device can send a switching request to the second network device; wherein the switching 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; and the first network device receives a switching request response sent by the second network device, and the switching request response includes at least one of the following: MBS session / bearer information that can be accepted by the second network device, MBS session / bearer information that cannot be accepted by the second network device, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device. Therefore, through the switching method and device, and the information sending method and device in the embodiments of the present invention, the problem of how to implement the switching process across base stations in the related technology can be solved, so as to achieve the effect of effectively ensuring the continuity of broadcast / multicast services during the switching process across stations. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0031] Figure 1 is a schematic diagram of the architecture of a wireless network system provided according to an embodiment of the present invention;

[0032] Figure 2 is a hardware structure block diagram of a mobile terminal provided according to an embodiment of the present invention;

[0033] Figure 3 is a flow chart of a switching method provided according to an embodiment of the present invention (I);

[0034] Figure 4 is a flow chart of an information sending method provided according to an embodiment of the present invention;

[0035] Figure 5 is a flow chart of a switching method provided according to an embodiment of the present invention (II);

[0036] Figure 6 is an interactive flow chart (I) of establishing an MBS session according to an exemplary embodiment of the present invention;

[0037] Figure 7 is an interactive flow chart (II) of establishing an MBS session according to an exemplary embodiment of the present invention;

[0038] Figure 8 is an interactive flow chart (I) of UE interest reporting provided according to an exemplary embodiment of the present invention;

[0039] Fig. 9is an interactive flow chart (II) of UE interest reporting provided according to an exemplary embodiment of the present invention;

[0040] Fig.10 is an interactive flow chart of a switching method provided according to an exemplary embodiment of the present invention;

[0041] Fig.11 is a structural block diagram of a switching device provided according to an embodiment of the present invention (I);

[0042] Fig.12 is a structural block diagram of an information sending device provided according to an embodiment of the present invention;

[0043] Fig.13 2 is a structural block diagram of a switching device provided according to an embodiment of the present invention. DETAILED DESCRIPTION

[0044] The present invention will be described in detail below with reference to the accompanying drawings and in combination with embodiments. It should be noted that the embodiments and features in the embodiments of the present application can be combined with each other without conflict.

[0045] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0046] To further illustrate the working modes of the switching method and device, and the information sending method and device in the embodiments of the present invention, the application scenarios of the switching method and device, and the information sending method and device in the embodiments of the present invention are described below:

[0047] 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 (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LIE-A (Advanced long term evolution) system, Universal Mobile Telecommunication System (UMTS), and fifth generation wireless systems (5G) system, etc., and the embodiments of the present invention are not limited to this. In the embodiments of the present invention, the 5G system is used as an example for explanation.

[0048] The embodiment of the present invention can be used in wireless networks of different standards. A wireless access network may include different communication nodes in different systems. Figure 1 is a schematic diagram of the architecture of a wireless network system provided according to an embodiment of the present invention. Figure 1 As shown, the wireless network system under the network architecture includes base station 101, base station 102, terminal 110, terminal 120, and terminal 130; base station 101 and base station 102 can be base stations of adjacent cells, base station 101 and base station 102 can respectively perform wireless communication with terminal 110, terminal 120, and terminal 130, and terminal 110, terminal 120, and terminal 130 can switch between base station 101 and base station 102.

[0049] In the embodiment of the present invention, the network device may be a device that can communicate with a user terminal. The network device may be any device with wireless transceiver functions, including but not limited to: a base station NodeB, an evolved base station eNodeB, a base station in a 5G communication system, a base station in a future communication system, an access node in a WiFi system, a wireless relay node, a wireless backhaul node, etc. The network device may also be a wireless controller in a cloud radio access network (cloud base station) scenario; the network device may also be a small station, a transmission reference point (TRP), etc., which is not limited in the embodiment of the present invention.

[0050] In the embodiment of the present invention, the terminal is a device with wireless transceiver function and can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.). The user terminal can be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiment of the present invention does not limit the above specific application scenarios or application objects. The terminal may sometimes also be referred to as 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., which is not limited in the embodiments of the present invention.

[0051] Take the above terminal as a mobile terminal (such as a mobile phone) as an example for explanation. Figure 2 is a hardware structure block diagram of a mobile terminal provided according to an embodiment of the present invention. Figure 2 As shown, the mobile terminal may include one or more ( Figure 2 Only one is shown in the figure) a processor 202 (the processor 202 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 204 for storing data. Optionally, the mobile terminal may also include a transmission device 206 and an input / output device 208 for communication functions. It can be understood by those skilled in the art that Figure 2 The structure shown is only for illustration and does not limit the structure of the mobile terminal. Figure 2 More or fewer components as shown, or with Figure 2 Different configurations are shown.

[0052] The memory 204 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the information sending method in the embodiment of the present invention. The processor 202 executes various functional applications and data processing by running the computer program stored in the memory 204, that is, to implement the above method. 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. In some examples, the memory 204 may further include a memory remotely arranged relative to the processor 202, and these remote memories may be connected to the mobile terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0053] The transmission device 206 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the mobile terminal. In one example, 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. In one example, the transmission device 206 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0054] The embodiment of the present invention involves information interaction between three entities: a terminal, a first network device, and a second network device, and mainly involves signaling transmission of Uu port and Xn port; wherein the first network device is a source network device, for example, a source base station, and the second network device is a target network device in a switching process, for example, a target base station, and the second network device can specifically be a network device of a cell adjacent to the first network device; the terminal in the embodiment of the present invention is a terminal in a connected state. The above-mentioned terminal, the first network device, and the second network device can correspond to the above-mentioned Figure 1 The terminal 110, the base station 101 and the base station 102 in the network architecture shown.

[0055] The following describes the working modes of the switching method and device, and the information sending method and device in the embodiments of the present invention:

[0056] Example 1

[0057] An embodiment of the present invention provides a switching method, which is applied to a first network device. Figure 3 is a flow chart (I) of a switching method provided according to an embodiment of the present invention, such as Figure 3 As shown, the switching method in this embodiment includes:

[0058] S102, the first network device sends a handover request to the second network device; wherein the handover request carries broadcast multicast service MBS session / bearer information;

[0059] S104, the first network device receives a switching request response sent by the second network device, where the switching request response includes at least one of the following: MBS session / bearer information that can be accommodated by the second network device, MBS session / bearer information that cannot be accommodated by the second network device, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.

[0060] It should be further explained that, in the above-mentioned 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.

[0061] It should be further explained that, the UE scheduling configuration information of the second network device and the bearer configuration information of the second network device included in the above-mentioned handover request response can be further sent to the UE in a transparent transmission manner by the first network device.

[0062] Through the switching method in this embodiment, since the first network device can send a switching request to the second network device; wherein the switching 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; and the first network device receives a switching request response sent by the second network device, the switching request response includes at least one of the following: MBS session / bearer information that can be accepted by the second network device, MBS session / bearer information that cannot be accepted by the second network device, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device. Therefore, through the switching method and device, and the information sending method and device in the embodiment of the present invention, the problem of how to implement the switching process across base stations in the related technology can be solved, so as to achieve the effect of effectively ensuring the continuity of broadcast / multicast services during the switching process across stations.

[0063] Specifically, through the switching method in the embodiment of the present invention, a specific method for executing the switching process across gNBs can be established in the 5G NR scenario, and during the switching process, the mobility of the connected UE and the continuity of the broadcast / multicast service can be guaranteed.

[0064] It should be further explained that, in the above embodiment, optionally, the MBS session information is also used to indicate the MBS service corresponding to the MBS session; the MBS session and the MBS service are one-to-one corresponding, so the MBS session indicated by the MBS session information can correspond to the corresponding MBS service.

[0065] Optionally, the MBS session / bearer information includes at least one of the following:

[0066] MBS session information that the terminal is interested in, MBS session / bearer information currently received by the terminal, and terminal capability information.

[0067] Optionally, the MBS session information of interest to the terminal includes at least one of the following:

[0068] The identification information of the MBS session that the terminal is interested in, the MBS area identification, the reception priority information, and the MBS session reception mode information expected by the terminal.

[0069] Optionally, the receiving priority information includes at least one of the following:

[0070] Prioritize unicast reception, prioritize broadcast / multicast reception, and prioritize the level of receiving MBS sessions.

[0071] Optionally, the MBS session / bearer information currently received by the terminal includes at least one of the following:

[0072] Identification information of the MBS session / bearer currently received by the terminal, reception mode information of the MBS session / bearer currently received by the terminal, radio bearer configuration information of the MBS bearer currently received by the terminal, and quality of service QoS configuration information of the MBS session / bearer currently received by the terminal.

[0073] Optionally, 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 PTP and PTM simultaneous reception;

[0074] The reception mode information of the MBS session / bearer currently received by the terminal includes at least one of the following: PTP reception, PTM reception, and PTP and PTM simultaneous reception.

[0075] Optionally, 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.

[0076] Optionally, the radio bearer configuration information includes: PTP bearer configuration information, and / or, PTM bearer configuration information;

[0077] 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:

[0078] 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;

[0079] The PTM bearer configuration information is used to configure the PTM bearer. The PTM bearer configuration information includes at least one of the following:

[0080] PTM radio bearer identifier, logical channel identifier, SDAP configuration information, PDCP configuration information, RLC bearer configuration information.

[0081] Optionally, 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;

[0082] Optionally, the acceptable MBS session / bearer information indicated in the handover request response includes at least one of the following:

[0083] The second network device can accept MBS session / bearer identifiers, broadcast / multicast service session reception modes, and acceptable service session / bearer QoS configuration information.

[0084] Optionally, the MBS session / bearer information that cannot be accommodated indicated in the handover request response includes at least one of the following:

[0085] The MBS session / bearer identifier that cannot be accepted by the second network device, and the reason why the second network device cannot accept the MBS session / bearer corresponding to the MBS session / bearer identifier.

[0086] Optionally, the bearer configuration information of the second network device includes at least one of the following:

[0087] PTM radio bearer identifier, logical channel identifier, SDAP configuration information, PDCP configuration information, RLC bearer configuration information.

[0088] Optionally, the UE scheduling configuration information of the second network device indicated in the handover request response includes at least one of the following:

[0089] Scheduling information of multicast service channels, and physical layer parameters required for configuring multicast service channels.

[0090] Optionally, 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.

[0091] Optionally, sending a switching request to the second network device includes:

[0092] A switching request is sent to an access and mobility management function (AMF), and the switching request is forwarded to the second network device through the AMF; wherein the switching request received by the second network device carries MBS session bearer information.

[0093] It should be further explained that the above-mentioned AMF can instruct the access mobility management function or gateway in the core network.

[0094] Optionally, before sending the switching request to the second network device, the method further includes:

[0095] The measurement results of the broadcast / multicast service frequencies sent by the receiving terminal.

[0096] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0097] Example 2

[0098] The embodiment of the present invention provides an information sending method, which is applied to UE. Figure 4 is a flow chart of a method for sending information according to an embodiment of the present invention. Figure 4 As shown, the information sending method in this embodiment includes:

[0099] S202, the UE sends MBS indication information in which the UE is interested and MBS indication information being received by the UE to the first network device;

[0100] S204: The UE receives RRC reconfiguration information returned by the first network device according to the MBS indication information in which the UE is interested.

[0101] Optionally, the MBS indication information of interest to the UE further includes:

[0102] Service identification information of the MBS that the UE is interested in;

[0103] The MBS service identification information further includes at least one of the following: an MBS service / session identification, a temporary mobile group identification TMGI of the MBS, an MBS identification, and a PDU session identification indicating an MBS session.

[0104] Optionally, the MBS indication information of interest to the UE further includes:

[0105] The reception mode of the MBS that the UE is interested in;

[0106] The receiving mode includes at least one of the following: unicast receiving, broadcast / multicast receiving, and unicast and multicast receiving simultaneously.

[0107] Optionally, the MBS indication information of interest to the UE further includes:

[0108] The service area of ​​the MBS that the UE is interested in.

[0109] Optionally, the RRC reconfiguration information includes:

[0110] Target cell identifier, acceptable MBS list, acceptable MBS configuration information, acceptable MBS reception mode information.

[0111] Optionally, the configuration information of the acceptable MBS includes at least one of the following:

[0112] PTM radio bearer identifier, logical channel identifier, SDAP configuration information, PDCP configuration information, RLC bearer configuration information.

[0113] Optionally, the configuration information of the acceptable MBS includes at least one of the following:

[0114] Scheduling information of multicast service channels, and physical layer parameters required for configuring multicast service channels.

[0115] Optionally, the acceptable MBS reception mode information includes at least one of the following:

[0116] Unicast reception, broadcast / multicast reception, and simultaneous unicast and multicast reception.

[0117] Optionally, after receiving the RRC reconfiguration information returned by the first network device according to the MBS indication information, the method further includes:

[0118] The resources of the first network device are released, and the PDCP and RLC are rebuilt and the MAC is reset according to the radio bearer configuration information from the second network device, thereby establishing a PTM bearer and receiving services based on the PTM bearer.

[0119] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0120] Example 3

[0121] An embodiment of the present invention provides a switching method, which is applied to a second network device. Figure 5 is a flow chart (II) of a switching method provided according to an embodiment of the present invention, such as Figure 5 As shown, the switching method in this embodiment includes:

[0122] S302, the second network device receives 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 the MBS session, and the MBS bearer information is used to indicate the MBS bearer;

[0123] S304, the second network device returns 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 can be accommodated by the second network device, MBS session / bearer information that cannot be accommodated by the second network device, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.

[0124] It should be further explained that the remaining optional embodiments and technical effects of the switching method in this embodiment correspond to the switching method in Example 1, so they are not repeated here.

[0125] Optionally, the MBS session / bearer information includes at least one of the following:

[0126] MBS session information that the terminal is interested in, MBS session / bearer information currently received by the terminal, and terminal capability information.

[0127] Optionally, the MBS session information of interest to the terminal includes at least one of the following:

[0128] The identification information of the MBS session that the terminal is interested in, the MBS area identification, the reception priority information, and the MBS session reception mode information expected by the terminal.

[0129] Optionally, the receiving priority information includes at least one of the following:

[0130] Prioritize unicast reception, prioritize broadcast / multicast reception, and prioritize the level of receiving MBS sessions.

[0131] Optionally, the MBS session / bearer information currently received by the terminal includes at least one of the following:

[0132] Identification information of the MBS session / bearer currently received by the terminal, reception mode information of the MBS session / bearer currently received by the terminal, radio bearer configuration information of the MBS bearer currently received by the terminal, and quality of service QoS configuration information of the MBS session / bearer currently received by the terminal.

[0133] Optionally, 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 PTP and PTM simultaneous reception;

[0134] The reception mode information of the MBS session / bearer currently received by the terminal includes at least one of the following: PTP reception, PTM reception, and PTP and PTM simultaneous reception.

[0135] Optionally, 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.

[0136] Optionally, the radio bearer configuration information includes: PTP bearer configuration information, and / or, PTM bearer configuration information;

[0137] 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:

[0138] 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;

[0139] The PTM bearer configuration information is used to configure the PTM bearer. The PTM bearer configuration information includes at least one of the following:

[0140] PTM radio bearer identifier, logical channel identifier, SDAP configuration information, PDCP configuration information, RLC bearer configuration information.

[0141] Optionally, 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;

[0142] Optionally, the acceptable MBS session / bearer information indicated in the handover request response includes at least one of the following:

[0143] The second network device can accept MBS session / bearer identifiers, broadcast / multicast service session reception modes, and acceptable service session / bearer QoS configuration information.

[0144] Optionally, the MBS session / bearer information that cannot be accommodated indicated in the handover request response includes at least one of the following:

[0145] The MBS session / bearer identifier that cannot be accepted by the second network device, and the reason why the second network device cannot accept the MBS session / bearer corresponding to the MBS session / bearer identifier.

[0146] Optionally, the bearer configuration information of the second network device includes at least one of the following:

[0147] PTM radio bearer identifier, logical channel identifier, SDAP configuration information, PDCP configuration information, RLC bearer configuration information.

[0148] Optionally, the UE scheduling configuration information of the second network device indicated in the handover request response includes at least one of the following:

[0149] Scheduling information of multicast service channels, and physical layer parameters required for configuring multicast service channels.

[0150] Optionally, 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.

[0151] Optionally, sending a switching request to the second network device includes:

[0152] A switching request is sent to the access mobility management function AMF, and the switching request is forwarded to the second network device through the AMF; wherein the switching request received by the second network device carries the MBS session bearer information.

[0153] Optionally, the MBS session information is further used to indicate an MBS service corresponding to the MBS session;

[0154] Among them, the MBS session corresponds to the MBS service one by one.

[0155] To further illustrate the switching method and information sending method described in the above-mentioned embodiments 1 to 3, the interaction process between the terminal, the first network device and the second network device indicated by the above-mentioned switching method and information sending method is further described below through exemplary embodiments.

[0156] Example 1

[0157] This example embodiment describes the process of establishing an MBS session in the embodiment of the present invention. Specifically, 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 ConfigurationUpdate process, OAM; it should be further explained that the source base station in this example embodiment is equivalent to the source network device in the embodiment of the present invention, and the neighboring cell base station in this example embodiment is equivalent to the target network device in the embodiment of the present invention. The above three establishment methods are explained below through three examples.

[0158] Example 1: Xn Setup process

[0159] Figure 6 is an interactive flow chart (I) of establishing an MBS session according to an exemplary embodiment of the present invention, such as Figure 6 As shown, the process of establishing an MBS session based on the Xn Setup process in this example is as follows:

[0160] S1, the source gNB sends an Xn establishment request message to the neighboring gNB, which carries the IE for obtaining neighboring MBS service information, and is used to request the neighboring gNB to respond with which MBS services are available in each cell and the cell identifier (the cell identifier is unique within the network, such as NR CGI).

[0161] S2, the neighboring cell base station receives the Xn setup request message from the source base station, which 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 ID through the Xn setup response message.

[0162] S3, after receiving the Xn establishment response message carrying the MBS service information of the neighboring cell and the cell identifier to which it belongs, the source base station will notify the UE through the SIB message or the dedicated RRC message.

[0163] S4, after the UE receives the MBS service information of the neighboring cells and the cell identifiers thereof from the source base station, it triggers the reporting of the MBS interest indication information of the UE.

[0164] Example 2: gNB Configuration Update process

[0165] Figure 7 is an interactive flow chart (II) of establishing an MBS session according to an exemplary embodiment of the present invention, such as Figure 7As shown, the process of establishing an MBS session based on the gNB Configuration Update process in this example is as follows:

[0166] S1: The source gNB sends a gNBConfiguration Update message to the neighboring gNB, which carries an IE for obtaining neighboring MBS service information. This message is used to request the neighboring gNB to respond with information about the MBS services in each cell and the cell ID (the cell ID is unique within the network, such as NR CGI).

[0167] S2: The neighboring cell base station receives the gNB Configuration Update message from the source base station, which 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 ID through the gNB Configuration Update ACK.

[0168] S3, after receiving the Xn establishment response message carrying the MBS service information of the neighboring cell and the cell identifier to which it belongs, the source base station will notify the UE through a SIB message or a dedicated RRC message.

[0169] S4, after the UE receives the MBS service information of the neighboring cells and the cell identifiers thereof from the source base station, it triggers the reporting of the MBS interest indication information of the UE.

[0170] Example 3: OAM

[0171] In this example, the MBS services owned by the neighboring cells and the cells to which they belong can be pre-configured for 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.

[0172] Example 2

[0173] This exemplary embodiment describes a process of switching between a source base station and a target base station by a UE under the premise that an MBS session is established between the UE and the source base station in exemplary embodiment 1. The process of switching between the source base station and the target base station by the UE is as follows:

[0174] First, the UE obtains user service information directly from the service / application layer.

[0175] The above steps are used for UE to report interest. Figure 8 is an interactive flow chart (I) of UE interest reporting provided according to an exemplary embodiment of the present invention. The process of UE interest reporting in the above steps is as follows Figure 8 shown.

[0176] Specifically, 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 information, MBS service area identifier, MBS service identifier, start and end time of the service, etc. After receiving the service-related information, the UE will report the MBS services that it is interested in receiving and is receiving based on the services available at the application / service layer and its own interests, to assist the source gNB in ​​selecting the target cell that can support the UE being received or interested in receiving as much as possible.

[0177] It should be noted that the services in the MBS interest indication information message reported by the UE are completely based on the UE's own interests.

[0178] In the technical solution recorded in the above steps, the UE's reporting of interest in the service is an autonomous behavior and is not limited by whether there are services of interest in the neighboring cells. When the gNB selects a target cell for the UE to switch, it tries to select a cell that can support the transmission of the MBS that the UE is receiving or interested in receiving. If a target cell cannot be found that can meet all the MBS services that the UE is receiving or interested in receiving, the cell that supports high-priority or receiving MBS services is given priority. Therefore, the above steps have better service flexibility. At the same time, updates or changes to service-related information at the application / service layer will be notified to the UE, which will then trigger the UE to report the services of interest.

[0179] In this exemplary embodiment, the UE can not only obtain the available MBS services and MBS service related information from the application / service layer, Fig. 9 is an interactive flow chart (II) of UE interest reporting according to an exemplary embodiment of the present invention. The process of UE interest reporting can also be as follows Fig. 9 As shown, the UE can also obtain which MBS services are provided by the current cell and the service area to which each service belongs, and which MBS services are provided by the neighboring cell and to which MBS service area each service belongs by reading the SIB message.

[0180] One of the purposes of the above-mentioned UE interest reporting is to serve the continuity of the service. Specifically, for a connected UE, the handover is a network-controlled handover, that is, switching the UE to a suitable target cell. In order to ensure the continuity of the MBS service, the serving cell needs to know the MBS service that the UE is receiving or interested in receiving, so that it is possible to switch the UE to the cell of interest. At the same time, 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 from the MBS interest indication information, it will try to avoid scheduling the broadcast and multicast transmission and unicast transmission of interest to the UE in the same time slot according to the UE's capabilities during scheduling.

[0181] To achieve the above technical objectives, Figure 8 or Fig. 9 As shown, in this exemplary embodiment, the UE needs to send MBS interest indication information to the source gNB, and the MBS interest indication information is used to tell the base station the broadcast multicast service that the UE is receiving or interested in receiving. The MBS interest indication information in this exemplary embodiment specifically includes the following information:

[0182] MBS service identifier list: a list of MBS services that the UE is receiving or interested in receiving. Each broadcast multicast service is marked with a service identifier. The MBS service list is sorted according to the UE's interest priority in the MBS services that it is receiving or interested in receiving. That is, the UE's interest in the broadcast multicast services before the sorting in the table is higher than that in the sorted broadcast multicast services.

[0183] MBS reception priority: indicates whether the UE has priority over unicast to receive MBS services. If the received information is "true", the UE has priority over unicast to receive MBS services in the target cell. This information may be used in case of network congestion. When the target base station receives this information, it may release the unicast bearer and give priority to receiving broadcast multicast transmission.

[0184] Optionally, the above-mentioned MBS interest indication information may further include:

[0185] Cast mode: which mode the UE expects to use to receive the corresponding MBS service data; specifically, the optional receiving modes include: which receiving mode the UE expects to use for the MBS service that it is receiving or interested in receiving as reported by the UE in the MBS interest indication message.

[0186] It should be noted that the MBS services reported by the UE that the UE is receiving or interested in receiving, that is, the list of MBS service identifiers in the MBS interest indication information, comes from: 1) the available MBS services notified by the application / service layer, and the related information of the MBS services; It should be noted that the available MBS services notified by the above-mentioned application / service layer, and the related information of the MBS services may or may not be available on the air interface, such as the broadcast multicast services reported by the MBS are not available on the air interface (which will trigger the UE to request the core network to establish the service); 2) informing the source base station through the Xn interface which MBS services are available in the neighboring cells, and then informing the UE through the SIB message or the proprietary RRC message, based on the MBS services available in the neighboring cells, the UE will report the MBS services it is interested in or receiving, and this service must be available on the air interface.

[0187] The MBS services reported by the UE that it is receiving or interested in receiving are reported in the order of the UE's interest priority in the MBS services. The MBS reception priority can be specifically used for, when the network is congested, the base station can decide to release the unicast bearer and give priority to receiving broadcast and multicast transmission data.

[0188] Furthermore, for a UE that is currently receiving MBS or is interested in MBS, the source gNB can configure the UE to measure the MBS frequency that the UE is interested in receiving. The UE measures the corresponding frequency and reports the measurement results. If the source gNB finds that the measurement results reported by the UE include 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.

[0189] When the gNB selects a target cell for the UE to switch to, it tries to select a cell that supports the MBS service that the UE is currently receiving or interested in. Even if a target cell cannot be found that satisfies the MBS service that the UE is currently receiving or interested in, the gNB will prioritize the cell that supports the MBS service that is of high priority or is currently being received.

[0190] Furthermore, after the source gNB selects a target cell for the UE, the source base station may send a handover request message to the target base station. To achieve continuity of the MBS service, the handover request message may include at least one of the following information:

[0191] 1) The UE's MBS interest indication information is used to assist the source base station in selecting a target cell and in the flexible scheduling of the target base station.

[0192] Specifically, the MBS interest indication information of the UE may include: 1.1) MBS service list; 1.2) MBS reception priority. Optionally, the handover request message may also include a reception mode that the UE expects to adopt for the service of interest.

[0193] The above-mentioned MBS interest indication information can assist the source base station in selecting 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 flexible scheduling after the target base station knows which MBS services the UE is interested in, avoiding scheduling the same MBS service at the same time in the same time slot.

[0194] 2) MBS service information currently received by the UE, such as MBS session identification information corresponding to the received MBS service, and MBS session bearer configuration information, such as PTM bearer configuration information and / or PTP bearer configuration information.

[0195] Specifically, the above-mentioned 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, a temporary mobile group identification TMGI of a broadcast multicast service, a broadcast multicast service identification, a PDU session identification indicating the MBS session, and an IP multicast address; 2.2) Radio bearer configuration information, which configures the radio bearer of the MBS session. Indicates the MBS session bearer configuration information currently received by the UE, and the radio bearer configuration information may further include: PTP bearer configuration information and / or PTM bearer configuration information. The PTP bearer configuration information specifically includes: PTP radio bearer identification, service data adaptation protocol SDAP configuration, packet data convergence protocol PDCP protocol, and radio link control RLC configuration; the PTM configuration information includes: PTM radio bearer identification, SDAP configuration, PDCP configuration, and RLC configuration. Optionally, the air interface resource configuration includes, for example, 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.

[0196] Through the above wireless bearer configuration information, if the MBS service received by the UE in the target cell is the same as the MBS service received in the source cell, the target base station can receive the MBS service by using the same set of bearer configuration information as the source base station, i.e., wireless bearer configuration, scheduling information of the multicast service channel and physical layer parameters for receiving the current MBS service. Another solution is that for the underlying configuration, such as the scheduling information of the multicast service channel and the physical layer parameters for receiving the current MBS service, which change in real time, the source base station may not send this part of information to the target base station, but the target base station may configure it and then notify the UE.

[0197] Optionally, the MBS service information may further include: a receiving mode adopted by the MBS session currently received by the UE, which may include an MBS service identifier and a service area identifier corresponding to the MBS service.

[0198] 3) QoS configuration information of the QoS flows within the MBS session, such as a list of QoS flow identifiers within the session, and QoS parameters corresponding to the QoS flow level of each QoS flow identifier.

[0199] Specifically, 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 parameters of the QoS flow level, and MBS session identifier information.

[0200] 4) Indication information of whether the UE uses a PTP radio bearer or a PTM radio bearer when receiving MBS data corresponding to the current MBS service identifier.

[0201] 5) MBS receiving capability of the UE, indicating whether the terminal supports the ability to receive both unicast transmission and broadcast multicast transmission in the same time slot. The MBS receiving capability of the UE allows the target network device to take the terminal capability into consideration during scheduling, thereby avoiding conflicts between the scheduling result and the terminal capability.

[0202] Further, after receiving the handover request message, the target base station may 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:

[0203] 1) MBS session resources that are of interest to UEs that can be accommodated / supported and MBS session resources that are of interest to UEs that cannot be accommodated / supported;

[0204] Specifically, 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 an accepted list of MBS service resources and an unacceptable list of MBS service resources in the handover request response message.

[0205] 2) For each acceptable MBS session resource of interest to the UE, it includes an acceptable QoS flow list and an unacceptable QoS flow list, as well as the PTP / PTM receiving mode indication and PTP / PTM bearer configuration corresponding to the MBS session.

[0206] Specifically, the target base station may also provide the receiving mode adopted by the corresponding MBS session in the target base station in the handover request response message, such as PTP and / or PTM reception, and provide the corresponding radio bearer configurations under the two modes. In addition, the QoS configuration of the radio bearer of the corresponding reception mode may also be provided.

[0207] Optionally, 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.

[0208] In addition, for the MBS services that the UE is interested in or is receiving, the target base station may have established a corresponding MBS session with the MCE / AMF. For the above MBS services, the target base station only needs to consider configuring the PTP and / or PTM mode for the UE to receive MBS. For the target base station that can support MBS but has not established an MBS session with the MCE / AMF, the target base station can initiate an MBS session establishment request to the MCE / AMF.

[0209] Optionally, for each MBS session resource that the UE is interested in and cannot be accommodated, the handover request response message may also include an MBS session identifier and a reason for not accommodating the MBS session resource.

[0210] Optionally, the handover request response message may also include SIB information of the target cell and MBS control channel and service channel configuration information.

[0211] Furthermore, at the same time as / after returning the switching request response message to the source base station, the target base station may also send a switching command message to the UE. The switching command message includes an RRC reconfiguration message. The RRC reconfiguration message specifically includes: the receiving method used to receive the corresponding MBS session, and the RB configuration (DRB / MRB) of the corresponding receiving mode.

[0212] Specifically, for the PTM reception method, the target base station needs to indicate which MBS service resources need to be transmitted in PTM mode and the corresponding MRB configuration in the handover response / command message. For the PTP and PTM reception methods, the target base station needs to indicate in the handover response message that the MBS service resources are accepted in PTM and PTP modes, and provide the corresponding configuration in the RRC reconfiguration message.

[0213] Optionally, the switching command message further includes a QoS profile indication of supported MBS services.

[0214] Furthermore, after receiving the handover command message sent by the target base station, the UE may also return a confirmation message to the target base station to confirm that the RRC connection reconfiguration is completed.

[0215] The following specifically describes the process of implementing handover of the UE between the source base station and the target base station through an example:

[0216] Example 4:

[0217] Fig.10 is an interactive flow chart of a handover method according to an exemplary embodiment of the present invention. In this example, the process of implementing handover between a source base station and a target base station by a UE is as follows: Fig.10 As shown, the specific process of the above switching is as follows:

[0218] S1, UE obtains the available MBS services and the related information of each MBS service from the service / application layer, including: the MBS service identifier (e.g., TMGI, MBS service ID), the frequency information, the MBS service area, and the start and end time of the MBS service. In addition, the UE will read the system message to know the MBS services in the current cell and neighboring cells and the MBS service area to which each service belongs.

[0219] S2, after the UE receives the information about MBS services from the service / application layer, as well as the MBS services available in the neighboring cells, based on this information, the UE will report the MBS services it is receiving or interested in receiving to the source base station through an MBS interest indication message. The MBS services reported by the UE are reported in order of priority of the services it is interested in. In addition, in order to serve the continuity of MBS services and support flexible scheduling.

[0220] 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 is receiving, and the priority of MBS transmission relative to unicast reception. Optionally, the MBS interest indication information message also includes the reception mode of the currently received MBS service and the UE capability.

[0221] S3, the UE will measure the frequency points that the network configures for the UE to be interested in receiving, and report the measurement results to the source base station through a measurement report message. The base station will try to select a cell that can support the broadcast multicast service that the UE is receiving or is interested in receiving.

[0222] S4, the source base station sends a switching request message to the target base station through the Xn interface, the purpose of which is to request resources for switching and inform the target base station of the UE context on the source base station side; the switching request message may specifically include at least one of the following information: interest indication information reported by the UE, MBS service information currently received by the UE (for example, MBS session identification information corresponding to the received MBS service), the MBS session bearer configuration information (for example, PTM bearer configuration information and / or PTP bearer configuration information), QoS configuration information of the QoS flow within the MBS session (for example, a list of QoS flow identifiers within the session, QoS parameters corresponding to the QoS flow level of each QoS flow identifier), indication information of whether the UE uses a PTP wireless bearer or a PTM wireless bearer when receiving the MBS data corresponding to the current MBS service identifier, and the UE's MBS receiving capability information.

[0223] S5, 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 acceptable MBS session will also include an acceptable QoS flow list and an unacceptable QoS flow list, as well as the PTP / PTM receiving mode indication and PTP / PTM bearer configuration corresponding to the MBS session.

[0224] The unacceptable MBS session resources include the MBS session identifier and the reason for not accepting the MBS session resources.

[0225] Optionally, the handover response message may also include SIB information of the target cell, MBS control channel and MBS service channel configuration information.

[0226] S6, the target base station may include an RRC reconfiguration message in the handover command to be sent to the UE, which mainly includes: the reception mode through which the MBS service is received and the radio bearer configuration of the corresponding reception mode.

[0227] S7, the UE responds to the target base station with an RRC reconfiguration completion message, the purpose of which is to confirm that an RRC connection configuration has been successfully connected. In this way, the corresponding broadcast multicast service can be received through the target base station in a PTP and / or PTM receiving mode.

[0228] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0229] Example 4

[0230] The embodiment of the present invention provides a switching device, which is applied to a first network device, and the device is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0231] Fig.11 is a structural block diagram of a switching device provided according to an embodiment of the present invention (I), such as Fig.11 As shown, the switching device in this embodiment includes:

[0232] The first sending module 402 is configured to send a handover request to the second network device; wherein the handover request carries the broadcast multicast service MBS session / bearer information;

[0233] The first receiving module 404 is configured to receive a switching request response sent by the second network device, where the switching request response includes at least one of the following:

[0234] MBS session / bearer information that can be accepted by the second network device, MBS session / bearer information that cannot be accepted by the second network device, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.

[0235] It should be further explained that the remaining optional embodiments and technical effects of the switching device in this embodiment correspond to the switching method recorded in Example 1, so they are not repeated here.

[0236] Optionally, the MBS session / bearer information includes at least one of the following:

[0237] MBS session information that the terminal is interested in, MBS session / bearer information currently received by the terminal, and terminal capability information.

[0238] Optionally, the MBS session information of interest to the terminal includes at least one of the following:

[0239] The identification information of the MBS session that the terminal is interested in, the MBS area identification, the reception priority information, and the MBS session reception mode information expected by the terminal.

[0240] Optionally, the receiving priority information includes at least one of the following:

[0241] Prioritize unicast reception, prioritize broadcast / multicast reception, and prioritize the level of receiving MBS sessions.

[0242] Optionally, the MBS session / bearer information currently received by the terminal includes at least one of the following:

[0243] Identification information of the MBS session / bearer currently received by the terminal, reception mode information of the MBS session / bearer currently received by the terminal, radio bearer configuration information of the MBS bearer currently received by the terminal, and quality of service QoS configuration information of the MBS session / bearer currently received by the terminal.

[0244] Optionally, 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 PTP and PTM simultaneous reception;

[0245] The reception mode information of the MBS session / bearer currently received by the terminal includes at least one of the following: PTP reception, PTM reception, and PTP and PTM simultaneous reception.

[0246] Optionally, 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.

[0247] Optionally, the radio bearer configuration information includes: PTP bearer configuration information, and / or, PTM bearer configuration information;

[0248] 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:

[0249] 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;

[0250] The PTM bearer configuration information is used to configure the PTM bearer. The PTM bearer configuration information includes at least one of the following:

[0251] PTM radio bearer identifier, logical channel identifier, SDAP configuration information, PDCP configuration information, RLC bearer configuration information.

[0252] Optionally, 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;

[0253] Optionally, the acceptable MBS session / bearer information indicated in the handover request response includes at least one of the following:

[0254] The second network device can accept MBS session / bearer identifiers, broadcast / multicast service session reception modes, and acceptable service session / bearer QoS configuration information.

[0255] Optionally, the MBS session / bearer information that cannot be accommodated indicated in the handover request response includes at least one of the following:

[0256] The MBS session / bearer identifier that cannot be accepted by the second network device, and the reason why the second network device cannot accept the MBS session / bearer corresponding to the MBS session / bearer identifier.

[0257] Optionally, the bearer configuration information of the second network device includes at least one of the following:

[0258] PTM radio bearer identifier, logical channel identifier, SDAP configuration information, PDCP configuration information, RLC bearer configuration information.

[0259] Optionally, the UE scheduling configuration information of the second network device indicated in the handover request response includes at least one of the following:

[0260] Scheduling information of multicast service channels, and physical layer parameters required for configuring multicast service channels.

[0261] Optionally, 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.

[0262] Optionally, sending a switching request to the second network device includes:

[0263] A switching request is sent to the access mobility management function AMF, and the switching request is forwarded to the second network device through the AMF; wherein the switching request received by the second network device carries the MBS session bearer information.

[0264] Optionally, before sending the switching request to the second network device, the method further includes:

[0265] The measurement results of the broadcast / multicast service frequencies sent by the receiving terminal.

[0266] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0267] Example 5

[0268] The embodiment of the present invention provides an information sending device, which is applied to a terminal. The device is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions thereof will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and contemplated.

[0269] Fig.12 is a structural block diagram of an information sending device provided according to an embodiment of the present invention, such as Fig.12 As shown, the information sending device in this embodiment includes:

[0270] A first sending module 502 is configured to send MBS indication information that the UE is interested in and MBS indication information that the UE is receiving to a first network device;

[0271] 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 of interest to the UE.

[0272] It should be further explained that the remaining optional embodiments and technical effects of the information sending device in this embodiment correspond to the information sending method recorded in Example 2, so they will not be repeated here.

[0273] Optionally, the MBS indication information of interest to the UE further includes:

[0274] Service identification information of the MBS that the UE is interested in;

[0275] The MBS service identification information further includes at least one of the following: an MBS service / session identification, a temporary mobile group identification TMGI of the MBS, an MBS identification, and a PDU session identification indicating an MBS session.

[0276] Optionally, the MBS indication information of interest to the UE further includes:

[0277] The reception mode of the MBS that the UE is interested in;

[0278] The receiving mode includes at least one of the following: unicast receiving, broadcast / multicast receiving, and unicast and multicast receiving simultaneously.

[0279] Optionally, the MBS indication information of interest to the UE further includes:

[0280] The service area of ​​the MBS that the UE is interested in.

[0281] Optionally, the RRC reconfiguration information includes:

[0282] Target cell identifier, acceptable MBS list, acceptable MBS configuration information, acceptable MBS reception mode information.

[0283] Optionally, the configuration information of the acceptable MBS includes at least one of the following:

[0284] PTM radio bearer identifier, logical channel identifier, SDAP configuration information, PDCP configuration information, RLC bearer configuration information.

[0285] Optionally, the configuration information of the acceptable MBS includes at least one of the following:

[0286] Scheduling information of multicast service channels, and physical layer parameters required for configuring multicast service channels.

[0287] Optionally, the acceptable MBS reception mode information includes at least one of the following:

[0288] Unicast reception, broadcast / multicast reception, and simultaneous unicast and multicast reception.

[0289] Optionally, after receiving the RRC reconfiguration information returned by the first network device according to the MBS indication information, the method further includes:

[0290] The resources of the first network device are released, and the PDCP and RLC are rebuilt and the MAC is reset according to the radio bearer configuration information from the second network device, thereby establishing a PTM bearer and receiving services based on the PTM bearer.

[0291] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0292] Example 6

[0293] The embodiment of the present invention provides a switching device, which is applied to a second network device. The device is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions thereof will not be repeated. As used below, the term "module" may implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and contemplated.

[0294] Fig.13 is a structural block diagram (II) of a switching device provided according to an embodiment of the present invention, such as Fig.13 As shown, the switching device in this embodiment includes:

[0295] The third receiving module 602 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 the MBS session, and the MBS bearer information is used to indicate the MBS bearer;

[0296] The return module 604 is used 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 can be accommodated by the second network device, MBS session / bearer information that cannot be accommodated by the second network device, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.

[0297] It should be further explained that the remaining optional embodiments and technical effects of the switching device in this embodiment correspond to the switching method in Example 3, so they are not repeated here.

[0298] Optionally, the MBS session / bearer information includes at least one of the following:

[0299] MBS session information that the terminal is interested in, MBS session / bearer information currently received by the terminal, and terminal capability information.

[0300] Optionally, the MBS session information of interest to the terminal includes at least one of the following:

[0301] The identification information of the MBS session that the terminal is interested in, the MBS area identification, the reception priority information, and the MBS session reception mode information expected by the terminal.

[0302] Optionally, the receiving priority information includes at least one of the following:

[0303] Prioritize unicast reception, prioritize broadcast / multicast reception, and prioritize the level of receiving MBS sessions.

[0304] Optionally, the MBS session / bearer information currently received by the terminal includes at least one of the following:

[0305] Identification information of the MBS session / bearer currently received by the terminal, reception mode information of the MBS session / bearer currently received by the terminal, radio bearer configuration information of the MBS bearer currently received by the terminal, and quality of service QoS configuration information of the MBS session / bearer currently received by the terminal.

[0306] Optionally, 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 PTP and PTM simultaneous reception;

[0307] The reception mode information of the MBS session / bearer currently received by the terminal includes at least one of the following: PTP reception, PTM reception, and PTP and PTM simultaneous reception.

[0308] Optionally, 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.

[0309] Optionally, the radio bearer configuration information includes: PTP bearer configuration information, and / or, PTM bearer configuration information;

[0310] 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:

[0311] 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;

[0312] The PTM bearer configuration information is used to configure the PTM bearer. The PTM bearer configuration information includes at least one of the following:

[0313] PTM radio bearer identifier, logical channel identifier, SDAP configuration information, PDCP configuration information, RLC bearer configuration information.

[0314] Optionally, 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;

[0315] Optionally, the acceptable MBS session / bearer information indicated in the handover request response includes at least one of the following:

[0316] The second network device can accept MBS session / bearer identifiers, broadcast / multicast service session reception modes, and acceptable service session / bearer QoS configuration information.

[0317] Optionally, the MBS session / bearer information that cannot be accommodated indicated in the handover request response includes at least one of the following:

[0318] The MBS session / bearer identifier that cannot be accepted by the second network device, and the reason why the second network device cannot accept the MBS session / bearer corresponding to the MBS session / bearer identifier.

[0319] Optionally, the bearer configuration information of the second network device includes at least one of the following:

[0320] PTM radio bearer identifier, logical channel identifier, SDAP configuration information, PDCP configuration information, RLC bearer configuration information.

[0321] Optionally, the UE scheduling configuration information of the second network device indicated in the handover request response includes at least one of the following:

[0322] Scheduling information of multicast service channels, and physical layer parameters required for configuring multicast service channels.

[0323] Optionally, 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.

[0324] Optionally, sending a switching request to the second network device includes:

[0325] A switching request is sent to the access mobility management function AMF, and the switching request is forwarded to the second network device through the AMF; wherein the switching request received by the second network device carries the MBS session bearer information.

[0326] Optionally, before sending the switching request to the second network device, the method further includes:

[0327] The measurement results of the broadcast / multicast service frequencies sent by the receiving terminal.

[0328] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0329] Example 7

[0330] An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0331] Optionally, in this embodiment, the computer-readable storage medium may be configured to store a computer program for executing the above embodiment.

[0332] Optionally, in this embodiment, the above-mentioned computer-readable storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store computer programs.

[0333] Example 8

[0334] An embodiment of the present invention further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0335] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0336] Optionally, in this embodiment, the processor may be configured to execute the steps in the above embodiment through a computer program.

[0337] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

[0338] Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0339] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A switching method, characterized in that: Applied to a first network device, the method comprises: Sending a handover request to a second network device; wherein the handover request carries broadcast multicast service MBS session / bearer information; wherein the MBS session / bearer information includes quality of service QoS configuration information of the MBS session / bearer currently received by the terminal; wherein the QoS configuration information is used to indicate each QoS flow in the QoS flow list of the radio bearer corresponding to the MBS service currently being received by the UE, including one or more QoS flow identifiers, QoS parameters of the QoS flow level, and MBS session identifier information; 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 can be accommodated by the second network device, MBS session / bearer information that cannot be accommodated by the second network device, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.

2. The method according to claim 1, characterized in that The MBS session / bearer information includes at least one of the following: MBS session information that the terminal is interested in, MBS session / bearer information currently received by the terminal, and terminal capability information.

3. The method according to claim 2, characterized in that The MBS session information of interest to the terminal includes at least one of the following: The terminal includes the identification information of the MBS session that the terminal is interested in, the MBS area identification, the reception priority information, and the MBS session reception mode information that the terminal expects.

4. The method according to claim 3, characterized in that The receiving priority information includes at least one of the following: Prioritize unicast reception, prioritize broadcast / multicast reception, and prioritize the level of receiving MBS sessions.

5. The method according to claim 2 or 3, characterized in that: The MBS session / bearer information currently received by the terminal includes at least one of the following: The terminal currently receives identification information of an MBS session / bearer, the terminal currently receives reception mode information of an MBS session / bearer, and the terminal currently receives radio bearer configuration information of an MBS bearer.

6. The method according to claim 5, characterized in that The MBS session reception mode information desired by the terminal includes at least one of the following: point-to-point PTP reception, point-to-multipoint PTM reception, and PTP and PTM simultaneous reception; The reception mode information of the MBS session / bearer currently received by the terminal includes at least one of the following: PTP reception, PTM reception, and PTP and PTM simultaneous reception.

7. The method according to claim 2, characterized in that The terminal capability information is used to indicate: the terminal supports receiving a unicast service and an MBS session in the same time slot; or the terminal does not support receiving a unicast service and an MBS session in the same time slot.

8. The method according to claim 5, characterized in that 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 a PTM bearer, and the PTM bearer configuration information includes at least one of the following: PTM radio bearer identifier, logical channel identifier, SDAP configuration information, PDCP configuration information, RLC bearer configuration information.

9. The method according to claim 3, characterized in that: 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.

10. The method according to claim 1, characterized in that The acceptable MBS session / bearer information indicated in the handover request response includes at least one of the following: The second network device can accept MBS session / bearer identifiers, broadcast / multicast service session reception modes, and acceptable service session / bearer QoS configuration information.

11. The method according to claim 1, characterized in that: The unacceptable MBS session / bearer information indicated in the handover request response includes at least one of the following: The MBS session / bearer identifier that cannot be accepted by the second network device, and the reason why the second network device cannot accept the MBS session / bearer corresponding to the MBS session / bearer identifier.

12. The method according to claim 1, characterized in that The bearer configuration information of the second network device includes at least one of the following: PTM radio bearer identifier, logical channel identifier, SDAP configuration information, PDCP configuration information, RLC bearer configuration information.

13. The method according to claim 1, characterized in that The UE scheduling configuration information of the second network device indicated in the handover request response includes at least one of the following: Scheduling information of multicast service channels, and physical layer parameters required for configuring multicast service channels.

14. The method according to claim 1, characterized in that The switching request response further includes at least one of the following: system information block configuration information, multicast control channel configuration information, and multicast service channel configuration information of the second network device.

15. The method according to claim 1, characterized in that The sending a switching request to the second network device includes: The switching request is sent to an access mobility management function AMF, and the switching request is forwarded to the second network device through the AMF; wherein the switching request received by the second network device carries the MBS session bearer information.

16. The method according to claim 1, characterized in that The MBS session information is further used to indicate the MBS service corresponding to the MBS session; The MBS sessions correspond to the MBS services one by one.

17. A switching method, characterized in that: Applied to the second network device, the method comprises: Receive a handover request sent by a 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 an MBS bearer; wherein the MBS session / bearer information includes quality of service QoS configuration information of the MBS session / bearer currently received by the terminal; wherein the QoS configuration information is used to indicate each QoS flow in a QoS flow list of a radio bearer corresponding to an MBS service currently being received by the UE, including one or more QoS flow identifiers, QoS parameters of a QoS flow level, and MBS session identifier information; 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 can be accommodated by the second network device, MBS session / bearer information that cannot be accommodated by the second network device, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.

18. The method according to claim 17, characterized in that The MBS session / bearer information includes at least one of the following: MBS session / bearer information that the terminal is interested in, MBS session / bearer information currently received by the terminal, and terminal capability information.

19. The method according to claim 18, characterized in that The MBS session / bearer information of interest to the terminal includes at least one of the following: The identification information of the MBS session that the terminal is interested in, the MBS area identification, the reception priority information, and the MBS session / bearer reception mode information expected by the terminal.

20. The method according to claim 19, characterized in that The receiving priority information includes at least one of the following: Prioritize unicast reception, prioritize broadcast / multicast reception, and prioritize the level of receiving MBS sessions.

21. The method according to claim 17 or 19, characterized in that The MBS session / bearer information currently received by the terminal includes at least one of the following: The terminal currently receives identification information of an MBS session / bearer, the terminal currently receives reception mode information of an MBS session / bearer, and the terminal currently receives radio bearer configuration information of an MBS bearer.

22. A switching device, characterized in that: Set on the first network device, the device includes: A first sending module is used to send a switching request to a second network device; wherein the switching request carries broadcast multicast service MBS session / bearer information; wherein the MBS session / bearer information includes quality of service QoS configuration information of the MBS session / bearer currently received by the terminal; wherein the QoS configuration information is used to indicate each QoS flow in the QoS flow list of the wireless bearer corresponding to the MBS service currently being received by the UE, including one or more QoS flow identifiers, QoS parameters of the QoS flow level, and MBS session identifier information; The first receiving module is configured to receive a handover request response sent by the second network device, wherein the handover request response includes at least one of the following: MBS session / bearer information that can be accommodated by the second network device, MBS session / bearer information that cannot be accommodated by the second network device, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.

23. A switching device, characterized in that: Set on the second network device, the device includes: A 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 an MBS bearer, wherein the MBS session / bearer information includes quality of service QoS configuration information of the MBS session / bearer currently received by the terminal; wherein the QoS configuration information is used to indicate each QoS flow in a QoS flow list of a radio bearer corresponding to an MBS service currently being received by the UE, including one or more QoS flow identifiers, QoS parameters of a QoS flow level, and MBS session identifier information; A return module is used 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 can be accommodated by the second network device, MBS session / bearer information that cannot be accommodated by the second network device, UE scheduling configuration information of the second network device, and bearer configuration information of the second network device.

24. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program is configured to execute the method described in any one of claims 1 to 16 and claims 17 to 21 when executed.

25. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to run the computer program to perform the method described in any one of claims 1 to 16 and claims 17 to 21.

Images