CN113661722B

CN113661722B - Service data transmission method and device, network equipment and terminal equipment

Info

Publication number: CN113661722B
Application number: CN201980095151.0A
Authority: CN
Inventors: 王淑坤; 杨宁
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-09-18
Filing date: 2019-09-18
Publication date: 2023-02-28
Anticipated expiration: 2039-09-18
Also published as: CN113661722A; WO2021051320A1

Abstract

The embodiment of the application provides a service data transmission method and device, network equipment and terminal equipment, wherein the method comprises the following steps: a first cell receives first indication information, wherein the first indication information is used for indicating that terminal equipment needs to receive a Multimedia Broadcast Multicast Service (MBMS) service; and the first cell determines that a second cell supports the transmission of the MBMS service, and provides the MBMS service for the terminal equipment through the second cell.

Description

Service data transmission method and device, network equipment and terminal equipment

Technical Field

The embodiment of the application relates to the technical field of mobile communication, in particular to a service data transmission method and device, network equipment and terminal equipment.

Background

Multimedia Broadcast Multicast Service (MBMS) is a technology for transmitting data from one data source to a plurality of users through a shared network resource, which can provide Multimedia services while efficiently utilizing the network resource to realize broadcasting and multicasting of Multimedia services at a higher rate (e.g., 256 kbps).

In New Radio (NR) systems, many scenarios need to support multicast and broadcast service requirements, such as in car networking, industrial internet, etc. It is necessary to introduce MBMS in NR. For the MBMS service in NR, after the terminal device changes cell, the target cell may not support the transmission of the MBMS service, and the terminal device has a requirement for receiving the MBMS service, which may cause the MBMS service to be interrupted.

Disclosure of Invention

The embodiment of the application provides a service data transmission method and device, network equipment and terminal equipment.

The service data transmission method provided by the embodiment of the application comprises the following steps:

a first cell receives first indication information, wherein the first indication information is used for indicating that terminal equipment needs to receive an MBMS service;

and the first cell determines that a second cell supports the transmission of the MBMS, and provides the MBMS for the terminal equipment through the second cell.

the terminal equipment sends first indication information to a first cell, wherein the first indication information is used for indicating that the terminal equipment needs to receive the MBMS service;

and the terminal equipment receives an MBMS provided by a second cell, wherein the second cell is the cell which is determined by the first cell and supports the transmission of the MBMS.

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

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

and the determining unit is used for determining that the second cell supports the transmission of the MBMS and providing the MBMS for the terminal equipment through the second cell.

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

a receiving unit, configured to receive an MBMS service provided by a second cell, where the second cell is a cell supporting sending of the MBMS service and determined by the first cell.

The network device provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing computer programs, and the processor is used for calling and running the computer programs stored in the memory to execute the service data transmission method.

The terminal device provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing computer programs, and the processor is used for calling and running the computer programs stored in the memory and executing the service data transmission method.

The chip provided by the embodiment of the application is used for realizing the service data transmission method.

Specifically, the chip includes: and the processor is used for calling and running the computer program from the memory so that the equipment provided with the chip executes the service data transmission method.

The computer-readable storage medium provided in the embodiments of the present application is used for storing a computer program, and the computer program enables a computer to execute the service data transmission method described above.

The computer program product provided by the embodiment of the present application includes computer program instructions, and the computer program instructions enable a computer to execute the service data transmission method.

The computer program provided in the embodiments of the present application, when running on a computer, causes the computer to execute the service data transmission method described above.

By the technical scheme, the NR system supports the broadcast and multicast of the MBMS. Meanwhile, on one hand, a mechanism based on double connection is provided to provide the MBMS service for the terminal equipment through the auxiliary cell; on the other hand, a mechanism for forwarding between network sides is proposed, that is, a cell which does not support MBMS service transmission forwards the MBMS service from a cell which supports MBMS service transmission to a terminal device through a dedicated signaling, so that a mechanism for forwarding between network sides or a dual connectivity architecture is based on to ensure that the terminal device can still realize continuous reception of the MBMS service when the terminal device is changed to a cell without MBMS service transmission.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

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

FIG. 2 is a diagram illustrating 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 in an embodiment of the present application;

fig. 4 is a PTM channel and a map thereof provided by an embodiment of the present application;

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

fig. 6 is a first schematic structural diagram of a service data transmission apparatus according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a service data transmission apparatus according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a communication device provided in 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 according to an embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. 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 technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, a 5G communication system, a future communication system, or the like.

Illustratively, a communication system 100 applied in the embodiment of the present 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 referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area. Optionally, the Network device 110 may be an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the Network device may be a mobile switching center, a relay station, an Access point, a vehicle-mounted 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, and the like.

The communication system 100 further comprises at least one terminal 120 located within the coverage area of the network device 110. As used herein, "terminal" includes, but is not limited to, connection via a wireline, such as via a Public Switched Telephone Network (PSTN), a Digital Subscriber Line (DSL), a Digital cable, a direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., for a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means of another terminal arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal that is arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal can refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal in a 5G network, or a terminal in a future evolved PLMN, etc.

Optionally, the terminals 120 may perform direct-to-Device (D2D) communication therebetween.

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

Fig. 1 exemplarily shows one network device and two terminals, and optionally, the communication system 100 may include a plurality of network devices and may include other numbers of terminals within the coverage of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that, in the embodiments of the present application, a device having a communication function in a network/system may be referred to as a communication device. 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 having a communication function, and the network device 110 and the terminal 120 may be the specific devices described above and are not described again here; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

In order to facilitate 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.

With the pursuit of speed, latency, high-speed mobility, energy efficiency and the diversity and complexity of the services in future life, the third generation partnership project (3) ^rd Generation Partnership Project,3 GPP) the international organization for standardization began developing 5G. The main application scenarios of 5G are: enhanced Mobile Ultra wide band (eMBB), low-Latency high-reliability Communications (URLLC), and massive Machine-Type Communications (mMTC).

On the one hand, the eMBB still targets users for multimedia content, services and data, and its demand is growing very rapidly. On the other hand, because the eMBB may be deployed in different scenarios, such as indoor, urban, rural, etc., and the difference between the capabilities and the requirements is relatively large, it cannot be said that it must be analyzed in detail in conjunction with a specific deployment scenario. Typical applications of URLLC include: industrial automation, power automation, remote medical operations (surgery), traffic safety, etc. Typical characteristics of mtc include: high connection density, small data volume, insensitive time delay service, low cost of module, long service life and the like.

When NR is deployed early, complete NR coverage is difficult to obtain, so typical network coverage is wide area LTE coverage and islanding coverage mode of NR. Moreover, a large amount of LTE is deployed below 6GHz, and the spectrum below 6GHz available for 5G is rare. NR must therefore be studied for spectrum applications above 6GHz, with limited high band coverage and fast signal fading. Meanwhile, in order to protect the early-stage LTE investment of mobile operators, a tight coupling (light interworking) working mode between LTE and NR is provided.

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

In the technical solution of the embodiment of the present application, a Dual Connectivity (DC) enhanced architecture, that is, a Multi Connectivity (MC) architecture is provided, and typically, the MC architecture may be an MR-MC architecture.

RRC state

In order to reduce air interface signaling, quickly recover wireless connection, and quickly recover data service, 5G defines a new Radio Resource Control (RRC) state, that is, an RRC INACTIVE (RRC _ INACTIVE) state. This state is distinguished from the RRC IDLE (RRC IDLE) state and the RRC ACTIVE (RRC ACTIVE) state. Wherein the content of the first and second substances,

1) RRC _ IDLE state (IDLE state for short): mobility is UE-based cell selection reselection, paging is initiated by a Core Network (CN), and a paging area is configured by the CN. The base station side has no UE context and no RRC connection.

2) RRC _ CONNECTED state (CONNECTED state for short): there is an RRC connection and there is a UE context on the base station side and the UE side. The network side knows that the location of the UE is at a specific cell level. Mobility is network side controlled mobility. Unicast data may be transmitted between the UE and the base station.

3) RRC _ INACTIVE state (INACTIVE state for short): mobility is UE-based cell selection reselection, there is a connection between CN-NRs, UE context exists on a certain base station, paging is triggered by RAN, RAN-based paging area is managed by RAN, and the network side knows that the location of UE is based on the RAN's paging area level.

MBMS

MBMS, a technology for transmitting data from one data source to a plurality of UEs through shared network resources, is introduced in 3GPP Release 6 (Release 6, R6), and provides multimedia services while efficiently utilizing network resources to implement broadcast and multicast of higher-rate (e.g., 256 kbps) multimedia services.

Because the MBMS spectrum efficiency in the 3GPP R6 is low, it is not enough to effectively carry and support the operation of the mobile tv type service. Therefore, in LTE, 3GPP explicitly proposes to enhance the support capability for downlink high-speed MBMS service, and determines the design requirements for the physical layer and air interface.

The 3GPP R9 introduces evolved MBMS (eMBMS) into LTE. eMBMS proposes a Single Frequency Network (SFN) concept, that is, a Multimedia Broadcast multicast service Single Frequency Network (MBSFN), where MBSFN employs a uniform Frequency to simultaneously transmit service data in all cells, but needs to ensure synchronization between the cells. The method can greatly improve the distribution of the overall signal-to-noise ratio of the cell, and the frequency spectrum efficiency can be correspondingly and greatly improved. eMBMS implements broadcast and multicast of services based on the IP multicast protocol.

In LTE or LTE-Advanced (LTE-a), MBMS has only a broadcast bearer mode and no multicast bearer mode. In addition, the reception of the MBMS service is applicable to the UE in an idle state or a connected state.

A Single Cell Point To multipoint (SC-PTM) concept is introduced into a 3GPP R13, and the SC-PTM is based on an MBMS network architecture.

MBMS introduces new logical channels including a Single Cell-Multicast Control Channel (SC-MCCH) and a Single Cell-Multicast Transport Channel (SC-MTCH). The SC-MCCH and SC-MTCH are mapped to a Downlink-Shared Channel (DL-SCH), and the DL-SCH is further mapped to a Physical Downlink Shared Channel (PDSCH), wherein the SC-MCCH and SC-MTCH belong to a logical Channel, the DL-SCH belongs to a transport Channel, and the PDSCH belongs to a Physical Channel. The SC-MCCH and SC-MTCH do not support Hybrid Automatic Repeat reQuest (HARQ) operation.

MBMS introduces a new System Information Block (SIB) type, SIB20. Specifically, configuration information of the SC-MCCH is transmitted through the SIB20, and one cell has only one SC-MCCH. The configuration information of the SC-MCCH comprises: the modification period of the SC-MCCH, the repetition period of the SC-MCCH, the wireless frame and the subframe for scheduling the SC-MCCH and the like. 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 SIB20 (i.e., SC-MCCH-modification period). 2) And the wireless frame for scheduling the SC-MCCH meets the following requirements: SFN mod MCCH-repetition period = MCCH-Offset, where SFN represents a system frame number of a radio frame, MCCH-repetition period represents a repetition period of the SC-MCCH, and MCCH-Offset represents an Offset of the SC-MCCH. 3) And the sub-frame for scheduling the SC-MCCH is indicated by SC-MCCH-Subframe.

The SC-MCCH is scheduled through a Physical Downlink Control Channel (PDCCH). On one hand, a new Radio Network Temporary Identity (RNTI), that is, a Single Cell RNTI (SC-RNTI), is introduced to identify a PDCCH (such as an SC-MCCH PDCCH) for scheduling an SC-MCCH, and optionally, the SC-RNTI is fixedly valued as FFFC. On the other hand, a new RNTI, that is, a Single Cell Notification RNTI (SC-N-RNTI) is introduced to identify a PDCCH (e.g., notification PDCCH) for indicating a change Notification of the SC-MCCH, and optionally, the SC-N-RNTI is fixedly set to FFFB; further, the change notification may be indicated by one bit of 8 bits (bits) of the DCI 1C. In LTE, the configuration information of SC-PTM is based on SC-MCCH configured by SIB20, and then SC-MCCH configures SC-MTCH which is used for transmitting service data.

Specifically, the SC-MCCH transmits only one message (i.e., SCPTMConfiguration) for configuring configuration information of the SC-PTM. The configuration information of SC-PTM includes: temporary Mobile Group Identity (TMGI), session Identity (session id), group RNTI (G-RNTI), discontinuous Reception (DRX) configuration information, SC-PTM service information of the neighbor cell, and the like. It should be noted that SC-PTM in R13 does not support Robust Header Compression (ROHC) function.

The discontinuous reception of the SC-PTM downlink is controlled by the following parameters: onDurationTimerSCPTM, drx-inactivityttimerscpim, SC-MICH-scheduling cycle, and SC-MTCH-scheduling offset.

When [ (SFN x 10) + subframe number ] module (SC-MTCH-scheduling cycle) = SC-MTCH-scheduling offset is satisfied, a timer onDurationTimerSCPTM is started;

when receiving downlink PDCCH dispatching, starting a timer drx-InactivetyTimerSCPTM;

the downlink SC-PTM service is received only when the timer onDurationTimerSCPTM or drx-inactivetiTimeSCPTM is running.

SC-PTM service continuity adopts the MBMS service continuity concept based on SIB15, namely, SIB15+ MBMSIntestrindication mode. The traffic continuity of idle UEs is based on the concept of frequency priority.

In NR, many scenarios need to support multicast and broadcast traffic needs, such as in car networking, industrial internet, etc. 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 an inactive state, where the target cell does not support MBMS service transmission, for example, an LTE cell or an NR cell does not transmit MBMS service data. At this time, the UE enters a connected state and is configured with MR-DC, the secondary cell (i.e. the cell corresponding to the SN) in the MR-DC supports MBMS service transmission, and the UE has a requirement for receiving MBMS service. For another scenario, the UE switches from a cell supporting MBMS service transmission to a cell not supporting MBMS service transmission in a connected state, and at this time, the configured secondary cell supports MBMS service transmission, and the UE has a requirement for receiving MBMS service. In order to satisfy the continuity of UE service reception in the above scenario, the MBMS service in which the UE is interested may be received through the secondary cell. Therefore, the following technical scheme of the embodiment of the application is provided.

In the technical solution of the embodiment of the present application, a new SIB (referred to as a first SIB) is defined, and referring to fig. 2, the first SIB includes configuration information of a first MCCH, where the first MCCH is a control channel of an MBMS service, in other words, the first SIB is used to configure configuration information of a control channel of an NR MBMS, and optionally, the control channel of the NR MBMS may also be referred to as an NR MCCH (i.e., the first MCCH).

Further, the first MCCH is used to carry a first signaling, and in this embodiment of the present application, the name of the first signaling is not limited, for example, the first signaling is signaling a, the first signaling includes configuration information of at least one first MTCH, where the first MTCH is a traffic channel (also referred to as a data channel or a transport channel) of an MBMS service, and the first MTCH is used to transmit MBMS service data (e.g., service data of NR MBMS). In other words, the first MCCH is used to configure configuration information of a traffic channel of the NR MBMS, which may also be called NR MTCH (i.e., the first MTCH) optionally.

Specifically, the first signaling is used to configure a service channel of the NR MBMS, 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, the identification information for identifying the service, such as the TMGI, the session id, and the like. 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, and the like.

It should be noted that the transmission of the first MCCH and the first MTCH is scheduled based on PDCCH. Wherein, the RNTI used by the PDCCH for scheduling the first MCCH uses a network-wide unique identifier, which 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, in the embodiment of the present application, naming of the first SIB, the first MCCH, and the first MTCH is not limited. For convenience 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, and referring to fig. 3, a PDCCH for scheduling MCCH (i.e., MCCH PDCCH) and a notification PDCCH are configured through SIB, wherein DCI carried through the MCCH PDCCH schedules PDSCH (i.e., MCCH PDSCH) for transmitting MCCH. Further, M PDCCHs (i.e., MTCH 1 PDCCH, MTCH 2 PDCCH,. Or MTCH M PDCCH) for scheduling MTCH are configured through the MCCH, wherein DCI carried by the MTCH n PDCCH schedules a PDSCH (i.e., MTCH n PDSCH) for transmitting MTCH n, n being an integer greater than or equal to 1 and less than or equal to M. Referring to fig. 4, MCCH and MTCH are mapped to DL-SCH, and further, DL-SCH is mapped to PDSCH, wherein MCCH and MTCH belong to a logical channel, DL-SCH belongs to a transport channel, and PDSCH belongs to a physical channel.

Fig. 5 is a schematic flow chart of a service data transmission method provided in an embodiment of the present application, and as shown in fig. 5, the service data transmission method includes the following steps:

step 501: the terminal equipment sends first indication information, the first cell receives the first indication information, and the first indication information is used for indicating that the terminal equipment needs to receive the MBMS service.

In this embodiment, the first cell is a target cell for the terminal device to perform cell replacement, 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 a target cell for performing cell replacement by the terminal device does not support sending the MBMS service, the terminal device sends first indication information, where the first indication information is used to indicate that the terminal device needs to receive the MBMS service. Here, the terminal device may send the first indication information to the first cell, or the terminal device sends 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: frequency point information of the MBMS, identification information (such as TMGI, session id) of the MBMS, G-RNTI and cell identification information of the last service.

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

In an optional embodiment of the present application, the MBMS service is an ongoing service before the terminal device performs cell change. Further, the MBMS service is a service that is ongoing in a third cell before the terminal device performs cell change, and the third cell is an original cell in which the terminal device performs cell change.

In this embodiment of the present application, the first cell receives the first indication information, and may determine whether itself supports sending the MBMS service based on the configuration information of the MBMS service carried by the first indication information.

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

Step 502: and the first cell determines that a second cell supports the transmission of the MBMS service, and provides the MBMS service for the terminal equipment through the second cell.

In this embodiment of the present application, when the first cell does not support sending the MBMS service, a second cell that supports sending the MBMS service is determined, and the MBMS service is provided to the terminal device through the second cell, 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 one of the following manners.

In a first mode

The first cell determines that a second cell supports the transmission of the MBMS service; and the first cell triggers the terminal equipment to be switched from the first cell to the second cell, and the MBMS service is provided for the terminal equipment through the second cell.

During specific implementation, the terminal device receives a switching 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.

Mode two

The first cell determines that a second cell supports the transmission of the MBMS service; the first cell configures the second cell as a secondary cell in a dual connectivity architecture, wherein the second cell and the first cell form the dual connectivity architecture, and the first cell is a primary cell in the dual connectivity architecture; and the first cell sends second indication information to the second cell, the second indication information carries configuration information of the MBMS, and the configuration information of the MBMS is used for the second cell to send the MBMS to the terminal equipment through a special signaling or send the MBMS to the terminal equipment through a multicast mode. 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 a multicast mode.

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

Mode III

The first cell determines that a second cell supports the transmission of the MBMS service; the first cell sends an MBMS service request to the second cell, wherein the MBMS service request carries the configuration information of the MBMS service; the first cell receives the MBMS sent by the second cell; and the first cell sends the MBMS to the terminal equipment through a special signaling. For a terminal device, the terminal device receives the MBMS service from the first cell, which is forwarded by the first cell through dedicated signaling.

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

The technical solutions of the embodiments of the present application are illustrated below with reference to specific application examples.

Example one

The method includes that terminal equipment in an idle state or an inactive state carries out an MBMS service on an original cell (namely a third cell), then cell reselection is carried out, a reselected target cell (namely a first cell) does not support the transmission of the MBMS service, or the terminal equipment wants to receive a certain MBMS service after the cell reselection is carried out, but the reselected target cell (namely the first cell) does not support the transmission of the MBMS service. After the network side (i.e. the first cell) acquires the first indication information, the network side (i.e. the first cell) may perform any one of the following operations:

1) And switching the terminal equipment to a second cell, wherein the second cell supports the transmission of the MBMS.

2) And configuring the second cell as a secondary cell (a cell corresponding to the SN). Meanwhile, the primary cell (the cell corresponding to the MN, i.e. the first cell) indicates the configuration information of the MBMS service in which the current terminal device of the second cell is interested. The second cell sends the MBMS to the terminal equipment through a special signaling, or configures the configuration information of the MBMS for the terminal equipment, so that the terminal equipment receives the MBMS in a multicast mode.

3) The first cell sends an MBMS service request to a 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 equipment through a special signaling. Here, the MBMS service transmitted by the second cell to the first cell may be PDCP PDU or IP packet or TB data, etc.

Example two

And the terminal equipment in a connection processing state sends first indication information to a network side (namely a third cell) which is currently served, wherein the first indication information is used for indicating the configuration information of the MBMS which is carried out by the terminal equipment. Here, the terminal device sends the first indication information to the third cell through dedicated signaling. Then, cell switching is executed, an original cell (i.e. a third cell) of the cell switching sends the first indication information to a target cell (i.e. a first cell) through a switching request message, and if the target cell (i.e. the first cell) does not support the MBMS service, any one of the following modes of operation can be executed:

1) And configuring the second cell as a secondary cell (a cell corresponding to the SN). Meanwhile, the primary cell (the cell corresponding to the MN, i.e. the first cell) indicates the configuration information of the MBMS service in which the current terminal device of the second cell is interested. The second cell sends the MBMS to the terminal equipment through a special signaling, or configures the configuration information of the MBMS for the terminal equipment, so that the terminal equipment receives the MBMS in a multicast mode.

2) A first cell sends an MBMS service request to a 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 equipment through a special signaling. Here, the MBMS service transmitted by the second cell to the first cell may be PDCP PDU or IP packet or TB data, etc.

Example three

The terminal equipment in a connected state is processed to send first indication information to a network side (namely, a first cell) so as to indicate the network side that the terminal equipment is receiving the MBMS and configuration information of the MBMS. After the network side (i.e. the first cell) acquires the first indication information, the network side (i.e. the first cell) may perform any one of the following operations:

2) And configuring the second cell as a secondary cell (cell corresponding to the SN). Meanwhile, the main cell (the cell corresponding to the MN, i.e. 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 to the terminal equipment through a special signaling, or configures the configuration information of the MBMS for the terminal equipment, so that the terminal equipment receives the MBMS in a multicast mode.

3) A first cell sends an MBMS service request to a 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 equipment through a special signaling.

Fig. 6 is a first schematic structural component diagram of a service data transmission device provided in an embodiment of the present application, and as shown in fig. 6, the service data transmission device includes:

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

a determining unit 602, configured to determine that a 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 apparatus further comprises:

a switching unit (not shown in the figure), 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 alternative embodiment, the apparatus further comprises:

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

a sending unit 603, 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 for the second cell to send the MBMS service to the terminal device through a dedicated signaling, or send the MBMS service to the terminal device through a multicast mode.

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

In an alternative embodiment, the apparatus further comprises:

a sending unit 603, 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 a dedicated signaling.

In an optional embodiment, the receiving unit 601 is further configured to receive a PDCP PDU, an 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 replacement, 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 cell change.

In an optional embodiment, the MBMS service is an ongoing service before the terminal device performs cell change.

In an optional embodiment, the MBMS service is a service that is ongoing in a third cell before the terminal device performs cell change, and the third cell is an original cell in which the terminal device performs cell change;

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

In an alternative embodiment, the cell change refers to cell reselection or cell handover.

Those skilled in the art should understand that the related description of the foregoing service data transmission apparatus according to the embodiment of the present application can be understood by referring to the related description of the service data transmission method according to the embodiment of the present application.

Fig. 7 is a schematic structural component diagram of a service data transmission device provided in an embodiment of the present application, and as shown in fig. 7, the service data transmission device includes:

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

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

In an optional implementation manner, the receiving unit 702 is configured to receive a handover instruction sent by the first cell, handover the first cell to the second cell, and receive the MBMS service sent by the second cell.

In an optional embodiment, 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 is a primary cell in the dual connectivity 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 the second cell through a multicast mode.

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

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

Fig. 8 is a schematic structural diagram of a communication device 800 according to an embodiment of the present application. The communication device may be a terminal device or a network device, and the communication device 800 shown in fig. 8 includes a processor 810, and the processor 810 may call and execute a computer program from a memory to implement the method in the embodiment of the present application.

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

The memory 820 may be a separate device from the processor 810, or may be integrated into 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, and in particular, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

Transceiver 830 may include a transmitter and a receiver, among other things. The transceiver 830 may further include one or more antennas.

Optionally, the communication device 800 may specifically be a network device in the embodiment of the present application, and the communication device 800 may implement a corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the communication device 800 may specifically be a mobile terminal/terminal device according to this embodiment, and the communication device 800 may implement a corresponding process implemented by the mobile terminal/terminal device in each method according to this embodiment, which is not described herein again for brevity.

Fig. 9 is a schematic structural diagram of a chip of the 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 a 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. From the memory 920, the processor 910 can call and run a computer program to implement the method in the embodiment of the present application.

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

Optionally, the chip 900 may further comprise an input interface 930. The processor 910 may control the input interface 930 to communicate with other devices or chips, and in particular, may obtain information or data transmitted 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 in particular, can output information or data to other devices or chips.

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

Optionally, the chip may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, no further description is given here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as 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.

The terminal device 1010 may be configured to implement the corresponding function implemented by the terminal device in the foregoing method, and the network device 1020 may be configured to implement the corresponding function implemented by the network device in the foregoing method, for brevity, no further description is provided here.

It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. The volatile Memory may be a Random Access Memory (RAM) which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), enhanced Synchronous SDRAM (ESDRAM), synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memories are exemplary but not limiting, for example, the memories in the embodiments 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 (DDR SDRAM), enhanced synchronous SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

An embodiment of the present application further provides a computer-readable storage medium for storing a computer program.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables a computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.

Optionally, the computer-readable storage medium may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

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

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions enable the computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.

Optionally, the computer program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instruction causes the computer to execute a corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute a corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It can be clearly understood by those skilled in the art that, for convenience and simplicity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

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

The functions may be stored in a computer-readable storage medium if they are implemented in the form of software functional units and sold or used as separate products. Based on such understanding, the technical solutions of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for transmitting service data, the method comprising:

a first cell receives first indication information, wherein the first indication information is used for indicating that terminal equipment needs to receive a Multimedia Broadcast Multicast Service (MBMS) service;

the first cell determines that a second cell supports the transmission of the MBMS, and the MBMS is provided for the terminal equipment through the second cell;

the first cell determining that a second cell supports sending the MBMS service, and providing the MBMS service for the terminal equipment through the second cell includes:

the first cell determines that a second cell supports the transmission of the MBMS service;

the first cell sends an MBMS service request to the second cell, wherein the MBMS service request carries the configuration information of the MBMS service;

the first cell receives the MBMS sent by the second cell;

and the first cell sends the MBMS to the terminal equipment through a special signaling.

2. The method of claim 1, wherein the first indication information carries configuration information of the MBMS service.

3. The method of claim 1 or 2, wherein the first cell determines that a second cell supports transmission of the MBMS service, and the MBMS service is provided to the terminal device through the second cell, further comprising:

and the first cell triggers the terminal equipment to be switched from the first cell to the second cell, and the MBMS service is provided for the terminal equipment through the second cell.

4. The method of claim 1 or 2, wherein the first cell determines that a second cell supports transmission of the MBMS service, and the MBMS service is provided to the terminal device through the second cell, further comprising:

the first cell configures the second cell as a secondary cell in a dual connectivity architecture, wherein the first cell is a primary cell in the dual connectivity architecture;

and the first cell sends second indication information to the second cell, the second indication information carries configuration information of the MBMS, and the configuration information of the MBMS is used for the second cell to send the MBMS to the terminal equipment through a special signaling or send the MBMS to the terminal equipment through a multicast mode.

5. The method of claim 4, wherein the second indication information is carried in a secondary node addition request message or a secondary node modification request message.

6. The method of claim 1, wherein the receiving, by the first cell, the MBMS service transmitted by the second cell comprises:

and the first cell receives a packet data convergence protocol PDCP packet data unit PDU, an IP data packet or a transmission block TB data corresponding to the MBMS sent by the second cell.

7. The method of claim 1 or 2, wherein the first cell is a target cell for the terminal device to perform cell change, and the first cell does not support transmission of the MBMS service.

8. The method of claim 7, wherein the MBMS service is a service that needs to be received after the terminal device performs cell change.

9. The method of claim 7, wherein the MBMS service is an ongoing service before the terminal device performs a cell change.

10. The method of claim 9, wherein the MBMS service is an ongoing service on a third cell before the terminal device performs a cell change, and the third cell is an original cell of the terminal device that performed the cell change;

the first cell receives first indication information, including:

the first cell receives first indication information sent by the third cell; alternatively, the first and second electrodes may be,

and the first cell receives first indication information sent by the terminal equipment.

11. The method of claim 7, wherein the cell change refers to a cell reselection or a cell handover.

12. A method for transmitting service data, the method comprising:

the terminal equipment receives an MBMS service provided by a second cell, wherein the second cell is a cell which is determined by the first cell and supports the transmission of the MBMS service;

wherein, the receiving, by the terminal device, the MBMS service provided by the second cell includes:

and the terminal equipment receives the MBMS from the first cell forwarded by the first cell through dedicated signaling.

13. The method of claim 12, wherein the first indication information carries configuration information of the MBMS service.

14. The method of claim 12 or 13, wherein the receiving, by the terminal device, the MBMS service provided by the second cell comprises:

and the terminal equipment receives a switching instruction sent by the first cell, switches from the first cell to the second cell and receives the MBMS sent by the second cell.

15. The method according to claim 12 or 13, 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 is a primary cell in the dual connectivity architecture;

the terminal equipment receives the MBMS provided by the second cell, and the method comprises the following steps:

and the terminal equipment receives the MBMS sent by the second cell through dedicated signaling or the MBMS sent by a multicast mode.

16. The method of claim 12 or 13, wherein the first cell is a target cell for the terminal device to perform a cell change, and the first cell does not support transmission of the MBMS service.

17. The method of claim 16, wherein the MBMS service is a service that needs to be received after the terminal device performs cell change.

18. The method of claim 16, wherein the MBMS service is an ongoing service before the terminal device performs a cell change.

19. The method of claim 16, wherein the cell change refers to a cell reselection or a cell handover.

20. A traffic data transmission apparatus, the apparatus comprising:

a determining unit, configured to determine that a 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 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 a dedicated signaling.

21. The apparatus of claim 20, wherein the first indication information carries configuration information of the MBMS service.

22. The apparatus of claim 20 or 21, wherein the apparatus further comprises:

and the switching unit is used for triggering the terminal equipment to be switched from the first cell to the second cell and providing the MBMS for the terminal equipment through the second cell.

23. The apparatus of claim 20 or 21, wherein the apparatus further comprises:

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

a sending unit, 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 to send the MBMS service to the terminal device through a dedicated signaling, or send the MBMS service to the terminal device through a multicast mode.

24. The apparatus of claim 23, wherein the second indication information is carried in a secondary node addition request message or a secondary node modification request message.

25. The apparatus of claim 20, wherein the receiving unit is further configured to receive PDCP PDUs, IP packets, or TB data corresponding to the MBMS service transmitted by the second cell.

26. The apparatus of claim 20 or 21, wherein a first cell is a target cell for the terminal device to perform cell change, and the first cell does not support transmission of the MBMS service.

27. The apparatus of claim 26, wherein the MBMS service is a service that needs to be received after the terminal device performs a cell change.

28. The apparatus of claim 26, wherein the MBMS service is an ongoing service before the terminal device performs a cell change.

29. The apparatus of claim 28, wherein the MBMS service is an ongoing service on a third cell before the terminal device performs a cell change, the third cell being an original cell in which the terminal device performed a cell change;

the receiving unit is configured to receive first indication information sent by the third cell; or receiving first indication information sent by the terminal equipment.

30. The apparatus of claim 26, wherein the cell change refers to a cell reselection or a cell handover.

31. A traffic data transmission apparatus, the apparatus comprising:

a receiving unit, configured to receive an MBMS service provided by a second cell, where the second cell is a cell supporting sending of the MBMS service and determined by the first cell;

the receiving unit is configured to receive the MBMS service from the first cell, which is forwarded by the first cell through dedicated signaling.

32. The apparatus of claim 31, wherein the first indication information carries configuration information of the MBMS service.

33. The apparatus of claim 31 or 32, wherein the receiving unit is configured to receive a handover command sent by the first cell, handover the first cell to the second cell, and receive the MBMS service sent by the second cell.

34. The apparatus of claim 31 or 32, wherein the second cell and the first cell form a dual connectivity architecture, the second cell being a secondary cell in the dual connectivity architecture, the first cell being a 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 the second cell through a multicast mode.

35. The apparatus of claim 31 or 32, wherein the first cell is a target cell for the terminal device to perform cell change, and the first cell does not support transmission of the MBMS service.

36. The apparatus of claim 35, wherein the MBMS service is a service that needs to be received after the terminal device performs a cell change.

37. The apparatus of claim 35, wherein the MBMS service is an ongoing service before the terminal device performs a cell change.

38. The apparatus of claim 35, wherein the cell change refers to a cell reselection or a cell handover.

39. A network device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 1 to 11.

40. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 12 to 19.

41. A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 11.

42. A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 12 to 19.

43. A computer-readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 11.

44. A computer-readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 12 to 19.