A semi-static scheduling method and device

Abstract

The present application discloses a semi-static scheduling method and device, which is used to solve the problem in the related art that the semi-static scheduling period does not match the actual data transmission demand, resulting in waste of wireless resources. The method includes: the network device determines the configuration of the semi-static scheduling to be activated from multiple semi-static scheduling configurations pre-allocated to the terminal according to the time interval of at least two requests, wherein the configuration of the semi-static scheduling to be activated is different from the configuration of the semi-static scheduling currently adopted by the network device and the terminal; multiple requests are used to instruct the network device to update the data to be sent or multiple requests are used to instruct the network device to allocate time-frequency resources; the time interval is the time interval between any two requests that are adjacent in the time domain among the multiple requests, and the time interval between any two requests that are adjacent in the time domain among the multiple requests is the same; the network device instructs the terminal to activate the configuration of the semi-static scheduling to be activated.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a semi-static scheduling method and device. Background Art

[0002] Semi-Persistent Scheduling (SPS) refers to configuring periodic scheduling parameters for the terminal based on Radio Resource Control (RRC) signaling, and scrambling the Physical Downlink Control Channel (PDCCH) through the Semi-Persistent Scheduling-Configured Scheduling RNTI (CS-RNTI) to activate the semi-persistent scheduling. When the semi-persistent scheduling is activated, the terminal can periodically receive downlink data at the same time-frequency resource location according to the period configured in the RRC signaling, so that the base station does not need to transmit PDCCH signaling in each scheduling time slot, which can save control channel resources.

[0003] However, if the selected semi-static scheduling cycle is unreasonable, it may lead to waste of video resources or reduction of service quality. For example, if the semi-static scheduling cycle is too short, it may cause the physical downlink shared channel (PDSCH) and the physical uplink shared channel (PUSCH) scheduled on some time slots to be padding data, which will waste the time and frequency resources of the PDSCH and PUSCH channels. On the contrary, if the semi-static scheduling cycle is too long, or it leads to the need to use dynamic scheduling to transmit data between two cycles, the purpose of saving PDCCH channel resources cannot be achieved. Summary of the invention

[0004] In an exemplary embodiment of the present application, a semi-static scheduling method and apparatus are provided to solve the problem in the related art that the semi-static scheduling period does not match the actual data transmission demand, resulting in waste of wireless resources.

[0005] In a first aspect, an embodiment of the present application provides a semi-static scheduling method, including:

[0006] The network device determines, according to a time interval of at least two requests, a configuration of the semi-static scheduling to be activated from a plurality of semi-static scheduling configurations pre-allocated to the terminal, wherein the configuration of the semi-static scheduling to be activated is different from the configuration of the semi-static scheduling currently adopted by the network device and the terminal; the plurality of requests are used to instruct the network device to update data to be sent or the plurality of requests are used to instruct the network device to allocate time-frequency resources; the time interval is a time interval between any two of the plurality of requests that are adjacent in the time domain, and the time interval between any two of the plurality of requests that are adjacent in the time domain is the same;

[0007] The network device instructs the terminal to activate the configuration of the semi-persistent scheduling to be activated.

[0008] In the related art, a fixed semi-static scheduling configuration is generally used for a service type. In some cases, the fixed semi-static scheduling may not conform to the actual data transmission between the network device and the terminal, resulting in a waste of wireless resources. Based on the above scheme, the network device can dynamically adjust the semi-static scheduling configuration according to the actual downlink data transmission situation, so that the semi-static scheduling configuration meets the actual requirements of data transmission between the network device and the terminal, avoiding waste of resources. In addition, since some service types, such as gaming services, do not have a dedicated 5G service quality identifier (5G QoS Identifier, 5QI) to carry, there is no semi-static scheduling configuration corresponding to such services in the network device. In the scheme proposed in the present application, even if there is no semi-static scheduling configuration for a certain service in the network device, the semi-static scheduling configuration that can be adopted by the service can be determined based on the actual uplink and downlink data transmission situation.

[0009] In some embodiments, when the multiple requests are used to instruct the network device to allocate time-frequency resources, the multiple requests are received from the terminal, and the method further includes:

[0010] When the network device does not receive a physical shared channel PUSCH signaling from the terminal within a set time period, it instructs the terminal to deactivate the currently adopted semi-static scheduling configuration.

[0011] In some embodiments, when the multiple requests are used to instruct the network device to update the data to be sent, the multiple requests are generated by the network device in the process of generating the data to be sent, and the method further includes:

[0012] When the network device does not generate the data to be sent within a set time period, it instructs the terminal to deactivate the configuration of the currently adopted semi-static scheduling.

[0013] Based on the above scheme, this application covers both uplink and downlink transmission scenarios, and can determine the semi-static scheduling configuration to be adopted according to the data transmission conditions in the two scenarios, respectively, to meet the actual requirements of network devices and terminals. In addition, in the above scheme, if the network device determines that there is no data transmission within the set time, it can deactivate the current semi-static scheduling configuration to avoid resource waste.

[0014] In some embodiments, each of the multiple semi-static scheduling configurations includes a period of each semi-static scheduling, and each of the semi-static scheduling configurations corresponds to a number, which is used to indicate activation of the corresponding semi-static scheduling configuration.

[0015] Based on the above scheme, each semi-static configuration corresponds to a number, and the number can be used to indicate to the terminal to activate the semi-static scheduling configuration. This solves the problem in the prior art that when multiple sets of semi-static scheduling are configured, the terminal needs to perform blind detection to determine which set of semi-static scheduling configuration is used, which puts a heavy burden on the terminal.

[0016] In some embodiments, determining a semi-persistent scheduling configuration to be activated from a plurality of semi-persistent scheduling configurations pre-allocated to a terminal according to a plurality of requested time intervals includes:

[0017] If the time interval is the same as a period of semi-static scheduling included in a first semi-static scheduling configuration among the multiple semi-static scheduling configurations, taking the first semi-static scheduling configuration as the semi-static scheduling configuration to be activated;

[0018] If the time interval is different from the multiple semi-static scheduling periods included in the multiple semi-static scheduling configurations, the second semi-static scheduling configuration is used as the configuration of the semi-static scheduling to be activated; the semi-static scheduling period included in the second semi-static scheduling configuration is the semi-static scheduling period among the multiple semi-static scheduling periods that is closest to the time interval.

[0019] In some embodiments, before instructing the terminal to activate the configuration of the semi-persistent scheduling to be activated, the method further includes:

[0020] The network device instructs the terminal to deactivate the currently adopted semi-persistent scheduling configuration.

[0021] In a second aspect, an embodiment of the present application provides a semi-static scheduling device, including:

[0022] A determination module, configured to determine a configuration of the semi-static scheduling to be activated from a plurality of semi-static scheduling configurations pre-allocated to the terminal according to a time interval of at least two requests, wherein the configuration of the semi-static scheduling to be activated is different from the configuration of the semi-static scheduling currently adopted by the network device and the terminal; the plurality of requests are used to instruct the network device to update data to be sent or the plurality of requests are used to instruct the network device to allocate time-frequency resources; the time interval is a time interval between any two of the plurality of requests that are adjacent in the time domain, and the time interval between any two of the plurality of requests that are adjacent in the time domain is the same;

[0023] The indication module is used to indicate to the terminal to activate the configuration of the semi-static scheduling to be activated.

[0024] In some embodiments, when the multiple requests are used to instruct the network device to allocate time-frequency resources, the multiple requests are received from the terminal, and the instructing module is further used to:

[0025] When no physical shared channel PUSCH signaling is received from the terminal within a set time period, the terminal is instructed to deactivate the currently adopted semi-static scheduling configuration.

[0026] In some embodiments, when the multiple requests are used to instruct the network device to update the data to be sent, the multiple requests are generated by the network device in the process of generating the data to be sent, and the indication module is further used to:

[0027] When the data to be sent is not generated within a set time period, instructing the terminal to deactivate the configuration of the currently adopted semi-static scheduling.

[0028] In some embodiments, each of the multiple semi-static scheduling configurations includes a period of each semi-static scheduling, and each of the semi-static scheduling configurations corresponds to a number, which is used to indicate activation of the corresponding semi-static scheduling configuration.

[0029] In some embodiments, the determining module is specifically configured to:

[0030] If the time interval is the same as a period of semi-static scheduling included in a first semi-static scheduling configuration among the multiple semi-static scheduling configurations, taking the first semi-static scheduling configuration as the semi-static scheduling configuration to be activated;

[0031] If the time interval is different from the multiple semi-static scheduling periods included in the multiple semi-static scheduling configurations, the second semi-static scheduling configuration is used as the configuration of the semi-static scheduling to be activated; the semi-static scheduling period included in the second semi-static scheduling configuration is the semi-static scheduling period among the multiple semi-static scheduling periods that is closest to the time interval.

[0032] In some embodiments, before instructing the terminal to activate the configuration of the semi-persistent scheduling to be activated, the instructing module is further used to:

[0033] Instruct the terminal to deactivate the currently adopted semi-persistent scheduling configuration.

[0034] In a third aspect, an embodiment of the present application provides an electronic device, the electronic device comprising a controller and a memory. The memory is used to store computer-executable instructions, and the controller executes the computer-executable instructions in the memory to use hardware resources in the controller to perform the operation steps of any possible implementation method of the first aspect.

[0035] In a fourth aspect, the present application provides a computer-readable storage medium, in which instructions are stored, and when the computer-readable storage medium is run on a computer, the computer executes the methods in the above aspects.

[0036] In addition, the beneficial effects of the second to fourth aspects can refer to the beneficial effects described in the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for describing the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application.

[0038] Figure 1 A schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0039] Figure 2 A flow chart of a semi-static scheduling method provided in an embodiment of the present application;

[0040] Figure 3 A flow chart of a method for uplink semi-static scheduling provided in an embodiment of the present application;

[0041] Figure 4 A flow chart of a method for downlink semi-static scheduling provided in an embodiment of the present application;

[0042] Figure 5 A schematic diagram of a device structure for implementing a semi-static scheduling method provided in an embodiment of the present application;

[0043] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0044] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the technical solution of the present application, rather than all of the embodiments. Based on the embodiments recorded in the application documents, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the technical solution of the present application.

[0045] The terms "first" and "second" in the specification and claims of the present application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the term "comprising" and any of their variations are intended to cover non-exclusive protection. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices. "Multiple" in the present application can mean at least two, for example, two, three or more, and the embodiments of the present application are not limited.

[0046] In addition, the term "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article, unless otherwise specified, generally indicates that the associated objects before and after are in an "or" relationship.

[0047] In order to facilitate understanding of the semi-static scheduling solution proposed in this application, the system architecture involved in this application is briefly introduced first. Figure 1 , is an architecture diagram of a communication system provided in an embodiment of the present application. It should be understood that the embodiment of the present application is not limited to Figure 1 In the system shown, in addition, Figure 1 The device in the structure can be hardware, software divided by function, or a combination of the two. Figure 1 As shown, the system architecture provided by the embodiment of the present application includes a terminal and a network device. The embodiment of the present application does not limit the number of terminals and network devices included in the system. The communication system may also include a core network device. Figure 1 Not shown.

[0048] User Equipment (UE), also known as terminal equipment, mobile station (MS), mobile terminal (MT), etc., is a device that provides voice and / or data connectivity to users, for example, a handheld device with wireless connection function, a vehicle-mounted device, etc. At present, some examples of terminals are: mobile phones, tablet computers, laptops, PDAs, mobile Internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.

[0049] The network equipment involved in the embodiments of the present application may also be referred to as a base station, an access network device or an access node (English: Access Node, abbreviated as: AN). A base station is a public mobile communication base station, which is an interface device for a mobile terminal to access the Internet. The network equipment may specifically be an evolved base station (English: Evolutional Node B, abbreviated as: eNB or eNodeB) in a long-term evolution (LTE) system, or a base station device (gNB) in a 5G network, and this application does not limit this.

[0050] For example, Figure 1 The core network equipment not shown in the figure may include an access and mobility management function (AMF), a session management function (SMF), etc.

[0051] At present, the methods used by network devices to perform resource scheduling for terminals include dynamic scheduling and semi-static scheduling. Dynamic scheduling refers to the allocation of uplink and downlink time-frequency domain resources to the terminal by the network device according to the scheduling request received from the terminal. Semi-static scheduling refers to the allocation of semi-static scheduling configuration to the terminal by the network device according to the type of service performed by the terminal, including the period and the time-frequency domain resources allocated to the terminal. Optionally, the network device can allocate the semi-static scheduling configuration to the terminal through Radio Resource Control (RRC) signaling. The network device can also indicate to the terminal to activate the semi-static scheduling configuration through Physical Downlink Control Channel (PDCCH) signaling. After the semi-static scheduling is activated, the terminal can periodically send and receive data on the time-frequency domain resources according to the semi-static scheduling configuration. Therefore, the selection of the period of semi-static scheduling is particularly important. If the period is selected too short, useless filler data will be sent on some time slots; if the period is selected too long, data will still be transmitted in a dynamic scheduling manner between the two periods, and the purpose of saving uplink and downlink channel resources will not be achieved.

[0052] In response to the above problems, the current solutions include the following two: one is that the network device allocates multiple sets of semi-static scheduling configurations to the terminal, each set of configurations corresponds to a semi-static scheduling-radio network temporary identifier (Configured Scheduling RNTI, CS-RNTI), and the network device will select one set from the multiple configurations according to the service type of the terminal. However, in this solution, the terminal does not know which set of semi-static scheduling configurations the network device has selected, so the terminal needs to blindly detect the PDCCH channel, which increases the burden on the terminal. Another solution is that after the network device allocates a set of semi-static scheduling configurations to the terminal, if it detects that this set of configurations is not suitable for the current service type of the terminal, it will reconfigure a set of semi-static scheduling configurations for the terminal to adapt to the current service type of the terminal. In this solution, the reconfiguration takes a long time, which may cause the current service of the terminal to be interrupted.

[0053] In view of this, the embodiment of the present application provides a method and apparatus for semi-static scheduling, whereby a network device can pre-allocate multiple sets of semi-static scheduling configurations for a terminal, and instruct the terminal to activate a set of semi-static scheduling configurations adapted to the service type of the current terminal according to the time interval of the scheduling request sent by the terminal or the time interval of the downlink data generated by the terminal. The semi-static scheduling configuration is adaptively adjusted according to the data transmission situation between the terminal and the terminal, thereby avoiding resource waste.

[0054] First, in order to understand the solution proposed in this application, see Figure 2, is a flow chart of a semi-static scheduling method provided in an embodiment of the present application, specifically including:

[0055] 201. A network device determines a semi-persistent scheduling configuration to be activated from a plurality of semi-persistent scheduling configurations pre-allocated to a terminal according to a time interval between at least two requests.

[0056] The semi-static scheduling configuration to be activated is different from the semi-static scheduling configuration currently used by the terminal. The time interval of the at least two requests refers to the time interval between any two requests that are adjacent in the time domain among the at least two requests, and the time interval between any two requests that are adjacent in the time domain among the multiple requests is the same. For example, the time interval between a request received at the first moment and a request received at the second moment is the same as the time interval between a request received at the second moment and a request received at the third moment.

[0057] Optionally, the number of requests may be pre-set. For example, the network device may pre-set that when 10 requests are received and the time intervals between any two of the 10 requests that are adjacent in time domain are the same, the semi-static scheduling configuration to be activated is determined according to the time interval between any two of the 10 requests that are adjacent in time domain.

[0058] As a possible implementation, the multiple requests may be scheduling requests sent by the terminal to the network device, for instructing the network device to allocate time-frequency resources. As another possible implementation, the multiple requests may also be used to instruct the network device to update the data to be sent.

[0059] 202. The network device instructs the terminal to activate the semi-static scheduling configuration to be activated.

[0060] Optionally, after the network device determines the semi-static scheduling configuration to be activated from multiple sets of pre-allocated semi-static scheduling configurations according to the time intervals of multiple requests, it can send indication information to the terminal to instruct the terminal to activate the semi-static scheduling configuration to be activated. Further, the terminal can periodically send and receive data on the corresponding time-frequency resources according to the activated semi-static scheduling configuration.

[0061] Based on the above scheme, the network device can dynamically adjust the semi-static scheduling configuration according to the actual downlink data transmission situation, so that the semi-static scheduling configuration meets the actual requirements of data transmission between the network device and the terminal, avoiding waste of resources. In addition, since some service types, such as gaming services, do not have dedicated 5QI bearers, there is no semi-static scheduling configuration corresponding to such services in the network device. In the scheme proposed in this application, even if there is no semi-static scheduling configuration for a certain service in the network device, the semi-static scheduling configuration that can be used for the service can be determined based on the actual uplink and downlink data transmission situation.

[0062] In some embodiments, the semi-static scheduling configuration may include the period of semi-static scheduling and the time-frequency domain resources allocated by the network device to the terminal. As an optional method, the network device may allocate multiple sets of semi-static scheduling configurations to the terminal when the terminal accesses, and the multiple periods included in the multiple sets of semi-static scheduling configurations may cover the data bearing periods of all periodic services that may be created by all terminals. As an example, the network device can count the data bearing periods corresponding to different service types, and then generate multiple different semi-static scheduling periods according to the multiple periods counted, and each semi-static scheduling period corresponds to a set of semi-static scheduling configurations. Optionally, the network device may also allocate a CS-RNTI to the terminal when the terminal accesses. Optionally, the network device may send multiple sets of semi-static scheduling configurations and CS-RNTIs allocated to it to the terminal through RRC signaling. As an example, each of the multiple sets of semi-static scheduling configurations sent by the network device may have a corresponding number.

[0063] In some embodiments, after allocating multiple sets of semi-static scheduling configurations to the terminal, the network device can detect the uplink and downlink data transmission conditions, and determine which set of semi-static scheduling configurations to use according to the data transmission conditions. As an optional method, the network device can determine the semi-static scheduling configuration to be activated based on the time interval between multiple requests. The time interval of the multiple requests refers to the time interval between any two adjacent requests in the time domain among the multiple requests. In one possible case, the multiple requests may be scheduling requests received by the network device from the terminal, used to instruct the network device to allocate time-frequency domain resources. In another possible case, the multiple requests may be generated by the network device when generating downlink data to be sent, used to instruct the network device to send downlink data.

[0064] Optionally, each set of semi-static scheduling configuration includes a semi-static scheduling period. When the network device determines the semi-static scheduling configuration to be activated according to the time intervals of multiple requests, the network device may adopt the following method: In one possible case, if the network device can determine that the time interval is the same as the semi-static scheduling period included in the first semi-static scheduling configuration in the multiple sets of semi-static scheduling configurations, the network device may use the first semi-static scheduling configuration as the semi-static scheduling configuration to be activated. In another possible case, if the network device can determine that the time interval is different from the semi-static scheduling period included in any of the multiple sets of semi-static scheduling configurations, the network device may use the semi-static scheduling configuration corresponding to the semi-static scheduling period closest to the time interval as the semi-static scheduling configuration to be activated. For example, if the time interval between the multiple requests determined by the network device is 10 seconds, the semi-static scheduling period included in any of the multiple sets of semi-static scheduling configurations allocated to the terminal is not 10 seconds, but the semi-static scheduling period included in the second semi-static scheduling configuration in the multiple sets of semi-static scheduling configurations is 9.8 seconds, the network device may use the second semi-static scheduling configuration as the semi-static scheduling configuration to be activated. In another possible case, if the network device determines that the time interval is different from the semi-static scheduling period included in any of the multiple sets of semi-static scheduling configurations, a new semi-static scheduling configuration can be created according to the time interval, and the newly created semi-static scheduling configuration is sent to the terminal through RRC signaling as the semi-static scheduling configuration to be activated. Optionally, the network device can also delete the semi-static scheduling configuration originally assigned to the terminal to save resources. Further, after the network device determines the semi-static scheduling configuration to be activated according to the time intervals of multiple requests, and determines that the semi-static scheduling configuration to be activated is not the semi-static scheduling configuration currently used by the terminal and the network device, it can instruct the terminal to activate the semi-static scheduling configuration to be activated.

[0065] As an optional method, each of the multiple sets of semi-static scheduling configurations allocated by the network device to the terminal has a corresponding number, and the network device can instruct the terminal to activate the semi-static scheduling configuration to be activated by sending the number of the semi-static scheduling configuration to be activated to the terminal. As an example, the network device can send a PDCCH signaling containing the number of the semi-static scheduling configuration to be activated to the terminal to instruct the terminal to activate the semi-static scheduling configuration to be activated. Optionally, the network device can also use CS-RNTI to scramble the PDCCH signaling sent to the terminal. Since CS-RNTI is pre-allocated by the network device to the terminal, using CS-RNTI to scramble the PDCCH signaling indicates that this PDCCH signaling is sent to the terminal.

[0066] In some embodiments, before instructing the terminal to activate the semi-static scheduling configuration to be activated, the network device may also instruct the terminal to deactivate the semi-static scheduling configuration currently used by the terminal. For example, the network device may send a PDCCH signaling carrying the terminal and the number of the semi-static scheduling configuration currently used by the network device to the terminal to instruct the terminal to deactivate the semi-static scheduling configuration currently used.

[0067] In order to further understand the semi-static scheduling solution proposed in the present application, the solution of the present application is introduced below in combination with specific scenarios.

[0068] Scenario 1: Uplink data transmission.

[0069] In scenario one, the network device can allocate multiple sets of uplink semi-static scheduling configurations to the terminal when the terminal accesses, and the uplink semi-static scheduling periods included in each set of semi-static configurations are different, and each set of uplink semi-static scheduling configurations corresponds to a number. Optionally, the network device can send multiple sets of uplink semi-static scheduling configurations allocated to it to the terminal through RRC signaling. Further, the network device can monitor the time intervals of multiple scheduling requests sent by the terminal for requesting time-frequency domain resources, and when it is determined that the time intervals between any two scheduling requests adjacent in the time domain are the same among the set number of scheduling requests, the uplink semi-static scheduling configuration to be activated is selected from the multiple sets of uplink semi-static scheduling configurations according to the time interval. The specific process of determining the uplink semi-static scheduling configuration to be activated according to the time interval can be found in the introduction of the above embodiment, and will not be repeated here. Further, the network device can instruct the terminal to activate the uplink semi-static scheduling configuration to be activated, for example, by sending a PDCCH signaling carrying the number of the uplink semi-static scheduling configuration to be activated.

[0070] In some embodiments, after the network device activates a set of uplink semi-static scheduling for the first time, it will continue to detect the time interval between scheduling requests from the terminal. When it is determined that the time interval between any two scheduling requests that are adjacent in the time domain among the set number of scheduling requests is the same, a set is selected from the pre-configured multiple sets of uplink semi-static scheduling configurations according to the time interval, and then it is determined whether the set of uplink semi-static scheduling configuration is the same as the uplink semi-static scheduling configuration currently used by the terminal. If they are the same, no operation is performed. If they are not the same, the set of uplink semi-static scheduling configuration is used as the new uplink semi-static scheduling configuration to be activated. Further, the network device can first instruct the terminal to deactivate the currently used uplink semi-static scheduling configuration, and then instruct the terminal to activate the newly determined uplink semi-static scheduling configuration to be activated. The terminal can periodically transmit uplink data at the set resource location according to the uplink semi-static scheduling period in the newly activated uplink semi-static scheduling.

[0071] In some embodiments, if the network device does not receive PUSCH signaling from the terminal within a set time length, it may also instruct the terminal to deactivate the currently used uplink semi-static scheduling configuration. For example, when the network device periodically receives PUSCH signaling at the corresponding time-frequency domain resource position according to the period included in the currently used uplink semi-static scheduling configuration, and does not receive PUSCH signaling for multiple times (that is, the results of multiple times are discontinuous transmission (DTX)), the network device may instruct the terminal to deactivate the currently used uplink semi-static scheduling configuration.

[0072] For easier understanding, see Figure 3 , the uplink semi-static scheduling method process in scenario one is introduced with a specific implementation example.

[0073] 301. The network device continues to receive scheduling requests from the terminal.

[0074] 302. The network device determines that the time intervals between any two scheduling requests that are adjacent in the time domain among multiple scheduling requests are the same.

[0075] Optionally, the network device may preset the number of scheduling requests. For example, the network device sets the number of scheduling requests to be received after 10 scheduling requests are received and the time intervals between any two scheduling requests that are adjacent in the time domain among the 10 scheduling requests are the same.

[0076] 303 , the network device determines an uplink semi-persistent scheduling configuration to be activated from a plurality of uplink semi-persistent scheduling configurations pre-allocated to the terminal according to a time interval.

[0077] The multiple sets of uplink semi-static scheduling configurations may be allocated by the network device to the terminal when the terminal accesses. Each set of uplink semi-static scheduling configurations has a corresponding number, and the uplink semi-static scheduling periods included in each set of uplink semi-static scheduling configurations are different.

[0078] Optionally, if the time interval is the same as the uplink semi-static scheduling period included in a set of configurations among the multiple sets of uplink semi-static scheduling configurations, the set of uplink semi-static scheduling configurations is used as the uplink semi-static scheduling configuration to be activated. If the time interval is different from the uplink semi-static scheduling period included in any of the multiple sets of configurations, the uplink semi-static scheduling configuration corresponding to the uplink semi-static scheduling period closest to the time interval can be selected as the uplink semi-static scheduling configuration to be activated.

[0079] 304 , the network device determines whether the uplink semi-static scheduling configuration to be activated is the same as the uplink semi-static scheduling configuration currently used by the terminal.

[0080] If they are the same, the network device does not perform any operation.

[0081] If not the same, continue to step 305.

[0082] 305. The network device instructs the terminal to deactivate the currently adopted uplink semi-static scheduling configuration.

[0083] Specifically, the network device may send a PDCCH signaling scrambled with a CS-RNTI to the terminal, in which the PDCCH signaling carries the number of the currently adopted uplink semi-persistent scheduling configuration.

[0084] 306. The network device instructs the terminal to activate the uplink semi-static scheduling configuration to be activated.

[0085] Specifically, the network device may send a PDCCH signaling scrambled with a CS-RNTI to the terminal, wherein the PDCCH signaling carries the number of the uplink semi-persistent scheduling configuration to be activated.

[0086] Scenario 2: Downlink data transmission.

[0087] In scenario two, the network device may allocate multiple sets of downlink semi-static scheduling configurations to the terminal when the terminal accesses. For details, please refer to the introduction in the above scenario one, which will not be repeated here. Further, the network device may count the time interval of the update request generated when the downlink data is generated, and the update request is used to instruct the network device to update the downlink data to be sent. As an example, the update request may be sent by the Radio Link Control (Radio Link Control, RLC) layer in the network device to the Media Access Control (Media Access Control, MAC) layer of the network device when the downlink data needs to be transmitted, and is used to instruct the MAC layer to update the downlink data to be transmitted. The network device (or the MAC layer of the network device) can count the time intervals of multiple update requests. When it is determined that the time intervals between any two update requests that are adjacent in the time domain in the set number of update requests are the same, the downlink semi-static scheduling configuration to be activated can be determined from the multiple sets of downlink semi-static scheduling configurations pre-allocated to the terminal according to the time interval. The specific process of determining the downlink semi-static scheduling configuration to be activated can refer to the introduction in the above scenario one, which will not be repeated here.

[0088] Further, the network device may determine whether the determined downlink semi-static scheduling configuration to be activated is the same as the downlink semi-static scheduling configuration currently used by the terminal. If they are not the same, the network device may first instruct the terminal to deactivate the currently used downlink semi-static scheduling configuration, and then instruct the terminal to activate the determined downlink semi-static scheduling configuration to be activated. The specific activation and deactivation process can be referred to the introduction in the above embodiment, which will not be repeated here.

[0089] In some embodiments, if the MAC layer of the network device does not receive an update request from the RLC layer within a set time period, it may also instruct the terminal to deactivate the currently used downlink semi-static scheduling configuration.

[0090] Below, see Figure 4 , is a flowchart of a method for downlink semi-static scheduling in scenario 2 provided in an embodiment of the present application. Figure 4 The method of downlink semi-static scheduling will be introduced in combination with various layers of network equipment, including:

[0091] 401. The MAC layer continues to receive update requests from the RLC layer.

[0092] The update request is used to instruct the MAC layer to update the downlink data to be transmitted.

[0093] 402. The MAC layer determines that the time intervals between any two adjacent requests in the time domain among the multiple update requests are the same.

[0094] Optionally, the MAC layer may predefine the number of update requests received. For example, the MAC layer is set to receive 10 update requests from the RLC layer, and the time intervals between any two update requests adjacent in the time domain among the 10 update requests are the same.

[0095] 403. The MAC layer determines, according to a time interval, a downlink semi-persistent scheduling configuration to be activated from a plurality of downlink semi-persistent scheduling configurations pre-allocated to the terminal.

[0096] The specific process can be found in the above Figure 3 Step 303 in the above will not be described in detail here.

[0097] 404. The MAC layer determines whether the downlink semi-persistent scheduling configuration to be activated is the same as the downlink semi-persistent scheduling configuration currently used by the terminal.

[0098] If they are the same, the MAC layer does not perform any operation.

[0099] If not the same, continue to step 405.

[0100] 405. The MAC layer instructs the terminal to deactivate the currently used downlink semi-static scheduling configuration.

[0101] See above for details Figure 3 Step 305 in the above will not be described in detail here.

[0102] 406. The MAC layer instructs the terminal to activate the downlink semi-persistent scheduling configuration to be activated.

[0103] See above for details Figure 3Step 306 in the above process will not be described in detail here.

[0104] Based on the same concept as the above method, see Figure 5 The embodiment of the present application further provides a device 500 for implementing a semi-static scheduling method. The device 500 can perform each step in the above method, which will not be described in detail here to avoid repetition. The device 500 includes: a determination module 501 and an indication module 502.

[0105] A determination module 501, configured to determine a configuration of the semi-static scheduling to be activated from multiple semi-static scheduling configurations pre-allocated to the terminal according to a time interval of at least two requests, wherein the configuration of the semi-static scheduling to be activated is different from the configuration of the semi-static scheduling currently adopted by the network device and the terminal; the multiple requests are used to instruct the network device to update the data to be sent or the multiple requests are used to instruct the network device to allocate time-frequency resources; the time interval is the time interval between any two requests in the multiple requests that are adjacent in the time domain, and the time interval between any two requests in the multiple requests that are adjacent in the time domain is the same;

[0106] The indication module 502 is used to indicate to the terminal to activate the configuration of the semi-persistent scheduling to be activated.

[0107] In some embodiments, when the multiple requests are used to instruct the network device to allocate time-frequency resources, the multiple requests are received from the terminal, and the instructing module 502 is further used to:

[0108] When no physical shared channel PUSCH signaling is received from the terminal within a set time period, the terminal is instructed to deactivate the currently adopted semi-static scheduling configuration.

[0109] In some embodiments, when the multiple requests are used to instruct the network device to update the data to be sent, the multiple requests are generated by the network device in the process of generating the data to be sent, and the indication module 502 is further used to:

[0110] When the data to be sent is not generated within a set time period, instructing the terminal to deactivate the configuration of the currently adopted semi-static scheduling.

[0111] In some embodiments, each of the multiple semi-static scheduling configurations includes a period of each semi-static scheduling, and each of the semi-static scheduling configurations corresponds to a number, which is used to indicate activation of the corresponding semi-static scheduling configuration.

[0112] In some embodiments, the determining module 501 is specifically configured to:

[0113] If the time interval is the same as a period of semi-static scheduling included in a first semi-static scheduling configuration among the multiple semi-static scheduling configurations, taking the first semi-static scheduling configuration as the semi-static scheduling configuration to be activated;

[0114] If the time interval is different from the multiple semi-static scheduling periods included in the multiple semi-static scheduling configurations, the second semi-static scheduling configuration is used as the configuration of the semi-static scheduling to be activated; the semi-static scheduling period included in the second semi-static scheduling configuration is the semi-static scheduling period among the multiple semi-static scheduling periods that is closest to the time interval.

[0115] In some embodiments, before instructing the terminal to activate the configuration of the semi-persistent scheduling to be activated, the instructing module 502 is further configured to:

[0116] Instruct the terminal to deactivate the currently adopted semi-persistent scheduling configuration.

[0117] Figure 6 The electronic device 600 in the embodiment of the present application may further include a communication interface 603, which is, for example, a network port, through which the electronic device can transmit data. For example, the communication interface 603 can implement the above Figure 5 Part of the functions of the indication module 502 in.

[0118] In the embodiment of the present application, the memory 602 stores instructions that can be executed by at least one controller 601. The at least one controller 601 can be used to execute each step in the above method by executing the instructions stored in the memory 602. For example, the controller 601 can implement the above Figure 5 The functions of the determination module 501 and part of the functions of the indication module 502.

[0119] Among them, the controller 601 is the control center of the electronic device, which can use various interfaces and lines to connect various parts of the entire electronic device, by running or executing instructions stored in the memory 602 and calling data stored in the memory 602. Optionally, the controller 601 may include one or more processing units, and the controller 601 may integrate an application controller and a modem controller, wherein the application controller mainly processes the operating system and application programs, etc., and the modem controller mainly processes wireless communications. It is understandable that the above-mentioned modem controller may not be integrated into the controller 601. In some embodiments, the controller 601 and the memory 602 may be implemented on the same chip, and in some embodiments, they may also be implemented separately on independent chips.

[0120] The controller 601 may be a general controller, such as a central processing unit (CPU), a digital signal controller, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general controller may be a microcontroller or any conventional controller, etc. The steps performed by the data statistics platform disclosed in the embodiments of the present application may be performed directly by a hardware controller, or performed by a combination of hardware and software modules in the controller.

[0121] The memory 602 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules. The memory 602 may include at least one type of storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory, a random access memory (Random Access Memory, RAM), a static random access memory (Static Random Access Memory, SRAM), a programmable read-only memory (Programmable Read Only Memory, PROM), a read-only memory (Read Only Memory, ROM), an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a magnetic memory, a disk, an optical disk, etc. The memory 602 is any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory 602 in the embodiment of the present application can also be a circuit or any other device that can realize a storage function, for storing program instructions and / or data.

[0122] By designing and programming the controller 601, for example, the code corresponding to the training method of the neural network model introduced in the aforementioned embodiment can be solidified into the chip, so that the chip can execute the steps of the aforementioned neural network model training method during operation. How to design and program the controller 601 is a technology well known to those skilled in the art and will not be repeated here.

[0123] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0124] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a controller of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the controller of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0125] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0126] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0127] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present application.

[0128] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A semi-static scheduling method, characterized in that: include: The network device determines a semi-static scheduling configuration to be activated from a plurality of semi-static scheduling configurations pre-allocated to a terminal according to a time interval of a plurality of requests, wherein each of the plurality of semi-static scheduling configurations includes a semi-static scheduling period and time-frequency domain resources allocated to the terminal; the semi-static scheduling configuration to be activated is different from the semi-static scheduling configuration currently adopted by the network device and the terminal; the plurality of requests are used to instruct the network device to update data to be sent or the plurality of requests are used to instruct the network device to allocate time-frequency resources; the time interval is the time interval between any two requests in the plurality of requests that are adjacent in the time domain, and the time interval between any two requests in the plurality of requests that are adjacent in the time domain is the same; The network device instructs the terminal to activate the configuration of the semi-persistent scheduling to be activated.

2. The method according to claim 1, characterized in that When the multiple requests are used to instruct the network device to allocate time-frequency resources, the multiple requests are received from the terminal, and the method further includes: When the network device does not receive a physical shared channel PUSCH signaling from the terminal within a set time period, it instructs the terminal to deactivate the currently adopted semi-static scheduling configuration.

3. The method according to claim 1, characterized in that When the multiple requests are used to instruct the network device to update the data to be sent, the multiple requests are generated by the network device in the process of generating the data to be sent, and the method further includes: When the network device does not generate the data to be sent within a set time period, it instructs the terminal to deactivate the configuration of the currently adopted semi-static scheduling.

4. The method according to any one of claims 1 to 3, characterized in that: Each of the multiple semi-static scheduling configurations includes a period of each semi-static scheduling, and each of the semi-static scheduling configurations corresponds to a number, and the number is used to indicate activation of the corresponding semi-static scheduling configuration.

5. The method according to claim 4, characterized in that Determining a semi-static scheduling configuration to be activated from a plurality of semi-static scheduling configurations pre-allocated to a terminal according to a plurality of requested time intervals, comprising: If the time interval is the same as a period of semi-static scheduling included in a first semi-static scheduling configuration among the multiple semi-static scheduling configurations, taking the first semi-static scheduling configuration as the semi-static scheduling configuration to be activated; If the time interval is different from the multiple semi-static scheduling periods included in the multiple semi-static scheduling configurations, the second semi-static scheduling configuration is used as the configuration of the semi-static scheduling to be activated; the semi-static scheduling period included in the second semi-static scheduling configuration is the semi-static scheduling period among the multiple semi-static scheduling periods that is closest to the time interval.

6. A semi-static scheduling device, characterized in that: include: A determination module, configured to determine a semi-static scheduling configuration to be activated from a plurality of semi-static scheduling configurations pre-allocated to a terminal according to a time interval of a plurality of requests, wherein each of the plurality of semi-static scheduling configurations includes a semi-static scheduling period and time-frequency domain resources allocated to the terminal; the semi-static scheduling configuration to be activated is different from the semi-static scheduling configuration currently adopted by the device and the terminal; the plurality of requests are used to instruct the device to update data to be sent or the plurality of requests are used to instruct the device to allocate time-frequency resources; the time interval is a time interval between any two requests in the plurality of requests that are adjacent in the time domain, and the time interval between any two requests in the plurality of requests that are adjacent in the time domain is the same; The indication module is used to indicate to the terminal to activate the configuration of the semi-static scheduling to be activated.

7. The device according to claim 6, characterized in that When the multiple requests are used to instruct the device to allocate time-frequency resources, the multiple requests are received from the terminal, and the instructing module is further used to: When no physical shared channel PUSCH signaling is received from the terminal within a set time period, the terminal is instructed to deactivate the currently adopted semi-static scheduling configuration.

8. The device according to claim 6, characterized in that When the multiple requests are used to instruct the device to update the data to be sent, the multiple requests are generated by the device in the process of generating the data to be sent, and the instructing module is further used to: When the data to be sent is not generated within a set time period, instructing the terminal to deactivate the configuration of the currently adopted semi-static scheduling.

9. The device according to any one of claims 6 to 8, characterized in that: Each of the multiple semi-static scheduling configurations includes a period of each semi-static scheduling, and each of the semi-static scheduling configurations corresponds to a number, and the number is used to indicate activation of the corresponding semi-static scheduling configuration.

10. The device according to claim 9, characterized in that The determination module is specifically used for: If the time interval is the same as a period of semi-static scheduling included in a first semi-static scheduling configuration among the multiple semi-static scheduling configurations, taking the first semi-static scheduling configuration as the semi-static scheduling configuration to be activated; If the time interval is different from the multiple semi-static scheduling periods included in the multiple semi-static scheduling configurations, the second semi-static scheduling configuration is used as the configuration of the semi-static scheduling to be activated; the semi-static scheduling period included in the second semi-static scheduling configuration is the semi-static scheduling period among the multiple semi-static scheduling periods that is closest to the time interval.

Images