WO2021051320A1

WO2021051320A1 - Service data transmission method and apparatus, network device, and terminal device

Info

Publication number: WO2021051320A1
Application number: PCT/CN2019/106509
Authority: WO
Inventors: 王淑坤; 杨宁
Original assignee: Oppo广东移动通信有限公司
Priority date: 2019-09-18
Filing date: 2019-09-18
Publication date: 2021-03-25
Also published as: CN113661722A; CN113661722B

Abstract

Embodiments of the present application provide a service data transmission method and apparatus, a network device, and a terminal device. The method comprises: a first cell receiving first indication information, wherein the first indication information is used to indicate that a terminal device needs to receive a multimedia broadcast multicast service (MBMS) service; and the fist cell determining that a second cell supports transmission of the MBMS service, and providing the MBMS service to the terminal device via the second cell.

Description

A business data transmission method and device, network equipment, and terminal equipment

Technical field

The embodiments of the present application relate to the field of mobile communication technology, and in particular to a method and device for transmitting service data, network equipment, and terminal equipment.

Background technique

Multimedia Broadcast Multicast Service (MBMS) is a technology that transmits data from one data source to multiple users by sharing network resources. This technology can effectively use network resources while providing multimedia services to achieve better performance. Broadcast and multicast of high-rate (such as 256kbps) multimedia services.

In the New Radio (NR) system, many scenarios need to support the service requirements of multicast and broadcast, such as the Internet of Vehicles and the Industrial Internet. So it is necessary to introduce MBMS in NR. For the MBMS service in NR, when the terminal device changes in the cell, the target cell may not support the transmission of the MBMS service, and the terminal device has a demand for receiving the MBMS service, which will cause the interruption of the MBMS service.

Summary of the invention

The embodiments of the present application provide a method and device for transmitting service data, network equipment, and terminal equipment.

The service data transmission method provided by the embodiment of the application includes:

The first cell receives first indication information, where the first indication information is used to indicate that the terminal device needs to receive the MBMS service;

The first cell determines that the second cell supports sending the MBMS service, and provides the MBMS service for the terminal device through the second cell.

The terminal device sends first indication information to the first cell, where the first indication information is used to indicate that the terminal device needs to receive the MBMS service;

The terminal device receives the MBMS service provided by a second cell, where the second cell is a cell determined by the first cell to support sending the MBMS service.

The service data transmission device provided by the embodiment of the application includes:

A receiving unit, configured to receive first indication information, where the first indication information is used to indicate that the terminal device needs to receive an MBMS service;

The determining unit is configured to determine that the second cell supports sending the MBMS service, and provide the MBMS service for the terminal device through the second cell.

A sending unit, configured to send first indication information to the first cell, where the first indication information is used to indicate that the terminal device needs to receive the MBMS service;

The receiving unit is configured to receive the MBMS service provided by the second cell, where the second cell is a cell determined by the first cell to support sending the MBMS service.

The network device provided by the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned business data transmission method.

The terminal device provided in the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the foregoing business data transmission method.

The chip provided in the embodiment of the present application is used to implement the foregoing service data transmission method.

Specifically, the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above-mentioned service data transmission method.

The computer-readable storage medium provided by the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute the above-mentioned service data transmission method.

The computer program product provided by the embodiment of the present application includes computer program instructions that cause a computer to execute the above-mentioned service data transmission method.

The computer program provided in the embodiment of the present application, when it runs on a computer, causes the computer to execute the above-mentioned service data transmission method.

Through the above technical solutions, the NR system supports broadcast and multicast of MBMS services. At the same time, on the one hand, a dual-connection-based mechanism is proposed to provide MBMS services to terminal devices through secondary cells; on the other hand, a mechanism for forwarding between the network sides is proposed, that is, cells that do not support MBMS service transmission use dedicated messages. Make the MBMS service from the cell that supports MBMS service transmission be forwarded to the terminal device. In this way, based on the dual-connection architecture or the forwarding mechanism between the network sides, the terminal device can still be able to change to a cell without MBMS service transmission. To achieve continuous reception of MBMS services.

Description of the drawings

The drawings described here are used to provide a further understanding of the application and constitute a part of the application. The exemplary embodiments and descriptions of the application are used to explain the application, and do not constitute an improper limitation of the application. In the attached picture:

FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of a first SIB related configuration provided by an embodiment of the present application;

Fig. 3 is a schematic diagram of a PTM configuration transmission mechanism provided by an embodiment of the present application;

Fig. 4 is a PTM channel and its mapping diagram provided by an embodiment of the present application;

FIG. 5 is a schematic flowchart of a service data transmission method provided by an embodiment of the present application;

FIG. 6 is a schematic diagram 1 of the structural composition of a service data transmission device provided by an embodiment of the present application;

FIG. 7 is a second schematic diagram of the structural composition of a service data transmission device provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a chip of an embodiment of the present application;

FIG. 10 is a schematic block diagram of a communication system provided by an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (Time Division Duplex) , TDD), system, 5G communication system or future communication system.

Exemplarily, the communication system 100 applied in the embodiment of this application is shown in FIG. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or called a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminals located in the coverage area. Optionally, the network device 110 may be an evolved base station (Evolutional Node B, eNB, or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or The network equipment can be a mobile switching center, a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network side device in a 5G network, or a network device in a future communication system, etc.

The communication system 100 also includes at least one terminal 120 located within the coverage area of the network device 110. The "terminal" used here includes, but is not limited to, connection via a wired line, such as via a public switched telephone network (PSTN), digital subscriber line (Digital Subscriber Line, DSL), digital cable, and direct cable connection; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM Broadcast transmitter; and/or another terminal's device configured to receive/send communication signals; and/or Internet of Things (IoT) equipment. A terminal set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a "wireless terminal" or a "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio telephone transceivers Electronic device. Terminal can refer to access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user Device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks, or terminals in the future evolution of PLMN, etc.

Optionally, direct terminal connection (Device to Device, D2D) communication may be performed between the terminals 120.

Optionally, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.

FIG. 1 exemplarily shows one network device and two terminals. Optionally, the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminals. This embodiment of the present application There is no restriction on this.

Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.

It should be understood that the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 and a terminal 120 with communication functions, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here; communication The device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.

It should be understood that the terms "system" and "network" in this article are often used interchangeably in this article. The term "and/or" in this article is only an association relationship describing the associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, exist alone B these three situations. In addition, the character "/" in this text generally indicates that the associated objects before and after are in an "or" relationship.

In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the technical solutions related to the embodiments of the present application are described below.

As people speed, latency, high-speed mobility, energy efficiency and the future of life in the pursuit of the business of diversity, complexity, for the third Generation Partnership Project ^{(3 rd Generation Partnership Project, 3GPP} ) ISO began the development of 5G . The main application scenarios of 5G are: Enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), Massive Machine-Type Communications (mMTC) ).

On the one hand, eMBB is still targeting users to obtain multimedia content, services and data, and its demand is growing very rapidly. On the other hand, because eMBB may be deployed in different scenarios, such as indoors, urban areas, rural areas, etc., its capabilities and requirements are also quite different, so it cannot be generalized and must be analyzed in detail in conjunction with specific deployment scenarios. Typical applications of URLLC include: industrial automation, power automation, telemedicine operations (surgery), traffic safety protection, etc. The typical characteristics of mMTC include: high connection density, small data volume, delay-insensitive services, low cost and long service life of the module.

In the early deployment of NR, complete NR coverage is difficult to obtain, so the typical network coverage is wide area LTE coverage and NR island coverage mode. Moreover, a large amount of LTE is deployed below 6GHz, and there are few sub-6GHz spectrums available for 5G. So NR must study the frequency spectrum application above 6GHz, and the high frequency band has limited coverage and fast signal fading. At the same time, in order to protect mobile operators' early investment in LTE, a tight interworking mode between LTE and NR is proposed.

In order to achieve 5G network deployment and commercial applications as soon as possible, 3GPP first completed the first 5G version, EN-DC (LTE-NR Dual Connectivity). In EN-DC, an LTE base station (eNB) serves as a master node (Master Node, MN), and an NR base station (gNB or en-gNB) serves as a secondary node (Secondary Node, SN). In the later stage of R15, other DC modes will be supported, namely NE-DC, 5GC-EN-DC, and NR DC. For EN-DC, the core network connected to the access network is EPC, while the core network connected to other DC modes is 5GC.

The technical solution of the embodiment of the present application proposes a dual-connectivity (DC) enhanced architecture, that is, a multiple-connectivity (Multiple Connectivity, MC) architecture. Typically, the MC architecture may be an MR-MC architecture.

RRC status

In order to reduce air interface signaling, quickly restore wireless connections, and quickly restore data services, 5G defines a new radio resource control (Radio Resource Control, RRC) state, that is, the RRC inactive (RRC_INACTIVE) state. This state is different from the RRC idle (RRC_IDLE) state and the RRC active (RRC_ACTIVE) state. among them,

1) RRC_IDLE state (abbreviated as idle state): mobility is UE-based cell selection and reselection, paging is initiated by the Core Network (Core Network, CN), and the paging area is configured by the CN. There is no UE context on the base station side, and no RRC connection.

2) RRC_CONNECTED state (referred to as connected state for short): There is an RRC connection, and UE context exists on the base station side and the UE side. The network side knows that the location of the UE is of a specific cell level. Mobility is the mobility controlled by the network side. Unicast data can be transmitted between the UE and the base station.

3) RRC_INACTIVE state (referred to as inactive state for short): Mobility is UE-based cell selection and reselection, there is a connection between CN-NR, UE context is stored on a certain base station, and paging is triggered by RAN, based on The paging area of the RAN is managed by the RAN, and the network side knows that the location of the UE is based on the paging area level of the RAN.

MBMS

MBMS was introduced in 3GPP Release 6 (Release 6, R6). MBMS is a technology that transmits data from one data source to multiple UEs by sharing network resources. This technology can effectively utilize network resources while providing multimedia services. Realize the broadcast and multicast of multimedia services at a higher rate (such as 256kbps).

Due to the low spectrum efficiency of MBMS in 3GPP R6, it is not enough to effectively carry and support the operation of mobile TV-type services. Therefore, in LTE, 3GPP clearly proposed to enhance the ability to support downlink high-speed MBMS services, and determined the design requirements for the physical layer and air interface.

3GPP R9 introduced evolved MBMS (evolved MBMS, eMBMS) into LTE. eMBMS proposes the concept of Single Frequency Network (SFN), namely Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN), MBSFN uses a unified frequency to send service data in all cells at the same time, but To ensure synchronization between the cells. This method can greatly improve the overall signal-to-noise ratio distribution of the cell, and the spectrum efficiency will be greatly improved accordingly. eMBMS realizes the broadcast and multicast of services based on the IP multicast protocol.

In LTE or enhanced LTE (LTE-Advanced, LTE-A), MBMS has only a broadcast bearer mode, and no multicast bearer mode. In addition, the reception of MBMS services is suitable for UEs in idle state or connected state.

3GPP R13 introduced the single cell point to multipoint (Single Cell Point To Multiploint, SC-PTM) concept, and SC-PTM is based on the MBMS network architecture.

MBMS introduces new logical channels, including Single Cell-Multicast Control Channel (SC-MCCH) and Single Cell-Multicast Transport Channel (SC-MTCH). SC-MCCH and SC-MTCH are mapped to downlink shared channel (Downlink-Shared Channel, DL-SCH), and further, DL-SCH is mapped to physical downlink shared channel (Physical Downlink Shared Channel, PDSCH), where SC -MCCH and SC-MTCH belong to logical channels, DL-SCH belongs to transport channels, and PDSCH belongs to physical channels. SC-MCCH and SC-MTCH do not support Hybrid Automatic Repeat reQuest (HARQ) operations.

MBMS introduces a new system information block (System Information Block, SIB) type, namely SIB20. Specifically, the SC-MCCH configuration information is transmitted through SIB20, and there is only one SC-MCCH in a cell. The configuration information of the SC-MCCH includes: the modification period of the SC-MCCH, the repetition period of the SC-MCCH, and information such as radio frames and subframes for scheduling the SC-MCCH. Further, 1) the boundary of the modification period of the SC-MCCH satisfies SFN mod m=0, where SFN represents the system frame number of the boundary, and m is the modification period of the SC-MCCH configured in the SIB20 (ie, sc-mcch-ModificationPeriod). 2) The radio frame scheduling SC-MCCH satisfies: SFN mod mcch-RepetitionPeriod=mcch-Offset, where SFN represents the system frame number of the radio frame, mcch-RepetitionPeriod represents the repetition period of SC-MCCH, and mcch-Offset represents SC-MCCH The offset. 3) The subframe for scheduling SC-MCCH is indicated by sc-mcch-Subframe.

The SC-MCCH is scheduled through the Physical Downlink Control Channel (PDCCH). On the one hand, a new radio network temporary identity (Radio Network Tempory Identity, RNTI), namely single cell RNTI (Single Cell RNTI, SC-RNTI) is introduced to identify the PDCCH (such as SC-MCCH PDCCH) used to schedule SC-MCCH, Optionally, the fixed value of SC-RNTI is FFFC. On the other hand, a new RNTI is introduced, namely Single Cell Notification RNTI (SC-N-RNTI) to identify the PDCCH used to indicate the change notification of the SC-MCCH (such as the notification PDCCH). Optionally, the SC -N-RNTI has a fixed value of FFFB; further, one of the 8 bits of DCI 1C can be used to indicate the change notification. In LTE, the configuration information of the SC-PTM is based on the SC-MCCH configured by the SIB20, and then the SC-MCCH is configured with the SC-MTCH, and the SC-MTCH is used to transmit service data.

Specifically, the SC-MCCH only transmits one message (that is, SCPTMConfiguration), which is used to configure the configuration information of the SC-PTM. The configuration information of SC-PTM includes: Temporary Mobile Group Identity (TMGI), session identifier (seession id), group RNTI (Group RNTI, G-RNTI), discontinuous reception (Discontinuous Reception, DRX) configuration information And the SC-PTM business information of the neighboring cell, etc. It should be noted that the SC-PTM in R13 does not support Robust Header Compression (ROHC) function.

The downlink discontinuous reception of SC-PTM is controlled by the following parameters: onDurationTimerSCPTM, drx-InactivityTimerSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.

When [(SFN*10)+subframe number]modulo(SC-MTCH-SchedulingCycle)=SC-MTCH-SchedulingOffset is satisfied, start the timer onDurationTimerSCPTM;

When receiving the downlink PDCCH scheduling, start the timer drx-InactivityTimerSCPTM;

Only when the timer onDurationTimerSCPTM or drx-InactivityTimerSCPTM is running, the downlink SC-PTM service is received.

SC-PTM service continuity adopts the concept of MBMS service continuity based on SIB15, namely "SIB15+MBMSInterestIndication" mode. The service continuity of the UE in the idle state is based on the concept of frequency priority.

In NR, many scenarios need to support the service requirements of multicast and broadcast, such as the Internet of Vehicles and the Industrial Internet. So it is necessary to introduce MBMS in NR. For one scenario, the UE performs cell reselection to a target cell in an idle state or in an inactive state, and the target cell does not support the transmission of MBMS services, for example, an LTE cell or an NR cell does not send MBMS service data. At this time, the UE enters the connected state and is configured with MR-DC. The secondary cell in the MR-DC (ie, the cell corresponding to the SN) supports the transmission of MBMS services, and the UE needs to receive the MBMS services. For another scenario, the UE switches from a cell that supports MBMS service transmission to a cell that does not support MBMS service transmission in the connected state. At this time, the configured secondary cell supports MBMS service transmission, and the UE has received MBMS service transmission. Business needs. In order to meet the continuity of UE service reception in the above scenario, the MBMS service that the UE is interested in can be received through the secondary cell. To this end, the following technical solutions of the embodiments of the present application are proposed.

In the technical solution of the embodiment of this application, a new SIB (called the first SIB) is defined. Referring to FIG. 2, the first SIB includes the configuration information of the first MCCH. Here, the first MCCH is the control channel of the MBMS service. In other words, the first SIB is used to configure the configuration information of the control channel of NR MBMS. Optionally, the control channel of NR MBMS may also be called NR MCCH (that is, the first MCCH).

Further, the first MCCH is used to carry the first signaling. The embodiment of this application does not limit the name of the first signaling. For example, the first signaling is signaling A, and the first signaling includes at least one first MTCH. Here, the first MTCH is a service channel of the MBMS service (also referred to as a data channel or a transmission channel), and the first MTCH is used to transmit MBMS service data (such as NR MBMS service data). In other words, the first MCCH is used to configure the configuration information of the NR MBMS traffic channel. Optionally, the NR MBMS traffic channel may also be called NR MTCH (that is, the first MTCH).

Specifically, the first signaling is used to configure a NR MBMS service channel, service information corresponding to the service channel, and scheduling information corresponding to the service channel. Further, optionally, the service information corresponding to the service channel, for example, TMGI, session id, and other identification information identifying the service. The scheduling information corresponding to the traffic channel, for example, the RNTI used when the MBMS service data corresponding to the traffic channel is scheduled, such as G-RNTI, DRX configuration information, etc.

It should be noted that the transmission of the first MCCH and the first MTCH is scheduled based on the PDCCH. Wherein, the RNTI used for scheduling the PDCCH of the first MCCH uses a unique identifier of the entire network, that is, a fixed value. The RNTI used by the PDCCH for scheduling the first MTCH is configured through the first MCCH.

It should be noted that the embodiment of the present application does not impose restrictions on the naming of the first SIB, the first MCCH, and the first MTCH. For ease of description, the first SIB may also be abbreviated as SIB, the first MCCH may also be abbreviated as MCCH, and the first MTCH may also be abbreviated as MTCH. Referring to FIG. 3, the PDCCH used to schedule the MCCH is configured through the SIB. (Ie MCCH PDCCH) and notification PDCCH, wherein the DCI carried by MCCH PDCCH is used to schedule the PDSCH (ie MCCH PDSCH) used to transmit the MCCH. Further, M PDCCHs (that is, MTCH 1PDCCH, MTCH 2PDCCH, ..., MTCH M PDCCH) for scheduling MTCH are configured through MCCH, where DCI carried by MTCH n PDCCH schedules PDSCH for transmitting MTCH n (ie MTCH n PDSCH) , N is an integer greater than or equal to 1 and less than or equal to M. 4, MCCH and MTCH are mapped to DL-SCH, and further, DL-SCH is mapped to PDSCH, where MCCH and MTCH belong to logical channels, DL-SCH belongs to transport channels, and PDSCH belongs to physical channels.

FIG. 5 is a schematic flowchart of a service data transmission method provided by an embodiment of the application. As shown in FIG. 5, the service data transmission method includes the following steps:

Step 501: The terminal device sends first indication information, and the first cell receives the first indication information, where the first indication information is used to indicate that the terminal device needs to receive the MBMS service.

In the embodiment of the present application, the first cell is a target cell for the terminal device to perform cell change, and the first cell does not support sending the MBMS service. Further, the cell change refers to cell reselection or cell handover.

In the embodiment of the present application, when the target cell where the terminal device performs cell change does not support sending the MBMS service, the terminal device sends first indication information, and the first indication information is used to indicate that the terminal device needs to receive MBMS business. Here, the terminal device may send the first indication information to the first cell, or the terminal device may send the first indication information to the third cell, and the third cell forwards the first indication information To the first cell. In an optional implementation manner, the first indication information carries configuration information of the MBMS service. Here, the configuration information of the MBMS service includes at least one of the following: frequency information of the MBMS service, identification information of the MBMS service (such as TMGI, session id), G-RNTI, and identification information of the last served cell.

In an optional implementation manner of the present application, the MBMS service is a service that needs to be received after the terminal device performs a cell change.

In an optional implementation manner of the present application, the MBMS service is a service that is ongoing before the terminal device performs cell change. Further, the MBMS service is a service that is ongoing on a third cell before the terminal device performs the cell change, and the third cell is the original cell where the terminal device performs the cell change.

In the embodiment of the present application, the first cell receiving the first indication information may determine whether it supports sending the MBMS service based on the configuration information of the MBMS service carried in the first indication information.

In an optional implementation manner of the present application, a terminal device in an idle state or in an inactive state or an active state sends first indication information to the first cell, so that the first cell receives the first indication information sent by the terminal device . In another optional implementation manner of the present application, the terminal device in the active state (through dedicated signaling) sends the first indication information to the third cell, and the third cell (through the handover request message) sends the first indication information to The first cell, and thus the first cell, receives the first indication information sent by the third cell. In a specific implementation, the third indication information is carried in a handover request message.

Step 502: The first cell determines that the second cell supports sending the MBMS service, and provides the MBMS service for the terminal device through the second cell.

In the embodiment of this application, when the first cell does not support the transmission of the MBMS service, a second cell that supports the transmission of the MBMS service is determined, and the MBMS is provided to the terminal device through the second cell Service, so that the terminal device receives the MBMS service provided by the second cell. Specifically, the MBMS service may be provided to the terminal device in any of the following manners.

method one

The first cell determines that the second cell supports the transmission of the MBMS service; the first cell triggers the terminal device to switch from the first cell to the second cell, and serves the terminal through the second cell The device provides the MBMS service.

During specific implementation, the terminal device receives the handover instruction sent by the first cell, switches from the first cell to the second cell, and receives the MBMS service sent by the second cell.

Way two

The first cell determines that the second cell supports sending the MBMS service; the first cell configures the second cell as a secondary cell in a dual connectivity architecture, where the second cell and the first cell A dual connectivity architecture is formed, and the first cell serves as the primary cell in the dual connectivity architecture; the first cell sends second indication information to the second cell, and the second indication information carries the information of the MBMS service Configuration information, the configuration information of the MBMS service is used by the second cell to send the MBMS service to the terminal device through dedicated signaling, or to send the MBMS service to the terminal device in a multicast manner. For the terminal device, the terminal device receives the MBMS service sent by the second cell through dedicated signaling, or the MBMS service sent by multicast.

Further, optionally, the second indication information is carried in a secondary node addition request message, or a secondary node modification request message, or a message between any two cells.

Way three

The first cell determines that the second cell supports sending the MBMS service; the first cell sends an MBMS service request to the second cell, where the MBMS service request carries configuration information of the MBMS service; the first The cell receives the MBMS service sent by the second cell; the first cell sends the MBMS service to the terminal device through dedicated signaling. For the terminal device, the terminal device receives the MBMS service from the first cell forwarded by the first cell through dedicated signaling.

Further, optionally, the first cell receives a Packet Data Convergence Protocol (PDCP) packet data unit (PDU) or an IP data packet corresponding to the MBMS service sent by the second cell , Or Transport Block (TB) data.

The following describes the technical solutions of the embodiments of the present application with specific application examples.

Example one

The terminal equipment in the idle state or in the inactive state is performing the MBMS service on the original cell (that is, the third cell), and then performs cell reselection, and the reselected target cell (that is, the first cell) does not support the transmission of the MBMS service , Or after performing cell reselection, the terminal device wants to receive a certain MBMS service, but the target cell (ie, the first cell) after the reselection does not support the transmission of the MBMS service. In this case, the terminal device sends the first The indication information is given to the network side (that is, the first cell) to indicate that the terminal device on the network side is receiving the MBMS service and the configuration information of the MBMS service. After the network side (that is, the first cell) obtains the first indication information, it can perform any of the following operations:

1) The terminal device is handed over to the second cell, and the second cell supports the transmission of the MBMS service.

2) Configure the second cell as a secondary cell (cell corresponding to SN). At the same time, the primary cell (the cell corresponding to the MN, that is, the first cell) indicates the configuration information of the MBMS service that the current terminal device of the second cell is interested in. The second cell sends the MBMS service to the terminal device through dedicated signaling, or configures the configuration information of the MBMS service for the terminal device, so that the terminal device receives the MBMS service in a multicast manner.

3) The first cell sends an MBMS service request to the second cell, and the second cell supports the sending of the MBMS service. The MBMS service request carries the configuration information of the MBMS service. Then, the second cell sends the corresponding MBMS service to the first cell, and the first cell sends the MBMS service to the terminal device through dedicated signaling. Here, the MBMS service sent by the second cell to the first cell may be PDCP PDU or IP packet or TB data.

Example two

The terminal device processing the connected state sends first indication information to the currently served network side (that is, the third cell), where the first indication information is used to indicate the configuration information of the ongoing MBMS service of the terminal device. Here, the terminal device sends the first indication information to the third cell through dedicated signaling. Then, the cell handover is performed, and the original cell (that is, the third cell) of the cell handover sends the first indication information to the target cell (that is, the first cell) through a handover request message. If the target cell (that is, the first cell) does not support the MBMS service can perform any of the following operations:

1) Configure the second cell as a secondary cell (cell corresponding to SN). At the same time, the primary cell (the cell corresponding to the MN, that is, the first cell) indicates the configuration information of the MBMS service that the current terminal device of the second cell is interested in. The second cell sends the MBMS service to the terminal device through dedicated signaling, or configures the configuration information of the MBMS service for the terminal device, so that the terminal device receives the MBMS service in a multicast manner.

2) The first cell sends an MBMS service request to the second cell, and the second cell supports the sending of the MBMS service. The MBMS service request carries the configuration information of the MBMS service. Then, the second cell sends the corresponding MBMS service to the first cell, and the first cell sends the MBMS service to the terminal device through dedicated signaling. Here, the MBMS service sent by the second cell to the first cell may be PDCP PDU or IP packet or TB data.

Example three

The terminal device processing the connected state sends first indication information to the network side (ie, the first cell) to indicate that the terminal device on the network side is receiving the MBMS service and the configuration information of the MBMS service. After the network side (that is, the first cell) obtains the first indication information, it can perform any of the following operations:

3) The first cell sends an MBMS service request to the second cell, and the second cell supports the sending of the MBMS service. The MBMS service request carries the configuration information of the MBMS service. Then, the second cell sends the corresponding MBMS service to the first cell, and the first cell sends the MBMS service to the terminal device through dedicated signaling.

Fig. 6 is a schematic diagram 1 of the structural composition of a service data transmission device provided by an embodiment of the application. As shown in Fig. 6, the service data transmission device includes:

The receiving unit 601 is configured to receive first indication information, where the first indication information is used to indicate that the terminal device needs to receive the MBMS service;

The determining unit 602 is configured to determine that the second cell supports sending the MBMS service, and provide the MBMS service for the terminal device through the second cell.

In an optional implementation manner, the first indication information carries configuration information of the MBMS service.

In an optional embodiment, the device further includes:

The handover unit (not shown in the figure) is configured to trigger the terminal device to switch from the first cell to the second cell, and provide the MBMS service for the terminal device through the second cell.

In an optional embodiment, the device further includes:

A configuration unit (not shown in the figure), configured to configure the second cell as a secondary cell in a dual connectivity architecture, where the first cell is used as a primary cell in the dual connectivity architecture;

The sending unit 603 is configured to send second indication information to the second cell, where the second indication information carries configuration information of the MBMS service, and the configuration information of the MBMS service is used by the second cell through a dedicated message. The MBMS service is sent to the terminal device, or the MBMS service is sent to the terminal device in a multicast manner.

In an optional implementation manner, the second indication information is carried in a secondary node addition request message or a secondary node modification request message.

In an optional embodiment, the device further includes:

The sending unit 603 is configured to send an MBMS service request to the second cell, where the MBMS service request carries configuration information of the MBMS service;

The receiving unit 601 is further configured to receive the MBMS service sent by the second cell;

The sending unit 603 is further configured to send the MBMS service to the terminal device through dedicated signaling.

In an optional implementation manner, the receiving unit 601 is further configured to receive PDCP PDU, or IP data packet, or TB data corresponding to the MBMS service sent by the second cell.

In an optional implementation manner, the first cell is a target cell for the terminal device to perform cell change, and the first cell does not support sending the MBMS service.

In an optional implementation manner, the MBMS service is a service that needs to be received after the terminal device performs a cell change.

In an optional implementation manner, the MBMS service is a service that is ongoing before the terminal device performs cell change.

In an optional implementation manner, the MBMS service is a service that is ongoing on a third cell before the terminal device performs cell change, and the third cell is the original cell where the terminal device performs cell change;

The receiving unit 601 is configured to receive the first indication information sent by the third cell; or, receive the first indication information sent by the terminal device.

In an optional implementation manner, the cell change refers to cell reselection or cell handover.

Those skilled in the art should understand that the relevant description of the foregoing service data transmission device in the embodiment of the present application can be understood with reference to the relevant description of the service data transmission method in the embodiment of the present application.

FIG. 7 is a second schematic diagram of the structural composition of the service data transmission device provided by the embodiment of the application. As shown in FIG. 7, the service data transmission device includes:

The sending unit 701 is configured to send first indication information to the first cell, where the first indication information is used to indicate that the terminal device needs to receive the MBMS service;

The receiving unit 702 is configured to receive an MBMS service provided by a second cell, where the second cell is a cell determined by the first cell to support sending the MBMS service.

In an optional implementation manner, the receiving unit 702 is configured to receive a handover instruction sent by the first cell, switch from the first cell to the second cell, and receive all the handover instructions sent by the second cell. Describes the MBMS business.

In an optional implementation manner, the second cell and the first cell form a dual connectivity architecture, the second cell is a secondary cell in the dual connectivity architecture, and the first cell serves as the dual connectivity architecture. The main cell in the architecture;

The receiving unit 702 is configured to receive the MBMS service sent by the second cell through dedicated signaling, or the MBMS service sent by multicast.

In an optional implementation manner, the receiving unit 702 is configured to receive the MBMS service from the first cell forwarded by the first cell through dedicated signaling.

FIG. 8 is a schematic structural diagram of a communication device 800 provided by an embodiment of the present application. The communication device may be a terminal device or a network device. The communication device 800 shown in FIG. 8 includes a processor 810. The processor 810 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 8, the communication device 800 may further include a memory 820. The processor 810 may call and run a computer program from the memory 820 to implement the method in the embodiment of the present application.

The memory 820 may be a separate device independent of the processor 810, or may be integrated in the processor 810.

Optionally, as shown in FIG. 8, the communication device 800 may further include a transceiver 830, and the processor 810 may control the transceiver 830 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.

Wherein, the transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include an antenna, and the number of antennas may be one or more.

Optionally, the communication device 800 may specifically be a network device in an embodiment of the present application, and the communication device 800 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here. .

Optionally, the communication device 800 may specifically be a mobile terminal/terminal device of an embodiment of the application, and the communication device 800 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the application. For the sake of brevity , I won’t repeat it here.

FIG. 9 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 900 shown in FIG. 9 includes a processor 910, and the processor 910 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 9, the chip 900 may further include a memory 920. The processor 910 can call and run a computer program from the memory 920 to implement the method in the embodiment of the present application.

The memory 920 may be a separate device independent of the processor 910, or may be integrated in the processor 910.

Optionally, the chip 900 may further include an input interface 930. The processor 910 can control the input interface 930 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.

Optionally, the chip 900 may further include an output interface 940. The processor 910 can control the output interface 940 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, details are not described herein again.

Optionally, the chip can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application. For the sake of brevity, here No longer.

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

FIG. 10 is a schematic block diagram of a communication system 1000 according to an embodiment of the present application. As shown in FIG. 10, the communication system 1000 includes a terminal device 1010 and a network device 1020.

Wherein, the terminal device 1010 can be used to implement the corresponding function implemented by the terminal device in the above method, and the network device 1020 can be used to implement the corresponding function implemented by the network device in the above method. For brevity, it will not be repeated here. .

It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (Random Access Memory, RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (Double Data Rate SDRAM, DDR SDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced SDRAM, ESDRAM), Synchronous Link Dynamic Random Access Memory (Synchlink DRAM, SLDRAM) ) And Direct Rambus RAM (DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

It should be understood that the foregoing memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.

The embodiment of the present application also provides a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium can be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application , For the sake of brevity, I won’t repeat it here.

The embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it is not here. Go into details again.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, For the sake of brevity, I will not repeat them here.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the network device in the embodiment of the present application. When the computer program runs on the computer, it causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity , I won’t repeat it here.

Optionally, the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application. When the computer program runs on the computer, the computer executes each method in the embodiment of the present application. For the sake of brevity, the corresponding process will not be repeated here.

A person of ordinary skill in the art may realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

A business data transmission method, the method includes:

The first cell receives first indication information, where the first indication information is used to indicate that the terminal device needs to receive the multimedia broadcast multicast service MBMS service;

The first cell determines that the second cell supports sending the MBMS service, and provides the MBMS service for the terminal device through the second cell.
The method according to claim 1, wherein the first indication information carries configuration information of the MBMS service.
The method according to claim 1 or 2, wherein the determining by the first cell that the second cell supports sending the MBMS service, and providing the MBMS service for the terminal device through the second cell, comprises:

Determining, by the first cell, that the second cell supports sending the MBMS service;

The first cell triggers the terminal device to switch from the first cell to the second cell, and provides the MBMS service for the terminal device through the second cell.
The method according to claim 1 or 2, wherein the determining by the first cell that the second cell supports sending the MBMS service, and providing the MBMS service for the terminal device through the second cell, comprises:

Determining, by the first cell, that the second cell supports sending the MBMS service;

Configuring, by the first cell, the second cell as a secondary cell in a dual connectivity architecture, where the first cell serves as a primary cell in the dual connectivity architecture;

The first cell sends second indication information to the second cell, where the second indication information carries configuration information of the MBMS service, and the configuration information of the MBMS service is used by the second cell through dedicated signaling Send the MBMS service to the terminal device, or send the MBMS service to the terminal device in a multicast manner.
The method according to claim 4, wherein the second indication information is carried in a secondary node addition request message or a secondary node modification request message.
The method according to claim 1 or 2, wherein the determining by the first cell that the second cell supports sending the MBMS service, and providing the MBMS service for the terminal device through the second cell includes:

Determining, by the first cell, that the second cell supports sending the MBMS service;

Sending, by the first cell, an MBMS service request to the second cell, where the MBMS service request carries configuration information of the MBMS service;

Receiving, by the first cell, the MBMS service sent by the second cell;

The first cell sends the MBMS service to the terminal device through dedicated signaling.
The method according to claim 6, wherein the first cell receiving the MBMS service sent by the second cell comprises:

The first cell receives the packet data convergence protocol PDCP packet data unit PDU, or IP data packet, or transmission block TB data corresponding to the MBMS service sent by the second cell.
The method according to any one of claims 1 to 7, wherein the first cell is a target cell for the terminal device to perform cell change, and the first cell does not support sending the MBMS service.
The method according to claim 8, wherein the MBMS service is a service that needs to be received after the terminal device performs a cell change.
The method according to claim 8 or 9, wherein the MBMS service is an ongoing service before the terminal device performs cell change.
The method according to claim 10, wherein the MBMS service is a service that is ongoing on a third cell before the terminal device performs cell change, and the third cell is the original cell where the terminal device performs cell change ；

The receiving of the first indication information by the first cell includes:

The first cell receives the first indication information sent by the third cell; or,

The first cell receives the first indication information sent by the terminal device.
The method according to any one of claims 8 to 11, wherein the cell change refers to cell reselection or cell handover.
A business data transmission method, the method includes:

The terminal device sends first indication information to the first cell, where the first indication information is used to indicate that the terminal device needs to receive the MBMS service;

The terminal device receives the MBMS service provided by a second cell, where the second cell is a cell determined by the first cell to support sending the MBMS service.
The method according to claim 13, wherein the first indication information carries configuration information of the MBMS service.
The method according to claim 13 or 14, wherein the terminal device receiving the MBMS service provided by the second cell includes:

The terminal device receives the handover instruction sent by the first cell, switches from the first cell to the second cell, and receives the MBMS service sent by the second cell.
The method according to claim 13 or 14, wherein the second cell and the first cell form a dual connectivity architecture, the second cell is a secondary cell in the dual connectivity architecture, and the first cell As the primary cell in the dual connectivity architecture;

The receiving of the MBMS service provided by the second cell by the terminal device includes:

The terminal device receives the MBMS service sent by the second cell through dedicated signaling, or the MBMS service sent by multicast.
The method according to claim 13 or 14, wherein the terminal device receiving the MBMS service provided by the second cell includes:

The terminal device receives the MBMS service from the first cell forwarded by the first cell through dedicated signaling.
The method according to any one of claims 13 to 17, wherein the first cell is a target cell for the terminal device to perform cell change, and the first cell does not support sending the MBMS service.
The method according to claim 18, wherein the MBMS service is a service that needs to be received after the terminal device performs cell change.
The method according to claim 18 or 19, wherein the MBMS service is an ongoing service before the terminal device performs a cell change.
The method according to any one of claims 18 to 20, wherein the cell change refers to cell reselection or cell handover.
A service data transmission device, the device includes:

A receiving unit, configured to receive first indication information, where the first indication information is used to indicate that the terminal device needs to receive an MBMS service;

The determining unit is configured to determine that the second cell supports sending the MBMS service, and provide the MBMS service for the terminal device through the second cell.
The apparatus according to claim 22, wherein the first indication information carries configuration information of the MBMS service.
The device according to claim 22 or 23, wherein the device further comprises:

The handover unit is configured to trigger the terminal device to switch from the first cell to the second cell, and provide the MBMS service for the terminal device through the second cell.
The device according to claim 22 or 23, wherein the device further comprises:

A configuration unit, configured to configure the second cell as a secondary cell in a dual connectivity architecture, where the first cell serves as a primary cell in the dual connectivity architecture;

The sending unit is configured to send second indication information to the second cell, where the second indication information carries configuration information of the MBMS service, and the configuration information of the MBMS service is used by the second cell through dedicated signaling Send the MBMS service to the terminal device, or send the MBMS service to the terminal device in a multicast manner.
The apparatus according to claim 25, wherein the second indication information is carried in a secondary node addition request message or a secondary node modification request message.
The device according to claim 22 or 23, wherein the device further comprises:

A sending unit, configured to send an MBMS service request to the second cell, where the MBMS service request carries configuration information of the MBMS service;

The receiving unit is further configured to receive the MBMS service sent by the second cell;

The sending unit is further configured to send the MBMS service to the terminal device through dedicated signaling.
The apparatus according to claim 27, wherein the receiving unit is further configured to receive PDCP PDU, or IP data packet, or TB data corresponding to the MBMS service sent by the second cell.
The apparatus according to any one of claims 22 to 28, wherein the first cell is a target cell for the terminal device to perform cell change, and the first cell does not support sending the MBMS service.
The apparatus according to claim 29, wherein the MBMS service is a service that needs to be received after the terminal device performs a cell change.
The apparatus according to claim 29 or 30, wherein the MBMS service is a service that is ongoing before the terminal device performs a cell change.
The apparatus according to claim 31, wherein the MBMS service is a service that is ongoing on a third cell before the terminal device performs cell change, and the third cell is the original cell where the terminal device performs cell change ；

The receiving unit is configured to receive the first indication information sent by the third cell; or, receive the first indication information sent by the terminal device.
The apparatus according to any one of claims 29 to 32, wherein the cell change refers to cell reselection or cell handover.
A service data transmission device, the device includes:

A sending unit, configured to send first indication information to the first cell, where the first indication information is used to indicate that the terminal device needs to receive the MBMS service;

The receiving unit is configured to receive the MBMS service provided by the second cell, where the second cell is a cell determined by the first cell to support sending the MBMS service.
The apparatus according to claim 34, wherein the first indication information carries configuration information of the MBMS service.
The apparatus according to claim 34 or 35, wherein the receiving unit is configured to receive a handover instruction sent by the first cell, switch from the first cell to the second cell, and receive the second cell. The MBMS service sent by the cell.
The device according to claim 34 or 35, wherein the second cell and the first cell form a dual connectivity architecture, the second cell is a secondary cell in the dual connectivity architecture, and the first cell As the primary cell in the dual connectivity architecture;

The receiving unit is configured to receive the MBMS service sent by the second cell through dedicated signaling, or the MBMS service sent by multicast.
The apparatus according to claim 34 or 35, wherein the receiving unit is configured to receive the MBMS service from the first cell forwarded by the first cell through dedicated signaling.
The apparatus according to any one of claims 34 to 38, wherein the first cell is a target cell for the terminal device to perform cell change, and the first cell does not support sending the MBMS service.
The apparatus according to claim 39, wherein the MBMS service is a service that needs to be received after the terminal device performs a cell change.
The apparatus according to claim 39 or 40, wherein the MBMS service is a service that is ongoing before the terminal device performs cell change.
The apparatus according to any one of claims 39 to 41, wherein the cell change refers to cell reselection or cell handover.
A network device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 1 to 12 Methods.
A terminal device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 13 to 21 Methods.
A chip comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 12.
A chip comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 13 to 21.
A computer-readable storage medium for storing a computer program that enables a computer to execute the method according to any one of claims 1 to 12.
A computer-readable storage medium for storing a computer program that enables a computer to execute the method according to any one of claims 13 to 21.
A computer program product comprising computer program instructions that cause a computer to execute the method according to any one of claims 1 to 12.
A computer program product comprising computer program instructions that cause a computer to execute the method according to any one of claims 13 to 21.
A computer program that causes a computer to execute the method according to any one of claims 1 to 12.
A computer program that causes a computer to execute the method according to any one of claims 13 to 21.