CN114071591A

CN114071591A - Multicast service implementation method and device and communication equipment

Info

Publication number: CN114071591A
Application number: CN202010754577.7A
Authority: CN
Inventors: 谢振华; 张艳霞; 柯小婉
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-07-30
Filing date: 2020-07-30
Publication date: 2022-02-18

Abstract

The application discloses a method and a device for realizing multicast service and communication equipment, and belongs to the technical field of communication. The method for realizing the multicast service comprises the following steps: and after receiving a first switching command of a source base station, the terminal sends first information to a target base station, wherein the first information is used for joining in the multicast service. By the technical scheme, the UE can join the multicast service in the target base station.

Description

Multicast service implementation method and device and communication equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for implementing a multicast service, and a communication device.

Background

In the related art, a multicast service is provided based on a network element form, and if a User Equipment (UE) switches when receiving multicast service data, a target base station may not support transmission of the multicast service data or only provide transmission of part of the multicast service data.

Disclosure of Invention

The embodiment of the application provides a method and a device for realizing multicast service and communication equipment, which can realize that UE joins in the multicast service in a target base station.

In a first aspect, an embodiment of the present application provides a method for implementing a multicast service, where the method includes:

and after receiving a first switching command of a source base station, the terminal sends first information to a target base station, wherein the first information is used for joining in the multicast service.

In a second aspect, an embodiment of the present application provides a method for implementing a multicast service, where the method includes:

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, wherein the first information is used for joining in a multicast service;

and the target base station sends the first information to a core network function.

In a third aspect, an embodiment of the present application provides an apparatus for implementing a multicast service, where the apparatus includes:

the sending module is used for sending first information to the target base station after receiving a first switching command of the source base station, wherein the first information is used for joining in the multicast service.

In some embodiments, the first information comprises multicast traffic information.

In some embodiments, the sending module is further configured to send the first information to a core network function through the target base station.

In some embodiments, the sending module is specifically configured to send a handover confirmation message to the target base station, where the handover confirmation message carries the first information.

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

In some embodiments, the sending module is specifically configured to perform any one of:

when the multicast resource information sent by the source base station is not received, the first information is sent;

and sending the first information according to the received multicast resource information sent by the source base station.

In some embodiments, the multicast resource information comprises a multicast service join indication.

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.

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

the sending module is specifically configured to send the first information when the multicast resource information includes information of part of already joined multicast services.

In a fourth aspect, an embodiment of the present application provides an apparatus for implementing a multicast service, where the apparatus includes:

a first sending module, configured to send multicast resource information to a terminal through a source base station;

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

and the second sending module is used for sending the first information to a core network function.

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

In some embodiments, the receiving module is further configured to receive a handover confirmation message sent by the terminal, where the first information is included in the handover confirmation message.

In some embodiments, the second sending module is further configured to send a handover complete message to the core network function, where the first information is included in the handover complete message.

In some embodiments, the multicast resource information comprises a multicast service join indication; and/or

The multicast resource information includes multicast service information.

In a fifth aspect, embodiments of the present application further provide an electronic device, which includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor, and when executed by the processor, the program or instructions implement the steps of the method described above.

In a sixth aspect, the present application provides a readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the method as described above.

In a seventh aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the method according to the first aspect or the second aspect.

In the embodiment of the application, if switching occurs when the terminal receives the multicast service data, the terminal sends the first information for joining the multicast service to the target base station, and after receiving the first information, the target base station can send the first information to the core network function to support sending of the multicast service data, so that the terminal joins the multicast service in the target base station.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments of the present application will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive exercise.

FIG. 1 shows a schematic diagram of a wireless communication system;

fig. 2 is a flowchart illustrating a method for implementing a multicast service on a terminal side according to an embodiment of the present application;

fig. 3 is a flowchart illustrating a method for implementing a multicast service on a target base station side according to an embodiment of the present application;

fig. 4 and fig. 5 are schematic flow charts illustrating a method for implementing a multicast service according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a multicast service implementing apparatus on a terminal side according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a multicast service implementing apparatus on a target base station side according to an embodiment of the present application;

fig. 8 is a schematic diagram showing the composition of a terminal according to an embodiment of the present application;

fig. 9 is a schematic diagram illustrating a configuration of a network device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

The techniques described herein are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, and may 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. CDMA systems may implement Radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and so on. UTRA includes Wideband CDMA (Wideband Code Division Multiple Access, WCDMA) and other CDMA variants. TDMA systems may implement radio technologies such as Global System for Mobile communications (GSM). The OFDMA system may implement radio technologies such as Ultra Mobile Broadband (UMB), evolved-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 the Universal Mobile Telecommunications System (UMTS). LTE and higher LTE (e.g., LTE-A) are new UMTS releases that use E-UTRA. UTRA, E-UTRA, UMTS, LTE-A, and GSM are described in documents from an organization named "third Generation Partnership Project" (3 GPP). CDMA2000 and UMB are described in documents from an organization named "third generation partnership project 2" (3GPP 2). The techniques described herein may be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes the NR system for purposes of example, and NR terminology is used in much of the description below, although the techniques may also be applied to applications other than NR system applications.

The following description provides examples and does not limit the scope, applicability, or configuration set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the spirit and scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the described methods may be performed in an order different than 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.

Referring to fig. 1, fig. 1 is a block diagram of a wireless communication system to which an embodiment of the present application is applicable. 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 Equipment (UE), where the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer), a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), a Wearable Device (Wearable Device), or a vehicle-mounted Device, and the specific type of the terminal 11 is not limited in this embodiment. The network-side device 12 may be a Base Station or a core network, wherein the Base Station may be a 5G or later-version Base Station (e.g., a gNB, a 5G NR NB, etc.), or a Base Station in other communication systems (e.g., an eNB, a WLAN access point, or other access points, etc.), or a location server (e.g., an E-SMLC or an lmf (location Manager function)), wherein the Base Station may be referred to as a node B, an evolved node B, an access point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a home evolved node B, a WLAN access point, a WiFi node, or some other suitable terminology in the field, as long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary, and 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.

An embodiment of the present application provides a method for implementing a multicast service, which is applied to a terminal, and as shown in fig. 2, the method includes:

step 101: and after receiving a first switching command of a source base station, sending first information to a target base station, wherein the first information is used for joining in the multicast service.

In this embodiment, if the terminal switches when receiving the multicast service data, the terminal sends the first information for joining the multicast service to the target base station, and after receiving the first information, the target base station may send the first information to the core network function, so as to support sending of the multicast service data, thereby enabling the terminal to join the multicast service in the target base station.

The first handover command may carry multicast air interface resource information, such as including a multicast identifier.

When the terminal accesses the target base station, it needs to send a Handover confirmation message, such as a Handover Confirm message, and also needs to send first information used to activate or establish a Protocol Data Unit (PDU) session related to the multicast service to the target base station, where 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 is aware of the multicast service information.

Since a core network Function CN NF (such as an Access and Mobility Management Function (AMF)) is required to reserve core network resources of the multicast-related PDU session based on the first information, the sending the first information to the target base station further includes:

and sending the first information to a core network function through the target base station.

Because when the terminal accesses the target base station, the handover confirmation message needs to be sent to the target base station, in order to save signaling overhead, sending the first information to the target base station includes: and sending a handover confirmation message to the target base station, wherein the handover confirmation message carries the first information, namely the first information is contained in the handover confirmation message.

In some embodiments, sending the first information comprises any one of:

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

In some embodiments, the multicast resource information may include a multicast service join indication.

In some embodiments of the present invention, the first and second,

one or more multicast services have been joined before the receiving of the first handover command of the source base station;

the terminal may send the first information when the multicast resource information includes information of part of already joined multicast services.

An embodiment of the present application provides a method for implementing a multicast service, which is applied to a target base station, and as shown in fig. 3, the method includes:

step 201: the target base station sends multicast resource information to the terminal through the source base station;

step 202: a target base station receives first information sent by the terminal, wherein the first information is used for joining in a multicast service;

step 203: and the target base station sends the first information to a core network function.

In some embodiments, the method further comprises:

and receiving a switching confirmation message sent by the terminal, wherein the first information is contained in the switching confirmation message. Since the handover 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, the first information may be included in the handover confirmation message.

In some embodiments, the method further comprises:

and sending a switching completion message to the core network function, wherein the first information is contained in the switching completion message.

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

The multicast resource information includes multicast service information.

In a specific example, as shown in fig. 4, the core network Function (CN NF) includes an AMF, a Session Management Function entity (SMF)/a core network User Plane Function entity (User Plane Function, UPF), and a Multicast (MB) -SMF/MB-UPF, and first the core network Function sends multicast data through a shared channel between the core network Function and a Source base station, the Source base station (Source gNB) distributes the multicast data to a terminal in a broadcast manner or a point-to-point manner, and the terminal has other PDU sessions in an active state (i.e., the terminal is in a connected state) at the same time, and the PDU sessions are unrelated to the multicast service.

The method for realizing the multicast service of the embodiment comprises the following steps:

step 1: the Source gNB decides to execute a Handover operation, selects a target gNB, and sends a Handover notification message, such as a Handover Required message, to the core network;

the Source gNB may select the target base station based on the measurement report or the candidate cell information, or may autonomously select the target base station.

Step 2: the CN NF sends a Handover Request to the target gbb, for example, sends a Handover Request message, which carries information in the Handover notification message, and may further include multicast service information, for example, a multicast service identifier, and quality of service (QoS) information related to the multicast service identifier;

and step 3: reserving air interface resources for the target base station, and reserving the air interface resources for the multicast service except for reserving the air interface resources for the PDU session;

and 4, step 4: the target base station returns a switching Response, such as a Handover Response message, to the CN NF, and may carry the air interface resource information obtained in step 3;

and 5: the CN NF sends a switching Command, such as a Handover Command message, to the source base station, and carries the received downlink forwarding and receiving resource information or the core network forwarding resource information;

step 6: the source base station sends a switching command to the UE, which may carry multicast air interface resource information, such as including a multicast identifier;

and 7: the UE accesses to a target base station, sends a switching confirmation message, such as a Handover Confirm message, to the target base station, and sends an NAS message to a core network function through the target base station for activating or establishing a PDU Session related to a multicast Service, wherein the NAS message can be a Service Request or a PDU Session Establishment Request message, and the NAS message can be contained in an NAS container of the switching confirmation message;

the UE may determine whether to send the NAS message based on whether the multicast resource information is received or not, or based on the received multicast resource information, for example, when the multicast resource information is not received or when the multicast resource information does not include all multicast service related resource information, the UE sends the NAS message.

And 8: the target base station forwards the NAS message and the handover complete message (request of N2) to the core network function, where the NAS message may be included in the NAS container of the handover complete message;

and 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, can update the multicast unrelated PDU session resources at the same time, and can also wait for the multicast related PDU session to be established or update the multicast unrelated PDU session resources after the activation is completed;

step 10: the core network function sends the resource information of the multicast related PDU session core network to the target base station, and the resource information of the multicast related PDU session core network can be contained in the N2 response;

step 11: the target base station interacts with the UE through an air interface based on the resource information of the multicast related PDU session core network, and reserves the air interface resource of the multicast related PDU session;

step 12: the target base station sends the resource information of the multicast related PDU session base station to the core network function, and the resource information of the multicast related PDU session base station can be carried in the N2 request;

step 13: the core network function uses the multicast related PDU session base station resource information to update the multicast related PDU session;

step 14: in step 7, under the condition that the UE does not carry the NAS message in the switching 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;

step 15: after the establishment or activation of the multicast related PDU session is completed, the core network function updates the multicast unrelated PDU session resources.

The core network function may then also establish a multicast-independent PDU session with the target base station.

In another specific example, as shown in fig. 5, the core network Function includes an AMF, a Session Management Function entity (SMF)/a core network User Plane Function entity (User Plane Function, UPF), and an MB-SMF/MB-UPF, where the core network Function first sends multicast data through a shared channel between the core network Function and a Source base station, the Source base station (Source gNB) distributes the multicast data to a terminal in a broadcast manner or a point-to-point manner, and other PDU sessions of the terminal are in an active state (i.e., the terminal is in a connected state) at the same time, and the PDU sessions are unrelated to the multicast service.

step 1, Source gNB decides to execute 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, where the Handover Request message may include multicast service information, such as a multicast service identifier, and QoS information related to the multicast service identifier;

Step 2: reserving air interface resources for the target base station, and reserving the air interface resources for the multicast service except for reserving the air interface resources for the PDU session;

and step 3: the target base station returns a switching Response to the source base station, for example, returns a Handover Response message carrying the air interface resource information;

and 4, step 4: the source base station sends a switching command to the UE, which may carry multicast air interface resource information, such as including a multicast identifier;

and 5: the UE accesses to a target base station, sends a switching confirmation message, such as a Handover Confirm message, to the target base station, and sends an NAS message to a core network function through the target base station for activating or establishing a PDU Session related to a multicast Service, wherein the NAS message can be a Service Request or a PDU Session Establishment Request message, and the NAS message can be contained in an NAS container of the switching confirmation message;

Step 6: the target base station forwards the NAS message and the N2 request to the core network function, wherein the NAS message can be contained in the NAS container requested by the N2;

and 7: the core network function (such as AMF) reserves the core network resources of the multicast related PDU session based on the NAS message, can update the multicast unrelated PDU session resources at the same time, and can also wait for the multicast related PDU session to be established or update the multicast unrelated PDU session resources after the activation is completed;

and 8: the core network function sends an N2 response to the target base station, wherein the response carries the resource information of the multicast related PDU session core network;

and step 9: the target base station interacts with the UE through an air interface based on the resource information of the multicast related PDU session core network, and reserves the air interface resource of the multicast related PDU session;

step 10: the target base station sends an N2 request to the core network function, wherein the request carries the resource information of the multicast related PDU session base station;

step 11: the core network function uses the multicast related PDU session base station resource information to update the multicast related PDU session;

step 12: under the condition that the UE does not carry the NAS message in the switching 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;

step 13: after the establishment or activation of the multicast related PDU session is completed, the core network function updates the multicast unrelated PDU session resources.

It should be noted that, in the multicast service implementation method provided in this embodiment of the present application, the execution main body may be a multicast service implementation device, or a module in the multicast service implementation device, configured to execute the method for implementing loading of the multicast service. In the embodiment of the present application, a method for implementing a multicast service by a multicast service implementation device to execute a load multicast service is taken as an example to describe the method for implementing a multicast service provided in the embodiment of the present application.

An embodiment of the present application provides a multicast service implementing apparatus, which is applied to a terminal 300, and as shown in fig. 6, the apparatus includes:

a sending module 310, configured to send first information to a target base station after receiving a first handover command of a source base station, where the first information is used to join a multicast service.

The multicast service implementing device in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device can be mobile electronic equipment or non-mobile electronic equipment. By way of example, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palm top computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a Personal Digital Assistant (PDA), and the like, and the non-mobile electronic device may be a Network Attached Storage (NAS), a personal computer (personal computer, PC), a Television (TV), a teller machine, a self-service machine, and the like, and the embodiments of the present application are not limited in particular.

The multicast service implementing device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.

An embodiment of the present application provides a multicast service implementing apparatus, which is applied to a target base station 400, and as shown in fig. 7, the apparatus includes:

a first sending module 410, configured to send multicast resource information to a terminal through a source base station;

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

a second sending module 430, configured to send the first information to a core network function.

In some embodiments, the receiving module 420 is further configured to receive a handover confirmation message sent by the terminal, where the first information is included in the handover confirmation message.

In some embodiments, the second sending module 430 is further configured to send a handover complete message to the core network function, where the first information is included in the handover complete message.

The multicast resource information includes multicast service information.

The multicast service implementation device in the embodiment of the present application may be a mobile electronic device or a non-mobile electronic device. By way of example, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palm top computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a Personal Digital Assistant (PDA), and the like, and the non-mobile electronic device may be a Network Attached Storage (NAS), a personal computer (personal computer, PC), a Television (TV), a teller machine, a self-service machine, and the like, and the embodiments of the present application are not limited in particular.

Optionally, an embodiment of the present application further provides an electronic device, which includes a processor, a memory, and a program or an instruction stored in the memory and capable of running on the processor, where the program or the instruction is executed by the processor to implement each process of the above-mentioned embodiment of the method for implementing an acquisition or multicast service, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.

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

The electronic device of the embodiment may be a terminal. Fig. 8 is a schematic hardware structure diagram of a terminal for implementing various embodiments of the present application, where 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 will appreciate that the terminal configuration shown in fig. 8 is not intended to be limiting, and that the terminal may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. In the embodiment of the present application, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.

It should be understood that, in the embodiment of the present application, the radio frequency unit 51 may be used for receiving and sending signals during a message sending and receiving process or a call process, and specifically, receives downlink data from a base station and then processes the received downlink data to the processor 510; in addition, the uplink data is transmitted to the base station. Typically, 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, and the like. In addition, the radio frequency unit 51 may also communicate with a network and other devices through a wireless communication system.

The memory 59 may be used to store software programs as well as various data. The memory 59 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 59 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 510 is a control center of the terminal, connects various parts of the entire terminal using various interfaces and lines, performs various functions of the terminal and processes data by operating or executing software programs and/or modules stored in the memory 59 and calling data stored in the memory 59, thereby performing overall monitoring of the terminal. Processor 510 may include one or more processing units; preferably, the processor 510 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 510.

The terminal 50 may further include a power supply 511 (e.g., a battery) for supplying power to various components, and preferably, the power supply 511 may be logically connected to the processor 510 via a power management system, so that functions of managing charging, discharging, and power consumption are performed via the power management system.

In addition, the terminal 50 includes some functional modules that are not shown, and will not be described in detail herein.

The electronic device of this embodiment may also be a network side device, such as a target base station. As shown in fig. 9, the network-side device 600 includes: antenna 61, radio frequency device 62, baseband device 63. The antenna 61 is connected to a radio frequency device 62. In the uplink direction, the rf device 62 receives information via the antenna 61 and sends the received information to the baseband device 63 for processing. In the downlink direction, the baseband device 63 processes information to be transmitted and transmits the information to the radio frequency device 62, and the radio frequency device 62 processes the received information and transmits the processed information through the antenna 61.

The above-mentioned band processing means may be located in the baseband means 63, and the method performed by the network side device in the above embodiment may be implemented in the baseband means 63, where the baseband means 63 includes a processor 64 and a memory 65.

The baseband device 63 may include at least one baseband board, for example, and a plurality of chips are disposed on the baseband board, as shown in fig. 9, wherein one chip, for example, the processor 64, is connected to the memory 65 to call up the program in the memory 65 to perform the network side device operation shown in the above method embodiment.

The baseband device 63 may further include a network interface 66 for exchanging information with the radio frequency device 62, such as a Common Public Radio Interface (CPRI).

The processor may be a single processor or a combination of multiple processing elements, for example, the processor may be a CPU, an ASIC, or one or more integrated circuits configured to implement the method performed by the above network-side device, for example: one or more microprocessors DSP, or one or more field programmable gate arrays FPGA, or the like. The storage element may be a memory or a combination of a plurality of storage elements.

The memory 65 may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a Read-only memory (ROM), a programmable Read-only memory (PROM), an erasable programmable Read-only memory (erasabprom, EPROM), an electrically erasable programmable Read-only memory (EEPROM), or a flash memory. The volatile memory may be a Random Access Memory (RAM) which functions as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (staticiram, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (syncronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), enhanced synchronous dynamic random access memory (EnhancedSDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM), and direct memory bus random access memory (DRRAM). The memory 65 described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the embodiment of the method for implementing an acquisition or multicast service, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement each process of the above embodiment of the method for implementing an acquisition or multicast service, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include those elements, but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than 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.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A method for implementing multicast service is characterized by comprising the following steps:

2. The method of claim 1,

the first information includes multicast service information.

3. The method of claim 1, wherein the sending the first information to the target base station further comprises:

4. The method of claim 1, wherein sending the first information to the target base station comprises:

and sending a switching confirmation message to the target base station, wherein the switching confirmation message carries the first information.

5. The method of claim 1,

the first information is used to establish or activate a protocol data unit, PDU, session.

6. The method of claim 1, wherein sending the first information comprises any one of:

7. The method of claim 6,

the multicast resource information comprises a multicast service joining indication.

8. The method of claim 6, wherein the sending the first information according to the received multicast resource information sent by the source base station comprises:

and when the multicast resource information does not contain multicast service information, sending the first information.

9. The method of claim 6,

the sending the first information according to the received multicast resource information sent by the source base station includes:

and when the multicast resource information contains the information of part of the joined multicast services, sending the first information.

10. A method for implementing multicast service is characterized by comprising the following steps:

11. The method of claim 10,

the first information includes multicast service information.

12. The method of claim 10,

the first information is used to activate or establish a protocol data unit, PDU, session.

13. The method for implementing multicast service according to claim 10, further comprising:

and receiving a switching confirmation message sent by the terminal, wherein the first information is contained in the switching confirmation message.

14. The method for implementing multicast service according to claim 10, further comprising:

15. The method of claim 10,

the multicast resource information comprises multicast service joining indication; and/or

The multicast resource information includes multicast service information.

16. An apparatus for implementing a multicast service, comprising:

17. The apparatus of claim 16, wherein the sending module is further configured to send the first information to a core network function through the target base station.

18. The apparatus of claim 16, wherein the sending module is specifically configured to perform any one of the following:

19. An apparatus for implementing a multicast service, comprising:

20. The multicast service implementing device according to claim 19,

the receiving module is further configured to receive a handover confirmation message sent by the terminal, where the first information is included in the handover confirmation message.

21. An electronic device comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps of the method of any one of claims 1-15.

22. A readable storage medium, characterized in that it stores thereon a program or instructions which, when executed by a processor, implement the steps of the method according to any one of claims 1-15.