CN114651453B

CN114651453B - Service transmission method and device, terminal equipment, network equipment and related products

Info

Publication number: CN114651453B
Application number: CN202080075150.2A
Authority: CN
Inventors: 王淑坤
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-01-15
Filing date: 2020-01-15
Publication date: 2023-08-29
Anticipated expiration: 2040-01-15
Also published as: WO2021142647A1; CN114651453A

Abstract

The embodiment of the application provides a service transmission method and device, terminal equipment, network equipment, a chip, a computer readable storage medium and a computer program product, wherein the method comprises the following steps: the method comprises the steps that terminal equipment receives first configuration information sent by network equipment, wherein the first configuration information is used for determining MBMS carriers and unicast carriers; the terminal device receives MBMS service data on the MBMS carrier and unicast service data on the unicast carrier.

Description

Service transmission method and device, terminal equipment, network equipment and related products

Technical Field

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

Background

Multimedia broadcast multicast service (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 effectively utilize the network resource while providing multimedia services, and realize broadcasting and multicasting of multimedia services at a higher rate (e.g., 256 kbps).

In a New Radio (NR) system, many scenarios need to support the service requirements of multicasting and broadcasting, such as in the internet of vehicles, industrial internet, etc. It is necessary to introduce MBMS in the NR. For the terminal equipment in the connection state, there is a need to receive the unicast service while receiving the MBMS service, so how to coordinate the unicast service and the MBMS service reception is a problem to be solved.

Disclosure of Invention

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

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

the method comprises the steps that terminal equipment receives first configuration information sent by network equipment, wherein the first configuration information is used for determining MBMS carriers and unicast carriers;

the terminal device receives MBMS service data on the MBMS carrier and unicast service data on the unicast carrier.

the terminal equipment receives second configuration information sent by the network equipment, wherein the second configuration information is used for determining MBMS BWP and special BWP;

the terminal device receives MBMS service data on the MBMS BWP and unicast service data on the dedicated BWP.

the network equipment sends first configuration information to the terminal equipment, wherein the first configuration information is used for determining a Multimedia Broadcast Multicast Service (MBMS) carrier and a unicast carrier;

the network device transmits MBMS service data on the MBMS carrier and unicast service data on the unicast carrier.

the network device transmits second configuration information to the terminal device, the second configuration information being used to determine the MBMS BWP and the dedicated BWP;

the network device transmits MBMS service data on the MBMS BWP and unicast service data on the dedicated BWP.

The service transmission device provided by the embodiment of the application is applied to terminal equipment, and comprises the following components:

the receiving unit is used for receiving first configuration information sent by the network equipment, wherein the first configuration information is used for determining MBMS carrier waves and unicast carrier waves; receiving MBMS service data on the MBMS carrier and receiving unicast service data on the unicast carrier.

A receiving unit, configured to receive second configuration information sent by a network device, where the second configuration information is used to determine MBMS BWP and dedicated BWP; MBMS service data is received on the MBMS BWP and unicast service data is received on the dedicated BWP.

The service transmission device provided by the embodiment of the application is applied to network equipment, and comprises the following components:

a sending unit, configured to send first configuration information to a terminal device, where the first configuration information is used to determine a multimedia broadcast multicast service MBMS carrier and a unicast carrier; and transmitting MBMS service data on the MBMS carrier and transmitting unicast service data on the unicast carrier.

a transmitting unit configured to transmit second configuration information to the terminal device, the second configuration information being used to determine MBMS BWP and dedicated BWP; MBMS service data is transmitted on the MBMS BWP and unicast service data is transmitted on the dedicated BWP.

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

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

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

Specifically, the chip includes: and a processor for calling and running the computer program from the memory, so that the device mounted with the chip executes the service transmission method.

The computer readable storage medium provided by the embodiment of the application is used for storing a computer program, and the computer program enables a computer to execute the service transmission method.

The computer program product provided by the embodiment of the application comprises computer program instructions, wherein the computer program instructions enable a computer to execute the service transmission method.

The computer program provided by the embodiment of the application, when running on a computer, causes the computer to execute the service transmission method.

Through the technical scheme, the NR system is realized to support the transmission of the MBMS, the network side configures the MBMS with independent MBMS carrier waves, and simultaneously configures the unicast carrier waves for the unicast service, so that the terminal equipment can simultaneously receive the MBMS data and the unicast service data, avoid the receiving conflict of the unicast service and the MBMS service, and meet the capability requirement of the terminal equipment.

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 specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:

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 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 flow chart of a service transmission method according to an embodiment of the present application;

fig. 6 is a second flow chart of a service transmission method according to an embodiment of the present application;

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

fig. 8 is a schematic diagram II of the structural composition of a service transmission device according to an embodiment of the present application;

fig. 9 is a schematic diagram III of the structural composition of a service transmission device according to an embodiment of the present application;

fig. 10 is a schematic diagram showing the structural components of a service transmission device according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 12 is a schematic block diagram of a chip of an embodiment of the application;

fig. 13 is a schematic block diagram of a communication system provided in an embodiment of the present application.

Detailed Description

The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: long term evolution (Long Term Evolution, LTE) systems, LTE frequency division duplex (Frequency Division Duplex, FDD) systems, LTE time division duplex (Time Division Duplex, TDD), systems, 5G communication systems, future communication systems, or the like.

An exemplary communication system 100 to which embodiments of the present application may be applied 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, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area. Alternatively, the network device 110 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in the LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a 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 further includes at least one terminal 120 located within the coverage area of the network device 110. "terminal" as used herein includes, but is not limited to, connection via wireline, such as via public-switched telephone network (Public Switched Telephone Networks, PSTN), digital subscriber line (Digital Subscriber Line, DSL), digital cable, 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 (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 the other terminal arranged to receive/transmit communication signals; and/or internet of things (Internet of Things, ioT) devices. Terminals arranged to communicate over a wireless interface may be referred to as "wireless communication terminals", "wireless terminals" or "mobile terminals". Examples of mobile terminals include, but are not limited to, satellites or cellular telephones; a personal communications system (Personal Communications System, PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that can include a radiotelephone, pager, internet/intranet access, web browser, organizer, calendar, and/or a global positioning system (Global Positioning System, GPS) receiver; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal may 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 (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a 5G network or a terminal in a future evolved PLMN, etc.

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

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

Fig. 1 illustrates one network device and two terminals, alternatively, the communication system 100 may include multiple network devices and each network device may include other numbers of terminals within its coverage area, which is not limited by the embodiment of the present application.

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

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

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

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following describes the technical solutions related to the embodiments of the present application.

With the pursuit of speed, delay, high speed mobility, energy efficiency and diversity and complexity of future life business, the third generation partnership project (3 ^rd Generation Partnership Project,3 GPP) international standards organization began developing 5G. The main application scenario of 5G is: enhanced translationDynamic Ultra-wideband (enhanced Mobile Broadband, emmbb), low latency high reliability communication (URLLC), large-scale Machine-based communication (mctc).

On the one hand, embbs still target users to obtain multimedia content, services and data, and their demand is growing very rapidly. On the other hand, since an eMBB may be deployed in different scenarios, such as indoors, urban, rural, etc., its capabilities and requirements are also quite different, so that detailed analysis must be performed in connection with a specific deployment scenario, not in general. Typical applications of URLLC include: industrial automation, electric power automation, remote medical operation (surgery), traffic safety guarantee and the like. Typical characteristics of mctc include: high connection density, small data volume, delay insensitive traffic, low cost and long service life of the module, etc.

At early deployment of NRs, full NR coverage is difficult to acquire, so typical network coverage is wide area LTE coverage and island coverage mode of NRs. And a large amount of LTE is deployed below 6GHz, and the frequency spectrum below 6GHz which can be used for 5G is few. NR must study spectral applications above 6GHz while high-band coverage is limited and signal fading is fast. Meanwhile, in order to protect the mobile operators from early investment in LTE, a working mode of tight coupling (tight interworking) between LTE and NR is proposed.

To enable 5G network deployment and commercial applications as soon as possible, 3GPP first completes the first 5G release, 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 stages of R15, other DC modes, namely NE-DC,5GC-EN-DC, NR DC will be supported. For EN-DC, the core network of the access network connection is EPC, while the core network of the other DC mode connection is 5GC.

RRC state

5G for the purposes of reducing air interface signaling and fast recovery of radio connections, fast recovery of data traffic, a new radio resource control (Radio Resource Control, RRC) state, namely an RRC INACTIVE (RRC_INACTIVE) state, is defined. This state is different from the RRC IDLE (rrc_idle) state and the RRC ACTIVE (rrc_active) state. Wherein, the liquid crystal display device comprises a liquid crystal display device,

1) Rrc_idle state (simply referred to as IDLE state): mobility is UE-based cell selection reselection, paging is initiated by a Core Network (CN), and paging areas are 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 UE contexts on the base station side and UE side. The network side knows that the location of the UE is cell specific. Mobility is network-side controlled mobility. Unicast data may be transmitted between the UE and the base station.

3) Rrc_inactive state (simply referred to as INACTIVE state): mobility is cell selection reselection based on UE, there is a connection between CN-NRs, UE context exists on a certain base station, paging is triggered by RAN, paging area based on RAN is managed by RAN, network side knows UE location is based on paging area level of RAN.

Bandwidth portion (BWP)

The maximum channel bandwidth in 5G may be 400MHz (i.e., wideband), which is large compared to the maximum channel bandwidth in LTE, 20 MHz. If the UE remains operating on a wideband carrier (i.e., maximum channel bandwidth), the power consumption of the UE is significant. It is suggested that the radio frequency bandwidth of the UE may be adjusted according to the actual throughput of the UE, for which the concept of BWP was introduced, the motivation for which was to optimize the power consumption of the UE. For example, the UE may be configured with a smaller bandwidth (i.e., a smaller BWP) if the UE has a low rate requirement, and a larger bandwidth (i.e., a larger BWP) if the UE has a high rate requirement. If the UE supports a high rate or operates in carrier aggregation (Carrier aggregation, CA) mode, the UE may be configured with multiple BWPs. In addition, another purpose of BWP is to trigger coexistence of multiple parameter sets (numerology) in one cell, e.g. BWP1 corresponds to numerology1 and BWP2 corresponds to numerology2.

The idle or inactive UEs reside on the initial BWP (initial BWP), which is visible to the idle or inactive UEs, and the UEs may acquire information such as a master information block (Master Information Block, MIB), remaining minimum system information (Remaining Minimum system Information, RMSI), other system information (Other System Information, OSI), and paging (paging) on the initial BWP.

MBMS

MBMS, a technology for transmitting data from one data source to a plurality of UEs through a shared network resource, is introduced in 3GPP Release 6 (R6), and is capable of effectively utilizing network resources while providing multimedia services, and realizing broadcasting and multicasting of multimedia services at a higher rate (e.g., 256 kbps).

Due to the low MBMS spectrum efficiency in 3gpp R6, it is not sufficient to effectively carry and support the operation of the mobile tv type service. In LTE, 3GPP has therefore explicitly proposed to enhance the support capability for the downlink high speed MBMS service and to determine the design requirements for the physical layer and the air interface.

The 3gpp R9 introduces evolved MBMS (eMBMS) into LTE. eMBMS proposes the concept of a single frequency network (Single Frequency Network, SFN), i.e. a multimedia broadcast multicast service single frequency network (Multimedia Broadcast multicast service Single Frequency Network, MBSFN), wherein the MBSFN uses a unified frequency to simultaneously transmit traffic data in all cells, but synchronization between the cells is guaranteed. The method can greatly improve the overall signal-to-noise ratio distribution of the cell, and the frequency spectrum efficiency can be correspondingly and greatly improved. eMBMS implements broadcast and multicast of services based on IP multicast protocols.

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 UEs in an idle state or a connected state.

A single cell point-to-multipoint (Single Cell Point To Multiploint, SC-PTM) concept is introduced in 3gpp r13, SC-PTM being 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) and Single Cell-Multicast Transport Channel. The SC-MCCH and SC-MTCH are mapped onto a Downlink-Shared Channel (DL-SCH), and further, the DL-SCH is mapped onto a physical Downlink Shared Channel (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 (Hybrid Automatic Repeat reQuest, HARQ) operation.

MBMS introduces a new system information block (System Information Block, SIB) type, SIB20. Specifically, the 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 radio frame and subframe for scheduling the SC-MCCH and other information. Further, 1) the boundary of the modification period of the SC-MCCH satisfies SFN mod m=0, where SFN represents a system frame number of the boundary, and m is a modification period (i.e., SC-MCCH-modification period) of the SC-MCCH configured in SIB20. 2) The radio frame of the scheduling SC-MCCH meets the following conditions: SFN mod MCCH-repetition period = MCCH-Offset, where SFN represents the system frame number of the radio frame, MCCH-repetition period represents the repetition period of the SC-MCCH, and MCCH-Offset represents the Offset of the SC-MCCH. 3) The subframes of the scheduling SC-MCCH are indicated by SC-MCCH-Subframe.

The SC-MCCH is scheduled through a physical downlink control channel (Physical Downlink Control Channel, PDCCH). In one aspect, a new radio network temporary identity (Radio Network Tempory Identity, RNTI), i.e., single Cell RNTI (SC-RNTI), is introduced to identify a PDCCH (e.g., SC-MCCH PDCCH) for scheduling the SC-MCCH, optionally with the SC-RNTI fixed value FFFC. On the other hand, a new RNTI, i.e., a single cell notification RNTI (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, optionally, the SC-N-RNTI is fixed to a value of FFFB; further, the change notification may be indicated with one bit of 8 bits (bits) of DCI 1C. In LTE, the configuration information of SC-PTM is based on the SC-MCCH configured by SIB20, and then SC-MCCH configures SC-MTCH for transmitting service data.

Specifically, the SC-MCCH transmits only one message (i.e., scptm configuration) for configuring configuration information of the SC-PTM. The configuration information of the SC-PTM comprises: temporary mobile Group identity (Temporary Mobile Group Identity, TMGI), session identity (session id), group RNTI (G-RNTI), discontinuous reception (Discontinuous Reception, DRX) configuration information, SC-PTM service information of neighbor cells, and the like. Note that SC-PTM in R13 does not support the robust header compression (Robust Header Compression, ROHC) function.

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

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

when receiving downlink PDCCH scheduling, starting a timer drx-InactivityTimerSCPTM;

the downstream SC-PTM service is received only when the timer onduration timerscpm or drx-incaactyitimerscpm is running.

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

In NR, many scenarios require supporting the traffic demands of multicasting and broadcasting, such as in the internet of vehicles, industrial internet, etc. It is necessary to introduce MBMS in the NR. In NR, terminal devices in three RRC states, i.e., idle state, inactive state, and connected state, have a need to receive MBMS service data. For a terminal device in a connection state, since the BWP concept is introduced, the terminal device can only receive data on one activated BWP, and the terminal device cannot receive unicast service data and MBMS service data at the same time, so as to realize that the terminal device can receive unicast service data and MBMS service data at the same time, the following technical scheme of the embodiment of the present 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, referring to fig. 2, where 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 the first signaling, where the name of the first signaling is not limited, for example, the first signaling is signaling a, and 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 transmission channel) of an MBMS service, and the first MTCH is used to transmit MBMS service data (such as 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, alternatively, the traffic channel of the NR MBMS may also be called as NR MTCH (i.e., the first MTCH).

Specifically, the first signaling is used for configuring 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, TMGI, session id, and other identification information for identifying the service. Scheduling information corresponding to the service channel, for example, RNTI used when MBMS service data corresponding to the service channel is scheduled, for example, G-RNTI, DRX configuration information, and the like.

The transmissions of the first MCCH and the first MTCH are scheduled based on the PDCCH. The RNTI used for scheduling the PDCCH of the first MCCH uses a unique network identifier, i.e. a fixed value. The RNTI used for scheduling PDCCH use of the first MTCH is configured through the first MCCH.

It should be noted that, in the embodiment of the present application, the 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 simply referred to as SIB, the first MCCH may also be simply referred to as MCCH, and the first MTCH may also be simply referred to as MTCH, and referring to fig. 3, a PDCCH (i.e. MCCH PDCCH) for scheduling the MCCH and a notification PDCCH are configured through the SIB, where a PDSCH (i.e. MCCH PDSCH) for transmitting the MCCH is scheduled through DCI carried in MCCH PDCCH. Further, M PDCCHs for scheduling MTCH (i.e., MTCH 1 PDCCH, MTCH 2 PDCCH, …, MTCH M PDCCH) are configured through the MCCH, wherein DCI carried by MTCH n PDCCH schedules PDSCH for transmitting MTCH n (i.e., MTCH n PDSCH), 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 onto DL-SCH, and further, DL-SCH is mapped onto PDSCH, wherein MCCH and MTCH belong to a logical channel, DL-SCH belongs to a transport channel, and PDSCH belongs to a physical channel.

It should be noted that, the MBMS related to the embodiment of the present application may refer to multicast or broadcast.

Fig. 5 is a flow chart of a service transmission method according to an embodiment of the present application, as shown in fig. 5, where the service transmission method includes the following steps:

step 501: the terminal equipment receives first configuration information sent by the network equipment, wherein the first configuration information is used for determining MBMS carrier waves and unicast carrier waves.

In the embodiment of the application, the network equipment sends the first configuration information to the terminal equipment, and correspondingly, the terminal equipment receives the first configuration information sent by the network equipment. Here, the network device may alternatively be a base station, such as a gNB. Here, the first configuration information is used to determine an MBMS carrier and a unicast carrier. Wherein, the MBMS carrier is used for the terminal equipment to receive the MBMS carrier, and the unicast carrier is used for the terminal equipment to receive the unicast service data.

It should be noted that the first configuration information may include configuration information of at least one MBMS carrier and configuration information of at least one unicast carrier.

In an alternative embodiment, before the network device sends the first configuration information to the terminal device, the method further comprises:

The terminal equipment sends first indication information to the network equipment, the network equipment receives the first indication information sent by the terminal equipment, and the first indication information is used for indicating the identification information of the first MBMS which is ready to be received or is being received by the terminal equipment.

Further, optionally, the identification information of the first MBMS service includes at least one of: G-RNTI, TMGI, session identifier, MBMS Service Area Identifier (SAI), frequency information. Here, it is considered that different MBMS services are associated with different G-RNTIs and/or TMGIs and/or session identifications and/or MBMS service area identifications and/or frequency information, and thus, one MBMS service may be identified by the G-RNTIs and/or TMGIs and/or session identifications and/or MBMS service area identifications and/or frequency information.

For example: and under the condition that the terminal equipment is in a connection state, preparing to receive a certain MBMS service (namely the first MBMS service), indicating the identification information of the first MBMS service which is prepared to be received by the terminal equipment at the network side by the terminal equipment.

For example: the terminal equipment enters a connection state after having received a certain MBMS service (namely the first MBMS service) in an idle state or a non-activated state, and then the terminal equipment indicates the identification information of the first MBMS service which is being received by the terminal equipment at the network side.

It should be noted that, alternatively, the first indication information in the above scheme may also be referred to as MBMS service indication information.

In an alternative embodiment, the terminal device sends first capability information to the network device, the network device receives the first capability information sent by the terminal device, and the first capability information is used for indicating at least one of the following:

a band (band) capability supported by the terminal device;

the frequency band combining capability supported by the terminal equipment;

the terminal device supports carrier aggregation (Carrier Aggregation, CA) capability;

the terminal device supports dual connectivity (Dual Connectivity, DC) capabilities;

the terminal equipment supports to simultaneously receive MBMS service data and unicast service data under a CA architecture;

the terminal device supports simultaneous reception of MBMS service data and unicast service data under a DC architecture.

It should be noted that, alternatively, the DC in the above scheme may be MR-DC.

It should be noted that, alternatively, the first capability information in the above scheme may also be referred to as UE capability information.

In the embodiment of the present application, after receiving the first indication information and/or the first capability information sent by the terminal device, the network side configures the first configuration information for the terminal device based on the first indication information and/or the first capability information, where the first configuration information includes at least one of the following: CA configuration, DC configuration and indication information of the MBMS carrier associated with the first MBMS service.

Further, optionally, the indication information of the MBMS carrier includes at least one of: serving cell identification information (servingcell id), secondary cell index information (Scell index). Further, optionally, the indication information of the MBMS carrier may further include identification information of an MBMS service associated with the MBMS carrier.

Step 502: the terminal device receives MBMS service data on the MBMS carrier and unicast service data on the unicast carrier.

In the embodiment of the application, the terminal equipment receives the corresponding MBMS service data on the MBMS carrier configured by the network side, and receives the unicast service data on other carriers (namely, unicast carriers). It should be noted that, for the network side, the network device does not send unicast service data on the MBMS carrier by implementing.

In an alternative embodiment, the network side may schedule the MBMS carrier for transmission of the uplink unicast data. Specifically, the network device sends uplink scheduling information on the unicast carrier or the MBMS carrier, the terminal device receives the uplink scheduling information on the unicast carrier or the MBMS carrier, and sends uplink unicast service data on the MBMS carrier based on the uplink scheduling information.

The uplink scheduling information is used to schedule the terminal device to transmit uplink unicast service data on the MBMS carrier.

The case where the network device transmits uplink scheduling information on the unicast carrier belongs to a case of cross-carrier scheduling. And the situation that the network equipment sends uplink scheduling information on the MBMS carrier belongs to the situation of carrier scheduling.

In the embodiment of the present application, the first configuration information is used to determine at least one MBMS carrier, where each MBMS carrier in the at least one MBMS carrier is capable of carrying one or more MBMS services.

In particular, the network side may configure one or more MBMS carriers to the terminal device, where one MBMS carrier may carry one or more MBMS services. Each MBMS carrier may be configured with an index number that identifies one MBMS carrier. Further, alternatively, the index number of the MBMS carrier may be Scell index or serving cell id.

In an alternative embodiment, during the handover procedure, the terminal device needs to switch the MBMS carrier, e.g. from the first MBMS carrier (i.e. the original MBMS carrier) to the second MBMS carrier (i.e. the target MBMS carrier). Alternatively, the state of a part (may be one or more) of the MBMS carriers is changed to the deactivated state or the first state, and the state of another part (may be one or more) of the MBMS carriers is changed to the activated state or the second state. Here, the first state refers to an active state having sleep behavior (dormancy), and the second state refers to an active state having non-sleep behavior (nonmancy).

1) Mode one

The network equipment sends second indication information to the terminal equipment, the terminal equipment receives the second indication information sent by the network equipment, and the second indication information is used for indicating the terminal equipment to add a target MBMS carrier and/or delete an original MBMS carrier.

Here, the network side may add the target MBMS carrier to the terminal device first, and then delete the original MBMS carrier.

2) Mode two

The terminal device associates multiple carriers under a CA or DC architecture, a first part (may be one or more) of the multiple carriers belonging to an MBMS carrier, and a second part (may be one or more) of the multiple carriers belonging to a unicast carrier.

The network device sends third indication information to the terminal device, the terminal device receives the third indication information sent by the network device, and the third indication information is used for indicating at least one of the following:

whether each MBMS carrier of the first portion of carriers is in an active state or in a deactivated state (i.e., only indicates an active state or a deactivated state of an MBMS carrier);

whether each MBMS carrier of the first portion of carriers is in a first state or a second state (i.e., indicates only the first state or the second state of MBMS carriers);

Whether each of the plurality of carriers is in an active state or a deactivated state (i.e., indicating an active state or a deactivated state for all carriers);

whether each of the plurality of carriers is in a first state or a second state (i.e., a first state or a second state indicating all carriers);

the first state refers to an active state with dormant behavior, and the second state refers to an active state with non-dormant behavior.

By the above scheme, the terminal device can determine the state of each MBMS carrier based on the received third indication information. The management method of the MBMS carrier in the switching process is realized, so that the reliability and the continuity of MBMS data reception are ensured in the switching process.

Further optionally, the third indication information includes a bitmap (bitmap), where each bit in the bitmap corresponds to one MBMS carrier, and the value of the bit is used to indicate whether the MBMS carrier corresponding to the bit is in an activated state or a deactivated state, or indicate whether the MBMS carrier corresponding to the bit is in a first state or a second state.

Further optionally, the third indication information includes a bitmap (bitmap), where each bit in the bitmap corresponds to a carrier, the carrier may be a unicast carrier or an MBMS carrier, and different types of carriers corresponding to different bits may be the same or different, and the value of the bit is used to indicate whether the carrier corresponding to the bit is in an activated state or a deactivated state, or indicate whether the carrier corresponding to the bit is in a first state or a second state.

Further optionally, the third indication information is carried in PDCCH or MAC CE or RRC signaling.

Further optionally, during the handover, the first indication information is forwarded from the original base station to the target base station.

Fig. 6 is a second flow chart of a service transmission method according to an embodiment of the present application, as shown in fig. 6, where the service transmission method includes the following steps:

step 601: the terminal device receives second configuration information transmitted by the network device, the second configuration information being used to determine the MBMS BWP and the dedicated BWP.

In the embodiment of the application, the network equipment sends the second configuration information to the terminal equipment, and correspondingly, the terminal equipment receives the second configuration information sent by the network equipment. Further optionally, the network device may be a base station, such as a gNB. Here, the first configuration information is used to determine MBMS BWP and dedicated BWP. Wherein, the MBMS BWP refers to BWP for the terminal device to receive MBMS service data, and the dedicated BWP refers to BWP for the terminal device to receive unicast service data.

In particular, the network side may configure the terminal device with spectrum range information (i.e., configuration information of MBMS BWP where the MBMS transmission is located) where the MBMS service is transmitted for a certain cell (e.g., a serving cell). Here, the configuration information of the MBMS BWP includes at least one of: bandwidth of MBMS BWP, start frequency point of MBMS BWP, end frequency point of MBMS BWP, intermediate frequency point of MBMS BWP. The network side may also configure the terminal device with a dedicated BWP for transmitting unicast traffic data, for example: the network side can configure up to 4 dedicated BWP. It should be noted that, since the dedicated BWP is used for the network side to transmit the downstream unicast service data, the dedicated BWP refers to downstream dedicated BWP.

The network side may configure the terminal device with an MBMS BWP associated with the first MBMS service based on the first indication information, that is, the MBMS BWP is used for the terminal device to receive the data of the first MBMS service.

It should be noted that the second configuration information is used to determine at least one MBMS BWP and at least one dedicated BWP, i.e., the second configuration information includes configuration information of at least one MBMS BWP and configuration of at least one dedicated BWP.

Further, optionally, in the handover process, the first indication information is forwarded to the target base station by the original base station, so that the target base station can learn the identification information of the first MBMS service that the terminal device is ready to receive or is receiving, and configure the terminal device with the MBMS carrier and/or the MBMS BWP associated with the first MBMS service.

Step 602: the terminal device receives MBMS service data on the MBMS BWP and unicast service data on the dedicated BWP.

In the embodiment of the present application, the network device transmits MBMS service data on the MBMS BWP and transmits the special BWP on the special BWP. So that the terminal device can simultaneously receive MBMS service data on the MBMS BWP and unicast service data on the dedicated BWP. The simultaneous receiving of MBMS service data and unicast service data is ensured.

In an alternative embodiment, the second configuration information is used to determine a first dedicated BWP list, where the first dedicated BWP list refers to one or more dedicated BWP configured by the network side for the terminal device (i.e. the second configuration information is used to determine at least one dedicated BWP).

The terminal equipment determines a second special BWP list from the first special BWP list according to the self radio frequency capability; wherein each dedicated BWP in the second dedicated BWP list and the MBMS BWP are receivable simultaneously by the terminal device; the terminal device sends the second special BWP list to the network device, and accordingly, the network device receives the second special BWP list sent by the terminal device.

Here, the second dedicated BWP list is provided to the network device in case the terminal device is in a connected state.

For example: the network side is configured with BWP1, BWP2 and BWP3 for the terminal device to receive unicast traffic data, where BWP1, BWP2 and BWP3 form a first dedicated BWP list. The terminal device determines whether the terminal device can simultaneously receive MBMS service data and unicast service data on the MBMS BWP and on BWP1, and whether the terminal device can simultaneously receive MBMS service data and unicast service data on the MBMS BWP and on BWP2, and whether the terminal device can simultaneously receive MBMS service data and unicast service data on the MBMS BWP and on BWP3, based on the spectrum information of the MBMS BWP and the spectrum information of the BWP1, BWP2, and BWP 3. If the terminal device can simultaneously receive MBMS service data and unicast service data on the MBMS BWP and on BWP1 and can simultaneously receive MBMS service data and unicast service data on the MBMS BWP and on BWP2, but cannot simultaneously receive MBMS service data and unicast service data on the MBMS BWP and on BWP3, the terminal device feeds back BWP1 and BWP2 to the network side, wherein BWP1 and BWP2 form a second dedicated BWP list.

Based on this, the network device, after receiving the second dedicated BWP list, performs a handover of dedicated BWP only in the second dedicated BWP list. Specifically, if the network side decides that the special BWP needs to be switched, the network device sends fourth indication information to the terminal device, where the terminal device receives the fourth indication information sent by the network device, where the fourth indication information is used to instruct the terminal device to switch from the first special BWP to the second special BWP, where the first special BWP and the second special BWP belong to the second special BWP list. After the BWP handover, the terminal device may receive the MBMS service data and the unicast service data at the same time, since the second dedicated BWP and the BMBS BWP after the handover may still be received at the terminal device at the same time.

Further, optionally, if the terminal device updates from receiving the first MBMS service to receiving the second MBMS service, the terminal device updates the second dedicated BWP list based on the MBMS BWP corresponding to the second MBMS service; and the terminal equipment sends the updated second special BWP list and/or the identification information of the second MBMS to the network equipment. Here, the second MBMS service prepares for the terminal device to receive or is receiving an MBMS service.

It should be noted that, the method for updating the second dedicated BWP list by the terminal device based on the MBMS BWP corresponding to the second MBMS service may be understood with reference to the foregoing method if the second dedicated BWP list is determined, and each of the updated second dedicated BWP list and the updated MBMS BWP may be received by the terminal device at the same time.

In an alternative embodiment, the second dedicated BWP list is sent by the primary base station to the target base station during the handover procedure, thereby facilitating the target base station to configure the appropriate dedicated BWP to the terminal device.

In the above scheme, the dedicated BWP and the MBMS BWP belong to separate BWP, and the dedicated BWP and the MBMS BWP may be received by the terminal device at the same time, i.e., the terminal device may receive unicast service data and MBMS service data on the dedicated BWP and the MBMS BWP at the same time, and may also be understood as that the radio frequency capability of the terminal device supports the spectrum ranges of the dedicated BWP and the MBMS BWP.

In an alternative embodiment, the spectral range of the dedicated BWP comprises the spectral range of the MBMS BWP.

In particular implementation, the network side may configure the MBMS BWP associated with the first MBMS service for the terminal device according to the first indication information sent by the terminal device, and at the same time, when the network side configures the special BWP, a spectrum range of the special BWP includes a spectrum range of the MBMS BWP. Therefore, the radio frequency capability of the terminal equipment can also support the frequency spectrum range of the MBMS BWP under the condition of supporting the frequency spectrum range of the special BWP, so that the terminal equipment can receive unicast service data and MBMS service data simultaneously.

Fig. 7 is a schematic structural diagram of a service transmission device according to an embodiment of the present application, which is applied to a terminal device, as shown in fig. 7, where the service transmission device includes:

a receiving unit 701, configured to receive first configuration information sent by a network device, where the first configuration information is used to determine an MBMS carrier and a unicast carrier; receiving MBMS service data on the MBMS carrier and receiving unicast service data on the unicast carrier.

In an alternative embodiment, the apparatus further comprises:

a transmitting unit 702, configured to transmit first indication information to the network device, where the first indication information is used to indicate identification information of a first MBMS service that the terminal device is ready to receive or is receiving.

In an alternative embodiment, the identification information of the first MBMS service includes at least one of: G-RNTI, TMGI, session identifier, MBMS service area identifier, and frequency information.

In an alternative embodiment, the apparatus further comprises:

a transmitting unit 702, configured to transmit first capability information to the network device, where the first capability information is used to indicate at least one of:

the frequency band capability supported by the terminal equipment;

The frequency band combining capability supported by the terminal equipment;

the terminal equipment supports CA capability;

the terminal device supports DC capability;

In an alternative embodiment, the first configuration information includes at least one of:

CA configuration, DC configuration and indication information of the MBMS carrier associated with the first MBMS service.

In an alternative embodiment, the indication information of the MBMS carrier includes at least one of: serving cell identification information, scell index information.

In an alternative embodiment, the first configuration information is used to determine at least one MBMS carrier, where each MBMS carrier of the at least one MBMS carrier is capable of carrying one or more MBMS services.

In an optional embodiment, the receiving unit 701 is further configured to receive uplink scheduling information on the unicast carrier or the MBMS carrier;

the apparatus further comprises: a transmitting unit 702, configured to transmit uplink unicast service data on the MBMS carrier based on the uplink scheduling information.

In an optional embodiment, the receiving unit 701 is further configured to receive second indication information sent by the network device, where the second indication information is used to instruct the terminal device to add a target MBMS carrier and/or delete an original MBMS carrier.

In an optional implementation manner, the terminal device associates multiple carriers under a CA or DC architecture, a first part of the multiple carriers belongs to an MBMS carrier, and a second part of the multiple carriers belongs to a unicast carrier;

the receiving unit 701 is further configured to receive third indication information sent by the network device, where the third indication information is used to indicate at least one of the following:

whether each MBMS carrier in the first partial carrier is in an active state or in a deactivated state;

whether each MBMS carrier in the first partial carrier is in a first state or in a second state;

whether each of the plurality of carriers is in an active state or a deactivated state;

whether each carrier of the plurality of carriers is in a first state or a second state;

In an alternative embodiment, the third indication information is carried in PDCCH or MAC CE or RRC signaling.

In an alternative embodiment, during the handover, the first indication information is forwarded from the original base station to the target base station.

It should be understood by those skilled in the art that the above description of the service transmission apparatus according to the embodiment of the present application may be understood with reference to the description of the service transmission method according to the embodiment of the present application.

Fig. 8 is a schematic diagram ii of the structural composition of a service transmission device according to an embodiment of the present application, which is applied to a terminal device, as shown in fig. 8, where the service transmission device includes:

a receiving unit 801, configured to receive second configuration information sent by a network device, where the second configuration information is used to determine MBMS BWP and dedicated BWP; MBMS service data is received on the MBMS BWP and unicast service data is received on the dedicated BWP.

In an alternative embodiment, the apparatus further comprises:

a transmitting unit 802, configured to transmit first indication information to the network device, where the first indication information is used to indicate identification information of a first MBMS service that the terminal device is ready to receive or is receiving.

In an alternative embodiment, the second configuration information is used to determine a first dedicated BWP list;

the apparatus further comprises:

a determining unit 803, configured to determine, according to its own radio frequency capability, a second dedicated BWP list from the first dedicated BWP list; wherein each dedicated BWP in the second dedicated BWP list and the MBMS BWP are receivable simultaneously by the terminal device;

a sending unit 802, configured to send the second dedicated BWP list to the network device.

In an alternative embodiment, the receiving unit 801 is further configured to receive fourth indication information sent by the network device, where the fourth indication information is used to instruct the terminal device to switch from a first dedicated BWP to a second dedicated BWP, and the first dedicated BWP and the second dedicated BWP belong to the second dedicated BWP list.

In an alternative embodiment, the apparatus further comprises:

an updating unit (not shown in the figure) configured to update the second dedicated BWP list based on an MBMS BWP corresponding to the second MBMS service if the terminal equipment updates from receiving the first MBMS service to receiving the second MBMS service;

The sending unit 802 is further configured to send the updated second dedicated BWP list and/or the identification information of the second MBMS service to the network device.

In an alternative embodiment, the second MBMS service is an MBMS service that the terminal equipment is ready to receive or is receiving.

In an alternative embodiment, the second dedicated BWP list is sent by the original base station to the target base station during the handover procedure.

In an alternative embodiment, the dedicated BWP and the MBMS BWP belong to separate BWP.

Fig. 9 is a schematic diagram III of the structural composition of a service transmission device according to an embodiment of the present application, which is applied to a network device, as shown in fig. 9, where the service transmission device includes:

a sending unit 901, configured to send first configuration information to a terminal device, where the first configuration information is used to determine a multimedia broadcast multicast service MBMS carrier and a unicast carrier; and transmitting MBMS service data on the MBMS carrier and transmitting unicast service data on the unicast carrier.

In an alternative embodiment, the apparatus further comprises:

a receiving unit 902, configured to receive first indication information sent by the terminal device, where the first indication information is used to indicate identification information of a first MBMS service that the terminal device is ready to receive or is receiving.

In an alternative embodiment, the apparatus further comprises:

a receiving unit 902, configured to receive first capability information sent by the terminal device, where the first capability information is used to indicate at least one of the following:

the frequency band capability supported by the terminal equipment;

the frequency band combining capability supported by the terminal equipment;

the terminal equipment supports CA capability;

the terminal device supports DC capability;

In an optional implementation manner, the sending unit is further configured to send uplink scheduling information on the unicast carrier or the MBMS carrier;

the apparatus further comprises: and a receiving unit 902, configured to receive uplink unicast service data sent by the terminal device on the MBMS carrier.

In an optional embodiment, the sending unit 901 is further configured to send second indication information to the terminal device, where the second indication information is used to instruct the terminal device to add a target MBMS carrier and/or delete an original MBMS carrier.

The sending unit 901 is further configured to send third indication information to the terminal device, where the third indication information is used to indicate at least one of the following:

Fig. 10 is a schematic diagram showing the structural composition of a service transmission device according to an embodiment of the present application, which is applied to a network device, as shown in fig. 10, where the service transmission device includes:

a transmitting unit 1001 configured to transmit second configuration information to a terminal device, where the second configuration information is used to determine MBMS BWP and dedicated BWP; MBMS service data is transmitted on the MBMS BWP and unicast service data is transmitted on the dedicated BWP.

In an alternative embodiment, the apparatus further comprises:

a receiving unit 1002, configured to receive first indication information sent by the terminal device, where the first indication information is used to indicate identification information of a first MBMS service that the terminal device is ready to receive or is receiving.

the apparatus further comprises: a receiving unit 1002, configured to receive a second dedicated BWP list sent by the terminal device, where the second dedicated BWP list is a subset belonging to the first dedicated BWP list, and each dedicated BWP in the second dedicated BWP list and the MBMS BWP are capable of being received simultaneously by the terminal device.

In an alternative embodiment, the sending unit 1001 is further configured to send fourth indication information to the terminal device, where the fourth indication information is used to instruct the terminal device to switch from a first dedicated BWP to a second dedicated BWP, and the first dedicated BWP and the second dedicated BWP belong to the second dedicated BWP list.

Fig. 11 is a schematic block diagram of a communication device 1100 according to an embodiment of the present application. The communication device may be a terminal device or a network device, and the communication device 1100 shown in fig. 11 includes a processor 1110, where the processor 1110 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. 11, the communication device 1100 may also include a memory 1120. Wherein the processor 1110 may call and run a computer program from the memory 1120 to implement the methods in embodiments of the present application.

Wherein the memory 1120 may be a separate device from the processor 1110 or may be integrated into the processor 1110.

Optionally, as shown in fig. 11, the communication device 1100 may further include a transceiver 1130, and the processor 1110 may control the transceiver 1130 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

The transceiver 1130 may include, among other things, a transmitter and a receiver. Transceiver 1130 may further include antennas, the number of which may be one or more.

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

Optionally, the communication device 1100 may be specifically a mobile terminal/terminal device according to an embodiment of the present application, and the communication device 1100 may implement a corresponding flow implemented by the mobile terminal/terminal device in each method according to an embodiment of the present application, which is not described herein for brevity.

Fig. 12 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 1200 shown in fig. 12 includes a processor 1210, and the processor 1210 may call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

Optionally, as shown in fig. 12, the chip 1200 may further include a memory 1220. Wherein the processor 1210 may call and run computer programs from the memory 1220 to implement the methods of embodiments of the present application.

The memory 1220 may be a separate device from the processor 1210, or may be integrated into the processor 1210.

Optionally, the chip 1200 may also include an input interface 1230. Wherein the processor 1210 may control the input interface 1230 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.

Optionally, the chip 1200 may further include an output interface 1240. Wherein processor 1210 may control the output interface 1240 to communicate with other devices or chips, and in particular may 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 a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

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

Fig. 13 is a schematic block diagram of a communication system 1300 provided by an embodiment of the present application. As shown in fig. 13, the communication system 1300 includes a terminal device 1310 and a network device 1320.

The terminal device 1310 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1320 may be used to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment 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 implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks 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 embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct 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 memory is illustrative but not restrictive, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

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

The embodiment of the application also provides a computer program product comprising computer program instructions.

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

Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein 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 solution. 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 will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within 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 traffic, the method comprising:

the method comprises the steps that terminal equipment receives first configuration information sent by network equipment, wherein the first configuration information is used for determining a Multimedia Broadcast Multicast Service (MBMS) carrier and a unicast carrier;

the terminal equipment receives MBMS service data on the MBMS carrier and receives unicast service data on the unicast carrier, wherein the terminal equipment associates a plurality of carriers under a carrier aggregation CA or a dual-connection DC architecture, a first part of carriers in the plurality of carriers belong to the MBMS carrier, and a second part of carriers in the plurality of carriers belong to the unicast carrier;

the method further comprises the steps of:

the terminal equipment receives third indication information sent by the network equipment, wherein the third indication information is used for indicating the following steps:

2. The method of claim 1, wherein the method further comprises:

the terminal device sends first indication information to the network device, where the first indication information is used to indicate identification information of a first MBMS service that the terminal device is ready to receive or is receiving.

3. The method of claim 2, wherein the identification information of the first MBMS service includes at least one of: the method comprises the steps of a group radio network temporary identifier G-RNTI, a temporary mobile group identifier TMGI, a session identifier, an MBMS service area identifier and frequency information.

4. The method of claim 1, wherein the method further comprises:

The terminal device sends first capability information to the network device, wherein the first capability information is used for indicating at least one of the following:

the frequency band capability supported by the terminal equipment;

the frequency band combining capability supported by the terminal equipment;

the terminal equipment supports carrier aggregation CA capability;

the terminal device supports dual connectivity DC capability;

5. The method of claim 2, wherein the first configuration information comprises at least one of:

6. The method of claim 5, wherein the indication information of the MBMS carrier comprises at least one of: serving cell identification information, secondary cell Scell index information.

7. The method of claim 1, wherein the first configuration information is used to determine at least one MBMS carrier, each of the at least one MBMS carrier capable of carrying one or more MBMS services.

8. The method of claim 1, wherein the method further comprises:

and the terminal equipment receives uplink scheduling information on the unicast carrier or the MBMS carrier and sends uplink unicast service data on the MBMS carrier based on the uplink scheduling information.

9. The method of claim 1, wherein the method further comprises:

and the terminal equipment receives second indication information sent by the network equipment, wherein the second indication information is used for indicating the terminal equipment to add a target MBMS carrier and/or delete an original MBMS carrier.

10. The method of claim 1, wherein the third indication information is carried in a physical downlink control channel PDCCH or a medium access control element MAC CE or radio resource control RRC signaling.

11. The method of claim 2, wherein the first indication information is forwarded by an original base station to a target base station during a handover procedure.

12. A method for transmitting traffic, the method comprising:

the terminal equipment receives second configuration information sent by the network equipment, wherein the second configuration information is used for determining a MBMS bandwidth part BWP and a special BWP;

The terminal device receives MBMS service data on the MBMS BWP and unicast service data on the dedicated BWP, wherein the second configuration information is used to determine a first dedicated BWP list;

the method further comprises the steps of:

the terminal equipment determines a second special BWP list from the first special BWP list according to the self radio frequency capability; wherein each dedicated BWP in the second dedicated BWP list and the MBMS BWP are receivable simultaneously by the terminal device;

the terminal device sends the second dedicated BWP list to the network device.

13. The method of claim 12, wherein the method further comprises:

14. The method of claim 13, wherein the identification information of the first MBMS service includes at least one of: G-RNTI, TMGI, session identifier, MBMS service area identifier, and frequency information.

15. The method of claim 12, wherein the method further comprises:

The terminal device receives fourth indication information sent by the network device, where the fourth indication information is used to instruct the terminal device to switch from a first dedicated BWP to a second dedicated BWP, and the first dedicated BWP and the second dedicated BWP belong to the second dedicated BWP list.

16. The method of claim 12, wherein the method further comprises:

if the terminal equipment updates from receiving a first MBMS service to receiving a second MBMS service, the terminal equipment updates the second special BWP list based on the MBMS BWP corresponding to the second MBMS service;

and the terminal equipment sends the updated second special BWP list and/or the identification information of the second MBMS to the network equipment.

17. The method of claim 16, wherein the second MBMS service is an MBMS service that the terminal device is ready to receive or is receiving.

18. The method of claim 12, wherein the second dedicated BWP list is transmitted by the original base station to the target base station during the handover.

19. The method of claim 12, wherein the dedicated BWP and the MBMS BWP belong to independent BWP.

20. The method of claim 12, wherein the dedicated BWP spectral range comprises the MBMS BWP spectral range.

21. The method of claim 13, wherein the first indication information is forwarded by an original base station to a target base station during a handover procedure.

22. A method for transmitting traffic, the method comprising:

the network equipment sends MBMS service data on the MBMS carrier and sends unicast service data on the unicast carrier, wherein the terminal equipment associates a plurality of carriers under a carrier aggregation CA or a dual-connection DC architecture, a first part of carriers in the plurality of carriers belong to the MBMS carrier, and a second part of carriers in the plurality of carriers belong to the unicast carrier;

the method further comprises the steps of:

the network device sends third indication information to the terminal device, wherein the third indication information is used for indicating the following steps:

23. The method of claim 22, wherein the method further comprises:

the network device receives first indication information sent by the terminal device, where the first indication information is used to indicate that the terminal device is ready to receive or is receiving identification information of a first MBMS service.

24. The method of claim 23, wherein the identification information of the first MBMS service includes at least one of: G-RNTI, TMGI, session identifier, MBMS service area identifier, and frequency information.

25. The method of claim 24, wherein the method further comprises:

the network device receives first capability information sent by the terminal device, wherein the first capability information is used for indicating at least one of the following:

The frequency band capability supported by the terminal equipment;

the frequency band combining capability supported by the terminal equipment;

the terminal equipment supports CA capability;

the terminal device supports DC capability;

26. The method of claim 23, wherein the first configuration information comprises at least one of:

27. The method of claim 26, wherein the indication information of the MBMS carrier comprises at least one of: serving cell identification information, scell index information.

28. The method of claim 22, wherein the first configuration information is used to determine at least one MBMS carrier, each of the at least one MBMS carrier capable of carrying one or more MBMS services.

29. The method of claim 22, wherein the method further comprises:

the network device sends uplink scheduling information on the unicast carrier or the MBMS carrier;

And the network equipment receives the uplink unicast service data sent by the terminal equipment on the MBMS carrier.

30. The method of claim 22, wherein the method further comprises:

and the network equipment sends second indication information to the terminal equipment, wherein the second indication information is used for indicating the terminal equipment to add a target MBMS carrier and/or delete an original MBMS carrier.

31. The method of claim 22, wherein the third indication information is carried in PDCCH or MAC CE or RRC signaling.

32. The method of claim 23, wherein the first indication information is forwarded by an original base station to a target base station during a handover procedure.

33. A method for transmitting traffic, the method comprising:

the network device transmits MBMS service data on the MBMS BWP and unicast service data on the dedicated BWP, wherein the second configuration information is used to determine a first dedicated BWP list;

the method further comprises the steps of:

the network device receives a second dedicated BWP list transmitted by the terminal device, wherein the second dedicated BWP list is a subset belonging to the first dedicated BWP list, and each dedicated BWP in the second dedicated BWP list and the MBMS BWP can be received simultaneously by the terminal device.

34. The method of claim 33, wherein the method further comprises:

35. The method of claim 34, wherein the identification information of the first MBMS service includes at least one of: G-RNTI, TMGI, session identifier, MBMS service area identifier, and frequency information.

36. The method of claim 33, wherein the method further comprises:

the network device sends fourth indication information to the terminal device, the fourth indication information being used to instruct the terminal device to switch from a first dedicated BWP to a second dedicated BWP, wherein the first dedicated BWP and the second dedicated BWP belong to the second dedicated BWP list.

37. The method of claim 33, wherein the second dedicated BWP list is transmitted by the original base station to the target base station during the handover.

38. The method of claim 33, wherein the dedicated BWP and the MBMS BWP belong to independent BWP.

39. The method of claim 33, wherein the dedicated BWP spectral range comprises the MBMS BWP spectral range.

40. The method of claim 34, wherein the first indication information is forwarded by an original base station to a target base station during a handover procedure.

41. A service transmission apparatus applied to a terminal device, the apparatus comprising:

the receiving unit is used for receiving first configuration information sent by the network equipment, wherein the first configuration information is used for determining MBMS carrier waves and unicast carrier waves; receiving MBMS service data on the MBMS carrier and receiving unicast service data on the unicast carrier, wherein the terminal equipment associates a plurality of carriers under a carrier aggregation CA or dual-connection DC architecture, a first part of carriers in the plurality of carriers belong to the MBMS carrier, and a second part of carriers in the plurality of carriers belong to the unicast carrier;

the receiving unit is further configured to receive third indication information sent by the network device, where the third indication information is used to indicate the following:

42. The apparatus of claim 41, wherein the apparatus further comprises:

and the sending unit is used for sending first indication information to the network equipment, wherein the first indication information is used for indicating the identification information of the first MBMS which is ready to be received or is being received by the terminal equipment.

43. The apparatus of claim 42, wherein the identification information of the first MBMS service comprises at least one of: G-RNTI, TMGI, session identifier, MBMS service area identifier, and frequency information.

44. The apparatus of claim 41, wherein the apparatus further comprises:

a transmitting unit configured to transmit, to the network device, first capability information indicating at least one of:

the frequency band capability supported by the terminal equipment;

the frequency band combining capability supported by the terminal equipment;

The terminal equipment supports CA capability;

the terminal device supports DC capability;

45. The apparatus of claim 42, wherein the first configuration information comprises at least one of:

46. The apparatus of claim 45, wherein the indication information of the MBMS carrier comprises at least one of: serving cell identification information, scell index information.

47. The apparatus of claim 41, wherein the first configuration information is used to determine at least one MBMS carrier, each of the at least one MBMS carrier being capable of carrying one or more MBMS services.

48. The apparatus of claim 41, wherein the receiving unit is further configured to receive uplink scheduling information on the unicast carrier or the MBMS carrier;

the apparatus further comprises: and the sending unit is used for sending the uplink unicast service data on the MBMS carrier based on the uplink scheduling information.

49. The apparatus of claim 41, wherein the receiving unit is further configured to receive second indication information sent by the network device, where the second indication information is used to instruct the terminal device to add a target MBMS carrier and/or delete an original MBMS carrier.

50. The apparatus of claim 41, wherein the third indication information is carried in PDCCH or MAC CE or RRC signaling.

51. The apparatus of claim 42, wherein the first indication information is forwarded by the original base station to the target base station during a handover procedure.

52. A service transmission apparatus applied to a terminal device, the apparatus comprising:

a receiving unit, configured to receive second configuration information sent by a network device, where the second configuration information is used to determine MBMS BWP and dedicated BWP; receiving MBMS service data on the MBMS BWP and unicast service data on the dedicated BWP, wherein the second configuration information is used to determine a first dedicated BWP list;

the apparatus further comprises:

a determining unit, configured to determine a second dedicated BWP list from the first dedicated BWP list according to its own radio frequency capability; wherein each dedicated BWP in the second dedicated BWP list and the MBMS BWP are receivable simultaneously by the terminal device;

And a sending unit, configured to send the second dedicated BWP list to the network device.

53. The apparatus of claim 52, wherein the apparatus further comprises:

54. The apparatus of claim 53, wherein the identification information of the first MBMS service comprises at least one of: G-RNTI, TMGI, session identifier, MBMS service area identifier, and frequency information.

55. The apparatus of claim 52, wherein the receiving unit is further configured to receive fourth indication information sent by the network device, the fourth indication information being configured to instruct the terminal device to switch from a first dedicated BWP to a second dedicated BWP, wherein the first dedicated BWP and the second dedicated BWP belong to the second dedicated BWP list.

56. The apparatus of claim 52, wherein the apparatus further comprises:

an updating unit, configured to update, if the terminal device updates from receiving a first MBMS service to receiving a second MBMS service, the second dedicated BWP list based on an MBMS BWP corresponding to the second MBMS service;

The sending unit is further configured to send the updated second dedicated BWP list and/or the identification information of the second MBMS service to the network device.

57. The apparatus of claim 56, wherein the second MBMS service is an MBMS service that the terminal device is ready to receive or is receiving.

58. The apparatus of claim 52, wherein the second dedicated BWP list is transmitted by the original base station to the target base station during the handover.

59. The apparatus of claim 52, wherein the dedicated BWP and the MBMS BWP belong to independent BWP.

60. The apparatus of claim 52, wherein the spectral range of the dedicated BWP comprises the spectral range of the MBMS BWP.

61. The apparatus of claim 53, wherein the first indication information is forwarded by an original base station to a target base station during a handover procedure.

62. A traffic transmission apparatus for use in a network device, the apparatus comprising:

a sending unit, configured to send first configuration information to a terminal device, where the first configuration information is used to determine a multimedia broadcast multicast service MBMS carrier and a unicast carrier; transmitting MBMS service data on the MBMS carrier and transmitting unicast service data on the unicast carrier, wherein the terminal equipment associates a plurality of carriers under a carrier aggregation CA or dual-connection DC architecture, a first part of carriers in the plurality of carriers belong to the MBMS carrier, and a second part of carriers in the plurality of carriers belong to the unicast carrier;

The sending unit is further configured to send third indication information to the terminal device, where the third indication information is used to indicate the following:

63. The apparatus of claim 62, wherein the apparatus further comprises:

and the receiving unit is used for receiving first indication information sent by the terminal equipment, wherein the first indication information is used for indicating the terminal equipment to prepare to receive or receive the identification information of the first MBMS.

64. The apparatus of claim 63, wherein the identification information of the first MBMS service comprises at least one of: G-RNTI, TMGI, session identifier, MBMS service area identifier, and frequency information.

65. The apparatus of claim 62, wherein the apparatus further comprises:

a receiving unit, configured to receive first capability information sent by the terminal device, where the first capability information is used to indicate at least one of the following:

the frequency band capability supported by the terminal equipment;

the frequency band combining capability supported by the terminal equipment;

the terminal equipment supports CA capability;

the terminal device supports DC capability;

66. The apparatus of claim 63, wherein the first configuration information comprises at least one of:

67. The apparatus of claim 65, wherein the indication information for the MBMS carrier comprises at least one of: serving cell identification information, scell index information.

68. The apparatus of claim 62, wherein the first configuration information is used to determine at least one MBMS carrier, each of the at least one MBMS carrier capable of carrying one or more MBMS services.

69. The apparatus of claim 62, wherein the transmitting unit is further configured to transmit uplink scheduling information on the unicast carrier or the MBMS carrier;

the apparatus further comprises: and the receiving unit is used for receiving the uplink unicast service data sent by the terminal equipment on the MBMS carrier.

70. The apparatus of claim 62, wherein the transmitting unit is further configured to transmit second indication information to the terminal device, where the second indication information is used to instruct the terminal device to add a target MBMS carrier and/or delete an original MBMS carrier.

71. The apparatus of claim 62, wherein the third indication information is carried in PDCCH or MAC CE or RRC signaling.

72. The apparatus of claim 63, wherein the first indication information is forwarded by an original base station to a target base station during a handover procedure.

73. A traffic transmission apparatus for use in a network device, the apparatus comprising:

a transmitting unit configured to transmit second configuration information to the terminal device, the second configuration information being used to determine MBMS BWP and dedicated BWP; transmitting MBMS service data on the MBMS BWP and unicast service data on the dedicated BWP, wherein the second configuration information is used to determine a first dedicated BWP list;

The apparatus further comprises: a receiving unit, configured to receive a second dedicated BWP list sent by the terminal device, where the second dedicated BWP list is a subset belonging to the first dedicated BWP list, and each dedicated BWP in the second dedicated BWP list and the MBMS BWP are capable of being received simultaneously by the terminal device.

74. The apparatus of claim 73, wherein the apparatus further comprises:

75. The apparatus of claim 74, wherein the identification information of the first MBMS service comprises at least one of: G-RNTI, TMGI, session identifier, MBMS service area identifier, and frequency information.

76. The apparatus of claim 73, wherein the transmitting unit is further configured to transmit fourth indication information to the terminal device, the fourth indication information being configured to instruct the terminal device to switch from a first dedicated BWP to a second dedicated BWP, wherein the first dedicated BWP and the second dedicated BWP belong to the second dedicated BWP list.

77. The apparatus of claim 73, wherein the second dedicated BWP list is transmitted by the original base station to the target base station during the handover.

78. The apparatus of claim 73, wherein the dedicated BWP and the MBMS BWP belong to separate BWP.

79. The apparatus of claim 73, wherein the spectral range of the dedicated BWP comprises the spectral range of the MBMS BWP.

80. The apparatus of claim 74, wherein the first indication information is forwarded by an original base station to a target base station during a handover procedure.

81. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory for performing the method according to claim 1.

82. A network device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory for performing the method according to claim 22.

83. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of claim 1.

84. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of claim 22.

85. A computer readable storage medium storing a computer program for causing a computer to perform the method of claim 1.

86. A computer readable storage medium storing a computer program for causing a computer to perform the method of claim 22.