WO2019214420A1

WO2019214420A1 - Service scheduling method, terminal, and network device

Info

Publication number: WO2019214420A1
Application number: PCT/CN2019/083449
Authority: WO
Inventors: 鲁智; 潘学明; 纪子超
Original assignee: 维沃移动通信有限公司
Priority date: 2018-05-11
Filing date: 2019-04-19
Publication date: 2019-11-14
Also published as: CN110475369B; CN110475369A

Abstract

Embodiments of the present disclosure relate to the technical field of communications, and provide a service scheduling method, a terminal, and a network device. The method comprises: when the terminal monitors a first DCI, determining, according to indication information, that the first DCI is a DCI for an ultra-reliable and low latency communications (URLLC) service; the indication information being used for indicating 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

Cross-reference to related applications

The present application claims priority to Chinese Patent Application No. 20181044863, filed on Jan. 11, 2011, the entire disclosure of which is hereby incorporated by reference.

Technical field

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

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: enhanced mobile broadband (eMBB), low latency and high reliability connection (Ultra-Reliable) And Low Latency Communications, URLLC), Massive Machine Type Communications (mMTC). In the related art, the downlink control information (DCI) sent by the base station to the terminal is mainly the DCI of the eMBB service used in the eMBB scenario, so that the terminal can monitor the DCI for the eMBB service sent by the base station. The eMBB service is scheduled according to the DCI.

However, the URLLC service for the URLLC scenario does not currently have a related DCI design, and there is no effective scheduling scheme for the URLLC service.

Summary of the invention

The embodiments of the present disclosure provide a service scheduling method, a terminal, and a network device, which are used to solve the problem that the URLLC service scheduling cannot be effectively performed due to the absence of DCI for the URLLC service in the related art.

In order to solve the above technical problems, the present disclosure is implemented as follows:

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

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

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

The URLLC service is scheduled according to the first DCI.

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

Generating a first DCI;

Sending the first DCI to the terminal;

The first DCI is a DCI for low-latency, high-reliability connection of the URLLC service, 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 disclosure provides a terminal, including:

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

And 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 disclosure provides a network device, including:

Generating a module, configured to generate a first DCI;

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

In a fifth aspect, an embodiment of the present disclosure provides a terminal, including a processor, a memory, and a computer program stored on the memory and executable 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 implemented.

In a sixth aspect, an embodiment of the present disclosure provides a network device, including a processor, a memory, and a computer program stored on the memory and executable on the processor, when the computer program is executed by the processor The steps of the service scheduling method as described in the second aspect are implemented.

In a seventh aspect, an embodiment of the present disclosure provides a computer readable storage medium storing a computer program on a storage medium, the computer program being executed by a processor to implement the steps of the service scheduling method.

In the embodiment of the present disclosure, when the terminal monitors the first DCI, the terminal may directly determine, according to the indication information, that the first DCI is a DCI for the URLLC service, so that the terminal can be used according to the proprietary URLLC service. The first DCI is effective for scheduling the URLLC service, improving communication efficiency and performance.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings used in the description of the embodiments of the present disclosure will be briefly described. It is obvious that the drawings in the following description are only some embodiments of the present disclosure. Other drawings may also be obtained from those of ordinary skill in the art in light of the inventive work.

1 is a schematic structural diagram of a communication system according to an embodiment of the present disclosure;

FIG. 2 is a schematic flowchart of a service scheduling method according to an embodiment of the present disclosure;

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

FIG. 4 is a third schematic flowchart of a service scheduling method according to an embodiment of the present disclosure;

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

FIG. 6 is a fifth schematic flowchart of a service scheduling method according to an embodiment of the present disclosure;

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

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

FIG. 9 is a second schematic structural diagram of a terminal according to an embodiment of the present disclosure;

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

detailed description

The technical solutions in the embodiments of the present disclosure are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present disclosure. It is obvious that the described embodiments are a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without departing from the inventive scope are the scope of the disclosure.

Some of the terms involved in this disclosure are explained below to facilitate the reader's understanding:

1. Downlink Control Indicator (DCI)

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

2, DCI blind detection (blind decode)

As mentioned above, DCI can be transmitted in the first 1 to 3 symbols of a subframe, and DCI can be transmitted at different aggregation levels. However, since the PDCCH is an instruction sent by the base station, the UE does not receive other information except some system information, so the UE does not know the number of control channel elements (CCEs) occupied by the UE, the location, and the transmitted DCI. The format (DCI format) does not know the aggregation level of the DCI. Therefore, the UE needs to detect the time-frequency resource location and aggregation level of the possible DCI by blind detection, thereby receiving the DCI. That is, the UE detects the downlink control channel PDCCH sent by the base station by using the blind detection mode 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, a Common Search Space (CSS) and a UE-specific Search Space (UESS), where the search is performed. 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, the terminal performs downlink control channel (PDCCH) detection in the corresponding CORESET. CORESET is composed of a group of REGs.

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

The CORESET configuration information can be notified through high layer signaling; or,

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

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

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

In general, a CORESET includes at least one search space, and a search space in CORESET can be considered a UESS.

4. Other terms

The term "and/or" in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship; in the formula, the character "/" indicates that the contextual object is a "divide" relationship. Unless otherwise stated, "multiple" in this document refers to two or more.

In order to facilitate the clear description of the technical solutions of the embodiments of the present disclosure, in the embodiments of the present disclosure, the words "first", "second", etc. are used to distinguish the same or similar items whose functions or functions are substantially the same, in the field. The skilled person will understand that the words "first", "second" and the like do not limit the number and order of execution.

It should be noted that, in the embodiments of the present disclosure, the words "exemplary" or "such as" are used to mean an example, an illustration, or a description. Any embodiment or design described as "exemplary" or "for example" in the disclosed embodiments should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the words "exemplary" or "such as" is intended to present the concepts in a particular manner.

The technical solutions provided by the present application are described below with reference to the accompanying drawings.

The technical solutions provided by the present disclosure can be applied to various communication systems, for example, a 5G communication system, a future evolution system, or a plurality of communication fusion systems, and the like. Can include a variety of application scenarios, for example, machine to machine (M2M), D2M, macro communication, enhanced mobile broadband (eMBB), ultra high reliability and ultra low latency communication (ultra Reliable & low latency communication (uRLLC) and massive machine type communication (mMTC) scenarios. These scenarios include, but are not limited to, communication between the terminal and the terminal, or communication between the network device and the network device, or communication between the network device and the terminal. Embodiments of the present disclosure may be applied to communication with a network device and a terminal in a 5G communication system, or communication between a terminal and a terminal, or communication between a network device and a network device.

FIG. 1 is a schematic diagram showing a possible structure of a communication system according to an embodiment of the present disclosure. 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 Point (TRP), a relay station, or an access point. The network device 100 may be a Global System for Mobile communication (GSM) or a Base Transceiver Station (BTS) in a Code Division Multiple Access (CDMA) network, or may be a broadband The NB (NodeB) in the Code Division Multiple Access (WCDMA) may also be an eNB or an eNodeB (evolutional 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 evolved network. The use of words does not constitute a limitation of the present disclosure.

The terminal 200 can be a wireless terminal or a wired terminal, and the wireless terminal can be a device that provides voice and/or other service data connectivity to the user, a handheld device with wireless communication capabilities, a computing device, or other processing connected to the wireless modem. Devices, in-vehicle devices, wearable devices, terminals in future 5G networks, or terminals in a future evolved PLMN network. The wireless terminal can communicate with one or more core networks via a Radio Access Network (RAN), which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal. For example, it can be a portable, pocket, handheld, computer built-in or in-vehicle mobile device that exchanges language and/or data with a wireless access network, as well as personal communication service (PCS) phones, cordless phones. a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), etc., and the wireless terminal can also be a mobile device or a user device ( User Equipment, 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, Subscriber Station, User Generation (User Agent), the terminal device and the like. As an example, in the embodiment of the present disclosure, FIG. 1 is exemplified by a terminal being a mobile phone.

2 is a schematic flowchart of a service scheduling method according to an embodiment of the present disclosure. 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 disclosure, the first DCI is the DCI for the URLLC service, and the first DCI is used to instruct the terminal to schedule the URL LC 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 disclosure 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 disclosure may be a terminal in the communication system shown in FIG. 1.

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

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

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

Exemplarily, the embodiment of the present disclosure may implement the service scheduling method provided by the present disclosure by using the following four implementation manners.

The first possible implementation:

In this implementation manner, the network device redesigns the partial domain of the existing DCI based on the existing DCI for the eMBB service, so that the redesigned DCI can adapt to the requirements of the URLLC service, thereby redesigning the DCI. As the DCI for the URLLC service. In general, if the redesigned DCI needs to adapt to the requirements of the URLLC service, the payload size of the redesigned DCI needs to be greater than or equal to the load size of the DCI used for the eMBB service. In this scenario, the network device can be used for eMBB. The domain value of the partial domain in the DCI of the service is set to a predetermined threshold to indicate to the terminal that the DCI is a DCI for the URLLC service.

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

S201a1: The network device generates a second DCI.

The second DCI is the DCI used for the eMBB service.

S201a2: The network device sets a domain value of the preset domain in the second DCI to a predetermined threshold A to generate a first DCI.

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

In the embodiment of the present disclosure, after the network device sets the domain value of the preset domain in the second DCI to the predetermined threshold A, if the load size of the domain other than the preset domain in the second DCI is greater than the specified The network device sets the domain value of the partial domain of the second DCI except the preset domain to a predetermined threshold B, because the terminal threshold of the predetermined threshold B is not interpreted. Thus, the size of the payload of the DCI actually used for the URLLC service in the second DCI is equal to the specified payload size of the DCI for the URLLC service. Certainly, if the payload size of the domain other than the preset domain in the second DCI is equal to the DCI payload size used for the URLLC service, the network device may directly use the second DCI after the domain value is reset as the first DCI.

For example, if the payload size of the second DCI is 40 bits, the number of bits in the preset domain in the second DCI is 8 bits. At this time, the load size of the domain other than the preset domain in the second DCI is 32 bits (40-8). =32), since the DCI payload size for the URLLC service is 25 bits, 32>25, the network device needs to fill the number of 0s in the second DCI except for the preset domain to 32-25= 7. Thus, the resulting first DCI has the same load size as the second DCI.

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

For example, if the load size of the DCI for the URLLC service is set to C, the location of the DCI load for the URLLC service in the DCI may be: the DCI is selected in accordance with the predetermined condition from the order of the arrival. The location of the domain, or the location of the domain that satisfies the predetermined condition, or other predefined locations in the DCI, in the DCI, excluding the CRC and the preset domain, in order from the back to the front. Wherein, the above-mentioned domain that satisfies the predetermined condition selected in the order from the going to the following refers to: all the domains corresponding to the accumulated load when the load of the domain in the DCI is sequentially accumulated from the time of the arrival until the accumulated load size is equal to C; The domain that satisfies the predetermined condition in the order from the back to the front refers to: accumulating the load of the domain excluding the CRC and the preset domain in the DCI from the back to the front until the accumulated load is equal to C, the accumulated load Corresponding to all domains.

It should be noted that the base station scheduling the DCI for the eMBB service does not use the state in which the preset domain is set to the predetermined threshold A. For example, after the terminal decodes the DCI, it is found that the domain value of the preset domain in the DCI is the same as the preset threshold A, and the terminal can determine the DCI as the DCI for the URLLC service based on the domain values of the preset domains. .

For example, Table 1 below is used to illustrate the domain definition of the domain in the downlink fallback DCI. The fallback DCI is the DCI used for the eMBB service.

Table 1

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

Exemplarily, the network device may reset all the domain values of the TPC command for PUCCH domain, the PUCCH resource indicator field, and the PDSCH-to-HARQ feedback timing indicator field before the CRC to a predefined value, for example, all set to 0. For example, the domain value 2 of the TPC command for PUCCH field is reset to 00, the domain value 3 of the PUCCH resource indicator field is reset to 000, and the domain 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 foregoing S201a1 and S201a2, the indication information is a domain value of a preset domain in the first DCI, and the terminal may be based on a domain value of the preset domain in the first DCI. It is determined whether the first DCI is a DCI for a URLLC service. Specifically, the foregoing 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 domain value of the preset domain is the same as the predetermined threshold A, the terminal determines that the first DCI is a DCI for the URLLC service.

The second DCI is the DCI used for the eMBB service.

In the embodiment of the present disclosure, when the terminal monitors a first DCI, the terminal may decode the first DCI, and obtain a domain value of the preset domain in the first DCI, if the terminal finds the domain value and a pre- If the preset threshold A is the same, the terminal can consider that the first DCI is a DCI for the URLLC service, and the domain values of the other domains in the first DCI can be in accordance with the domain value of the DCI used for the URLLC service. Interpretation of meaning.

The second possible implementation:

In this implementation manner, the network device may configure a Radio Network Temporary Identity (RNTI) that is unique to the URL LC service for the terminal, that is, different RNTIs are used to distinguish DCIs of different services, and the terminal may use the first DCI according to the first DCI. The corresponding RNTI determines whether the first DCI is a DCI for a URLLC service.

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

S201b1: The network device generates a third DCI.

The third DCI is the DCI used for the URLLC service.

S201b2: The network device scrambles the CRC code in the third DCI by using the RNTI corresponding to the URLLC service to generate a first DCI.

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

Optionally, as shown in FIG. 4, in the embodiment of the present disclosure, the foregoing 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 CRC check on the CRC code. If the check passes, it determines that the first DCI is the DCI used for the URLLC service.

In the embodiment of the present disclosure, 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, the CRC of the DCI can be scrambled by using the proprietary RNTI corresponding to the service, and the scrambled DCI is sent to the terminal, and after the terminal monitors the DCI, If the terminal receives the RNTI of the target service (for example, the RNTI corresponding to the URLLC service), the terminal can use the RNTI to descramble the DCI. If the verification succeeds, 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 the different service to descramble the DCI. If the check is passed, the DCI is the DCI of the service corresponding to the RNTI.

The third possible implementation:

In this implementation manner, the network device may allocate an independent CORESET for the control channel of the URLLC service, that is, the DCI sent under the CORESET is the DCI used for the URLLC service, so that the terminal can detect the DCI in the CORESET. The DCI is directly determined to be the DCI for the URLLC service.

Optionally, as shown in FIG. 5, in the embodiment of the present disclosure, the foregoing indication information is configuration information of the CORESET, where the configuration information is used to indicate that the terminal monitors the DCI in the CORESET, and the DCI in the CORESET is used for DCI for URLLC services. Specifically, in the embodiment of the present disclosure, 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 disclosure, before S203, the method includes the following steps:

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

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

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

In the fourth possible implementation:

The implementation manner is implemented on the basis of the third possible implementation manner. Specifically, if a CORESET includes three search spaces, the network device may allocate a separate search space in the CORESET for the control channel of the URLLC service, that is, The DCI sent in the search space is DCI for the URLLC service, so that the terminal can directly determine the DCI as the DCI for the URLLC service after monitoring the DCI in the search space in the CORESET.

Optionally, as shown in FIG. 6, in the embodiment of the present disclosure, the configuration information of the CORESET is specifically used to indicate that the terminal monitors the DCI on a predetermined search space in the CORESET.

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

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

Further, in the embodiment of the present disclosure, the foregoing S203c3 specifically includes the following steps:

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

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

The service scheduling method provided by the embodiment of the present disclosure, after the network device generates the first DCI for the URLLC service, sends the first DCI to the terminal, and when the terminal listens to the first DCI, the terminal may directly determine according to the indication information. The first DCI is a DCI for the URLLC service, so that the terminal can effectively perform the scheduling of the URLLC service according to the first DCI for the URLLC service, thereby improving communication efficiency and performance.

It should be noted that the first DCI for the URLLC service designed by the embodiment of the present disclosure may be used for uplink scheduling and downlink scheduling, and details are not described herein again.

As shown in FIG. 7, the embodiment of the present disclosure provides a terminal 300, where the terminal 300 includes: a determining module 301 and a scheduling module 302, where:

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

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

Optionally, the foregoing indication information is a domain value of the preset domain in the first DCI; the determining module 301 is specifically configured to: if the load size of the first DCI is equal to a load size of the second DCI, and The domain value of the preset domain is the same as the predetermined threshold, and the first DCI is determined to be the DCI for the URLLC service, where the second DCI is the DCI for the eMBB service.

Optionally, the foregoing indication information is configuration information of a control resource set CORESET, where the configuration information is used to indicate that the terminal monitors DCI in the CORESET, and the DCI in the CORESET is a 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, where:

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

Optionally, the foregoing configuration information is specifically used to indicate that the terminal monitors the DCI on a predetermined search space in the CORESET; the monitoring module 304 is specifically configured to: according to the configuration information received by the receiving module, Monitoring the first DCI transmitted by the network device on the predetermined search space on a predetermined search space of the CORESET.

The terminal provided by the embodiment of the present disclosure, when the first DCI is monitored, the terminal may directly determine, according to the indication information, that the first DCI is a DCI for the URLLC service, so that the terminal can be used according to a proprietary URLLC service. The first DCI is effective for scheduling the URLLC service, improving communication efficiency and performance.

The terminal provided by the embodiment of the present disclosure can implement the process shown in any one of the foregoing method embodiments in FIG. 2 to FIG. 6 . To avoid repetition, details are not described herein again.

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

The generating module 401 is 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, where the first DCI is a DCI for a URLLC service, and the first DCI is used to indicate the terminal. The URLLC service is scheduled according to the first DCI.

Optionally, the generating module is specifically configured to: generate a second DCI, set a domain value of the preset domain in the second DCI to a predetermined threshold, and generate the first DCI; wherein the second DCI For DCI for eMBB service, the load size of the first DCI described above is equal to the load size of the second DCI.

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

a second sending module 403, configured to send, to the terminal, configuration information of a control resource set CORESET, where the configuration information is used to indicate that the terminal monitors DCI in the CORESET, and the DCI in the CORESET is used for the The DCI of the URLLC service is configured to send the first DCI generated by the generating module 401 to the terminal on the CORESET.

Optionally, the foregoing configuration information is specifically used to indicate that the terminal monitors DCI on a predetermined search space in the CORESET; the first sending module 402 is specifically configured to: in a predetermined search space in the CORESET The terminal sends the first DCI generated by the generating module.

The network device provided by the embodiment of the present disclosure, after generating the first DCI for the URLLC service, the network device sends the first DCI to the terminal, and when the terminal listens to the first DCI, the terminal may directly determine according to the indication information. The first DCI is a DCI for the URLLC service, so that the terminal can effectively perform the scheduling of the URLLC service according to the first DCI for the URLLC service, thereby improving communication efficiency and performance.

The network device provided by the embodiment of the present disclosure can implement the process shown in any one of the foregoing method embodiments in FIG. 2 to FIG. 6. To avoid repetition, details are not described herein again.

FIG. 9 is a schematic diagram of a hardware structure of a terminal that implements various embodiments of the present disclosure. 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, and a display unit 106. The user input unit 107, the interface unit 108, the memory 109, the processor 110, and the power source 111 and the like. It will be understood by those skilled in the art that the structure of the terminal 100 shown in FIG. 9 does not constitute a limitation of the terminal, and the terminal 100 may include more or less components than those illustrated, or combine some components, or different components. Arrangement. In the embodiment of the present disclosure, the terminal 100 includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.

The processor 110 is configured to: when the terminal monitors the first DCI, determine, according to the indication information, that the first DCI is a DCI for the URLLC service, where the indication information is used to indicate that the first DCI is DCI for the URLLC service; scheduling URLLC service according to the first DCI.

It should be understood that, in the embodiment of the present disclosure, the radio frequency unit 101 can be used for receiving and transmitting signals during and after receiving or transmitting information or a call, and specifically, receiving downlink data from the base station, and processing the data to the processor 110; The uplink data is sent to the base station. In general, 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 unit 101 can also communicate with the 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 to send and receive emails, browse web pages, and access streaming media.

The audio output unit 103 can convert the 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. Moreover, the audio output unit 103 can also provide audio output (eg, call signal reception sound, message reception sound, etc.) related to a specific function performed by the terminal 100. The audio output unit 103 includes a speaker, a buzzer, a receiver, and the like.

The input unit 104 is for receiving an audio or video signal. The input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042 that images an still picture or video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The data is processed. The processed image frame can 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 medium) or transmitted via the radio unit 101 or the network module 102. The microphone 1042 can receive sound and can process such sound as audio data. The processed audio data can be converted to a format output that can be transmitted to the mobile communication base station via the radio unit 101 in the case of a telephone call mode.

Terminal 100 also includes at least one type of sensor 105, such as a light sensor, 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 close 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 all directions (usually three axes). When it is stationary, it can detect the magnitude and direction of gravity. It can be used to identify the terminal attitude (such as horizontal and vertical screen switching, related games, Magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.; sensor 105 may also include fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared Sensors, etc., will not be described here.

The display unit 106 is for displaying information input by the user or information provided to the user. The display unit 106 can include a display panel 1061. The display panel 1061 can 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 can be used to receive input numeric or character information, and to 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. The touch panel 1071, also referred to as a touch screen, can collect touch operations on or near the user (such as the user using a finger, a stylus, or the like on the touch panel 1071 or near the touch panel 1071. operating). The touch panel 1071 may include two parts of a touch detection device and a touch controller. Wherein, the touch detection device detects the touch orientation of the user, and detects a 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 the touch information into contact coordinates, and sends the touch information. To the processor 110, the commands sent by the processor 110 are received and executed. In addition, the touch panel 1071 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. 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 buttons, switch buttons, etc.), trackballs, mice, and joysticks, and are not described herein.

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

The interface unit 108 is an interface in which an external device is connected to the terminal 100. For example, the 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 having an identification module, and an audio input/output. (I/O) port, video I/O port, headphone port, and more. The interface unit 108 can be configured to receive input from an external device (eg, data information, power, etc.) and transmit the received input to one or more components within the terminal 100 or can be used at the terminal 100 and external devices Transfer data between.

Memory 109 can 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 required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to Data created by the use of the mobile phone (such as audio data, phone book, etc.). Further, the memory 109 may include a high speed random access memory, and may also include a nonvolatile memory such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

Processor 110 is the control center of terminal 100, which connects various portions of the entire terminal 100 using various interfaces and lines, by running or executing software programs and/or modules stored in memory 109, and recalling data stored in memory 109. The various functions and processing data of the terminal 100 are executed to perform overall monitoring of the terminal 100. 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 an operating system, a user interface, an application, etc., and a modulation solution The processor mainly handles wireless communication. It can be understood that the above modem processor may not be integrated into the processor 110.

The terminal 100 may further include a power source 111 (such as a battery) for supplying power to various components. Alternatively, the power source 111 may be logically connected to the processor 110 through a power management system to manage charging, discharging, and power management through the power management system. And other functions.

In addition, the terminal 100 includes some functional modules not shown, and details are not described herein again.

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

The processor 501 generates a first DCI, and the transceiver 502 is configured to send, to the terminal, the first DCI generated by the processor 501, where the first DCI is a DCI for the URLLC service, and the first DCI is used. Instructing the terminal to schedule the URLLC service according to the first DCI.

In the disclosed embodiment, in FIG. 8, the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 501 and various circuits of memory represented by memory 503. . The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein. The bus interface provides an interface. Transceiver 502 can be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium. For different user devices, the user interface 504 may also be an interface capable of externally connecting the required devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, 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 in performing operations.

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

Optionally, an embodiment of the present disclosure further provides a terminal, including a processor, a memory, a computer program stored on the memory and executable on the processor, and the computer program is executed by the processor to implement the foregoing Embodiment 1. The process of the service scheduling method can achieve the same technical effect. To avoid repetition, it will not be repeated here.

Optionally, the embodiment of the present disclosure further provides a network device, including a processor, a memory, a computer program stored on the memory and executable on the processor, and the computer program is executed by the processor to implement the foregoing Embodiment 1. The process of the business scheduling method, and can achieve the same technical effect, in order to avoid duplication, no longer repeat here.

The embodiment of the present disclosure further provides a computer readable storage medium, where the computer readable storage medium stores a computer program, and when the computer program is executed by the processor, implements multiple processes of the service scheduling method in the foregoing embodiment, and can reach The same technical effect, in order to avoid repetition, will not be described here. The computer readable storage medium, such as a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

The embodiment of the present disclosure further provides a computer readable storage medium, where the computer readable storage medium stores a computer program, and when the computer program is executed by the processor, implements multiple processes of the foregoing random access method embodiment, and can achieve the same The technical effect, in order to avoid duplication, will not be repeated here. The computer readable storage medium, such as a ROM, a RAM, a magnetic disk, or an optical disk.

It is to be understood that the term "comprises", "comprising", or any other variants thereof, is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes those elements. It also includes other elements that are not explicitly listed, or elements that are inherent to such a process, method, article, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better. Implementation. Based on such understanding, the technical solution of the present disclosure, which is essential or contributes to the related art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, CD-ROM). The instructions include a number of instructions for causing a terminal (which may be a cell phone, computer, server, air conditioner, or network device, etc.) to perform the methods described in various embodiments of the present disclosure.

The embodiments of the present disclosure have been described above with reference to the drawings, but the present disclosure is not limited to the specific embodiments described above, but the specific embodiments described above are merely illustrative and not restrictive, and those skilled in the art In the light of the present disclosure, many forms may be made without departing from the scope of the disclosure and the scope of the appended claims.

Claims

A service scheduling method is applied to a terminal, and the method includes:

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

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

The URLLC service is scheduled according to the first DCI.
The method of claim 1 wherein

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

Determining, according to the indication information, that the first DCI is a DCI for a URLLC service, including:

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 predetermined threshold, determining that the first DCI is a DCI for the URLLC service;

The second DCI is a DCI for enhancing mobile bandwidth eMBB service.
The method of claim 1 wherein

The indication information is configuration information of a control resource set CORESET, the configuration information is used to indicate that the terminal monitors DCI in the CORESET, and the DCI in the CORESET is a DCI for the URLLC service.
The method according to claim 3, wherein the method further comprises: before determining whether the first DCI is a DCI for a URLLC service according to the indication information, the method further comprising:

Receiving configuration information of the CORESET sent by the network device to the terminal;

And monitoring, according to the configuration information, the first DCI sent by the network device on the CORESET on the CORESET.
The method of claim 4, wherein the configuration information is specifically for instructing the terminal to monitor a 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, including:

And monitoring, according to the configuration information, the first DCI sent by the network device on the predetermined search space on a predetermined search space of the CORESET.
A service scheduling method is applied to a network device, and the method includes:

Generating a first DCI;

Sending the first DCI to the terminal;

The first DCI is a DCI for low-latency, high-reliability connection of the URLLC service, and the first DCI is used to instruct the terminal to schedule the URLLC service according to the first DCI.
The method of claim 6 wherein said generating said first DCI comprises:

Generating a second DCI;

Setting a domain value of the preset domain in the second DCI to a predetermined threshold to generate the first DCI;

The second DCI is a DCI for enhancing a mobile bandwidth eMBB service, and a payload size of the first DCI is equal to a payload size of the second DCI.
The method of claim 6 wherein

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

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

The sending the first DCI to the terminal includes:

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

Sending the first DCI to the terminal on the CORESET, including:

Transmitting the first DCI to the terminal on a predetermined search space in the CORESET.
A terminal comprising:

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

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

And a scheduling module, configured to schedule the URLLC service according to the first DCI determined by the determining module.
The terminal according to claim 10, wherein

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 predetermined threshold, determining that the first DCI is a DCI for the URLLC service;

The second DCI is a DCI for enhancing mobile bandwidth eMBB service.
The terminal according to claim 10, wherein

The indication information is configuration information of a control resource set CORESET, the configuration information is used to indicate that the terminal monitors DCI in the CORESET, and the DCI in the CORESET is a DCI for the URLLC service.
The terminal of claim 12, wherein the terminal further comprises:

a receiving module, configured to receive configuration information of the CORESET sent by the network device to the terminal;

And a monitoring module, configured to monitor, according to the configuration information received by the receiving module, the first DCI sent by the network device on the CORESET on the CORESET.
The terminal according to claim 13, wherein the configuration information is specifically used to indicate that the terminal monitors DCI on a predetermined search space in the CORESET;

The monitoring module is configured to: monitor, according to the configuration information received by the receiving module, the first DCI sent by the network device on the predetermined search space on a predetermined search space of the CORESET .
A network device, including:

Generating a module, configured to generate a first DCI;

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

The first DCI is a DCI for low-latency, high-reliability connection of the URLLC service, and the first DCI is used to instruct the terminal to schedule the URLLC service according to the first DCI.
The network device according to claim 15, wherein

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

The second DCI is a DCI for enhancing a mobile bandwidth eMBB service, and a payload size of the first DCI is equal to a payload size of the second DCI.
The network device of claim 15, wherein the network device further comprises:

a second sending module, configured to send configuration information of a control resource set CORESET to the terminal, where the configuration information is used to indicate that the terminal monitors DCI in the CORESET, and the DCI in the CORESET is used for the URLLC Business DCI;

The first sending module is specifically configured to send, by using the CORESET, the first DCI generated by the generating module to the terminal.
The network device according to claim 17, wherein the configuration information is specifically used to indicate that the terminal monitors DCI on a predetermined search space in the CORESET;

The first sending module is specifically configured to: send the first DCI generated by the generating module to the terminal in a predetermined search space in the CORESET.
A terminal comprising a processor, a memory, and a computer program stored on the memory and operable on the processor, the computer program being executed by the processor to implement any one of claims 1 to 5 The steps of the service scheduling method described in the item.
A network device comprising a processor, a memory, and a computer program stored on the memory and operable on the processor, the computer program being executed by the processor to implement any of claims 6 to 9 A step of the described service scheduling method.
A computer readable storage medium, wherein the computer readable storage medium stores a computer program, the computer program being executed by a processor to implement the steps of the service scheduling method according to any one of claims 1 to 9. .