CN114747285A

CN114747285A - Resource scheduling method and communication device

Info

Publication number: CN114747285A
Application number: CN201980102661.6A
Authority: CN
Inventors: 王俊伟
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-12-05
Filing date: 2019-12-05
Publication date: 2022-07-12
Also published as: WO2021109047A1

Abstract

The application provides a resource scheduling method and a communication device. The method comprises the following steps: determining a first resource; and sending a resource scheduling message of the first resource, wherein the resource scheduling message is used for indicating whether the service is transmitted in an SFN mode on the first resource. The network device may determine any idle resource as the first resource that can be used to transmit the service in the SFN mode by using a dynamic scheduling method, so that the network device may adapt to the dynamic change of the transmission rate of the service transmitted in the SFN mode, flexibly schedule the SFN resource for transmitting the service in the SFN mode, and avoid the waste of resources.

Description

Resource scheduling method and communication device

Technical Field

The present application relates to the field of wireless communication, and more particularly, to a method and a communication apparatus for resource scheduling.

Background

In the current process of transmitting a service to a terminal device in a Single Frequency Network (SFN) mode, in order to simplify a coordination process between network devices, the network device configures a timeslot resource for transmitting the service in the SFN mode to the terminal device in a semi-static manner. Semi-static configuration means that traffic can only be transmitted in SFN mode on SFN slot resources and in non-SFN mode on non-SFN slot resources. Therefore, in the case where the traffic demand for transmission in the SFN mode becomes large, the traffic cannot be transmitted in the SFN mode using the non-SFN slot resource, or in the case where the traffic demand for transmission in the non-SFN mode becomes large, the traffic cannot be transmitted in the non-SFN mode using the SFN slot resource.

Therefore, the above-mentioned semi-static way of configuring SFN slot resources is not flexible enough.

Disclosure of Invention

The application provides a resource scheduling method, aiming to achieve the purpose of flexibly scheduling SFN resources.

In a first aspect, a method for resource scheduling is provided, where the method includes: determining a first resource; and sending a resource scheduling message of the first resource, wherein the resource scheduling message is used for indicating whether the service is transmitted in the SFN mode on the first resource.

Based on the above technical solution, the network device may determine any idle resource as the first resource that can be used for transmitting the service in the SFN mode by using a dynamic scheduling method, so that the network device may adapt to the dynamic change of the transmission rate of the SFN service, flexibly schedule the SFN resource for transmitting the service in the SFN mode, and avoid the waste of resources.

With reference to the first aspect, in some implementations of the first aspect, the sending the resource scheduling message of the first resource includes: transmitting the resource scheduling message on a second resource; wherein the resource scheduling message is used for indicating whether the service is transmitted in the SFN mode on the first resource, and comprises: if the second resource is an SFN resource, indicating that the service is transmitted in an SFN mode on the first resource, wherein the SFN resource is a resource for transmitting the service in the SFN mode; if the second resource is a non-SFN resource, it indicates that the service is transmitted in a non-SFN mode on the first resource.

Based on the above technical solution, the terminal device may determine, according to the second resource of the message for transmitting resource scheduling, whether to transmit the service in the SFN mode or the non-SFN mode on the first resource indicated by the resource scheduling message.

With reference to the first aspect, in certain implementations of the first aspect, the resource scheduling message includes first indication information for indicating a transmission mode; wherein the resource scheduling message is used for indicating whether the service is transmitted in the SFN mode on the first resource, and comprises: if the first indication information indicates that the sending mode is the SFN mode, the SFN mode is used for transmitting the service on the first resource; if the first indication information indicates that the transmission mode is a non-SFN mode, it indicates that the service is transmitted in the non-SFN mode on the first resource.

With reference to the first aspect, in some implementations of the first aspect, the resource scheduling message is used to indicate whether to transmit the service in an SFN manner on the first resource, and includes: if the resource scheduling message can be received with a first Radio Network Temporary Identity (RNTI) as a scrambling code, indicating that traffic is transmitted in SFN mode on the first resource, and if the resource scheduling message cannot be received with the first RNTI as a scrambling code, indicating that traffic is transmitted in non-SFN mode on the first resource.

Optionally, the first RNTI may be an SFN-RNTI.

With reference to the first aspect, in certain implementations of the first aspect, in a case that the second resource is an SFN resource, the resource scheduling message is further configured to indicate a parameter K0, where a value of the parameter K0 indicates a number of time domain resource units spaced between the first resource and the second resource, where the time domain resource units do not include a resource that is not available for transmitting a service in an SFN mode.

Based on the above scheme, when the network device indicates the parameter K0, resources that are not available for service transmission in the SFN mode are not included, so that air interface signaling when the network device indicates the parameter K0 can be saved.

With reference to the first aspect, in certain implementations of the first aspect, if the resource scheduling message indicates that the service is transmitted in the SFN mode on the first resource, the resource scheduling message further includes second indication information, where the second indication information is used to indicate a reference signal associated with the service transmitted in the SFN mode, and the second indication information includes one or more of: reference signal type, reference signal number, indication bit information.

Based on the above technical solution, the resource scheduling message sent by the network device to the terminal device may further include second indication information for indicating a reference signal associated with the service transmitted in the SFN mode, and according to the second indication information, the terminal device may determine parameters such as a time-frequency synchronization signal and a receiving beam direction when receiving the service transmitted in the SFN mode, so that the same service data synchronously sent from different transmission nodes of the network device may be effectively received.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: transmitting first configuration information, the first configuration information comprising: reference signal type, reference signal number, indication bit information.

With reference to the first aspect, in some implementations of the first aspect, if the resource scheduling message indicates that the service is transmitted in the SFN mode on the first resource, the resource scheduling message further includes a first Temporary Mobile Group Identity (TMGI), the first TMGI being used to indicate a reference signal and a second TMGI associated with the service transmitted in the SFN mode, and the first TMGI being associated with the second TMGI, the second TMGI being used to identify an identifier of the service transmitted in the SFN mode.

Based on the above technical solution, the resource scheduling message sent by the network device to the terminal device may further include a first TMGI, and the terminal device may determine, according to the first TMGI, a parameter when receiving the service transmitted in the SFN mode, so as to effectively receive the same service data synchronously sent by different transmission nodes of the network device, may also determine a second TMGI, and further may determine a type of the service transmitted in the SFN mode according to the second TMGI, and if the terminal device is not interested in the service transmitted in the SFN mode, the terminal device may not receive the service transmitted in the SFN mode, so as to achieve the purpose of saving power consumption.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: sending second configuration information, wherein the second configuration information comprises: the first TMGI, the second TMGI, and a reference signal associated with the service transmitted in SFN mode.

In a second aspect, a method for resource scheduling is provided, where the method includes: receiving a resource scheduling message, the resource scheduling message indicating a first resource; determining whether to transmit traffic in SFN mode on the first resource according to the resource scheduling message.

With reference to the second aspect, in some implementations of the second aspect, receiving the resource scheduling message for the first resource includes: receiving the resource scheduling message on a second resource; wherein determining whether to transmit the service in the SFN mode on the first resource according to the resource scheduling message comprises: if the second resource is an SFN resource, indicating that the service is transmitted in an SFN mode on the first resource, wherein the SFN resource is a resource for transmitting the service in the SFN mode; if the second resource is a non-SFN resource, it indicates that the service is transmitted in a non-SFN mode on the first resource.

With reference to the second aspect, in some implementations of the second aspect, the resource scheduling message includes first indication information for indicating a transmission mode; wherein determining whether to transmit traffic in an SFN mode on the first resource according to the resource scheduling message comprises: if the first indication information indicates that the sending mode is the SFN mode, the SFN mode is used for transmitting the service on the first resource; if the first indication information indicates that the transmission mode is a non-SFN mode, it indicates that the service is transmitted in the non-SFN mode on the first resource.

With reference to the second aspect, in some implementations of the second aspect, the determining whether to transmit the service in the SFN mode on the first resource according to the resource scheduling message includes: if the resource scheduling message can be received with the first radio network temporary identifier RNTI as the scrambling code, it indicates that the traffic is transmitted in the SFN mode on the first resource, and if the resource scheduling message cannot be received with the first RNTI as the scrambling code, it indicates that the traffic is transmitted in the non-SFN mode on the first resource.

Optionally, the first RNTI may be an SFN-RNTI.

With reference to the second aspect, in certain implementation manners of the second aspect, in case that the second resource is an SFN resource, the resource scheduling message is further configured to indicate a parameter K0, where a value of the parameter K0 indicates a number of time domain resource units spaced between the first resource and the second resource, where the time domain resource units do not include a resource that is not available for transmitting a service in an SFN mode.

With reference to the second aspect, in some implementations of the second aspect, if the resource scheduling message indicates that the service is transmitted in the SFN mode on the first resource, the resource scheduling message further includes second indication information, where the second indication information is used to indicate a reference signal associated with the service transmitted in the SFN mode, and the second indication information includes one or more of the following: reference signal type, reference signal number, indication bit information.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: receiving first configuration information, the first configuration information comprising: reference signal type, reference signal number, indication bit information.

With reference to the second aspect, in certain implementations of the second aspect, if the resource scheduling message indicates that the service is transmitted in the SFN mode on the first resource, the resource scheduling message further includes a first temporary mobile group identification, TMGI, the first TMGI being used to indicate a reference signal and a second TMGI associated with the service transmitted in the SFN mode, and the first TMGI being associated with the second TMGI, the second TMGI being used to identify the identifier of the service transmitted in the SFN mode.

Based on the above technical solution, the resource scheduling message sent by the network device to the terminal device may further include a first TMGI, and the terminal device may determine, according to the first TMGI, a parameter when receiving the service transmitted in the SFN mode, so as to effectively receive the same service data synchronously sent by different transmission nodes of the network device, may also determine a second TMGI, and further may determine a service type transmitted in the SFN mode according to the second TMGI, and if the terminal device is not interested in the service transmitted in the SFN mode, the terminal device may not receive the service transmitted in the SFN mode, so as to achieve the purpose of saving power consumption.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: receiving second configuration information, the second configuration information comprising: the first TMGI, the second TMGI, and a reference signal associated with the service transmitted in SFN mode.

It will be appreciated that the first aspect described above may be combined with the method provided in the second aspect.

In a third aspect, a communication device is provided, which includes various means or units for performing the method of the first aspect and any one of the possible implementations of the first aspect.

In a fourth aspect, a communication device is provided, which comprises means for performing the method of the second aspect and any one of the possible implementations of the second aspect.

In a fifth aspect, a communications apparatus is provided that includes a processor. The processor is coupled to the memory and is operable to execute instructions or data in the memory to implement the method of any one of the possible implementations of the first aspect and the first aspect. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

In one implementation, the communication device is a network device. When the communication device is a network device, the communication interface may be a transceiver, or an input/output interface.

In another implementation, the communication device is a chip configured in the network device. When the communication device is a chip configured in a network device, the communication interface may be an input/output interface.

Alternatively, the transceiver may be a transmit-receive circuit. Alternatively, the input/output interface may be an input/output circuit.

In a sixth aspect, a communications apparatus is provided that includes a processor. The processor is coupled to the memory and is operable to execute instructions or data in the memory to implement the method of any of the second aspect and possible implementations of the second aspect. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

In one implementation, the communication device is a terminal device. When the communication device is a terminal device, the communication interface may be a transceiver, or an input/output interface.

In another implementation, the communication device is a chip configured in the terminal equipment. When the communication device is a chip configured in a terminal device, the communication interface may be an input/output interface.

In a seventh aspect, a processor is provided, including: input circuit, output circuit and processing circuit. The processing circuit is configured to receive a signal through the input circuit and send a signal through the output circuit, so that the processor performs the method of any one of the possible implementations of the first aspect to the second aspect and the first aspect to the second aspect.

In a specific implementation process, the processor may be one or more chips, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, various logic circuits, and the like. The input signal received by the input circuit may be received and input by, for example and without limitation, a receiver, the signal output by the output circuit may be output to and transmitted by a transmitter, for example and without limitation, and the input circuit and the output circuit may be the same circuit that functions as the input circuit and the output circuit, respectively, at different times. The embodiment of the present application does not limit the specific implementation manner of the processor and various circuits.

In an eighth aspect, a processing apparatus is provided that includes a processor and a memory. The processor is configured to read instructions stored in the memory, and may receive a signal via the receiver and transmit a signal via the transmitter to perform the method of any one of the possible implementations of the first to second aspects and the first to second aspects.

Optionally, the number of the processors is one or more, and the number of the memories is one or more.

Alternatively, the memory may be integral to the processor or provided separately from the processor.

In a specific implementation process, the memory may be a non-transient memory, such as a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.

It will be appreciated that the associated data interaction process, for example, sending the indication information, may be a process of outputting the indication information from the processor, and receiving the capability information may be a process of receiving the input capability information from the processor. In particular, data output by the processor may be output to a transmitter and input data received by the processor may be from a receiver. The transmitter and receiver may be collectively referred to as a transceiver, among others.

The processing means in the above-mentioned eighth aspect may be one or more chips. The processor in the processing device may be implemented by hardware or may be implemented by software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated with the processor, located external to the processor, or stand-alone.

In a ninth aspect, there is provided a computer program product, the computer program product comprising: a computer program (which may also be referred to as code, or instructions), which when executed, causes the method of any one of the possible implementations of the first to second aspects and the first to second aspects described above to be performed.

A tenth aspect provides a computer-readable storage medium storing a computer program (which may also be referred to as code or instructions) which, when executed on a computer, causes the computer to perform the method of any one of the possible implementations of the first to second aspects and the first to second aspects.

In an eleventh aspect, there is provided a communication system comprising: the aforementioned network device, and/or terminal device.

Drawings

Fig. 1 is a schematic diagram of a communication system of a method provided in an embodiment of the present application.

Fig. 2 is a schematic diagram of an extended CP and a normal CP provided in an embodiment of the present application.

Fig. 3 is a schematic flow chart of a method for resource scheduling provided by an embodiment of the present application.

Fig. 4 is a schematic diagram of a communication system of a method provided in an embodiment of the present application.

Fig. 5 is a schematic diagram of a method for using an associated reference signal according to an embodiment of the present application.

Fig. 6 is a schematic flow chart of a method for resource scheduling provided by an embodiment of the present application.

Fig. 7 is a schematic diagram of a method for resource scheduling according to an embodiment of the present application.

Fig. 8 is a schematic diagram of a method for resource scheduling according to an embodiment of the present application.

Fig. 9 is a schematic diagram of a method for resource scheduling according to an embodiment of the present application.

Fig. 10 is a schematic diagram of a method for resource scheduling according to an embodiment of the present application.

Fig. 11 is a schematic flow chart of a method for resource scheduling provided by an embodiment of the present application.

Fig. 12 is a schematic diagram of a method for resource scheduling according to an embodiment of the present application.

Fig. 13 is a schematic diagram of a method for resource scheduling according to an embodiment of the present application.

Fig. 14 is a schematic diagram of a method for resource scheduling according to an embodiment of the present application.

Fig. 15 is a schematic diagram of a method for resource scheduling according to an embodiment of the present application.

Fig. 16 is a schematic block diagram of a communication device provided in an embodiment of the present application.

Fig. 17 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

Fig. 18 is a schematic structural diagram of a network device according to an embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

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 Universal Mobile Telecommunications System (UMTS), a universal microwave access (WiMAX) communication system, a fifth generation (5th generation, 5G) mobile communication system or a new radio access technology (NR) or a next generation communication, such as 6G. The 5G mobile communication system may be a non-independent Network (NSA) or an independent network (SA), among others.

The technical scheme provided by the application can also be applied to Machine Type Communication (MTC), Long Term Evolution-machine (LTE-M) communication between machines, device to device (D2D) network, machine to machine (M2M) network, internet of things (IoT) network, or other networks. The IoT network may comprise, for example, a car networking network. The communication modes in the car networking system are collectively referred to as car-to-other devices (V2X, X may represent anything), for example, the V2X may include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) or vehicle to network (V2N) communication, etc.

The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation mobile communication system and the like. This is not limited in this application.

In the embodiment of the present application, the network device may be any device having a wireless transceiving function. Such devices include, but are not limited to: evolved Node B (eNB), Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), home base station (e.g., home evolved Node B or home Node B, HNB), baseband unit (BBU), Access Point (AP) in wireless fidelity (WiFi) system, wireless relay Node, wireless backhaul Node, Transmission Point (TP) or Transmission and Reception Point (TRP), etc., and may also be 5G, such as NR, gbb in the system, or transmission point (TRP or TP), one or a group of base stations in the 5G system may also include multiple antennas, or panels, and may also be configured as network panels or NB, such as a baseband unit (BBU), or a Distributed Unit (DU), or a base station in a next generation communication 6G system, etc.

In some deployments, the gNB may include Centralized Units (CUs) and DUs. The gNB may further include an Active Antenna Unit (AAU). The CU implements part of functions of the gNB, and the DU implements part of functions of the gNB, for example, the CU is responsible for processing non-real-time protocols and services, and implements functions of a Radio Resource Control (RRC) layer and a Packet Data Convergence Protocol (PDCP) layer. The DU is responsible for processing a physical layer protocol and a real-time service, and implements functions of a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer. The AAU implements part of the physical layer processing functions, radio frequency processing and active antenna related functions. Since the information of the RRC layer eventually becomes or is converted from the information of the PHY layer, the higher layer signaling, such as the RRC layer signaling, may also be considered to be transmitted by the DU or transmitted by the DU and the AAU under this architecture. It is to be understood that the network device may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into network devices in an access network (RAN), or may be divided into network devices in a Core Network (CN), which is not limited in this embodiment of the present application.

In the embodiments of the present application, a terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. The terminal device in the embodiment of the present application may be a mobile phone (mobile phone), a tablet (pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation security (transportation security), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local area, PDA) station, a personal digital assistant (wldigital assistant), a handheld wireless communication device with a wireless transceiving function, and a handheld personal communication device with a wireless communication function, A computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network, a terminal device in a Public Land Mobile Network (PLMN) for future evolution, or a terminal device in a non-public network, etc.

Wherein, wearable equipment also can be called as wearing formula smart machine, is the general term of using wearing formula technique to carry out intelligent design, developing the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.

Furthermore, the terminal device may also be a terminal device in an Internet of things (IoT) system. The IoT is an important component of future information technology development, and is mainly technically characterized in that articles are connected with a network through a communication technology, so that an intelligent network with man-machine interconnection and object interconnection is realized.

The specific form of the terminal device is not limited in the present application.

For the understanding of the embodiments of the present application, a communication system suitable for the embodiments of the present application will be described in detail with reference to fig. 1. Fig. 1 is a schematic diagram of a communication system suitable for the method provided in the embodiment of the present application.

As shown in fig. 1, the communication system 100 may include a plurality of network devices, such as the network device 110 and the network device 120 shown in fig. 1, and the communication system 100 may include at least one terminal device, such as the terminal device 130 shown in fig. 1. The network device may transmit data to the terminal device in SFN mode. The so-called SFN mode is when a plurality of adjacent network devices or transmitting nodes transmit the same data to the terminal device. Correspondingly, the terminal device may receive the same data from multiple network devices or transmitting nodes in the SFN manner. For example, in fig. 1, network device 110 and network device 120 form an SFN transmission group covering a certain size of area, and network device 110 and network device 120 may transmit the same data in SFN mode on a specific time and frequency resource. Correspondingly, terminal device 130 may receive the same data from network device 110 and network device 120 in SFN manner.

It should be understood that the figures are only schematic and show two network devices and two terminal devices, but this should not limit the present application in any way. In the communication system, a larger number of terminal devices and a larger number of network devices may also be included.

Since the SFN mode is that a plurality of network devices transmit the same data, a device like a central control unit is required to coordinate the transmission time and transmission content of each network device in the process of transmitting data in the SFN mode. The functions of the central control unit device may be performed by a certain network device or may be performed by a separate device.

In a fourth generation (4th generation, 4G) mobile communication system, in order to simplify coordination between network devices, the network devices configure slot resources for transmitting broadcast multicast data in a semi-static manner in an SFN manner, and transmit these semi-static configuration information to terminal devices. The configuration information of SFN timeslot resources required by the terminal device has the following two main reasons:

(1) if the network device transmits channel data or signals in SFN mode, the slot format of the channel data or signals is an extended Cyclic Prefix (CP). If the network device sends the channel data or signal in a non-SFN manner, the slot format of the channel data or signal is a normal CP. On the side of the terminal device, the received symbols of the extended CP and the normal CP require timing conversion. Fig. 2 shows an example of the normal CP and the extended CP, and as shown in fig. 2, if the network device transmits data on the extended CP slot n +6, the slot format of the data is the extended CP, and if the network device transmits data on the normal CP slot n +2, the slot format of the data is the normal CP.

(2) When the network device transmits channel data or signals in the SFN mode, the terminal device needs to know the time and/or frequency synchronization signal with different network devices, which is transmitted to the terminal device by the network device, since the channel data or signals come from multiple network devices. If the network device transmits channel data or signals in a non-SFN mode, the terminal device receives multicast broadcast data from only one network device, and thus the time and/or frequency synchronization signal comes from only one network device. That is, if the terminal device receives data in the SFN mode, it will switch to the time and/or frequency synchronization signal of the SFN mode to perform time/frequency synchronization; if the terminal equipment receives data in a non-SFN manner, time and/or frequency synchronization is performed on the time and/or frequency synchronization signal of the local cell.

However, configuring SFN resources in a semi-static manner means that only SFN resources are configured, traffic can be transmitted in SFN mode on SFN resources, and only traffic in SFN mode can be transmitted on SFN resources. The idle SFN resource cannot be used when the communication speed of the service transmitted in the non-SFN mode increases. When the traffic demand for transmission in SFN mode becomes large, the idle ordinary resources cannot be used by itself. Therefore, configuring SFN resources in a semi-static manner will result in poor resource flexibility and difficulty in adapting to the requirements of different services for rate change.

In view of the above, the present application is directed to a method for resource scheduling, so as to achieve the purpose of flexibly configuring SFN resources.

The method provided by the embodiment of the application will be described in detail below with reference to the accompanying drawings.

To facilitate understanding of the embodiments of the present application, the following description is made before describing the embodiments of the present application.

First, in the embodiments of the present application, "for indicating" may include for direct indication and for indirect indication, and may also include explicit indication and implicit indication. If the information indicated by a certain piece of information is referred to as information to be indicated, in a specific implementation process, there are many ways of indicating the information to be indicated, for example, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or an index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, wherein an association relationship exists between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other part of the information to be indicated is known or predetermined. For example, indication of information to be indicated can also be implemented by means of pre-agreed (e.g., protocol specification) whether a certain cell exists, thereby reducing the indication overhead to some extent.

Second, in the embodiments shown below, the first, second and various numerical numbers are merely for convenience of description and are not intended to limit the scope of the embodiments of the present application. For example, different indication information is distinguished, and the like.

Third, the "protocol" referred to in the embodiment of the present application may refer to a standard protocol in the communication field, for example, the standard protocol may include an LTE protocol, an NR protocol, and a related protocol applied in a future communication system, which is not limited in the present application.

Fourth, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, and c, may represent: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b and c. Wherein a, b and c may be single or multiple respectively.

Fifth, in the embodiments of the present application, the descriptions "when … …", "in … …", "if" and "if" all refer to that a device (e.g., a terminal device or a network device) performs corresponding processing under a certain objective condition, and do not limit the time, and do not require a certain judgment action when the device (e.g., a terminal device or a network device) is implemented, and do not mean that there are other limitations.

Sixthly, the embodiments are described in detail below with reference to a plurality of flowcharts, but it should be understood that the flowcharts and the related description of the corresponding embodiments are only examples for easy understanding, and should not limit the present application in any way. It is not necessary that each step in the flowcharts be performed, and some steps may be skipped, for example. In addition, the execution sequence of each step is not fixed or limited to that shown in the figures, and the execution sequence of each step should be determined by the function and the inherent logic of each step. The embodiments shown below illustrate the method provided by the embodiments of the present application, taking the interaction between the network device and the terminal device as an example. This should not be construed as limiting the application in any way. For example, the terminal device shown in the following embodiments may be replaced with a component (such as a chip, a chip system, a circuit, or the like) configured in the terminal device. The network devices shown in the following embodiments may also be replaced with components (such as chips, systems of chips, circuits, etc.) configured in the network devices.

The embodiments shown below do not particularly limit the specific structure of the execution subject of the method provided by the embodiments of the present application, as long as the communication can be performed according to the method provided by the embodiments of the present application by running the program recorded with the code of the method provided by the embodiments of the present application, for example, the execution subject of the method provided by the embodiments of the present application may be a terminal device or a network device, or a functional module capable of calling the program and executing the program in the terminal device or the network device.

It should be noted that the SFN service described in the embodiment of the present application refers to a service transmitted in an SFN mode. The service may be service data or control data. The non-SFN service described in the embodiments of the present application refers to a service transmitted in a non-SFN mode, and the non-SFN mode may be, for example, a single-cell-point-to-multipoint (SC-PTM) mode.

Fig. 3 shows a schematic flowchart of a method for resource scheduling provided by an embodiment of the present application. Method 300 shown in fig. 3 may be performed by network device 110 or network device 120 and terminal device 130 shown in fig. 1. As shown in fig. 3, the method 300 includes S310 and S320, each of which is described below.

S310, the network device determines a first resource.

The network device may transmit traffic in the SFN mode on the first resource or may transmit traffic in the non-SFN mode on the first resource.

The embodiment of the present application does not specifically limit how the network device determines the first resource.

In one implementation, the network device may determine any free resources as the first resources.

The network device may not configure SFN resources for the terminal device before the network device determines any free resources as the first resources.

For example, the network device has not previously configured SFN resources for the terminal device. In this case, if the network device needs to transmit the SFN service, the resource for transmitting the SFN service is indicated to the terminal device in a dynamic scheduling manner.

In another implementation, the network device may determine, as the first resource, the non-SFN resource and the SFN resource previously configured for the terminal device, that is, the network device may determine, as the first resource, a resource that is available for transmitting the SFN service. Wherein the non-SFN resource is a normal resource or a candidate resource.

As an example, the non-SFN resource is a normal resource, i.e. the network device may determine a normal resource and an SFN resource previously configured for the terminal device as the first resource. The SFN resource may be used for transmitting SFN service, and the common resource may be used for transmitting non-SFN service as well as SFN service. In this case, the network device may transmit the configuration information #1 of the SFN resource to the terminal device before transmitting the resource scheduling message indicating the first resource, and the content and manner of transmitting the configuration information #1 by the network device will be described in detail later in conjunction with other embodiments, which will not be detailed herein.

As another example, the non-SFN resource is a candidate resource, i.e., the network device may determine the SFN resource and the candidate SFN resource as the first resource. The SFN resource is used for transmitting SFN service data, and the candidate resource may be used for transmitting SFN data or non-SFN service data. In this case, the network device may transmit the configuration information #2 of the SFN resource to the terminal device before transmitting the resource scheduling message indicating the first resource, and the content and manner of transmitting the configuration information #2 by the network device will be described in detail later in conjunction with other embodiments, which will not be detailed herein.

S320, the network equipment sends a resource scheduling message of the first resource to the terminal equipment.

Wherein the resource scheduling message is used to indicate whether the traffic is transmitted in SFN mode on the first resource, i.e. the traffic may be transmitted in SFN mode on the first resource, or may be transmitted in non-SFN mode.

Correspondingly, the terminal equipment receives the resource scheduling message. Further, the terminal device determines whether to transmit the service in the SFN mode on the first resource according to the resource scheduling message.

The embodiment of the present application does not limit how the terminal device determines whether to transmit the service in the SFN mode on the first resource.

In one implementation, the resource scheduling message may include first indication information indicating a transmission mode. The terminal device may determine whether to transmit the service in the SFN mode on the first resource according to the first indication information. If the first indication information indicates that the sending mode is the SFN mode, the terminal equipment determines that data are transmitted in the SFN mode on the first resource; if the first indication information indicates that the transmission mode is a non-SFN mode, the terminal device determines to transmit the service in the non-SFN mode on the first resource.

For example, a Downlink Control Information (DCI) transmitted from the network device to the terminal device may include a cell indicating a traffic transmission mode. The transmission mode of the traffic may include: SFN mode, SC-PTM mode. The added cells may include: modulation and coding scheme indication (modulation and coding scheme) for indicating a modulation and coding format of a service; the service sends a mode indication, which may be a boolean (boolean) type variable, for example, a value of 1 indicates SC-PTM mode and a value of 0 indicates SFN mode.

In another implementation, the network device may configure the terminal device with a first RNTI for receiving the resource scheduling message before transmitting the resource scheduling message. If the terminal device adopts the first RNTI as the scrambling code to successfully receive the resource scheduling message sent by the network device, the terminal device can determine that the service is transmitted on the first resource in the SFN mode; if the terminal device does not receive the resource scheduling message sent by the network device using the first RNTI as the scrambling code, the terminal device may determine that the service is transmitted in the non-SFN mode on the first resource.

Optionally, the first RNTI may be an SFN-RNTI.

The network device may also configure the terminal device with a second RNTI for receiving the resource scheduling message before transmitting the resource scheduling message. If the terminal device adopts the second RNTI as the scrambling code to successfully receive the resource scheduling message sent by the network device, the terminal device can determine that the service is transmitted on the first resource in the non-SFN mode; if the terminal device does not receive the resource scheduling message sent by the network device by using the second RNTI as the scrambling code, the terminal device may determine to transmit the service in the SFN mode on the first resource.

In yet another implementation, the terminal device determines whether to transmit traffic in SFN mode on the first resource according to the second resource of the transmission resource scheduling message. If the second resource is an SFN resource, the terminal device may determine to transmit the service in the SFN mode on the first resource. If the second resource is a non-SFN resource, the terminal device may determine to transmit the service in the non-SFN mode on the first resource.

In the embodiment of the present application, the network device may determine any idle resource as the first resource that can be used for transmitting the SFN service by using a dynamic scheduling method, so that the network device may adapt to the dynamic change of the transmission rate of the SFN service, flexibly schedule the SFN resource for transmitting the SFN service, and avoid resource waste.

Or, the network device may further determine an SFN resource and a common resource previously configured for the terminal device as the first resource, and further, the network device may transmit the service in the SFN mode on the idle common resource, so that the network device may adapt to a situation that a demand amount of the SFN service increases, and avoid waste of resources.

Further, the network device may transmit the service in the SFN mode on the candidate resource or transmit the service in the non-SFN mode on the candidate resource, so that the network device may adapt to the situation that the data demand of the SFN service increases, or adapt to the situation that the data demand of the non-SFN service increases, and avoid the waste of resources.

If the resource scheduling message sent by the network device to the terminal device indicates that the service is transmitted in the SFN mode on the first resource, the resource scheduling message further includes indication information for indicating a reference signal associated with SFN service data.

In one implementation, the resource scheduling message further includes second indication information indicating a Reference Signal (RS) associated with the SFN traffic transmitted on the first resource, the second indication information including one or more of: reference signal type, reference signal number, indication bit information.

The type of the reference signal is not limited in the embodiments of the present application, for example, the associated reference signal may be one or more of the following: quasi-common address (QCL), channel state information reference signal (CSI-RS), Synchronization Signal Block (SSB), Time Reference Signal (TRS), and beam receiving direction.

And the incidence relation between the associated reference signal and the SFN service is used for determining the parameter of the terminal equipment for receiving the SFN service.

For example, the association relationship between the beam receiving direction and the SFN service is used to determine the parameter configuration of the receiving antenna when the terminal device receives the SFN service.

As another example, the association between the TRS and the SFN service is used to determine the synchronization setting of the time domain and/or frequency when the terminal device receives the SFN service.

As shown in fig. 4, network device 410 and network device 420 form SFN transmission group #1, and network device 430 and network device 440 form SFN transmission group # 2. The network device 410 and the network device 420 first transmit a resource scheduling message to the terminal device 450, the resource scheduling message indicating a resource for transmitting data #1 and the resource scheduling message including TRS # 1. Correspondingly, the terminal apparatus 450 determines the time timing and the frequency timing at which the network apparatus 410 and the network apparatus 420 transmit the data #1 through the TRS # 1. Likewise, the network device 430 and the network device 440 first transmit a resource scheduling message to the terminal device 450, the resource scheduling message indicating a resource for transmitting data #2 and including TRS #2 therein. Correspondingly, terminal apparatus 450 determines the time timing and frequency timing at which network apparatus 430 and network apparatus 440 transmit data #2 through TRS # 2.

As shown in fig. 5, there is a timing error between the time timing and the frequency timing determined by the terminal device based on the TRS #1 and the time timing and the frequency timing determined by the TRS #2, and if the terminal device receives the data #2 based on the time timing and the frequency timing determined by the TRS #1, a reception error may occur as well if the terminal device receives the data #1 based on the time timing and the frequency timing determined by the TRS # 2.

The second indication information may only include indication bit information, and since there is a one-to-one correspondence relationship between the indication bit information and different associated reference signals, the terminal device may determine a specific associated reference signal according to the indication bit information; if the network device has a one-to-one correspondence relationship between different associated reference signals and associated reference signal numbers in the configuration information of the associated reference signals sent to the terminal device in advance, the second indication information may only include the associated reference signal numbers; if only one associated reference signal of different types is in the configuration information of the associated reference signal sent by the network device to the terminal device in advance, the second indication information may only include the associated reference signal type. If different types of associated reference signals correspond to the same associated reference signal number in the configuration information of the associated reference signals sent by the network device to the terminal device in advance, the second indication information may include the associated reference signal type and the associated reference signal number. It is to be understood that, in case that the second indication information includes indication bit information, the second indication information may further include an associated reference signal type and/or an associated reference signal number.

It is to be understood that, before the network device sends the resource scheduling message to the terminal device, the network device may also send first configuration information to the terminal device, where the first configuration information includes: reference signal type, reference signal number, indication bit information.

The network device may send the first configuration information to the terminal device by using a high-level signaling. For example, the network device may send the first configuration information to the terminal device by establishing an RRC radio connection with the terminal device; alternatively, the network device may transmit the first configuration information to the terminal device through a Media Access Control (MAC) Control Element (CE). The embodiment of the present application does not limit this.

The embodiment of the present application is described by taking an example that in the first configuration information sent by the network device to the terminal device, there is a one-to-one correspondence relationship between different associated reference signals and reference signal numbers. Table 1 shows configuration information in which reference signal types and reference signal numbers correspond to one another.

TABLE 1

Indicating bit information	Associated reference signal type	Associating reference signal numbers
11	TRS#1	XXXX
01	TRS#2	YYYY
10	CSI-RS#1	ZZZZ
11	CSI-RS#2	KKKK

As shown in the above table, if the first indication information is 00, the terminal device may determine that the SFN service of the current transmission is associated with the TRS #1 with the XXXX number; alternatively, if the association reference signal indicates XXXX, the terminal device may also consider that the SFN service of the current transmission is associated with TRS # 1.

In another implementation, the resource scheduling message may further include a first TMGI indicating a reference signal associated with the SFN service and a second TMGI, the first TMGI being associated with the second TMGI, the second TMGI being used to identify the SFN service.

It is to be understood that, before the network device sends the resource scheduling message to the terminal device, the network device may also send second configuration information to the terminal device, where the second configuration information includes: a first TMGI, a second TMGI, a reference signal associated with the SFN service.

The network device may send the second configuration information to the terminal device by using a high-level signaling. For example, the network device may send the second configuration information to the terminal device by establishing an RRC radio connection with the terminal device; alternatively, the network device may transmit the second configuration information to the terminal device through the MAC CE. The embodiment of the present application does not limit this.

It is to be understood that one first TMGI may correspond to one or more second TMGIs. For example, if multiple different SFN services are associated with different reference signals (i.e., indicating that the multiple different SFN services have different network transmission nodes), one first TMGI corresponds to one second TMGI; if multiple different SFN services are associated with the same reference signal (i.e., multiple different SFN services have the same network transmitting nodes), multiple second TMGIs corresponding to the multiple SFN services may correspond to one first TMGI.

Further, after the terminal device receives the first TMGI in the resource scheduling message, the number of the SFN service transmitted on the first resource indicated by the resource scheduling message may be confirmed according to the second TMGI associated with the first TMGI, and the reference signal associated with the SFN service may be confirmed.

As described above, before the network device transmits the resource scheduling message to the terminal device, the network device may transmit the configuration information #2 of the SFN resource to the terminal device. In this case, if the resource scheduling message sent by the network device to the terminal device indicates that the service is transmitted in the SFN mode on the first resource, the resource scheduling message is further used to indicate a parameter K0, and a value of the parameter K0 is used to indicate a number of time domain resource units spaced between the first resource and a second resource for transmitting the resource scheduling message, where the time domain resource units do not include a resource that is not available for transmitting the SFN service.

It is to be understood that, if the resource scheduling message indicates that the traffic is transmitted in the non-SFN mode on the first resource, the resource scheduling message may also include indication information for indicating a reference signal associated with the non-SFN traffic. The network device may also send configuration information of reference signals associated with non-SFN traffic to the terminal device before the network device sends the resource scheduling message.

For example, when the network device configures a downlink shared channel (PDSCH) for transmitting a service for the terminal device, the network device may configure a reference signal associated with the service. The configuration information sent by the network device may be, for example:

Broadcastulitcast-PDSCH configuration

{

SFN modes

{

Association RS1{ reference Signal type, reference Signal Identification (ID) }

Association RS2{ reference Signal type, reference Signal ID }

CP type { extended CP, Normal CP },// at configuration, one of them is selected

}

SC-PTM mode

{

Association RS1{ reference Signal type, reference Signal ID }

Association RS2{ reference Signal type, reference Signal ID }

}

The SFN mode refers to 2 or more than 2 network transmission nodes, which synchronously transmit the same service data; correspondingly, the terminal equipment receives the service data sent by different sending nodes through different transmission paths. The SC-PMT mode refers to a mode in which a single cell (which may also be understood as a single node) transmits service data in a broadcast or multicast manner.

In this embodiment, the resource scheduling message sent by the network device to the terminal device may further include second indication information for indicating a reference signal associated with the SFN service, and according to the second indication information, the terminal device may determine parameters such as a time-frequency synchronization signal and a receiving beam direction when receiving the SFN service, so that the same SFN service synchronously sent from different transmission nodes of the network device may be effectively received.

Or, the resource scheduling message sent by the network device to the terminal device may further include a first TMGI, and the terminal device may determine, according to the first TMGI, a parameter when receiving the SFN service, so that the same service data synchronously sent by different transmission nodes of the network device may be effectively received, may also determine a second TMGI, and further may determine the SFN service type according to the second TMGI, and if the terminal device is not interested in the SFN service, the SFN service may not be received, so that the purpose of saving power consumption may be achieved.

Fig. 6 shows a schematic flow chart of a method for resource scheduling provided by an embodiment of the present application. The method 600 shown in fig. 6 describes in more detail an example in which the non-SFN resource mentioned in step S310 is a common resource.

As shown in FIG. 6, the method 600 includes S610-S630, the steps of which are described in detail below.

S610, the network device sends the configuration information #1 to the terminal device.

Wherein, the configuration information #1 may include configuration information and indication information #1 of SFN resources and general resources.

The configuration information of the SFN resource and the common resource may include: the allocation cycle of the radio frame containing the SFN time slot, the offset of the radio frame containing the SFN time slot, and the allocation information of the SFN time slot and the common time slot in the radio frame containing the SFN time slot. The SFN slot is a slot in which the SFN resource is located, and the normal slot is a slot in which the normal resource is located. The indication information #1 is used to indicate: if the resource for transmitting the SFN service data indicated by the resource scheduling message sent by the network device is a common resource, the common resource is converted into an SFN resource.

The network device may send configuration information #1 to the terminal device by using higher layer signaling. For example, the network device may send configuration information of SFN resources to the terminal device in a manner of establishing RRC radio connection with the terminal device; alternatively, the network device may send the configuration information of the SFN resource to the terminal device through the MAC CE. The embodiments of the present application do not limit this.

The configuration information of the SFN resource sent by the network device to the terminal device may include the following information: (1) radioframe allocationperiod: indicating an allocation period of a radio frame containing SFN slots, which may be 1, 2, 4, 8, 16, 32, or other values; (2) radioframeallocationoffset: indicating an allocation offset for a radio frame containing an SFN slot, which may be 0, 1, 2, 3, 4, 5, 6, 7, or other values; (3) candidate sfn: indicating whether a certain timeslot in the radio frame containing the SFN timeslot is an SFN timeslot or a normal timeslot, where the value may be of a pool type, for example, a value of 1 indicates the SFN timeslot, and a value of 0 indicates the normal timeslot; (4) SFNslotOneFrame: the numerical value of the SFN slot allocation information in the radio frame containing the SFN slot may be a string type, where a bitmap (bitmap) is used, 1 indicates the SFN slot, 0 indicates the normal slot, and the length of the string is the number of slots included in one radio frame, for example, when a subcarrier spacing (SCS) is 15KHz, the length of the string is 10, when the SCS is 30KHz, the length of the string is 20, when the SCS is 60KHz, the length of the string is 40, and when the SCS is 120KHz, the length of the string is 80.

As shown in fig. 7, the radio frame having the SFN timeslot has an allocation period of 4, i.e., a radio frame allocation period of 4; the allocated offset of the radio frame containing the SFN slot is 0, that is, the radioframe allocationoffset is 0; the length of the radio frame shown in the figure is 10ms, and includes 20 slots, i.e. SCS is 30KHz, so the length of the value of SFNslotOneFrame is 20, the SFN slot allocation string shown in the figure is 11001000100001100010, i.e. SFNslotOneFrame is 11001000100001100010, where 1 is denoted as SFN slot, and 0 is denoted as normal slot. Therefore, it can be known that

slots

1, 2, 5, 9, 14, 15, and 19 in each radio frame containing SFN slots are SFN slots, and the rest slots are normal slots.

Optionally, the configuration information of the SFN resource and the common resource may further include: the allocation period of the slot containing the SFN symbol, the offset of the slot containing the SFN symbol, and the allocation information of the SFN symbol and the ordinary symbol in the slot containing the SFN symbol. The SFN symbol is a symbol where the SFN resource is located, and the normal symbol is a symbol where the normal resource is located. The indication information #1 is used to indicate: if the resource for transmitting the SFN service data, indicated by the resource scheduling message sent by the network device, is a common resource, the common resource is converted into an SFN resource.

The configuration information of the SFN resource sent by the network device to the terminal device may include the following information: (1) radioframe allocationperiod: indicating an allocation period of a slot containing an SFN symbol, which may have a period of 1, 2, 4, 8, 16, 32, or other values; (2) radioframeallocationoffset: an allocation offset indicating a slot containing SFN symbols, which may have a value of 0, 1, 2, 3, 4, 5, 6, 7, or other values; (3) candidate sfn: indicating whether a symbol in the radio frame containing the SFN symbol is an SFN symbol or a normal symbol, where the value may be a bool type, for example, a value of 1 indicates the SFN symbol, and a value of 0 indicates the normal symbol; (4) SFNslotOneFrame: the value of the allocation information of the SFN symbol in the slot containing the SFN symbol may be a character string type, a bit mapping (bitmap) manner is adopted, 1 is denoted as the SFN symbol, 0 is denoted as a common symbol, the length of the character string is 14, and the method for representing the allocation information may use an enumeration method, such as a fixed concentration case { frontalt-slot, endhalf-slot, and all-slot }, where frontalt-slot denotes that the first seven symbols in one slot are SFN symbols, endhalf-slot denotes that the last seven symbols in one slot are SFN symbols, and all-slot denotes that all symbols in one slot are SFN symbols.

As shown in fig. 8, the allocation period of the timeslot including the SFN symbol is 4, that is, the radioframe allocationperiod is 4, the allocation offset of the timeslot including the SFN symbol is 0, that is, the radioframe allocationoffset is 0, the length of the value of SFNslotOneFrame is 14, the SFN symbol allocation string shown in the figure is 00000001111111, that is, SFNslotOneFrame is 00000001111111, where 1 is denoted as an SFN symbol and 0 is denoted as a common symbol. Therefore, it can be seen that the first seven symbols of each slot containing SFN symbols are normal symbols, and the last seven symbols are SFN symbols.

S620, the network device determines the first resource.

As described previously, the network device may determine the SFN resource and the normal resource as the first resource.

S630, the network device transmits a resource scheduling message #1 (an example of a resource scheduling message) on the SFN resource.

Wherein the resource scheduling message #1 indicates that the traffic is transmitted in the SFN mode on the first resource.

As described above, if the terminal device receives the resource scheduling message #1 on the SFN resource, it can be determined that the resource scheduling message #1 indicates that the traffic is transmitted in the SFN mode on the first resource.

It can be understood that, if the network device transmits the configuration information of the SFN resource to the terminal device, the network device transmits the resource scheduling message #1 to the terminal device only on the SFN resource. Correspondingly, the terminal device receives the resource scheduling message #1 only on SFN resources. If the terminal device receives the resource scheduling message #1 from the network device on the SFN resource, it can be determined that the resource indicated by the resource scheduling message #1 is a resource for transmitting SFN service data. Further, the terminal equipment receives SFN service data on the resource indicated by the resource scheduling message #1 in an SFN manner.

As described above, the network device may determine the SFN resource and the normal resource as the first resource, and thus the first resource indicated by the resource scheduling message #1 may be the SFN resource or the normal resource. And the terminal device can determine, according to the indication information #1, that if the first resource is a normal resource, the normal resource is converted into an SFN resource.

For example, the network device transmits the resource scheduling message #1 to the terminal device through the SFN resource in the time slot n, and the time domain position of the first resource indicated by the resource scheduling message #1 is in the normal time slot n +2, that is, the first resource is a normal resource. Further, the network device transmits the SFN service to the terminal device through the first resource indicated by the resource scheduling message #1 in the time slot n + 2. Correspondingly, the terminal equipment receives the SFN service in the time slot n +2 in an SFN mode. And, the normal resource on the slot n +2 is converted into the SFN resource. As shown in fig. 9, in the SFN scheduling signaling sent by the network device through the SFN resource in the time slot n, the indicated time domain position of the resource for transmitting the SFN service is in the normal time slot n +2, and then the normal resource in the time slot n +2 is scheduled as the SFN resource.

As described above, if the terminal device receives the resource scheduling message #2 (another example of the resource scheduling message) on the normal resource, it may be determined that the resource scheduling message #2 indicates non-SFN mode transmission traffic on the first resource.

The network device may scramble the resource scheduling message #1 using a broadcast radio network temporary identity (bc-RNTI). Correspondingly, the terminal device receives the resource scheduling message #1 using bc-RNTI as a scrambling code.

In one implementation, the resource scheduling message #1 sent by the network device to the terminal device may include: a frequency domain resource allocation indication (frequency domain resource allocation) for indicating a frequency domain information position of a resource for transmitting the SFN service; a time domain resource allocation indication (time domain resource allocation) for indicating a time domain information position of a resource for transmitting the SFN service; modulation and coding scheme (modulation and coding scheme) for indicating a modulation and coding format of the SFN service; an associated reference signal indicator (an example of the second indication information) is used to indicate an associated reference signal index when the terminal device receives the SFN service.

The time domain resource indication includes a slot offset K0 (an example of a parameter K0) and a Start Length Indication Value (SLIV). K0 indicates the number of time domain resource units spaced between the resource indicated by the resource scheduling message #1 and the resource indicated by the resource scheduling message #1, for example, K0 is 1, and the number of time domain resource units spaced between the resource indicated by the resource scheduling message #1 and the resource indicated by the resource scheduling message #1 is 0, and it may be understood that the resource indicated by the resource scheduling message #1 and the resource of the resource scheduling message #1 are in the same time slot, or, for example, K0 is 1, and the number of time domain resource units spaced between the resource indicated by the resource scheduling message #1 and the resource of the resource scheduling message #1 is 1, and it may be understood that the resource indicated by the resource scheduling message #1 is in the time slot next to the time slot in which the resource of the resource scheduling message #1 is located. The SLIV is used to indicate a starting symbol and a symbol length of a resource indicated in the resource scheduling message #1 in a certain slot, S denotes the starting symbol, and L denotes the symbol length.

As shown in fig. 10, the time domain resource indication parameters included in the DCI sent by the network device in the time slot n are: k0 ═ 1, starting symbol (S): #0, symbol length (L): 14, indicating that the time domain position of the resource indicated by the DCI transmitted by the network device in slot n is next to slot n, i.e. slot n +1, and the starting symbol of the resource indicated by the DCI is #0 and the symbol length is 14; the time domain resource indication parameter included in the DCI transmitted by the network device in the time slot n +3 is: k0 ═ 0, starting symbol (S): #3, symbol length (L): 11, it indicates that the resource indicated by the DCI transmitted by the network device in slot n +3 is in the same slot of slot n, i.e. slot n +3, and the starting symbol of the resource indicated by the DCI is #3 and the symbol length is 11.

Before the network device transmits the resource scheduling message #1 to the terminal device, the network device may transmit first configuration information to the network device, where the first configuration information may include: associated reference signal type, associated reference signal number, indication bit information. Wherein, the indication bit information is in one-to-one correspondence with different associated reference signals.

The manner and content of sending the first configuration information to the terminal device by the network device are as described above, and are not described herein again for brevity.

In another implementation, the resource scheduling message #1 sent by the network device to the terminal device may include: a frequency domain resource allocation indication for indicating the frequency domain information position of the resource for transmitting the SFN service; a time domain resource allocation indication for indicating the time domain information position of the resource for transmitting the SFN service; a modulation coding format for indicating the modulation coding format of the SFN service; and the first TMGI is used for indicating the associated reference signal index and the identification number of the SFN service when the terminal equipment receives the SFN service.

Before the network device sends the resource scheduling message #1 to the terminal device, the network device may send second configuration information to the terminal device, and the second configuration information may include: a second TMGI; a first TMGI value; an associated reference signal type; reference signal numbers are associated. Wherein the second TMGI is used to identify the identifier of the SFN service data, and the value of the first TMGI is the number associated with the second TMGI.

The manner and content of sending the second configuration information to the terminal device by the network device are as described above, and are not described herein again for brevity.

In the embodiment of the application, the network device adopts a semi-static mode to configure the SFN resources for transmitting the SFN services and the common resources for transmitting the SFN services and the non-SFN services for the terminal device, and the common resources can be scheduled as the SFN resources under the condition that the demand of the SFN services is increased, so that the demand increase of the SFN services can be adapted, and the aim of flexibly configuring the SFN resources is fulfilled.

Fig. 11 shows a schematic flowchart of a method for resource scheduling according to another embodiment of the present application. The method 1100 shown in fig. 11 describes in more detail examples where the non-SFN resource mentioned in step S310 is a normal resource and a candidate resource.

As shown in fig. 11, the method 1100 may include S1101-S1103, each of which is described in detail below.

S1101, the network device transmits configuration information #2 to the terminal device.

The configuration information #2 may include configuration information and indication information #2 of SFN resources, normal resources, and candidate resources, among others.

The configuration information of the SFN resource, the common resource and the candidate resource may include: the allocation period of the wireless frame containing the SFN time slot, the offset of the wireless frame containing the SFN time slot, and the allocation information of the SFN time slot, the ordinary time slot and the candidate time slot in the wireless frame containing the SFN time slot. The SFN time slot is a time slot in which the SFN resource is located, the normal time slot is a time slot in which the normal resource is located, and the candidate time slot is a time slot in which the candidate resource is located. The indication information #2 is used to indicate: if the resource for transmitting the SFN service indicated by the resource scheduling message sent by the network equipment is a candidate resource, the candidate resource is converted into the SFN resource; if the resource for transmitting the non-SFN service indicated by the resource scheduling message sent by the network equipment is a candidate resource, the candidate resource is converted into a common resource.

The network device may send configuration information #2 to the terminal device by using higher layer signaling. For example, the network device may send configuration information of SFN resources to the terminal device in a manner of establishing RRC radio connection with the terminal device; alternatively, the network device may send the configuration information of the SFN resource to the terminal device through the MAC CE. The embodiment of the present application does not limit this.

It should be understood that the network device may first send the configuration information of the SFN resource to the terminal device, and then send the configuration information of the candidate resource to the terminal device; or, first send the configuration information of the candidate resource to the terminal device, and then send the configuration information of the SFN resource to the terminal device, which is not limited in the embodiment of the present application.

The embodiment of the present application takes an example in which a network device first sends configuration information of SFN resources to a terminal device, and then sends configuration information of candidate resources to the terminal device.

The configuration information of the SFN resource sent by the network device to the terminal device is the same as that described in S610 of the method 600, and is not described herein again for brevity.

As shown in fig. 7, the allocation period of the radio frame containing the SFN slot is 4, that is, the radio frame allocation period is 4, the allocation offset of the radio frame containing the SFN slot is 0, that is, the radio frame allocation offset is 0, the length of the radio frame shown in the figure is 10ms, and the radio frame contains 20 slots, that is, the SCS is 30KHz, so the length of the value of the SFNslotOneFrame is 20, the SFN slot allocation string shown in the figure is 11001000100001100010, that is, the SFNslotOneFrame is 11001000100001100010, where 1 is denoted as the SFN slot, and 0 is denoted as the normal slot. Therefore, it can be seen that

slots

1, 2, 5, 9, 14, 15, and 19 of each radio frame containing SFN slots are SFN slots, and the rest of slots are normal slots.

Likewise, the configuration information of the candidate resource sent by the network device to the terminal device may include the following information: (1) radioframe allocationperiod: indicating an allocation period of a radio frame containing SFN slots, which may be 1, 2, 4, 8, 16, 32, or other values; (2) radioframeallocationoffset: indicating an allocation offset for a radio frame containing an SFN slot, which may be 0, 1, 2, 3, 4, 5, 6, 7, or other values; (3) candidate sfn: indicating whether a certain timeslot in the radio frame containing the SFN timeslot is a candidate timeslot or a normal timeslot, where the value may be of a pool type, for example, a value of 1 indicates the candidate timeslot, and a value of 0 indicates the normal timeslot; (4) SFNslotOneFrame: the value of the allocation information of the candidate timeslot in the wireless frame containing the MBSFN timeslot may be a string type, and a bitmap method is adopted, where 1 denotes a candidate timeslot, 0 denotes a normal timeslot, and the length of the string is the number of timeslots included in one wireless frame, for example, when a sub-carrier spacing (SCS) is 15KHz, the length of the string is 10, when the SCS is 30KHz, the length of the string is 20, when the SCS is 60KHz, the length of the string is 40, and when the SCS is 120KHz, the length of the string is 80.

As shown in fig. 12, the allocation period of the radio frame containing the SFN is 4, that is, the radio frame allocation period is 4, the allocation offset of the radio frame containing the SFN is 0, that is, the radio frame allocation offset is 0, the length of the radio frame shown in the figure is 10ms, and the radio frame shown in the figure includes 20 slots, that is, SCS is 30KHz, so that the length of the value of the SFNslotOneFrame is 20, the candidate slot allocation string shown in the figure is 0011001000100001100, that is, SFNslotOneFrame is 0011001000100001100, where 1 represents a candidate slot, 0 represents a normal slot, and therefore, it can be known that

slots

3, 4, 7, 11, 12, 17, and 18 of each radio frame containing the SFN slot are candidate slots, and the rest are normal slots.

By integrating the configuration information of the SFN resource and the configuration information of the candidate timeslot resource sent by the network device to the terminal device, the terminal device can determine which timeslots are SFN timeslots, which timeslots are candidate timeslots, and which timeslots are normal timeslots in a wireless frame containing SFN timeslots.

Referring to fig. 7 and 12, as shown in fig. 13, each of

slots

1, 2, 5, 9, 14, 15, and 19 of the radio frame including the SFN slot is the SFN slot,

slots

3, 4, 7, 11, 12, 17, and 18 are candidate slots, and the rest slots are normal slots.

S1102, the network device determines a first resource that can be an SFN resource.

As previously described, the network device may determine the SFN resource and the candidate resource as the first resource.

S1103, the network device transmits the resource scheduling message #1 on the SFN resource.

Wherein, the first resource indicated by the resource scheduling message #1 is an SFN resource.

As described above, if the terminal device receives the resource scheduling message #1 at the SFN resource, it may be determined that the resource scheduling message #1 indicates that the service is transmitted in the SFN mode on the first resource.

As described above, the network device may determine the SFN resource and the candidate resource as the first resource, and thus the first resource indicated by the resource scheduling message #1 may be the SFN resource or the candidate resource. And the terminal device may determine, according to the indication information #2, that if the first resource indicated by the resource scheduling message #1 is a candidate resource, the candidate resource is changed to an SFN resource.

For example, the network device transmits the resource scheduling message #1 to the terminal device through the SFN resource in the time slot n, and the time domain position of the first resource indicated by the resource scheduling message #1 is in the candidate time slot n +2, i.e. the first resource is a candidate resource. Further, the network device transmits the SFN service to the terminal device through the first resource in the candidate timeslot n + 2. Correspondingly, the terminal equipment receives the SFN service in the candidate time slot n +2 in an SFN mode. And the candidate resource at slot n +2 is converted to an SFN resource. As shown in fig. 14, in the SFN scheduling signaling sent by the network device through the SFN resource in SFN slot n, the indicated time domain position of the transmission resource for transmitting the SFN service is in candidate slot n +2, and then the candidate resource in slot n +2 is scheduled as the SFN resource.

As described above, if the terminal device receives the resource scheduling message #2 on the normal resource, it may be determined that the resource scheduling message #2 indicates that the traffic is transmitted in the non-SFN mode on the first resource. And the first resource indicated by the resource scheduling message #2 may be a normal resource or a candidate resource. And the terminal device may determine, according to the indication information #2, that if the first resource indicated by the resource scheduling message #2 is a candidate resource, the candidate resource is changed to a normal resource.

For example, the network device transmits a resource scheduling message #2 to the terminal device through the normal resource in the time slot n +5, and the time domain position of the first resource indicated by the resource scheduling message #2 is in the candidate time slot n + 6. Further, the network device transmits the non-SFN service to the terminal device through the first resource indicated by the resource scheduling message #2 in the candidate time slot n + 6. Correspondingly, the terminal equipment receives the non-SFN service data on the candidate time slot n + 6. And, the candidate resource on the slot n +6 is changed to the normal resource. As shown in fig. 14, in the time slot n +5, through the normal scheduling signaling sent by the normal resource, the time domain position of the transmission resource for transmitting the non-SFN service, which is indicated by the network device, is in the candidate time slot n +6, and then the candidate resource in the time slot n +6 is scheduled as the normal resource.

The network device may scramble the resource scheduling message #1 with bc-RNTI. Correspondingly, the terminal device receives the resource scheduling message #1 using bc-RNTI as a scrambling code.

As described above, the resource scheduling message #1 transmitted by the network device to the terminal device may include: frequency domain resource allocation indication, time domain resource allocation indication, modulation coding format, and associated reference signal indication.

Under the condition that the network device configures SFN resources, common resources and candidate resources for the terminal device, the calculation method of the parameter K0 is as follows: only SFN resources and candidate resources for an interval between the resource for transmitting the resource scheduling message #1 and the resource for transmitting SFN service data are calculated, and not for general resources.

As shown in fig. 15, the time domain resource indication parameters included in the DCI sent by the network device in the time slot n are: k0 ═ 1, starting symbol (S): #0, symbol length (L): 14, indicating that the time domain position of the resource indicated by the DCI transmitted by the network device at the time slot n is at the time slot n +2, that is, only the SFN slot and the candidate slot are calculated when calculating K0. Since the slot n +1 is a normal slot, the slot n +1 is skipped when calculating K0, and the starting symbol of the indicated resource is #0 and the symbol length is 14; the time domain resource indication parameter included in the DCI transmitted by the network device in the time slot n +3 is: k0 ═ 0, starting symbol (S): #3, symbol length (L): 11, indicating that the resource indicated by the DCI transmitted by the network device in slot n +3 is in the same slot of slot n +3, i.e. slot n +3, and the starting symbol of the indicated resource is #3 and the symbol length is 11.

Before the network device transmits the resource scheduling message #1 to the terminal device, the network device may transmit first configuration information to the network device, and the first configuration information may include: associated reference signal type, associated reference signal number, indication bit information. Wherein, the indication bit information is in one-to-one correspondence with different associated reference signals.

As described above, the resource scheduling message #1 sent by the network device to the terminal device may further include: a frequency domain resource allocation indication, a time domain resource allocation indication, a modulation and coding format, and a first TMGI.

Before the network device sends the resource scheduling message #1 to the terminal device, the network device may send second configuration information to the terminal device, and the second configuration information may include: a second TMGI; a first TMGI value; an associated reference signal type; reference signal numbers are associated.

In the embodiment of the application, the network device configures SFN resources for transmitting SFN service data, common resources for non-SFN services, and candidate resources for transmitting non-SFN services and SFN services for the terminal device in a semi-static manner, where the candidate resources may be scheduled as SFN resources when a demand of the SFN service increases, and the candidate resources may be scheduled as common resources when the demand of the non-SFN service increases, so that the purpose of flexibly configuring SFN resources is achieved.

The method provided by the embodiment of the present application is described in detail above with reference to fig. 2 to fig. 15. Hereinafter, the apparatus provided in the embodiment of the present application will be described in detail with reference to fig. 16 to 18.

Fig. 16 is a schematic block diagram of a communication device provided in an embodiment of the present application. As shown in fig. 16, the communication device 2000 may include a processing unit 2100 and a transceiving unit 2200.

In one possible design, the communication device 2000 may correspond to the terminal device in the above method embodiment, and may be, for example, the terminal device or a component (such as a chip or a chip system) configured in the terminal device.

It should be understood that the communication apparatus 2000 may correspond to the terminal device in the method 300, the method 600, and the method 1100 according to the embodiments of the present application, and that the communication apparatus 2000 may include means for performing the method performed by the terminal device in the method 300 in fig. 3, the method 600 in fig. 6, and the method 1100 in fig. 11. Also, the units in the communication device 2000 and the other operations and/or functions described above are respectively for implementing the corresponding flows of the method 300 in fig. 3, the method 600 in fig. 6, and the method 1100 in fig. 11.

When the communication apparatus 2000 is configured to execute the method 300 in fig. 3, the processing unit 2100 may be configured to execute S320 in the method 300, and the transceiver unit 2200 may be configured to execute S320 in the method 300. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

When the communication device 2000 is configured to perform the method 600 in fig. 6, the processing unit 2100 may be configured to perform S630 in the method 600, and the transceiver unit 2200 may be configured to perform S610 and S630 in the method 600. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

When the communication device 2000 is configured to perform the method 1100 in fig. 11, the processing unit 2100 may be configured to perform S1103 in the method 1100, and the transceiving unit 2200 may be configured to perform S1101 and S1103 in the method 1100. It should be understood that, the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and are not described herein again for brevity.

It is further understood that when the communication apparatus 2000 is a terminal device, the transceiver unit 2200 in the communication apparatus 2000 may be implemented by a transceiver, for example, may correspond to the transceiver 3020 in the terminal device 3000 shown in fig. 17, and the processing unit 2100 in the communication apparatus 2000 may be implemented by at least one processor, for example, may correspond to the processor 3010 in the terminal device 3000 shown in fig. 17.

It should also be understood that, when the communication device 2000 is a chip or a chip system configured in a terminal device, the transceiver unit 2200 in the communication device 2000 may be implemented by an input/output interface, and the processing unit 2100 in the communication device 2000 may be implemented by a processor, a microprocessor, an integrated circuit, or the like integrated on the chip or the chip system.

In another possible design, the communication apparatus 2000 may correspond to the network device in the above method embodiment, and may be a network device, or a component (such as a chip or a chip system) configured in a network device, for example.

It should be understood that the communication apparatus 2000 may correspond to the network device in the method 300, the method 600, and the method 1100 according to the embodiments of the present application, and the communication apparatus 2000 may include a unit for performing the method performed by the network device in the method 300 in fig. 3, the method 600 in fig. 6, and the method 1100 in fig. 11. Also, the units in the communication device 2000 and the other operations and/or functions described above are respectively for implementing the corresponding flows of the method 300 in fig. 3, the method 600 in fig. 6, and the method 1100 in fig. 11.

When the communication device 2000 is configured to execute the method 300 in fig. 3, the processing unit 2100 may be configured to execute S310 in the method 300, and the transceiver unit 2200 may be configured to execute S320 in the method 300. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

When the communication device 2000 is configured to perform the method 600 in fig. 6, the processing unit 2100 may be configured to perform S620 in the method 600, and the transceiver unit 2200 may be configured to perform S610 and S630 in the method 600. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

When the communication apparatus 2000 is configured to execute the method 1100 in fig. 11, the processing unit 2100 may be configured to execute S1102 in the method 1100, and the transceiving unit 2200 may be configured to execute S1101 and S1103 in the method 1100. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

It is further understood that when the communication apparatus 2000 is a network device, the transceiver unit 2200 in the communication apparatus 2000 may be implemented by a transceiver, for example, may correspond to the transceiver 4200 in the network device 4000 shown in fig. 18, and the processing unit 2100 in the communication apparatus 2000 may be implemented by at least one processor, for example, may correspond to the processor 4100 in the network device 4000 shown in fig. 18.

It should also be understood that, when the communication device 2000 is a chip or a system-on-chip configured in a network device, the transceiver unit 2200 in the communication device 2000 may be implemented by an input/output interface, and the processing unit 2100 in the communication device 2000 may be implemented by a processor, a microprocessor, an integrated circuit, or the like integrated on the chip or the system-on-chip.

Fig. 17 is a schematic structural diagram of a terminal device 3000 according to an embodiment of the present application. The terminal device 3000 can be applied to the system shown in fig. 1, and performs the functions of the terminal device in the above method embodiment. As shown, the terminal device 3000 includes a processor 3010 and a transceiver 3020. Optionally, the terminal device 3000 further includes a memory 3030. The processor 3010, the transceiver 3002 and the memory 3030 may communicate with each other via an internal connection path to transmit control and/or data signals, the memory 3030 is used for storing a computer program, and the processor 3010 is used for calling and running the computer program from the memory 3030 to control the transceiver 3020 to transmit and receive signals. Optionally, the terminal device 3000 may further include an antenna 3040, configured to send uplink data or uplink control signaling output by the transceiver 3020 through a wireless signal.

The processor 3010 and the memory 3030 may be combined into a processing device, and the processor 3010 is configured to execute the program codes stored in the memory 3030 to implement the functions described above. In particular, the memory 3030 may be integrated with the processor 3010 or may be separate from the processor 3010. The processor 3010 may correspond to the processing unit 2100 in fig. 16.

The transceiver 3020 may correspond to the transceiver 2200 in fig. 16, and may also be referred to as a transceiver. The transceiver 2020 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Wherein the receiver is used for receiving signals, and the transmitter is used for transmitting signals.

It should be understood that the terminal device 3000 shown in fig. 17 is capable of implementing various processes involving the terminal device in the method embodiments shown in fig. 3, 6, and 11. The operations and/or functions of the modules in the terminal device 3000 are respectively for implementing the corresponding flows in the above method embodiments. Reference may be made specifically to the description of the above method embodiments, and a detailed description is appropriately omitted herein to avoid redundancy.

The processor 3010 may be configured to perform actions implemented internally by the terminal device in the foregoing method embodiment, such as determining to transmit the service in the SFN mode on the first resource. The transceiver 3020 may be configured to perform the actions of the terminal device to transmit to or receive from the network device, such as receiving a resource scheduling message, and the like, described in the foregoing method embodiments. Please refer to the description of the previous embodiment of the method, which is not repeated herein.

The terminal device 3000 may further include a power supply 3050 for supplying power to various devices or circuits in the terminal device.

In addition to this, in order to make the functions of the terminal device more complete, the terminal device 3000 may further include one or more of an input unit 3060, a display unit 3070, an audio circuit 3080, a camera 3090, a sensor 3100, and the like, and the audio circuit may further include a speaker 3082, a microphone 3084, and the like.

Fig. 18 is a schematic structural diagram of a network device provided in the embodiment of the present application, which may be a schematic structural diagram of a base station, for example. The base station 4000 may be applied to the system shown in fig. 1, and performs the functions of the network device in the above method embodiments. As shown, the base station 4000 may include one or more radio frequency units, such as a Remote Radio Unit (RRU) 4100 and one or more baseband units (BBUs) (also referred to as Distributed Units (DUs)) 4200. The RRU 4100 may be referred to as a transceiver unit or a part of a transceiver unit, and corresponds to the transceiver unit 2200 in fig. 16. Alternatively, the transceiver unit 4100 may also be referred to as a transceiver, a transceiving circuit, a transceiver, or the like, which may include at least one antenna 4101 and a radio frequency unit 4102. Alternatively, the transceiver 4100 may include a receiving unit and a sending unit, the receiving unit may correspond to a receiver (or receiver, receiving circuit), and the sending unit may correspond to a transmitter (or transmitter, sending circuit). The RRU 4100 is mainly used for transceiving radio frequency signals and converting the radio frequency signals and baseband signals, for example, for sending resource scheduling messages to a terminal device. Please refer to the description in the previous embodiment of the method, which is not repeated herein.

The BBU 4200 is mainly used to perform baseband processing, control a base station, and the like. The RRU 4100 and the BBU 4200 may be physically disposed together or may be physically disposed separately, that is, distributed base stations.

The BBU 4200 is a control center of a base station, which may also be referred to as a processing unit, and may correspond to the processing unit 2100 in fig. 16, and may be configured to perform baseband processing functions, such as channel coding, multiplexing, modulation, spreading, and the like. For example, the BBU (processing unit) may be configured to control the base station to perform an operation procedure related to the network device in the foregoing method embodiment, for example, to generate the foregoing resource allocation information. Please refer to the description in the previous embodiment of the method, which is not repeated herein.

In an example, the BBU 4200 may be formed by one or more boards, and the multiple boards may collectively support a radio access network of a single access system (e.g., an LTE network), or may respectively support radio access networks of different access systems (e.g., an LTE network, a 5G network, or other networks). The BBU 4200 further includes a memory 4201 and a processor 4202. The memory 4201 is used to store necessary instructions and data. The processor 4202 is configured to control the base station to perform necessary actions, for example, to control the base station to perform the operation procedure related to the network device in the above method embodiment. The memory 4201 and the processor 4202 may serve one or more boards. That is, the memory and processor may be provided separately on each board. Multiple boards may share the same memory and processor. In addition, each single board can be provided with necessary circuits.

It should be understood that the base station 4000 shown in fig. 18 can implement various processes involving network devices in the method embodiments shown in fig. 3, 6, and 11. The operations and/or functions of the respective modules in the base station 4000 are respectively to implement the corresponding flows in the above-described method embodiments. Reference may be made specifically to the description of the above method embodiments, and a detailed description is appropriately omitted herein to avoid redundancy.

BBU 4200 described above may be used to perform actions described in the foregoing method embodiments that are implemented internally by the network device, while RRU 4100 may be used to perform actions described in the foregoing method embodiments that the network device sends to or receives from the terminal device. Please refer to the description of the previous embodiment of the method, which is not repeated herein.

It should be understood that the base station 4000 shown in fig. 18 is only one possible form of network device, and should not limit the present application in any way. The method provided by the application can be applied to network equipment in other forms. For example, including AAUs, and may also include CUs and/or DUs, or including BBUs and Adaptive Radio Units (ARUs), or BBUs; the network device may also be a Customer Premise Equipment (CPE) or other forms, and the present application is not limited to a specific form of the network device.

Wherein the CU and/or DU may be configured to perform the actions described in the previous method embodiments that are implemented internally by the network device, and the AAU may be configured to perform the actions described in the previous method embodiments that the network device transmits to or receives from the terminal device. Please refer to the description of the previous embodiment of the method, which is not repeated herein.

The embodiment of the application also provides a processing device, which comprises a processor and an interface; the processor is configured to perform the method of any of the above method embodiments.

It is to be understood that the processing means described above may be one or more chips. For example, the processing device may be a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), a system on chip (SoC), a Central Processing Unit (CPU), a Network Processor (NP), a digital signal processing circuit (DSP), a Microcontroller (MCU), a Programmable Logic Device (PLD), or other integrated chips.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a 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. To avoid repetition, it is not described in detail here.

It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip having signal processing capability. 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 described above may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, 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 (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (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.

According to the method provided by the embodiment of the present application, the present application further provides a computer program product, which includes: computer program code which, when run on a computer, causes the computer to perform the methods performed by the terminal device and the network device, respectively, in the embodiments shown in fig. 3, 6 and 11.

According to the method provided by the embodiment of the present application, the present application further provides a computer-readable medium, which stores program codes, and when the program codes are run on a computer, the computer is caused to execute the methods respectively executed by the terminal device and the network device in the embodiments shown in fig. 3, fig. 6 and fig. 11.

According to the method provided by the embodiment of the present application, the present application further provides a system, which includes the foregoing one or more terminal devices and one or more network devices.

The network device in the foregoing device embodiments completely corresponds to the terminal device and the network device or the terminal device in the method embodiments, and the corresponding module or unit executes the corresponding steps, for example, the communication unit (transceiver) executes the steps of receiving or transmitting in the method embodiments, and other steps besides transmitting and receiving may be executed by the processing unit (processor). The functions of the specific elements may be referred to in the respective method embodiments. The number of the processors may be one or more.

As used in this specification, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between 2 or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from two components interacting with another component in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).

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

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

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

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

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

In the above embodiments, the functions of the functional units may be fully or partially implemented by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). The procedures or functions described in accordance with the embodiments of the present application are generated in whole or in part when the computer program instructions (programs) are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

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 resource scheduling, comprising:

determining a first resource;

and sending a resource scheduling message of the first resource, wherein the resource scheduling message is used for indicating whether the service is transmitted in the SFN mode on the first resource.
The method of claim 1, wherein sending the resource scheduling message for the first resource comprises:

transmitting the resource scheduling message on a second resource;

wherein the resource scheduling message is used for indicating whether to transmit the service in the SFN mode on the first resource, and comprises:

if the second resource is an SFN resource, indicating that the service is transmitted in an SFN mode on the first resource, wherein the SFN resource is a resource for transmitting the service in the SFN mode;

if the second resource is a non-SFN resource, indicating that the service is transmitted in a non-SFN mode on the first resource.
The method of claim 1, wherein the resource scheduling message includes first indication information for indicating a transmission mode;

wherein the resource scheduling message is used for indicating whether to transmit the service in the SFN mode on the first resource, and comprises:

if the first indication information indicates that the sending mode is the SFN mode, the first indication information indicates that the service is transmitted in the SFN mode on the first resource;

if the first indication information indicates that the sending mode is a non-SFN mode, it indicates that the service is transmitted in the non-SFN mode on the first resource.
The method of claim 1, wherein the resource scheduling message is used to indicate whether traffic is transmitted in an SFN manner on the first resource, and wherein the method comprises:

if the resource scheduling message can be received with a first radio network temporary identity, RNTI, as a scrambling code, indicating that traffic is transmitted in SFN mode on the first resource,

if the resource scheduling message cannot be received with the first RNTI as a scrambling code, indicating that traffic is transmitted in a non-SFN mode on the first resource.
The method of claim 2, wherein the resource scheduling message is further configured to indicate a parameter K0 in case the second resource is an SFN resource, and wherein a value of the parameter K0 indicates a number of time domain resource units spaced between the first resource and the second resource, wherein the time domain resource units do not include resources unavailable for transmission of traffic in SFN mode.
The method of any of claims 1-5, wherein if the resource scheduling message indicates that the service is transmitted in SFN mode on the first resource, the resource scheduling message further comprises second indication information indicating reference signals associated with the service transmitted in SFN mode, and wherein the second indication information comprises one or more of: reference signal type, reference signal number, indication bit information.
The method of claim 6, further comprising:

sending first configuration information, wherein the first configuration information comprises: reference signal type, reference signal number, indication bit information.
The method of any of claims 1-5, wherein if the resource scheduling message indicates that the service is transmitted in SFN mode on the first resource, the resource scheduling message further comprises a first Temporary Mobile Group Identity (TMGI) indicating a reference signal and a second TMGI associated with the service transmitted in SFN mode, and wherein the first TMGI is associated with the second TMGI identifying an identifier of the service transmitted in SFN mode.
The method of claim 8, further comprising:

sending second configuration information, wherein the second configuration information comprises: the first TMGI, the second TMGI, a reference signal associated with a service transmitted in SFN mode.
A method for resource scheduling, comprising:

receiving a resource scheduling message, the resource scheduling message indicating a first resource;

and determining whether the service is transmitted in the SFN mode on the first resource according to the resource scheduling message.
The method of claim 10, wherein receiving the resource scheduling message for the first resource comprises:

receiving the resource scheduling message on a second resource;

wherein determining whether to transmit traffic in SFN mode on the first resource according to the resource scheduling message comprises:

if the second resource is an SFN resource, indicating that the service is transmitted in an SFN mode on the first resource, wherein the SFN resource is a resource for transmitting the service transmitted in the SFN mode;

and if the second resource is a non-SFN resource, indicating that the service is transmitted in a non-SFN mode on the first resource.
The method of claim 10, wherein the resource scheduling message includes first indication information indicating a transmission mode;

wherein determining whether to transmit traffic in SFN mode on the first resource according to the resource scheduling message comprises:

if the first indication information indicates that the sending mode is the SFN mode, the first indication information indicates that the service is transmitted in the SFN mode on the first resource;

if the first indication information indicates that the sending mode is a non-SFN mode, it indicates that the service is transmitted in the non-SFN mode on the first resource.
The method of claim 10, wherein the determining whether to transmit traffic in SFN mode on the first resource according to the resource scheduling message comprises:

if the resource scheduling message can be received with the first radio network temporary identity RNTI as a scrambling code, indicating that traffic is transmitted in SFN mode on the first resource,

and if the resource scheduling message can not be received by using the first RNTI as a scrambling code, indicating that the service is transmitted in a non-SFN mode on the first resource.
The method of claim 11, wherein a value of the parameter K0 indicates a number of time domain resource units spaced between the first resource and the second resource, and wherein the time domain resource units do not include resources unavailable for transmission of traffic in an SFN mode, further used for indicating a parameter K0 in the resource scheduling message in case the second resource is an SFN resource.
The method according to any of claims 10-14, wherein if the resource scheduling message indicates that the traffic is transmitted in SFN mode on the first resource, the resource scheduling message further comprises second indication information, the second indication information is used for indicating a reference signal associated with the traffic transmitted in SFN mode, and the second indication information comprises one or more of the following items: reference signal type, reference signal number, indication bit information.
The method of claim 15, further comprising:

receiving first configuration information, the first configuration information comprising: reference signal type, reference signal number, indication bit information.
The method of any of claims 10-14, wherein if the resource scheduling message indicates that traffic is transmitted in SFN mode on the first resource, the resource scheduling message further comprises a first temporary mobile group identification, TMGI, the first TMGI indicating a reference signal and a second TMGI associated with traffic transmitted in SFN mode, and the first TMGI being associated with the second TMGI, the second TMGI identifying an identifier of traffic transmitted in SFN mode.
The method of claim 17, further comprising:

receiving second configuration information, wherein the second configuration information comprises: the first TMGI, the second TMGI, a reference signal associated with a service transmitted in SFN mode.
A communication device is characterized by comprising a processing unit and a transmitting-receiving unit

The processing unit is configured to: determining a first resource;

the transceiver unit is configured to: and sending a resource scheduling message of the first resource, wherein the resource scheduling message is used for indicating whether the service is transmitted in the SFN mode on the first resource.
The communications apparatus according to claim 19, wherein the transceiver unit is specifically configured to:

transmitting the resource scheduling message on a second resource;

wherein the resource scheduling message is used for indicating whether to transmit the service in the SFN mode on the first resource, and comprises:

if the second resource is an SFN resource, indicating that the service is transmitted in an SFN mode on the first resource, wherein the SFN resource is a resource for transmitting the service in the SFN mode;

if the second resource is a non-SFN resource, indicating that the service is transmitted in a non-SFN mode on the first resource.
The communications apparatus according to claim 19, wherein the resource scheduling message includes first indication information indicating a transmission mode;

wherein the resource scheduling message is used for indicating whether to transmit the service in the SFN mode on the first resource, and comprises:

if the first indication information indicates that the sending mode is the SFN mode, the first indication information indicates that the service is transmitted in the SFN mode on the first resource;

if the first indication information indicates that the sending mode is a non-SFN mode, it indicates that the service is transmitted in the non-SFN mode on the first resource.
The communications apparatus of claim 19, wherein the resource scheduling message is configured to indicate whether traffic is transmitted on the first resource in an SFN manner, and wherein the resource scheduling message comprises:

if the resource scheduling message can be received with a first radio network temporary identity, RNTI, as a scrambling code, indicating that traffic is transmitted in SFN mode on the first resource,

if the resource scheduling message cannot be received with the first RNTI as a scrambling code, indicating that traffic is transmitted in a non-SFN mode on the first resource.
A communications apparatus as claimed in claim 20, wherein in the case that the second resource is an SFN resource, the resource scheduling message is further configured to indicate a parameter K0, a value of the parameter K0 indicates a number of time domain resource units spaced between the first resource and the second resource, wherein the time domain resource units do not include resources unavailable for transmitting traffic in SFN mode.
The communications apparatus as claimed in any of claims 19-23, wherein if the resource scheduling message indicates that traffic is transmitted in SFN mode on the first resource, the resource scheduling message further comprises second indication information indicating reference signals associated with the traffic transmitted in SFN mode, and the second indication information comprises one or more of: reference signal type, reference signal number, indication bit information.
The communications apparatus of claim 24, wherein the transceiver unit is further configured to:

sending first configuration information, wherein the first configuration information comprises: reference signal type, reference signal number, indication bit information.
The communications apparatus of any of claims 19-23, wherein if the resource scheduling message indicates that traffic is transmitted in SFN mode on the first resource, the resource scheduling message further comprises a first temporary mobile group identification, TMGI, the first TMGI indicating a reference signal and a second TMGI associated with traffic transmitted in SFN mode, and the first TMGI being associated with the second TMGI, the second TMGI identifying an identifier of traffic transmitted in SFN mode.
The communications apparatus of claim 26, wherein the transceiver unit is further configured to:

sending second configuration information, wherein the second configuration information comprises: the first TMGI, the second TMGI, a reference signal associated with a service transmitted in SFN mode.
A communication apparatus, comprising a transceiver unit and a processing unit:

the transceiver unit is configured to: receiving a resource scheduling message, the resource scheduling message indicating a first resource;

the processing unit is configured to: and determining whether the service is transmitted in the SFN mode on the first resource according to the resource scheduling message.
The communications device according to claim 28, wherein the transceiver unit is specifically configured to:

receiving the resource scheduling message on a second resource;

the processing unit is specifically configured to:

if the second resource is an SFN resource, indicating that the service is transmitted in an SFN mode on the first resource, wherein the SFN resource is a resource for transmitting the service in the SFN mode;

if the second resource is a non-SFN resource, indicating that the service is transmitted in a non-SFN mode on the first resource.
The communications apparatus as claimed in claim 28, wherein the resource scheduling message includes first indication information indicating a transmission mode;

the processing unit is specifically configured to:

if the first indication information indicates that the sending mode is the SFN mode, the first indication information indicates that the service is transmitted in the SFN mode on the first resource;

if the first indication information indicates that the sending mode is a non-SFN mode, it indicates that the service is transmitted in the non-SFN mode on the first resource.
The communications apparatus as claimed in claim 28, wherein the processing unit is specifically configured to:

if the resource scheduling message can be received with the first radio network temporary identity RNTI as a scrambling code, indicating that traffic is transmitted in SFN mode on the first resource,

and if the resource scheduling message can not be received by using the first RNTI as a scrambling code, indicating that the service is transmitted in a non-SFN mode on the first resource.
The communications apparatus of claim 29, wherein the resource scheduling message further indicates a parameter K0 in case the second resource is an SFN resource, and a value of the parameter K0 indicates a number of time domain resource units spaced between the first resource and the second resource, wherein the time domain resource units do not include resources unavailable for transmitting traffic in SFN mode.
The communications apparatus as claimed in any of claims 28-32, wherein if the resource scheduling message indicates that the traffic is transmitted in SFN mode on the first resource, the resource scheduling message further comprises second indication information indicating a reference signal associated with the traffic transmitted in SFN mode, and the second indication information comprises one or more of the following: reference signal type, reference signal number, indication bit information.
The communications apparatus of claim 33, wherein the transceiver unit is further configured to:

receiving first configuration information, the first configuration information comprising: reference signal type, reference signal number, indication bit information.
The communications apparatus of any of claims 28-32, wherein if the resource scheduling message indicates that traffic is transmitted in SFN mode on the first resource, the resource scheduling message further comprises a first temporary mobile group identification, TMGI, the first TMGI indicating a reference signal and a second TMGI associated with traffic transmitted in SFN mode, and the first TMGI being associated with the second TMGI, the second TMGI identifying an identifier of traffic transmitted in SFN mode.
The communications apparatus of claim 35, wherein the transceiver unit is further configured to:

receiving second configuration information, wherein the second configuration information comprises: the first TMGI, the second TMGI, a reference signal associated with a service transmitted in SFN mode.
A communications apparatus, comprising:

a processor to execute computer instructions stored in a memory to cause the apparatus to perform: the method of any one of claims 1-9.
A communications apparatus, comprising:

a processor to execute computer instructions stored in the memory to cause the apparatus to perform: the method of any one of claims 10-18.
A computer-readable storage medium, having stored thereon a computer program which, when executed, causes the method of any of claims 1-18 to be performed.