CN114600473A

CN114600473A - Service synchronous scheduling method and device, and communication equipment

Info

Publication number: CN114600473A
Application number: CN202080072877.5A
Authority: CN
Inventors: 王淑坤; 卢前溪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-01-07
Filing date: 2020-01-07
Publication date: 2022-06-07
Anticipated expiration: 2040-01-07
Also published as: WO2021138805A1; CN114600473B

Abstract

The embodiment of the application provides a service synchronous scheduling method, a device and communication equipment, wherein the method comprises the following steps: a distribution unit DU receives MBMS scheduling information sent by a central unit CU; and the DU transmits MBMS PDCCH and/or MBMS service data based on the MBMS scheduling information.

Description

Service synchronous scheduling method and device, and communication equipment

Technical Field

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

Background

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

In a New Radio (NR) system, many scenarios need to support multicast and broadcast service requirements, such as in car networking, industrial internet, etc. It is necessary to introduce MBMS in NR. For MBMS services, the performance of the cell edge is generally poor, so if the content synchronization of the transmission between the cells is implemented, the terminal device can receive the same data from two cells at the cell edge, thereby improving the reliability of data transmission by combining gains, but how to implement the content synchronization transmission between two adjacent cells is a problem.

Disclosure of Invention

The embodiment of the application provides a service synchronous scheduling method and device and communication equipment.

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

a Distributed Unit (DU) receives MBMS scheduling information transmitted by a Central Unit (CU);

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

and the CU transmits MBMS scheduling information to at least one DU, wherein the MBMS scheduling information is used for transmitting MBMS PDCCH and/or MBMS service data by each DU in the at least one DU.

The service synchronous scheduling device provided by the embodiment of the application is applied to a DU, and the device comprises:

a receiving unit, configured to receive MBMS scheduling information sent by a CU;

and the sending unit is used for sending the MBMS PDCCH and/or the MBMS service data based on the MBMS scheduling information.

The service synchronous scheduling device provided by the embodiment of the application is applied to a CU, and the device comprises:

a sending unit, 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 application comprises a processor and a memory. The memory is used for storing computer programs, and the processor is used for calling and running the computer programs stored in the memory to execute the service synchronous scheduling method.

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

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

The computer-readable storage medium provided in the embodiments of the present application is configured to store a computer program, where the computer program enables a computer to execute the service synchronous scheduling method.

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

The computer program provided in the embodiment of the present application, when running on a computer, enables the computer to execute the service synchronous scheduling method.

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

Drawings

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

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

fig. 2 is a schematic diagram of Beam surfing provided in an embodiment of the present application;

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

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

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

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

fig. 8 is a schematic flowchart of a service synchronous scheduling method according to an embodiment of the present application;

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

fig. 10 is a first schematic structural diagram of a service synchronous scheduling apparatus according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a service synchronous scheduling apparatus according to an embodiment of the present application;

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

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

fig. 14 is a schematic block diagram of a communication system according to an embodiment of the present application.

Detailed Description

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

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, a 5G communication system, a future communication system, or the like.

Illustratively, a communication system 100 applied in the embodiment of the present application is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area. Optionally, the Network device 110 may be an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the Network device may be a mobile switching center, a relay station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a future communication system, and the like.

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

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

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

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

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

It should be understood that a device having a communication function in a network/system in the embodiments 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 having a communication function, and the network device 110 and the terminal 120 may be the 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 other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

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

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

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

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

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

RRC state

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

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

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

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

Beam scanning (beam sweeping)

NR will be deployed at high frequency in the future, and in order to improve coverage, in 5G, the requirement of coverage (coverage by space and space by time) is satisfied by introducing a beam surfing mechanism, as shown in fig. 2. After the beam scanning is introduced, a synchronization Signal needs to be transmitted in each beam direction, and a 5G synchronization Signal is given in the form of a synchronization Signal block (SS/PBCH block, SSB) and includes a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSs), and a Physical Broadcast Channel (PBCH), as shown in fig. 3. The synchronization signal of 5G appears periodically in the time domain in the form of a burst set of synchronization signals (SS burst set), as shown in fig. 4.

The number of beams actually transmitted in each cell is determined by 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 (maximum beam number)
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 may be 400MHz (i.e., wideband), which is large compared to the maximum channel bandwidth in LTE of 20 MHz. The power consumption of the UE is significant if the UE remains operating on a wideband carrier (i.e., the maximum channel bandwidth). It is proposed that the radio frequency bandwidth of the UE can be adjusted according to the actual throughput of the UE, and for this reason the concept of BWP is introduced, the motivation for which is to optimize the power consumption of the UE. For example, if the rate requirement of the UE is low, the UE may be configured with a smaller bandwidth (i.e., BWP with smaller bandwidth), and if the rate requirement of the UE is high, the UE may be configured with a larger bandwidth (i.e., BWP with larger bandwidth). If the UE supports high rate or operates in Carrier Aggregation (CA) mode, the UE may be configured with multiple BWPs. Furthermore, another purpose of BWP is to trigger coexistence of multiple parameter sets (numerology) in a cell, such as BWP1 for numerology1 and BWP2 for numerology 2.

The idle or inactive UE resides on an initial BWP (initial BWP), which is visible to the idle or inactive UE, and the UE may obtain Information such as a Master Information Block (MIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), and paging (paging) on the initial BWP.

MBMS

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

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

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

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

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

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

MBMS introduces a new System Information Block (SIB) type, SIB 20. Specifically, the configuration information of the SC-MCCH is transmitted through 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, and the scheduling of the wireless frame and the subframe of the SC-MCCH. Further, 1) the boundary of the modification period of the SC-MCCH satisfies SFN mod m ═ 0, where SFN represents the system frame number of the boundary, and m is the modification period of the SC-MCCH (i.e., SC-MCCH-modification period) configured in SIB 20. 2) And scheduling the radio frame of the SC-MCCH to meet the following requirements: SFN mod MCCH-repetition period ═ MCCH-Offset, where SFN represents the system frame number of a radio frame, MCCH-repetition period represents the repetition period of SC-MCCH, and MCCH-Offset represents the Offset of SC-MCCH. 3) The sub-frame of the SC-MCCH is scheduled and indicated by SC-MCCH-Subframe.

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

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

The downlink discontinuous reception of SC-PTMs is controlled by the following parameters: ondurationTimerSCPTM, drx-InactivetTimeSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.

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

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

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

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

In NR, many scenarios need to support multicast and broadcast traffic needs, such as in car networking, industrial internet, etc. It is necessary to introduce MBMS in NR, however, since transmission of MBMS service cannot change the transmitted scheduling information according to the channel environment of a specific certain terminal device to achieve reliability of data transmission, for example, change TB size or MCS, etc. The performance of the cell edge is generally poor for MBMS services. If the content synchronization of the transmission between the cells is realized, that is, the adjacent cells transmit the same data in the same time-frequency resource, the terminal equipment can receive the same data from the two cells at the cell edge, so as to improve the reliability of the data transmission by combining the gains, but how to realize the content synchronization transmission between the adjacent cells needs to be clear. Therefore, the following technical scheme of the embodiment of the application is provided.

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

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

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

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

It should be noted that, in the embodiment of the present application, naming of the first SIB, the first MCCH, and the first MTCH is not limited. For convenience of description, the first SIB may also be abbreviated as SIB, the first MCCH may also be abbreviated as MCCH, and the first MTCH may also be abbreviated as MTCH, and referring to fig. 6, a PDCCH (i.e., MCCH PDCCH) for scheduling MCCH and a notification PDCCH are configured through SIB, wherein a PDSCH (i.e., MCCH PDSCH) for transmitting MCCH is scheduled through DCI carried by MCCH PDCCH. Further, M PDCCHs (i.e., MTCH 1 PDCCH, MTCH 2 PDCCH, …, MTCH M PDCCH) for scheduling MTCH are configured through the MCCH, wherein DCI carried by the MTCH n PDCCH schedules a PDSCH (i.e., MTCH n PDSCH) for transmitting MTCH n, n being an integer of 1 or more and M or less. Referring to fig. 7, MCCH and MTCH are mapped to DL-SCH, which belong to a logical channel, DL-SCH which belongs to a transport channel, and PDSCH which belongs to a physical channel, and further DL-SCH which is mapped to PDSCH.

In this embodiment, the network side is a CU and DU separation architecture, and may be regarded as a network device including a CU and at least one DU, in which case, the MBMS related configuration is configured by the CU to each DU in the at least one DU. 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, and in general, cells covered by a plurality of DUs belonging to the same CU are neighboring cells. Content synchronization between neighboring cells may be achieved by transmitting MBMS scheduling information to at least one CU with which the DU is associated, as described in more detail below.

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

step 801: the CU transmits MBMS scheduling information to at least one DU, and the DU receives the MBMS scheduling information transmitted by the CU.

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

In the embodiment of the present application, a network side employs a CU and DU separation architecture, where a CU and a DU both belong to entities on a base station side, and one CU may associate with one or more DUs. The protocol stack in charge of the CU comprises the following steps: the SDAP layer and the PDCP layer. The protocol stack for which the DU is responsible includes: RLC layer, MAC layer, and PHY layer.

In an alternative embodiment, the base station is a gNB, and accordingly, a CU may also be referred to as a gNB CU, and a DU may also be referred to as a gNB DU. As shown in fig. 9, MBMS service data is transmitted between the gNB CU and the core network side through a GTP tunnel. MBMS service data is also transmitted between the gNB CU and the gNB DU1 and the gNB DU2 through GTP tunnels. DU1 and DU2 transmit MBMS service data so that terminal devices can receive the MBMS service data.

In this embodiment, a CU may pre-configure at least one DU with MBMS PDCCH resource configuration information (which may be referred to as pre-configuration information), and the information may include the pre-configuration informationSpecifically, the CU transmits 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, wherein the MBMS PDCCH resource configuration information comprises 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;

and configuring the scheduling period of the MBMS PDCCH resource.

In a specific implementation, referring to fig. 9, the gNB CU pre-configures the MBMS PDCCH resource configuration information to each DU of the at least one DU through an F1 interface. Here, the F1 interface is an interface between the gNB CU and the 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 an MBMS PDCCH time window; the scheduling cycle configuration of the MBMS PDCCH resource comprises at least one of the following:

the period of the MBMS PDCCH time window;

biasing of MBMS PDCCH time window;

duration of MBMS PDCCH time window.

It should be noted that the MBMS PDCCH time window occurs periodically in the time domain, and the time domain resources in the MBMS PDCCH time window are used for transmitting the MBMS PDCCH.

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

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

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

MBMS service scheduling information;

the resource information of MBMS PDCCH, the MBMS PDCCH is used for bearing MBMS service scheduling information;

G-RNTI information used for scrambling MBMS PDCCH.

Further optionally, the MBMS service scheduling information includes, but is not limited to, at least one of the following: time domain position information of the MBMS service, frequency domain position 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:

identification information (such as a set id) of an MBMS core in which the MBMS PDCCH is located;

identification information (such as a search Space id) of an MBMS search Space in which the MBMS PDCCH is located;

and time domain position information of the MBMS PDCCH.

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

the number of SFN where MBMS PDCCH is located;

the number of the time slot in which the MBMS PDCCH is positioned;

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 PDCCH occasting.

In the above scheme, the MBMS PDCCH may occupy one or more PDCCH occasions; optionally, for the case that the MBMS PDCCH occupies multiple PDCCH occasions, the multiple PDCCH occasions may be multiple consecutive PDCCH occasions; here, if the MBMS PDCCH occupies a plurality of PDCCH occasions, SSB index information associated with each PDCCH occasion needs to be given.

It should be noted that PDCCH occase is periodically distributed in a certain time range and/or frequency spectrum range, and is numbered according to a certain rule. Further, alternatively, one MBMS occasion may contain several symbols or several slots.

Further, optionally, the CU configures, for each MBMS service, G-RNTI information for scheduling the service, wherein different G-RNTI information is associated with different MBMS services. In order to ensure that the G-RNTI information distributed by the MBMS service has uniqueness, the following method can be adopted:

the first method is as follows: and if the DU determines that the G-RNTI information distributed by the first MBMS is already distributed to the second MBMS, the DU requests the CU to distribute the G-RNTI information for the first MBMS again, or the DU requests the CU to replace the G-RNTI information associated with the second MBMS.

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

The second method comprises the following steps: and if the DU determines that the G-RNTI information distributed by the first MBMS is already distributed to the first user, the DU requests the CU to distribute the G-RNTI information for the first MBMS again, or the DU requests the CU to replace the RNTI information used by the first user, or the DU replaces the RNTI information used by the first user.

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

The third method comprises the following steps: the DU receives first indication information sent by the CU, wherein the first indication information is used for indicating the value range of the G-RNTI; and the value of the G-RNTI information in the MBMS scheduling information belongs to the value range.

Here, the CU configures a value range for the DU, and a value in the value range is only used for configuring the G-RNTI, so that collision between values of other RNTIs and values of the G-RNTI can be avoided.

In the embodiment of the present application, after acquiring the MBMS scheduling information, the DU transmits MBMS PDCCH and/or MBMS service data based on the MBMS scheduling information, which is described in detail below.

1) Control plane: transmission of MBMS PDCCH

The DU scrambles an MBMS PDCCH based on the G-RNTI information, wherein the MBMS PDCCH carries the MBMS service scheduling information; and the DU sends the scrambled MBMS PDCCH at a specified resource position based on the resource information of the MBMS PDCCH.

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

It should be noted that, after scrambling the MBMS PDCCH based on the G-RNTI information, the DU needs to be sent in the designated resource location after being processed by the physical layer. Here, the physical layer process includes, but is not limited to, a modulation coding process.

2) User side: transmission of MBMS service data

After receiving the MBMS service data sent by the CU, the DU determines MBMS service scheduling information matched with the MBMS service data; and the DU carries out data processing on the MBMS data based on the matched MBMS scheduling information and sends the processed MBMS data on a specified resource position.

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

before receiving the MBMS service data, the DU receives the last MBMS service scheduling information from the CU; or,

the DU receives first MBMS service scheduling information from the CU after receiving the MBMS service data; or,

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

Specifically, referring to fig. 9, the gNB CU transmits MBMS service data to the DU through a GTP tunnel. Wherein, the GTP tunnel is specifically an F1GTP tunnel. After receiving MBMS service data, the gNB DU has the following three processing modes:

A) the gNB DU matches the newly received MBMS service data with the latest MBMS service scheduling information from the gNB CU (namely the last MBMS service scheduling information received from the CU before receiving the MBMS service data), carries out physical layer processing on the MBMS service data by using the MBMS service scheduling information, and transmits the processed MBMS service data according to the time-frequency resource given by the MBMS service scheduling information. Here, the physical layer process includes, but is not limited to, a modulation coding process.

B) The gNB DU matches the newly received MBMS service data with the first MBMS service scheduling information (namely the first MBMS service scheduling information received from the GNB CU after receiving the MBMS service data) after the MBMS service data from the gNB CU, performs physical layer processing on the MBMS service data by using the MBMS service scheduling information, and transmits the processed MBMS service data according to the time-frequency resource given by the MBMS service scheduling information. Here, the physical layer process includes, but is not limited to, a modulation coding process.

C) The gNB DU matches the newly received MBMS service data with the first unused MBMS service scheduling information (i.e. the longest unused MBMS service scheduling information) from the gNB CU, performs physical layer processing on the MBMS service data by using the MBMS service scheduling information, and transmits the processed MBMS service data according to the time-frequency resource given by the MBMS service scheduling information. Here, the physical layer process includes, but is not limited to, a modulation coding process.

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

In an optional embodiment of the present application, the DU determines suggested MBMS scheduling information, and sends the suggested MBMS scheduling information to the CU; wherein, the proposed MBMS scheduling information is used by the CU to adjust MBMS scheduling information delivered to the DU. Further, optionally, the DU determines suggested MBMS scheduling information based on the received CSI reports.

Referring to fig. 9, during receiving MBMS service data, a terminal device may feed back channel quality to a gNB DU, that is, the terminal device reports a CSI report (CSI report) to the DU. After receiving the CSI report sent by the terminal device, the gNB DU provides the suggested MBMS scheduling information according to the CSI report fed back by one or more terminal devices in the MBMS service reception group, and sends the suggested MBMS scheduling information to the gNB CU. And the gNB CU decides MBMS scheduling information according to the suggested MBMS scheduling information sent by one or more gNB DUs, and sends the MBMS scheduling information to the gNB DUs for scheduling new MBMS service data.

According to the technical scheme of the embodiment of the application, the plurality of DUs receive the MBMS scheduling information sent by the CU, and the MBMS PDCCH and/or the MBMS service data are/is sent based on the MBMS scheduling information, so that the content synchronization between adjacent cells is realized.

Fig. 10 is a schematic structural diagram of a service synchronization scheduling apparatus according to an embodiment of the present application, which is applied to a DU, and as shown in fig. 10, the service synchronization scheduling apparatus includes:

a receiving unit 1001 configured to receive MBMS scheduling information sent by a CU;

a sending unit 1002, configured to send an MBMS PDCCH and/or MBMS service data based on the MBMS scheduling information.

In an optional embodiment, 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:

configuring MBMS CORESET;

configuring MBMS search Space;

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

and configuring the scheduling period of the MBMS PDCCH resource.

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

the scheduling cycle configuration of the MBMS PDCCH resource comprises at least one of the following:

a period of an MBMS PDCCH time window;

biasing of MBMS PDCCH time window;

duration of MBMS PDCCH time window.

In an optional embodiment, the configuring the scheduling cycle of the MBMS PDCCH resource further includes:

and the MBMS service information associated with the MBMS PDCCH time window.

In an optional embodiment, the MBMS scheduling information includes at least one of:

MBMS service scheduling information;

G-RNTI information used for scrambling MBMS PDCCH.

In an optional embodiment, the resource information of the MBMS PDCCH includes at least one of:

identification information of MBMS CORESET where MBMS PDCCH is located;

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

and time domain position information of the MBMS PDCCH.

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

the number of SFN where MBMS PDCCH is located;

the number of the time slot in which the MBMS PDCCH is positioned;

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

PDCCH occast information occupied by MBMS PDCCH;

SSB index information associated with PDCCH occasting.

In an optional embodiment, different G-RNTI information is associated with different MBMS services; the device further comprises:

and a replacing unit (not shown in the figure) configured to request the CU to re-allocate G-RNTI information for the first MBMS service or request the CU to replace G-RNTI information associated with the second MBMS service if it is determined that the G-RNTI information allocated to the first MBMS service has been allocated to the second MBMS service.

In an alternative embodiment, the apparatus further comprises:

and a replacing unit (not shown in the figure) configured to request the CU to re-allocate G-RNTI information for the first MBMS service, or request the CU to replace RNTI information used by the first user, or replace RNTI information used by the first user, if it is determined that the allocated G-RNTI information of the first MBMS service has been already allocated to the first user.

In an optional embodiment, 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 a value range of a G-RNTI; and the value of the G-RNTI information in the MBMS scheduling information belongs to the value range.

In an alternative embodiment, the apparatus further comprises:

a processing unit 1003, configured to scramble an 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 MBMS PDCCH after scrambling at a specified resource location based on the resource information of the MBMS PDCCH.

In an alternative embodiment, the apparatus further comprises:

a processing unit 1003, configured to determine MBMS service scheduling information matched with the MBMS service data; based on the matched MBMS service scheduling information, performing data processing on the MBMS service data;

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

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

the DU receives the first unused MBMS service scheduling information from the CU.

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

In an alternative embodiment, the apparatus further comprises:

a determining unit 1004 for determining the proposed MBMS scheduling information;

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

It should be understood by those skilled in the art that the related description of the service synchronization scheduling apparatus in the embodiment of the present application can be understood by referring to the related description of the service synchronization scheduling method in the embodiment of the present application.

Fig. 11 is a schematic structural diagram of a service synchronization scheduling apparatus according to an embodiment of the present application, which is applied to a CU, and as shown in fig. 11, the service synchronization scheduling apparatus includes:

a sending unit 1101, 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 embodiment, 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:

configuring MBMS CORESET;

configuring MBMS search Space;

and configuring the scheduling period of the MBMS PDCCH resource.

the period of the MBMS PDCCH time window;

biasing of MBMS PDCCH time window;

duration of MBMS PDCCH time window.

and the MBMS service information associated with the MBMS PDCCH time window.

MBMS service scheduling information;

G-RNTI information used for scrambling MBMS PDCCH.

identification information of MBMS CORESET where MBMS PDCCH is located;

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

and time domain position information of the MBMS PDCCH.

the number of SFN where MBMS PDCCH is located;

the number of the time slot in which the MBMS PDCCH is positioned;

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

PDCCH occast information occupied by MBMS PDCCH;

SSB index information associated with PDCCH occasting.

In an optional embodiment, 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 a value range of the G-RNTI; and the value of the G-RNTI information in the MBMS scheduling information belongs to the value range.

In an alternative embodiment, the apparatus further comprises:

a receiving unit 1102, configured to receive proposed MBMS scheduling information sent by the at least one DU;

an adjusting unit 1103, configured to adjust the MBMS scheduling information sent to the DU based on the suggested MBMS scheduling information.

Fig. 12 is a schematic structural diagram of a communication device 1200 according to an embodiment of the present application. The communication device may be a terminal device or a network device, and the communication device 1200 shown in fig. 12 includes a processor 1210, where the processor 1210 may invoke and execute 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. From the memory 1220, the processor 1210 may call and execute a computer program to implement the method in the embodiment 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, 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, and in particular, may transmit information or data to other devices or receive information or data transmitted by other devices.

The transceiver 1230 may include a transmitter and a receiver, among others. 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 in the embodiment of the present application, and the communication device 1200 may implement a corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

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

Fig. 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 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. 13, the chip 1300 may further include a memory 1320. From the memory 1320, the processor 1310 may call and execute a computer program to implement the method of the present embodiment.

The memory 1320 may be a separate device from the processor 1310, or may be integrated into the processor 1310.

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

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

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

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

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

Fig. 14 is a schematic block diagram of a communication system 1400 provided in 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.

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

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

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

It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), Synchronous Link DRAM (SLDRAM), Direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

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

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

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

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

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

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

The embodiment of the application also provides a computer program.

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

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

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

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

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

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

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

The functions, 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 such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

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

Claims

A method for synchronously scheduling services, the method comprising:

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

and the DU transmits MBMS PDCCH and/or MBMS service data based on the MBMS scheduling information.
The method of claim 1, wherein the method further comprises:

the DU receives MBMS PDCCH resource configuration information sent by the CU, wherein the MBMS PDCCH resource configuration information comprises at least one of the following:

configuring MBMS control resource set MBMS CORESET;

configuring MBMS search Space in an MBMS search Space;

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

and configuring the scheduling period of the MBMS PDCCH resource.
The method of claim 2, wherein a scheduling period configuration of the MBMS PDCCH resource is used to determine an MBMS PDCCH time window;

the scheduling cycle configuration of the MBMS PDCCH resource comprises at least one of the following:

the period of the MBMS PDCCH time window;

biasing of MBMS PDCCH time window;

duration of MBMS PDCCH time window.
The method of claim 3, wherein the scheduling cycle configuration of the MBMS PDCCH resources further comprises:

and the MBMS service information associated with the MBMS PDCCH time window.
The method of any of claims 1-4, wherein the MBMS scheduling information comprises at least one of:

MBMS service scheduling information;

the resource information of MBMS PDCCH, the MBMS PDCCH is used for bearing MBMS service scheduling information;

G-RNTI information used for scrambling MBMS PDCCH.
The method of claim 5, wherein the resource information of the MBMS PDCCH comprises at least one of:

identification information of MBMS CORESET where MBMS PDCCH is located;

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

and time domain position information of the MBMS PDCCH.
The method of claim 6, wherein the time domain location information in which the MBMS PDCCH is located comprises at least one of:

the number of SFN where MBMS PDCCH is located;

the number of the time slot in which the MBMS PDCCH is positioned;

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

PDCCH opportunity PDCCH occast information occupied by MBMS PDCCH;

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

and if the DU determines that the G-RNTI information distributed by the first MBMS is already distributed to the second MBMS, the DU requests the CU to distribute the G-RNTI information for the first MBMS again, or the DU requests the CU to replace the G-RNTI information associated with the second MBMS.
The method of any of claims 5 to 7, wherein the method further comprises:

and if the DU determines that the G-RNTI information distributed by the first MBMS is already distributed to the first user, the DU requests the CU to distribute the G-RNTI information for the first MBMS again, or the DU requests the CU to replace the RNTI information used by the first user, or the DU replaces the RNTI information used by the first user.
The method of any of claims 5 to 7, wherein the method further comprises:

the DU receives first indication information sent by the CU, wherein the first indication information is used for indicating the value range of the G-RNTI; and the value of the G-RNTI information in the MBMS scheduling information belongs to the value range.
The method of any of claims 5-10, wherein the DU transmits an MBMS PDCCH based on the MBMS scheduling information, comprising:

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

and the DU sends the scrambled MBMS PDCCH at a specified resource position based on the resource information of the MBMS PDCCH.
The method of any of claims 5 to 11, wherein the DU transmits MBMS service data based on the MBMS scheduling information, comprising:

after receiving the MBMS service data sent by the CU, the DU determines MBMS service scheduling information matched with the MBMS service data;

and the DU carries out data processing on the MBMS data based on the matched MBMS scheduling information and sends the processed MBMS data on a specified resource position.
The method of claim 12, wherein the matching MBMS service scheduling information is:

before receiving the MBMS service data, the DU receives the last MBMS service scheduling information from the CU; or,

the DU receives first MBMS service scheduling information from the CU after receiving the MBMS service data; or,

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

and the DU receives a CSI report sent by at least one terminal device, wherein the at least one terminal device belongs to the receiving group of the MBMS service data.
The method of any 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; wherein, the proposed MBMS scheduling information is used by the CU to adjust MBMS scheduling information delivered to the DU.
A method for synchronously scheduling services, the method comprising:

and the CU transmits MBMS scheduling information to at least one DU, wherein the MBMS scheduling information is used for transmitting MBMS PDCCH and/or MBMS service data by each DU in the at least one DU.
The method of claim 16, wherein the method further comprises:

the CU transmits MBMS PDCCH resource configuration information to the at least one DU, wherein the MBMS PDCCH resource configuration information comprises at least one of the following:

configuring MBMS CORESET;

configuring MBMS search Space;

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

and configuring the scheduling period of the MBMS PDCCH resource.
The method of claim 17, wherein a scheduling period configuration of the MBMS PDCCH resource is used to determine an MBMS PDCCH time window;

the scheduling cycle configuration of the MBMS PDCCH resource comprises at least one of the following:

the period of the MBMS PDCCH time window;

biasing of MBMS PDCCH time window;

duration of MBMS PDCCH time window.
The method of claim 18, wherein the scheduling cycle configuration of the MBMS PDCCH resource further comprises:

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

MBMS service scheduling information;

the resource information of MBMS PDCCH, the MBMS PDCCH is used for bearing MBMS service scheduling information;

G-RNTI information used for scrambling MBMS PDCCH.
The method of claim 20, wherein the resource information of the MBMS PDCCH comprises at least one of:

identification information of MBMS CORESET where MBMS PDCCH is located;

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

and time domain position information of the MBMS PDCCH.
The method of claim 21, wherein the time domain location information in which the MBMS PDCCH is located comprises at least one of:

the number of SFN where MBMS PDCCH is located;

the number of the time slot in which the MBMS PDCCH is positioned;

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

PDCCH occast information occupied by MBMS PDCCH;

SSB index information associated with PDCCH occasting.
The method according to any 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, wherein the first indication information is used for indicating the value range of the G-RNTI; and the value of the G-RNTI information in the MBMS scheduling information belongs to the value range.
The method of any of claims 16 to 23, wherein the method further comprises:

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

a receiving unit, configured to receive MBMS scheduling information sent by a CU;

and the sending unit is used for sending the MBMS PDCCH and/or the MBMS service data based on the MBMS scheduling information.
The apparatus of 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 comprises at least one of:

configuring MBMS CORESET;

configuring MBMS search Space;

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

and configuring the scheduling period of the MBMS PDCCH resource.
The apparatus of claim 26, wherein a scheduling period configuration of the MBMS PDCCH resource is used to determine an MBMS PDCCH time window;

the scheduling cycle configuration of the MBMS PDCCH resource comprises at least one of the following:

the period of the MBMS PDCCH time window;

biasing of MBMS PDCCH time window;

duration of MBMS PDCCH time window.
The apparatus of claim 27, wherein the scheduling cycle configuration of the MBMS PDCCH resource further comprises:

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

MBMS service scheduling information;

the resource information of MBMS PDCCH, the MBMS PDCCH is used for bearing MBMS service scheduling information;

G-RNTI information used for scrambling MBMS PDCCH.
The apparatus of claim 29, wherein the resource information of the MBMS PDCCH comprises at least one of:

identification information of MBMS CORESET where MBMS PDCCH is located;

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

and time domain position information of the MBMS PDCCH.
The apparatus of claim 30, wherein the time domain location information in which the MBMS PDCCH is located comprises at least one of:

the number of SFN where MBMS PDCCH is located;

the number of the time slot in which the MBMS PDCCH is positioned;

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

PDCCH occast information occupied by MBMS PDCCH;

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

and the replacing unit is used for requesting the CU to re-allocate the G-RNTI information for the first MBMS or requesting the CU to replace the G-RNTI information associated with the second MBMS if the G-RNTI information allocated to the first MBMS is determined to be already allocated to the second MBMS.
The apparatus of any one of claims 29 to 31, wherein the apparatus further comprises:

and the replacing unit is used for requesting the CU to re-allocate the G-RNTI information for the first MBMS service or requesting the CU to replace the RNTI information used by the first user or replacing the RNTI information used by the first user if the fact that the G-RNTI information allocated to the first MBMS service is already allocated to the first user is determined.
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, where the first indication information is used to indicate a value range of a G-RNTI; and the value of the G-RNTI information in the MBMS scheduling information belongs to the value range.
The apparatus of any one of claims 29 to 34, wherein the apparatus further comprises:

the processing unit is used for scrambling the MBMS PDCCH based on the G-RNTI information, wherein the MBMS PDCCH carries the MBMS service scheduling information;

the sending unit is configured to send the MBMS PDCCH after scrambling at a specified resource location based on the resource information of the MBMS PDCCH.
The apparatus of any one of claims 29 to 35, wherein the apparatus further comprises:

the processing unit is used for determining MBMS scheduling information matched with the MBMS data; based on the matched MBMS service scheduling information, performing data processing on the MBMS service data;

and the sending unit is used for sending the processed MBMS service data at the specified resource position.
The apparatus of claim 36, wherein the matching MBMS service scheduling information is:

before receiving the MBMS service data, the DU receives the last MBMS service scheduling information from the CU; or,

the DU receives first MBMS service scheduling information from the CU after receiving the MBMS service data; or,

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

a determining unit for determining suggested MBMS scheduling information;

the sending unit is further configured to send the suggested MBMS scheduling information to the CU; wherein, the proposed MBMS scheduling information is used by the CU to adjust MBMS scheduling information delivered to the DU.
A service synchronization scheduling device applied to a CU (central office), the device comprising:

a sending unit, 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 apparatus of claim 40, wherein the transmitting unit is further configured to transmit MBMS PDCCH resource configuration information to the at least one DU, wherein the MBMS PDCCH resource configuration information comprises at least one of:

configuring MBMS CORESET;

configuring MBMS search Space;

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

and configuring the scheduling period of the MBMS PDCCH resource.
The apparatus of claim 41, wherein a scheduling periodicity configuration of the MBMS PDCCH resources is used to determine an MBMS PDCCH time window;

the scheduling cycle configuration of the MBMS PDCCH resource comprises at least one of the following:

the period of the MBMS PDCCH time window;

biasing of MBMS PDCCH time window;

duration of MBMS PDCCH time window.
The apparatus of claim 42, wherein the scheduling cycle configuration of the MBMS PDCCH resources further comprises:

and the MBMS service information associated with the MBMS PDCCH time window.
The apparatus of any of claims 40-43, wherein the MBMS scheduling information comprises at least one of:

MBMS service scheduling information;

the resource information of MBMS PDCCH, the MBMS PDCCH is used for bearing MBMS service scheduling information;

G-RNTI information used for scrambling MBMS PDCCH.
The apparatus of claim 44, wherein the resource information of the MBMS PDCCH comprises at least one of:

identification information of MBMS CORESET where MBMS PDCCH is located;

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

and time domain position information of the MBMS PDCCH.
The apparatus of claim 45, wherein the time domain location information in which the MBMS PDCCH is located comprises at least one of:

the number of SFN where MBMS PDCCH is located;

the number of the time slot in which the MBMS PDCCH is positioned;

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

PDCCH occast information occupied by MBMS PDCCH;

SSB index information associated with PDCCH occasting.
The apparatus of any 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 a value range of the G-RNTI; and the value of the G-RNTI information in the MBMS scheduling information belongs to the value range.
The apparatus of any one of claims 40 to 47, wherein the apparatus further comprises:

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

and an adjusting unit, configured to adjust the MBMS scheduling information issued to the DU based on the suggested MBMS scheduling information.
A communication device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory, to perform the method of any of claims 1 to 15, or to perform the method of any of claims 16 to 24.
A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any of claims 1 to 15, or the method of any of claims 16 to 24.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any of claims 1 to 15 or the method of any of claims 16 to 24.
A computer program product comprising computer program instructions to cause a computer to perform the method of any of claims 1 to 15, or the method of any of claims 16 to 24.
A computer program for causing a computer to perform the method of any one of claims 1 to 15, or the method of any one of claims 16 to 24.