CN110475369B

CN110475369B - Service scheduling method, terminal and network equipment

Info

Publication number: CN110475369B
Application number: CN201810448635.6A
Authority: CN
Inventors: 鲁智; 潘学明; 纪子超
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2018-05-11
Filing date: 2018-05-11
Publication date: 2021-06-01
Anticipated expiration: 2038-05-11
Also published as: CN110475369A; WO2019214420A1

Abstract

The embodiment of the invention provides a service scheduling method, a terminal and network equipment, relates to the technical field of communication, and aims to solve the problem that the URLLC service scheduling cannot be effectively carried out due to the fact that DCI (downlink control information) for the URLLC service is not available in the prior art. 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.

Description

Service scheduling method, terminal and network equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a service scheduling method, a terminal, and a network device.

Background

Currently, ITU-R (international telecommunications union radio communication office) has determined that future 5G communication systems have three major application scenarios: eMBB (enhanced Mobile Broadband), URLLC (Ultra-Reliable and Low Latency high reliability connectivity), mMTC (massive Machine Type Communications, Large-Scale Internet of things). In the prior art, Downlink Control Information (DCI) sent by a base station to a terminal is mainly DCI for an eMBB service in an eMBB scenario, so that the terminal can schedule the eMBB service according to the DCI after monitoring the DCI for the eMBB service sent by the base station.

However, there is no relevant DCI design for URLLC traffic for URLLC scenarios, and there is no effective scheduling scheme for URLLC traffic.

Disclosure of Invention

Embodiments of the present invention provide a service scheduling method, a terminal, and a network device, so as to solve the problem in the prior art that URLLC service scheduling cannot be effectively performed because no DCI is used for the URLLC service.

In order to solve the technical problem, the invention is realized as follows:

in a 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 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.

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;

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.

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

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;

and the scheduling module is used for scheduling 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 for generating a first DCI;

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

In a fifth aspect, an embodiment of the present invention provides a terminal, including a processor, a memory, and a computer program stored on the memory and executable on the processor, where the computer program, when executed by the processor, implements the steps of the service scheduling method according to the first aspect.

In a sixth aspect, an embodiment of the present invention provides a network device, which includes a processor, a memory, and a computer program stored on the memory and executable on the processor, and when executed by the processor, the computer program implements the steps of the traffic scheduling method according to the second aspect.

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 service scheduling method are implemented.

In the embodiment of the present invention, when the terminal monitors the first DCI, the terminal may directly determine, according to the indication information, that the first DCI is the DCI for the URLLC service, so that the terminal can effectively schedule the URLLC service according to the first DCI for the URLLC service, and communication efficiency and efficiency are improved.

Drawings

Fig. 1 is a schematic diagram of a possible structure of a communication system according to an embodiment of the present invention;

fig. 2 is a schematic flow chart of a service scheduling method according to an embodiment of the present invention;

fig. 3 is a second schematic flowchart of a service scheduling method according to an embodiment of the present invention;

fig. 4 is a third schematic flow chart of a service scheduling method according to an embodiment of the present invention;

fig. 5 is a fourth schematic flowchart of a service scheduling method according to an embodiment of the present invention;

fig. 6 is a fifth flowchart of a service scheduling method according to an embodiment of the present invention;

fig. 7 is a schematic structural diagram of a terminal according to an embodiment of the present invention;

fig. 8 is a schematic structural diagram of a network device according to an embodiment of the present invention;

fig. 9 is a second schematic structural diagram of a terminal according to a second embodiment of the present invention;

fig. 10 is a second schematic structural diagram of a network device according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Some of the terms referred to in this disclosure are explained below for the convenience of the reader:

1. downlink Control Information (DCI)

In the LTE system, a downlink control channel (PDCCH) is transmitted 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 transmitted through first 1-3 Orthogonal Frequency Division Multiplexing (OFDM) symbols of one downlink subframe. Generally, a basic unit of time-frequency resources of DCI carried on a PDCCH is also a Control Channel Element (CCE). DCI may be transmitted using different Aggregation Levels (ALs). The aggregation level refers to how many CCEs DCI is carried on. The aggregation level may be, for example, but not limited to, 1, 2, 4, 8, 16, 32, etc., e.g., an aggregation level of 2 means that DCI is carried on 2 CCEs.

2. DCI Blind detection (blind decode)

As described above, DCI may be in the first 1 to 3 symbols of one subframe, and DCI may 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, and therefore the UE does not know the number and location of Control Channel Elements (CCEs) occupied by the UE, the DCI format (DCI format) to be transmitted, or the aggregation level of the DCI, and therefore the User Equipment (UE) needs to detect the time-frequency resource location and the aggregation level of the DCI that may be tried by 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 obtain the downlink control information DCI.

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

3. Controlling Resource Set (CORESET)

The CORESET is a kind of time-frequency resource set introduced in the 5G NR system, that is, the terminal detects a downlink control channel (PDCCH) in the corresponding CORESET. CORESET consists of a group of REGs.

Illustratively, the configuration information of the CORESET may be notified by one or more of the following combinations:

the configuration information of the CORESET can be notified through high-level signaling; alternatively, the first and second electrodes may be,

the configuration information of the CORESET can be sent through a broadcast channel, system information and the like; alternatively, the first and second electrodes may be,

the configuration information of CORESET may be predefined according to one or more of system bandwidth, subcarrier spacing, antenna configuration, and carrier frequency, for example.

Configuration information for CORESET herein includes, but is not limited to, at least one of the following: the CORESET time frequency resource information comprises: the information includes, for example, information about frequency resources of the CORESET (e.g., number of PRBs, time-frequency position, etc.) and information about time-domain resources of the CORESET (e.g., number of OFDM symbols), a PDCCH aggregation level set that needs blind detection in the CORESET, the number of candidate resources of blind detection PDCCH at each PDCCH aggregation level that needs blind detection in the CORESET, and PDCCH DCI parameters (e.g., DCI format, DCI length) that need blind detection in the CORESET.

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

4. Other terms

The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship; in the formula, the character "/" indicates that the preceding and following related objects are in a relationship of "division". The term "plurality" herein means two or more, unless otherwise specified.

For the convenience of clearly describing the technical solutions of the embodiments of the present invention, in the embodiments of the present invention, the words "first", "second", and the like are used to distinguish the same items or similar items with basically the same functions or actions, and those skilled in the art can understand that the words "first", "second", and the like 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 to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "e.g.," an embodiment of the present invention is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

The technical scheme provided by the application is described below with reference to the accompanying drawings.

The technical scheme provided by the invention can be applied to various communication systems, such as a 5G communication system, a future evolution system or a plurality of communication convergence systems and the like. A variety of application scenarios may be included, for example, scenarios such as machine-to-machine (M2M), D2M, macro-micro communication, enhanced mobile broadband (eMBB), ultra high reliability and ultra low latency communication (urrllc), and mass internet of things communication (mtc). These scenarios include, but are not limited to: the communication between the terminals, the communication between the network devices, or the communication between the network devices and the terminals. The embodiment of the invention can be applied to the communication between the network equipment and the terminal in the 5G communication system, or the communication between the terminal and the terminal, or the communication between the network equipment and the network equipment.

Fig. 1 shows a schematic diagram of a possible structure of a communication system according to 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 to which each network device 100 is connected.

The network device 100 may be a base station, a core network device, a Transmission and Reception node (TRP), a relay station, an access Point, or the like. The network device 100 may be a Base Transceiver Station (BTS) in a Global System for Mobile communication (GSM) or Code Division Multiple Access (CDMA) network, or may be an nb (nodeb) in Wideband Code Division Multiple Access (WCDMA), or may be an eNB or enodeb (evolved nodeb) in LTE. The Network device 100 may also be a wireless controller in a Cloud Radio 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. The words used are not to be construed as limitations of the invention.

The terminal 200 may be a wireless terminal, which may be a device providing voice and/or other traffic data connectivity to a user, a handheld device having wireless communication functionality, a computing device or other processing device connected to a wireless modem, a vehicle mounted device, a wearable device, a terminal in a future 5G network or a terminal in a future evolved PLMN network, etc., as well as a wired terminal. A Wireless terminal may communicate with one or more core networks via a Radio Access Network (RAN), and may be a Mobile terminal, such as a Mobile phone (or "cellular" phone) and a computer with a Mobile terminal, for example, a portable, pocket, hand-held, computer-included or vehicle-mounted Mobile device, which exchanges languages and/or data with the RAN, and Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and the like, and may also be a Mobile device, UE terminal, Access terminal, Wireless Communication device, terminal unit, terminal Station, Mobile Station (Mobile Station), and/or Mobile terminal, A Mobile Station (Mobile), a Remote Station (Remote Station), a Remote Station, a Remote Terminal (Remote Terminal), a Subscriber Unit (Subscriber Unit), a Subscriber Station (Subscriber Station), a User Agent (User Agent), a Terminal device, and the like. As an example, in the embodiment of the present invention, fig. 1 illustrates that the terminal is a mobile phone.

Fig. 2 shows a schematic flow chart of a service scheduling method according to an embodiment of the present invention, and as shown in fig. 2, the service scheduling method may include:

s201: the network device generates a first DCI.

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

S202: the network device transmits the first DCI to the terminal.

Correspondingly, the opposite 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: and when the terminal monitors the first DCI, the terminal determines the first DCI as the DCI for the URLLC service according to the indication information.

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

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

For example, the embodiment of the present invention may implement the service scheduling method provided by the present invention through the following four implementation manners.

A first possible implementation:

in this implementation, the network device redesigns the partial domain of the existing DCI on the basis of the existing DCI for the eMBB service, so that the redesigned DCI can meet the requirement of the URLLC service, and thus the redesigned DCI is used as the DCI for the URLLC service. Generally, if the redesigned DCI needs to meet the requirements of the URLLC service, the payload size of the DCI that needs to be redesigned is greater than or equal to the payload size of the DCI for the eMBB service, and in this scenario, the network device may indicate, to the terminal, that the DCI is the DCI for the URLLC service by setting the domain values of the partial domains in the DCI for the eMBB service to a predetermined threshold.

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

s201a 1: the network device generates a second DCI.

The second DCI is a DCI for an eMBB service.

S201a 2: and the network equipment sets the domain value of the preset domain in the second DCI as a preset threshold value A, and generates the first DCI.

And the load size of the first DCI is equal to the load size of the second DCI.

In this embodiment of the present invention, after the network device sets the domain value of the preset domain in the second DCI as the predetermined threshold a, if the load size of the other domains except the preset domain in the second DCI is greater than the load size of the specified DCI for the URLLC service, the network device sets the domain values of some domains in the other domains except the preset domain in the second DCI as the predetermined threshold B, and since the terminal side of the predetermined threshold B does not interpret, the size of the load of the DCI actually used for the URLLC service in the second DCI is equal to the load size of the specified DCI for the URLLC service. Of course, if the load size of the other domains except the preset domain in the second DCI is equal to the DCI load size for the URLLC service, the network device may directly take the second DCI after the domain value is reset as the first DCI.

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

It should be noted that the location of the payload of the DCI for the URLLC traffic described above in the DCI may be pre-configured by the network device.

For example, if the payload size of the DCI for the URLLC service is set to C, the position of the payload of the DCI for the URLLC service in the DCI may be: the positions of the domains meeting the preset conditions, which are selected from the DCI according to the sequence from front to back, or the positions of the domains meeting the preset conditions, which are selected from the DCI except the CRC and the preset domains according to the sequence from back to front, or other predefined positions in the DCI. Wherein, the domains which are selected from the front to the back and meet the preset conditions are as follows: sequentially accumulating the loads of the domains in the DCI from front to back until the size of the accumulated load is equal to C, and accumulating all the domains corresponding to the load; the above-mentioned fields satisfying the predetermined condition, which are selected in the order from back to front, refer to: and sequentially accumulating the loads of the domains excluding the CRC and the preset domains in the DCI from back to front until the size of the accumulated load is equal to C, and accumulating all the domains corresponding to the load.

It should be noted that the base station does not use the state in which the above-mentioned preset field is set to the predetermined threshold a when scheduling DCI for the eMBB service. Therefore, after the terminal decodes the DCI, the terminal may determine that the DCI is the DCI for the URLLC service based on the domain values of the preset domains, if it finds that the domain value of the preset domain in the DCI is the same as the preset threshold a.

For example, table 1 below is used to illustrate the domain definition of the fields in the downlink fallback (fallback) DCI. Wherein, the fallback DCI is DCI used for eMBB service.

TABLE 1

The abbreviations in table 1 refer to the following notations for english abbreviations: a Physical Downlink Shared Channel (PDSCH); hybrid automatic Repeat reQuest (HARQ); physical Uplink Control CHannel (PUCCH); transmission Control Protocol (TCP).

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

Optionally, as shown in fig. 3, in combination with the foregoing S201a1 and S201a2, where the foregoing indication information is a domain value of a preset domain in the first DCI, the terminal may determine whether the first DCI is a DCI for a URLLC service according to the domain value of the preset domain in the first DCI. Specifically, the step S203 specifically includes the following steps:

s203 a: and 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 A, the terminal determines that the first DCI is the DCI used for the URLLC service.

The second DCI is a DCI for an eMBB service.

In the embodiment of the present invention, when the terminal monitors a first DCI, the terminal may decode the first DCI, and obtain a domain value of a preset domain in the first DCI, and if the terminal finds that the domain values are the same as a predefined preset threshold value a, the terminal may consider the first DCI as a DCI for a URLLC service, and at this time, the domain values of other domains in the first DCI may be interpreted according to the meaning of the domain values of the DCI for the URLLC service.

A second possible implementation:

in this implementation manner, the Network device may configure a Radio Network Temporary Identity (RNTI) specific to the URLLC service for the terminal, that is, different RNTIs are used to distinguish DCI of different services, and the terminal may determine whether the first DCI is DCI for the URLLC service according to the RNTI corresponding to the first DCI.

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

s201b 1: the network device generates a third DCI.

Wherein, the third DCI is a DCI for a URLLC service.

S201b 2: and the network equipment scrambles the CRC code in the third DCI by using the RNTI corresponding to the URLLC service to generate the first DCI.

In the embodiment of the present invention, the RNTI corresponding to the URLLC service may be predefined, that is, specified by a protocol, or may be 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 step S203 specifically includes the following steps:

s203b 1: and the terminal descrambles the first DCI by using the RNTI corresponding to the URLLC service to obtain a CRC code.

S203b 2: and the terminal performs CRC check on the CRC code, and if the check is passed, the first DCI is determined to be the DCI used for the URLLC service.

In the embodiment of the invention, the network equipment configures different RNTIs for different services, so that DCIs of different services can be distinguished by using different RNTIs. After the network equipment encodes DCI of corresponding services, the network equipment can scramble CRC of the DCI by using the special RNTI corresponding to the services and send the scrambled DCI to the terminal, and after the terminal monitors the DCI, if the terminal receives the RNTI (such as the RNTI corresponding to the URLLC services) of target services sent by the network equipment, the terminal can descramble the DCI by using the RNTI, if the verification is passed, the DCI is the DCI of the target services, if the terminal does not receive the RNTI of the target services sent by the network equipment, the terminal can descramble the DCI by using the RNTI of different services, and if the verification is passed, the DCI of the services corresponding to the RNTI is indicated.

A third possible implementation:

in this implementation, the network device may allocate an independent CORESET to the control channel of the URLLC service, that is, the DCI sent under the CORESET is all the DCI for the URLLC service, so that after the terminal monitors the DCI in the CORESET, it may directly determine that the DCI is the DCI for the URLLC service.

Optionally, as shown in fig. 5, in the embodiment of the present invention, the indication information is configuration information of a core set, where the configuration information is used to indicate that the terminal monitors DCI in the core set, and the DCI in the core set is DCI for a URLLC service. Specifically, in the embodiment of the present invention, S202 specifically includes the following steps:

s202c 1: 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:

s202c 2: the network equipment sends the configuration information of the CORESET to the terminal.

Correspondingly, the opposite terminal receives the configuration information of the CORESET sent to the terminal by the network equipment.

S202c 3: and the terminal monitors the first DCI sent by the network equipment on the CORESET according to the configuration information.

A fourth possible implementation:

the present implementation is implemented on the basis of a third possible implementation, and specifically, assuming that one CORESET includes three search spaces, the network device may allocate an independent search space in the CORESET to the control channel of the URLLC service, that is, DCI sent in the search space is all DCI for the URLLC service, so that after the terminal monitors DCI in the search space in the CORESET, it may directly determine that the DCI is DCI for the URLLC service.

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

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

s202d 1: the network device transmits the first DCI to the terminal over a predetermined search space in the CORESET.

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

s202d 2: and the terminal monitors the first DCI transmitted by the network equipment on the preset search space of the CORESET according to the configuration information.

Compared with the third possible implementation manner, the scheme that the independent search space of the CORESET is allocated to the URLLC service in the fourth possible implementation manner can further narrow the blind detection range of the terminal.

According to the service scheduling method provided by the embodiment of the invention, the network equipment sends the first DCI used for the URLLC service to the terminal after generating the first DCI, and when the terminal monitors the first DCI, the first DCI can be directly determined to be the DCI used for the URLLC service according to the indication information, so that the terminal can effectively schedule the URLLC service according to the first DCI exclusively used for the URLLC service, and the communication efficiency and the efficiency are improved.

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

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

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

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

Optionally, the indication information is a field value of a preset field in the first DCI; the determining module 301 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 for the URLLC service; the second DCI is a DCI for an eMBB service.

Optionally, the indication information is configuration information for controlling a resource set, where the configuration information is used to indicate the terminal to monitor DCI in the core set, and the DCI in the core set is DCI for a URLLC service.

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

a receiving module 303, configured to receive the configuration information of the CORESET sent by the network device to the terminal; and 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 configuration information is specifically used to instruct the terminal to monitor DCI in a predetermined search space in the CORESET; the monitoring module 304 is specifically configured to: and monitoring a first DCI (downlink control information) transmitted by the network equipment on a preset search space of the CORESET according to the configuration information received by the receiving module.

According to the terminal provided by the embodiment of the invention, when the terminal monitors the first DCI, the first DCI can be directly determined to be the DCI used for the URLLC service according to the indication information, so that the terminal can effectively schedule the URLLC service according to the first DCI exclusively used for the URLLC service, and the communication efficiency and the efficiency are improved.

The terminal provided in the embodiment of the present invention is capable of implementing the process shown in any one of fig. 2 to 6 in the above method embodiment, and is not described herein again to avoid repetition.

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

a generating module 401 is configured to generate the first DCI.

A first sending module 402, configured to send the first DCI generated by the generating module 401 to the terminal; the first DCI is a DCI used for a URLLC service, and the first DCI is used for indicating the terminal to schedule the URLLC service according to the first DCI.

Optionally, the generating 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 first DCI; the second DCI is a DCI for an eMBB service, and a payload size of the first DCI is equal to a payload size of the second DCI.

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

a second sending module 403, configured to send configuration information of a control resource set, the configuration information is used to instruct the terminal to monitor DCI in the CORESET, where the DCI in the CORESET is DCI for a URLLC service; the first sending module 402 is specifically configured to: the first DCI generated by the generation module 401 is transmitted to the terminal on the CORESET.

Optionally, the configuration information is specifically used to instruct the terminal to monitor DCI in a predetermined search space in the CORESET; the first sending module 402 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.

According to the network device provided by the embodiment of the invention, after the first DCI for the URLLC service is generated, the first DCI is sent to the terminal, and when the terminal monitors the first DCI, the first DCI can be directly determined to be the DCI for the URLLC service according to the indication information, so that the terminal can effectively schedule the URLLC service according to the first DCI exclusively used for the URLLC service, and the communication efficiency and the efficiency are improved.

The network device provided in the embodiment of the present invention is capable of implementing the process shown in any one of fig. 2 to fig. 6 in the above method embodiment, and is not described here again to avoid repetition.

Fig. 9 is a schematic diagram of a hardware structure of a terminal for implementing various embodiments of the present invention, where the terminal 100 includes, but is not limited to: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111. Those skilled in the art will appreciate that the configuration of terminal 100 shown in fig. 9 is not intended to be limiting, and terminal 100 may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. 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 palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.

The processor 110 is configured to determine, according to the indication information, that the first DCI is a DCI for a URLLC service when the terminal monitors the first DCI; 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.

It should be understood that, in the embodiment of the present invention, the radio frequency unit 101 may be used for receiving and sending signals during a message transmission or call process, and specifically, after receiving downlink data from a base station, the downlink data is processed by the processor 110; in addition, the uplink data is transmitted to the base station. Typically, 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 a network and other devices through a wireless communication system.

The terminal 100 provides the user with wireless broadband internet access through the network module 102, such as helping the user send and receive e-mails, 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 (e.g., a call signal reception sound, a 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 an audio or video signal. The input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042, and the Graphics processor 1041 processes image data of a still picture or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the graphic processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the network module 102. The microphone 1042 may receive sound and may be capable of processing such sound into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 101 in case of a phone call mode.

The terminal 100 also includes at least one sensor 105, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 1061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 1061 and/or a backlight when the terminal 100 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the terminal posture (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration identification related functions (such as pedometer, tapping), and the like; the sensors 105 may also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., which are not described in detail herein.

The display unit 106 is used to display information input by a 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 (LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 107 may be used to receive input numeric or character information and generate key signal inputs 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. Touch panel 1071, also referred to as a touch screen, may collect touch operations by a user on or near the touch panel 1071 (e.g., operations by a user on or near touch panel 1071 using a finger, stylus, or any suitable object or attachment). The touch panel 1071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 110, and receives and executes commands sent by the processor 110. In addition, the touch panel 1071 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may include other input devices 1072. Specifically, other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

Further, the touch panel 1071 may be overlaid on the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or nearby, the touch panel 1071 transmits the touch operation to the processor 110 to determine the type of the touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of the touch event. Although in fig. 9, the touch panel 1071 and the display panel 1061 are two independent components to implement the input and output functions of the terminal 100, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the terminal 100, and is not limited herein.

The interface unit 108 is an interface for connecting an external device to the terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the terminal 100 or may be used to transmit data between the terminal 100 and the external device.

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

The processor 110 is a control center of the terminal 100, connects various parts of the entire terminal 100 using various interfaces and lines, performs various functions of the terminal 100 and processes data by running or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the terminal 100. Processor 110 may include one or more processing units; alternatively, the processor 110 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.

The terminal 100 may further include a power supply 111 (e.g., a battery) for supplying power to various components, and optionally, the power supply 111 may be logically connected to the processor 110 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system.

In addition, the terminal 100 includes some functional modules that are not shown, and thus, the detailed description thereof is omitted.

Fig. 10 is a schematic hardware structure diagram of a network device for implementing an embodiment of the present invention, where 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 a first DCI; a transceiver 502 for transmitting the first DCI generated by the processor 501 to a terminal; the first DCI is a DCI used for a URLLC service, and the first DCI is used for indicating the terminal to schedule the URLLC service according to the first DCI.

In embodiments of the present invention, in FIG. 10, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 501 and various circuits of memory represented by memory 503 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 502 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. For different user devices, the user interface 504 may also be an interface capable of interfacing with a desired device, including but not limited to a keypad, display, speaker, microphone, joystick, etc. The processor 501 is responsible for managing the bus architecture and general processing, and the memory 503 may store data used by the processor 801 in performing operations.

In addition, the network device 500 further includes some functional modules that are not shown, and are not described herein again.

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 capable of running on the processor, where the computer program, when executed by the processor, implements the process of the service scheduling method in the first embodiment, and can achieve the same technical effect, and details are not repeated here to avoid repetition.

Optionally, an embodiment of the present invention further provides a network device, which includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor, where the computer program, when executed by the processor, implements the process of the service scheduling method in the first embodiment, and can achieve the same technical effect, and details are not repeated here to avoid repetition.

An embodiment of the present invention further 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 computer program implements multiple processes of the service scheduling method in the foregoing embodiments, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

An embodiment of the present invention further 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 computer program implements a plurality of processes of the foregoing random access method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer readable storage medium is, for example, ROM, RAM, magnetic disk or optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

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

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

scheduling the URLLC service according to the first DCI;

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

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

generating a second DCI;

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

transmitting the first DCI to a terminal;

the first DCI is DCI used for low-delay high-reliability connection of URLLC service, and the first DCI is used for indicating the terminal to schedule the URLLC service according to 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.

3. A terminal, comprising:

a determining module, configured to determine, when the terminal monitors a first DCI, that the first DCI is a DCI for the URLLC service if a load size of the first DCI is equal to a load size of a second DCI and a threshold value of a preset domain in the first DCI is the same as a predetermined threshold value;

a scheduling module, configured to schedule the URLLC service according to the first DCI;

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

4. A network device, comprising:

a generating module, configured to generate a second DCI, set a domain value of a preset domain in the second DCI to a predetermined threshold, and generate a first DCI;

5. 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 claim 1.

6. 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 claim 2.

7. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the traffic scheduling method according to claim 1 or 2.