Multicast service implementation method and device, and communication equipment

Abstract

The present application discloses a method and apparatus for implementing a multicast service, and a communication device, which belongs to the field of communication technology. The method for implementing a multicast service includes: after a terminal receives a first switching command from a source base station, the terminal sends first information to a target base station, and the first information is used to join the multicast service. Through the technical solution disclosed in the present application, it is possible to enable a UE to join a multicast service at a target base station.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method and apparatus for implementing a multicast service, and a communication device. Background Art

[0002] Related technologies provide multicast services in the form of network elements. If a handover occurs when a user terminal (UE) receives multicast service data, the target base station may not support the transmission of the multicast service data or only provide the transmission of part of the multicast service data. Summary of the invention

[0003] The embodiments of the present application provide a method and apparatus for implementing a multicast service, and a communication device, which can enable a UE to join a multicast service at a target base station.

[0004] In a first aspect, an embodiment of the present application provides a method for implementing a multicast service, the method comprising:

[0005] After receiving the first switching command from the source base station, the terminal sends first information to the target base station, where the first information is used to join the multicast service.

[0006] In a second aspect, an embodiment of the present application provides a method for implementing a multicast service, the method comprising:

[0007] The target base station sends multicast resource information to the terminal through the source base station;

[0008] The target base station receives first information sent by the terminal, where the first information is used to join a multicast service;

[0009] The target base station sends the first information to the core network function.

[0010] In a third aspect, an embodiment of the present application provides a multicast service implementation device, the device comprising:

[0011] The sending module is used to send first information to the target base station after receiving the first switching command from the source base station, where the first information is used to join the multicast service.

[0012] In some embodiments, the first information includes multicast service information.

[0013] In some embodiments, the sending module is further used to send the first information to the core network function through the target base station.

[0014] In some embodiments, the sending module is specifically used to send a switching confirmation message to the target base station, carrying the first information.

[0015] In some embodiments, the first information is used to establish or activate a protocol data unit (PDU) session.

[0016] In some embodiments, the sending module is specifically configured to perform any of the following:

[0017] When the multicast resource information sent by the source base station is not received, sending the first information;

[0018] The first information is sent according to the received multicast resource information sent by the source base station.

[0019] In some embodiments, the multicast resource information includes a multicast service joining indication.

[0020] In some embodiments, the sending module is specifically configured to send the first information when the multicast resource information does not include multicast service information.

[0021] In some embodiments, the terminal has joined one or more multicast services before receiving the first handover command from the source base station;

[0022] The sending module is specifically configured to send the first information when the multicast resource information includes information about a portion of multicast services that have been added.

[0023] In a fourth aspect, an embodiment of the present application provides a multicast service implementation device, the device comprising:

[0024] A first sending module, configured to send multicast resource information to a terminal via a source base station;

[0025] A receiving module, configured to receive first information sent by the terminal, where the first information is used to join a multicast service;

[0026] The second sending module is used to send the first information to the core network function.

[0027] In some embodiments, the first information includes multicast service information.

[0028] In some embodiments, the first information is used to activate or establish a protocol data unit (PDU) session.

[0029] In some embodiments, the receiving module is further configured to receive a switching confirmation message sent by the terminal, and the first information is included in the switching confirmation message.

[0030] In some embodiments, the second sending module is further used to send a switching completion message to the core network function, and the first information is included in the switching completion message.

[0031] In some embodiments, the multicast resource information includes a multicast service joining indication; and / or

[0032] The multicast resource information includes multicast service information.

[0033] In a fifth aspect, an embodiment of the present application further provides an electronic device, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction implements the steps of the method described above when executed by the processor.

[0034] In a sixth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and the program or instruction, when executed by a processor, implements the steps of the method described above.

[0035] In the seventh aspect, an embodiment of the present application provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect or the second aspect.

[0036] In an embodiment of the present application, if switching occurs when the terminal receives multicast service data, the terminal sends first information for joining the multicast service to the target base station. After receiving the first information, the target base station can send the first information to the core network function to support the sending of multicast service data, thereby enabling the terminal to join the multicast service at the target base station. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments of the present application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0038] Figure 1 A schematic diagram showing a wireless communication system;

[0039] Figure 2 A schematic diagram showing a flow chart of a method for implementing a multicast service on a terminal side according to an embodiment of the present application;

[0040] Figure 3 A schematic diagram showing a flow chart of a method for implementing a multicast service on a target base station side according to an embodiment of the present application;

[0041] Figure 4 and Figure 5 A flowchart showing a method for implementing a multicast service according to a specific embodiment of the present application;

[0042] Figure 6 A schematic diagram showing the structure of a device for implementing a multicast service on a terminal side according to an embodiment of the present application;

[0043] Figure 7A schematic diagram showing the structure of a device for implementing a multicast service at a target base station side according to an embodiment of the present application;

[0044] Figure 8 A schematic diagram showing the composition of a terminal according to an embodiment of the present application;

[0045] Fig. 9 A schematic diagram showing the composition of a network side device according to an embodiment of the present application. DETAILED DESCRIPTION

[0046] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0047] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here. In addition, the "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated with each other are in an "or" relationship.

[0048] The technology described herein is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, and can also be used for various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" are often used interchangeably. A CDMA system can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA). UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants. A TDMA system can implement radio technologies such as Global System for Mobile Communication (GSM). OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolution-UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are parts of Universal Mobile Telecommunications System (UMTS). LTE and more advanced LTE (such as LTE-A) are new UMTS versions that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).The techniques described herein may be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. However, the following description describes an NR system for example purposes and uses NR terminology in much of the following description, although the techniques may also be applicable to applications other than NR system applications.

[0049] The following description provides examples and does not limit the scope, applicability, or configuration set forth in the claims. Changes may be made to the functions and arrangements of the elements discussed without departing from the spirit and scope of the present disclosure. Various examples may appropriately omit, replace, or add various procedures or components. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

[0050] See also Figure 1 , Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. The terminal 11 may also be referred to as a terminal device or a user terminal (User Equipment, UE). The terminal 11 may be a terminal side device such as a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a personal digital assistant (Personal Digital Assistant, PDA), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 can be a base station or a core network, wherein the above-mentioned base station can be a base station of 5G and later versions (for example: gNB, 5G NR NB, etc.), or a base station in other communication systems (for example: eNB, WLAN access point, or other access point, etc.), or a location server (for example: E-SMLC or LMF (Location Manager Function)), wherein the base station can be called a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the embodiment of the present application does not limit the specific type of the base station and the specific communication system.

[0051] The embodiments of the present application provide a method and apparatus for implementing a multicast service, and a communication device, which can enable a UE to join a multicast service at a target base station.

[0052] The present application embodiment provides a method for implementing a multicast service, which is applied to a terminal, such as Figure 2 As shown, including:

[0053] Step 101: After receiving a first switching command from a source base station, first information is sent to a target base station, where the first information is used to join a multicast service.

[0054] In this embodiment, if switching occurs when the terminal receives multicast service data, the terminal sends first information for joining the multicast service to the target base station. After receiving the first information, the target base station can send the first information to the core network function to support the sending of multicast service data, thereby enabling the terminal to join the multicast service at the target base station.

[0055] The first switching command may carry multicast air interface resource information, such as a multicast identifier.

[0056] When the terminal accesses the target base station, it is necessary to send a handover confirmation message, such as a HandoverConfirm message, to the target base station, and it is also necessary to send first information for activating or establishing a protocol data unit (PDU) session related to the multicast service to the target base station, and the first information may specifically be a non-access stratum (NAS) message. In some embodiments, the first information may include multicast service information, so that the target base station can be informed of the multicast service information.

[0057] Since a core network function CN NF (such as an access and mobility management function (AMF)) is required to reserve core network resources for a multicast-related PDU session based on the first information, the sending of the first information to the target base station further includes:

[0058] The first information is sent to the core network function through the target base station.

[0059] Since a switching confirmation message needs to be sent to the target base station when the terminal accesses the target base station, in order to save signaling overhead, sending the first information to the target base station includes: sending a switching confirmation message to the target base station, carrying the first information, that is, the first information is included in the switching confirmation message.

[0060] In some embodiments, sending the first information includes any of the following:

[0061] When the multicast resource information sent by the source base station is not received, sending the first information;

[0062] The first information is sent according to the received multicast resource information sent by the source base station.

[0063] For example, when the multicast resource information does not include multicast service information, the first information is sent.

[0064] In some embodiments, the multicast resource information may include a multicast service joining indication.

[0065] In some embodiments,

[0066] Before receiving the first switching command from the source base station, one or more multicast services have been added;

[0067] The terminal may send the first information when the multicast resource information includes information of a portion of multicast services that have been added.

[0068] The embodiment of the present application provides a method for implementing a multicast service, which is applied to a target base station, such as Figure 3 As shown, including:

[0069] Step 201: The target base station sends multicast resource information to the terminal through the source base station;

[0070] Step 202: The target base station receives first information sent by the terminal, where the first information is used to join a multicast service;

[0071] Step 203: The target base station sends the first information to the core network function.

[0072] In this embodiment, if switching occurs when the terminal receives multicast service data, the terminal sends first information for joining the multicast service to the target base station. After receiving the first information, the target base station can send the first information to the core network function to support the sending of multicast service data, thereby enabling the terminal to join the multicast service at the target base station.

[0073] When the terminal accesses the target base station, it is necessary to send a handover confirmation message, such as a HandoverConfirm message, to the target base station, and it is also necessary to send first information for activating or establishing a protocol data unit (PDU) session related to the multicast service to the target base station, and the first information may specifically be a non-access stratum (NAS) message. In some embodiments, the first information may include multicast service information, so that the target base station can be informed of the multicast service information.

[0074] In some embodiments, the method further comprises:

[0075] A handover confirmation message sent by the terminal is received, wherein the first information is included in the handover confirmation message. Since the terminal needs to send a handover confirmation message to the target base station when accessing the target base station, in order to save signaling overhead, the first information can be included in the handover confirmation message.

[0076] In some embodiments, the method further comprises:

[0077] A switching completion message is sent to the core network function, wherein the first information is included in the switching completion message.

[0078] Since the target base station needs to send a handover completion message to the core network function after the handover is completed, in order to save signaling overhead, the first information can be included in the handover completion message.

[0079] In some embodiments, the multicast resource information includes a multicast service joining indication; and / or

[0080] The multicast resource information includes multicast service information.

[0081] In a specific example, Figure 4 As shown, the core network function (CN NF) includes AMF, session management function (SMF) / core network user plane function (UPF), multicast (MB)-SMF / MB-UPF. First, the core network function sends multicast data through a shared channel with the source base station. The source base station (Source gNB) distributes multicast data to the terminal through broadcast or point-to-point mode. The terminal also has other PDU sessions in an active state (that is, the terminal is in a connected state), and these PDU sessions are not related to the multicast service.

[0082] The method for implementing the multicast service in this embodiment includes the following steps:

[0083] Step 1: The Source gNB decides to perform a handover operation, selects a target gNB, and sends a handover notification message, such as a Handover Required message, to the core network.

[0084] Among them, the Source gNB can select the target base station based on the measurement report or candidate cell information, or it can independently select the target base station.

[0085] Step 2: The CN NF sends a handover request to the target gNB, such as a Handover Request message, which carries the information in the Handover Notification message and may also include multicast service information, such as the multicast service identifier and the quality of service (QoS) information related to the multicast service identifier.

[0086] Step 3: The target base station reserves air interface resources. In addition to reserving air interface resources for PDU sessions, air interface resources can also be reserved for multicast services.

[0087] Step 4: The target base station returns a handover response to the CN NF, such as a Handover Response message, which may carry the air interface resource information obtained in step 3;

[0088] Step 5: The CN NF sends a handover command to the source base station, such as a Handover Command message, carrying the received downlink forwarding reception resource information or core network forwarding resource information;

[0089] Step 6: The source base station sends a handover command to the UE, which may carry multicast air interface resource information, such as a multicast identifier;

[0090] Step 7: The UE accesses the target base station, sends a handover confirmation message, such as a HandoverConfirm message, to the target base station, and sends a NAS message to the core network function through the target base station to activate or establish a PDU session related to the multicast service. The NAS message may be a Service Request or a PDU Session Establishment Request message, which may be included in the NAS container of the handover confirmation message.

[0091] The UE may decide whether to send a NAS message based on whether the multicast resource information is received or based on the received multicast resource information. For example, the UE may send a NAS message when the multicast resource information is not received or when the received multicast resource information does not contain all multicast service-related resource information.

[0092] Step 8: The target base station forwards the NAS message and the handover completion message (N2 request) to the core network function. The NAS message may be included in the NAS container of the handover completion message.

[0093] Step 9: The core network function (such as AMF) reserves the core network resources of the multicast-related PDU session based on the NAS message, and may update the multicast-irrelevant PDU session resources at the same time, or may wait until the multicast-related PDU session is established or activated before updating the multicast-irrelevant PDU session resources;

[0094] Step 10: The core network function sends the multicast-related PDU session core network resource information to the target base station. The multicast-related PDU session core network resource information may be included in the N2 response.

[0095] Step 11: The target base station interacts with the UE through the air interface based on the core network resource information of the multicast-related PDU session, and reserves the air interface resources of the multicast-related PDU session;

[0096] Step 12: The target base station sends multicast-related PDU session base station resource information to the core network function. The multicast-related PDU session base station resource information may be carried in the N2 request;

[0097] Step 13: The core network function updates the multicast-related PDU session using the multicast-related PDU session base station resource information;

[0098] Step 14: In the case that the UE does not carry a NAS message in the handover confirmation message in step 7, the network side and the UE establish or activate a multicast-related PDU session based on the NAS message sent by the UE;

[0099] Step 15: After the multicast-related PDU session is established or activated, the core network function updates the multicast-independent PDU session resources.

[0100] Afterwards, the core network function may also establish a multicast-independent PDU session with the target base station.

[0101] In another specific example, Figure 5 As shown, the core network functions include AMF, session management function entity (SessionManagement Function, SMF) / core network user plane function entity (User Plane Function, UPF), MB-SMF / MB-UPF. First, the core network function sends multicast data through a shared channel with the source base station. The source base station (SourcegNB) distributes multicast data to the terminal through broadcast or point-to-point mode. The terminal also has other PDU sessions in an active state (that is, the terminal is in a connected state), and these PDU sessions are not related to the multicast service.

[0102] The method for implementing the multicast service in this embodiment includes the following steps:

[0103] Step 1: The Source gNB decides to perform a handover operation, selects a target base station, and sends a handover request message, such as a Handover Request message, to the target base station, which may include multicast service information, such as a multicast service identifier and QoS information related to the multicast service identifier.

[0104] Among them, the Source gNB can select the target base station based on the measurement report or candidate cell information, or it can independently select the target base station.

[0105] Step 2: The target base station reserves air interface resources. In addition to reserving air interface resources for PDU sessions, air interface resources can also be reserved for multicast services.

[0106] Step 3: The target base station returns a handover response to the source base station, such as a Handover Response message carrying air interface resource information;

[0107] Step 4: The source base station sends a handover command to the UE, which may carry multicast air interface resource information, such as a multicast identifier;

[0108] Step 5: The UE accesses the target base station, sends a handover confirmation message, such as a HandoverConfirm message, to the target base station, and sends a NAS message to the core network function through the target base station to activate or establish a PDU session related to the multicast service. The NAS message may be a Service Request or a PDU Session Establishment Request message, which may be included in the NAS container of the handover confirmation message;

[0109] The UE may decide whether to send a NAS message based on whether the multicast resource information is received or based on the received multicast resource information. For example, the UE may send a NAS message when the multicast resource information is not received or when the received multicast resource information does not contain all multicast service-related resource information.

[0110] Step 6: The target base station forwards the NAS message and the N2 request to the core network function. The NAS message may be included in the NAS container of the N2 request.

[0111] Step 7: The core network function (such as AMF) reserves the core network resources of the multicast-related PDU session based on the NAS message, and may update the multicast-irrelevant PDU session resources at the same time, or may wait until the multicast-related PDU session is established or activated before updating the multicast-irrelevant PDU session resources;

[0112] Step 8: The core network function sends an N2 response to the target base station, which carries the core network resource information of the multicast-related PDU session;

[0113] Step 9: The target base station interacts with the UE through the air interface based on the core network resource information of the multicast-related PDU session, and reserves the air interface resources of the multicast-related PDU session;

[0114] Step 10: The target base station sends an N2 request to the core network function, which carries the multicast-related PDU session base station resource information;

[0115] Step 11: The core network function updates the multicast-related PDU session using the multicast-related PDU session base station resource information;

[0116] Step 12: When the UE does not carry a NAS message in the handover confirmation message, the network side and the UE establish or activate a multicast-related PDU session based on the NAS message sent by the UE;

[0117] Step 13: After the multicast-related PDU session is established or activated, the core network function updates the multicast-independent PDU session resources.

[0118] Afterwards, the core network function may also establish a multicast-independent PDU session with the target base station.

[0119] It should be noted that the multicast service implementation method provided in the embodiment of the present application can be executed by a multicast service implementation device, or a module in the multicast service implementation device for executing the loading multicast service implementation method. In the embodiment of the present application, the multicast service implementation method provided in the embodiment of the present application is described by taking the multicast service implementation device executing the loading multicast service implementation method as an example.

[0120] The embodiment of the present application provides a multicast service implementation device, which is applied to a terminal 300, such as Figure 6 As shown, the device comprises:

[0121] The sending module 310 is used to send first information to the target base station after receiving the first switching command from the source base station, where the first information is used to join the multicast service.

[0122] In this embodiment, if switching occurs when the terminal receives multicast service data, the terminal sends first information for joining the multicast service to the target base station. After receiving the first information, the target base station can send the first information to the core network function to support the sending of multicast service data, thereby enabling the terminal to join the multicast service at the target base station.

[0123] In some embodiments, the first information includes multicast service information.

[0124] In some embodiments, the sending module is further used to send the first information to the core network function through the target base station.

[0125] In some embodiments, the sending module is specifically used to send a switching confirmation message to the target base station, carrying the first information.

[0126] In some embodiments, the first information is used to establish or activate a protocol data unit (PDU) session.

[0127] In some embodiments, the sending module is specifically configured to perform any of the following:

[0128] When the multicast resource information sent by the source base station is not received, sending the first information;

[0129] The first information is sent according to the received multicast resource information sent by the source base station.

[0130] In some embodiments, the multicast resource information includes a multicast service joining indication.

[0131] In some embodiments, the sending module is specifically configured to send the first information when the multicast resource information does not include multicast service information.

[0132] In some embodiments, the terminal has joined one or more multicast services before receiving the first handover command from the source base station;

[0133] The sending module is specifically configured to send the first information when the multicast resource information includes information about a portion of multicast services that have been added.

[0134] The multicast service implementation device in the embodiment of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. Exemplarily, the mobile electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), etc. The non-mobile electronic device can be a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0135] The multicast service implementation device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0136] It should be noted that the multicast service implementation method provided in the embodiment of the present application can be executed by a multicast service implementation device, or a module in the multicast service implementation device for executing the loading multicast service implementation method. In the embodiment of the present application, the multicast service implementation method provided in the embodiment of the present application is described by taking the multicast service implementation device executing the loading multicast service implementation method as an example.

[0137] The embodiment of the present application provides a multicast service implementation device, which is applied to a target base station 400, such as Figure 7 As shown, the device comprises:

[0138] A first sending module 410, configured to send multicast resource information to a terminal via a source base station;

[0139] A receiving module 420, configured to receive first information sent by the terminal, where the first information is used to join a multicast service;

[0140] The second sending module 430 is used to send the first information to the core network function.

[0141] In this embodiment, if switching occurs when the terminal receives multicast service data, the terminal sends first information for joining the multicast service to the target base station. After receiving the first information, the target base station can send the first information to the core network function to support the sending of multicast service data, thereby enabling the terminal to join the multicast service at the target base station.

[0142] In some embodiments, the first information includes multicast service information.

[0143] In some embodiments, the first information is used to activate or establish a protocol data unit (PDU) session.

[0144] In some embodiments, the receiving module 420 is further configured to receive a switching confirmation message sent by the terminal, and the first information is included in the switching confirmation message.

[0145] In some embodiments, the second sending module 430 is further configured to send a switching completion message to the core network function, wherein the first information is included in the switching completion message.

[0146] In some embodiments, the multicast resource information includes a multicast service joining indication; and / or

[0147] The multicast resource information includes multicast service information.

[0148] The multicast service implementation device in the embodiment of the present application can be a mobile electronic device or a non-mobile electronic device. For example, the mobile electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a personal digital assistant (PDA), etc., and the non-mobile electronic device can be a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0149] The multicast service implementation device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0150] Optionally, an embodiment of the present application also provides an electronic device, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, the various processes of the embodiment of the above-mentioned acquisition or multicast service implementation method are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0151] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.

[0152] The electronic device of this embodiment may be a terminal. Figure 8 In order to implement the hardware structure diagram of a terminal in each embodiment of the present application, the terminal 50 includes but is not limited to: a radio frequency unit 51, a network module 52, an audio output unit 53, an input unit 54, a sensor 55, a display unit 56, a user input unit 57, an interface unit 58, a memory 59, a processor 510, and a power supply 511. Those skilled in the art can understand that Figure 8 The terminal structure shown in the figure does not constitute a limitation on the terminal, and the terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. In the embodiments of the present application, the terminal includes but is not limited to a mobile phone, a tablet computer, a laptop computer, a PDA, a vehicle-mounted terminal, a wearable device, and a pedometer.

[0153] It should be understood that in the embodiment of the present application, the radio frequency unit 51 can be used for receiving and sending signals during information transmission or calls. Specifically, after receiving downlink data from the base station, it is sent to the processor 510 for processing; in addition, uplink data is sent to the base station. Generally, the radio frequency unit 51 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc. In addition, the radio frequency unit 51 can also communicate with the network and other devices through a wireless communication system.

[0154] The memory 59 can be used to store software programs and various data. The memory 59 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area can store data created according to the use of the mobile phone (such as audio data, a phone book, etc.), etc. In addition, the memory 59 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0155] The processor 510 is the control center of the terminal. It uses various interfaces and lines to connect various parts of the entire terminal. It executes various functions of the terminal and processes data by running or executing software programs and / or modules stored in the memory 59, and calling data stored in the memory 59, so as to monitor the terminal as a whole. The processor 510 may include one or more processing units; preferably, the processor 510 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 510.

[0156] The terminal 50 may also include a power supply 511 (such as a battery) for supplying power to various components. Preferably, the power supply 511 may be logically connected to the processor 510 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system.

[0157] In addition, the terminal 50 includes some functional modules not shown, which will not be described in detail here.

[0158] The electronic device of this embodiment may also be a network side device, such as a target base station. Fig. 9 As shown, the network side device 600 includes: an antenna 61, a radio frequency device 62, and a baseband device 63. The antenna 61 is connected to the radio frequency device 62. In the uplink direction, the radio frequency device 62 receives information through the antenna 61 and sends the received information to the baseband device 63 for processing. In the downlink direction, the baseband device 63 processes the information to be sent and sends it to the radio frequency device 62. The radio frequency device 62 processes the received information and sends it out through the antenna 61.

[0159] The frequency band processing device may be located in a baseband device 63 . The method performed by the network-side device in the above embodiment may be implemented in the baseband device 63 . The baseband device 63 includes a processor 64 and a memory 65 .

[0160] The baseband device 63 may include, for example, at least one baseband board on which a plurality of chips are arranged. Fig. 9 As shown, one of the chips is, for example, a processor 64, which is connected to a memory 65 to call a program in the memory 65 to execute the network-side device operations shown in the above method embodiment.

[0161] The baseband device 63 may further include a network interface 66 for exchanging information with the radio frequency device 62 . The interface may be, for example, a common public radio interface (CPRI).

[0162] The processor here can be a processor or a collective name for multiple processing elements. For example, the processor can be a CPU, an ASIC, or one or more integrated circuits configured to implement the method executed by the above network-side device, such as one or more microprocessors DSP, or one or more field programmable gate arrays FPGA, etc. The storage element can be a memory or a collective name for multiple storage elements.

[0163] The memory 65 may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the nonvolatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct memory bus random access memory (DRRAM). The memory 65 described in the present application is intended to include, but is not limited to, these and any other suitable types of memory.

[0164] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the embodiment of the above-mentioned acquisition or multicast service implementation method are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0165] The processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0166] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned embodiments of the acquisition or multicast service implementation method, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0167] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0168] It should be noted that, in this article, the term "comprises", "includes" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements does not include those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0169] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, 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 a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0170] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A method for implementing a multicast service, It is characterized in that include: After receiving the first handover command from the source base station, the terminal sends first information to the target base station, where the first information is used to join the multicast service and the first information is also used to establish or activate a protocol data unit PDU session; Sending the first information includes: When the multicast resource information sent by the source base station is not received, sending the first information; The sending of the first information to the target base station further includes: The first information is sent to the core network function through the target base station, so that the core network function reserves core network resources for the multicast-related PDU session based on the first information.

2. The method for implementing a multicast service according to claim 1, It is characterized in that The first information includes multicast service information.

3. The method for implementing a multicast service according to claim 1, It is characterized in that Sending first information to the target base station includes: A handover confirmation message is sent to the target base station, carrying the first information.

4. The method for implementing a multicast service according to claim 1, It is characterized in that The multicast resource information includes a multicast service joining indication.

5. The method for implementing a multicast service according to claim 1, It is characterized in that The method further comprises: When the multicast resource information sent by the source base station is received and the multicast resource information does not include multicast service information, the first information is sent.

6. The method for implementing a multicast service according to claim 1, It is characterized in that Before receiving the first switching command from the source base station, one or more multicast services have been added; The method further comprises: When the multicast resource information sent by the source base station is received and the multicast resource information includes information of a portion of the multicast services that have been added, the first information is sent.

7. A method for implementing a multicast service, It is characterized in that include: The target base station sends multicast resource information to the terminal through the source base station; The target base station receives first information sent by the terminal, where the first information is used to join a multicast service and the first information is also used to establish or activate a protocol data unit (PDU) session; The target base station sends the first information to the core network function, so that the core network function reserves core network resources for the multicast-related PDU session based on the first information.

8. The method for implementing a multicast service according to claim 7, It is characterized in that The first information includes multicast service information.

9. The method for implementing a multicast service according to claim 7, It is characterized in that Also includes: A switching confirmation message sent by the terminal is received, wherein the first information is included in the switching confirmation message.

10. The method for implementing a multicast service according to claim 7, It is characterized in that Also includes: A switching completion message is sent to the core network function, wherein the first information is included in the switching completion message.

11. The method for implementing a multicast service according to claim 7, It is characterized in that The multicast resource information includes a multicast service joining instruction; and / or The multicast resource information includes multicast service information.

12. A device for implementing a multicast service, It is characterized in that include: A sending module, configured to send first information to a target base station after receiving a first switching command from a source base station, wherein the first information is used to join a multicast service and is also used to establish or activate a protocol data unit (PDU) session; The sending module is specifically used to execute: When the multicast resource information sent by the source base station is not received, sending the first information; The sending module is further used to send the first information to the core network function through the target base station, so that the core network function reserves core network resources for the multicast-related PDU session based on the first information.

13. A device for implementing a multicast service, It is characterized in that include: A first sending module, configured to send multicast resource information to a terminal via a source base station; A receiving module, configured to receive first information sent by the terminal, wherein the first information is used to join a multicast service, and the first information is also used to establish or activate a protocol data unit PDU session; The second sending module is used to send the first information to the core network function, so that the core network function reserves core network resources for multicast-related PDU sessions based on the first information.

14. The multicast service implementation device according to claim 13, It is characterized in that The receiving module is further configured to receive a switching confirmation message sent by the terminal, wherein the first information is included in the switching confirmation message.

15. An electronic device, It is characterized in that The method comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method according to any one of claims 1 to 11.

16. A readable storage medium, It is characterized in that The readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented.

Images