WO2021138805A1 - Method and apparatus for synchronously scheduling a service, and communication device - Google Patents

Abstract

Provided are a method and apparatus for synchronously scheduling a service, and a communication device. The method comprises: a distributed unit (DU) receiving MBMS scheduling information sent by a centralized unit (CU); and the DU sending an MBMS PDCCH and/or MBMS service data according to the MBMS scheduling information.

Description

Method and device for business synchronization scheduling, and communication equipment Technical field

The embodiments of the application relate to the field of mobile communication technology, and in particular to a method and device for service synchronization scheduling, and communication equipment.

Background technique

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

In the New Radio (NR) system, many scenarios need to support the service requirements of multicast and broadcast, such as the Internet of Vehicles, the industrial Internet, and so on. So it is necessary to introduce MBMS in NR. Cell edge performance is generally poor for MBMS services, so if the content of transmission between cells is synchronized, terminal equipment can receive the same data from two cells at the cell edge at the same time, thereby improving data transmission by combining gains However, how to achieve synchronous transmission of content between two adjacent cells is a problem.

Summary of the invention

The embodiments of the present application provide a method and device for service synchronization scheduling, and communication equipment.

The service synchronization scheduling method provided by the embodiment of the present application includes:

A distributed unit (Distributed Unit, DU) receives MBMS scheduling information sent by a central unit (Centralized Unit, CU);

The DU sends MBMS PDCCH and/or MBMS service data based on the MBMS scheduling information.

The service synchronization scheduling method provided by the embodiment of the present application includes:

The CU sends MBMS scheduling information to at least one DU, where the MBMS scheduling information is used for each DU in the at least one DU to send MBMS PDCCH and/or MBMS service data.

The service synchronization scheduling device provided by the embodiment of the present application is applied to the DU, and the device includes:

The receiving unit is used to receive the MBMS scheduling information sent by the CU;

The sending unit is configured to send MBMS PDCCH and/or MBMS service data based on the MBMS scheduling information.

The service synchronization scheduling device provided by the embodiment of the present application is applied to a CU, and the device includes:

The sending unit is configured to send MBMS scheduling information to at least one DU, where the MBMS scheduling information is used for each DU in the at least one DU to send MBMS PDCCH and/or MBMS service data.

The communication device provided by the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the aforementioned business synchronization scheduling method.

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

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

The computer-readable storage medium provided by the embodiments of the present application is used to store a computer program, and the computer program enables a computer to execute the foregoing business synchronization scheduling method.

The computer program product provided by the embodiment of the present application includes computer program instructions that cause a computer to execute the above-mentioned business synchronization scheduling method.

The computer program provided in the embodiment of the present application, when it runs on a computer, causes the computer to execute the foregoing business synchronization scheduling method.

Through the above technical solution, the CU configures MBMS scheduling information for at least one DU, so that each DU in at least one DU can send MBMS PDCCH and/or MBMS service data synchronously based on the same MBMS scheduling information, realizing synchronization of MBMS services Dynamic scheduling. On the other hand, because different cells are covered by different DUs, the synchronous transmission of content between cells when supporting MBMS service transmission in the NR system is realized, and the transmission reliability of MBMS service data at the cell edge is improved.

Description of the drawings

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

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

FIG. 2 is a schematic diagram of Beam sweeping provided by an embodiment of the application;

FIG. 3 is a schematic diagram of an SSB provided by an embodiment of the application;

FIG. 4 is a schematic diagram of the SSB burst set period provided by an embodiment of the application;

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

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

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

FIG. 8 is a schematic flowchart of a service synchronization scheduling method provided by an embodiment of the application;

FIG. 9 is a diagram of a network communication architecture provided by an embodiment of the application;

FIG. 10 is a schematic diagram 1 of the structural composition of a service synchronization scheduling apparatus provided by an embodiment of this application;

FIG. 11 is a schematic diagram 2 of the structural composition of the service synchronization scheduling apparatus provided by an embodiment of the application;

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

FIG. 13 is a schematic structural diagram of a chip according to an embodiment of the present application;

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

Detailed ways

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

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

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

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

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

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

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

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

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

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

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

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

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

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

RRC status

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

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

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

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

Beam sweeping

NR will be deployed at high frequencies in the future. In order to improve coverage, in 5G, a beam sweeping mechanism is introduced to meet the coverage requirements (using space for coverage and time for space), as shown in Figure 2. After the introduction of beam sweeping, synchronization signals need to be sent in each beam direction. 5G synchronization signals are given in the form of synchronization signal blocks (SS/PBCH block, SSB), including primary synchronization signals (Primary Synchronization Signal, PSS), The secondary synchronization signal (Secondary Synchronization Signal, SSS) and the physical broadcast channel (Physical Broadcast Channel, PBCH) are shown in Figure 3. The 5G synchronization signal periodically appears in the time domain in the form of a synchronization signal burst set (SS burst), as shown in Figure 4.

The actual number of beams transmitted in each cell is determined by the network side configuration, but the frequency point where the cell is located determines the maximum number of beams that can be configured, as shown in Table 1 below.

Frequency Range	L (the maximum number of beams)
up to 3(2.4)GHz	4
3(2.4)GHz-6GHz	8
6GHz—52.6GHz	64

Table 1

Bandwidth part (BWP)

The maximum channel bandwidth in 5G can be 400MHz (ie, broadband). Compared with the maximum channel bandwidth of 20MHz in LTE, the maximum channel bandwidth in 5G is very large. If the UE keeps working on a broadband carrier (that is, the maximum channel bandwidth), the power consumption of the UE is very large. Therefore, it is recommended that the radio frequency bandwidth of the UE can be adjusted according to the actual throughput of the UE. For this reason, the concept of BWP is introduced. The motivation for introducing BWP is to optimize the power consumption of the UE. For example, the rate requirement of the UE is very low. You can configure the UE with a smaller bandwidth (that is, a BWP with a smaller bandwidth). If the UE has a high rate requirement, you can configure the UE with a larger bandwidth (that is, a BWP with a larger bandwidth). . If the UE supports a high rate or operates in a carrier aggregation (CA) mode, multiple BWPs can be configured for the UE. In addition, another purpose of BWP is to trigger the coexistence of multiple parameter sets (numerology) in a cell, for example, BWP1 corresponds to numerology1, and BWP2 corresponds to numerology2.

An idle or inactive UE camps on the initial BWP (initial BWP). The initial BWP is visible to the idle or inactive UE. The UE can obtain the Master Information Block (MIB) on the initial BWP. ), remaining minimum system information (Remaining Minimum system Information, RMSI), other system information (Other System Information, OSI), and paging (paging) information.

MBMS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

In NR, many scenarios need to support the service requirements of multicast and broadcast, such as the Internet of Vehicles and the Industrial Internet. Therefore, it is necessary to introduce MBMS into NR. However, the transmission of MBMS services cannot change the transmission scheduling information according to the channel environment of a specific terminal device to achieve the reliability of data transmission, such as changing the TB size or MCS. Therefore, the cell edge generally has poor performance for MBMS services. If the content of transmission between cells is synchronized, that is, neighboring cells send the same data in the same time-frequency resource, so that the terminal device can receive the same data from the two cells at the cell edge at the same time, thereby increasing the gain by combining The reliability of data transmission, but how to achieve synchronous transmission of content between neighboring cells needs to be clear. To this end, the following technical solutions of the embodiments of the present application are proposed.

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

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

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

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

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

In the embodiments of the present application, the network side has a CU and DU separated architecture, which can be regarded as a network device including a CU and at least one DU. In this case, the MBMS-related configuration is configured by the CU for each DU in the at least one DU. . It should be noted that in the case of multiple DUs, the MBMS-related configuration configured by the CU for the multiple DUs is the same. Different DUs can cover different cells. Generally, the cells covered by multiple DUs belonging to the same CU are neighboring cells. The content synchronization between neighboring cells can be implemented by using the DU to send MBMS scheduling information to at least one of its associated CUs, which is described in detail below.

FIG. 8 is a schematic flowchart of a service synchronization scheduling method provided by an embodiment of the application. As shown in FIG. 8, the service synchronization scheduling method includes the following steps:

Step 801: The CU sends MBMS scheduling information to at least one DU, and the DU receives the MBMS scheduling information sent by the CU.

Step 802: The DU sends MBMS PDCCH and/or MBMS service data based on the MBMS scheduling information.

In the embodiment of the present application, the network side adopts a CU and DU separation architecture, where both CU and DU belong to entities on the base station side, and one CU may be associated with one or more DUs. Among them, the protocol stack responsible for the CU includes: SDAP layer and PDCP layer. The protocol stack that DU is responsible for includes: RLC layer, MAC layer and PHY layer.

In an optional implementation manner, the base station is a gNB, and accordingly, the CU may also be referred to as gNB CU, and the DU may also be referred to as gNB DU. As shown in Figure 9, the gNB CU and the core network side transmit MBMS service data through a GTP tunnel. The gNB CU and gNB DU1 and gNB DU2 also transmit MBMS service data through the GTP tunnel. DU1 and DU2 send MBMS service data, so that the terminal device can receive the MBMS service data.

In the embodiment of the present application, the CU may configure MBMS PDCCH resource configuration information (may be referred to as pre-configuration information) for at least one DU in advance. Specifically, the CU sends MBMS PDCCH resource configuration information to the at least one DU,

For each DU, the DU receives MBMS PDCCH resource configuration information sent by the CU, where the MBMS PDCCH resource configuration information includes at least one of the following:

MBMS control resource set (MBMS CORESET) configuration;

MBMS search space (MBMS search Space) configuration;

MBMS service information associated with the MBMS PDCCH resource configuration information, for example, MBMS service identification information;

MBMS PDCCH resource scheduling period configuration.

In specific implementation, referring to FIG. 9, the gNB CU pre-configures the MBMS PDCCH resource configuration information to each of the at least one DU through the F1 interface. Here, the F1 interface is the interface between gNB CU and gNB DU.

In an optional manner, the MBMS PDCCH resource configuration information may be associated with one or more MBMS service information, where each MBMS service information is associated with one MBMS service.

In an optional manner, the scheduling period configuration of the MBMS PDCCH resource is used to determine the MBMS PDCCH time window; the scheduling period configuration of the MBMS PDCCH resource includes at least one of the following:

MBMS PDCCH time window period;

MBMS PDCCH time window offset;

The duration of the MBMS PDCCH time window.

It should be noted that the MBMS PDCCH time window appears periodically in the time domain, and the time domain resources in the MBMS PDCCH time window are used to transmit the MBMS PDCCH.

Further, optionally, the scheduling period configuration of the MBMS PDCCH resource further includes: MBMS service information associated with the MBMS PDCCH time window.

For example: MBMS service information of the first MBMS service associated with the first MBMS PDCCH time window, and MBMS service information of the second MBMS service associated with the second MBMS PDCCH time window.

In the embodiment of the present application, on the basis that the CU configures MBMS PDCCH resource configuration information for at least one DU in advance, the CU may also dynamically send MBMS scheduling information to the at least one DU. For each DU, the DU receives The MBMS scheduling information sent by the CU. Optionally, the MBMS scheduling information includes at least one of the following:

MBMS business scheduling information;

Resource information of MBMS PDCCH, where the MBMS PDCCH is used to carry MBMS service scheduling information;

G-RNTI information, the G-RNTI information is used to scramble MBMS PDCCH.

Further, optionally, the MBMS service scheduling information includes but is not limited to at least one of the following: time domain location information of the MBMS service, frequency domain location information of the MBMS service, MCS of the MBMS service, and TB size of the MBMS service.

Further, optionally, the resource information of the MBMS PDCCH includes at least one of the following:

The identification information (such as CORSET id) of the MBMS CORESET where the MBMS PDCCH is located;

Identification information (such as search space id) of the MBMS search Space where the MBMS PDCCH is located;

MBMS PDCCH location information in time domain.

Here, the time domain location information where the MBMS PDCCH is located includes at least one of the following:

The number of the SFN where the MBMS PDCCH is located;

The number of the time slot where the MBMS PDCCH is located;

The number of the symbol where the MBMS PDCCH is located;

PDCCH occasion (PDCCH occasion) information occupied by MBMS PDCCH;

SSB index information associated with the PDCCH occurrence.

In the above solution, MBMS PDCCH can occupy one or more PDCCH occasions; alternatively, for the case where MBMS PDCCH occupies multiple PDCCH occasions, multiple PDCCH occasions can be consecutive multiple PDCCH occasions; here, if MBMS PDCCH occupies more occasions For each PDCCH occurrence, the SSB index information associated with each PDCCH occurrence needs to be given.

It should be noted that the PDCCH occurrences are periodically distributed in a certain time range and/or spectrum range, and are numbered according to certain rules. Further, optionally, one MBMS occasion may include several symbols or several time slots.

Further, optionally, the CU configures G-RNTI information for scheduling the service for each MBMS service, where different G-RNTI information is associated with different MBMS services. In order to ensure the uniqueness of the G-RNTI information allocated for the MBMS service, the following methods can be used to achieve:

Manner 1: If the DU determines that the G-RNTI information allocated for the first MBMS service has been allocated to the second MBMS service, the DU requests the CU to re-allocate G-RNTI information for the first MBMS service Or, the DU requests the CU to change the G-RNTI information associated with the second MBMS service.

Here, the allocated G-RNTI information of the first MBMS service has been allocated to the second MBMS service means: the value of the allocated G-RNTI information of the first MBMS service has been occupied by the G-RNTI of the second MBMS service .

Manner 2: If the DU determines that the G-RNTI information allocated for the first MBMS service has been allocated to the first user, the DU requests the CU to re-allocate the G-RNTI information for the first MBMS service, Alternatively, the DU requests the CU to change the RNTI information used by the first user, or the DU changes the RNTI information used by the first user.

Here, the RNTI information used by the first user may be C-RNTI information. The allocated G-RNTI information of the first MBMS service has been allocated to the first user means that the value of the allocated G-RNTI information of the first MBMS service has been occupied by the C-RNTI of the first user.

Manner 3: The DU receives first indication information sent by the CU, where the first indication information is used to indicate the value range of G-RNTI; wherein, the value of the G-RNTI information in the MBMS scheduling information The value belongs to the value range.

Here, the CU configures a value range for the DU, and the values within the value range are only used to configure the G-RNTI. In this way, conflicts between the values of other RNTIs and the values of G-RNTI can be avoided.

In the embodiment of the present application, after obtaining the MBMS scheduling information, the DU sends the MBMS PDCCH and/or MBMS service data based on the MBMS scheduling information, which will be described in detail below.

1) Control plane: MBMS PDCCH transmission

The DU scrambles the MBMS PDCCH based on the G-RNTI information, where the MBMS PDCCH carries the MBMS service scheduling information; the DU is based on the resource information of the MBMS PDCCH and is located at a designated resource location Send the scrambled MBMS PDCCH.

It should be noted that at least one of the G-RNTI information, MBMS service scheduling information, and MBMS PDCCH resource information here is carried in the MBMS scheduling information.

It should be noted that, after the DU scrambles the MBMS PDCCH based on the G-RNTI information, it needs to undergo physical layer processing before it is sent on the designated resource location. Here, the physical layer processing includes, but is not limited to, modulation and coding processing.

2) User plane: sending of MBMS service data

After the DU receives the MBMS service data sent by the CU, it determines the MBMS service scheduling information that matches the MBMS service data; the DU performs data on the MBMS service data based on the matched MBMS service scheduling information Processing, and sending the processed MBMS service data on the designated resource location.

Further, optionally, the matched MBMS service scheduling information is:

The last MBMS service scheduling information received by the DU from the CU before the DU receives the MBMS service data; or,

The first MBMS service scheduling information received by the DU from the CU after receiving the MBMS service data; or,

The first unused MBMS service scheduling information received by the DU from the CU.

Specifically, referring to FIG. 9, the gNB CU sends MBMS service data to the DU through the GTP tunnel. Among them, the GTP tunnel is specifically an F1GTP tunnel. After the gNB DU receives the MBMS service data, it has the following three processing methods:

A) The gNB DU matches the newly received MBMS service data to the latest MBMS service scheduling information from the gNB CU (that is, the last MBMS service scheduling information received from the CU before receiving the MBMS service data), and uses the MBMS The service scheduling information performs physical layer processing on the MBMS service data, and sends the processed MBMS service data according to the time-frequency resources given by the MBMS service scheduling information. Here, the physical layer processing includes, but is not limited to, modulation and coding processing.

B) The gNB DU matches the newly received MBMS service data to the first MBMS service scheduling information after the MBMS service data from the gNB CU (that is, the first MBMS service received from the CU after receiving the MBMS service data) Scheduling information), using the MBMS service scheduling information to perform physical layer processing on the MBMS service data, and sending the processed MBMS service data according to the time-frequency resources given according to the MBMS service scheduling information. Here, the physical layer processing includes, but is not limited to, modulation and coding processing.

C) gNB DU matches the newly received MBMS service data to the first unused MBMS service scheduling information from gNB CU (that is, the oldest unused MBMS service scheduling information), and uses this MBMS service The scheduling information performs physical layer processing on the MBMS service data, and sends the processed MBMS service data according to the time-frequency resources given by the MBMS service scheduling information. Here, the physical layer processing includes, but is not limited to, modulation and coding processing.

In an optional implementation manner of the present application, the DU receives a CSI report sent by at least one terminal device, and the at least one terminal device belongs to a receiving group of the MBMS service data.

In an optional implementation manner of the present application, the DU determines the recommended MBMS scheduling information, and sends the recommended MBMS scheduling information to the CU; wherein, the recommended MBMS scheduling information is used for the CU to adjust the direction MBMS scheduling information issued by the DU. Further, optionally, the DU determines recommended MBMS scheduling information based on the received CSI report.

Referring to FIG. 9, the terminal device can feed back the channel quality to the gNB DU during the period of receiving the MBMS service data, that is, the terminal device reports the CSI report to the DU. After the gNB DU receives the CSI report sent by the terminal device, it gives the recommended MBMS scheduling information according to the CSI report fed back by one or more terminal devices in the MBMS service receiving group, and sends the recommended MBMS scheduling information to gNB CU. The gNB CU determines the MBMS scheduling information according to the recommended MBMS scheduling information sent by one or more gNB DUs, and sends it to the gNB DU for scheduling new MBMS service data.

In the technical solution of the embodiment of the present application, multiple DUs receive the MBMS scheduling information sent by the CU, and send MBMS PDCCH and/or MBMS service data based on the MBMS scheduling information, thereby achieving content synchronization between neighboring cells.

FIG. 10 is a schematic diagram 1 of the structural composition of a service synchronization scheduling device provided by an embodiment of the application, which is applied to a DU. As shown in FIG. 10, the service synchronization scheduling device includes:

The receiving unit 1001 is configured to receive MBMS scheduling information sent by the CU;

The sending unit 1002 is configured to send MBMS PDCCH and/or MBMS service data based on the MBMS scheduling information.

In an optional implementation manner, the receiving unit 1001 is further configured to receive MBMS PDCCH resource configuration information sent by the CU, where the MBMS PDCCH resource configuration information includes at least one of the following:

MBMS CORESET configuration;

MBMS search Space configuration;

MBMS service information associated with the MBMS PDCCH resource configuration information;

MBMS PDCCH resource scheduling period configuration.

In an optional implementation manner, the scheduling period configuration of the MBMS PDCCH resource is used to determine the MBMS PDCCH time window;

The scheduling period configuration of the MBMS PDCCH resource includes at least one of the following:

MBMS PDCCH time window period;

MBMS PDCCH time window offset;

The length of the MBMS PDCCH time window.

In an optional implementation manner, the scheduling period configuration of the MBMS PDCCH resource further includes:

MBMS service information associated with the MBMS PDCCH time window.

In an optional implementation manner, the MBMS scheduling information includes at least one of the following:

MBMS business scheduling information;

Resource information of MBMS PDCCH, where the MBMS PDCCH is used to carry MBMS service scheduling information;

G-RNTI information, the G-RNTI information is used to scramble MBMS PDCCH.

In an optional implementation manner, the resource information of the MBMS PDCCH includes at least one of the following:

The identification information of the MBMS CORESET where the MBMS PDCCH is located;

The identification information of the MBMS search Space where the MBMS PDCCH is located;

MBMS PDCCH location information in time domain.

In an optional implementation manner, the time domain location information where the MBMS PDCCH is located includes at least one of the following:

The number of the SFN where the MBMS PDCCH is located;

The number of the time slot where the MBMS PDCCH is located;

The number of the symbol where the MBMS PDCCH is located;

PDCCH occasion information occupied by MBMS PDCCH;

SSB index information associated with the PDCCH occurrence.

In an optional implementation manner, different G-RNTI information is associated with different MBMS services; the apparatus further includes:

The replacement unit (not shown in the figure) is used to request the CU to re-allocate G for the first MBMS service if it is determined that the G-RNTI information allocated for the first MBMS service has been allocated to the second MBMS service. -RNTI information, or request the CU to change the G-RNTI information associated with the second MBMS service.

In an optional embodiment, the device further includes:

The replacement unit (not shown in the figure) is used to request the CU to re-allocate G-RNTI information for the first MBMS service if it is determined that the G-RNTI information allocated for the first MBMS service has been allocated to the first user. RNTI information, or request the CU to change the RNTI information used by the first user, or change the RNTI information used by the first user.

In an optional implementation manner, the receiving unit 1001 is further configured to receive first indication information sent by the CU, where the first indication information is used to indicate the value range of G-RNTI; wherein, the MBMS The value of the G-RNTI information in the scheduling information belongs to the value range.

In an optional embodiment, the device further includes:

The processing unit 1003 is configured to scramble the MBMS PDCCH based on the G-RNTI information, where the MBMS PDCCH carries the MBMS service scheduling information;

The sending unit 1002 is configured to send the scrambled MBMS PDCCH at a designated resource location based on the resource information of the MBMS PDCCH.

In an optional embodiment, the device further includes:

The processing unit 1003 is configured to determine MBMS service scheduling information that matches the MBMS service data; perform data processing on the MBMS service data based on the matched MBMS service scheduling information;

The sending unit 1002 is configured to send the processed MBMS service data at a designated resource location.

In an optional implementation manner, the matched MBMS service scheduling information is:

The last MBMS service scheduling information received by the DU from the CU before the DU receives the MBMS service data; or,

The first MBMS service scheduling information received by the DU from the CU after receiving the MBMS service data; or,

The first unused MBMS service scheduling information received by the DU from the CU.

In an optional implementation manner, the receiving unit 1001 is further configured to receive a CSI report sent by at least one terminal device, and the at least one terminal device belongs to the MBMS service data receiving group.

In an optional embodiment, the device further includes:

The determining unit 1004 is used to determine recommended MBMS scheduling information;

The sending unit 1002 is further configured to send the recommended MBMS scheduling information to the CU; wherein the recommended MBMS scheduling information is used by the CU to adjust the MBMS scheduling information delivered to the DU.

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

FIG. 11 is a schematic diagram 2 of the structural composition of a service synchronization scheduling device provided by an embodiment of the application, which is applied to a CU. As shown in FIG. 11, the service synchronization scheduling device includes:

The sending unit 1101 is configured to send MBMS scheduling information to at least one DU, where the MBMS scheduling information is used for each DU in the at least one DU to send MBMS PDCCH and/or MBMS service data.

In an optional implementation manner, the sending unit 1101 is further configured to send MBMS PDCCH resource configuration information to the at least one DU, where the MBMS PDCCH resource configuration information includes at least one of the following:

MBMS CORESET configuration;

MBMS search Space configuration;

MBMS service information associated with the MBMS PDCCH resource configuration information;

MBMS PDCCH resource scheduling period configuration.

In an optional implementation manner, the scheduling period configuration of the MBMS PDCCH resource is used to determine the MBMS PDCCH time window;

The scheduling period configuration of the MBMS PDCCH resource includes at least one of the following:

MBMS PDCCH time window period;

MBMS PDCCH time window offset;

The length of the MBMS PDCCH time window.

In an optional implementation manner, the scheduling period configuration of the MBMS PDCCH resource further includes:

MBMS service information associated with the MBMS PDCCH time window.

In an optional implementation manner, the MBMS scheduling information includes at least one of the following:

MBMS business scheduling information;

Resource information of MBMS PDCCH, where the MBMS PDCCH is used to carry MBMS service scheduling information;

G-RNTI information, the G-RNTI information is used to scramble MBMS PDCCH.

In an optional implementation manner, the resource information of the MBMS PDCCH includes at least one of the following:

The identification information of the MBMS CORESET where the MBMS PDCCH is located;

The identification information of the MBMS search Space where the MBMS PDCCH is located;

MBMS PDCCH location information in time domain.

In an optional implementation manner, the time domain location information where the MBMS PDCCH is located includes at least one of the following:

The number of the SFN where the MBMS PDCCH is located;

The number of the time slot where the MBMS PDCCH is located;

The number of the symbol where the MBMS PDCCH is located;

PDCCH occasion information occupied by MBMS PDCCH;

SSB index information associated with the PDCCH occurrence.

In an optional implementation manner, different G-RNTI information is associated with different MBMS services;

The sending unit 1101 is further configured to send first indication information to the at least one DU, where the first indication information is used to indicate the value range of G-RNTI; wherein, the G-RNTI in the MBMS scheduling information -The value of the RNTI information belongs to the value range.

In an optional embodiment, the device further includes:

The receiving unit 1102 is configured to receive recommended MBMS scheduling information sent by the at least one DU;

The adjusting unit 1103 is configured to adjust the MBMS scheduling information delivered to the DU based on the recommended MBMS scheduling information.

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

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

Optionally, as shown in FIG. 12, the communication device 1200 may further include a memory 1220. The processor 1210 can call and run a computer program from the memory 1220 to implement the method in the embodiment of the present application.

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

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

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

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

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

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

Optionally, as shown in FIG. 13, the chip 1300 may further include a memory 1320. The processor 1310 can call and run a computer program from the memory 1320 to implement the method in the embodiment of the present application.

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

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

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

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

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

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

FIG. 14 is a schematic block diagram of a communication system 1400 according to an embodiment of the present application. As shown in FIG. 14, the communication system 1400 includes a terminal device 1410 and a network device 1420.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims (53)

1. A business synchronization scheduling method, the method includes:

   The distribution unit DU receives the multimedia broadcast multicast service MBMS scheduling information sent by the central unit CU;

   The DU sends MBMS PDCCH and/or MBMS service data based on the MBMS scheduling information.
2. The method according to claim 1, wherein the method further comprises:

   The DU receives MBMS PDCCH resource configuration information sent by the CU, where the MBMS PDCCH resource configuration information includes at least one of the following:

   MBMS control resource set MBMS CORESET configuration;

   MBMS search space MBMS search Space configuration;

   MBMS service information associated with the MBMS PDCCH resource configuration information;

   MBMS PDCCH resource scheduling period configuration.
3. The method according to claim 2, wherein the scheduling period configuration of the MBMS PDCCH resource is used to determine the MBMS PDCCH time window;

   The scheduling period configuration of the MBMS PDCCH resource includes at least one of the following:

   MBMS PDCCH time window period;

   MBMS PDCCH time window offset;

   The length of the MBMS PDCCH time window.
4. The method according to claim 3, wherein the scheduling period configuration of the MBMS PDCCH resource further comprises:

   MBMS service information associated with the MBMS PDCCH time window.
5. The method according to any one of claims 1 to 4, wherein the MBMS scheduling information includes at least one of the following:

   MBMS business scheduling information;

   Resource information of MBMS PDCCH, where the MBMS PDCCH is used to carry MBMS service scheduling information;

   G-RNTI information, the G-RNTI information is used to scramble MBMS PDCCH.
6. The method according to claim 5, wherein the resource information of the MBMS PDCCH includes at least one of the following:

   The identification information of the MBMS CORESET where the MBMS PDCCH is located;

   The identification information of the MBMS search Space where the MBMS PDCCH is located;

   MBMS PDCCH location information in time domain.
7. The method according to claim 6, wherein the time domain location information where the MBMS PDCCH is located includes at least one of the following:

   The number of the SFN where the MBMS PDCCH is located;

   The number of the time slot where the MBMS PDCCH is located;

   The number of the symbol where the MBMS PDCCH is located;

   PDCCH occasion information occupied by MBMS PDCCH;

   SSB index information associated with the PDCCH occurrence.
8. The method according to any one of claims 5 to 7, wherein different G-RNTI information is associated with different MBMS services; the method further comprises:

   If the DU determines that the G-RNTI information allocated for the first MBMS service has been allocated to the second MBMS service, the DU requests the CU to re-allocate G-RNTI information for the first MBMS service, or, The DU requests the CU to change the G-RNTI information associated with the second MBMS service.
9. The method according to any one of claims 5 to 7, wherein the method further comprises:

   If the DU determines that the G-RNTI information allocated for the first MBMS service has been allocated to the first user, the DU requests the CU to re-allocate G-RNTI information for the first MBMS service, or The DU requests the CU to change the RNTI information used by the first user, or the DU changes the RNTI information used by the first user.
10. The method according to any one of claims 5 to 7, wherein the method further comprises:

    The DU receives first indication information sent by the CU, where the first indication information is used to indicate the value range of G-RNTI; wherein the value of the G-RNTI information in the MBMS scheduling information belongs to The value range.
11. The method according to any one of claims 5 to 10, wherein the DU sending MBMS PDCCH based on the MBMS scheduling information includes:

    The DU scrambles the MBMS PDCCH based on the G-RNTI information, where the MBMS PDCCH carries the MBMS service scheduling information;

    The DU sends the scrambled MBMS PDCCH at a designated resource location based on the resource information of the MBMS PDCCH.
12. The method according to any one of claims 5 to 11, wherein the DU sending MBMS service data based on the MBMS scheduling information includes:

    After receiving the MBMS service data sent by the CU, the DU determines MBMS service scheduling information that matches the MBMS service data;

    The DU performs data processing on the MBMS service data based on the matched MBMS service scheduling information, and sends the processed MBMS service data at a designated resource location.
13. The method according to claim 12, wherein the matched MBMS service scheduling information is:

    The last MBMS service scheduling information received by the DU from the CU before the DU receives the MBMS service data; or,

    The first MBMS service scheduling information received by the DU from the CU after receiving the MBMS service data; or,

    The first unused MBMS service scheduling information received by the DU from the CU.
14. The method according to any one of claims 1 to 13, wherein the method further comprises:

    The DU receives a CSI report sent by at least one terminal device, and the at least one terminal device belongs to a receiving group of the MBMS service data.
15. The method according to any one of claims 1 to 14, wherein the method further comprises:

    The DU determines the recommended MBMS scheduling information, and sends the recommended MBMS scheduling information to the CU; where the recommended MBMS scheduling information is used by the CU to adjust the MBMS scheduling information delivered to the DU.
16. A business synchronization scheduling method, the method includes:

    The CU sends MBMS scheduling information to at least one DU, where the MBMS scheduling information is used for each DU in the at least one DU to send MBMS PDCCH and/or MBMS service data.
17. The method according to claim 16, wherein the method further comprises:

    The CU sends MBMS PDCCH resource configuration information to the at least one DU, where the MBMS PDCCH resource configuration information includes at least one of the following:

    MBMS CORESET configuration;

    MBMS search Space configuration;

    MBMS service information associated with the MBMS PDCCH resource configuration information;

    MBMS PDCCH resource scheduling period configuration.
18. The method according to claim 17, wherein the scheduling period configuration of the MBMS PDCCH resource is used to determine the MBMS PDCCH time window;

    The scheduling period configuration of the MBMS PDCCH resource includes at least one of the following:

    MBMS PDCCH time window period;

    MBMS PDCCH time window offset;

    The length of the MBMS PDCCH time window.
19. The method according to claim 18, wherein the scheduling period configuration of the MBMS PDCCH resource further comprises:

    MBMS service information associated with the MBMS PDCCH time window.
20. The method according to any one of claims 16 to 19, wherein the MBMS scheduling information includes at least one of the following:

    MBMS business scheduling information;

    Resource information of MBMS PDCCH, where the MBMS PDCCH is used to carry MBMS service scheduling information;

    G-RNTI information, the G-RNTI information is used to scramble MBMS PDCCH.
21. The method according to claim 20, wherein the resource information of the MBMS PDCCH includes at least one of the following:

    The identification information of the MBMS CORESET where the MBMS PDCCH is located;

    The identification information of the MBMS search Space where the MBMS PDCCH is located;

    MBMS PDCCH location information in time domain.
22. The method according to claim 21, wherein the time domain location information where the MBMS PDCCH is located includes at least one of the following:

    The number of the SFN where the MBMS PDCCH is located;

    The number of the time slot where the MBMS PDCCH is located;

    The number of the symbol where the MBMS PDCCH is located;

    PDCCH occasion information occupied by MBMS PDCCH;

    SSB index information associated with the PDCCH occurrence.
23. The method according to any one of claims 20 to 22, wherein different G-RNTI information is associated with different MBMS services;

    The CU sends first indication information to the at least one DU, where the first indication information is used to indicate the value range of G-RNTI; wherein, the value of the G-RNTI information in the MBMS scheduling information It belongs to the stated value range.
24. The method according to any one of claims 16 to 23, wherein the method further comprises:

    The CU receives the recommended MBMS scheduling information sent by the at least one DU, and adjusts the MBMS scheduling information delivered to the DU based on the recommended MBMS scheduling information.
25. A service synchronization scheduling device applied to DU, and the device includes:

    The receiving unit is used to receive the MBMS scheduling information sent by the CU;

    The sending unit is configured to send MBMS PDCCH and/or MBMS service data based on the MBMS scheduling information.
26. The apparatus according to claim 25, wherein the receiving unit is further configured to receive MBMS PDCCH resource configuration information sent by the CU, wherein the MBMS PDCCH resource configuration information includes at least one of the following:

    MBMS CORESET configuration;

    MBMS search Space configuration;

    MBMS service information associated with the MBMS PDCCH resource configuration information;

    MBMS PDCCH resource scheduling period configuration.
27. The apparatus according to claim 26, wherein the scheduling period configuration of the MBMS PDCCH resource is used to determine the MBMS PDCCH time window;

    The scheduling period configuration of the MBMS PDCCH resource includes at least one of the following:

    MBMS PDCCH time window period;

    MBMS PDCCH time window offset;

    The length of the MBMS PDCCH time window.
28. The apparatus according to claim 27, wherein the scheduling period configuration of the MBMS PDCCH resource further comprises:

    MBMS service information associated with the MBMS PDCCH time window.
29. The apparatus according to any one of claims 25 to 28, wherein the MBMS scheduling information includes at least one of the following:

    MBMS business scheduling information;

    Resource information of MBMS PDCCH, where the MBMS PDCCH is used to carry MBMS service scheduling information;

    G-RNTI information, the G-RNTI information is used to scramble MBMS PDCCH.
30. The apparatus according to claim 29, wherein the resource information of the MBMS PDCCH includes at least one of the following:

    The identification information of the MBMS CORESET where the MBMS PDCCH is located;

    The identification information of the MBMS search Space where the MBMS PDCCH is located;

    MBMS PDCCH location information in time domain.
31. The apparatus according to claim 30, wherein the time domain location information where the MBMS PDCCH is located includes at least one of the following:

    The number of the SFN where the MBMS PDCCH is located;

    The number of the time slot where the MBMS PDCCH is located;

    The number of the symbol where the MBMS PDCCH is located;

    PDCCH occasion information occupied by MBMS PDCCH;

    SSB index information associated with the PDCCH occurrence.
32. The apparatus according to any one of claims 29 to 31, wherein different G-RNTI information is associated with different MBMS services; the apparatus further comprises:

    The replacement unit is used to request the CU to re-allocate G-RNTI information for the first MBMS service if it is determined that the G-RNTI information allocated for the first MBMS service has been allocated to the second MBMS service, or request The CU replaces the G-RNTI information associated with the second MBMS service.
33. The device according to any one of claims 29 to 31, wherein the device further comprises:

    The replacement unit is configured to, if it is determined that the G-RNTI information allocated for the first MBMS service has been allocated to the first user, request the CU to re-allocate the G-RNTI information for the first MBMS service, or request all The CU changes the RNTI information used by the first user, or changes the RNTI information used by the first user.
34. The apparatus according to any one of claims 29 to 31, wherein the receiving unit is further configured to receive first indication information sent by the CU, and the first indication information is used to indicate the selection of G-RNTI Value range; wherein the value of the G-RNTI information in the MBMS scheduling information belongs to the value range.
35. The device according to any one of claims 29 to 34, wherein the device further comprises:

    A processing unit, configured to scramble the MBMS PDCCH based on the G-RNTI information, where the MBMS PDCCH carries the MBMS service scheduling information;

    The sending unit is configured to send the scrambled MBMS PDCCH at a designated resource location based on the resource information of the MBMS PDCCH.
36. The device according to any one of claims 29 to 35, wherein the device further comprises:

    A processing unit, configured to determine MBMS service scheduling information matching the MBMS service data; perform data processing on the MBMS service data based on the matched MBMS service scheduling information;

    The sending unit is configured to send the processed MBMS service data at a designated resource location.
37. The apparatus according to claim 36, wherein the matched MBMS service scheduling information is:

    The last MBMS service scheduling information received by the DU from the CU before the DU receives the MBMS service data; or,

    The first MBMS service scheduling information received by the DU from the CU after receiving the MBMS service data; or,

    The first unused MBMS service scheduling information received by the DU from the CU.
38. The apparatus according to any one of claims 25 to 37, wherein the receiving unit is further configured to receive a CSI report sent by at least one terminal device, and the at least one terminal device belongs to the receiving group of the MBMS service data .
39. The device according to any one of claims 25 to 38, wherein the device further comprises:

    The determining unit is used to determine the recommended MBMS scheduling information;

    The sending unit is further configured to send the recommended MBMS scheduling information to the CU; wherein the recommended MBMS scheduling information is used by the CU to adjust the MBMS scheduling information delivered to the DU.
40. A service synchronization scheduling device, applied to a CU, and the device includes:

    The sending unit is configured to send MBMS scheduling information to at least one DU, where the MBMS scheduling information is used for each DU in the at least one DU to send MBMS PDCCH and/or MBMS service data.
41. The apparatus according to claim 40, wherein the sending unit is further configured to send MBMS PDCCH resource configuration information to the at least one DU, wherein the MBMS PDCCH resource configuration information includes at least one of the following:

    MBMS CORESET configuration;

    MBMS search Space configuration;

    MBMS service information associated with the MBMS PDCCH resource configuration information;

    MBMS PDCCH resource scheduling period configuration.
42. The apparatus according to claim 41, wherein the scheduling period configuration of the MBMS PDCCH resource is used to determine the MBMS PDCCH time window;

    The scheduling period configuration of the MBMS PDCCH resource includes at least one of the following:

    MBMS PDCCH time window period;

    MBMS PDCCH time window offset;

    The length of the MBMS PDCCH time window.
43. The apparatus according to claim 42, wherein the scheduling period configuration of the MBMS PDCCH resource further comprises:

    MBMS service information associated with the MBMS PDCCH time window.
44. The apparatus according to any one of claims 40 to 43, wherein the MBMS scheduling information includes at least one of the following:

    MBMS business scheduling information;

    Resource information of MBMS PDCCH, where the MBMS PDCCH is used to carry MBMS service scheduling information;

    G-RNTI information, the G-RNTI information is used to scramble MBMS PDCCH.
45. The apparatus according to claim 44, wherein the resource information of the MBMS PDCCH includes at least one of the following:

    The identification information of the MBMS CORESET where the MBMS PDCCH is located;

    The identification information of the MBMS search Space where the MBMS PDCCH is located;

    MBMS PDCCH location information in time domain.
46. The apparatus according to claim 45, wherein the time domain location information where the MBMS PDCCH is located includes at least one of the following:

    The number of the SFN where the MBMS PDCCH is located;

    The number of the time slot where the MBMS PDCCH is located;

    The number of the symbol where the MBMS PDCCH is located;

    PDCCH occasion information occupied by MBMS PDCCH;

    SSB index information associated with the PDCCH occurrence.
47. The apparatus according to any one of claims 44 to 46, wherein different G-RNTI information is associated with different MBMS services;

    The sending unit is further configured to send first indication information to the at least one DU, where the first indication information is used to indicate the value range of G-RNTI; wherein, the G-RNTI in the MBMS scheduling information The value of the RNTI information belongs to the value range.
48. The device according to any one of claims 40 to 47, wherein the device further comprises:

    A receiving unit, configured to receive suggested MBMS scheduling information sent by the at least one DU;

    The adjustment unit is configured to adjust the MBMS scheduling information delivered to the DU based on the recommended MBMS scheduling information.
49. A communication device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 1 to 15 , Or the method of any one of claims 16 to 24.
50. A chip comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 15, or claims 16 to 24 The method of any one of.
51. A computer-readable storage medium for storing a computer program that enables a computer to execute the method according to any one of claims 1 to 15 or the method according to any one of claims 16 to 24 .
52. A computer program product comprising computer program instructions that cause a computer to execute the method according to any one of claims 1 to 15 or the method according to any one of claims 16 to 24.
53. A computer program that causes a computer to execute the method according to any one of claims 1 to 15 or the method according to any one of claims 16 to 24.

Images