A method for resource scheduling and a communication device
Through dynamic scheduling and resource scheduling messages, network equipment flexibly configures SFN resources, solving the problem of inflexible resource allocation in the existing technology, achieving efficient resource utilization and service rate adaptability, and improving the synchronization and power consumption management of terminal equipment.
Patent Information
- Application Number
- CN201980102661.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-12-05
- Publication Date
- 2025-07-11
- Estimated Expiration
- 2039-12-05
AI Technical Summary
In the prior art, the resource allocation method in the single-frequency network mode is too semi-static and cannot flexibly respond to the dynamic changes in business needs, resulting in waste of resources and the inability to meet the needs of different business rates.
Using the dynamic scheduling method, the network device can determine any idle resource as a resource for the SFN mode transmission service, indicate whether the terminal device transmits the service in SFN or non-SFN mode through the resource scheduling message, and provides reference signals and TMGI information to ensure synchronization and save power consumption.
It realizes flexible scheduling of SFN resources, adapts to the dynamic changes in service transmission rates, avoids resource waste, and improves the synchronization capability and power consumption management of terminal equipment.
Smart Images

Figure CN114747285B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of wireless communications, and more particularly, to a method for resource scheduling and a communication device. Background Art
[0002] In the current process of transmitting services to terminal devices in the single frequency network (SFN) mode, in order to simplify the coordination process between network devices, the network devices configure time slot resources for transmitting services in the SFN mode to the terminal devices in a semi-static manner. Semi-static configuration means that services can only be transmitted in the SFN mode on SFN time slot resources, and services can only be transmitted in the non-SFN mode on non-SFN time slot resources. Therefore, when the demand for services transmitted in the SFN mode increases, it is impossible to use non-SFN time slot resources to transmit services in the SFN mode, or when the demand for services transmitted in the non-SFN mode increases, it is also impossible to use SFN time slot resources to transmit services in the non-SFN mode.
[0003] Therefore, the above semi-static configuration method of SFN time slot resources is not flexible enough. Summary of the Invention
[0004] This application provides a method for resource scheduling, aiming to achieve the purpose of flexibly scheduling SFN resources.
[0005] In a first aspect, a method for resource scheduling is provided. The method includes: determining a first resource; sending a resource scheduling message of the first resource, where the resource scheduling message is used to indicate whether to transmit services in the SFN mode on the first resource.
[0006] Based on the above technical solution, the network device can use a dynamic scheduling method to determine any idle resource as the first resource that can be used to transmit services in the SFN mode. Therefore, it can not only adapt to the dynamic changes in the SFN service transmission rate, flexibly schedule the SFN resources for transmitting services in the SFN mode, but also avoid resource waste.
[0007] In combination with the first aspect, in some implementation manners of the first aspect, sending the resource scheduling message of the first resource includes: sending the resource scheduling message on a second resource; where the resource scheduling message is used to indicate whether to transmit services in the SFN mode on the first resource, including: if the second resource is an SFN resource, it indicates that services are transmitted in the SFN mode on the first resource, and the SFN resource is a resource for transmitting services in the SFN mode; if the second resource is a non-SFN resource, it indicates that services are transmitted in the non-SFN mode on the first resource.
[0008] Based on the above technical solution, the terminal device can determine whether to transmit services in SFN mode or non-SFN mode on the first resource indicated by the resource scheduling message according to the second resource of the resource scheduling message.
[0009] In combination with the first aspect, in some implementation manners of the first aspect, the resource scheduling message includes first indication information for indicating a transmission mode; wherein, the resource scheduling message is used to indicate whether to transmit services in SFN mode on the first resource, including: if the first indication information indicates that the transmission mode is SFN mode, it indicates that services are transmitted in SFN mode on the first resource; if the first indication information indicates that the transmission mode is non-SFN mode, it indicates that services are transmitted in non-SFN mode on the first resource.
[0010] In combination with the first aspect, in some implementation manners of the first aspect, the resource scheduling message is used to indicate whether to transmit services in SFN mode on the first resource, including: if the resource scheduling message can be received with a first radio network temporary identity (RNTI) as a scrambling code, it indicates that services are transmitted in SFN mode on the first resource; if the resource scheduling message cannot be received with the first RNTI as a scrambling code, it indicates that services are transmitted in non-SFN mode on the first resource.
[0011] Optionally, the first RNTI may be an SFN-RNTI.
[0012] In combination with the first aspect, in some implementation manners of the first aspect, when the second resource is an SFN resource, the resource scheduling message is further used to indicate a parameter K0, and the value of the parameter K0 indicates the number of time-domain resource units separated between the first resource and the second resource, where the time-domain resource units do not include resources that are not available for transmitting services in SFN mode.
[0013] Based on the above solution, when the network device indicates the parameter K0, it does not count the resources that are not available for transmitting services in SFN mode, so that the air interface signaling when the network device indicates the parameter K0 can be saved.
[0014] In combination with the first aspect, in some implementation manners of the first aspect, if the resource scheduling message indicates that services are transmitted in SFN mode on the first resource, the resource scheduling message further includes second indication information, and the second indication information is used to indicate a reference signal associated with the services transmitted in SFN mode, and the second indication information includes one or more of the following: reference signal type, reference signal number, indication bit information.
[0015] 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. According to this second indication information, the terminal device can determine parameters such as the time-frequency synchronization signal and the receiving beam direction 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.
[0016] In combination with the first aspect, in some implementation manners of the first aspect, the method further includes: sending first configuration information, where the first configuration information includes: reference signal type, reference signal number, indication bit information.
[0017] In combination with the first aspect, in some implementation manners of the first aspect, if the resource scheduling message indicates that a service is transmitted in the SFN mode on the first resource, the resource scheduling message further includes a first temporary mobile group identity (TMGI), where the first TMGI is used to indicate a reference signal associated with the service transmitted in the SFN mode and a second TMGI, and the first TMGI is associated with the second TMGI, and the second TMGI is used to identify the identification number of the service transmitted in the SFN mode.
[0018] Based on the above technical solution, the resource scheduling message sent by the network device to the terminal device may further include the first TMGI. The terminal device can determine the parameters when receiving the service transmitted in the SFN mode according to the first TMGI, so as to effectively receive the same service data synchronously sent by different transmission nodes of the network device, and can also determine the second TMGI. Further, according to the second TMGI, the type of the service transmitted in the SFN mode can be determined. If the terminal device is not interested in the service transmitted in the SFN mode, it can not receive the service transmitted in the SFN mode, so as to achieve the purpose of power consumption saving.
[0019] In combination with the first aspect, in some implementation manners of the first aspect, the method further includes: sending second configuration information, where the second configuration information includes: the first TMGI, the second TMGI, and a reference signal associated with the service transmitted in the SFN mode.
[0020] In a second aspect, a method for resource scheduling is provided, characterized in that the method includes: receiving a resource scheduling message, where the resource scheduling message indicates a first resource; determining whether a service is transmitted in the SFN mode on the first resource according to the resource scheduling message.
[0021] Based on the above technical solution, the network device can adopt a dynamic scheduling method to determine any idle resource as the first resource that can be used to transmit services in the SFN mode. Therefore, it can not only adapt to the dynamic changes in the transmission rate of SFN services, flexibly schedule the SFN resources for transmitting services in the SFN mode, but also avoid resource waste.
[0022] Combined with the second aspect, in some implementation manners of the second aspect, receiving the resource scheduling message of the first resource includes: receiving the resource scheduling message on the second resource; wherein, according to the resource scheduling message, determining whether to transmit services in the SFN mode on the first resource includes: if the second resource is an SFN resource, it indicates that services are transmitted in the SFN mode on the first resource, and the SFN resource is a resource for transmitting services in the SFN mode; if the second resource is a non-SFN resource, it indicates that services are transmitted in a non-SFN mode on the first resource.
[0023] Based on the above technical solution, the terminal device can determine whether to transmit services in the SFN mode or in a non-SFN mode on the first resource indicated by the resource scheduling message according to the second resource of the message for transmitting resource scheduling.
[0024] Combined with the second aspect, in some implementation manners of the second aspect, the resource scheduling message includes first indication information for indicating the transmission mode; wherein, according to the resource scheduling message, determining whether to transmit services in the SFN mode on the first resource includes: if the first indication information indicates that the transmission mode is the SFN mode, it indicates that services 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, it indicates that services are transmitted in a non-SFN mode on the first resource.
[0025] Combined with the second aspect, in some implementation manners of the second aspect, according to the resource scheduling message, determining whether to transmit services in the SFN mode on the first resource includes: if the resource scheduling message can be received with the first radio network temporary identity (RNTI) as the scrambling code, it indicates that services are transmitted in the SFN mode on the first resource; if the resource scheduling message cannot be received with the first RNTI as the scrambling code, it indicates that services are transmitted in a non-SFN mode on the first resource.
[0026] Optionally, the first RNTI may be an SFN-RNTI.
[0027] Combined with the second aspect, in some implementation manners of the second aspect, when the second resource is an SFN resource, the resource scheduling message is further used to indicate a parameter K0, and the value of the parameter K0 indicates the number of time-domain resource units separated between the first resource and the second resource, where the time-domain resource units do not include resources that are not available for transmitting services in the SFN mode.
[0028] Based on the above solution, when the network device indicates the parameter K0, it will not include the resources that are not available for transmitting services in the SFN mode. Therefore, the air interface signaling when the network device indicates the parameter K0 can be saved.
[0029] Combined with the second aspect, in some implementation manners of the second aspect, if the resource scheduling message indicates to transmit services 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 services 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.
[0030] 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 services transmitted in the SFN mode. According to the second indication information, the terminal device can determine parameters such as the time-frequency synchronization signal and the reception beam direction when receiving the services transmitted in the SFN mode, so that the terminal device can effectively receive the same service data synchronously sent by different transmission nodes of the network device.
[0031] Combined with the second aspect, in some implementation manners of the second aspect, the method further includes: receiving first configuration information, where the first configuration information includes: reference signal type, reference signal number, indication bit information.
[0032] Combined with the second aspect, in some implementation manners of the second aspect, if the resource scheduling message indicates to transmit services in the SFN mode on the first resource, the resource scheduling message further includes a first temporary mobility group identifier (TMGI), where the first TMGI is used to indicate a reference signal associated with the services transmitted in the SFN mode and a second TMGI, and the first TMGI is associated with the second TMGI, and the second TMGI is used to identify the identification number of the services transmitted in the SFN mode.
[0033] 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. The terminal device can determine the parameters when receiving the services transmitted in the SFN mode according to the first TMGI, so that the terminal device can effectively receive the same service data synchronously sent by different transmission nodes of the network device. The terminal device can also determine the second TMGI, and further determine the service type transmitted in the SFN mode according to the second TMGI. If the terminal device is not interested in the services transmitted in the SFN mode, the terminal device may not receive the services transmitted in the SFN mode, thereby achieving the purpose of saving power consumption.
[0034] In combination with the second aspect, in some implementations of the second aspect, the method further includes: receiving second configuration information, where the second configuration information includes: the first TMGI, the second TMGI, and a reference signal associated with the service transmitted in SFN mode.
[0035] It should be understood that the first aspect described above can be combined with the method provided in the second aspect.
[0036] In a third aspect, a communication device is provided, including various modules or units for performing the method in the first aspect and any possible implementation manner in the first aspect.
[0037] In a fourth aspect, a communication device is provided, including various modules or units for performing the method in the second aspect and any possible implementation manner in the second aspect.
[0038] In a fifth aspect, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in the first aspect and any possible implementation manner in the first aspect. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.
[0039] In one implementation, the communication device is a network device. When the communication device is a network device, the communication interface can be a transceiver, or an input / output interface.
[0040] In another implementation, the communication device is a chip configured in a network device. When the communication device is a chip configured in a network device, the communication interface can be an input / output interface.
[0041] Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.
[0042] In a sixth aspect, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in the second aspect and any possible implementation manner in the second aspect. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.
[0043] In one implementation, the communication device is a terminal device. When the communication device is a terminal device, the communication interface can be a transceiver, or an input / output interface.
[0044] In another implementation, the communication device is a chip configured in a terminal device. When the communication device is a chip configured in a terminal device, the communication interface may be an input / output interface.
[0045] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.
[0046] In a seventh aspect, a processor is provided, including: an input circuit, an output circuit, and a 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 executes the methods in the first aspect to the second aspect and any possible implementation manners in the first aspect to the second aspect.
[0047] In a specific implementation process, the above-mentioned 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 transistors, gate circuits, flip-flops, and various logic circuits, etc. The input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver. The signal output by the output circuit may be output to, for example, but not limited to, a transmitter and transmitted by the transmitter. Moreover, the input circuit and the output circuit may be the same circuit, which serves as the input circuit and the output circuit at different times respectively. The embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.
[0048] In an eighth aspect, a processing device is provided, including a processor and a memory. The processor is configured to read instructions stored in the memory, and may receive a signal through a receiver and transmit a signal through a transmitter to execute the methods in the first aspect to the second aspect and any possible implementation manners in the first aspect to the second aspect.
[0049] Optionally, there may be one or more processors and one or more memories.
[0050] Optionally, the memory may be integrated with the processor, or the memory and the processor are separately arranged.
[0051] In a specific implementation process, the memory may be a non-transitory memory, such as a read only memory (ROM), which may be integrated with the processor on the same chip or separately arranged on different chips. The embodiments of the present application do not limit the type of the memory and the arrangement manner of the memory and the processor.
[0052] It should be understood that in relevant data interaction processes, for example, sending indication information can be a process of outputting indication information from the processor, and receiving capability information can be a process of the processor receiving input capability information. Specifically, the data output by the processor can be output to the transmitter, and the input data received by the processor can come from the receiver. Among them, the transmitter and the receiver can be collectively referred to as the transceiver.
[0053] The processing device in the above eighth aspect can be one or more chips. The processor in this processing device can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. The memory can be integrated in the processor or can be located outside the processor and exist independently.
[0054] In a ninth aspect, there is provided a computer program product, which includes: a computer program (which can also be referred to as code or instruction). When the computer program is run, it causes the methods in the above first aspect to the second aspect and any possible implementation manner in the first aspect to the second aspect to be executed.
[0055] In a tenth aspect, there is provided a computer-readable storage medium, which stores a computer program (which can also be referred to as code or instruction). When it runs on a computer, it causes the computer to execute the methods in the above first aspect to the second aspect and any possible implementation manner in the first aspect to the second aspect.
[0056] In an eleventh aspect, there is provided a communication system, including: the aforementioned network device, and / or, a terminal device. Description of the Drawings
[0057] Figure 1 is a schematic diagram of a communication system of the method provided by an embodiment of the present application.
[0058] Figure 2 is a schematic diagram of extended CP and normal CP provided by an embodiment of the present application.
[0059] Figure 3 is a schematic flowchart of the method for resource scheduling provided by an embodiment of the present application.
[0060] Figure 4 is a schematic diagram of a communication system of the method provided by an embodiment of the present application.
[0061] Figure 5 is a schematic diagram of the method for using associated reference signals provided by an embodiment of the present application.
[0062] Figure 6It is a schematic flowchart of the resource scheduling method provided by the embodiments of the present application.
[0063] Figure 7 It is a schematic diagram of the resource scheduling method provided by the embodiments of the present application.
[0064] Figure 8 It is a schematic diagram of the resource scheduling method provided by the embodiments of the present application.
[0065] Figure 9 It is a schematic diagram of the resource scheduling method provided by the embodiments of the present application.
[0066] Figure 10 It is a schematic diagram of the resource scheduling method provided by the embodiments of the present application.
[0067] Figure 11 It is a schematic flowchart of the resource scheduling method provided by the embodiments of the present application.
[0068] Figure 12 It is a schematic diagram of the resource scheduling method provided by the embodiments of the present application.
[0069] Figure 13 It is a schematic diagram of the resource scheduling method provided by the embodiments of the present application.
[0070] Figure 14 It is a schematic diagram of the resource scheduling method provided by the embodiments of the present application.
[0071] Figure 15 It is a schematic diagram of the resource scheduling method provided by the embodiments of the present application.
[0072] Figure 16 It is a schematic block diagram of the communication device provided by the embodiments of the present application.
[0073] Figure 17 It is a schematic structural diagram of the terminal device provided by the embodiments of the present application.
[0074] Figure 18 It is a schematic structural diagram of the network device provided by the embodiments of the present application. Detailed implementation manners
[0075] Next, the technical solutions in the present application will be described in conjunction with the accompanying drawings.
[0076] The technical solution of the embodiment of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5th generation (5G) mobile communication system or New Radio Access Technology (NR) or next-generation communication, such as 6G. Among them, the 5G mobile communication system can be non-standalone (NSA) or standalone (SA).
[0077] The technical solution provided by the present application can also be applied to Machine Type Communication (MTC), Long Term Evolution - machine (LTE-M), Device to Device (D2D) network, Machine to Machine (M2M) network, Internet of Things (IoT) network or other networks. Among them, the IoT network can include, for example, the vehicle-to-everything (V2X) network. Among them, the communication methods in the V2X system are collectively referred to as vehicle to X (V2X, where X can represent anything), for example, the V2X can include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, communication between vehicle and pedestrian (V2P) or vehicle to network (V2N) communication, etc.
[0078] The technical solution provided by the present application can also be applied to future communication systems, such as the sixth-generation mobile communication system, etc. The present application does not limit this.
[0079] In the embodiments of the present application, the network device may be any device with wireless transceiver functions. The device includes but is 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 (for example, home evolved Node B, or home Node B, HNB), baseband unit (BBU), access point (AP) in a wireless fidelity (WiFi) system, wireless relay node, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP), etc. It may also be a gNB in a 5G system such as NR, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or it may also be a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), or a base station in a next-generation communication 6G system, etc.
[0080] In some deployments, the gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC), media access control (MAC), and physical (PHY) layers. The AAU implements some physical layer processing functions, radio frequency processing, and related functions of active antennas. Since the information of the RRC layer will ultimately become the information of the PHY layer, or is transformed from the information of the PHY layer, therefore, in this architecture, high-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or sent by the DU and the AAU. It can be understood that the network device may be a device including one or more of the CU node, DU node, and AAU node. In addition, the CU may be classified as a network device in the radio access network (RAN), or the CU may be classified as a network device in the core network (CN). The embodiments of this application do not make any limitations in this regard.
[0081] In the embodiments of the present application, the terminal device may also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile phone, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The terminal device in the embodiments of the present application may be a mobile phone, a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device, or other processing devices connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, a terminal device in a future evolved public land mobile network (PLMN), or a terminal device in a non-public network, etc.
[0082] Among them, the wearable device may also be referred to as a wearable intelligent device, which is a general term for devices developed by applying wearable technology to intelligent design of daily wear, such as glasses, gloves, watches, clothing, and shoes. The wearable device is a portable device that can be directly worn on the body or integrated into the user's clothes or accessories. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable intelligent devices include those with complete functions and large sizes that can realize complete or partial functions without relying on a smart phone, such as smart watches or smart glasses, etc., and those that only focus on a certain type of application function and need to cooperate with other devices such as smart phones, such as various smart bracelets and smart jewelry for physical sign monitoring.
[0083] In addition, the terminal device can also be a terminal device in an Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-object interconnection.
[0084] This application does not limit the specific form of the terminal device.
[0085] To facilitate the understanding of the embodiments of this application, first, in combination with Figure 1 A communication system applicable to the embodiments of this application will be described in detail. Figure 1 FIG. is a schematic diagram of a communication system applicable to the method provided in the embodiments of this application.
[0086] As Figure 1 shown, the communication system 100 may include multiple network devices, such as Figure 1 the network device 110 and the network device 120 shown. The communication system 100 may include at least one terminal device, such as Figure 1 the terminal device 130 shown. The network device may send data to the terminal device in the SFN mode. The so-called SFN mode means that multiple adjacent network devices or sending nodes send the same data to the terminal device. Correspondingly, the terminal device may receive the same data from multiple network devices or sending nodes in the SFN manner. For example Figure 1 in, the network device 110 and the network device 120 form an SFN transmission group, covering a certain area. The network device 110 and the network device 120 may send the same data in the SFN mode on specific time and frequency domain resources. Correspondingly, the terminal device 130 may receive the same data from the network device 110 and the network device 120 in the SFN manner.
[0087] It should be understood that only for illustration, two network devices and two terminal devices are shown in the figure, but this should not impose any limitation on this application. In this communication system, more terminal devices and more network devices may also be included.
[0088] Since the SFN mode is that multiple network devices send the same data, therefore, in the process of sending data in the SFN mode, a device similar to a central control unit is required to coordinate the sending time and sending content of each network device. The function of this central control unit device may be executed by a certain network device, or may also be executed by a separate device.
[0089] In the fourth-generation (4G) mobile communication system, in order to simplify the coordination between network devices, the network devices configure the time slot resources for transmitting broadcast and multicast data in the SFN mode in a semi-static manner, and send this semi-static configuration information to the terminal device. There are two main reasons why the terminal device needs the configuration information of the SFN time slot resources:
[0090] (1) If the network device transmits channel data or signals in the SFN mode, the time slot format of the channel data or signals is an extended cyclic prefix (CP). If the network device transmits channel data or signals in a non-SFN manner, the time slot format of the channel data or signals is a normal CP. On the terminal device side, the received symbols of the extended CP and the normal CP need to be converted in timing. Figure 2 An example of the normal CP and the extended CP is shown. As Figure 2 shown, if the network device transmits data in the extended CP time slot n + 6, the time slot format of the data is the extended CP. If the network device transmits data in the normal CP time slot n + 2, the time slot format of the data is the normal CP.
[0091] (2) When the network device transmits channel data or signals in the SFN mode, since the channel data or signals come from multiple network devices, the terminal device needs to know the time and / or frequency synchronization signals between different network devices, and this time and / or frequency synchronization signal is sent from the network device to the terminal device. If the network device transmits channel data or signals in a non-SFN mode, the terminal device receives multicast and broadcast data from only one network device, so 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 needs to switch to the time and / or frequency synchronization signal in the SFN mode for time / frequency synchronization; if the terminal device receives data in a non-SFN mode, it needs to perform time and / or frequency synchronization on the time and / or frequency synchronization signal of the local cell.
[0092] However, configuring the SFN resources in a semi-static manner means that only when the SFN resources are configured can services be transmitted in the SFN mode on the SFN resources, and on the SFN resources, services can only be transmitted in the SFN mode. When the communication speed of services transmitted in the non-SFN mode increases, the idle SFN resources cannot be used. When the demand for services transmitted in the SFN mode becomes large, the idle ordinary resources cannot be used either. Therefore, configuring the SFN resources in a semi-static manner will result in poor resource flexibility and it is difficult to meet the requirements of different services for rate changes.
[0093] In view of this, the present application aims to provide a resource scheduling method to achieve the purpose of flexibly configuring SFN resources.
[0094] The method provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.
[0095] To facilitate the understanding of the embodiments of the present application, the following explanations are made before introducing the embodiments of the present application.
[0096] First, in the embodiments of the present application, "for indicating" may include direct indication and indirect indication, and may also include explicit indication and implicit indication. The information indicated by a certain piece of information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated. For example, but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated. It is also possible to indirectly indicate the information to be indicated by indicating other information, where there is an association relationship between the other information and the information to be indicated. It is also possible to only indicate a part of the information to be indicated, while the other parts of the information to be indicated are known or pre-agreed. For example, it is also possible to indicate the information to be indicated by relying on a pre-agreement (such as protocol regulations) on the existence of a certain cell, so as to reduce the indication overhead to a certain extent.
[0097] Second, in the embodiments shown below, the first, second, and various numerical numbers are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. For example, to distinguish different indication information, etc.
[0098] Third, the "protocol" involved in the embodiments of the present application may refer to standard protocols in the communication field. For example, it may include LTE protocols, NR protocols, and related protocols applied to future communication systems. The present application does not make any limitations in this regard.
[0099] Fourth, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects and indicates that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects before and after. "At least one (item)" or similar expressions below refer to any combination of these items, including any combination of single items (items) or plural items (items). For example, at least one (item) of a, b, and c can represent: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Where a, b, and c can be single or multiple respectively.
[0100] Fifth, in the embodiments of the present application, descriptions such as "when...", "in the case of...", "if", and "when" all refer to the situation where the device (such as a terminal device or a network device) will perform corresponding processing under certain objective circumstances, rather than limiting the time, and it is not required that the device (such as a terminal device or a network device) must have a judgment action when implemented, nor does it mean there are other limitations.
[0101] Sixth, multiple embodiments are described in detail below in combination with multiple flowcharts. However, it should be understood that the relevant descriptions of these flowcharts and their corresponding embodiments are only examples for easy understanding and should not constitute any limitation to the present application. Each step in each flowchart is not necessarily required to be executed. For example, some steps can be skipped. Moreover, the execution order of each step is not fixed and unchangeable, nor is it limited to that shown in the figures. The execution order of each step should be determined according to its function and internal logic. The embodiments shown below take the interaction between a network device and a terminal device as an example to illustrate the method provided by the embodiments of the present application. However, this should not constitute any limitation to the present application. For example, the terminal device shown in the embodiments below can be replaced by components configured in the terminal device (such as a chip, a chip system, or a circuit, etc.). The network device shown in the embodiments below can also be replaced by components configured in the network device (such as a chip, a chip system, or a circuit, etc.).
[0102] The embodiments shown below do not particularly limit the specific structure of the execution entity of the method provided by the embodiments of the present application. As long as it can communicate according to the method provided by the embodiments of the present application by running a program recording the code of the method provided by the embodiments of the present application. For example, the execution entity of the method provided by the embodiments of the present application can be a terminal device or a network device, or a functional module in the terminal device or the network device that can call and execute the program.
[0103] It should be noted that the SFN service described in the embodiments of the present application refers to a service sent in the SFN manner. Among them, the service can be service data or control data. The non-SFN service described in the embodiments of the present application refers to a service sent in a non-SFN mode. The non-SFN mode can be, for example, a single-cell point-to-multipoint (SC-PTM) mode.
[0104] Figure 3 The schematic flowchart of the resource scheduling method provided by the embodiments of the present application is shown. Figure 3 The method 300 shown can be performed by Figure 1 the network device 110 or the network device 120 shown and the terminal device 130. As Figure 3As shown, the method 300 includes S310 and S320, and each step is described below.
[0105] S310, the network device determines a first resource.
[0106] The network device can transmit services in SFN mode on the first resource, or can transmit services in non - SFN mode on the first resource.
[0107] The embodiments of the present application do not specifically limit how the network device determines the first resource.
[0108] In one implementation, the network device can determine any idle resource as the first resource.
[0109] Before the network device determines any idle resource as the first resource, the network device may not configure SFN resources for the terminal device.
[0110] For example, the network device has not configured SFN resources for the terminal device before. In this case, if the network device needs to transmit SFN services, it uses a dynamic scheduling method to indicate to the terminal device the resources for transmitting SFN services.
[0111] In another implementation, the network device can determine the non - SFN resources and SFN resources previously configured for the terminal device as the first resource, that is, the network device can determine the resources available for transmitting SFN services as the first resource. Among them, the non - SFN resources are ordinary resources, or are candidate resources.
[0112] As an example, the non - SFN resources are ordinary resources, that is, the network device can determine the ordinary resources and SFN resources previously configured for the terminal device as the first resource. Among them, the SFN resources can be used to transmit SFN services, and the ordinary resources can be used to transmit either non - SFN services or SFN services. In this case, the network device can send the configuration information #1 of the SFN resources to the terminal device before sending the resource scheduling message indicating the first resource. The content and method of the network device sending the configuration information #1 will be described in detail in combination with other embodiments later, and will not be elaborated here for the time being.
[0113] As another example, the non - SFN resources are candidate resources, that is, the network device can determine the SFN resources and candidate SFN resources as the first resource. Among them, the SFN resources are used to transmit SFN service data, and the candidate resources can be used to transmit SFN data or non - SFN service data. In this case, the network device can send the configuration information #2 of the SFN resources to the terminal device before sending the resource scheduling message indicating the first resource. The content and method of the network device sending the configuration information #2 will be described in detail in combination with other embodiments later, and will not be elaborated here for the time being.
[0114] S320, the network device sends a resource scheduling message of a first resource to the terminal device.
[0115] Wherein, the resource scheduling message is used to indicate whether to transmit services in the SFN mode on the first resource, that is, services can be transmitted in the SFN mode on the first resource, or can be transmitted in a non-SFN mode.
[0116] Correspondingly, the terminal device receives the resource scheduling message. Further, the terminal device determines whether to transmit services in the SFN mode on the first resource according to the resource scheduling message.
[0117] The embodiments of the present application do not limit the manner in which the terminal device determines whether to transmit services in the SFN mode on the first resource.
[0118] In one implementation manner, the resource scheduling message may include first indication information for indicating a transmission mode. The terminal device can determine whether to transmit services in the SFN mode on the first resource according to the first indication information. If the first indication information indicates that the transmission mode is the SFN mode, the terminal device determines to transmit data 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 services in the non-SFN mode on the first resource.
[0119] For example, a cell for indicating a service transmission mode may be added to the downlink control information (DCI) sent by the network device to the terminal device. The service transmission modes may include: SFN mode, SC-PTM mode. The added cell may include: modulation and coding scheme indication, which is used to indicate the modulation and coding format of the service; service transmission mode indication, and its value may be a Boolean variable. For example, a value of 1 indicates the SC-PTM mode, and a value of 0 indicates the SFN mode.
[0120] In another implementation manner, the network device may configure a first RNTI for the terminal device to receive the resource scheduling message before sending the resource scheduling message. If the terminal device successfully receives the resource scheduling message sent by the network device by using the first RNTI as a scrambling code, the terminal device can determine to transmit services in the SFN mode on the first resource; if the terminal device does not receive the resource scheduling message sent by the network device by using the first RNTI as a scrambling code, the terminal device can determine to transmit services in the non-SFN mode on the first resource.
[0121] Optionally, the first RNTI may be an SFN-RNTI.
[0122] The network device may also configure a second RNTI for the terminal device to receive the resource scheduling message before sending the resource scheduling message. If the terminal device successfully receives the resource scheduling message sent by the network device using the second RNTI as a scrambling code, the terminal device may determine to transmit services in a non-SFN mode on the first resource; if the terminal device does not receive the resource scheduling message sent by the network device using the second RNTI as a scrambling code, the terminal device may determine to transmit services in an SFN mode on the first resource.
[0123] In another implementation, the terminal device determines whether to transmit services in an SFN mode on the first resource according to a second resource for transmitting the resource scheduling message. If the second resource is an SFN resource, the terminal device may determine to transmit services in an SFN mode on the first resource. If the second resource is a non-SFN resource, the terminal device may determine to transmit services in a non-SFN mode on the first resource.
[0124] In the embodiments of the present application, the network device may use a dynamic scheduling method to determine any idle resource as the first resource that can be used to transmit SFN services. Therefore, it can not only adapt to the dynamic change of the SFN service transmission rate, flexibly schedule the SFN resources for transmitting SFN services, but also avoid resource waste.
[0125] Alternatively, the network device may also determine the previously configured SFN resources and ordinary resources for the terminal device as the first resource. Further, the network device may transmit services in an SFN mode on the idle ordinary resources, so as to adapt to the increase in the demand for SFN services and avoid resource waste.
[0126] Or, the network device may also determine the previously configured SFN resources and candidate resources for the terminal device as the first resource. Further, the network device may transmit services in an SFN mode on the candidate resources, or transmit services in a non-SFN mode on the candidate resources. Therefore, it can not only adapt to the increase in the demand for SFN service data, but also adapt to the increase in the demand for non-SFN service data, and avoid resource waste.
[0127] If the resource scheduling message sent by the network device to the terminal device indicates to transmit services in an SFN mode on the first resource, the resource scheduling message further includes indication information for indicating a reference signal associated with the SFN service data.
[0128] In one implementation, the resource scheduling message further includes second indication information, which is used to indicate a reference signal (RS) associated with the SFN service transmitted on the first resource. The second indication information includes one or more of the following: reference signal type, reference signal number, indication bit information.
[0129] The embodiments of the present application do not limit the type of the reference signal. For example, the associated reference signal may be one or more of the following: quasi co-location (QCL), channel state information reference signal (CSI-RS), synchronization signal block (SSB), time reference signal (TRS), beam reception direction.
[0130] The association relationship between the associated reference signal and the SFN service is used to determine the parameters for the terminal device to receive the SFN service.
[0131] For example, the association relationship between the beam reception direction and the SFN service is used to determine the parameter configuration of the receiving antenna when the terminal device receives the SFN service.
[0132] For another example, the association relationship between the TRS and the SFN service is used to determine the time domain and / or frequency synchronization settings when the terminal device receives the SFN service.
[0133] As Figure 4 shown, 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. Network device 410 and network device 420 first send a resource scheduling message to terminal device 450. The resource scheduling message is used to indicate the resources for transmitting data #1, and the resource scheduling message includes TRS #1. Correspondingly, terminal device 450 determines the time timing and frequency timing for network device 410 and network device 420 to send data #1 through TRS #1. Similarly, network device 430 and network device 440 first send a resource scheduling message to terminal device 450. The resource scheduling message is used to indicate the resources for transmitting data #2, and the resource scheduling message includes TRS #2. Correspondingly, terminal device 450 determines the time timing and frequency timing for network device 430 and network device 440 to send data #2 through TRS #2.
[0134] As Figure 5As shown, there is a timing error between the time timing and frequency timing determined by the terminal device according to TRS#1 and the time timing and frequency timing determined by the terminal device according to TRS#2. If the terminal device receives Data#2 according to the time timing and frequency timing determined by TRS#1, a reception error will occur. Similarly, if the terminal device receives Data#1 according to the time timing and frequency timing determined by TRS#2, a reception error will also occur.
[0135] This second indication information may only include indication bit information. Since there is a one-to-one correspondence between the indication bit information and different associated reference signals, the terminal device can determine the specific associated reference signal according to the indication bit information. If, in the configuration information of the associated reference signal previously sent by the network device to the terminal device, there is a one-to-one correspondence between different associated reference signals and the associated reference signal numbers, then this second indication information may only include the associated reference signal numbers. If, in the configuration information of the associated reference signal previously sent by the network device to the terminal device, there is only one type of associated reference signal, then the second indication information may only include the type of associated reference signal. If, in the configuration information of the associated reference signal previously sent by the network device to the terminal device, different types of associated reference signals correspond to the same associated reference signal number, then the second indication information may include the type of associated reference signal and the associated reference signal number. It can be understood that when the second indication information includes indication bit information, the second indication information may also include the type of associated reference signal and / or the associated reference signal number.
[0136] It can be understood that before the network device sends a resource scheduling message to the terminal device, the network device may also send first configuration information to the terminal device, and the first configuration information includes: the type of reference signal, the reference signal number, and the indication bit information.
[0137] The network device may send the first configuration information to the terminal device by using high-layer 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; or, the network device may send the first configuration information to the terminal device through a media access control (MAC) control element (CE). The embodiments of the present application do not make any limitations in this regard.
[0138] The embodiments of the present application are described by taking as an example that in the first configuration information previously sent by the network device to the terminal device, there is a one-to-one correspondence between different associated reference signals and the reference signal numbers. Table 1 is a schematic diagram of the configuration information in which the type of reference signal and the reference signal number are in one-to-one correspondence.
[0139] Indicator bit information Associated reference signal type Associated reference signal number 11 TRS#1 XXXX 01 TRS#2 YYYY 10 CSI-RS#1 ZZZZ 11 CSI-RS#2 KKKK
[0140] As shown in the above table, if the first indication information is 00, the terminal device can determine that the SFN service transmitted this time is associated with TRS#1 numbered XXXX; or, if the associated reference signal indication is XXXX, the terminal device can also consider that the SFN service transmitted this time is associated with TRS#1.
[0141] In another implementation, the resource scheduling message may further include a first TMGI, where the first TMGI is used to indicate a reference signal associated with the SFN service and a second TMGI, the first TMGI is associated with the second TMGI, and the second TMGI is used to identify the SFN service.
[0142] It can 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, and the second configuration information includes: a first TMGI, a second TMGI, and a reference signal associated with the SFN service.
[0143] The network device may send the second configuration information to the terminal device by using a high-layer signaling method. 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; or, the network device may send the second configuration information to the terminal device through a MAC CE. The embodiments of the present application do not make any limitations in this regard.
[0144] It should 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 (that is, it means that multiple different SFN services have different network sending nodes), then one first TMGI corresponds to one second TMGI; if multiple different SFN services are associated with the same reference signal (that is, it means that multiple different SFN services have the same multiple network sending nodes), then multiple second TMGIs corresponding to the multiple SFN services may correspond to one first TMGI.
[0145] Further, after the terminal device receives the first TMGI in the resource scheduling message, it can confirm the number of the SFN service transmitted on the first resource indicated by the resource scheduling message according to the second TMGI associated with the first TMGI, and can confirm the reference signal associated with the SFN service.
[0146] As described above, before the network device sends a resource scheduling message to the terminal device, the network device may send the configuration information of the SFN resource #2 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 the parameter K0, and the value of the parameter K0 is used to indicate the number of time-domain resource units between the first resource and the second resource for transmitting the resource scheduling message, where the time-domain resource unit does not include the resources that are not available for transmitting SFN services.
[0147] It can be understood that if the resource scheduling message indicates that the service is transmitted in a non-SFN mode on the first resource, the resource scheduling message may also include the indication information for indicating the reference signal associated with the non-SFN service. Before the network device sends the resource scheduling message, the network device may also send the configuration information of the reference signal associated with the non-SFN service to the terminal device.
[0148] For example, when the network device configures the downlink shared channel (PDSCH) for the terminal device to transmit the service, it may configure the reference signal associated with the service. The configuration information sent by the network device may be, for example:
[0149] broadcastmulitcast-PDSCH configuration
[0150] {
[0151] SFN mode
[0152] {
[0153] associated RS1 {reference signal type, reference signal identity (ID)}
[0154] associated RS2 {reference signal type, reference signal ID}
[0155] CP type {extended CP, normal CP}, / / when configuring, select one
[0156] }
[0157] SC-PTM mode
[0158] {
[0159] associated RS1 {reference signal type, reference signal ID}
[0160] associated RS2 {reference signal type, reference signal ID}
[0161] }
[0162] }
[0163] Among them, the SFN mode means that two or more network sending nodes synchronously send the same service data; correspondingly, the terminal device receives the service data sent by different sending nodes through different transmission paths. The SC-PMT mode means that a single cell (which can also be understood as a single node) transmits service data in a broadcast or multicast manner.
[0164] In the embodiment of the present application, 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. According to this second indication information, the terminal device can determine parameters such as the time-frequency synchronization signal and the receiving beam direction when receiving the SFN service, so as to effectively receive the same SFN service synchronously sent by different transmission nodes of the network device.
[0165] Alternatively, the resource scheduling message sent by the network device to the terminal device may further include a first TMGI. The terminal device can determine the parameters when receiving the SFN service according to this first TMGI, so as to effectively receive the same service data synchronously sent by different transmission nodes of the network device, and can also determine a second TMGI. Further, according to the second TMGI, the SFN service type can be determined. If the terminal device is not interested in this SFN service, it can not receive this SFN service, so as to achieve the purpose of power consumption saving.
[0166] Figure 6 It shows a schematic flowchart of the resource scheduling method provided by the embodiment of the present application. Figure 6 The method 600 shown makes a more detailed description of the example where the non-SFN resource mentioned in step S310 is a common resource.
[0167] Such as Figure 6 As shown, the method 600 includes S610 - S630, and each step is described in detail below.
[0168] S610, the network device sends configuration information #1 to the terminal device.
[0169] Among them, the configuration information #1 may include the configuration information and indication information #1 of the SFN resource and the common resource.
[0170] The configuration information of the SFN resource and the general resource may include: the allocation period 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 general time slot in the radio frame containing the SFN time slot. Among them, the SFN time slot is the time slot where the SFN resource is located, and the general time slot is the time slot where the general resource is located. The indication information #1 is used to indicate that if the resource for transmitting SFN service data indicated by the resource scheduling message sent by the network device is a general resource, then the general resource is converted into an SFN resource.
[0171] The network device may send the configuration information #1 to the terminal device by using high-layer signaling. For example, the network device may send the configuration information of the SFN resource to the terminal device by establishing an RRC radio connection with the terminal device; or, the network device may send the configuration information of the SFN resource to the terminal device through MAC CE. The embodiments of this application do not make any limitations in this regard.
[0172] The configuration information of the SFN resource sent by the network device to the terminal device may include the following information: (1) radioframeAllociationPeriod: indicating the allocation period of the radio frame containing the SFN time slot, and its period may be 1, 2, 4, 8, 16, 32, or other values; (2) radioframeAllociationOffset: indicating the allocation offset of the radio frame containing the SFN time slot, and its value may be 0, 1, 2, 3, 4, 5, 6, 7, or other values; (3) candidateSFN: indicating whether a certain time slot in the radio frame containing the SFN time slot is an SFN time slot or a general time slot, and its value may be of bool type. For example, a value of 1 indicates an SFN time slot, and a value of 0 indicates a general time slot; (4) SFNslotOneFrame: the allocation information of the SFN time slot in the radio frame containing the SFN time slot, and its value may be of string type, and the bit mapping (bitmap) method is adopted, where 1 indicates an SFN time slot and 0 indicates a general time slot, and the length of the string is the number of time slots included in a radio frame. For example, when the sub-carrier spacing (SCS) = 15 KHz, the length of the string is 10; when SCS = 30 KHz, the length of the string is 20; when SCS = 60 KHz, the length of the string is 40; when SCS = 120 KHz, the length of the string is 80.
[0173] Such as Figure 7As shown in the figure, the allocation period of the radio frame containing SFN time slots is 4, i.e., radioframeAllociationPeriod = 4; the allocation offset of the radio frame containing SFN time slots is 0, i.e., radioframeAllociationOffset = 0; the length of the radio frame shown in the figure is 10 ms, including 20 time slots, i.e., SCS = 30 KHz. Therefore, the length of the value of SFNslotOneFrame is 20, and the SFN time slot allocation string shown in the figure is 11001000100001100010, i.e., SFNslotOneFrame = 11001000100001100010, where 1 represents an SFN time slot and 0 represents a normal time slot. Therefore, it can be known that time slots 1, 2, 5, 9, 14, 15, and 19 in each radio frame containing SFN time slots are SFN time slots, and the remaining time slots are normal time slots.
[0174] Optionally, the configuration information of the SFN resource and the normal resource may further include: the allocation period of the time slot containing SFN symbols, the offset of the time slot containing SFN symbols, and the allocation information of SFN symbols and normal symbols in the time slot containing SFN symbols. Among them, the SFN symbol is the symbol where the SFN resource is located, and the normal symbol is the symbol where the normal resource is located. The indication information #1 is used to indicate that if the resource for transmitting SFN service data indicated by the resource scheduling message sent by the network device is a normal resource, then the normal resource is converted into an SFN resource.
[0175] The configuration information of the SFN resource sent by the network device to the terminal device may include the following information: (1) radioframeAllociationPeriod: indicating the allocation period of the time slot containing the SFN symbol, and the period may be 1, 2, 4, 8, 16, 32, or other values; (2) radioframeAllociationOffset: indicating the allocation offset of the time slot containing the SFN symbol, and the value may be 0, 1, 2, 3, 4, 5, 6, 7, or other values; (3) candidateSFN: indicating whether a certain symbol in the radio frame containing the SFN symbol is an SFN symbol or a common symbol, and the value may be of bool type. For example, the value of 1 indicates an SFN symbol, and the value of 0 indicates a common symbol; (4) SFNslotOneFrame: the allocation information of the SFN symbol in the time slot containing the SFN symbol, and the value may be of string type, using the bitmap method, 1 indicates an SFN symbol, 0 indicates a common symbol, and the length of the string is 14. The representation method may use the enumeration method, such as the fixed set of situations {fronthalt-slot, endhalf-slot, all-slot}, where fronthalt-slot means the first seven symbols in a time slot are SFN symbols, endhalf-slot means the last seven symbols in a time slot are SFN symbols, and all-slot means all symbols in a time slot are SFN symbols.
[0176] As Figure 8 shown, the allocation period of the time slot containing the SFN symbol is 4, that is, radioframeAllociationPeriod = 4, the allocation offset of the time slot containing the SFN symbol is 0, that is, radioframeAllociationOffset = 0, the length of the value of SFNslotOneFrame is 14, and the SFN symbol allocation string shown in the figure is 00000001111111, that is, SFNslotOneFrame = 00000001111111, where 1 indicates an SFN symbol and 0 indicates a common symbol. Therefore, it can be known that the first seven symbols of each time slot containing the SFN symbol are common symbols, and the last seven symbols are SFN symbols.
[0177] S620, the network device determines the first resource.
[0178] As described above, the network device may determine the SFN resource and the common resource as the first resource.
[0179] S630, the network device sends a resource scheduling message #1 (an example of a resource scheduling message) on the SFN resource.
[0180] Among them, the resource scheduling message #1 indicates that services are transmitted in SFN mode on the first resource.
[0181] 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 services are transmitted in SFN mode on the first resource.
[0182] It can be understood that if the network device sends the configuration information of the SFN resource to the terminal device, the network device only sends the resource scheduling message #1 to the terminal device on the SFN resource. Correspondingly, the terminal device only receives the resource scheduling message #1 on the SFN resource. 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 the resource for transmitting SFN service data. Further, the terminal device receives the SFN service data on the resource indicated by the resource scheduling message #1 in SFN mode.
[0183] As described above, the network device can determine the SFN resource and the ordinary resource as the first resource. Therefore, the first resource indicated by the resource scheduling message #1 can be an SFN resource or an ordinary resource. And the terminal device can determine according to the indication information #1 that if the first resource is an ordinary resource, then the ordinary resource is converted into an SFN resource.
[0184] For example, the network device sends the resource scheduling message #1 to the terminal device through the SFN resource in time slot n. The time domain position of the first resource indicated by the resource scheduling message #1 is in the ordinary time slot n + 2, that is, the first resource is an ordinary resource. Further, the network device sends the SFN service to the terminal device through the first resource indicated by the resource scheduling message #1 in time slot n + 2. Correspondingly, the terminal device receives the SFN service in SFN mode in time slot n + 2. And, the ordinary resource in time slot n + 2 is converted into an SFN resource. As Figure 9 shown, the SFN scheduling signaling sent by the network device through the SFN resource in time slot n indicates that the time domain position of the resource for transmitting the SFN service is in the ordinary time slot n + 2, then the ordinary resource in time slot n + 2 is scheduled as an SFN resource.
[0185] As described above, if the terminal device receives the resource scheduling message #2 (another example of the resource scheduling message) on the ordinary resource, it can be determined that the resource scheduling message #2 indicates that services are transmitted in non - SFN mode on the first resource.
[0186] The network device may scramble the resource scheduling message #1 using a broadcast radio network temporary identity (bc-RNTI). Correspondingly, the terminal device uses the bc-RNTI as a scrambling code to receive the resource scheduling message #1.
[0187] 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, which is used to indicate the position of the frequency domain information of the resources for transmitting the SFN service; a time domain resource allocation indication, which is used to indicate the position of the time domain information of the resources for transmitting the SFN service; a modulation and coding scheme, which is used to indicate the modulation and coding format of the SFN service; an associated reference signal indication (an example of the second indication information), which is used to indicate the associated reference signal index when the terminal device receives the SFN service.
[0188] Among them, the time domain resource indication includes a time slot offset K0 (an example of the parameter K0) and a start and length indicator (SLIV). K0 is used to indicate the number of time domain resource units between the resources for transmitting the resource scheduling message #1 and the resources indicated by the resource scheduling message #1. For example, K0 = 1 indicates that the number of time domain resource units between the resources indicated by the resource scheduling message #1 and the resources for transmitting the resource scheduling message #1 is 0, which can also be understood as the resources indicated by the resource scheduling message #1 and the resources for transmitting the resource scheduling message #1 are in the same time slot. Another example, K0 = 1 indicates that the number of time domain resource units between the resources indicated by the resource scheduling message #1 and the resources for transmitting the resource scheduling message #1 is 1, which can also be understood as the resources indicated by the resource scheduling message #1 are in the next time slot after the time slot where the resources for transmitting the resource scheduling message #1 are located. SLIV is used to indicate the start symbol and the symbol length of the resources indicated by the resource scheduling message #1 in a certain time slot, where S represents the start symbol and L represents the symbol length.
[0189] Such as Figure 10As shown in the figure, the time-domain resource indication parameters included in the DCI sent by the network device in 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 sent by the network device in time slot n is in the next time slot of time slot n, that is, time 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 parameters included in the DCI sent by the network device in time slot n + 3 are: K0 = 0, starting symbol (S): #3, symbol length (L): 11, indicating that the resource indicated by the DCI sent by the network device in time slot n + 3 is in the same time slot as time slot n, that is, time slot n + 3, and the starting symbol of the resource indicated by the DCI is #3 and the symbol length is 11.
[0190] Before the network device sends the resource scheduling message #1 to the terminal device, the network device may send 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. Among them, the indication bit information is in one-to-one correspondence with different associated reference signals.
[0191] The manner and content of the network device sending the first configuration information to the terminal device are as described above. For the sake of brevity, it will not be elaborated here.
[0192] In another implementation manner, the resource scheduling message #1 sent by the network device to the terminal device may include: frequency-domain resource allocation indication, used to indicate the frequency-domain information position of the resource for transmitting the SFN service; time-domain resource allocation indication, used to indicate the time-domain information position of the resource for transmitting the SFN service; modulation and coding format, used to indicate the modulation and coding format of the SFN service; first TMGI, used to indicate the associated reference signal index and the identification number of the SFN service when the terminal device receives the SFN service.
[0193] 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: second TMGI; first TMGI value; associated reference signal type; associated reference signal number. Among them, the second TMGI is used to identify the identification number of the SFN service data, and the value of the first TMGI is the number associated with the second TMGI.
[0194] The manner and content of the network device sending the second configuration information to the terminal device are as described above. For the sake of brevity, it will not be elaborated here.
[0195] In an embodiment of the present application, the network device configures SFN resources for transmitting SFN services and ordinary resources for transmitting SFN services and non-SFN services in a semi-static manner. When the demand for SFN services increases, ordinary resources can be scheduled as SFN resources, thereby adapting to the increasing demand for SFN services and achieving the purpose of flexible configuration of SFN resources.
[0196] Figure 11 FIG. 4 shows a schematic flowchart of a resource scheduling method provided in another embodiment of the present application. Figure 11 The method 1100 shown makes a more detailed description of the example where the non-SFN resources mentioned in step S310 are ordinary resources and candidate resources.
[0197] As Figure 11 shown, the method 1100 may include S1101-S1103, and each step is described in detail below.
[0198] S1101, the network device sends configuration information #2 to the terminal device.
[0199] Among them, the configuration information #2 may include configuration information and indication information #2 of SFN resources, ordinary resources, and candidate resources.
[0200] The configuration information of the SFN resources, ordinary resources, and candidate resources may include: the allocation period of the radio frame containing SFN time slots, the offset of the radio frame containing SFN time slots, and the allocation information of SFN time slots, ordinary time slots, and candidate time slots in the radio frame containing SFN time slots. Among them, the SFN time slot is the time slot where the SFN resource is located, the ordinary time slot is the time slot where the ordinary resource is located, and the candidate time slot is the time slot where the candidate resource is located. The indication information #2 is used to indicate that: if the resource for transmitting SFN services indicated in the resource scheduling message sent by the network device is a candidate resource, then the candidate resource is converted into an SFN resource; if the resource for transmitting non-SFN services indicated in the resource scheduling message sent by the network device is a candidate resource, then the candidate resource is converted into an ordinary resource.
[0201] The network device may send the configuration information #2 to the terminal device by using high-layer signaling. For example, the network device may send the configuration information of the SFN resources to the terminal device by establishing an RRC radio connection with the terminal device; or, the network device may send the configuration information of the SFN resources to the terminal device through MAC CE. The embodiments of the present application do not limit this.
[0202] 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. The embodiments of the present application do not limit this.
[0203] Taking the example that the network device first sends the configuration information of the SFN resource to the terminal device and then sends the configuration information of the candidate resource to the terminal device, the embodiments of the present application are described as follows.
[0204] 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 method 600. For the sake of brevity, it will not be elaborated here.
[0205] As Figure 7 shown, the allocation period of the radio frame containing the SFN time slot is 4, that is, radioframeAllociationPeriod = 4, the allocation offset of the radio frame containing the SFN time slot is 0, that is, radioframeAllociationOffset = 0. The length of the radio frame shown in the figure is 10 ms and contains 20 time slots, that is, SCS = 30 KHz. Therefore, the length of the value of SFNslotOneFrame is 20. The SFN time slot allocation string shown in the figure is 11001000100001100010, that is, SFNslotOneFrame = 11001000100001100010, where 1 represents the SFN time slot and 0 represents the normal time slot. Therefore, it can be known that time slots 1, 2, 5, 9, 14, 15, and 19 of each radio frame containing the SFN time slot are SFN time slots, and the remaining time slots are normal time slots.
[0206] Similarly, the configuration information of candidate resources sent by the network device to the terminal device may include the following information: (1) radioframeAllociationPeriod: indicating the allocation period of the radio frame containing the SFN time slot, and the period may be 1, 2, 4, 8, 16, 32, or other values; (2) radioframeAllociationOffset: indicating the allocation offset of the radio frame containing the SFN time slot, and the value may be 0, 1, 2, 3, 4, 5, 6, 7, or other values; (3) candidateSFN: indicating whether a certain time slot in the radio frame containing the SFN time slot is a candidate time slot or a normal time slot, and the value may be of bool type. For example, the value of 1 indicates a candidate time slot, and the value of 0 indicates a normal time slot; (4) SFNslotOneFrame: the allocation information of the candidate time slot in the radio frame containing the MBSFN time slot, and the value may be of string type and adopt the bitmap method. 1 indicates a candidate time slot, and 0 indicates a normal time slot. The length of the string is the number of time slots included in a radio frame. For example, when the sub-carrier space (SCS) = 15 KHz, the length of the string is 10; when SCS = 30 KHz, the length of the string is 20; when SCS = 60 KHz, the length of the string is 40; when SCS = 120 KHz, the length of the string is 80.
[0207] As Figure 12 shown, the allocation period of the radio frame containing the SFN radio frame is 4, that is, radioframeAllociationPeriod = 4, the allocation offset of the radio frame containing the SFN radio frame is 0, that is, radioframeAllociationOffset = 0. The length of the radio frame shown in the figure is 10 ms and contains 20 time slots, that is, SCS = 30 KHz. Therefore, the length of the value of SFNslotOneFrame is 20. The candidate time slot allocation string shown in the figure is 0011001000100001100, that is, SFNslotOneFrame = 0011001000100001100, where 1 indicates a candidate time slot and 0 indicates a normal time slot. Therefore, it can be known that time slots 3, 4, 7, 11, 12, 17, and 18 in each radio frame containing the SFN time slot are candidate time slots, and the remaining time slots are normal time slots.
[0208] Based on the configuration information of the SFN resources and the configuration information of the candidate time slot resources sent by the network device to the terminal device, the terminal device can determine which time slots are SFN time slots, which time slots are candidate time slots, and which time slots are normal time slots in a radio frame containing the SFN time slot.
[0209] Combined withFigure 7 and Figure 12 , such as Figure 13 As shown, in each radio frame containing SFN time slots, time slots 1, 2, 5, 9, 14, 15, 19 are SFN time slots, time slots 3, 4, 7, 11, 12, 17, 18 are candidate time slots, and the remaining time slots are ordinary time slots.
[0210] S1102, the network device determines a first resource that can be used as an SFN resource.
[0211] As described above, the network device can determine the SFN resource and the candidate resource as the first resource.
[0212] S1103, the network device sends resource scheduling message #1 on the SFN resource.
[0213] Among them, the first resource indicated by the resource scheduling message #1 is an SFN resource.
[0214] As described above, if the terminal device receives the resource scheduling message #1 on the SFN resource, it can determine that the resource scheduling message #1 indicates that services are transmitted in the SFN mode on the first resource.
[0215] As described above, the network device can determine the SFN resource and the candidate resource as the first resource. Therefore, the first resource indicated by the resource scheduling message #1 can be an SFN resource or a candidate resource. And according to indication information #2, the terminal device can determine that if the first resource indicated by the resource scheduling message #1 is a candidate resource, then the candidate resource is transformed into an SFN resource.
[0216] For example, the network device sends the resource scheduling message #1 to the terminal device through the SFN resource in time slot n. The time domain position of the first resource indicated by the resource scheduling message #1 is in the candidate time slot n + 2, that is, the first resource is a candidate resource. Further, the network device sends SFN services to the terminal device through the first resource in the candidate time slot n + 2. Correspondingly, the terminal device receives the SFN services in the candidate time slot n + 2 in the SFN manner. And the candidate resource in time slot n + 2 is transformed into an SFN resource. As Figure 14 shown, the SFN scheduling signaling sent by the network device through the SFN resource in the SFN time slot n indicates that the time domain position of the transmission resource for transmitting the SFN service is in the candidate time slot n + 2, then the candidate resource in time slot n + 2 is scheduled as an SFN resource.
[0217] As described above, if the terminal device receives the resource scheduling message #2 on the normal resource, it can determine that the resource scheduling message #2 indicates the transmission of services in the non-SFN mode on the first resource. And the first resource indicated by the resource scheduling message #2 can be a normal resource or a candidate resource. And the terminal device can determine according to the indication information #2 that if the first resource indicated by the resource scheduling message #2 is a candidate resource, then the candidate resource is transformed into a normal resource.
[0218] For example, the network device sends the resource scheduling message #2 to the terminal device through the normal resource in 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 sends 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 device receives the non-SFN service data in the candidate time slot n+6. And the candidate resource in the time slot n+6 is transformed into a normal resource. As Figure 14 shown, the normal scheduling signaling sent by the network device through the normal resource in the time slot n+5 indicates that the time domain position of the transmission resource for transmitting the non-SFN service is in the candidate time slot n+6, then the candidate resource in the time slot n+6 is scheduled as a normal resource.
[0219] The network device can scramble the resource scheduling message #1 with the bc-RNTI. Correspondingly, the terminal device receives the resource scheduling message #1 using the bc-RNTI as the scrambling code.
[0220] As described above, the resource scheduling message #1 sent by the network device to the terminal device may include: frequency domain resource allocation indication, time domain resource allocation indication, modulation and coding format, associated reference signal indication.
[0221] In the case where the network device configures the SFN resource, the normal resource, and the candidate resource for the terminal device, the calculation method of the parameter K0 is: only calculate the SFN resources and candidate resources with an interval between the resource for transmitting the resource scheduling message #1 and the resource for transmitting the SFN service data, and do not calculate the normal resources.
[0222] As Figure 15As shown in the figure, the time-domain resource indication parameters included in the DCI sent by the network device in 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 sent by the network device in time slot n is in time slot n + 2, that is, only the SFN time slot and the candidate time slot are calculated when calculating K0. Since time slot n + 1 is an ordinary time slot, time 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 parameters included in the DCI sent by the network device in time slot n + 3 are: K0 = 0, starting symbol (S): #3, symbol length (L): 11, indicating that the resource indicated by the DCI sent by the network device in time slot n + 3 is in the same time slot as time slot n + 3, that is, time slot n + 3, and the starting symbol of the indicated resource is #3 and the symbol length is 11.
[0223] Before the network device sends resource scheduling message #1 to the terminal device, the network device may send 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. Among them, the indication bit information corresponds one-to-one with different associated reference signals.
[0224] The manner and content of the network device sending the first configuration information to the terminal device are as described above. For the sake of brevity, it will not be elaborated here.
[0225] As described above, the resource scheduling message #1 sent by the network device to the terminal device may further include: frequency-domain resource allocation indication, time-domain resource allocation indication, modulation and coding format, first TMGI.
[0226] Before the network device sends 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: second TMGI; first TMGI value; associated reference signal type; associated reference signal number.
[0227] The manner and content of the network device sending the second configuration information to the terminal device are as described above. For the sake of brevity, it will not be elaborated here.
[0228] In the embodiments of the present application, the network device configures SFN resources for transmitting SFN service data, ordinary 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. In the case of an increase in the demand for SFN services, the candidate resources can be scheduled as SFN resources. In the case of an increase in the demand for non-SFN services, the candidate resources can be scheduled as ordinary resources, thereby achieving the purpose of flexible configuration of SFN resources.
[0229] Above, in combination with Figures 2 to 15The method provided by the embodiments of the present application is described in detail. Below, in combination with Figures 16 to 18 The device provided by the embodiments of the present application is described in detail.
[0230] Figure 16 It is a schematic block diagram of a communication device provided by an embodiment of the present application. As Figure 16 shown, the communication device 2000 may include a processing unit 2100 and a transceiver unit 2200.
[0231] In a possible design, the communication device 2000 may correspond to the terminal device in the above method embodiment. For example, it may be a terminal device, or a component (such as a chip or a chip system) configured in the terminal device.
[0232] It should be understood that the communication device 2000 may correspond to the terminal device in the method 300, method 600, and method 1100 according to the embodiments of the present application. The communication device 2000 may include units for executing Figure 3 the method 300 in Figure 6 the method 600 in Figure 11 the method 1100 executed by the terminal device in. And each unit in the communication device 2000 and the above other operations and / or functions respectively are for implementing Figure 3 the method 300 in Figure 6 the method 600 in Figure 11 the corresponding processes of the method 1100 in.
[0233] Among them, when the communication device 2000 is used to execute Figure 3 the method 300 in, the processing unit 2100 may be used to execute S320 in the method 300, and the transceiver unit 2200 may be used to execute S320 in the method 300. It should be understood that the specific processes of each unit executing the above corresponding steps have been described in detail in the above method embodiments. For the sake of brevity, they will not be repeated here.
[0234] When the communication device 2000 is used to execute Figure 6 the method 600 in, the processing unit 2100 may be used to execute S630 in the method 600, and the transceiver unit 2200 may be used to execute S610 and S630 in the method 600. It should be understood that the specific processes of each unit executing the above corresponding steps have been described in detail in the above method embodiments. For the sake of brevity, they will not be repeated here.
[0235] When the communication device 2000 is used to execute Figure 11When implementing the method 1100, the processing unit 2100 can be used to execute S1103 in the method 1100, and the transceiver unit 2200 can be used to execute S1101 and S1103 in the method 1100. It should be understood that the specific processes of the respective units in executing the above corresponding steps have been described in detail in the above method embodiments. For the sake of brevity, they will not be elaborated here.
[0236] It should also be understood that when the communication device 2000 is a terminal device, the transceiver unit 2200 in the communication device 2000 can be implemented by a transceiver. For example, it can correspond to Figure 17 the transceiver 3020 in the terminal device 3000 shown in Figure 17 and the processing unit 2100 in the communication device 2000 can be implemented by at least one processor. For example, it can correspond to
[0237] the processor 3010 in the terminal device 3000 shown in
[0238] In another possible design, the communication device 2000 can correspond to the network device in the above method embodiments. For example, it can be a network device or a component (such as a chip or a chip system) configured in a network device.
[0239] It should be understood that the communication device 2000 can correspond to the network device in Method 300, Method 600, and Method 1100 according to the embodiments of the present application. The communication device 2000 may include units for executing Figure 3 the method 300 in Figure 6 the method 600 in Figure 11 the method 1100 that the network device executes in Figure 3 the method 300 in Figure 6 the method 600 in Figure 11 the method 1100. And each unit in the communication device 2000 and the above other operations and / or functions respectively are for implementing
[0240] When the communication device 2000 is used to execute Figure 3 the method 300 in
[0241] When the communication device 2000 is used to execute Figure 6 method 600 in, the processing unit 2100 can be used to execute S620 in method 600, and the transceiver unit 2200 can be used to execute S610 and S630 in method 600. It should be understood that the specific processes of each unit executing the above corresponding steps have been described in detail in the above method embodiments. For the sake of brevity, they will not be repeated here.
[0242] When the communication device 2000 is used to execute Figure 11 method 1100 in, the processing unit 2100 can be used to execute S1102 in method 1100, and the transceiver unit 2200 can be used to execute S1101 and S1103 in method 1100. It should be understood that the specific processes of each unit executing the above corresponding steps have been described in detail in the above method embodiments. For the sake of brevity, they will not be repeated here.
[0243] It should also be understood that when the communication device 2000 is a network device, the transceiver unit 2200 in the communication device 2000 can be implemented by a transceiver, for example, it can correspond to Figure 18 the transceiver 4200 in the network device 4000 shown in, and the processing unit 2100 in the communication device 2000 can be implemented by at least one processor, for example, it can correspond to Figure 18 the processor 4100 in the network device 4000 shown in.
[0244] It should also be understood that when the communication device 2000 is a chip or a chip system configured in a network device, the transceiver unit 2200 in the communication device 2000 can be implemented through an input / output interface, and the processing unit 2100 in the communication device 2000 can be implemented through a processor, a microprocessor or an integrated circuit integrated on the chip or the chip system, etc.
[0245] Figure 17 is a schematic structural diagram of the terminal device 3000 provided by the embodiments of the present application. The terminal device 3000 can be applied to, such as Figure 1In the system shown, the functions of the terminal device in the above method embodiments are performed. As shown in the figure, the terminal device 3000 includes a processor 3010 and a transceiver 3020. Optionally, the terminal device 3000 further includes a memory 3030. Among them, the processor 3010, the transceiver 3002, and the memory 3030 can communicate with each other through an internal connection path to transmit control and / or data signals. The memory 3030 is used to store a computer program, and the processor 3010 is used to call and run 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, which is used to send the uplink data or uplink control signaling output by the transceiver 3020 through a wireless signal.
[0246] The above-mentioned processor 3010 and the memory 3030 can be integrated into a processing device. The processor 3010 is used to execute the program code stored in the memory 3030 to implement the above functions. Specifically, the memory 3030 can also be integrated in the processor 3010 or independent of the processor 3010. The processor 3010 can correspond to Figure 16 the processing unit 2100 therein.
[0247] The above-mentioned transceiver 3020 can correspond to Figure 16 the transceiver unit 2200 therein and can also be referred to as the transceiver unit. The transceiver 2020 can include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Among them, the receiver is used to receive signals, and the transmitter is used to transmit signals.
[0248] It should be understood that Figure 17 the terminal device 3000 shown can implement Figure 3 , Figure 6 and Figure 11 each process related to the terminal device in the method embodiments shown therein. The operations and / or functions of each module in the terminal device 3000 are respectively for implementing the corresponding processes in the above method embodiments. For details, reference can be made to the description in the above method embodiments. To avoid repetition, the detailed description is appropriately omitted here.
[0249] The above-mentioned processor 3010 can be used to execute the actions implemented internally by the terminal device described in the previous method embodiments, such as determining to transmit services in the SFN mode on the first resource, etc. The transceiver 3020 can be used to execute the actions of the terminal device sending to or receiving from the network device described in the previous method embodiments, such as receiving a resource scheduling message, etc. For details, reference can be made to the description in the previous method embodiments and will not be elaborated here.
[0250] Among them, the above terminal device 3000 may further include a power supply 3050 for supplying power to various components or circuits in the terminal device.
[0251] In addition, 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, and a sensor 3100, etc. The audio circuit may further include a speaker 3082, a microphone 3084, etc.
[0252] Figure 18 is a schematic structural diagram of a network device provided by an embodiment of the present application, which may be, for example, a schematic structural diagram of a base station. The base station 4000 can be applied to a system as shown in Figure 1 and perform the functions of the network device in the above method embodiments. As shown in the figure, 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) (which may also be referred to as distributed units (DUs)) 4200. The RRU 4100 may be referred to as a transceiver unit or a part of the transceiver unit, corresponding to the transceiver unit 2200 in Figure 16 . Optionally, the transceiver unit 4100 may also be referred to as a transceiver, a transceiver circuit, or a transceiver, etc., and may include at least one antenna 4101 and a radio frequency unit 4102. Optionally, the transceiver unit 4100 may include a receiving unit and a transmitting unit. The receiving unit may correspond to a receiver (or a receiver circuit), and the transmitting unit may correspond to a transmitter (or a transmitter circuit). The RRU 4100 part is mainly used for the transceiver of radio frequency signals and the conversion between radio frequency signals and baseband signals. For example, it is used to send resource scheduling messages to the terminal device, etc. For specific details, please refer to the description in the previous method embodiments, and details will not be repeated here.
[0253] The BBU 4200 part is mainly used for baseband processing and controlling the base station, etc. The RRU 4100 and the BBU 4200 may be physically set together or physically separated, that is, a distributed base station.
[0254] The BBU 4200 is the control center of the base station and may also be referred to as a processing unit, corresponding to the processing unit 2100 in Figure 16 , and can be used to complete baseband processing functions, such as channel coding, multiplexing, modulation, spreading, etc. For example, the BBU (processing unit) can be used to control the base station to execute the operation process of the network device in the above method embodiments. For example, to generate the above resource allocation information, etc. For specific details, please refer to the description in the previous method embodiments, and details will not be repeated here.
[0255] In one example, the BBU 4200 may be composed of one or more single boards. Multiple single boards may jointly support a radio access network of a single access mode (such as an LTE network), or may separately support radio access networks of different access modes (such as 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 used to control the base station to perform necessary actions, for example, to control the base station to execute the operation procedures of the network device in the above method embodiments. The memory 4201 and the processor 4202 may serve one or more single boards. That is to say, a memory and a processor may be separately provided on each single board. It is also possible that multiple single boards share the same memory and processor. In addition, necessary circuits may be provided on each single board.
[0256] It should be understood that Figure 18 the shown base station 4000 can implement Figure 3 , Figure 6 and Figure 11 each process related to the network device in the shown method embodiments. The operations and / or functions of each module in the base station 4000 are respectively for implementing the corresponding processes in the above method embodiments. For details, reference may be made to the descriptions in the above method embodiments. To avoid repetition, detailed descriptions are appropriately omitted here.
[0257] The above BBU 4200 may be used to execute the actions implemented inside the network device described in the previous method embodiments, while the RRU 4100 may be used to execute the actions of the network device sending to or receiving from the terminal device described in the previous method embodiments. For details, please refer to the descriptions in the previous method embodiments and will not be repeated here.
[0258] It should be understood that Figure 18 the shown base station 4000 is only a possible form of the network device and should not impose any limitation on the present application. The method provided by the present application is applicable to other forms of network devices. For example, it includes an AAU, and may also include a CU and / or a DU, or includes a BBU and an adaptive radio unit (ARU), or a BBU; it may also be a customer premises equipment (CPE), or other forms. The present application does not limit the specific form of the network device.
[0259] Among them, the CU and / or DU can be used to perform the actions implemented inside the network device described in the foregoing method embodiments, while the AAU can be used to perform the actions of the network device sending to or receiving from the terminal device described in the foregoing method embodiments. For specific details, please refer to the description in the foregoing method embodiments and will not be elaborated here.
[0260] An embodiment of this application also provides a processing device, including a processor and an interface; the processor is used to execute the method in any of the foregoing method embodiments.
[0261] It should be understood that the foregoing processing device 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 processor unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.
[0262] In the implementation process, each step of the foregoing method can be completed by the integrated logic circuit in the hardware of the processor or the instructions in the form of software. The steps of the method disclosed in combination with the embodiments of this application can be directly embodied as being executed and completed by the hardware processor, or executed and completed by the combination of the hardware and software modules in the processor. The software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read only memory, a programmable read only memory, or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the foregoing method. To avoid repetition, it will not be described in detail here.
[0263] It should be noted that the processor in the embodiments of the present application can be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the above method embodiments can be completed by the integrated logic circuit in the hardware of the processor or instructions in the form of software. The above processor can 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 devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the art such as a random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.
[0264] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. 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 synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct rambus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include but not be limited to these and any other suitable types of memory.
[0265] According to the method provided by the embodiments of the present application, the present application also provides a computer program product, which includes: computer program code, when the computer program code runs on a computer, it causes the computer to execute Figure 3 , Figure 6 and Figure 11 the methods respectively executed by the terminal device and the network device in the embodiments shown.
[0266] According to the method provided by the embodiments of the present application, the present application also provides a computer-readable medium, which stores program code, when the program code runs on a computer, it causes the computer to execute Figure 3 , Figure 6 and Figure 11 the methods respectively executed by the terminal device and the network device in the embodiments shown.
[0267] According to the method provided by the embodiments of the present application, the present application also provides a system, which includes one or more of the foregoing terminal devices and one or more network devices.
[0268] The network device in each of the above device embodiments corresponds exactly to the network device or the terminal device in the method embodiments, and the corresponding modules or units execute the corresponding steps. For example, the communication unit (transceiver) executes the steps of receiving or sending in the method embodiments, and other steps except sending and receiving can be executed by the processing unit (processor). The functions of the specific units can refer to the corresponding method embodiments. Among them, the processor can be one or more.
[0269] The terms "component", "module", "system", etc. used in this specification are used to represent computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. By way of illustration, an application running on a computing device and the computing device can both be components. One or more components can reside in a process and / or an execution thread, and the components can be located on one computer and / or distributed between two or more computers. In addition, these components can execute from various computer-readable media on which various data structures are stored. Components can communicate, for example, through local and / or remote processes according to signals having one or more data packets (for example, data from two components interacting with each other between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems through signals).
[0270] Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of this application.
[0271] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and will not be elaborated herein.
[0272] In several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces, and the indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.
[0273] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they can be located in one place, or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0274] In addition, the functional units in each embodiment of this application can be integrated in one processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.
[0275] In the above embodiments, the functions of each functional unit can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can 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). When the computer program instructions (programs) are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired manner (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that the computer can access, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a high-density digital video disc (DVD)), or a semiconductor medium (such as a solid-state disk (SSD)).
[0276] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs, etc., which can store program codes of various kinds.
[0277] As described above, the above are only specific implementation manners of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application, and all of them should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.
Claims
1. A resource scheduling method, characterized in that Including: Determine a first resource, where the first resource includes a single-frequency network (SFN) resource and a non-SFN resource previously configured by a network device for a terminal device. The SFN resource is a resource used to transmit services in SFN mode, and the non-SFN resource includes a general resource or a candidate resource; Send a resource scheduling message of the first resource, where the resource scheduling message is used to indicate to transmit services in SFN mode or non-SFN mode on the first resource.
2. The method according to claim 1, characterized in that Sending the resource scheduling message of the first resource includes: Send the resource scheduling message on a second resource; Wherein, the resource scheduling message is used to indicate to transmit services in SFN mode or non-SFN mode on the first resource, including: If the second resource is an SFN resource, it indicates to transmit services in SFN mode on the first resource; If the second resource is a non-SFN resource, it indicates to transmit services in non-SFN mode on the first resource.
3. The method according to claim 1, wherein The resource scheduling message includes first indication information for indicating a transmission mode; Wherein, the resource scheduling message is used to indicate to transmit services in SFN mode or non-SFN mode on the first resource, including: If the first indication information indicates that the transmission mode is SFN mode, it indicates to transmit services in SFN mode on the first resource; If the first indication information indicates that the transmission mode is non-SFN mode, it indicates to transmit services in non-SFN mode on the first resource.
4. The method according to claim 1, characterized in that The resource scheduling message is used to indicate to transmit services in SFN mode or non-SFN mode on the first resource, including: If the resource scheduling message can be received with a first radio network temporary identity (RNTI) as a scrambling code, it indicates to transmit services in SFN mode on the first resource, If the resource scheduling message cannot be received with the first RNTI as a scrambling code, it indicates to transmit services in non-SFN mode on the first resource.
5. The method according to claim 2, wherein When the second resource is an SFN resource, the resource scheduling message is further used to indicate a parameter K0, and the value of the parameter K0 indicates the number of time-domain resource units between the first resource and the second resource, where the time-domain resource units do not include resources that are not available for transmitting services in SFN mode.
6. The method according to any one of claims 1-5, characterized in that, If the resource scheduling message indicates to transmit services in 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 SFN mode, and the second indication information includes one or more of the following: reference signal type, reference signal number, indication bit information.
7. The method according to claim 6, characterized in that, The method further includes: Send first configuration information, where the first configuration information includes: reference signal type, reference signal number, indication bit information.
8. The method according to any one of claims 1 to 5, characterized in that, If the resource scheduling message indicates that traffic is transmitted in 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 traffic transmitted in SFN mode, and the first TMGI is associated with the second TMGI, the second TMGI being used to identify the identification number of the traffic transmitted in SFN mode.
9. The method according to claim 8, characterized in that, The method further includes: Sending second configuration information, the second configuration information including: the first TMGI, the second TMGI, and a reference signal associated with the traffic transmitted in SFN mode.
10. A method for resource scheduling, characterized in that, Including: Receiving a resource scheduling message, the resource scheduling message indicating a first resource, the first resource including a Single Frequency Network (SFN) resource and a non-SFN resource pre-configured by a network device for a terminal device, the SFN resource being a resource for transmitting traffic in SFN mode, and the non-SFN resource including a normal resource or a candidate resource; Determining, according to the resource scheduling message, to transmit traffic in SFN mode or in non-SFN mode on the first resource.
11. The method according to claim 10, characterized in that, Receiving the resource scheduling message of the first resource includes: Receiving the resource scheduling message on a second resource; Wherein, determining to transmit traffic in SFN mode or in non-SFN mode on the first resource according to the resource scheduling message includes: If the second resource is an SFN resource, it indicates that traffic is transmitted in SFN mode on the first resource; If the second resource is a non-SFN resource, it indicates that traffic is transmitted in non-SFN mode on the first resource.
12. The method according to claim 10, characterized in that The resource scheduling message includes first indication information for indicating a transmission mode; Wherein, determining to transmit traffic in SFN mode or in non-SFN mode on the first resource according to the resource scheduling message includes: If the first indication information indicates that the transmission mode is SFN mode, it indicates that traffic is transmitted in SFN mode on the first resource; If the first indication information indicates that the transmission mode is non-SFN mode, it indicates that traffic is transmitted in non-SFN mode on the first resource.
13. The method according to claim 10, wherein Determining to transmit traffic in SFN mode or in non-SFN mode on the first resource according to the resource scheduling message includes: If the resource scheduling message can be received using a first Radio Network Temporary Identity (RNTI) as a scrambling code, it indicates that traffic is transmitted in SFN mode on the first resource, If the resource scheduling message cannot be received using the first RNTI as a scrambling code, it indicates that traffic is transmitted in non-SFN mode on the first resource.
14. The method according to claim 11, wherein In the case where the second resource is an SFN resource, the resource scheduling message is further used to indicate a parameter K0, and the value of the parameter K0 indicates the number of time domain resource units between the first resource and the second resource, where the time domain resource units do not include resources that are not available for transmitting traffic in SFN mode.
15. The method according to any one of claims 10-14, characterized in that, If the resource scheduling message indicates that services are transmitted in SFN mode on the first resource, the resource scheduling message further includes second indication information for indicating a reference signal associated with the services transmitted in SFN mode, and the second indication information includes one or more of the following: reference signal type, reference signal number, indication bit information.
16. The method according to claim 15, wherein The method further includes: receiving first configuration information, where the first configuration information includes: reference signal type, reference signal number, indication bit information.
17. The method according to any one of claims 10 to 14, characterized in that If the resource scheduling message indicates that services are transmitted in SFN mode on the first resource, the resource scheduling message further includes a first Temporary Mobile Group Identity (TMGI), where the first TMGI is used to indicate a reference signal and a second TMGI associated with the services transmitted in SFN mode, and the first TMGI is associated with the second TMGI, and the second TMGI is used to identify an identification number of the services transmitted in SFN mode.
18. The method according to claim 17, characterized in that, The method further includes: receiving second configuration information, where the second configuration information includes: the first TMGI, the second TMGI, and a reference signal associated with the services transmitted in SFN mode.
19. A communication device, characterized in that, including a processing unit and a transceiver unit The processing unit is configured to: determine a first resource, where the first resource includes an SFN resource and a non-SFN resource pre-configured by a network device for a terminal device, the SFN resource is a resource for transmitting services in SFN mode, and the non-SFN resource includes a normal resource or a candidate resource; The transceiver unit is configured to: send a resource scheduling message of the first resource, where the resource scheduling message is used to indicate that services are transmitted in SFN mode or non-SFN mode on the first resource.
20. The communication device according to claim 19, wherein Specifically, the transceiver unit is configured to: send the resource scheduling message on a second resource; wherein, the resource scheduling message for indicating that services are transmitted in SFN mode or non-SFN mode on the first resource includes: if the second resource is an SFN resource, it indicates that services are transmitted in SFN mode on the first resource; if the second resource is a non-SFN resource, it indicates that services are transmitted in non-SFN mode on the first resource.
21. The communication device according to claim 19, characterized in that, The resource scheduling message includes first indication information for indicating a transmission mode; wherein, the resource scheduling message for indicating that services are transmitted in SFN mode or non-SFN mode on the first resource includes: if the first indication information indicates that the transmission mode is SFN mode, it indicates that services are transmitted in SFN mode on the first resource; if the first indication information indicates that the transmission mode is non-SFN mode, it indicates that services are transmitted in non-SFN mode on the first resource.
22. The communication device according to claim 19, wherein The resource scheduling message for indicating that services are transmitted in SFN mode or non-SFN mode on the first resource includes: if the resource scheduling message can be received with a first Radio Network Temporary Identity (RNTI) as a scrambling code, it indicates that services are transmitted in SFN mode on the first resource, If the resource scheduling message cannot be received with the first RNTI as the scrambling code, it indicates that services are transmitted in a non-SFN mode on the first resource.
23. The communication device according to claim 20, wherein When the second resource is an SFN resource, the resource scheduling message is further used to indicate a parameter K0, and the value of the parameter K0 indicates the number of time-domain resource units between the first resource and the second resource, where the time-domain resource units do not include resources that are not available for transmitting services in the SFN mode.
24. The communication device according to any one of claims 19-23, characterized in that, If the resource scheduling message indicates that services are transmitted in the SFN mode on the first resource, the resource scheduling message further includes second indication information, which is used to indicate a reference signal associated with the services 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.
25. The communication device according to claim 24, wherein The transceiver unit is further configured to: Transmit first configuration information, where the first configuration information includes: reference signal type, reference signal number, indication bit information.
26. The communication device according to any one of claims 19-23, characterized in that, If the resource scheduling message indicates that services are transmitted in the SFN mode on the first resource, the resource scheduling message further includes a first temporary mobile group identifier (TMGI), where the first TMGI is used to indicate a reference signal and a second TMGI associated with the services transmitted in the SFN mode, and the first TMGI is associated with the second TMGI, and the second TMGI is used to identify the identification number of the services transmitted in the SFN mode.
27. The communication device according to claim 26, wherein The transceiver unit is further configured to: Transmit second configuration information, where the second configuration information includes: the first TMGI, the second TMGI, and a reference signal associated with the services transmitted in the SFN mode.
28. A communication device, characterized in that, Comprising a transceiver unit and a processing unit: The transceiver unit is configured to: receive a resource scheduling message, where the resource scheduling message indicates a first resource, and the first resource includes a single-frequency network (SFN) resource and a non-SFN resource pre-configured by a network device for a terminal device, the SFN resource is a resource for transmitting services in the SFN mode, and the non-SFN resource includes a normal resource or a candidate resource; The processing unit is configured to: determine whether to transmit services in the SFN mode or in a non-SFN mode on the first resource according to the resource scheduling message.
29. The communication device according to claim 28, wherein, Specifically, the transceiver unit is configured to: Receive the resource scheduling message on a second resource; Specifically, the processing unit is configured to: If the second resource is an SFN resource, it indicates that services are transmitted in the SFN mode on the first resource; If the second resource is a non-SFN resource, it indicates that services are transmitted in a non-SFN mode on the first resource.
30. The communication device according to claim 28, wherein The resource scheduling message includes first indication information for indicating a transmission mode; Specifically, the processing unit is configured to: If the first indication information indicates that the transmission mode is the SFN mode, it indicates that services 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, it indicates that services are transmitted in a non-SFN mode on the first resource.
31. The communication device according to claim 28, characterized in that, Specifically, the processing unit is configured to: If the resource scheduling message can be received with the first radio network temporary identifier (RNTI) as the scrambling code, it indicates that services are transmitted in the SFN mode on the first resource. If the resource scheduling message cannot be received with the first RNTI as the scrambling code, it indicates that services are transmitted in a non-SFN mode on the first resource.
32. The communication device according to claim 29, wherein, When the second resource is an SFN resource, the resource scheduling message is further used to indicate a parameter K0, and the value of the parameter K0 indicates the number of time-domain resource units between the first resource and the second resource, where the time-domain resource units do not include resources that are not available for transmitting services in the SFN mode.
33. The communication device according to any one of claims 28-32, characterized in that, If the resource scheduling message indicates that services are transmitted in the SFN mode on the first resource, the resource scheduling message further includes second indication information, which is used to indicate a reference signal associated with the services transmitted in the SFN mode. The second indication information includes one or more of the following: reference signal type, reference signal number, indication bit information.
34. The communication device according to claim 33, characterized in that, The transceiver unit is further configured to: Receive first configuration information, which includes: reference signal type, reference signal number, indication bit information.
35. The communication device according to any one of claims 28-32, characterized in that, If the resource scheduling message indicates that services are transmitted in the SFN mode on the first resource, the resource scheduling message further includes a first temporary mobile group identifier (TMGI). The first TMGI is used to indicate a reference signal associated with the services transmitted in the SFN mode and a second TMGI, and the first TMGI is associated with the second TMGI. The second TMGI is used to identify the identification number of the services transmitted in the SFN mode.
36. The communication device according to claim 35, characterized in that, The transceiver unit is further configured to: Receive second configuration information, which includes: the first TMGI, the second TMGI, and a reference signal associated with the services transmitted in the SFN mode.
37. A communication device, characterized in that, Comprising: A processor, configured to execute computer instructions stored in a memory, so that the device executes: the method according to any one of claims 1-9.
38. A communication device, characterized in that, Comprising: A processor, configured to execute computer instructions stored in a memory, so that the device executes: the method according to any one of claims 10-18.
39. A computer-readable storage medium, characterized in that, A computer program is stored thereon, and when the computer program is executed, it causes the execution of the method according to any one of claims 1-18.
Citation Information
Patent Citations
System and method for providing services using the same frequency in a wireless communication system
US20060148408A1