CN110475369A - A kind of business scheduling method, terminal and the network equipment - Google Patents

Abstract

The embodiment of the present invention provides a kind of business scheduling method, terminal and the network equipment, is related to field of communication technology, can not effectively carry out URLLC traffic scheduling caused by the DCI due to not being used for URLLC business in the prior art to solve the problem of.This method comprises:, according to instruction information, determining that the first DCI is the DCI for the highly reliable linking URL LC business of low time delay in the case where the terminal monitoring to the first DCI；Wherein, it is the DCI for the URLLC business that the instruction information, which is used to indicate the first DCI,；The URLLC business is dispatched according to the first DCI.

Description

A service scheduling method, terminal and network equipment

technical field

The present invention relates to the field of communication technology, in particular to a service scheduling method, terminal and network equipment.

Background technique

At present, ITU-R (International Telecommunication Union Radiocommunication Bureau) has determined that the future 5G communication system has the following three main application scenarios: eMBB (enhanced Mobile Broadband, enhanced mobile broadband), URLLC (Ultra-Reliable and Low Latency Communications, Low latency and highly reliable connection), mMTC (massiveMachine Type Communications, large-scale Internet of Things). In the prior art, the downlink control information (Downlink Control Indicator, DCI) sent by the base station to the terminal is mainly the DCI used for the eMBB service in the eMBB scenario, so that after the terminal monitors the DCI sent by the base station for the eMBB service, it will The eMBB service can be scheduled according to the DCI.

However, there is currently no relevant DCI design for the URLLC service used in the URLLC scenario, and there is no effective scheduling scheme for the URLLC service.

Contents of the invention

Embodiments of the present invention provide a service scheduling method, terminal and network equipment to solve the problem in the prior art that the URLLC service cannot be effectively scheduled due to the lack of DCI for the URLLC service.

In order to solve the problems of the technologies described above, the present invention is achieved in that:

In the first aspect, an embodiment of the present invention provides a service scheduling method, which is applied to a terminal, and the method includes:

When the terminal monitors the first DCI, according to the indication information, determine that the first DCI is a DCI for low-latency and high-reliability connection URLLC services;

Wherein, the indication information is used to indicate that the first DCI is the DCI used for the URLLC service;

Scheduling the URLLC service according to the first DCI.

In a second aspect, an embodiment of the present invention provides a service scheduling method, which is applied to a network device, and the method includes:

generating a first DCI;

sending the first DCI to the terminal;

Wherein, the first DCI is a DCI for URLLC service with low latency and high reliability connection, and the first DCI is used to instruct the terminal to schedule the URLLC service according to the first DCI.

In a third aspect, an embodiment of the present invention provides a terminal, including:

A determining module, configured to determine, according to the indication information, that the first DCI is a DCI for low-latency and high-reliability connection URLLC services when the terminal monitors the first DCI;

Wherein, the indication information is used to indicate that the first DCI is the DCI used for the URLLC service;

A scheduling module, configured to schedule the URLLC service according to the first DCI determined by the determining module.

In a fourth aspect, an embodiment of the present invention provides a network device, including:

a generating module, configured to generate a first DCI;

a first sending module, configured to send the first DCI generated by the generating module to a terminal;

Wherein, the first DCI is a DCI for URLLC service with low latency and high reliability connection, and the first DCI is used to instruct the terminal to schedule the URLLC service according to the first DCI.

In the fifth aspect, an embodiment of the present invention provides a terminal, including a processor, a memory, and a computer program stored in the memory and operable on the processor. When the computer program is executed by the processor, The steps of the service scheduling method as described in the first aspect are realized.

In a sixth aspect, an embodiment of the present invention provides a network device, including a processor, a memory, and a computer program stored on the memory and operable on the processor. When the computer program is executed by the processor, The steps of the service scheduling method described in the second aspect are realized.

In a seventh aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the above service scheduling method are implemented.

In the embodiment of the present invention, when the terminal monitors the first DCI, the terminal can directly determine that the first DCI is the DCI for URLLC service according to the indication information, so that the terminal can use the proprietary URLLC service The first DCI is used to effectively schedule URLLC services, improving communication efficiency and effectiveness.

Description of drawings

FIG. 1 is a schematic structural diagram of a possible communication system involved in an embodiment of the present invention;

FIG. 2 is one of the schematic flow diagrams of a service scheduling method provided by an embodiment of the present invention;

FIG. 3 is the second schematic flow diagram of a service scheduling method provided by an embodiment of the present invention;

FIG. 4 is the third schematic flow diagram of a service scheduling method provided by an embodiment of the present invention;

FIG. 5 is the fourth schematic flow diagram of a service scheduling method provided by an embodiment of the present invention;

FIG. 6 is the fifth schematic flow diagram of a service scheduling method provided by an embodiment of the present invention;

FIG. 7 is one of the schematic structural diagrams of a terminal provided by an embodiment of the present invention;

FIG. 8 is one of the schematic structural diagrams of a network device provided by an embodiment of the present invention;

FIG. 9 is a second structural schematic diagram of a terminal provided by an embodiment of the present invention;

FIG. 10 is a second schematic structural diagram of a network device provided by an embodiment of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some of the embodiments of the present invention, but not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

Some terms involved in the present invention are explained below for the convenience of readers:

1. Downlink Control Indicator (DCI)

In the LTE system, a downlink control channel (PDCCH) is sent in a downlink subframe, and the PDCCH and a physical downlink shared channel (PDSCH) form a time division multiplexing (TDM) multiplexing relationship. The PDCCH is sent through the first 1-3 Orthogonal Frequency Division Multiplexing (OFDM) symbols of a downlink subframe. Generally, the basic unit of the time-frequency resource of the DCI carried on the PDCCH is also a control channel element (control channel element, CCE). The DCI may be transmitted using different aggregation levels (aggregation level, AL). The aggregation level refers to how many CCEs the DCI is carried on. The aggregation level can be, for example but not limited to, 1, 2, 4, 8, 16, 32, etc. For example, if the aggregation level is 2, it means that the DCI is carried on two CCEs.

2. DCI blind detection (blind decode)

As mentioned above, DCI can be in the first 1 to 3 symbols of a subframe, and DCI can be transmitted with different aggregation levels. However, since the PDCCH is an instruction sent by the base station, the UE has not received other information except some system information before, so the UE does not know the number, location, and DCI of the Control Channel Element (CCE) occupied by it. format (DCI format), and the DCI aggregation level is also unknown, therefore, the user equipment (User Equipment, UE) needs to detect possible DCI time-frequency resource positions and aggregation levels through blind detection, so as to receive the DCI. That is, the UE detects the downlink control channel PDCCH sent by the base station in a blind detection manner to acquire downlink control information DCI.

In order to reduce the complexity of UE blind detection, two kinds of search spaces are defined in the LTE system, namely the common search space (Common Search Space, CSS) and the UE-specific search space (UE-specific Search Space, UESS), wherein, the search The unit of the size of the space is the number of CCEs.

3. Control Resource Set (CORESET)

CORESET is a set of time-frequency resources introduced in the 5G NR system, that is to say, the terminal detects the downlink control channel (PDCCH) in the corresponding CORESET. CORESET is composed of a set of REGs.

Exemplarily, the configuration information of CORESET can be notified through one or more of the following combinations:

The configuration information of CORESET can be notified through high-level signaling; or,

CORESET configuration information can be sent through broadcast channels, system information, etc.; or,

The configuration information of CORESET can be pre-defined according to one or more information such as system bandwidth, subcarrier spacing, antenna configuration, and carrier frequency.

The CORESET configuration information herein includes but is not limited to at least one of the following information: CORESET time-frequency resource information, the CORESET time-frequency resource information includes: CORESET frequency resource information (such as PRB number, time-frequency location, etc.) and CORESET time-frequency resource information Domain resource information (such as the number of OFDM symbols), the set of PDCCH aggregation levels that require blind detection in CORESET, the number of blind PDCCH candidate resources for each PDCCH aggregation level that requires blind detection in CORESET, and the PDCCH DCI that requires blind detection in CORESET Parameters (eg, DCI format, DCI length), etc.

Generally, a CORESET includes at least one search space, and the search space in the CORESET can be considered as UESS.

4. Other terms

The term "and/or" in this article is just an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist simultaneously, and there exists alone B these three situations. In addition, the character "/" in this paper generally indicates that the contextual objects are an "or" relationship; in the formula, the character "/" indicates that the contextual objects are a "division" relationship. "Plurality" herein refers to two or more, if not stated otherwise.

In order to clearly describe the technical solutions of the embodiments of the present invention, in the embodiments of the present invention, words such as "first" and "second" are used to distinguish the same or similar items with basically the same function or effect. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order.

It should be noted that, in the embodiments of the present invention, words such as "exemplary" or "for example" are used for example, illustration or description. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present invention shall not be construed as being more preferred or more advantageous than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete manner.

The technical solutions provided by the present application will be introduced below in conjunction with the accompanying drawings.

The technical solutions provided by the present invention can be applied to various communication systems, for example, 5G communication systems, future evolution systems or multiple communication fusion systems and the like. It can include a variety of application scenarios, such as machine to machine (M2M), D2M, macro-micro communication, enhanced mobile Internet (enhance mobile broadband, eMBB), ultra-reliable & low-latency communication (ultra reliable&low latency communication (uRLLC) and massive machine type communication (mMTC) and other scenarios. These scenarios include but are not limited to: communication between terminals, or communication between network devices, or communication between network devices and terminals. The embodiments of the present invention may be applied to communication between a network device and a terminal, or between a terminal and a terminal, or between a network device and a network device in a 5G communication system.

Fig. 1 shows a possible structural diagram of a communication system involved in an embodiment of the present invention. As shown in FIG. 1 , the communication system includes at least one network device 100 (only one is shown in FIG. 1 ) and one or more terminals 200 connected to each network device 100 .

Wherein, the aforementioned network device 100 may be a base station, a core network device, a transmission and reception point (Transmission and Reception Point, TRP), a relay station or an access point, and the like. The network device 100 may be a base transceiver station (Base Transceiver Station, BTS) in a Global System for Mobile communication (GSM) or Code Division Multiple Access (CDMA) network, or a wideband code The NB (NodeB) in Division Multiple Access (Wideband Code Division Multiple Access, WCDMA) may also be the eNB or eNodeB (evolutional NodeB) in LTE. The network device 100 may also be a wireless controller in a cloud radio access network (CloudRadio Access Network, CRAN) scenario. The network device 100 may also be a network device in a 5G communication system or a network device in a future evolution network. However, the wording does not constitute a limitation of the present invention.

The terminal 200 can be a wireless terminal or a wired terminal. The wireless terminal can be a device that provides voice and/or other business data connectivity to the user, a handheld device with a wireless communication function, a computing device, or other processing devices connected to a wireless modem. Devices, in-vehicle devices, wearable devices, terminals in the future 5G network or terminals in the future evolved PLMN network, etc. The wireless terminal can communicate with one or more core networks via the radio access network (Radio Access Network, RAN), and the wireless terminal can be a mobile terminal, such as a mobile phone (or called a "cellular" phone) and a computer with a mobile terminal , for example, may be portable, pocket, handheld, computer built-in or vehicle-mounted mobile devices that exchange voice and/or data with the wireless access network, as well as Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (Session Initiation Protocol, SIP) phone, Wireless Local Loop (Wireless Local Loop, WLL) station, Personal Digital Assistant (Personal Digital Assistant, PDA) and other equipment, and the wireless terminal can also be a mobile device, UE, UE terminal, Access terminal, wireless communication device, terminal unit, terminal station, mobile station (Mobile Station), mobile station (Mobile), remote station (Remote Station), remote station, remote terminal (Remote Terminal), subscriber unit (SubscriberUnit), Subscriber station (Subscriber Station), user agent (User Agent), terminal device, etc. As an example, in the embodiment of the present invention, FIG. 1 shows that the terminal is a mobile phone as an example.

Fig. 2 shows a schematic flowchart of a service scheduling method provided by an embodiment of the present invention. As shown in Fig. 2, the service scheduling method may include:

S201: The network device generates a first DCI.

In the embodiment of the present invention, the above-mentioned first DCI is a DCI for the URLLC service, and the above-mentioned first DCI is used to instruct the terminal to schedule the URLLC service according to the first DCI.

S202: The network device sends the first DCI to the terminal.

Correspondingly, the peer terminal receives the first DCI sent by the network device.

The network device in the embodiment of the present invention may be a network device in the communication system shown in FIG. 1 , for example, a base station; the terminal in the embodiment of the present invention may be a terminal in the communication system shown in FIG. 1 .

S203: When the terminal detects the first DCI, the terminal determines, according to the indication information, that the first DCI is the DCI used for the URLLC service.

In the embodiment of the present invention, the above indication information is used to indicate that the first DCI is a DCI for the URLLC service.

S204: The terminal schedules the URLLC service according to the first DCI.

Exemplarily, the embodiment of the present invention can implement the service scheduling method provided by the present invention through the following four implementation manners.

First possible implementation:

In this implementation, the network device redesigns some domains of the existing DCI on the basis of the existing DCI for the eMBB service, so that the redesigned DCI can meet the requirements of the URLLC service, and the redesigned DCI DCI used as URLLC service. Generally, if the redesigned DCI wants to meet the requirements of the URLLC service, the payload size of the redesigned DCI needs to be greater than or equal to the payload size of the DCI used for the eMBB service. In this scenario, the network device can be used for eMBB The field values of some fields in the DCI of the service are set as predetermined thresholds to indicate to the terminal that the DCI is the DCI for the URLLC service.

Optionally, as shown in FIG. 3, in the embodiment of the present invention, the above S201 specifically includes the following steps:

S201a1: The network device generates the second DCI.

Wherein, the above-mentioned second DCI is the DCI used for the eMBB service.

S201a2: The network device sets a field value of a preset field in the second DCI as a predetermined threshold A, and generates the first DCI.

Wherein, the above-mentioned payload size of the first DCI is equal to the above-mentioned payload size of the second DCI.

In the embodiment of the present invention, after the network device sets the field value of the preset field in the second DCI to a predetermined threshold A, if the load size of other fields in the second DCI except the preset field is greater than the specified Depending on the load size of the DCI of the URLLC service, the network device will set the field values of some fields in the second DCI other than the preset field to the predetermined threshold B, because the predetermined threshold B is not interpreted by the terminal side. , so that the payload size of the DCI actually used for the URLLC service in the second DCI is equal to the specified payload size of the DCI used for the URLLC service. Of course, if the load size of other domains in the second DCI except the preset domain is equal to the DCI load size used for URLLC service, the network device may directly use the second DCI with the domain value reset as the first DCI.

For example, assuming that the payload size of the second DCI is 40 bits, and the number of bits of the preset field in the second DCI is 8 bits, at this time, the payload size of other fields except the preset field in the second DCI is 32 bits (40-8 =32), since the DCI load size used for the URLLC service is 25bit, 32>25, then the number of 0s that the network device needs to fill in fields other than the preset field in the second DCI is 32-25=7 . In this way, the payload size of the first DCI obtained finally is the same as the payload size of the second DCI.

It should be noted that the position of the DCI payload used for the URLLC service in the DCI may be pre-configured by the network device.

For example, if the payload size of the DCI used for the URLLC service is set to C, the position of the above-mentioned DCI payload used for the URLLC service in the DCI can be: the DCI selected in order from front to back that meets the predetermined condition The position of the field, or the position of the field in the DCI excluding the CRC and the preset field selected from the back to the front and satisfying the predetermined condition, or other predefined positions in the DCI. Wherein, the above-mentioned domains that meet the predetermined conditions selected in order from front to back refer to: when the loads of the domains in the DCI are accumulated sequentially from front to back until the accumulated load size is equal to C, all domains corresponding to the accumulated load; the above The domains that meet the predetermined conditions selected in the order from the back to the front refer to: when the loads of domains outside the CRC and preset domains in the DCI are accumulated from the back to the front until the accumulated load size is equal to C, the accumulated load All corresponding domains.

It should be noted that, when the base station schedules the DCI for the eMBB service, it will not use the above-mentioned state where the preset field is set to the predetermined threshold A. Therefore, when the terminal decodes the DCI and finds that the field values of the preset fields in the DCI are the same as the preset threshold A, the terminal can determine that the DCI is the DCI for the URLLC service based on the field values of these preset fields.

For example, the following Table 1 is used to illustrate the field definition of the field in the downlink fallback (fallback) DCI. Wherein, the fallbackDCI is the DCI used for the eMBB service.

Table 1

The English abbreviations involved in Table 1 are as follows: Physical Downlink Shared Channel (Physical Downlink Shared Channel, PDSCH); Hybrid Automatic Repeat reQuest (Hybrid Automatic Repeat reQuest, HARQ); Physical Uplink Control Channel (Physical Uplink Control CHannel, PUCCH ); Transmission Control Protocol (Transmission Control Protocol, TCP).

Exemplarily, the network device may reset all field values of the TPC command for PUCCH field, PUCCHresource indicator field, and PDSCH-to-HARQ feedback timing indicator field before the CRC to predefined values, for example, all are set to 0. For example, the field value 2 of the TPC command for PUCCH field is reset to 00, the field value 3 of the PUCCHresource indicator field is reset to 000, and the field value 3 of the PDSCH-to-HARQ feedback timing indicator field is reset to 000.

Optionally, as shown in FIG. 3, in combination with the above S201a1 and S201a2, the above indication information is the field value of the preset field in the first DCI, and the terminal may, according to the field value of the preset field in the first DCI, to determine whether the first DCI is a DCI for URLLC services. Specifically, the above S203 specifically includes the following steps:

S203a: If the payload size of the first DCI is equal to the payload size of the second DCI, and the field value of the above-mentioned preset field is the same as the predetermined threshold A, then the terminal determines that the first DCI is a DCI for URLLC service.

Wherein, the above-mentioned second DCI is the DCI used for the eMBB service.

In the embodiment of the present invention, when the terminal detects a first DCI, the terminal can decode the first DCI, and obtain the field values of the preset fields in the first DCI, if the terminal finds that these field values are consistent with a preset The defined preset threshold A is the same, then the terminal can consider the first DCI as a DCI for URLLC service, and at this time, the field values of other fields in the first DCI can be set according to the field values of the DCI for URLLC service Interpretation of meaning.

Second possible implementation:

In this implementation, the network device can configure a URLLC service-specific radio network temporary identity (Radio Network Tempory Identity, RNTI) for the terminal, that is, use different RNTIs to distinguish DCIs of different services, and the terminal can use the first DCI The corresponding RNTI is used to determine whether the first DCI is a DCI for URLLC services.

Optionally, as shown in FIG. 4, in the embodiment of the present invention, the above S201 specifically includes the following steps:

S201b1: The network device generates a third DCI.

Wherein, the above-mentioned third DCI is the DCI used for the URLLC service.

S201b2: The network device uses the RNTI corresponding to the URLLC service to scramble the CRC code in the third DCI to generate the first DCI.

In the embodiment of the present invention, the RNTI corresponding to the aforementioned URLLC service may be predefined, that is, stipulated in the protocol, or sent to the terminal by the network device, which is not limited in the present invention.

Optionally, as shown in FIG. 4, in the embodiment of the present invention, the above S203 specifically includes the following steps:

S203b1: The terminal uses the RNTI corresponding to the URLLC service to descramble the first DCI to obtain a CRC code.

S203b2: The terminal performs a CRC check on the CRC code, and if the check passes, determines that the first DCI is the DCI used for the URLLC service.

In the embodiment of the present invention, the network device configures different RNTIs for different services, so that different RNTIs can be used to distinguish DCIs of different services. In this way, after the network device encodes the DCI of the corresponding service, it can use the proprietary RNTI corresponding to the service to scramble the CRC of the DCI, and send the scrambled DCI to the terminal. After the terminal detects the DCI, If the terminal receives the RNTI of the target service sent by the network device (for example, the RNTI corresponding to the URLLC service), it can use the RNTI to descramble the DCI. If the verification passes, it means that the DCI is the DCI of the target service , if the terminal does not receive the RNTI of the target service sent by the network device, the terminal may use the RNTI of a different service to descramble the DCI, and if the verification passes, it means that the DCI is the DCI of the service corresponding to the RNTI.

A third possible implementation:

In this implementation, the network device can allocate an independent CORESET for the control channel of the URLLC service, that is, the DCI sent under the CORESET is all DCI for the URLLC service, so that after the terminal detects the DCI in the CORESET, it can The DCI is directly determined as the DCI used for the URLLC service.

Optionally, as shown in FIG. 5, in the embodiment of the present invention, the above indication information is CORESET configuration information, and the configuration information is used to instruct the terminal to monitor DCI in the CORESET, and the DCI in the CORESET is used for DCI of the URLLC service. Specifically, in the embodiment of the present invention, S202 specifically includes the following steps:

S202c1: The network device sends the first DCI to the terminal on the CORESET.

Further, as shown in FIG. 5, in the embodiment of the present invention, before S203, the method includes the following steps:

S202c2: The network device sends CORESET configuration information to the terminal.

Correspondingly, the peer terminal receives the CORESET configuration information sent by the network device to the terminal.

S202c3: The terminal monitors on the CORESET the first DCI sent by the network device on the CORESET according to the configuration information.

A fourth possible implementation:

This implementation is implemented on the basis of the third possible implementation. Specifically, assuming that a CORESET includes three search spaces, the network device can allocate an independent search space in the CORESET for the control channel of the URLLC service, namely The DCIs sent in the search space are all DCIs for URLLC services, so that after the terminal detects the DCI in the search space in the CORESET, it can directly determine that the DCI is the DCI for URLLC services.

Optionally, as shown in FIG. 6 , in the embodiment of the present invention, the above CORESET configuration information is specifically used to instruct the terminal to monitor DCI on a predetermined search space in the CORESET.

Specifically, in the embodiment of the present invention, S202c1 specifically includes the following steps:

S202d1: The network device sends the first DCI to the terminal on the predetermined search space in the CORESET.

Further, in the embodiment of the present invention, the above S202c3 specifically includes the following steps:

S202d2: The terminal monitors the first DCI sent by the network device on the predetermined search space of the CORESET according to the configuration information.

Compared with the above third possible implementation manner, the fourth possible implementation manner provides a scheme of allocating a CORESET independent search space for the URLLC service, which can further narrow the scope of terminal blind detection.

In the service scheduling method provided by the embodiment of the present invention, after the network device generates the first DCI for the URLLC service, it sends the first DCI to the terminal, and the terminal can determine it directly according to the indication information when it monitors the first DCI The first DCI is DCI for URLLC services, so that the terminal can effectively schedule URLLC services according to the dedicated first DCI for URLLC services, improving communication efficiency and performance.

It should be noted that the first DCI designed for the URLLC service in the embodiment of the present invention can be used for uplink scheduling or downlink scheduling, which is not limited in the present invention.

As shown in FIG. 7, an embodiment of the present invention provides a terminal 300, the terminal 300 includes: a determination module 301 and a scheduling module 302, wherein:

The determining module 301 is configured to, when the terminal monitors the first DCI, determine that the first DCI is a DCI for URLLC services according to indication information; wherein, the above indication information is used to indicate that the first DCI is for URLLC services DCI.

The scheduling module 302 is configured to schedule URLLC services according to the first DCI determined by the determining module 301 .

Optionally, the above-mentioned indication information is a field value of a preset field in the first DCI; the above-mentioned determining module 301 is specifically configured to: if the payload size of the first DCI is equal to the payload size of the second DCI, and the preset field If the domain value is the same as the predetermined threshold, it is determined that the first DCI is the DCI for the URLLC service; wherein, the above-mentioned second DCI is the DCI for the eMBB service.

Optionally, the above indication information is configuration information of the control resource set CORESET, and the configuration information is used to instruct the terminal to monitor DCI in the CORESET, and the DCI in the CORESET is the DCI used for the URLLC service.

Optionally, as shown in FIG. 7, the terminal further includes: a receiving module 303 and a monitoring module 304, wherein:

The receiving module 303 is configured to receive CORESET configuration information sent by the network device to the terminal; the monitoring module 304 is configured to monitor on the CORESET the first DCI sent by the network device on the CORESET according to the configuration information received by the receiving module.

Optionally, the above configuration information is specifically used to instruct the terminal to monitor the DCI on the predetermined search space in CORESET; the monitoring module 304 is specifically used to: monitor the network device on the predetermined search space of CORESET according to the configuration information received by the receiving module A first DCI sent over a predetermined search space.

In the terminal provided by the embodiment of the present invention, when the terminal monitors the first DCI, it can directly determine that the first DCI is the DCI for URLLC service according to the indication information, so that the terminal can use the proprietary URLLC service The first DCI is used to effectively schedule URLLC services and improve communication efficiency and effectiveness.

The terminal provided by the embodiment of the present invention can implement the process shown in any one of FIG. 2 to FIG. 6 in the above method embodiment, and to avoid repetition, details are not repeated here.

FIG. 8 is a schematic diagram of a hardware structure of a network device implementing an embodiment of the present invention. The network device 400 includes: a generating module 401 and a first sending module 402, wherein:

A generating module 401, configured to generate a first DCI.

The first sending module 402 is configured to send the first DCI generated by the generating module 401 to the terminal; wherein, the above-mentioned first DCI is a DCI for URLLC services, and the above-mentioned first DCI is used to instruct the terminal to schedule URLLC according to the first DCI business.

Optionally, the above-mentioned generation module is specifically configured to: generate the second DCI, set the field value of the preset field in the second DCI to a predetermined threshold, and generate the first DCI; wherein, the second DCI is used for the eMBB service For DCI, the payload size of the above-mentioned first DCI is equal to the payload size of the second DCI.

Optionally, as shown in FIG. 8, the network device 400 further includes: a second sending module 403, where:

The second sending module 403 is configured to send configuration information of the control resource set CORESET to the terminal, the above-mentioned configuration information is used to instruct the terminal to monitor DCI in the CORESET, and the DCI in the above-mentioned CORESET is DCI for URLLC services; the first sending The module 402 is specifically configured to: send the first DCI generated by the generating module 401 to the terminal on the CORESET.

Optionally, the above configuration information is specifically used to instruct the terminal to monitor the DCI on the predetermined search space in CORESET; the first sending module 402 is specifically used to: send the first DCI generated by the generation module to the terminal on the predetermined search space in CORESET. DCI.

In the network device provided by the embodiment of the present invention, after the network device generates the first DCI for the URLLC service, it sends the first DCI to the terminal, and when the terminal monitors the first DCI, it can directly determine according to the indication information The first DCI is DCI for URLLC services, so that the terminal can effectively schedule URLLC services according to the dedicated first DCI for URLLC services, improving communication efficiency and performance.

The network device provided by the embodiment of the present invention can implement the process shown in any one of FIG. 2 to FIG. 6 in the above method embodiment, and to avoid repetition, details are not repeated here.

9 is a schematic diagram of a hardware structure of a terminal implementing various embodiments of the present invention. The terminal 100 includes, but is not limited to: a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, User input unit 107, interface unit 108, memory 109, processor 110, power supply 111 and other components. Those skilled in the art can understand that the structure of the terminal 100 shown in FIG. 9 does not constitute a limitation on the terminal, and the terminal 100 may include more or less components than shown in the figure, or combine certain components, or different components layout. In the embodiment of the present invention, the terminal 100 includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a vehicle terminal, a wearable device, and a pedometer.

Wherein, the processor 110 is configured to, when the terminal monitors the first DCI, determine the first DCI as the DCI for URLLC service according to the indication information; wherein, the above indication information is used to indicate that the first DCI is The DCI used for the URLLC service; the URLLC service is scheduled according to the first DCI.

In the terminal provided by the embodiment of the present invention, when the terminal monitors the first DCI, it can directly determine that the first DCI is the DCI for URLLC service according to the indication information, so that the terminal can use the proprietary URLLC service The first DCI is used to effectively schedule URLLC services and improve communication efficiency and effectiveness.

It should be understood that, in the embodiment of the present invention, the radio frequency unit 101 can be used for receiving and sending signals during sending and receiving information or during a call. Specifically, after receiving the downlink data from the base station, the processor 110 processes it; Uplink data is sent to the base station. Generally, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 can also communicate with the network and other devices through a wireless communication system.

The terminal 100 provides users with wireless broadband Internet access through the network module 102, such as helping users send and receive emails, browse web pages, and access streaming media.

The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the network module 102 or stored in the memory 109 into an audio signal and output as sound. Also, the audio output unit 103 may also provide audio output related to a specific function performed by the terminal 100 (for example, call signal reception sound, message reception sound, etc.). The audio output unit 103 includes a speaker, a buzzer, a receiver, and the like.

The input unit 104 is used to receive audio or video signals. The input unit 104 may include a graphics processing unit (Graphics Processing Unit, GPU) 1041 and a microphone 1042, and the graphics processing unit 1041 is used for still pictures or video images obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The data is processed. The processed image frames may be displayed on the display unit 106 . The image frames processed by the graphics processor 1041 may be stored in the memory 109 (or other storage media) or sent via the radio frequency unit 101 or the network module 102 . The microphone 1042 can receive sound and can process such sound into audio data. The processed audio data can be converted into a format that can be sent to a mobile communication base station via the radio frequency unit 101 for output in the case of a phone call mode.

The terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 1061 according to the brightness of the ambient light, and the proximity sensor can turn off the display panel 1061 and/or when the terminal 100 moves to the ear. or backlight. As a kind of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and can detect the magnitude and direction of gravity when it is stationary, and can be used to identify terminal posture (such as horizontal and vertical screen switching, related games, Magnetometer posture calibration), vibration recognition related functions (such as pedometer, knocking), etc.; sensor 105 can also include fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared ray Sensors, etc., will not be described in detail here.

The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061 , and the display panel 1061 may be configured in the form of a liquid crystal display (Liquid Crystal Display, LCD) or an organic light-emitting diode (Organic Light-Emitting Diode, OLED).

The user input unit 107 can be used to receive input numbers or character information, and generate key signal input related to user settings and function control of the terminal 100 . Specifically, the user input unit 107 includes a touch panel 1071 and other input devices 1072 . The touch panel 1071, also referred to as a touch screen, can collect touch operations of the user on or near it (for example, the user uses any suitable object or accessory such as a finger or a stylus on the touch panel 1071 or near the touch panel 1071). operate). The touch panel 1071 may include two parts, a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, and detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and sends it to the For the processor 110, receive the command sent by the processor 110 and execute it. In addition, the touch panel 1071 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071 , the user input unit 107 may also include other input devices 1072 . Specifically, other input devices 1072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.

Further, the touch panel 1071 can be covered on the display panel 1061, and when the touch panel 1071 detects a touch operation on or near it, it will be sent to the processor 110 to determine the type of the touch event, and then the processor 110 can The type of event provides a corresponding visual output on the display panel 1061 . Although in FIG. 9, the touch panel 1071 and the display panel 1061 are used as two independent components to realize the input and output functions of the terminal 100, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated. The implementation of the input and output functions of the terminal 100 is not specifically limited here.

The interface unit 108 is an interface for connecting an external device to the terminal 100 . For example, an external device may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, audio input/output (I/O) ports, video I/O ports, headphone ports, and more. The interface unit 108 may be used to receive input from an external device (for example, data information, power, etc.) transfer data between.

The memory 109 can be used to store software programs as well as various data. The memory 109 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, at least one application program required by a function (such as a sound playback function, an image playback function, etc.) etc.; Data created by the use of mobile phones (such as audio data, phonebook, etc.), etc. In addition, the memory 109 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage devices.

The processor 110 is the control center of the terminal 100, and uses various interfaces and lines to connect various parts of the entire terminal 100, by running or executing software programs and/or modules stored in the memory 109, and calling data stored in the memory 109 , execute various functions of the terminal 100 and process data, so as to monitor the terminal 100 as a whole. The processor 110 may include one or more processing units; optionally, the processor 110 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface and application programs, etc., and the modem The tuner processor mainly handles wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 110 .

The terminal 100 may also include a power supply 111 (such as a battery) for supplying power to various components. Optionally, the power supply 111 may be logically connected to the processor 110 through a power management system, so as to manage charging, discharging, and power consumption through the power management system. and other functions.

In addition, the terminal 100 includes some functional modules not shown, which will not be repeated here.

FIG. 10 is a schematic diagram of a hardware structure of a network device implementing an embodiment of the present invention. The network device 500 includes: a processor 501 , a transceiver 502 , a memory 503 , a user interface 504 and a bus interface.

Wherein, the processor 501 generates the first DCI; the transceiver 502 is configured to send the first DCI generated by the processor 501 to the terminal; Instructing the terminal to schedule URLLC services according to the first DCI.

In the network device provided by the embodiment of the present invention, after the network device generates the first DCI for the URLLC service, it sends the first DCI to the terminal, and when the terminal monitors the first DCI, it can directly determine according to the indication information The first DCI is DCI for URLLC services, so that the terminal can effectively schedule URLLC services according to the dedicated first DCI for URLLC services, improving communication efficiency and performance.

In the embodiment of the present invention, in FIG. 10 , the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 501 and various circuits of the memory represented by the memory 503 are linked together . The bus architecture can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, etc., which are well known in the art and therefore will not be further described herein. The bus interface provides the interface. Transceiver 502 may be a plurality of elements, including a transmitter and a receiver, providing a means for communicating with various other devices over transmission media. Used for different user devices, the user interface 504 may also be an interface capable of connecting externally and internally to required devices, and the connected devices include but are not limited to keypads, displays, speakers, microphones, joysticks, and the like. The processor 501 is responsible for managing the bus architecture and general processing, and the memory 503 can store data used by the processor 801 when performing operations.

In addition, the network device 500 also includes some functional modules not shown, which will not be repeated here.

Optionally, an embodiment of the present invention further provides a terminal, including a processor, a memory, and a computer program stored in the memory and operable on the processor. When the computer program is executed by the processor, the above-mentioned embodiment 1 is implemented. The process of the business scheduling method can achieve the same technical effect, so in order to avoid repetition, it will not be repeated here.

Optionally, an embodiment of the present invention further provides a network device, including a processor, a memory, and a computer program stored in the memory and operable on the processor. When the computer program is executed by the processor, the above-mentioned embodiment 1 is implemented. The process of the business scheduling method, and can achieve the same technical effect, in order to avoid repetition, it will not be repeated here.

An embodiment of the present invention also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, multiple processes of the business scheduling method in the above-mentioned embodiments are implemented, and can achieve The same technical effects are not repeated here to avoid repetition. Wherein, the computer-readable storage medium is, for example, a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk or an optical disk, and the like.

The embodiment of the present invention also provides a computer-readable storage medium. A computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, multiple processes in the above random access method embodiment are implemented, and the same To avoid repetition, the technical effects will not be repeated here. Wherein, the computer-readable storage medium, such as ROM, RAM, magnetic disk or optical disk, and the like.

It should be noted that, in this document, the term "comprising", "comprising" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising that element.

Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation. Based on such an understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art can be embodied in the form of software products, and the computer software products are stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to enable a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in multiple embodiments of the present invention.

Embodiments of the present invention have been described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementations, and the above-mentioned specific implementations are only illustrative, rather than restrictive, and those of ordinary skill in the art will Under the enlightenment of the present invention, without departing from the gist of the present invention and the protection scope of the claims, many forms can also be made, all of which belong to the protection of the present invention.

Claims (21)

1. A service scheduling method is applied to a terminal, and the method comprises the following steps:

when the terminal monitors a first DCI, determining the first DCI as a DCI for a low-delay high-reliability URLLC connection service according to indication information;

wherein, the indication information is used to indicate that the first DCI is a DCI for the URLLC service;

and scheduling the URLLC service according to the first DCI.

2. The method of claim 1,

the indication information is a domain value of a preset domain in the first DCI;

the determining, according to the indication information, that the first DCI is a DCI for a URLLC service includes:

if the load size of the first DCI is equal to the load size of the second DCI and the domain value of the preset domain is the same as the preset threshold, determining that the first DCI is the DCI used for the URLLC service;

and the second DCI is a DCI for enhancing a mobile bandwidth eMBB service.

3. The method of claim 1,

the indication information is configuration information for controlling a resource set, the configuration information is used for indicating the terminal to monitor DCI in the CORESET, and the DCI in the CORESET is DCI for the URLLC service.

4. The method of claim 3, wherein the determining whether the first DCI is preceded by a DCI for URLLC traffic according to the indication information, the method further comprising:

receiving configuration information of the CORESET sent to the terminal by network equipment;

and monitoring the first DCI sent by the network equipment on the CORESET according to the configuration information.

5. The method according to claim 4, wherein the configuration information is specifically used to instruct the terminal to monitor DCI on a predetermined search space in the CORESET;

the monitoring, in the CORESET, the first DCI sent by the network device in the CORESET according to the configuration information includes:

and monitoring the first DCI sent by the network equipment on a preset search space of the CORESET according to the configuration information.

6. A service scheduling method is applied to a network device, and the method comprises the following steps:

generating a first DCI;

transmitting the first DCI to a terminal;

the first DCI is DCI used for low-delay high-reliability URLLC service connection, and the first DCI is used for indicating the terminal to schedule the URLLC service according to the first DCI.

7. The method of claim 6, wherein the generating the first DCI comprises:

generating a second DCI;

setting a domain value of a preset domain in the second DCI to be a preset threshold value, and generating the first DCI;

the second DCI is a DCI for enhancing a mobile bandwidth eMBB service, and the load size of the first DCI is equal to that of the second DCI.

8. The method of claim 6,

before the sending the first DCI to the terminal, the method further includes:

and sending configuration information for controlling a resource set (CORESET) to the terminal, wherein the configuration information is used for indicating the terminal to monitor DCI in the CORESET, and the DCI in the CORESET is the DCI for the URLLC service.

The sending the first DCI to the terminal includes:

and sending the first DCI to the terminal on the CORESET.

9. The method according to claim 8, wherein the configuration information is specifically used to instruct the terminal to monitor DCI on a predetermined search space in the CORESET;

the sending the first DCI to the terminal on the CORESET includes:

and transmitting the first DCI to the terminal on a preset search space in the CORESET.

10. A terminal, comprising:

a determining module, configured to determine, when the terminal monitors a first DCI, that the first DCI is a DCI for a low-latency high-reliability URLLC connection service according to indication information;

wherein, the indication information is used to indicate that the first DCI is a DCI for the URLLC service;

and the scheduling module is used for scheduling the URLLC service according to the first DCI determined by the determining module.

11. The terminal of claim 10,

the indication information is a domain value of a preset domain in the first DCI;

the determining module is specifically configured to:

if the load size of the first DCI is equal to the load size of the second DCI and the domain value of the preset domain is the same as the preset threshold, determining that the first DCI is the DCI used for the URLLC service;

and the second DCI is a DCI for enhancing a mobile bandwidth eMBB service.

12. The terminal of claim 10,

the indication information is configuration information for controlling a resource set, the configuration information is used for indicating the terminal to monitor DCI in the CORESET, and the DCI in the CORESET is DCI for the URLLC service.

13. The terminal of claim 12, wherein the terminal further comprises:

the receiving module is used for receiving the configuration information of the CORESET sent to the terminal by the network equipment;

and the monitoring module is used for monitoring the first DCI sent by the network equipment on the CORESET according to the configuration information received by the receiving module.

14. The terminal of claim 13, wherein the configuration information is specifically configured to instruct the terminal to monitor DCI in a predetermined search space in the CORESET;

the monitoring module is specifically configured to: and monitoring the first DCI sent by the network equipment on a preset search space of the CORESET according to the configuration information received by the receiving module.

15. A network device, comprising:

a generating module for generating a first DCI;

a first sending module, configured to send the first DCI generated by the generating module to a terminal;

the first DCI is DCI used for low-delay high-reliability URLLC service connection, and the first DCI is used for indicating the terminal to schedule the URLLC service according to the first DCI.

16. The network device of claim 15,

the generation module is specifically configured to: generating second DCI, setting a domain value of a preset domain in the second DCI as a preset threshold value, and generating the first DCI;

the second DCI is a DCI for enhancing a mobile bandwidth eMBB service, and the load size of the first DCI is equal to that of the second DCI.

17. The network device of claim 15, wherein the network device further comprises:

a second sending module, configured to send configuration information for controlling a resource set, CORESET, to the terminal, where the configuration information is used to instruct the terminal to monitor DCI in the CORESET, and the DCI in the CORESET is DCI for the URLLC service;

the first sending module is specifically configured to: and sending the first DCI generated by the generation module to the terminal on the CORESET.

18. The network device of claim 17, wherein the configuration information is specifically configured to instruct the terminal to monitor DCI in a predetermined search space in the CORESET;

the first sending module is specifically configured to: and transmitting the first DCI generated by the generation module to the terminal on a preset search space in the CORESET.

19. A terminal, characterized in that it comprises a processor, a memory and a computer program stored on the memory and executable on the processor, which computer program, when executed by the processor, implements the steps of the traffic scheduling method according to any of claims 1 to 5.

20. A network device comprising a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the traffic scheduling method according to any one of claims 6 to 9.

21. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the traffic scheduling method according to any one of claims 1 to 9.