Semi-static scheduling methods, user equipment, base stations and communication systems

Abstract

This application provides a semi-static scheduling method, user equipment, base station, and communication system. In this method, the user equipment receives first configuration information of an SPS resource configuration pool sent by the base station, including one or more SPS resource configuration information and an index number corresponding to each SPS resource configuration information, as well as second configuration information indicating at least one index number in the SPS resource configuration pool and the order of the at least one index number. This allows the user equipment to determine the SPS resource configuration information corresponding to at least one index number based on the first and second configuration information. In this way, the user equipment can repeatedly receive data scheduled by the base station through SPS resources by using the SPS resources corresponding to the SPS resource configuration information corresponding to at least one index number in the order indicated by the second configuration information, so that the SPS resources are matched with services with periodic characteristics.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a semi-static scheduling method, user equipment, base station and communication system. Background Technology

[0002] Semi-Persistent Scheduling (SPS), also known as semi-persistent or semi-permanent scheduling, differs from dynamic scheduling. Dynamic scheduling involves the base station (gNB) allocating radio resources to the user equipment (UE) once per scheduling period (e.g., TTI) via the Physical Downlink Control Channel (PDCCH). SPS allows for semi-static configuration of radio resources, periodically allocating these resources to a specific UE—a one-time allocation for multiple uses. This eliminates the need for the gNB to configure radio resources for the UE in every TTI, thus reducing PDCCH overhead. Therefore, SPS is well-suited for services with periodic characteristics, such as extended reality (XR) services.

[0003] However, since the time-frequency resource configuration information corresponding to the existing SPS resources is fixed, meaning the size of the SPS resources called in each TTI is constant, while the size of the data frames transmitted in each cycle of the XR service is different, a mismatch occurs between the SPS resources and the XR service data frames. This mismatch leads to a waste of resources such as UE power consumption and base station system capacity. Summary of the Invention

[0004] To address the aforementioned technical issues, this application provides a semi-static scheduling method, user equipment, base station, and communication system, aiming to match the resource allocation of semi-static scheduling with the diversified wireless resource demands of services with periodic characteristics, thereby reducing user equipment power consumption and avoiding a reduction in base station system capacity.

[0005] In a first aspect, this application provides a semi-static scheduling method. The method is applied to a user equipment and includes: receiving first configuration information from a base station, the first configuration information including a semi-static scheduling SPS resource configuration pool, the SPS resource configuration pool including one or more SPS resource configuration information and an index number corresponding to each SPS resource configuration information; receiving second configuration information from the base station, the second configuration information indicating at least one index number in the SPS resource configuration pool and the order of the at least one index number; determining SPS resource configuration information corresponding to the at least one index number based on the first configuration information and the second configuration information; sequentially using the SPS resources corresponding to the SPS resource configuration information corresponding to the at least one index number to receive data scheduled by the base station through SPS resources; after receiving data using the SPS resources corresponding to the SPS resource configuration information corresponding to the last of the at least one index number, repeatedly sequentially using the SPS resources corresponding to the SPS resource configuration information corresponding to the at least one index number to receive data scheduled by the base station through SPS resources. Therefore, the user equipment can repeatedly receive data scheduled by the base station through SPS resources by using the SPS resources corresponding to the SPS resource configuration information corresponding to at least one index number in the order indicated by the second configuration information, so that the SPS resources are matched with the data frames of XR services, thereby reducing the power consumption of the user equipment and avoiding reducing the system capacity of the base station.

[0006] According to the first aspect, the second configuration information is carried in the downlink control information (DCI).

[0007] According to the first aspect, or any implementation of the first aspect above, the SPS resource configuration information includes SPS frequency domain resource configuration information; the second configuration information is carried in the frequency domain resource configuration FDRA field of the DCI.

[0008] According to the first aspect, or any implementation of the first aspect above, the SPS resource configuration information includes SPS time-domain resource configuration information; the second configuration information is carried in the DCI time-domain resource configuration TDRA field.

[0009] According to the first aspect, or any implementation of the first aspect above, the SPS resource configuration information includes SPS modulation and coding scheme resource configuration information; the second configuration information is carried in the modulation and coding scheme MCS field in the DCI.

[0010] According to the first aspect, or any implementation thereof, the SPS resource configuration pool also includes public SPS resource configuration information; wherein, the public SPS resource configuration information includes at least one or more SPS time-frequency resource configuration information. Therefore, by introducing public SPS resource configuration information, it is possible to select SPS resources corresponding to different sizes of public SPS resource configuration information based on the SPS resources corresponding to the SPS resource configuration information, thereby achieving the scheduling of SPS resources of different sizes and better adapting to the diversified needs of services with periodic characteristics for wireless resources.

[0011] According to the first aspect, or any implementation of the first aspect above, the method further includes: receiving enabling information from the base station, wherein the enabling information is used to instruct the user equipment to detect whether there is a demodulation reference signal (DMRS) of the user equipment in the SPS resources corresponding to the public SPS resource configuration information during each SPS scheduling cycle. Thus, the use of the SPS resources corresponding to the public SPS resource configuration information can be dynamically realized through the enabling information.

[0012] According to the first aspect, or any implementation of the first aspect above, after receiving the enable information from the base station, the method further includes: detecting whether there is a user equipment DMRS in the SPS resources corresponding to the public SPS resource configuration information in each SPS scheduling cycle; when the user equipment DMRS is detected in the SPS resources corresponding to the public SPS resource configuration information in each SPS scheduling cycle, receiving the data scheduled by the base station through the SPS resources corresponding to the public SPS resource configuration information.

[0013] According to the first aspect, or any implementation thereof, a third configuration information is sent to the base station. This third configuration information indicates at least one index number in the SPS resource configuration pool, and the order of these index numbers. Data is then sent to the base station sequentially using the SPS resources corresponding to the SPS resource configuration information corresponding to the at least one index number. Thus, the base station can repeatedly receive data scheduled by the user equipment using the SPS resources corresponding to the SPS resource configuration information corresponding to the at least one index number, following the order indicated by the third configuration information. This matches the SPS resources with the data frames of the XR service, thereby reducing the power consumption of the user equipment and avoiding a reduction in the system capacity of the base station.

[0014] According to the first aspect, or any of the above implementations of the first aspect, the third configuration information is carried in the configuration authorization uplink control information CG-UCI.

[0015] According to the first aspect, or any implementation of the first aspect above, when the SPS resource configuration information includes SPS frequency domain resource configuration information, the third configuration information is carried in the frequency domain resource configuration field of CG-UCI; or, when the SPS resource configuration information includes SPS time domain resource configuration information, the third configuration information is carried in the time domain resource configuration field of CG-UCI; or, when the SPS resource configuration information includes SPS modulation and coding scheme resource configuration information, the third configuration information is carried in the modulation configuration coding field of CG-UCI; or, when the SPS resource configuration information includes SPS time-frequency resource configuration information, the third configuration information is carried in the time-frequency resource configuration field of CG-UCI.

[0016] Secondly, this application provides a semi-static scheduling method. The method is applied to a base station and includes: sending first configuration information to a user equipment, the first configuration information including a semi-static scheduling SPS resource configuration pool, the SPS resource configuration pool including one or more SPS resource configuration information and an index number corresponding to each SPS resource configuration information; and sending second configuration information to the user equipment, the second configuration information indicating at least one index number in the SPS resource configuration pool and the order of the at least one index number.

[0017] According to the second aspect, the SPS resource configuration pool also includes public SPS resource configuration information; wherein, the public SPS resource configuration information includes at least one or more SPS time-frequency resource configuration information.

[0018] According to the second aspect, or any implementation of the second aspect above, the method further includes: sending enable information to the user equipment, the enable information being used to instruct the user equipment to detect whether there is a demodulation reference signal (DMRS) of the user equipment in the SPS resource corresponding to the public SPS resource configuration information during each SPS scheduling cycle.

[0019] According to the second aspect, or any implementation of the second aspect above, after sending the enable information to the user equipment, the method further includes: adding the user equipment's DMRS to the SPS resource corresponding to the public SPS resource configuration information.

[0020] According to the second aspect, or any implementation of the second aspect above, the method further includes: receiving third configuration information from a user equipment, the third configuration information indicating at least one index number in an SPS resource configuration pool, and the order of the at least one index number; determining SPS resource configuration information corresponding to the at least one index number based on the first configuration information and the third configuration information; sequentially using the SPS resources corresponding to the SPS resource configuration information corresponding to the at least one index number to receive data scheduled by the user equipment through SPS resources; and after receiving data using the SPS resources corresponding to the SPS resource configuration information corresponding to the last index number among the at least one index number, repeatedly sequentially using the SPS resources corresponding to the SPS resource configuration information corresponding to the at least one index number to receive data scheduled by the user equipment through SPS resources.

[0021] The second aspect and any implementation thereof correspond to the first aspect and any implementation thereof, respectively. The technical effects of the second aspect and any implementation thereof are similar to those of the first aspect and any implementation thereof, and will not be repeated here.

[0022] Thirdly, this application provides a semi-static scheduling method. This method is applied to a user equipment and includes: receiving fourth configuration information from a base station, the fourth configuration information including a semi-static scheduling SPS resource configuration pool, the SPS resource configuration pool including one or more SPS resource configuration information and an index number corresponding to each SPS resource configuration information; receiving fifth configuration information from the base station, the fifth configuration information including an SPS resource activation pool, the SPS resource activation pool including one or more SPS resource configuration queues and an index number corresponding to each SPS resource configuration queue, each SPS resource configuration queue indicating at least one index number in the SPS resource configuration pool, and the order of the at least one index number; and receiving sixth configuration information from the base station, the sixth configuration... The information indicates the index number corresponding to an SPS resource configuration queue in the SPS resource activation pool; based on the fourth, fifth, and sixth configuration information, the SPS resource configuration information corresponding to at least one index number is determined; the SPS resource corresponding to the SPS resource configuration information corresponding to at least one index number is used sequentially to receive data scheduled by the base station through SPS resources; after using the SPS resource corresponding to the SPS resource configuration information corresponding to the last index number among the at least one index number to receive data, the data scheduled by the base station through SPS resources corresponding to the SPS resource configuration information corresponding to at least one index number is used sequentially again. Therefore, by introducing the SPS resource activation pool, at least one index number in the SPS resource configuration pool, and its order, is configured into the SPS resource configuration queues within the SPS resource activation pool. Thus, based on the index number of an SPS resource configuration queue, at least one index number in the SPS resource configuration pool, and its order, can be determined, thereby making it applicable to more service scenarios.

[0023] In addition, when the user equipment receives both the fourth and fifth configuration information, the content indicated by the sixth configuration information sent by the base station can be the index number corresponding to an SPS resource configuration queue in the SPS resource activation pool. In this way, the same field can be used to achieve the cyclic use of more SPS cycles, thus making it applicable to more service scenarios.

[0024] According to the third aspect, determining the SPS resource configuration information corresponding to at least one index number based on the fourth configuration information, the fifth configuration information, and the sixth configuration information includes: determining the SPS resource configuration queue in the SPS resource activation pool corresponding to the index number indicated by the sixth configuration information based on the fifth configuration information and the sixth configuration information; and determining the SPS resource configuration information corresponding to at least one index number based on the fourth configuration information and the determined SPS resource configuration queue.

[0025] According to the third aspect, the sixth configuration information is carried in the downlink control information (DCI).

[0026] According to the third aspect, or any of the above implementations of the third aspect, the SPS resource configuration information includes SPS frequency domain resource configuration information; the sixth configuration information is carried in the frequency domain resource configuration FDRA field of the DCI.

[0027] According to the third aspect, or any of the above implementations of the third aspect, the SPS resource configuration information includes the SPS time-domain resource configuration information; the sixth configuration information is carried in the DCI time-domain resource configuration TDRA field.

[0028] According to the third aspect, or any of the above implementations of the third aspect, the SPS resource configuration information includes SPS modulation and coding scheme resource configuration information; the sixth configuration information is carried in the modulation and coding scheme MCS field in the DCI.

[0029] According to the third aspect, or any implementation of the third aspect above, the SPS resource configuration pool also includes public SPS resource configuration information; wherein, the public SPS resource configuration information includes at least one or more SPS time-frequency resource configuration information. Therefore, by introducing public SPS resource configuration information, it is possible to select SPS resources corresponding to different sizes of public SPS resource configuration information based on the SPS resources corresponding to the SPS resource configuration information, thereby achieving the scheduling of SPS resources of different sizes and better adapting to the diversified needs of services with periodic characteristics for wireless resources.

[0030] According to the third aspect, or any implementation of the third aspect above, the method further includes: receiving enabling information from the base station, wherein the enabling information is used to instruct the user equipment to detect whether there is a demodulation reference signal (DMRS) of the user equipment in the SPS resources corresponding to the public SPS resource configuration information during each SPS scheduling cycle. Thus, the use of the SPS resources corresponding to the public SPS resource configuration information can be dynamically realized through the enabling information.

[0031] According to the third aspect, or any implementation of the third aspect above, after receiving the enable information from the base station, the method further includes: detecting whether there is a user equipment DMRS in the SPS resources corresponding to the public SPS resource configuration information in each SPS scheduling cycle; when the user equipment DMRS is detected in the SPS resources corresponding to the public SPS resource configuration information in each SPS scheduling cycle, receiving the data scheduled by the base station through the SPS resources corresponding to the public SPS resource configuration information.

[0032] According to the third aspect, or any implementation of the third aspect above, a seventh configuration information is sent to the base station. This seventh configuration information indicates at least one index number in the SPS resource configuration pool, and the order of these index numbers. Data is then sent to the base station sequentially using the SPS resources corresponding to the SPS resource configuration information corresponding to the at least one index number. Thus, the base station can repeatedly receive data scheduled by user equipment using SPS resources according to the order indicated by the seventh configuration information, matching the SPS resources with the data frames of XR services. This reduces user equipment power consumption and avoids reducing the base station's system capacity.

[0033] According to the third aspect, or any of the above implementations of the third aspect, the seventh configuration information is carried in the uplink control information CG-UCI of the configuration authorization.

[0034] According to the third aspect, or any implementation of the third aspect above, when the SPS resource configuration information includes SPS frequency domain resource configuration information, the seventh configuration information is carried in the frequency domain resource configuration field of CG-UCI; or, when the SPS resource configuration information includes SPS time domain resource configuration information, the seventh configuration information is carried in the time domain resource configuration field of CG-UCI; or, when the SPS resource configuration information includes SPS modulation and coding scheme resource configuration information, the seventh configuration information is carried in the modulation configuration coding field of CG-UCI; or, when the SPS resource configuration information includes SPS time-frequency resource configuration information, the seventh configuration information is carried in the time-frequency resource configuration field of CG-UCI.

[0035] Fourthly, this application provides a semi-static scheduling method. This method is applied to a base station and includes: sending fourth configuration information to a user equipment (UE), the fourth configuration information including a semi-static scheduling SPS resource configuration pool, the SPS resource configuration pool including one or more SPS resource configuration information entries and an index number corresponding to each SPS resource configuration information entry; sending fifth configuration information to the UE, the fifth configuration information including an SPS resource activation pool, the SPS resource activation pool including one or more SPS resource configuration queues and an index number corresponding to each SPS resource configuration queue, each SPS resource configuration queue indicating at least one index number in the SPS resource configuration pool and the order of the at least one index number; and sending sixth configuration information to the UE, the sixth configuration information indicating the index number corresponding to one SPS resource configuration queue in the SPS resource activation pool.

[0036] According to the fourth aspect, the SPS resource configuration pool also includes public SPS resource configuration information; wherein, public SPS resource configuration information includes at least one or more SPS time-frequency resource configuration information.

[0037] According to the fourth aspect, or any implementation of the fourth aspect above, the method further includes: sending enable information to the user equipment, the enable information being used to instruct the user equipment to detect whether there is a demodulation reference signal (DMRS) of the user equipment in the SPS resource corresponding to the public SPS resource configuration information during each SPS scheduling cycle.

[0038] According to the fourth aspect, or any implementation of the fourth aspect above, after sending the enable information to the user equipment, the method further includes: adding the user equipment's DMRS to the SPS resource corresponding to the public SPS resource configuration information.

[0039] According to the fourth aspect, or any implementation of the fourth aspect above, the method further includes: receiving seventh configuration information from the user equipment, the seventh configuration information indicating at least one index number in the SPS resource configuration pool, and the order of the at least one index number; determining SPS resource configuration information corresponding to the at least one index number based on the first configuration information and the seventh configuration information; sequentially using the SPS resources corresponding to the SPS resource configuration information corresponding to the at least one index number to receive data scheduled by the user equipment through the SPS resources; after receiving data using the SPS resources corresponding to the SPS resource configuration information corresponding to the last index number among the at least one index number, repeatedly sequentially using the SPS resources corresponding to the SPS resource configuration information corresponding to the at least one index number to receive data scheduled by the user equipment through the SPS resources.

[0040] The fourth aspect and any implementation thereof correspond to the third aspect and any implementation thereof, respectively. The technical effects of the fourth aspect and any implementation thereof can be found in the technical effects of the third aspect and any implementation thereof, as described above, and will not be repeated here.

[0041] Fifthly, this application provides a user equipment for executing the semi-static scheduling method involved in the first aspect or any implementation of the first aspect; or for executing the semi-static scheduling method involved in the third aspect or any implementation of the third aspect.

[0042] Sixthly, this application provides a base station for executing the semi-static scheduling method involved in the second aspect or any implementation of the second aspect above; or for executing the semi-static scheduling method involved in the fourth aspect or any implementation of the fourth aspect above.

[0043] In a seventh aspect, this application provides a communication system including the user equipment involved in the fifth aspect and the base station involved in the sixth aspect. Attached Figure Description

[0044] Figure 1 This is an example of a communication network architecture;

[0045] Figure 2 This is a schematic diagram of the hardware structure of a user equipment as an example.

[0046] Figure 3 This is a schematic diagram illustrating an example of a mismatch between SPS time-frequency resources and XR service frames;

[0047] Figure 4 One of the timing diagrams for setting SPS time-frequency resources based on the semi-static scheduling method provided in the embodiments of this application is shown as an example;

[0048] Figure 5 This is one of the exemplary schematic diagrams showing the matching of SPS time-frequency resources and XR service frames;

[0049] Figure 6 This is a second timing diagram illustrating the semi-static scheduling method based on the embodiments of this application, which uses SPS time-frequency resources.

[0050] Figure 7 This is the second illustrative diagram showing the matching of SPS time-frequency resources and XR service frames;

[0051] Figure 8 The third illustration is a schematic diagram of SPS time-frequency resource and XR service frame matching as an example.

[0052] Figure 9 The fourth illustration is a schematic diagram of SPS time-frequency resource and XR service frame matching as an example.

[0053] Figure 10 The third timing diagram illustrating the semi-static scheduling method based on the embodiments of this application, which sets up SPS time-frequency resources, is shown as an example.

[0054] Figure 11 This is an illustrative diagram illustrating the changes in user perspective in an XR business scenario.

[0055] Figure 12 The fourth timing diagram illustrating the semi-static scheduling method based on the embodiments of this application, which sets up SPS time-frequency resources, is shown as an example.

[0056] Figure 13 The fifth timeline diagram illustrating the semi-static scheduling method based on the embodiments of this application, which sets up SPS time-frequency resources, is shown as an example.

[0057] Figure 14The timing diagram shown is the sixth example of the semi-static scheduling method based on the embodiments of this application, which sets up SPS time-frequency resources.

[0058] Figure 15 This is one of the timing diagrams of a semi-static scheduling method provided in an embodiment of this application, as illustrated by example.

[0059] Figure 16 This is a second timing diagram illustrating the semi-static scheduling method provided in an embodiment of this application. Detailed Implementation

[0060] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0061] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0062] The terms "first" and "second," etc., used in the specification and claims of this application are used to distinguish different objects, not to describe a specific order of objects. For example, "first target object" and "second target object," etc., are used to distinguish different target objects, not to describe a specific order of target objects.

[0063] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0064] In the description of the embodiments in this application, unless otherwise stated, "multiple" means two or more. For example, multiple processing units means two or more processing units; multiple systems means two or more systems.

[0065] Before describing the technical solutions of the embodiments of this application, examples of communication systems to which the embodiments of this application can be applied will be given first.

[0066] For example, embodiments of this application may be applied to, but are not limited to, the following communication systems: Narrowband-Internet of Things (NB-IoT) systems, Wireless Local Access Network (WLAN) systems, Long Term Evolution (LTE) systems, Vehicle-to-X (V2X) wireless communication systems, 5th Generation Mobile Networks or 5th Generation Wireless Systems (5G), also known as New Radio (NR) systems, or communication systems after 5G, such as 6G systems, Device-to-Device (D2D) communication systems, etc.

[0067] To facilitate understanding of the communication network architecture of the above communication system, the following is combined with... Figure 1 The communication network architecture of the communication system to which the embodiments of this application are applicable will be described.

[0068] For example, Figure 1Taking the network service architecture of a 5G system as an example, this paper illustrates the interaction relationship between network functions and entities, as well as the corresponding interfaces. The service-based architecture (SBA) of the 3rd Generation Partnership Project (3GPP) of this 5G system mainly includes the following network functions and entities: User Equipment (UE), Access Network (AN) or Radio Access Network (RAN), User Plane Function (UPF), Data Network (DN), Access Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Policy Control Function (PCF), Application Function (AF), Network Slice Selection Function (NSSF), Unified Data Management (UDM), Network Exposure Function (NEF), and Network Repository Function (NRF).

[0069] Among them, UE, AN / RAN, UPF, and DN are generally referred to as user plane network functions and entities (or user plane network elements), while the others are generally referred to as control plane network functions and entities (or control plane network elements). Control plane network elements are defined by 3GPP as processing functions within a network. Control plane network elements have functional behaviors and interfaces defined by 3GPP. Network functions can be implemented as network elements running on proprietary hardware, software instances running on proprietary hardware, or virtual functions instantiated on a suitable platform, such as those implemented in a cloud infrastructure.

[0070] The main functions of each network element are described in detail below.

[0071] AN / RAN: AN / RAN can be various types of base stations, such as macro base stations, micro base stations (also known as "small stations"), and distributed unit-control units (DU-CUs). Additionally, these base stations can also be radio controllers in Cloud Radio Access Network (CRAN) scenarios, or relay stations, access points, vehicle-mounted equipment, wearable devices, or network equipment in future evolved Public Land Mobile Network (PLMN) networks. AN / RAN can also be Broadband Network Gateway (BNG), aggregation switches, and non-3GPP access equipment. AN / RAN is primarily responsible for air interface-side radio resource management, uplink and downlink data classification, Quality of Service (QoS) management, data compression and encryption, signaling processing with control plane network elements, and data forwarding with user plane function network elements. This application does not limit the specific form and structure of AN / RAN. For example, in systems employing different radio access technologies, the names of devices with base station functions may differ. For example, a base station can be an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) device in LTE, such as an Evolutionary NodeB (eNB or e-NodeB), or a Next Generation Radio Access Network (NG-RAN) device (such as a gNB) in a 5G system.

[0072] UPF: Primarily responsible for packet routing and forwarding, as well as QoS processing and billing information statistics for user plane data. The transmission resources and scheduling functions that provide services to the UE in UPF are managed and controlled by SMF.

[0073] DN: DN is a network used for transmitting data. For example, DN can be a carrier service network, Internet access, or a third-party service network.

[0074] AMF (Access Controller Function): Primarily responsible for processing control plane messages, such as access control, mobility management, lawful interception, and access authentication / authorization. Specifically, the AMF's functions include: 1) processing access network control plane messages; 2) processing NAS messages, responsible for NAS encryption and integrity protection; 3) registration management; 4) connection management; 5) access management; 6) mobility management; 7) lawful message interception; 8) providing session management messages between the UE and SMF; 9) implementing transparent transmission of routed session management (SM) messages, similar to a transparent proxy; 10) access authentication; 11) access authorization; 12) forwarding SMS messages between the UE and the Short Message Service Function (SMSF); 13) interacting with the AMF and UE to obtain the UE authentication intermediate key; and 14) calculating the access network-specific key.

[0075] SMF: Primarily used for session management, UE Internet Protocol (IP) address allocation and management, selection of manageable user plane functions, policy control and charging function interface endpoints, downlink data notification, etc.

[0076] PCF: Primarily used to provide UE policy rules, AM policy rules, and SM policy rules-related parameters to UE, AMF, or SMF respectively, manage user subscription information, and interface with UDM to access subscription user information related to policy decisions, etc.

[0077] NRF: Primarily used to provide internal / external addressing functions, receive query requests from other network elements for a certain type of network element, and return information about the relevant network element.

[0078] AUSF: Primarily responsible for network security, it generates keys to enable two-way authentication for UEs and supports a unified authentication framework.

[0079] AF: Used to provide services, primarily for: 1) the application impact on business routing; 2) the exposure of network access capabilities; and 3) interacting with the policy framework for policy control. NSSF: Primarily used for the selection and management of Network Slice Instances (NSIs), determining the mapping between allowed and used network slice information, and determining the mapping between configured and subscribed network slice information.

[0080] NEF: It is an interface network element for bidirectional information exchange between internal and external entities in the network. It is also a logical unit for internal information distribution and aggregation. It mainly includes three capabilities: monitoring capability, provisioning capability, and policy / billing capability.

[0081] UDM consists of two parts: the application front-end (FE) and the user data warehouse (UDR).

[0082] The data to be transmitted can be transmitted through the PDU session established between the UE and DN (i.e., the communication bearer described in the specification). The transmission will pass through two network functional entities, (R)AN and UPF. The UE and (R)AN communicate with each other using a certain air interface technology. N1 is the interface between the UE and AMF, N2 is the interface between (R)AN and AMF, N3 is the interface between (R)AN and UPF, N4 is the interface between SMF and UPF, and N6 is the interface between UPF and DN. Namf is the service-based interface presented by AMF, Nsmf is the service-based interface presented by SMF, Nausf is the service-based interface presented by AUSF, Nnssf is the service-based interface presented by NSSF, Nnef is the service-based interface presented by NEF, Nnrf is the service-based interface presented by NRF, Npcf is the service-based interface presented by PCF, Nudm is the service-based interface presented by UDM, and Naf is the service-based interface presented by AF.

[0083] For an introduction to the functions of network elements such as UPF, DN, AUSF, NSSF, NEF, NRF, and UDM, please refer to the explanations and descriptions in conventional technical documents; they will not be elaborated upon here.

[0084] Furthermore, it should be noted that the terms "system" and "network" used in the embodiments of this application can be used interchangeably.

[0085] Furthermore, in this embodiment, the UE can be a desktop device, laptop device, handheld device, wearable device, smart home device, computing device, etc., with wireless connectivity. Examples include netbooks, tablets, AR / VR devices, etc., which will not be listed here.

[0086] Furthermore, the embodiments of this application do not limit the specific type and structure of the UE.

[0087] To facilitate understanding of the UE involved in the technical solutions provided in the embodiments of this application, the following is combined with... Figure 2 The hardware structure of a UE is described.

[0088] For example, in some embodiments, the structure of the UE can be as follows: Figure 2As shown, it includes, for example: processor 210, external memory interface 220, internal memory 221, universal serial bus (USB) interface 230, charging management module 240, power management module 241, battery 242, antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, audio module 270, speaker 270A, receiver 270B, microphone 270C, headphone jack 270D, sensor module 280, button 290, motor 291, indicator 292, camera 293, display screen 294, and subscriber identification module (SIM) card interface 295, etc. The sensor module 280 may include a pressure sensor 280A, a gyroscope sensor 280B, a barometric pressure sensor 280C, a magnetic sensor 280D, an accelerometer sensor 280E, a distance sensor 280F, a proximity sensor 280G, a fingerprint sensor 280H, a temperature sensor 280J, a touch sensor 280K, an ambient light sensor 280L, a bone conduction sensor 280M, etc.

[0089] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the UE. In other embodiments, the UE may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0090] Processor 210 may include one or more processing units, such as application processors (APs), modems, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0091] The charging management module 240 is used to receive charging input from the charger. The charger can be a wireless charger or a wired charger.

[0092] The power management module 241 is used to connect the battery 242, the charging management module 240, and the processor 210. The power management module 241 receives input from the battery 242 and / or the charging management module 240 to power the processor 210, internal memory 221, display 294, camera 293, and wireless communication module 260, etc.

[0093] The UE's wireless communication function can be implemented through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem, and baseband processor.

[0094] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the UE can be used to cover one or more communication frequency bands. Different antennas can also be reused to improve antenna utilization.

[0095] The mobile communication module 250 can provide solutions for wireless communication applications such as 2G / 3G / 4G / 5G on the UE.

[0096] The wireless communication module 260 can provide solutions for wireless communication applications on the UE, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 260 can be one or more devices integrating at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 210. The wireless communication module 260 can also receive signals to be transmitted from processor 210, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0097] In this embodiment, the wireless communication module 260 can be used by the UE to send data frames of the current service to the network node, and to receive data frames sent by the network node.

[0098] The UE implements display functions through the GPU, display screen 294, and application processor. The GPU is a microprocessor for image processing, connecting the display screen 294 and the application processor.

[0099] Display screen 294 is used to display images, videos, etc. A series of graphical user interfaces (GUIs) can be displayed on the UE's display screen 294.

[0100] The UE can achieve shooting functions through ISP, camera 293, video codec, GPU, display 294 and application processor.

[0101] Camera 293 is used to capture still images or videos.

[0102] The external memory interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the UE.

[0103] Internal memory 221 can be used to store computer executable program code, which includes instructions. Processor 210 executes various functional applications and data processing of the UE by running the instructions stored in internal memory 221.

[0104] The UE can implement audio functions through an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headphone jack 270D, and an application processor. Examples include music playback and recording. The UE may also include a pressure sensor 280A, a barometric pressure sensor 280C, a gyroscope sensor 280B, a magnetometer sensor 280D, an accelerometer sensor 280E, a proximity sensor 280F, a proximity light sensor 280G, an ambient light sensor 280L, a fingerprint sensor 280H, a temperature sensor 280J, a touch sensor 280K, a bone conduction sensor 280M, buttons 290, a motor 291, and an indicator 292.

[0105] The SIM card interface 295 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 295 to establish contact with the UE. The UE can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 295 supports Nano SIM cards, Micro SIM cards, and other SIM cards. Multiple cards can be inserted into the same SIM card interface 295 simultaneously. The SIM card interface 295 is also compatible with external memory cards. The UE interacts with the network through the SIM card to perform functions such as calls and data communication.

[0106] In addition, an operating system, such as HarmonyOS, iOS, Android, or Windows, runs on top of the aforementioned components. Applications can be installed and run on this operating system. In some embodiments, multiple operating systems may run within the UE.

[0107] It should be understood that, Figure 2 The hardware modules included in the UE shown are merely illustrative and do not limit the specific structure of the UE. In fact, the UE provided in this application embodiment may also include other hardware modules that interact with the hardware modules shown in the figure, which are not specifically limited here. For example, the UE may also include a flash, a miniature projection device, etc. Furthermore, if the UE is a PC, then the UE may also include components such as a keyboard and a mouse.

[0108] Furthermore, it should be noted that, based on the periodic characteristics of SPS, the technical solutions provided in this application embodiment can be applied to periodic services in the above-mentioned system, such as XR services.

[0109] It should be understood that the descriptions of the business scenarios addressed in all embodiments of this application are for the purpose of facilitating the understanding of the technical solutions provided in this application, and are not intended to limit the business scenarios to which the technical solutions provided in this application are applicable.

[0110] Furthermore, it is understandable that XR refers to all real and virtual combined environments and human-computer interactions generated by computer technology and wearable devices. Representative forms include Augmented Reality (AR), Mixed Reality (MR), and Virtual Reality (VR), as well as interdisciplinary scenarios in between.

[0111] To better understand the technical solutions provided in the embodiments of this application, the following is combined with... Figure 3 This paper provides a detailed explanation of the current mismatch between SPS time-frequency resources and XR service frames.

[0112] Taking VR scenarios within XR services as an example, the video content to be displayed undergoes processing by an encoder and a decoder. Specifically, the encoder encodes multiple images (each frame represents a still image) to generate Group of Pictures (GOPs), and the decoder reads each GOP segment, decodes it, and then renders and displays the resulting image.

[0113] Understandably, a Group of Pictures (GOP) is a group of consecutive frames consisting of one I-frame and several B-frames / P-frames. It is the basic unit accessed by the video image encoder and decoder, and its order will be repeated until the end of the video. I-frames are internally coded frames (also known as keyframes), P-frames are forward prediction frames (forward reference frames / forward difference frames), and B-frames are bidirectional interpolated frames (bidirectional reference frames / bidirectional difference frames).

[0114] Simply put, an I-frame is a complete picture, and decoding only requires the data of this frame (because it contains the complete picture); a P-frame represents the difference between this frame and the previous I-frame (or P-frame). Decoding requires superimposing the previously cached picture with the difference defined in this frame to generate the final picture. That is, a P-frame does not contain complete picture data, but only data on the difference between the picture and the previous frame; a B-frame records the difference between this frame and the frames before and after it. That is, to decode a B-frame, not only must the previously cached picture be obtained, but the following picture must also be decoded. The final picture is obtained by superimposing the data corresponding to the previous and following pictures with the data of this frame.

[0115] Based on this, we can see that I-frames have the largest size, B-frames have the smallest size, and P-frames are between I-frames and B-frames. Figure 3 The XR frame shown is an example. However, once SPS is activated, the time-frequency resource configuration information corresponding to the time-frequency resources scheduled in each scheduling cycle (hereinafter referred to as SPS resources) remains fixed, such as... Figure 3 The time-domain resource size shown in the figure is T1, and the frequency-domain resource size is F1 for each scheduling cycle. Obviously, the current SPS time-frequency resource allocation cannot match the diversified needs of XR services, which will lead to a waste of resources such as UE power consumption and base station system capacity.

[0116] Based on this, in order to solve the above-mentioned problem caused by the mismatch between the time-frequency resources of SPS and the service frames with periodic characteristics, this application provides a semi-static scheduling method. This method configures time-frequency resources of various sizes for SPS, so that SPS can cyclically schedule time-frequency resources of different sizes in each scheduling cycle according to the configuration. This makes the time-frequency resources of SPS match the diversified wireless resource requirements of services with periodic characteristics, thereby reducing the power consumption of user equipment and avoiding reducing the system capacity of the base station.

[0117] Before describing the technical solutions of the embodiments of this application, the methods of uplink SPS and downlink SPS in the existing semi-static scheduling will be explained first.

[0118] For example, for downlink SPS, on the network side, such as the base station (gNB), the UE is first configured with the data transmission period via RRC signaling. Then, the UE is activated with a Physical Downlink Control Channel (PDCCH) scrambled with a Configured Scheduling-RadioNetwork Temporary Identifier (CS-RNTI) (hereinafter referred to as the downlink control channel), and the radio resources for the downlink SPS are specified (hereinafter referred to as downlink SPS resources). Then, in each period, the UE can use the downlink SPS resources to receive the Physical Downlink Shared Channel (PDSCH) (hereinafter referred to as the downlink data channel), and the gNB does not need to retransmit the PDCCH to specify the allocated downlink SPS resources.

[0119] It should be understood that CS-RNTI is used for SPS scheduling and is carried to the UE via RRC signaling. Specifically, when the UE receives the PDCCH sent by the gNB, if the PDCCH is scrambled with CS-RNTI, it indicates that SPS adaptation service needs to be used.

[0120] Next, when it is determined that SPS needs to be used to adapt to services, the startup / activation or release of SPS can be determined by decoding PDCCH.

[0121] For example, if SPS activation is determined based on the decoding result, in this case, the UE decodes the downlink control information (DCI) in the PDCCH corresponding to the first downlink data frame to determine the specific time-frequency resource information of the PDSCH for the gNB to transmit service data (hereinafter referred to as downlink resource information for ease of distinction); then, the UE can obtain the service data transmitted by the gNB by decoding the PDSCH based on the obtained downlink resource information.

[0122] Accordingly, after downlink SPS is activated, for subsequent downlink data frames, the gNB no longer needs to occupy the PDCCH to send DCI to allocate downlink SPS resources for the service data sent by the gNB. Instead, the UE will use the same downlink resource information (downlink resource information when SPS is activated) to decode the PDSCH to obtain subsequent downlink data frames according to the SPS period configured in the RRC signaling.

[0123] It should be noted that the "same downlink resource information" mentioned in this embodiment means that the frequency domain resource size and time domain resource size corresponding to the downlink resource information are the same, and does not limit the starting position to be the same.

[0124] Furthermore, it is understandable that if, in practical applications, the PDCCH is scrambled using the Cell-RadioNetworkTemporaryIdentifier (C-RNTI), it indicates that the current scheduling is normal scheduling, i.e., dynamic scheduling, rather than SPS scheduling.

[0125] For example, there are two methods for uplink SPS, the main difference being the activation method.

[0126] For mode 1, hereinafter referred to as type 1 (Configured grant type 1, CG type 1), all parameters are configured and uplink transmission is activated via RRC signaling. As long as the configuration is successful, DCI activation is not required, and the UE can transmit the Physical Uplink Shared Channel (PUSCH) on the configured periodic uplink resources.

[0127] Scheme 2, hereinafter referred to as Type 2 (Configured grant type 2, CG type 2), involves the network first configuring the data transmission period for the UE via RRC signaling. Then, it activates the uplink SPS using CS-RNTI scrambled PDCCH and specifies radio resources for the uplink SPS (hereinafter referred to as uplink SPS resources). Each period, the UE can then use these uplink SPS resources to transmit PUSCH.

[0128] Specifically, for Type 2, the gNB first sends the DCI via the PDCCH scrambled by CS-RNTI. Correspondingly, the UE decodes the DCI in the PDCCH to determine the specific time-frequency resource information (hereinafter referred to as uplink resource information) in the PUSCH that the gNB specifies for transmitting service data. Then, when the UE needs to send service data to the gNB, it sends the service data to the gNB via the PUSCH based on the obtained uplink resource information.

[0129] Accordingly, after uplink SPS is activated, for subsequent uplink data frames, the gNB no longer needs to occupy the PDCCH to send DCI to allocate uplink SPS resources for the service data sent by the UE. Instead, the UE will use the same uplink resource information (uplink resource information when SPS is activated) according to the SPS period configured in the RRC signaling to send the subsequent uplink data frames to the gNB through the PUSCH.

[0130] It should be noted that the "same uplink resource information" mentioned in this embodiment means that the frequency domain resource size and time domain resource size corresponding to the uplink resource information are the same, and does not limit the starting position to be the same.

[0131] Based on the above description, SPS activation can be divided into activation via DCI and activation via RRC signaling. This application proposes technical solutions for both activation methods.

[0132] Option 1: Time and frequency resource configuration for downlink SPS and uplink SPS activated via CG type 2 (uplink CG type 2).

[0133] For example, both downlink SPS and uplink CG type2 are activated via DCI transmitted by the gNB. DCI contains many fields, such as the Frequency Domain Resource Assignment (FDRA) field for configuring the frequency domain resource size, the Time Domain Resource Assignment (TDRA) field for configuring the time domain resource size, and the Modulation and Coding Scheme (MCS) field for configuring the modulation and coding scheme. These will not be listed here.

[0134] Based on this, this scheme enables the configuration of multiple frequency domain resources that can be cyclically scheduled by reusing the FDRA field in DCI, enables the configuration of multiple time domain resources that can be cyclically scheduled by reusing the TDRA field in DCI, and enables the configuration of multiple modulation and coding schemes that can be cyclically scheduled by reusing the MCS field in DCI.

[0135] For ease of explanation, this application's semi-static scheduling method will be illustrated by taking the example of reusing the FDRA field in DCI to configure multiple frequency domain resources that can be cyclically scheduled, thereby changing the size of SPS radio resources to adapt to different XR service frames.

[0136] See Figure 4 This embodiment includes:

[0137] S101, gNB sends RRC signaling carrying the SPS frequency domain resource configuration pool to UE.

[0138] For example, if the service adapted by SPS is an XR service, then gNB can configure relevant parameters for SPS based on the service frames of the existing XR service (such as I-frames, P-frames, and B-frames).

[0139] In other words, in practical applications, the SPS frequency domain resource configuration pool can include multiple frequency domain resource configuration information for different service frames.

[0140] The format of each SPS frequency domain configuration information (Sps-Fdraconfig) in the SPS frequency domain resource configuration pool can be as follows: Sps-Fdraconfig{index1, frequency domain configuration 1}, Sps-Fdraconfig{index2, frequency domain configuration 2}, Sps-Fdraconfig{index3, frequency domain configuration 3}, ...

[0141] Understandably, index numbers such as index1, index2, and index3 are used to identify the frequency domain configuration in the SPS frequency domain resource configuration pool. For example, index1 identifies frequency domain configuration 1, index2 identifies frequency domain configuration 2, and index3 identifies frequency domain configuration 3.

[0142] It should be noted that in actual application scenarios, each index is different, and the frequency domain configuration identified by each index can be the same or different. This embodiment does not impose any restrictions on this.

[0143] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the only limitation of this embodiment.

[0144] S102, the UE stores the SPS frequency domain resource configuration pool carried in the RRC signaling.

[0145] Understandably, for downlink SPS and uplink CG type2, the frequency domain resource configuration information of the SPS resources scheduled in each scheduling cycle after the activation of uplink CG type2 and downlink SPS can be selected from the SPS frequency domain resource configuration pool according to the DCI sent by the gNB. Therefore, after the UE receives the RRC signaling sent by the gNB, it can first store the SPS frequency domain resource configuration pool carried in the RRC signaling locally, wait for the DCI sent by the gNB, and then determine the frequency domain resource configuration information of the SPS resources scheduled in each scheduling cycle for downlink SPS and uplink CG type2.

[0146] S103, gNB configures the frequency domain resource configuration information used by SPS cyclically using the FDRA field in DCI based on the index number in the SPS frequency domain resource configuration pool.

[0147] Specifically, in existing communication standards, the configuration information corresponding to the FDRA field in DCI can be represented, for example, by the start position and length information, or by a bitmap.

[0148] This embodiment illustrates the setting of existing FDRA fields using starting position and length information, as shown in Table 1.

[0149] Table 1 shows the settings for the FDRA field when activating uplink CG type 2 and downlink SPS using DCI.

[0150]

[0151] It should be noted that, according to the existing communication standards, the types of uplink and downlink data are identified differently in DCI. Uplink is represented by "0_", such as "0_0", "0_1" and "0_2" in the table above; downlink is represented by "1_", such as "1_0", "1_1" and "1_2" in the table above.

[0152] For example, according to the setting in Table 1, “RIV (Resource indicator value) indicates start “A” and length “B”, the frequency domain resources of the radio resources of uplink CG type2 and downlink SPS will be set to start from position “A” and have a length of “B”.

[0153] To achieve cyclic scheduling of frequency domain resources (SPS resources) of various sizes, the technical solution provided in this implementation reuses the FDRA field and redefines the setting information of the FDRA field, thereby achieving cyclic scheduling of frequency domain resources of various sizes, so that different service frames correspond to different sizes of frequency domain resources, and realizing the matching of SPS frequency domain resources with service frames.

[0154] Furthermore, it should be noted that in practical applications, the FDRA field is a variable-bit field. For example, in a 20M bandwidth scenario, the FDRA field can reach a maximum of 13 bits. Therefore, the number of bits in the FDRA field can be agreed upon based on the corresponding bandwidth.

[0155] For ease of explanation, this embodiment uses a 20M bandwidth and a 13-bit FDRA field as an example.

[0156] For example, in the above scenario, it can be agreed that every 4 bits correspond to an index in the SPS frequency domain resource configuration pool. This allows for the configuration of 3 frequency domain resources to be used cyclically using the FDRA field. Based on this, the modified FDRA field settings are added to the corresponding communication standard. When configuring the frequency domain resources corresponding to the cyclically scheduled radio resources for the UE, the modified FDRA field and the SPS frequency domain resource configuration pool can be used to select the SPS frequency domain resource matching the service frame.

[0157] For example, the modified FDRA field can be shown in Table 2.

[0158] Table 2 shows the FDRA field settings when activating uplink CG type 2 and downlink SPS using DCI in this embodiment.

[0159]

[0160] Referring to Table 2, "FDRA(20M, maximum 13 bits)" indicates that the FDRA field occupies a maximum of 13 bits under a 20M bandwidth; "set to(sps-FdraConfigindexA:4 bits, sps-FdraConfigindexB:4 bits, ...)" means that for the 13 bits of the FDRA field, each 4 bits are assigned an index number, such as index numbers sps-FdraConfigindexA and sps-FdraConfigindexB. sps-FdraConfigindexA and sps-FdraConfigindexB are any two index numbers in the SPS frequency domain resource configuration pool sent by the gNB to the UE.

[0161] For example, in some implementations, the frequency domain resources of both uplink CG type2 and downlink SPS can be set to multiple as shown in Table 2, so that they can be used cyclically during SPS scheduling, i.e., every 4 bits correspond to one frequency domain configuration index.

[0162] For example, in some other implementations, the uplink CG type2 frequency domain resources can be set to multiple, while the downlink SPS uses a fixed frequency domain. Thus, during SPS scheduling, the uplink CG type2 can cyclically schedule the multiple frequency domain resources set, while the downlink SPS uses the same frequency domain resource.

[0163] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the only limitation of this embodiment.

[0164] S104, gNB sends DCI to UE via CS-RNTI scrambled PDCCH.

[0165] S105, the UE selects the SPS resource corresponding to the frequency domain resource configuration information of the current scheduling period from the SPS frequency domain resource configuration pool according to the frequency domain resource configuration information configured in the FDRA field of the DCI, and receives the data scheduled by the gNB through the SPS resource.

[0166] Taking the conventions given in Table 2 as an example, based on the above conventions, if the FDRA field in DCI is "0001001000110", it means that the frequency domain resource configuration information of the cyclically used radio resources are frequency domain configuration 1 corresponding to index1 (0001), frequency domain configuration 2 corresponding to index2 (0010), and frequency domain configuration 3 corresponding to index3 (0011) in the SPS frequency domain resource configuration pool. That is, frequency domain configuration 1, frequency domain configuration 2, frequency domain configuration 3, frequency domain configuration 1, frequency domain configuration 2, frequency domain configuration 3, ...

[0167] It should be noted that when the FDRA field has a maximum of 13 bits, the value of the 13th bit does not affect the technical solution provided in this embodiment. In practical applications, the value of the 13th bit of the FDRA field can be set to "0" or "1" by default. The example "0001001000110" above is an example of "0".

[0168] For example, if the frequency domain configuration is 1 (corresponding to...) Figure 5 The frequency domain resource corresponding to F1 is the largest, and the frequency domain configuration is 3 (corresponding to...). Figure 5 The frequency domain resource corresponding to F3 is the smallest, and the frequency domain configuration is 2 (corresponding to...). Figure 5 The frequency domain resource corresponding to F2 in the above example is between the frequency domain resources corresponding to frequency domain configuration 1 and frequency domain configuration 3. This is assuming the time domain resources remain unchanged. Figure 5 In each scheduling cycle, the time-domain resource size of the radio resources scheduled by the SPS is T1. When the XR frame to be processed is the largest I-frame, radio resources with a frequency-domain resource size of F1 and a time-domain resource size of T1 are configured for the SPS. When the XR frame to be processed is the smallest B-frame, radio resources with a frequency-domain resource size of F3 and a time-domain resource size of T1 are configured for the SPS. When the XR frame to be processed is a P-frame, radio resources with a frequency-domain resource size of F2 and a time-domain resource size of T1 are configured for the SPS. Figure 5 As shown.

[0169] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the only limitation of this embodiment.

[0170] Therefore, the technical solution provided in this embodiment allows the gNB to pre-configure an SPS frequency domain resource configuration pool and utilize the FDRA field in the DCI to configure multiple frequency domain resource configuration information that can be used cyclically for uplink CG type2 and downlink SPS. This enables uplink CG type2 and downlink SPS to achieve cyclic scheduling of frequency domain resources of various sizes, so that different service frames correspond to different sizes of frequency domain resources, thereby achieving matching between SPS frequency domain resources and service frames, reducing user equipment power consumption, and avoiding reducing the system capacity of the base station.

[0171] It should be noted that, in practical application scenarios, the technical solution provided in this embodiment can also be applied to service scenarios involving single frequency domain resource configuration information. Specifically, for scenarios requiring single-cycle configuration for uplink CG type2 and downlink SPS, the content corresponding to every 4 bits in the FDRA field can be the same.

[0172] For example, when the FDRA field is “0001000100010”, it means that the data scheduled by the gNB through PS resources is always received in the frequency domain configuration 1 corresponding to index1.

[0173] For example, when the FDRA field is “0010001000100”, it means that the data scheduled by the gNB through PS resources is always received in the frequency domain configuration 2 corresponding to index2.

[0174] For example, when the FDRA field is “0011001100110”, it means that the data scheduled by the gNB through PS resources is always received in the frequency domain configuration 3 corresponding to index3.

[0175] Understandably, in some implementations, "0000" can be designated as an invalid configuration.

[0176] Accordingly, if "0000" is defined as an invalid configuration, the FDRA field can be "0001000000000" when the frequency domain configuration 1 corresponding to index1 is used to receive data scheduled by the gNB through SPS resources; the FDRA field can be "0010000000000" when the frequency domain configuration 2 corresponding to index2 is used to receive data scheduled by the gNB through SPS resources; and the FDRA field can be "00110000000000" when the frequency domain configuration 3 corresponding to index3 is used to receive data scheduled by the gNB through SPS resources.

[0177] It should be noted that when the FDRA field has a maximum of 13 bits, the value of the 13th bit does not affect the technical solution provided in this embodiment. In practical applications, the value of the 13th bit of the FDRA field can be set to "0" or "1" by default. The above examples "0001000100010", "0010001000100", "0011001100110", and "0011000000000" are all based on "0".

[0178] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the only limitation of this embodiment.

[0179] For a 20M bandwidth scenario, since the FDRA field has a maximum of only 13 bits, if it is agreed that 4 bits correspond to one frequency domain configuration index, then at most 3 frequency domain configurations can be selected for cyclic use. In the SPS frequency domain resource configuration pool, only the frequency domain configurations corresponding to the 15 index numbers from index1 to index15 are available (it is agreed that "0000" is an invalid value and is not used).

[0180] For example, if it is agreed that 3 bits correspond to one frequency domain configuration index, then at most 4 frequency domain configurations can be selected in a cycle, and only the frequency domain configurations corresponding to the 7 index numbers from index1 to index7 are available in the SPS frequency domain resource configuration pool (it is agreed that "000" is an invalid value and is not used).

[0181] For example, if it is agreed that 2 bits correspond to one frequency domain configuration index, then a maximum of 6 frequency domain configurations can be selected for cyclic use, and only the frequency domain configurations corresponding to the three index numbers index1-index3 in the SPS frequency domain resource configuration pool are available (it is agreed that "00" is an invalid value and is not used).

[0182] Therefore, its applicability is limited. To enable the technical solution provided in this application to be applicable to more business scenarios and to achieve more frequency domain cycles, another implementation method is proposed based on the above embodiments.

[0183] See Figure 6 This embodiment includes:

[0184] S201, gNB sends RRC signaling to UE carrying the SPS frequency domain resource configuration pool and the SPS frequency domain resource activation pool.

[0185] S202, the UE stores the SPS frequency domain resource configuration pool and SPS frequency domain resource activation pool carried in the RRC signaling.

[0186] S203, gNB configures the frequency domain resource configuration information for SPS cyclic use using the FDRA field in DCI based on the index number in the SPS frequency domain resource activation pool.

[0187] S204, gNB sends DCI to UE via CS-RNTI scrambled PDCCH.

[0188] S205, the UE selects the SPS resource corresponding to the frequency domain resource configuration information of the current scheduling period from the SPS frequency domain resource activation pool and the SPS frequency domain resource configuration pool according to the frequency domain resource configuration information configured in the FDRA field of the DCI, and receives the data scheduled by the gNB through the PS resource.

[0189] The difference between this embodiment and the above embodiment is that the RRC signaling sent by the gNB to the UE includes not only the SPS frequency domain resource configuration pool configured in the above embodiment, but also the SPS frequency domain resource activation pool. The following focuses on explaining the differences; for similarities, please refer to [link to relevant documentation]. Figure 4 The embodiments shown will not be described again here.

[0190] The SPS frequency domain resource activation information in the SPS frequency domain resource activation pool mentioned above may include, for example, an index number that identifies the SPS frequency domain resource activation information, and the index number of the frequency domain configuration that can be cyclically configured (the index number in the SPS frequency domain resource configuration pool).

[0191] For example, an SPS frequency domain resource activation pool may include one or more SPS frequency domain resource activation information. For each SPS frequency domain resource activation information, it may include, for example, an index number identifying the SPS frequency domain resource activation information, an index number of the corresponding available SPS frequency domain resource configuration information, and the order of the available SPS frequency domain resource configuration information index numbers.

[0192] For example, if the SPS frequency domain resource activation pool includes multiple SPS frequency domain resource activation information, the form of the SPS frequency domain resource activation pool can be as follows: sps-FdraConfigActivationList{1:{1,2},2:{1,2,3},3:{3,1},4:{3,2},…}.

[0193] In this example, the parameter before the colon is the index number that identifies the SPS frequency domain resource activation information, and the parameter in the curly braces after the colon is the index number of the available frequency domain resource configuration information (the index number in the SPS frequency domain resource configuration pool). In practical applications, multiple available frequency domain resource configuration information (the index number in the SPS frequency domain resource configuration pool) can be selected from the SPS frequency domain resource configuration pool according to business needs. This embodiment does not impose any restrictions on this.

[0194] Furthermore, for schemes that have set up SPS frequency domain resource activation pools, all bits of the FDRA field can be agreed upon. For example, under 20M bandwidth, 13 bits correspond to the index number of SPS frequency domain resource activation information in an SPS frequency domain resource activation pool. Then, according to "0000000000000" to "11111111111111", there can be 2 to the power of 13 index numbers of SPS frequency domain resource activation information. And the index number of each SPS frequency domain resource activation information corresponding to the available cyclic frequency domain resource configuration information (the index number in the SPS frequency domain resource configuration pool) can be configured multiple times according to business needs. This can support more configuration methods, make more frequency domain configurations available for cyclic use, and thus adapt to the diverse needs of XR services.

[0195] Similarly, in some implementations, "0000000000000" can be defined as an invalid configuration.

[0196] Based on this, the modified FDRA field settings are added to the corresponding communication standard. When configuring the frequency domain resources corresponding to the cyclically scheduled radio resources for the UE, the radio resources that match the service frame can be selected according to the modified FDRA field, the SPS frequency domain resource activation pool, and the SPS frequency domain resource configuration pool.

[0197] For example, the modified FDRA field can be shown in Table 3.

[0198] Table 3 shows the FDRA field settings when activating uplink CG type2 and downlink SPS using DCI in this embodiment.

[0199]

[0200] Taking the conventions given in Table 3 as an example, based on the above conventions, if the FDRA field in DCI is “0000000000010”, it means that the resource scheduling of subsequent (or next frame) SPS is scheduled in a cyclic manner according to the SPS frequency domain resource configuration information {1, 2, 3} corresponding to the SPS frequency domain resource activation information with index number “2” in the SPS frequency domain resource activation pool, that is, frequency domain configuration 1, frequency domain configuration 2, frequency domain configuration 3, frequency domain configuration 1, frequency domain configuration 2, frequency domain configuration 3, ...

[0201] Correspondingly, if the FDRA field in the DCI is “0000000000001”, it means that the subsequent SPS resource scheduling is scheduled according to the periodic cycle of the SPS configuration information {1, 2} corresponding to the SPS activation information with index number “1” in the SPS resource activation pool, that is, frequency domain configuration 1, frequency domain configuration 2, frequency domain configuration 1, frequency domain configuration 2, ...

[0202] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the only limitation of this embodiment.

[0203] Therefore, the technical solution provided in this embodiment pre-configures an SPS frequency domain resource configuration pool that can cover the diverse needs of XR services as much as possible, and an SPS frequency domain resource activation pool that can set multiple cyclically usable frequency domain configurations according to service requirements. By utilizing the FDRA field in the DCI, multiple cyclically usable frequency domain resource configuration information is configured for uplink CG type2 and downlink SPS, enabling uplink CG type2 and downlink SPS to achieve cyclic scheduling of frequency domain resources of various sizes. This ensures that different service frames correspond to different sizes of frequency domain resources, achieving matching between SPS frequency domain resources and service frames, thereby reducing user equipment power consumption and avoiding reducing the system capacity of the base station.

[0204] Similarly, in practical application scenarios, the technical solution provided in this embodiment can also be applied to business scenarios involving single frequency domain resource configuration information. Those skilled in the art can configure it according to business needs, and this embodiment does not impose any limitations on this.

[0205] This concludes the description of the scheme that uses configuration information for multiple frequency domain resources available for cyclic use to allocate SPS resources of different sizes to different service frames, thereby enabling the service frames and SPS resources to be matched.

[0206] Furthermore, based on the content described in the above embodiments, multiple time-domain resource configuration information that can be used cyclically can be configured to allocate SPS resources of different sizes to different service frames, thereby enabling the service frames and SPS resources to be matched.

[0207] The configuration of cyclic time-domain resource configuration information can be achieved by redefining the TDRA field and configuring the SPS time-domain resource configuration pool.

[0208] For example, since the TDRA field consists of 4 bits, in some implementations, it can be agreed that every two bits in the TDRA field correspond to a time-domain configuration. For instance, "11" corresponds to index 3, time-domain configuration 3; "10" corresponds to index 2, time-domain configuration 2; "01" corresponds to index 1, time-domain configuration 1; and "00" indicates an invalid configuration. Based on this, when the TDRA field is "1101", the time-domain resources that can be used cyclically are time-domain configuration 3, time-domain configuration 1, time-domain configuration 3, time-domain configuration 1, ...

[0209] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the only limitation of this embodiment.

[0210] Since the TDRA field only has 4 bits, only two time-domain resource configuration information can be selected at a time for cyclic use, meaning only a dual-time-domain approach can be used, thus limiting its applicability to certain scenarios. To make the technical solution provided in this application applicable to more service scenarios, an SPS time-domain resource activation pool can also be introduced in the scheme of separately modifying the time domain to achieve SPS radio resource and service frame matching.

[0211] The method of introducing the SPS time domain resource activation pool uses 4 bits to represent the index number of the SPS time domain resource activation pool, which allows the time domain configuration to be increased from 2 indices to 16 indices (if it is agreed that "0000" means no invalid configuration, there can also be 15 indices from index1 to index15), and the available time domain configurations corresponding to each index can be selected multiple times according to business needs.

[0212] For example, if time domain configuration 1 (corresponding to Figure 7 The time-domain resource corresponding to T1 in the time domain is the largest, and the time-domain configuration is 3 (corresponding to...). Figure 7 The time-domain resource corresponding to T3 in the time-domain configuration is the smallest, and the time-domain configuration is 2 (corresponding to...). Figure 7 The time-domain resource corresponding to T2 in the above example is between the time-domain resources corresponding to time-domain configuration 1 and time-domain configuration 3, provided that the size of the frequency-domain resource remains unchanged. Figure 7In each scheduling cycle, the SPS schedules radio resources with a frequency domain resource size of F1. When the XR frame to be processed is the largest I-frame, the SPS is configured with radio resources of frequency domain size F1 and time domain size T1. When the XR frame to be processed is the smallest B-frame, the SPS is configured with radio resources of frequency domain size F1 and time domain size T3. When the XR frame to be processed is a P-frame, the SPS is configured with radio resources of frequency domain size F1 and time domain size T2. Figure 7 As shown.

[0213] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the only limitation of this embodiment.

[0214] Therefore, by configuring multiple time-domain resource configuration information that can be used cyclically, different sizes of SPS resources can be allocated to different service frames, thereby enabling the service frames and SPS resources to be matched.

[0215] In addition, it is understandable that in some other implementations, in order to match the radio resources scheduled by SPS with the diverse service requirements of XR services, in addition to modifying the frequency domain configuration alone or the time domain configuration alone, the radio resources scheduled by SPS can also be adjusted by modifying both the frequency domain configuration and the time domain configuration simultaneously.

[0216] For example, if time domain configuration 1 (corresponding to Figure 8 The time-domain resource corresponding to T1 in the time domain is the largest, and the time-domain configuration is 3 (corresponding to...). Figure 8 The time-domain resource corresponding to T3 in the time-domain configuration is the smallest, and the time-domain configuration is 2 (corresponding to...). Figure 8 The time-domain resource corresponding to T2 in the above context is between the time-domain resource corresponding to time-domain configuration 1 and the time-domain resource corresponding to time-domain configuration 3. The frequency-domain resource corresponding to T2 is between the time-domain resource corresponding to time-domain configuration 1 and the time-domain resource corresponding to time-domain configuration 3. Figure 8 The frequency domain resource corresponding to F1 is the largest, and the frequency domain configuration is 3 (corresponding to...). Figure 8 The frequency domain resource corresponding to F3 is the smallest, and the frequency domain configuration is 2 (corresponding to...). Figure 8 The frequency domain resource corresponding to F2 in the above configuration is between the frequency domain resources corresponding to frequency domain configuration 1 and frequency domain configuration 3. When the XR frame to be processed is the largest I-frame, a radio resource with a frequency domain resource size of F1 and a time domain resource size of T1 is configured for the SPS. When the XR frame to be processed is the smallest B-frame, a radio resource with a frequency domain resource size of F3 and a time domain resource size of T3 is configured for the SPS. When the XR frame to be processed is a P-frame, a radio resource with a frequency domain resource size of F2 and a time domain resource size of T2 is configured for the SPS. Figure 8 As shown.

[0217] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the sole limitation of this embodiment. In practical applications, it is not limited to the maximum time-domain and frequency-domain configurations corresponding to I-frames, nor is it limited to the minimum time-domain and frequency-domain configurations corresponding to B-frames, nor is it limited to the time-domain and frequency-domain configurations corresponding to P-frames being between those of I-frames and B-frames. Those skilled in the art can configure according to actual business needs, and this embodiment does not impose any restrictions in this regard.

[0218] Based on the above description, by reusing the MCS field in DCI, multiple modulation and coding schemes that can be configured for cyclic scheduling can also be achieved. That is, for the service frames that need to be processed in the scheduling cycle, different modulation and coding schemes can be used for processing, so that the resource scheduling of SPS can be better matched with XR services.

[0219] Regarding the scheme for reusing the TDRA field and the MCS field, please refer to the description in the above embodiment on reusing FDRA to match the resource scheduling of SPS with XR services, which will not be repeated here.

[0220] Option 2: Time and frequency resource configuration for downlink SPS.

[0221] As described in the above embodiments, the cyclic configuration method of SPS resources given in Scheme 1 requires separate configuration of SPS resources (time domain resources and / or frequency domain resources) for each UE's different SPS scheduling periods. To simplify this process while ensuring that the radio resources scheduled for each downlink SPS can still match the service frames of each scheduling period, Scheme 2 provides a combination of basic radio resources (determined by basic SPS resource configuration information) and common radio resources (determined by common SPS resource configuration information). In this embodiment, the gNB can configure multiple common radio resources (of different sizes) according to service requirements and configure the same size of basic radio resources for each SPS scheduling period of the UE. In this way, for service frames of different sizes, the UE can select different sizes of common radio resources based on the basic radio resources, thus achieving the scheduling of radio resources of different sizes.

[0222] In other words, for a UE, the basic radio resources that can be used are the same when SPS resource scheduling is performed in different scheduling periods, while the public radio resources will vary depending on the actual service.

[0223] For example, in Scheme 2, for the aforementioned basic radio resources, the gNB can configure RRC signaling. In this RRC signaling, fixed frequency domain resource configuration information and time domain resource configuration information can be configured through the FDRA and TDRA fields, for example... Figure 9The frequency domain resource size of all SPS resources corresponding to the SPS is F3, and the time domain resource size is T1.

[0224] Furthermore, based on the above, the RRC signaling also needs to configure a common time-frequency resource configuration pool (time-domain resource configuration information and frequency-domain resource configuration information) that can be selected by the UE.

[0225] For example, a public time-frequency resource configuration pool (e.g., named Sps-ResourceConfigCommon) could take the form of: Sps-ResourceConfigCommon{{index1, time-domain configuration 1, frequency-domain configuration 1},{index2, time-domain configuration 2, frequency-domain configuration 2},{index3, time-domain configuration 3, frequency-domain configuration 3},...}.

[0226] Understandably, one or more public time-frequency resource configuration information (public radio resources) can be configured in the public time-frequency resource configuration pool for UE to select.

[0227] In addition, it should be noted that in order for the UE to determine whether it needs to use or which public radio resource to use when performing SPS resource scheduling in each scheduling cycle, it is specifically done by detecting whether the public radio resource carries the demodulation reference signal (DMRS) corresponding to the current UE.

[0228] Understandably, each UE typically has a unique DMRS that identifies it; that is, each UE has a different DMRS. Therefore, by detecting whether its own DMRS is present in the public radio resources, the UE can determine the specific radio resources to be used in this SPS resource scheduling.

[0229] For example, in practical applications, in addition to using the basic radio resources of the current scheduling period, the UE also needs to check whether there is a corresponding DMRS among one or more public radio resources corresponding to the current scheduling period. If there is, it means that the public radio resources corresponding to the current scheduling period need to be used; otherwise, they are not used.

[0230] In addition, it should be noted that in practical applications, the UE can only detect whether its own DMRS is in the public radio resources in each scheduling cycle after the public radio resources are enabled.

[0231] For example, enabling public radio resources can be done either through RRC signaling alone or by agreeing on a specific bit in the DCI.

[0232] For methods that use RRC signaling alone, for example, after sending the RRC signaling configured with basic radio resources and public radio resources to the UE, such as UE1, UE2 and UE3, if it is determined according to service requirements that UE1 needs to occupy additional radio resources on top of the basic radio resources when performing SPS resource scheduling, the gNB can send information on configuring additional public radio resources to UE1 separately through RRC signaling. In this way, the public time and frequency resources (public radio resources) in the public time and frequency resource configuration pool stored in UE1 are enabled.

[0233] For example, in this method of enabling public time and frequency resources solely through RRC signaling, the information carried in the RRC signaling could be, for example, "sps-AdditionalResource ENUMERATED{true}", thereby enabling the public time and frequency resources.

[0234] In practical applications, by specifying a certain bit in the DCI, for example, it can be agreed that the first bit of the FDRA field in the DCI can be used to enable it, such as agreeing that "1" enables it and "0" disables it.

[0235] Furthermore, after the common time and frequency resources are enabled, UE1 can detect whether there is a DMRS corresponding to UE1 on the common time and frequency resources.

[0236] For example, if we call the common time-frequency resource corresponding to index1 in Sps-ResourceConfigCommon "Common1", and the common time-frequency resource corresponding to index2 in Sps-ResourceConfigCommon "Common2", and agree that basic radio resource + Common1 corresponds to I-frames, basic radio resource + Common2 corresponds to P-frames, and basic radio resource corresponds to B-frames, after enabling Common1 and Common2 for UE1, the radio resources corresponding to UE1 in each scheduling cycle can be configured as follows: Figure 9 As shown.

[0237] It should be noted that the aforementioned enabling specifically refers to the gNB sending "sps-AdditionalResourceENUMERATED{true}" to UE1, and UE1 detecting its own DMRS on Common1 and Common2. In this case, the radio resources corresponding to UE1 in each scheduling cycle are as follows: Figure 9 As shown.

[0238] For example, in some implementations, the size of the Common corresponding to different indices can be the same or different.

[0239] For example, in some other implementations, the size of the Common corresponding to different indices can decrease as the index increases, for example... Figure 9 As shown, the size of Common1 is larger than the size of Common2.

[0240] For example, in some other implementations, the size of the Common corresponding to different indices can be set according to the size of the corresponding XR frame.

[0241] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the only limitation of this embodiment.

[0242] Furthermore, based on the above implementation, the gNB can be configured to transmit only low-priority data frames on public radio resources. In this way, even if the UE fails to decode the data on public time and frequency resources due to missing its corresponding DMRS or bit errors, the impact on the service processing results will be small, thereby ensuring the stability of the service.

[0243] Furthermore, to further simplify the gNB's processing flow, for example, in scenarios where multiple UEs can transmit the same data frames (such as multiple users playing a game together, where each UE displays essentially the same screen, thus allowing the transmission of identical data frames), a common DMRS can be defined to correspond to common radio resources, with common data frames transmitted through these resources. Thus, for service scenarios requiring UEs to use common radio resources, the gNB simply adds a common DMRS to the common radio resources for common data frames that need to be decoded by multiple UEs, and adds the DMRS for data frames that need to be decoded by a specific UE. In this way, by utilizing both the common DMRS and its own DMRS to decode the common radio resources, the UE can decode both the common data frames sent by the gNB and the data frames sent only to itself from the common radio resources.

[0244] Therefore, the technical solution provided in this embodiment, for downlink SPS, since the gNB can know in advance which UEs need which radio resources, can configure basic radio resources for each access UE, configure one or more common time-frequency resources (common time-frequency domain resources) according to service requirements, and dynamically enable the configured common time-frequency resources (common time-frequency domain resources) according to service requirements, thereby realizing the allocation of different radio resources for different UEs, thus meeting the diverse needs of XR services and matching the XR service frames corresponding to each scheduling cycle.

[0245] Option 3: Time and frequency resource configuration for uplink SPS (uplink CG type 1 and uplink CG type 2).

[0246] For example, see Figure 10 The implementation of Scheme 3 may include:

[0247] S301, gNB sends RRC signaling carrying the SPS time-frequency resource configuration pool to UE.

[0248] Understandably, the SPS time-frequency resource configuration pool mentioned above may include one or more time-frequency resource configuration information. Each time-frequency resource configuration information is identified by a different index, and each time-frequency resource configuration information simultaneously configures time-domain resource configuration information and frequency-domain resource configuration information.

[0249] For example, the time-domain resource configuration information and the frequency-domain resource configuration information in the time-frequency resource configuration information of each index may be the same or different, and this embodiment does not impose any restrictions on this.

[0250] For example, in some implementations, the SPS time-frequency resource configuration pool can be set as follows: Sps-ResourceConfig{{index1, time-domain configuration 1, frequency-domain configuration 1},{index2, time-domain configuration 2, frequency-domain configuration 2},{index3, time-domain configuration 3, frequency-domain configuration 3},…}.

[0251] S302, the UE stores the SPS time-frequency resource configuration pool carried in the RRC signaling.

[0252] S303, the UE adds the SPS time-frequency resource configuration information corresponding to the data frame sent this time to the CG-UCI.

[0253] Understandably, the CG-UCI mentioned above, namely the Configuredgrant Uplink Control Information, is added to the PUSCH when the UE sends uplink data frames to the gNB via the PUSCH. In the current implementation scenario, it usually carries the content shown in Table 4.

[0254] Table 4. Field information carried in existing CG-UCI

[0255] Field Bitwidth HARQ process number 4 Redundancy version 2 New data indicator 1 … …

[0256] Referring to Table 4, “HARQ process number” represents the process number of the Hybrid Automatic Repeat Request, and its corresponding “4” indicates that it occupies 4 bits; “Redundancy version” represents the redundant version, and its corresponding “2” indicates that it occupies 2 bits; “New data indicator” represents the new / retransmitted data indicator, and its corresponding “1” indicates that it occupies 1 bit.

[0257] Understandably, in practical applications, CG-UCI can also record other field information, which will not be listed here, and this embodiment does not impose any restrictions on this.

[0258] For example, in order to enable the UE to actively determine the SPS resource corresponding to the uplink data frame and inform the gNB so that the gNB can obtain the uplink data frame from the specified SPS resource, the technical solution provided in this embodiment adds a field information specifying the SPS time-frequency resource corresponding to the data frame to be transmitted, based on Table 4 above. The field information written in the modified CG-UCI is shown in Table 5, for example.

[0259] Table 5 shows the field information carried in the CG-UCI of this embodiment (with the SPS resource config index field added).

[0260] Field Bitwidth HARQ process number 4 Redundancy version 2 New data indicator 1 … … SPS resource config index 3

[0261] Among them, "SPS resource config index" represents the index number of the SPS time-frequency resource (SPS resource) corresponding to the uplink data frame sent this time in the SPS time-frequency resource configuration pool Sps-ResourceConfig.

[0262] For example, taking Table 5 as an example, the "3" corresponding to "SPS resource config index" indicates that it occupies 3 bits. Based on this, when "SPS resource config index" occupies 3 bits, if the value of the "SPS resource configindex" field (the binary code corresponding to 3 bits) is "011", it means that the UE uses the time-frequency resource configuration information corresponding to index3 in Sps-ResourceConfig.

[0263] Taking the example of Sps-ResourceConfig{{index1, time domain configuration 1, frequency domain configuration 1}, {index2, time domain configuration 2, frequency domain configuration 2}, {index3, time domain configuration 3, frequency domain configuration 3}, ...} in S301, the time domain resource size of the SPS resource specified by CG-UCI in Table 5 is time domain configuration 3, and the frequency domain resource size is frequency domain configuration 3.

[0264] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the only limitation of this embodiment.

[0265] In addition, it should be noted that in some implementations, the UE can specify the index corresponding to the time domain configuration for transmitting uplink data frames separately through CG-UCI, and adjust the radio resources scheduled by uplink SPS by changing the time domain configuration to better match the uplink data frames.

[0266] For example, when specifying the index corresponding to the time domain configuration for transmitting uplink data frames separately, the RRC signaling sent by the gNB to the UE needs to carry the SPS time domain resource configuration pool.

[0267] For example, the SPS time-domain resource configuration pool can take the form of: Sps-Tdraconfig{index1, time-domain configuration 1}, Sps-Tdraconfig{index2, time-domain configuration 2}, Sps-Tdraconfig{index3, time-domain configuration 3}, ...

[0268] Based on the aforementioned SPS time-domain resource configuration pool, the UE can specify the corresponding index of the time-domain configuration for transmitting uplink data frames separately through CG-UCI, as shown in Table 6.

[0269] Table 6 shows the field information carried in the CG-UCI of this embodiment (with the SPS TDRA config index field added).

[0270] Field Bitwidth HARQ process number 4 Redundancy version 2 New data indicator 1 … … SPS TDRA config index 3

[0271] Here, "SPS TDRA config index" represents the index number of the time domain configuration corresponding to the uplink data frame sent this time in the SPS time domain resource configuration pool Sps-Tdraconfig.

[0272] For example, taking Table 6 as an example, the "3" corresponding to "SPS TDRA config index" indicates that it occupies 3 bits. Based on this, when "SPS TDRA config index" occupies 3 bits, if the value of the "SPS TDRA config index" field (the binary code corresponding to the 3 bits) is "010", it means that the UE uses the time domain resource configuration information corresponding to index2 in Sps-Tdraconfig.

[0273] Taking the examples above, such as Sps-Tdraconfig{index1, time domain configuration 1}, Sps-Tdraconfig{index2, time domain configuration 2}, Sps-Tdraconfig{index3, time domain configuration 3}, ..., the time domain resource size of the SPS resource specified by CG-UCI in Table 6 is time domain configuration 3.

[0274] Understandably, for this configuration, the frequency domain can be fixed, i.e., specified in the RRC signaling via FDRA.

[0275] Furthermore, it should be understood that the above description is merely an example provided for a better understanding of the technical solution of this embodiment, and is not intended as the sole limitation of this embodiment.

[0276] In addition, it should be noted that in some other implementations, the UE can also specify the corresponding index of the frequency domain configuration for transmitting uplink data frames separately through CG-UCI, and adjust the radio resources scheduled by uplink SPS by changing the frequency domain configuration in order to better match the uplink data frames.

[0277] For example, for the method of specifying the index corresponding to the frequency domain configuration of the uplink data frame to be transmitted separately, the RRC signaling sent by the gNB to the UE needs to carry the SPS frequency domain resource configuration pool.

[0278] For example, the SPS frequency domain resource configuration pool can take the form of Sps-Fdraconfig{index1, frequency domain configuration 1}, Sps-Fdraconfig{index2, frequency domain configuration 2}, Sps-Fdraconfig{index3, frequency domain configuration 3}, Sps-Fdraconfig{index4, frequency domain configuration 4}, ...

[0279] Based on the SPS frequency domain resource configuration pool mentioned above, the UE can specify the corresponding index of the frequency domain configuration for transmitting uplink data frames separately through CG-UCI, as shown in Table 7.

[0280] Table 7 shows the field information carried in the CG-UCI of this embodiment (with the SPS FDRA config index field added).

[0281]

[0282]

[0283] Here, "SPS FDRA config index" represents the index number of the frequency domain configuration corresponding to the uplink data frame sent this time in the SPS frequency domain resource configuration pool Sps-Fdraconfig.

[0284] For example, taking Table 7 as an example, the "4" corresponding to "SPS FDRA config index" indicates that it occupies 4 bits. Based on this, when "SPS FDRA config index" occupies 4 bits, if the value of the "SPS FDRA config index" field (the binary code corresponding to 4 bits) is "0001", it means that the UE uses the frequency domain resource configuration information corresponding to index1 in Sps-Fdraconfig.

[0285] Taking the examples above, such as Sps-Fdraconfig{index1, frequency domain configuration 1}, Sps-Fdraconfig{index2, frequency domain configuration 2}, Sps-Fdraconfig{index3, frequency domain configuration 3}, Sps-Fdraconfig{index4, frequency domain configuration 4}, ..., the frequency domain resource size of the SPS resource specified by CG-UCI in Table 7 is frequency domain configuration 1.

[0286] Understandably, for this configuration, the time domain can be fixed, i.e., specified in the RRC signaling via TDRA.

[0287] Furthermore, it should be understood that the above description is merely an example provided for a better understanding of the technical solution of this embodiment, and is not intended as the sole limitation of this embodiment.

[0288] In addition, it should be noted that in some implementations, the UE can specify the index corresponding to the time domain configuration and the index corresponding to the frequency domain configuration for transmitting uplink data frames separately through CG-UCI. By changing the time domain configuration and frequency domain configuration, the radio resources scheduled for uplink SPS can be adjusted to better match the uplink data frames.

[0289] For example, for the method of simultaneously specifying the index corresponding to the time domain configuration and the index corresponding to the frequency domain configuration for transmitting uplink data frames, the method corresponding to Table 5 above can be used to set the gNB to send RRC signaling carrying the SPS time-frequency resource configuration pool to the UE, or the gNB can be set to send RRC signaling carrying both the SPS time domain resource configuration pool and the SPS frequency domain resource configuration pool.

[0290] For the latter, for example, the form of the SPS time-domain resource configuration pool can be: Sps-Tdraconfig{index1, time-domain configuration 1}, Sps-Tdraconfig{index2, time-domain configuration 2}, Sps-Tdraconfig{index3, time-domain configuration 3}, ...

[0291] The SPS frequency domain resource configuration pool can take the form of, for example, Sps-Fdraconfig{index1, frequency domain configuration 1}, Sps-Fdraconfig{index2, frequency domain configuration 2}, Sps-Fdraconfig{index3, frequency domain configuration 3}, Sps-Fdraconfig{index4, frequency domain configuration 4}, ...

[0292] Based on the aforementioned SPS time-domain resource configuration pool and SPS frequency-domain resource configuration pool, the UE can specify the index corresponding to the time-domain configuration and the index corresponding to the frequency-domain configuration for transmitting uplink data frames separately through CG-UCI, as shown in Table 8.

[0293] Table 8 shows the field information carried in the CG-UCI of this embodiment (with the SPS TDRA config index field added).

[0294]

[0295]

[0296] For example, taking the above-mentioned examples of "Sps-Tdraconfig{index1, time domain configuration 1}, Sps-Tdraconfig{index2, time domain configuration 2}, Sps-Tdraconfig{index3, time domain configuration 3}, ..." and "Sps-Fdraconfig{index1, frequency domain configuration 1}, Sps-Fdraconfig{index2, frequency domain configuration 2}, Sps-Fdraconfig{index3, frequency domain configuration 3}, Sps-Fdraconfig{index4, frequency domain configuration 4}, ..." as examples, if the value of the "SPS FDRA config index" field (the binary code corresponding to the 4 bits) is "0001", it means that the UE uses the frequency domain resource configuration information corresponding to index1 in Sps-Fdraconfig. If "SPS TDRA config When the value of the "index" field (the binary code corresponding to the 3 bits) is "001", it means that the UE uses the frequency domain resource configuration information corresponding to index1 in Sps-Tdraconfig. That is, the time domain resource size of the SPS resource specified by CG-UCI in Table 8 is time domain configuration 1, and the frequency domain resource size is frequency domain configuration 1.

[0297] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the only limitation of this embodiment.

[0298] S304, the UE sends the CG-UCI to the gNB via the PUSCH.

[0299] S305, the gNB obtains the uplink data frames sent by the UE from the SPS time-frequency resources specified in the CG-UCI.

[0300] Therefore, the technical solution provided in this embodiment allows the gNB to configure an SPS time-frequency resource configuration pool (SPS time-domain resource configuration pool and / or SPS frequency-domain resource configuration pool) for the UE. This enables the UE to actively report the SPS resources corresponding to the current uplink data frame by carrying the CG-UCI each time it sends an uplink data frame to the gNB. As a result, when scheduling each uplink data frame sent by the UE, the gNB can decode the uplink data frame according to the SPS resources specified in the CG-UCI, thereby ensuring that the radio resources of the uplink SPS can be matched with the uplink data frame.

[0301] Option 4: Configure time and frequency resources (radio resources) for downlink SPS.

[0302] It should be noted that in XR service scenarios, UEs can usually determine the size of downlink data frames based on the current user's behavior. For example, the UE can determine the size of the next downlink data frame by the range of changes in the user's perspective (the size of the next downlink data frame will be referred to as prior information).

[0303] For example, the greater the range of viewpoint changes, the larger the content of the screen involved, which means that the downlink data frame of the corresponding screen will be larger, and therefore the SPS resources matching the downlink data frame also need to be larger.

[0304] Based on this relationship, see Figure 11 The range of change for viewpoint 1 is smaller than that for viewpoint 2, and the range of change for viewpoint 2 is smaller than that for viewpoint 3. Therefore, in practical applications, if the user's viewpoint remains primarily within viewpoint 1 for a given period, the size of the next downlink data frame will be relatively small; if the user's viewpoint remains primarily within viewpoint 3 for a given period, the size of the next downlink data frame will be relatively large; and if the user's viewpoint remains primarily within viewpoint 2 for a given period, the size of the next downlink data frame will be between the sizes of the downlink data frames corresponding to viewpoints 1 and 3.

[0305] For example, if it is agreed that the SPS resources to be scheduled for the downlink data frame corresponding to view 1 are configuration 1, the SPS resources to be scheduled for the downlink data frame corresponding to view 2 are configuration 2, and the SPS resources to be scheduled for the downlink data frame corresponding to view 3 are configuration 3.

[0306] Based on this, the configuration of downlink SPS resources can be achieved in the following three ways.

[0307] Before describing the three configuration methods for implementing downlink SPS resources, we will first explain the objects involved in these three configuration methods.

[0308] For example, in some implementation scenarios, it can be divided into a UE (User Equipment) client, a gNB (Gate Network NodeB) that interacts with the UE, and an AF (Application Server Array) that interacts with the gNB, where both the gNB and the AF are connected to the core network AMF (Active Network Function).

[0309] See Figure 12 Method 1 for configuring downlink SPS resources based on prior information includes:

[0310] S401, the UE selects the radio resource configuration information corresponding to the downlink SPS from the RRC signaling carrying the radio resource configuration pool sent by the gNB based on prior information.

[0311] Understandably, the aforementioned RRC signaling carrying the radio resource configuration pool can, for example, be configured by the gNB according to the service requirements of the XR service after the UE accesses the gNB, i.e., after the two establish a communication connection. For example, radio resource configuration information corresponding to small data volume (hereinafter referred to as configuration 1), radio resource configuration information corresponding to large data volume (hereinafter referred to as configuration 3), and radio resource configuration information between these two data volumes (hereinafter referred to as configuration 2). Then, the RRC signaling carrying the above-mentioned radio resource configuration information is sent to the UE via RRC signaling.

[0312] Accordingly, after receiving the RRC signaling, the UE stores it locally. When it needs to transmit data with the gNB via SPS, it selects the radio resource configuration information corresponding to the current prior information, i.e. the estimated next downlink data frame, from the RRC signaling based on the estimated prior information, and determines the radio resources to be scheduled by the downlink SPS.

[0313] S402, the UE sends the radio resource configuration information corresponding to the selected downlink SPS of the next frame to the AF.

[0314] Understandably, in practical applications, the UE needs the assistance of the gNB and AMF to send the radio resource configuration information corresponding to the selected downlink SPS to the AF. That is, the UE first needs to send the radio resource configuration information corresponding to the selected downlink SPS to the gNB, then the gNB sends the radio resource configuration information corresponding to the selected downlink SPS to the AMF, and finally the AMF sends the radio resource configuration information corresponding to the selected downlink SPS to the AF.

[0315] It should be noted that in this embodiment, the radio resource configuration information corresponding to the next downlink SPS selected by the UE is sent to the AF through application layer data. Therefore, the gNB and AMF only pass through this data without parsing it. As a result, the gNB and AMF cannot know the radio resource configuration information corresponding to the next downlink SPS selected by the UE.

[0316] S403, AF encapsulates downlink data packets (downlink data frames) according to the data packet threshold value corresponding to the radio resource configuration information corresponding to the downlink SPS selected by the UE.

[0317] For ease of explanation, this embodiment takes the wireless resource configuration information as divided into configuration 1 (small), configuration 2 (medium), and configuration 3 (large) as mentioned above. For these three types of wireless resource configuration information, AF and gNB and / or AMF can agree on two data packet threshold values, for example, 500KB and 1000KB.

[0318] Accordingly, based on these two data packet thresholds, the radio resource configuration information corresponding to the data packet in the range of [0KB, 500KB) is configuration 1; the radio resource configuration information corresponding to the data packet in the range of [500KB, 1000KB) is configuration 2; and the radio resource configuration information corresponding to the data packet in the range of [1000KB, ∞KB) is configuration 3.

[0319] In other words, based on the above agreement, when the radio resource configuration information corresponding to the downlink SPS selected by the UE is configuration 1, the downlink data packet encapsulated by AF shall not exceed 500KB.

[0320] Accordingly, when the radio resource configuration information corresponding to the downlink SPS selected by the UE is configuration 2, the downlink data packet encapsulated by AF shall not exceed 1000KB at most and shall not be less than 500KB at least.

[0321] Accordingly, when the radio resource configuration information corresponding to the downlink SPS selected by the UE is configuration 3, the minimum downlink data packet encapsulated by AF is not less than 1000KB.

[0322] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the only limitation of this embodiment.

[0323] S404, AF sends the encapsulated downlink data packet to gNB.

[0324] Understandably, in practical applications, the AF needs the AMF to send downlink data packets, encapsulated according to the data packet threshold value corresponding to the radio resource configuration information of the downlink SPS selected by the UE, to the gNB. That is, the AF needs to first send the encapsulated downlink data packets to the AMF, and then the AMF sends the downlink data packets sent by the AF to the gNB.

[0325] S405, gNB determines the radio resource configuration information corresponding to the downlink data packet encapsulated by AF based on the correspondence between the data packet threshold value agreed with AF and the radio resource configuration information.

[0326] Taking the relationship between the threshold value range data packet size and radio resource configuration information agreed upon in S403 as an example, if the size of the downlink data packet received by the gNB is between 500KB and 1000KB, then the radio resource configuration information of the downlink SPS that transmits the downlink data packet is determined to be Configuration 2.

[0327] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the sole limitation of this embodiment. In practical applications, the gNB can configure multiple radio resource configuration information according to the diversified needs of XR services, and at the same time agree with the AF on the correspondence between multiple data packet threshold values ​​and these radio resource configuration information, so that the radio resources scheduled by downlink SPS can be better matched with XR services.

[0328] S406, the gNB sends the AF-encapsulated downlink data packets to the UE using the downlink SPS resources corresponding to the determined radio resource configuration information.

[0329] Therefore, in the technical solution provided in this embodiment, the gNB and AF pre-agree on the correspondence between the data packet threshold value and the radio resource configuration information. Then, the AF encapsulates the downlink data packet according to the size of the next downlink data frame (data packet) estimated by the UE, so that the gNB can determine the radio resources of the downlink SPS that need to be scheduled according to the agreed correspondence, so as to better adapt to XR services.

[0330] See Figure 13 Method 2 for configuring downlink SPS resources based on prior information includes:

[0331] S501, the UE selects the radio resource configuration information corresponding to the downlink SPS from the RRC signaling carrying the radio resource configuration pool sent by the gNB based on prior information.

[0332] Understandably, step S501 in this embodiment is largely the same as step S401 in the above embodiment; for specific implementation details, please refer to [link to relevant documentation]. Figure 12 The corresponding implementation examples will not be described in detail here.

[0333] S502, the UE sends the radio resource configuration information corresponding to the selected downlink SPS of the next frame to the gNB via CG-UCI.

[0334] Understandably, the operation of the UE sending the radio resource configuration information corresponding to the selected downlink SPS to the gNB via CG-UCI is largely the same as the implementation method given in Scheme 3. For specific implementation details, please refer to [link to relevant documentation]. Figure 10 The corresponding implementation examples will not be described in detail here.

[0335] S503, the gNB sends the AF-encapsulated downlink data packets to the UE through the downlink SPS resources corresponding to the radio resource configuration information reported in CG-UCI.

[0336] Therefore, in the technical solution provided in this embodiment, the UE reports the required downlink SPS resource configuration information to the gNB through UCI / CG-UCI based on prior information. The gNB uses the configuration reported by the UE to schedule the next data packet. In this way, after the UE reports, it only detects the reported downlink SPS resources in the next cycle, thereby realizing the matching of downlink SPS resources with XR services.

[0337] See Figure 14 Method 3, which configures downlink SPS resources based on prior information, includes:

[0338] S601, the UE selects the radio resource configuration information corresponding to the downlink SPS from the RRC signaling carrying the radio resource configuration pool sent by the gNB based on prior information.

[0339] S602, the UE sends the radio resource configuration information corresponding to the selected downlink SPS to the AF.

[0340] Steps S601 and S602 in this embodiment are the same as Figure 12 Steps S401 and S402 in the corresponding embodiments are largely the same; for specific implementation details, please refer to [link / reference needed]. Figure 12 The corresponding implementation examples will not be described in detail here.

[0341] S603, the AF sends the encapsulated downlink data packet and the radio resource configuration information corresponding to the downlink SPS selected by the UE to the gNB.

[0342] For example, in this embodiment, the gNB and AF do not need to agree on the correspondence between the data packet threshold value and the radio resource configuration information, so they do not need to encapsulate the downlink data packet according to the radio resource configuration information corresponding to the downlink SPS selected by the UE.

[0343] In addition, in order for the gNB to schedule downlink data packets according to the downlink SPS resource configuration information corresponding to the downlink SPS selected by the UE, the AF can send the radio resource configuration information corresponding to the downlink SPS selected by the UE to the gNB at the same time when sending downlink data packets, or it can send them separately. This embodiment does not restrict this.

[0344] S604, the gNB sends the downlink data packets encapsulated by the AF to the UE via the downlink SPS resources corresponding to the radio resource configuration information sent by the AF.

[0345] Therefore, in the technical solution provided in this embodiment, the AF not only sends the encapsulated downlink data packets to the gNB, but also sends the radio resource configuration information corresponding to the downlink SPS selected by the UE. Thus, it is not necessary to set a correspondence between the data packet threshold and the radio resource configuration information between the gNB and the AF, nor is it necessary to limit the size of the downlink data packets encapsulated by the AF. It is only necessary to send the radio resource configuration information corresponding to the downlink SPS selected by the UE to the gNB, so that the gNB can use the configuration reported by the UE to schedule the next data packet. In this way, after the UE reports, it only checks the reported downlink SPS resources in the next cycle, thereby realizing the matching of downlink SPS resources with XR services.

[0346] Furthermore, it should be noted that, regarding the implementation scheme in the above embodiments where the base station only sends the SPS resource configuration pool (e.g., SPS frequency domain resource configuration pool / SPS time domain resource configuration pool / SPS modulation and coding scheme resource configuration pool / SPS time-frequency resource configuration pool) to the user equipment, in specific implementation, it can be achieved through... Figure 15 The process shown is implemented.

[0347] For example, see Figure 15 The process of semi-static scheduling for user equipment and base stations includes:

[0348] S701, send first configuration information to the user equipment. The first configuration information includes a semi-static scheduling SPS resource configuration pool. The SPS resource configuration pool includes one or more SPS resource configuration information and an index number corresponding to each SPS resource configuration information.

[0349] For example, after the base station sends the first configuration information to the user equipment, the user equipment will receive the first configuration information from the base station.

[0350] Furthermore, it should be noted that in this embodiment, the first configuration information is carried in Radio Resource Control (RRC) signaling. That is, the base station sends the first configuration information to the user equipment through RRC signaling, and the user equipment can parse the first configuration information from the received RRC signaling.

[0351] Understandably, the SPS resource configuration pool included in the first configuration information mentioned in this embodiment may be, for example, Figure 4 The corresponding embodiment mentions the SPS frequency domain resource configuration pool. For details on the specific form of the SPS frequency domain resource configuration pool, please refer to... Figure 4 The description of the corresponding embodiments is omitted here.

[0352] S702, send second configuration information to the user equipment, the second configuration information indicating at least one index number in the SPS resource configuration pool, and the order of the at least one index number.

[0353] For example, after the base station sends the second configuration information to the user equipment, the user equipment will receive the second configuration information from the base station.

[0354] For example, the second configuration information is carried in the downlink control information (DCI).

[0355] For example, as described in the above embodiments, the SPS resource configuration information included in the SPS resource configuration pool may be, for example, an SPS frequency domain resource configuration pool, an SPS time domain resource configuration pool, an SPS modulation and coding scheme resource configuration pool, etc. For different SPS resource configuration information, the second configuration information is specifically carried in different fields in the DCI.

[0356] For example, when the SPS resource configuration information includes SPS frequency domain resource configuration information, the second configuration information is carried in the frequency domain resource configuration FDRA field of the DCI.

[0357] For example, when the SPS resource configuration information includes SPS time-domain resource configuration information, the second configuration information is carried in the DCI time-domain resource configuration TDRA field.

[0358] For example, when the SPS resource configuration information includes SPS modulation and coding scheme resource configuration information, the second configuration information is carried in the modulation and coding scheme MCS field in the DCI.

[0359] S703, determine the SPS resource configuration information corresponding to at least one index number based on the first configuration information and the second configuration information.

[0360] Specifically, based on at least one index number in the SPS resource configuration pool indicated in the second configuration information, the SPS resource configuration information corresponding to at least one index number is determined from the SPS resource configuration pool included in the first configuration information.

[0361] For example, if the second configuration information indicates index0 and index2 in the SPS resource configuration pool, then the determined SPS resource configuration information is the SPS resource configuration information corresponding to index0 (hereinafter referred to as SPS resource configuration 1) and the SPS resource configuration information corresponding to index2 (hereinafter referred to as SPS resource configuration 2).

[0362] S704, sequentially using the SPS resources corresponding to the SPS resource configuration information corresponding to at least one index number to receive data scheduled by the base station through SPS resources.

[0363] For example, taking the example given in step S703, when the order of at least one index number indicated in the second configuration information is index0 and index2, the user equipment receives the data scheduled by the base station through the SPS resources in the order of the SPS resource corresponding to SPS resource configuration 1 (hereinafter referred to as SPS resource 1) and the SPS resource corresponding to SPS resource configuration 2 (hereinafter referred to as SPS resource 2).

[0364] S705, after receiving SPS resource data corresponding to the SPS resource configuration information corresponding to the last index number in at least one index number, the base station repeatedly receives data scheduled by SPS resource by using the SPS resource configuration information corresponding to the SPS resource configuration information corresponding to at least one index number in sequence.

[0365] For example, taking the example given in step S704, after the user equipment receives data using SPS resource 2, it will repeatedly use SPS resource 1 corresponding to at least one index number of SPS resource configuration 1 to receive data scheduled by the base station through SPS resources in the above order, that is, it will use SPS resource 1, SPS resource 2, SPS resource 1, SPS resource 2... in a cyclical manner to receive data scheduled by the base station through SPS resources.

[0366] Therefore, the user equipment can repeatedly receive data scheduled by the base station through SPS resources by using the SPS resources corresponding to the SPS resource configuration information corresponding to at least one index number in the order indicated by the second configuration information, so that the SPS resources are matched with the data frames of XR services, thereby reducing the power consumption of the user equipment and avoiding reducing the system capacity of the base station.

[0367] That concludes the introduction to the configuration of downlink SPS resources. The following section, based on the embodiment corresponding to 15, introduces the configuration of uplink SPS resources.

[0368] For example, after receiving the first and second configuration information from the base station, the user equipment will send third configuration information to the base station. The third configuration information indicates at least one index number in the SPS resource configuration pool, and the order of the at least one index number.

[0369] Accordingly, after sending the third configuration information to the base station, the user equipment will send data to the base station in each SPS scheduling cycle using the SPS resources corresponding to the SPS resource configuration information corresponding to at least one index number in the order indicated in the third configuration information.

[0370] For example, after the user equipment sends third configuration information to the base station, the base station will receive the third configuration information from the user equipment.

[0371] Furthermore, it should be noted that in this embodiment, the third configuration information is carried in the uplink control information CG-UCI of the configuration authorization.

[0372] It is understood that the SPS resource configuration pool mentioned in this embodiment may be, for example, the SPS frequency domain resource configuration pool, SPS time domain resource configuration pool, SPS time-frequency resource configuration pool, SPS modulation and coding scheme resource configuration pool, etc. mentioned in the above embodiments.

[0373] For example, if the SPS resource configuration pool is an SPS time-frequency resource configuration pool, and the SPS resource configuration information is specifically SPS time-frequency resource configuration information, then the third configuration information is carried in the time-frequency resource configuration field in CG-UCI (e.g., the SPS resource config index in Table 5).

[0374] For example, in the scenario where the SPS resource configuration pool is the SPS time-domain resource configuration pool and the SPS resource configuration information is specifically the SPS time-domain resource configuration information, the third configuration information is carried in the time-domain resource configuration field in CG-UCI (e.g., the SPS TDRA config index in Table 6).

[0375] For example, in the scenario where the SPS resource configuration pool is an SPS frequency domain resource configuration pool and the SPS resource configuration information is specifically SPS frequency domain resource configuration information, the third configuration information is carried in the frequency domain resource configuration field in CG-UCI (e.g., the SPS FDRA config index in Table 7).

[0376] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the only limitation of this embodiment.

[0377] For example, in a scenario where a user equipment sends third configuration information to a base station, after receiving the third configuration information from the user equipment, the base station determines the SPS resource configuration information corresponding to at least one index number based on the first configuration information and the third configuration information. Then, it sequentially uses the SPS resources corresponding to the SPS resource configuration information corresponding to at least one index number to receive data scheduled by the user equipment through the SPS resources. After receiving data using the SPS resources corresponding to the SPS resource configuration information corresponding to the last index number among the at least one index number, the base station repeatedly sequentially uses the SPS resources corresponding to the SPS resource configuration information corresponding to at least one index number to receive data scheduled by the user equipment through the SPS resources.

[0378] Furthermore, it should be noted that, regarding the implementation scheme in the above embodiments where the base station sends both an SPS resource configuration pool (e.g., SPS frequency domain resource configuration pool / SPS time domain resource configuration pool / SPS modulation and coding scheme resource configuration pool / SPS time-frequency resource configuration pool) to the user equipment, and also sends an SPS resource activation pool (e.g., SPS frequency domain resource activation pool / SPS time domain resource activation pool / SPS modulation and coding scheme resource activation pool / SPS time-frequency resource activation pool) to the user equipment, in specific implementations, it can be achieved through... Figure 16 The process shown is implemented.

[0379] For example, see Figure 16 The process of semi-static scheduling for user equipment and base stations includes:

[0380] S801, send fourth configuration information to the user equipment. The fourth configuration information includes a semi-static scheduling SPS resource configuration pool. The SPS resource configuration pool includes one or more SPS resource configuration information and an index number corresponding to each SPS resource configuration information.

[0381] For example, after the base station sends the fourth configuration information to the user equipment, the user equipment will receive the fourth configuration information from the base station.

[0382] Furthermore, it should be noted that in this embodiment, the fourth configuration information is carried in the Radio Resource Control (RRC) signaling. That is, the base station sends the fourth configuration information to the user equipment through the RRC signaling, and the user equipment can parse the fourth configuration information from the received RRC signaling.

[0383] Understandably, the SPS resource configuration pool included in the fourth configuration information mentioned in this embodiment may be, for example, Figure 4 The corresponding embodiment mentions the SPS frequency domain resource configuration pool. For details on the specific form of the SPS frequency domain resource configuration pool, please refer to... Figure 4 The description of the corresponding embodiments is omitted here.

[0384] S802, send fifth configuration information to the user equipment. The fifth configuration information includes an SPS resource activation pool. The SPS resource activation pool includes one or more SPS resource configuration queues and an index number corresponding to each SPS resource configuration queue. Each SPS resource configuration queue indicates at least one index number in the SPS resource configuration pool and the order of the at least one index number.

[0385] It should be noted that, in order to ensure that the SPS resources corresponding to the configured cyclically used SPS resources are matched with diverse service scenarios, the base station also needs to send fifth configuration information to the user equipment. This fifth configuration information includes an SPS resource activation pool, which comprises one or more SPS resource configuration queues, and an index number corresponding to each SPS resource configuration queue. Furthermore, for each SPS resource configuration queue, it indicates at least one index number within the SPS resource configuration pool, as well as the order of these index numbers.

[0386] For example, in practical applications, the fifth configuration information includes, for instance, the SPS resource activation pool. Figure 6 The corresponding embodiment mentions the SPS frequency domain resource activation pool. For details on the specific form of the SPS frequency domain resource activation pool, please refer to... Figure 6 The description of the corresponding embodiments is omitted here.

[0387] Understandably, in a scenario where the base station sends the fifth configuration information to the user equipment, the user equipment will receive not only the fourth configuration information from the base station, but also the fifth configuration information.

[0388] For example, in practical applications, the fifth configuration information can also be carried in RRC signaling. That is, the base station sends the fifth configuration information to the user equipment through RRC signaling, and the user equipment can parse the fifth configuration information from the received RRC signaling.

[0389] Understandably, in practical applications, the fourth and fifth configuration information can be sent to the user equipment via the same RRC signaling.

[0390] S803 sends the sixth configuration information to the user equipment, which indicates the index number of an SPS resource configuration queue in the SPS resource activation pool.

[0391] For example, after the base station sends the sixth configuration information to the user equipment, the user equipment will receive the sixth configuration information from the base station.

[0392] For example, the sixth configuration information is carried in the downlink control information (DCI).

[0393] For example, as described in the above embodiments, the SPS resource configuration information included in the SPS resource configuration pool may be, for example, an SPS frequency domain resource configuration pool, an SPS time domain resource configuration pool, an SPS modulation and coding scheme resource configuration pool, etc. For different SPS resource configuration information, the sixth configuration information is specifically carried in different fields in the DCI.

[0394] For example, when the SPS resource configuration information includes SPS frequency domain resource configuration information, the sixth configuration information is carried in the frequency domain resource configuration FDRA field of the DCI.

[0395] For example, when the SPS resource configuration information includes SPS time-domain resource configuration information, the sixth configuration information is carried in the DCI time-domain resource configuration TDRA field.

[0396] For example, when the SPS resource configuration information includes SPS modulation and coding scheme resource configuration information, the sixth configuration information is carried in the modulation and coding scheme MCS field in the DCI.

[0397] S804, determine the SPS resource configuration information corresponding to at least one index number based on the fourth configuration information, the fifth configuration information and the sixth configuration information.

[0398] Understandably, in some implementations, the base station determines the SPS resource configuration information corresponding to at least one index number based on the fourth configuration information, the fifth configuration information, and the sixth configuration information. For example, it may be as follows: first, determine the SPS resource configuration queue in the SPS resource activation pool corresponding to the index number indicated by the sixth configuration information based on the fifth configuration information and the sixth configuration information; then, determine the SPS resource configuration information corresponding to at least one index number based on the fourth configuration information and the determined SPS resource configuration queue.

[0399] S805, sequentially using the SPS resources corresponding to the SPS resource configuration information corresponding to at least one index number to receive data scheduled by the base station through SPS resources.

[0400] S806, after receiving data using SPS resource configuration information corresponding to the last index number in at least one index number, repeatedly receive data scheduled by the base station using SPS resource configuration information corresponding to at least one index number in sequence.

[0401] For details on the implementation of steps S805 and S806, please refer to [link / reference]. Figure 15 The descriptions of steps S704 and S705 in the corresponding embodiments will not be repeated here.

[0402] Therefore, by introducing the SPS resource activation pool, at least one index number in the SPS resource configuration pool, and the order of at least one index number, can be configured into the SPS resource configuration queue in the SPS resource activation pool. Thus, at least one index number in the SPS resource configuration pool, and the order of at least one index number, can be determined based on the index number of an SPS resource configuration queue, thereby making it applicable to more business scenarios.

[0403] In addition, when the user equipment receives both the fourth and fifth configuration information, the content indicated by the sixth configuration information sent by the base station can be the index number corresponding to an SPS resource configuration queue in the SPS resource activation pool. In this way, the same field can be used to achieve the cyclic use of more SPS cycles, thus making it applicable to more service scenarios.

[0404] That concludes the introduction to the configuration of downlink SPS resources. Based on the embodiment corresponding to 16, the following section introduces the configuration of uplink SPS resources.

[0405] For example, after receiving the fourth, fifth, and sixth configuration information from the base station, the user equipment will send a seventh configuration information to the base station. The seventh configuration information indicates at least one index number in the SPS resource configuration pool, and the order of the at least one index number.

[0406] Accordingly, after sending the seventh configuration information to the base station, the user equipment will send data to the base station in each SPS scheduling cycle using the SPS resources corresponding to the SPS resource configuration information corresponding to at least one index number in the order indicated in the seventh configuration information.

[0407] For example, after the user equipment sends the seventh configuration information to the base station, the base station will receive the seventh configuration information from the user equipment.

[0408] Furthermore, it should be noted that in this embodiment, the seventh configuration information is carried in the uplink control information CG-UCI for configuration authorization.

[0409] It is understood that the SPS resource configuration pool mentioned in the seventh configuration information in this embodiment may be, for example, the SPS frequency domain resource configuration pool, SPS time domain resource configuration pool, SPS time-frequency resource configuration pool, SPS modulation and coding scheme resource configuration pool, etc. mentioned in the above embodiments.

[0410] For example, in the scenario where the SPS resource configuration pool is the SPS time-frequency resource configuration pool and the SPS resource configuration information is specifically the SPS time-frequency resource configuration information, the seventh configuration information is carried in the time-frequency resource configuration field in CG-UCI (e.g., the SPS resource config index in Table 5).

[0411] For example, in the scenario where the SPS resource configuration pool is the SPS time-domain resource configuration pool and the SPS resource configuration information is specifically the SPS time-domain resource configuration information, the seventh configuration information is carried in the time-domain resource configuration field in CG-UCI (e.g., the SPS TDRA config index in Table 6).

[0412] For example, in the scenario where the SPS resource configuration pool is an SPS frequency domain resource configuration pool and the SPS resource configuration information is specifically SPS frequency domain resource configuration information, the seventh configuration information is carried in the frequency domain resource configuration field in CG-UCI (e.g., the SPS FDRA config index in Table 7).

[0413] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the only limitation of this embodiment.

[0414] For example, in a scenario where a user equipment sends seventh configuration information to a base station, after receiving the seventh configuration information from the user equipment, the base station determines the SPS resource configuration information corresponding to at least one index number based on the first configuration information and the third configuration information. Then, it sequentially uses the SPS resources corresponding to the SPS resource configuration information corresponding to at least one index number to receive data scheduled by the user equipment through the SPS resources. After receiving data using the SPS resources corresponding to the SPS resource configuration information corresponding to the last index number among the at least one index number, the base station repeatedly sequentially uses the SPS resources corresponding to the SPS resource configuration information corresponding to at least one index number to receive data scheduled by the user equipment through the SPS resources.

[0415] In addition, it should be noted that, in order to Figure 15 Corresponding embodiments and Figure 16 The corresponding implementation can be applied to scenarios with basic wireless resources + public wireless resources, and the above-mentioned SPS resource configuration pool can also include public SPS resource configuration information.

[0416] For example, the public SPS resource configuration information includes at least one or more SPS time-frequency resource configuration information, and each SPS time-frequency resource configuration information includes SPS time-domain resource configuration information and SPS frequency-domain resource configuration information. The SPS time-domain resource configuration information and SPS frequency-domain resource configuration information correspond to the same index number, that is, SPS time-domain resource configuration information and SPS frequency-domain resource configuration information can be configured simultaneously through one index number.

[0417] Understandably, in scenarios where public SPS resource configuration information exists, in order for the user equipment to detect whether its demodulation reference signal (DMRS) exists in the SPS resource corresponding to the public SPS resource configuration information during each SPS scheduling cycle, and to determine whether to receive data scheduled by the base station through the SPS resource corresponding to the public SPS resource configuration information, the base station will also send enable information to the user equipment.

[0418] For example, the enabling information mentioned in this embodiment is used to instruct the user equipment to detect whether there is a demodulation reference signal (DMRS) of the user equipment in the SPS resources corresponding to the public SPS resource configuration information during each SPS scheduling cycle.

[0419] For example, after sending enable information to the user equipment, if the base station wants the user equipment A to receive data scheduled by the base station through the SPS resource corresponding to the public SPS resource configuration information 1 from the SPS resource corresponding to the public SPS resource configuration information 1, the base station will add the DMRS of user equipment A to the SPS resource corresponding to the public SPS resource configuration information 1.

[0420] Accordingly, after the base station sends the enable information to the user equipment, the user equipment will receive the enable information. In this way, in each SPS scheduling cycle, the user equipment will check whether its own DMRS is in the SPS resource corresponding to the public SPS resource configuration information.

[0421] Accordingly, if a user equipment's DMRS is detected in the SPS resource corresponding to the public SPS resource configuration information in each SPS scheduling cycle, then the user equipment will receive the data scheduled by the base station through the SPS resource corresponding to the public SPS resource configuration information. For example, if user equipment A detects its own DMRS in public SPS resource configuration information 1 in an SPS scheduling cycle, user equipment A will receive the data scheduled by the base station through the SPS resource corresponding to public SPS resource configuration information 1.

[0422] Therefore, by introducing public SPS resource configuration information, it is possible to select SPS resources of different sizes corresponding to the public SPS resource configuration information based on the SPS resources corresponding to the SPS resource configuration information, thereby realizing the scheduling of SPS resources of different sizes and better adapting to the diversified needs of services with periodic characteristics for wireless resources.

[0423] Through the above description of the embodiments, those skilled in the art will clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0424] In the several embodiments provided in this example, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0425] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0426] Furthermore, in each embodiment of this invention, the functional units can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0427] If the integrated unit is implemented as 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 this embodiment, in essence, or the part that contributes to the prior art, or all or part of the 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 cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments. The aforementioned storage medium includes various media capable of storing program code, such as flash memory, portable hard disk, read-only memory, random access memory, magnetic disk, or optical disk.

[0428] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A semi-static scheduling method, characterized in that, Applied to user equipment, the method includes: The first configuration information is received from the base station. The first configuration information includes a semi-static scheduling SPS resource configuration pool. The SPS resource configuration pool includes one or more SPS resource configuration information and an index number corresponding to each SPS resource configuration information. Receive second configuration information from the base station, the second configuration information indicating at least one index number in the SPS resource configuration pool, and the order of the at least one index number; Based on the first configuration information and the second configuration information, determine the SPS resource configuration information corresponding to the at least one index number; The base station receives data scheduled by SPS resources in the order described above, using the SPS resources corresponding to the SPS resource configuration information corresponding to the at least one index number; After receiving data using SPS resources corresponding to the SPS resource configuration information corresponding to the last of the at least one index number, the base station repeatedly receives data scheduled by SPS resources by using SPS resources corresponding to the SPS resource configuration information corresponding to the at least one index number in the same order.

2. The method according to claim 1, characterized in that, The second configuration information is carried in the downlink control information (DCI).

3. The method according to claim 2, characterized in that, The SPS resource configuration information includes SPS frequency domain resource configuration information; The second configuration information is carried in the Frequency Domain Resource Configuration (FDRA) field of the DCI.

4. The method according to claim 2, characterized in that, The SPS resource configuration information includes SPS time-domain resource configuration information; The second configuration information is carried in the Time Domain Resource Configuration (TDRA) field of the DCI.

5. The method according to claim 2, characterized in that, The SPS resource configuration information includes SPS modulation and coding scheme resource configuration information; The second configuration information is carried in the modulation and coding scheme (MCS) field of the DCI.

6. The method according to any one of claims 1 to 5, characterized in that, The SPS resource configuration pool also includes public SPS resource configuration information; The public SPS resource configuration information includes at least one or more SPS time-frequency resource configuration information.

7. The method according to claim 6, characterized in that, The method further includes: The user equipment receives enable information from the base station, which instructs the user equipment to detect whether the demodulation reference signal (DMRS) of the user equipment exists in the SPS resources corresponding to the public SPS resource configuration information during each SPS scheduling cycle.

8. The method according to claim 7, characterized in that, After receiving the enable information from the base station, the method further includes: In each SPS scheduling cycle, check whether the user equipment's DMRS is present in the SPS resources corresponding to the public SPS resource configuration information; When the DMRS of the user equipment is detected in the SPS resource corresponding to the public SPS resource configuration information in each SPS scheduling cycle, the base station receives the data scheduled by the SPS resource corresponding to the public SPS resource configuration information.

9. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Send third configuration information to the base station, the third configuration information indicating at least one index number in the SPS resource configuration pool, and the order of the at least one index number; Data is sent to the base station in the order described, using the SPS resources corresponding to the SPS resource configuration information corresponding to the at least one index number.

10. The method according to claim 9, characterized in that, The third configuration information is carried in the uplink control information CG-UCI for configuration authorization.

11. The method according to claim 10, characterized in that, When the SPS resource configuration information includes SPS frequency domain resource configuration information, the third configuration information is carried in the frequency domain resource configuration field of CG-UCI; or, When the SPS resource configuration information includes SPS time-domain resource configuration information, the third configuration information is carried in the time-domain resource configuration field of CG-UCI; or, When the SPS resource configuration information includes SPS modulation and coding scheme resource configuration information, the third configuration information is carried in the modulation configuration coding field of CG-UCI; or, When the SPS resource configuration information includes SPS time-frequency resource configuration information, the third configuration information is carried in the time-frequency resource configuration field of CG-UCI.

12. A semi-static scheduling method, characterized in that, Applied to a base station, the method includes: Send first configuration information to the user equipment. The first configuration information includes a semi-static scheduling SPS resource configuration pool. The SPS resource configuration pool includes one or more SPS resource configuration information and an index number corresponding to each SPS resource configuration information. Send second configuration information to the user equipment, the second configuration information indicating at least one index number in the SPS resource configuration pool, and the order of the at least one index number; Wherein, the first configuration information and the second configuration information are used to indicate SPS resource configuration information corresponding to the at least one index number; on the SPS resource corresponding to the SPS resource configuration information corresponding to the at least one index number, the data scheduled by the base station through SPS resource is received in the order of the at least one index number; after the SPS resource corresponding to the SPS resource configuration information corresponding to the last of the at least one index number is used to receive data, the data scheduled by the base station through SPS resource is repeatedly received in the order of the at least one index number on the SPS resource corresponding to the SPS resource configuration information corresponding to the at least one index number.

13. The method according to claim 12, characterized in that, The SPS resource configuration pool also includes public SPS resource configuration information; The public SPS resource configuration information includes at least one or more SPS time-frequency resource configuration information.

14. The method according to claim 13, characterized in that, The method further includes: An enable message is sent to the user equipment, which instructs the user equipment to check whether the demodulation reference signal (DMRS) of the user equipment is present in the SPS resources corresponding to the public SPS resource configuration information during each SPS scheduling cycle.

15. The method according to any one of claims 12 to 14, characterized in that, The method further includes: Receive third configuration information from the user equipment, the third configuration information indicating at least one index number in the SPS resource configuration pool, and the order of the at least one index number; Based on the first configuration information and the third configuration information, determine the SPS resource configuration information corresponding to the at least one index number; The user equipment receives data scheduled by SPS resources in the order described above, using the SPS resources corresponding to the SPS resource configuration information corresponding to the at least one index number; After receiving data using SPS resources corresponding to the SPS resource configuration information corresponding to the last of the at least one index number, the user equipment receives data scheduled by SPS resources by using SPS resources in the same order.

16. A semi-static scheduling method, characterized in that, Applied to user equipment, the method includes: The fourth configuration information is received from the base station. The fourth configuration information includes a semi-static scheduling SPS resource configuration pool. The SPS resource configuration pool includes one or more SPS resource configuration information and an index number corresponding to each SPS resource configuration information. The fifth configuration information is received from the base station. The fifth configuration information includes an SPS resource activation pool. The SPS resource activation pool includes one or more SPS resource configuration queues and an index number corresponding to each SPS resource configuration queue. Each SPS resource configuration queue indicates at least one index number in the SPS resource configuration pool and the order of the at least one index number. The sixth configuration information is received from the base station, which indicates the index number corresponding to an SPS resource configuration queue in the SPS resource activation pool; Based on the fourth configuration information, the fifth configuration information, and the sixth configuration information, determine the SPS resource configuration information corresponding to the at least one index number; The base station receives data scheduled by SPS resources in the order described above, using the SPS resources corresponding to the SPS resource configuration information corresponding to the at least one index number; After receiving data using SPS resources corresponding to the SPS resource configuration information corresponding to the last of the at least one index number, the base station repeatedly receives data scheduled by SPS resources by using SPS resources corresponding to the SPS resource configuration information corresponding to the at least one index number in the same order.

17. The method according to claim 16, characterized in that, The step of determining the SPS resource configuration information corresponding to the at least one index number based on the fourth configuration information, the fifth configuration information, and the sixth configuration information includes: Based on the fifth and sixth configuration information, determine the SPS resource configuration queue in the SPS resource activation pool that corresponds to the index number indicated by the sixth configuration information; Based on the fourth configuration information and the determined SPS resource configuration queue, determine the SPS resource configuration information corresponding to the at least one index number.

18. A semi-static scheduling method, characterized in that, Applied to a base station, the method includes: Send fourth configuration information to the user equipment. The fourth configuration information includes a semi-static scheduling SPS resource configuration pool. The SPS resource configuration pool includes one or more SPS resource configuration information and an index number corresponding to each SPS resource configuration information. Send fifth configuration information to the user equipment. The fifth configuration information includes an SPS resource activation pool. The SPS resource activation pool includes one or more SPS resource configuration queues and an index number corresponding to each SPS resource configuration queue. Each SPS resource configuration queue indicates at least one index number in the SPS resource configuration pool and the order of the at least one index number. Send a sixth configuration message to the user equipment, the sixth configuration message indicating the index number corresponding to an SPS resource configuration queue in the SPS resource activation pool; Wherein, the fourth configuration information, the fifth configuration information, and the sixth configuration information are used to indicate the SPS resource configuration information corresponding to the at least one index number; on the SPS resource corresponding to the SPS resource information corresponding to the at least one index number, the data scheduled by the base station through SPS resource is received in the order of the at least one index number; after the SPS resource corresponding to the SPS resource configuration information corresponding to the last of the at least one index number is used to receive data, the data scheduled by the base station through SPS resource is repeatedly received in the order of the at least one index number on the SPS resource corresponding to the SPS resource configuration information corresponding to the at least one index number.

19. A user equipment, characterized in that, Used to perform the semi-static scheduling method as described in any one of claims 1 to 11, or to perform the semi-static scheduling method as described in claim 16 or 17.

20. A base station, characterized in that, Used to perform the semi-static scheduling method as described in any one of claims 12 to 15, or to perform the semi-static scheduling method as described in claim 18.

21. A communication system, characterized in that, include: The user equipment as described in claim 19 and the base station as described in claim 20.

Images