WO2019115225A2 - Procédés et dispositifs de planification de ressource dans un système de communication - Google Patents

Procédés et dispositifs de planification de ressource dans un système de communication Download PDF

Info

Publication number
WO2019115225A2
WO2019115225A2 PCT/EP2018/082750 EP2018082750W WO2019115225A2 WO 2019115225 A2 WO2019115225 A2 WO 2019115225A2 EP 2018082750 W EP2018082750 W EP 2018082750W WO 2019115225 A2 WO2019115225 A2 WO 2019115225A2
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
response
network device
downlink data
uplink resource
Prior art date
Application number
PCT/EP2018/082750
Other languages
English (en)
Other versions
WO2019115225A3 (fr
Inventor
Leilei Li
Shenglin SHI
Zhijun Liao
Yaling QU
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Publication of WO2019115225A2 publication Critical patent/WO2019115225A2/fr
Publication of WO2019115225A3 publication Critical patent/WO2019115225A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient

Definitions

  • Embodiments of the present disclosure generally relate to communication techniques and more specifically, to methods and devices for resource scheduling in a communication system.
  • a terminal device in connection with the network requires an uplink resource to transmit uplink information to a network device, while the network device transmits downlink information to the terminal device using a downlink resource.
  • the uplink and downlink resources are scheduled by the network device to serve the terminal devices in its the coverage.
  • a narrowband Intemet-of-Things (NB-IoT) communication system is an IoT communication system operating on a narrowband (e.g. a spectrum of 180 kHz), which supports Machine Type Communications (MTC) with low throughput, low complexity, and low energy consumption.
  • MTC Machine Type Communications
  • the IoT communication system can serve a massive amount of terminal devices and supports extended coverage.
  • a terminal device probably transmits and receives information with a low frequency.
  • the communication complexity and energy consumption at the terminal side need to be reduced as much as possible.
  • Uplink and downlink resources scheduling in the communication system may affect various aspects of the system, including the communication complexity, communication efficiency, resource utilization, energy consumption, and the like. Due to the characteristics of the NB-IoT communication system, such as the low throughput, low complexity, low energy consumption, and the like, resource scheduling becomes a more challenging task.
  • Embodiments of the present disclosure provide a solution for resource scheduling in a communication system.
  • a method implemented at a network device of a communication system includes transmitting downlink data to a terminal device.
  • the method also includes predicting, based on a traffic mode of the terminal device, whether a response to the downlink data is to be transmitted by the terminal device, and in response to predicting that the response to the downlink data is to be transmitted by the terminal device, transmitting a grant of an uplink resource without waiting for an uplink resource scheduling request from the terminal device.
  • the method further includes receiving, from the terminal device, the response to the downlink data using the uplink resource.
  • a method implemented at a network device of a communication system includes receiving uplink data from a terminal device.
  • the method also includes predicting, based on a traffic mode of the terminal device, whether downlink data is to be transmitted to the terminal device, and in response to predicting that downlink data is to be transmitted to the terminal device, determining a period of delay time for a response to the uplink data.
  • the method further includes in response to the period of delay time expiring and the network device having the downlink data to be transmitted, transmitting to the terminal device the response and at least part of the downlink data using a same downlink resource.
  • a method implemented at a terminal device of a communication system includes receiving downlink data from a network device.
  • the method also includes receiving from the network device a grant of an uplink resource in absence of a transmission of an uplink resource scheduling request to the network device, the grant of the uplink resource being transmitted by the network device in response to predicting, based on a traffic mode of the terminal device, that a response to the downlink data is to be transmitted by the terminal device.
  • the method further includes transmitting, to the network device, the response to the downlink data using the uplink resource.
  • a method implemented at a terminal device of a communication system includes transmitting uplink data to a network device.
  • the method further includes after a period of time since the receiving of the uplink data, receiving at least part of downlink data and a response to the uplink data from the network device using a same downlink resource, the response being delayed by the network device for the period of time based on a traffic mode of the terminal device.
  • the network device includes a processor and a memory coupled to the processor, the memory having instructions stored thereon which, when executed by the processor, cause the network device to perform the method according to the first or second aspect.
  • a terminal device in a sixth aspect of the present disclosure, includes a processor and a memory coupled to the processor, the memory having instructions stored thereon which, when executed by the processor, cause the network device to perform the method according to the third or fourth aspect.
  • a computer readable medium has computer executable instructions stored thereon, the computer executable instructions, when executed by one or more processors, causing the one or more processors to perform steps of the method according to any of the first aspect to the fourth aspect.
  • FIG. 1 is a diagram illustrating a communication system in which embodiments described herein can be implemented
  • FIG. 2 illustrates a communication process of resource scheduling in a traditional communication system
  • FIG. 3 illustrates a flowchart of a communication process of uplink resource scheduling in accordance with some embodiments of the present disclosure
  • Fig. 4 illustrates a flowchart of a communication process of downlink resource scheduling in accordance with some embodiments of the present disclosure
  • FIG. 5 illustrates a flowchart of a communication process of uplink resource scheduling at a network device side in accordance with some embodiments of the present disclosure
  • FIG. 6 illustrates a flowchart of a communication process of downlink resource scheduling at a network device side in accordance with some embodiments of the present disclosure
  • FIG. 7 illustrates a flowchart of a communication process of uplink resource scheduling at a terminal device side in accordance with some embodiments of the present disclosure
  • FIG. 8 illustrates a flowchart of a communication process of downlink resource scheduling at a terminal device side in accordance with some embodiments of the present disclosure
  • FIG. 9 illustrates a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.
  • Fig. 10 illustrates a block diagram of an example computer readable medium in accordance with some embodiments of the present disclosure.
  • the term“includes” and its variants are to be read as open-ended terms that mean“includes, but is not limited to.”
  • the term“based on” is to be read as“based at least in part on.”
  • the term“one embodiment” and“the embodiment” are to be read as“at least one embodiment.”
  • the terms“first,”“second,” and the like may refer to different or the same objects. Other definitions, either explicit or implicit, may be included below.
  • the term“network device” refers to a base station or other entities or nodes of a specific functionality in a communication network.
  • Base station may represent a Node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low power node such as a femto node, a pico node, and the like. Coverage of the base station, namely a geographical region capable of providing service therein, is referred to as a cell.
  • the terms “network device” and “base station” may be used interchangeably, and eNB may be mainly used as an example of the network device for purpose of discussion.
  • the term“terminal device” or“user equipment (UE)” refers to any terminal device capable of wirelessly communicating with the base station or counterparts.
  • the terminal device may include a mobile terminal (MT), a subscriber station (SS), a portable subscriber station (PSS), a mobile station (MS) or an access terminal (At), and any of the foregoing devices on a board.
  • MT mobile terminal
  • SS subscriber station
  • PSS portable subscriber station
  • MS mobile station
  • At access terminal
  • the terminal device may be a mobile terminal, a fixed terminal, or a portable terminal of any type, including a mobile phone, a site, a unit, a device, a multimedia computer, a multimedia tablet, an Internet node, a communicator, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio/video player, a digital camera/video camera, a positioning device, a television receiver, a wireless broadcast receiver, an E-book device, a game device, or other devices for communication, or any combination of the above.
  • PCS personal communication system
  • PDA personal digital assistant
  • the terminal device may be an IoT terminal device, including a smart appliance (e.g. a rice cooker, a refrigerator, a washing machine, a water heater, and the like), a smart meter (e.g. a water meter, a ammeter, a gas meter, and the like), an intelligent electronic device (e.g. a smoke detector, a switch, a transformer, and the like) and/or any other electronic devices that can be internetworked.
  • a smart appliance e.g. a rice cooker, a refrigerator, a washing machine, a water heater, and the like
  • a smart meter e.g. a water meter, a ammeter, a gas meter, and the like
  • an intelligent electronic device e.g. a smoke detector, a switch, a transformer, and the like
  • Fig. 1 shows a communication system 100 in which embodiments of the present disclosure can be implemented.
  • the communication system 100 includes a network device 100 and terminal devices 120-1, 120-2, 120-3 and 120-4 located within a serving cell of the network device 110.
  • terminal devices 120 may be collectively or individually referred to as terminal devices 120.
  • the network device 110 and the terminal device 120 can communicate with each other to facilitate transmissions of various traffic data, control information, or the like.
  • a transmitter of transmission may be the network device 110, and a receiver may be one or more terminal devices 120. Such transmission may be referred to as downlink (DL) transmission.
  • the transmitter of transmission may be a terminal device 120, and the receiver may be the network device 110.
  • Such transmission may be referred to as uplink (UL) transmission.
  • Communications in the communication system 100 may be implemented in accordance with any suitable communication protocols, including, but no limited to, cellular communication protocols such as the first generation (1G), the second generation (2G), the third generation (3G), the fourth generation (4G), the fifth generation (5G), wireless LAN communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and/or any other protocols that are currently known or to be developed in the future.
  • the communication system 100 is embodied as an Internet-of-Things (IoT) communication system, for example, a narrowband IoT (NB-IoT) communication system operating on a narrowband spectrum.
  • IoT Internet-of-Things
  • NB-IoT narrowband IoT
  • the terminal devices 120 may include IoT terminal devices, such as various smart appliances, smart meters, intelligent electronic devices, and/or any other electronic devices that can be internetworked.
  • the communication of the IoT terminal devices is characterized by low throughput, a low complexity and/or low energy consumption.
  • the IoT terminal devices may not communicate frequently with the network device 110, and the interval time between communications may be hours, days, or even months, with a small amount of data in each communication.
  • the network device 110 may serve more or fewer terminal devices, and the served terminal devices may be of identical or different types.
  • other terminal devices such as mobile phones or notebook computers may also be located in the serving cell and can be served by the network device 110.
  • the communication system 100 may include more network devices and terminal devices at its service.
  • the NB-IoT communication system is described as an example in the following discussion, it would be appreciated that the solution according to embodiments of the present disclosure may be likewise applied to communication systems of other types.
  • a network device in the communication system needs to schedule uplink and downlink resources to support communication in the corresponding directions.
  • Resource scheduling may affect various aspects of the system, including the communication complexity, communication efficiency, resource utilization, energy consumption, and the like.
  • a terminal device may request the uplink resource from the network device by initiating a random access (RA) process.
  • RA random access
  • the network device may transmit data to the terminal devices using a particular downlink resource according to the communication requirement.
  • Fig. 2 shows a communication process 200 of resource scheduling in a traditional communication system.
  • a network device 202 and a terminal device 201 are involved in the process 200.
  • the terminal device 201 expects to transmit information to the network device 202 and thus needs to initiate a random access process 205 to request from the network device an uplink resource for information transmission.
  • the terminal device 201 transmits at 210 a random assess request via a Physical Random Access Channel (PRACH) to the network device 202.
  • PRACH Physical Random Access Channel
  • the random assess request is also referred to as Message 1 (MSG 1) including a random access preamble.
  • MSG 1 Message 1
  • the network device 202 transmits to the terminal device 201 a response to the random access request, which is also referred to as a random access response or Message 2 (MSG 2). Then, the terminal device 202 transmits at 220 to the network device 202 uplink data, which is also referred to as Message 3 (MSG 3). At 225, the network device 202 transmits to the terminal device 201 a contention resolution, which is also referred to as Message 4 (MSG 4). The Message 2 or Message 4 may indicate the uplink resource to the terminal device 202. After the random access process 205 is completed, the terminal device 202 may transmit at 230information to the network device 202 using the scheduled uplink resource.
  • the network device 202 receives at 240 uplink data transmitted by the terminal device 201.
  • the network device 202 transmits at 245 a response to the uplink data to the terminal device 201 using an available downlink resource.
  • the network device 202 After transmitting the response, if the network device 202 obtains downlink data to be transmitted to the terminal device 201, the network device 202 transmits at 250 downlink data to the terminal device 201 using a further available downlink resource.
  • the network device 202 may schedule the respective downlink resources based on real-time demands of the downlink transmission.
  • NPDCCH Narrowband Physical Downlink Control Channel
  • NPDSCH Narrowband Physical Downlink Shared Channel
  • NPUSCH Narrowband Uplink Shared Channel
  • the scheduling resource solution includes a solution for uplink resource scheduling.
  • the network device may proactively transmit, based on a traffic mode of the terminal device, a grant of the uplink resource to the terminal device. This avoids resources and signaling overheads required for responding to the uplink resource scheduling request, and reduces the communication complexity and energy consumption at the terminal device.
  • the resource scheduling solution according to the present disclosure also includes a solution for downlink resource scheduling.
  • the network device delays, based on a traffic mode of the terminal device, a response to uplink data to be transmitted to the terminal device, and merge the response with downlink data to be transmitted in a same downlink resource for transmission. This improves the utilization of the downlink resource and reduces the communication complexity and energy consumption at the terminal device.
  • Fig. 3 shows a flowchart of a communication process 300 of uplink resource scheduling in accordance with some embodiments of the present disclosure.
  • the process 300 will be described with reference to Fig. 1.
  • the process 300 involves the network device 110 and the terminal device 120 in the communication system 100 of Fig.1.
  • the network device 110 transmits downlink data to the terminal device 120.
  • the network device 110 may need to transmit the downlink data to the terminal device 120 in many circumstances.
  • the network device 110 may determine whether an access connection to the terminal device 120 is a mobile terminated (MT) access.
  • MT mobile terminated
  • the core network for example, an element for managing the IoT terminal devices in the core network
  • the core network expects to trigger a report of the terminal device and transmit the corresponding downlink data via a core network element (e.g. an evolved packet core (EPC)) to the network device 110.
  • the network device 110 may page and establish a connection with the terminal device 120.
  • EPC evolved packet core
  • the network device 110 may determine, from an identification in a Radio Resource Control (RRC) connection request transmitted from the terminal device 120, that the access of the terminal device 120 is an MT access. After establishing the connection, the network device 110 may send the downlink data to the terminal device 120.
  • RRC Radio Resource Control
  • the network device 110 may also transmit the downlink data to the terminal device 120 in other cases.
  • the element for managing the IoT terminal device may be implemented by an element independent of the EPC or integrated into the EPC.
  • the network device 110 may determine, based on a traffic mode of the terminal device 120, whether an uplink resource is proactively allocated to the terminal device 120 without waiting for an uplink resource scheduling request from the terminal device 120. Specifically, at 310, the network device 110 predicts whether, based on the traffic mode of the terminal device 120, a response to the downlink data is to be transmitted by the terminal device 120.
  • the traffic mode of the terminal device is also referred to as a traffic model, which indicates characteristics related to payloads and periods of uplink and downlink traffic and the like.
  • the traffic mode may indicate whether a certain terminal device will transmit the uplink data, the downlink data, or a response to the downlink data, or the occurrence period of the traffic, and the like.
  • each terminal device may be assigned with a corresponding traffic mode based on the type and traffic of the terminal device.
  • the traffic mode of the terminal device 120 may be acquired by the network device 110 in advance or reported by the terminal device 120. In some cases, the traffic mode of the terminal device 120 may be changed according to the configuration.
  • Traffic modes for terminal device have been specified in some communication standards, including a mobile autonomous reporting (MAR) traffic mode, a network command (NC) traffic mode, a software update/reconfiguration traffic mode, and the like.
  • MAR traffic mode may specifically include a MAR exception report model and a MAR periodic report.
  • the traffic mode of the terminal device 120 may be selected from these traffic modes.
  • Table 1 provides some specific illustrations of these traffic modes. It would be appreciated that these illustrations are provided only as an example, and with development of the communication techniques, specific divisions of the traffic modes may be updated, and other new traffic modes may also be included.
  • the network device 110 may predict whether the terminal device 120 will transmit the response to the downlink data based thereon.
  • the network device 110 determines that the traffic mode of the terminal device 120 is a NC traffic mode. It can be determined from Table 1 that the characteristic of the NC traffic mode is that: there is a certain probability that the terminal device 120 is to transmit the response to the downlink data. Therefore, the network device 110 predicts that the response to the downlink data is to be transmitted by the terminal device 120. In some other embodiments, if other traffic modes also indicate that the reception of the downlink data will trigger any uplink transmission by the terminal device 120, the network device 110 may also predict that the response to the downlink data is to be transmitted by the terminal device 120.
  • the transmission of the downlink data by the network device 110 at 305 is configured depending on the traffic mode of the terminal device 120. For example, for the NC traffic mode, the network device 110, upon buffered downlink data is running out in the transmission, sets an indication in a last data packet to request the terminal device to transmit an uplink response.
  • the network device 110 may set the indication in a polling (P) field of a Radio Link Control Protocol Data Unit (RLC PDU).
  • P polling
  • RLC PDU Radio Link Control Protocol Data Unit
  • the network 110 predicts that the response to the downlink data is to be transmitted by the terminal device 120, at 315, the network 110 sends a grant of the uplink resource to the terminal device 120 without waiting for an uplink resource scheduling request from the terminal device 120.
  • the grant of the uplink resource By proactively sending the grant of the uplink resource to the terminal device 120, it is possible to reduce the resource and signaling overheads and energy consumption caused by the uplink resource scheduling request of the terminal device 120.
  • the network device 110 may transmit a resource of a Narrowband Physical Uplink Shared channel (NPUSCH) to the terminal device 120 for the user selection.
  • NPUSCH Narrowband Physical Uplink Shared channel
  • the terminal device 120 may take a certain time for the terminal device 120 to prepare the response to the downlink data, such as radio link control (a RLC status report) and/or an uplink report of an application layer.
  • the RLC status report may include an acknowledgement (ACK) or a negative acknowledgement (NACK).
  • the network device 110 may transmit the grant of the uplink resource to the terminal device 120 after a period of time since the transmission of the downlink data.
  • the period of time may be predetermined and may be varied depending on the processing capability of the terminal device 120 or may be set as a fixed value (e.g. 300ms, 400ms, 500ms, etc.) for various terminal devices.
  • the period of time may be based on the time taken by transmitting the downlink data from the network device 110 to the terminal device 120. It would be appreciated that the period of time may be set as other values depending on the actual system deployment.
  • the network device 110 may set a timer corresponding to the period of time and start the timer after transmitting the downlink data and determining to proactively transmit the grant.
  • the network device 110 transmits the proactive grant to the terminal device 120 after the time expires.
  • the network device 110 may terminate the proactive grant of the uplink resource and respond to the scheduling request. In other examples, the network device 110 may continue to transmit the grant of the uplink resource, for example, immediately after receiving the request.
  • the scheduling request sent by the terminal device 120 may be any message that is used to request an uplink resource from the network device 110. For example, if the uplink resource is requested in a random access process, the uplink resource scheduling request may be a random access request.
  • the network device 110 determines, based on the traffic mode of the terminal device 120, whether a proactive grant of an uplink resource is to be transmitted. In some embodiments, the network device 110 may also determine whether such proactive grant is to be transmitted based on other factors. These factors may include a number of repetitions associated with a transmission related to the terminal device 120 and/or a number of terminal devices served by the network device 110.
  • the number of repetitions associated with a transmission related to the terminal device 120 refers to a number of repetitions for sending a data block by the terminal device 120 in an uplink transmission or for transmitting a data block to the terminal device 120 in a downlink transmission.
  • the number of repetitions may affect the resources consumed by the terminal device 120 and the network device 110 to successfully perform resource scheduling in the case that the terminal device 120 issues the uplink resource scheduling request to request the resource scheduling. If the number of repetitions is high, it indicates that in the resource scheduling process (e.g. the random access process) performed in response to the request of the terminal device 120, the signaling between the network device 110 and/or the terminal device 120 may be repeated for multiple times so as to achieve a successful transmission.
  • the resource scheduling process e.g. the random access process
  • the network device 110 determines whether the number of repetitions associated with a transmission related to the terminal device 120 is greater than a repetition number threshold. If the number of repetitions is greater than the repetition number threshold (and it is predicted that the response is to be transmitted by the terminal device 120), the network device 110 proactively transmits the grant of the uplink resource to the terminal device 120.
  • the repetition number threshold may be set as any predetermined value. The setting the repetition number threshold may be based on the available uplink resources of the network device 110 or other factors.
  • the number of repetitions associated with the terminal device 120 may be determined based on a coverage level of the terminal device 120.
  • a coverage level of a terminal device is associated with a channel quality of the terminal device.
  • the channel qualities of different terminal devices may be varied due to their distances to the network device, their deployment environments, and the like.
  • the terminal devices are divided into different coverage levels, each of which is assigned with a different number of repetitions based on the corresponding channel quality.
  • the coverage levels may include a normal coverage level, a robust coverage level, and an extreme coverage level. Different coverage levels are related with different numbers of repetitions. In some specifications, a different coverage level indicates a number of repetitions associated with a different quality of channel. For example, for transmission on NPDCCH, NPDSCH and NPUSCH, each of the normal coverage level, the robust coverage level, and the extreme coverage level indicates a same or different number of repetitions. In the embodiments of the present disclosure, for a great number of repetitions, the resources and signaling overheads in the resource scheduling process requested by the terminal device 120 may be saved significantly by proactively transmitting the grants of the uplink resources by the network device 110.
  • the network device 110 may transmit a proactive grant of an uplink resource to the terminal device 120 with a corresponding coverage level (for example, the extreme coverage level). For terminal devices with other coverage levels (for example, a smaller number of repetitions), the network device 110 may not transmit the proactive grant, but wait for the uplink resource scheduling request transmitted by the terminal device 120.
  • a corresponding coverage level for example, the extreme coverage level.
  • the network device 110 may not transmit the proactive grant, but wait for the uplink resource scheduling request transmitted by the terminal device 120.
  • the network device 110 may determine, based on the number of terminal devices served by the network device 110, whether the proactive grant of the uplink resource is to be transmitted. If there is a great number of terminal devices served by the network device 110 (such as a great number of terminal devices having access to the network device 110), a contention for the uplink resource of the network device 110 is relatively intense. In order to increase the resource utilization, upon predicting that the response is to be transmitted by the terminal device 120, the network device 110 may transmit the proactive grant of the uplink resource to the terminal device 120 in the case that there is a great number of terminal devices (for example, being greater than the number threshold) being served.
  • the network device 110 may not need to transmit the grant of the uplink resource proactively, but instead wait for the uplink resource scheduling request from the terminal device 120.
  • the terminal device 120 receives at 305 the downlink data from the network device 110.
  • the terminal device 120 receives the grant of the uplink resource from the network device 110.
  • the terminal device 120 transmits a response to the downlink data to the network device 110 using the granted uplink resource.
  • Such response may include an acknowledgement of reception of the downlink data, for example ACK/NACK.
  • the response to the downlink data may include a triggered application layer uplink report after the terminal device 120 receives the downlink data.
  • the network device 110 may transmit at 320 the response to the core network after receiving the response to the downlink data from the terminal device 120 using the uplink resource.
  • the response may be transmitted via a non-access stratum to an EPC of the core network and then transmitted to an element for managing the terminal device 120 of a type of IoT (for example, an IoT application entertainment platform (IoT AEP)) as required.
  • IoT AEP IoT application entertainment platform
  • a communication process 400 of downlink resource scheduling will be described below with reference to Fig. 4.
  • the process 400 will be described with reference to Fig. 1.
  • the process 400 involves the network device 110 and the terminal device 120 in the communication system 100 of Fig. 1.
  • the terminal device 120 transmits uplink data to the network device 110.
  • the terminal device 120 may need to transmit the uplink data to the network device 110.
  • the terminal device 120 needs to report information to the network device 110 according to a predetermined configuration.
  • the access connection between the terminal device 120 and the network device 110 may be a Mobile Originated (MO) access.
  • MO Mobile Originated
  • the resource for sending the uplink data by the terminal device 120 may be proactively granted to the terminal device 120 according to the process 300 as discussed above, or may be obtained in other ways (for example through the random access process).
  • the network device 110 receives the uplink data of the terminal device 120 and needs to transmit a response to the uplink data (such as a RLC status report) to the terminal device 120.
  • the network device 110 may delay the response to the uplink data for a period of time so as to be merged and transmitted with downlink data.
  • the network 110 predicts, based on the traffic mode of the terminal device 120, whether downlink data is to be transmitted to the terminal device 120.
  • the traffic mode of the terminal device indicates characteristics related to payloads and periods of uplink and downlink traffic. By the traffic mode of the terminal device 120, the network 110 may predict whether the downlink data is to be transmitted to the terminal device 120.
  • the network device 110 predicts that the downlink data is to be transmitted, and such downlink data may include information expected to be transmitted to the terminal device 120 from the core network side, such as the downlink acknowledgement information.
  • This example scenario may occur in the following condition: the network device 110 transmits, upon receiving the uplink data from the terminal device 120 at 405, the uplink data via a non-access stratum to the core network (for example, to the EPC element of the core network, which is then forwarded by the EPC to IoT AEP); and in response to the uplink data, the core network expects to transmit the downlink acknowledgement information.
  • the downlink acknowledgement information from the core network may be considered as the downlink data and transmitted by the network device 110.
  • the confirmation information may include various contents, and the embodiments of the present disclosure are not limited in this regard.
  • the network device 110 may perform the prediction accordingly.
  • the network device 110 determines a period of delay time for a response to the uplink data received at 405.
  • the network device 110 may not directly schedule the downlink resource to transmit the response to the uplink data, but instead delay the response for the period of time.
  • the period of delay time may be configured with any predetermined value (such as 50ms, lOOms, l50ms).
  • the network device 110 may set a timer corresponding to the period of delay time, and start the timer after receiving the uplink data and predicting that the downlink data is to be transmitted.
  • the network device 110 may buffer the downlink data if it obtains the downlink data to be transmitted (for example, it receives the downlink data from the core network).
  • the network device 110 transmits to the terminal device 120 at least part of the downlink data and the response to the previously received uplink data using the same downlink resource.
  • the network device 110 may merge and transmit all the downlink data and the response in the next downlink transmission.
  • the network device 110 may merge and transmit the response and the possible downlink data in a single downlink transmission, thereby saving the downlink resource, lowering the signaling overheads and reducing the energy consumption of the device.
  • the network device 110 may transmit the response to the uplink data in separate using the downlink resource.
  • the network device 110 determines, based on the traffic mode of the terminal device 120, whether the response and the downlink data are merged for transmission. In some embodiments, the network device 110 may determine, based on other factors, whether the response and the downlink data are merged for transmission. These factors may include a number of repetitions associated with the terminal device 120 and/or a number of terminal devices served by the network device 110.
  • the number of repetitions associated with a transmission related to the terminal device 120 may affect the resources consumed by transmission of the downlink data and the response to the uplink data. If the number of repetitions is large, it indicates that a success reception of the response and the downlink data can be achieved only if a number of repetitions are performed. In order to reduce the resources and energy consumption, in some embodiments, the network device 110 determines whether the number of repetitions associated with a transmission related to the terminal device 120 is greater than the repetition number threshold. If the number of repetitions is greater than the repetition number threshold (and predicting that the downlink data is to be transmitted), the network device 110 determines the period of delay time for delaying the response to the uplink data.
  • the repetition number threshold may be set as any predetermined value. Setting the repetition number threshold may be based on the available uplink resources of the network device 110 or other factors.
  • the number of repetitions associated with the terminal device 120 may be determined based on a coverage level of the terminal device 120, and the coverage level may include a normal coverage level, a robust coverage level, an extreme coverage level, or the like.
  • the network device 110 may delay the response to the uplink data to be transmitted for a terminal device with a specific coverage level (for example, the extreme coverage level).
  • the network device 110 may not delay the response to the downlink data, but perform the transmission using a separate downlink resource. If there is still downlink data to be transmitted to the terminal devices with that coverage level subsequently, the network device 110 may perform the transmission using other downlink resources.
  • the network device 110 may determine, based on the number of terminal devices at its service, a period of delay time for the response to the uplink data. If there is a great number of terminal devices served by the network device 110 (such as a great number of terminal devices having access to the network device 110), the downlink resource of the network device 110 may not be sufficient. In order to increase the resource utilization, upon predicting that the downlink data is to be transmitted to the terminal device 120, the network device 100 may determine the period of delay time in the case that there is a great number of terminal devices at its service (for example, being greater than the threshold number), so as to delay the response to the uplink data.
  • the terminal device 120 transmits the uplink data to the network device 110 at 405, and receives from the network device 110 at least part of downlink data and a response to the uplink data using the same downlink resource at 420. If not all downlink data are received in one downlink transmission due to the large size of the downlink data, the terminal device 120 may receive the remaining downlink data using other downlink resources.
  • FIG. 5 shows a flowchart of a communication process 500 of uplink resource scheduling at a network device side in accordance with some embodiments of the present disclosure. It would be appreciated that the process 500 may be implemented for example at the network device 110 as shown in Fig. 1. For sake of description, the process 500 will be described below with reference to Fig. 1.
  • the network device 110 transmits downlink data to the terminal device 120.
  • the network device 110 predicts, based on the traffic mode of the terminal device 120, whether a response to the downlink data is to be transmitted by the terminal device 120.
  • the network device 110 transmits a grant of an uplink resource to the terminal device 120 without waiting for an uplink resource scheduling request from the terminal device 120.
  • the network device 110 receives, from the terminal device 120, the response to the downlink data using the uplink resource.
  • the predicting may include: determining whether a traffic mode of the terminal device 120 is a network command (NC) traffic mode, and in response to determining that the traffic mode is a NC traffic mode, predicting that the response to the downlink data is to be transmitted by the terminal device 120.
  • NC network command
  • transmitting the grant of the uplink resource may include: determining whether a number of repetitions associated with a transmission related to the terminal device 120 is greater than a repetition number threshold; and in response to determining that the number of repetitions is greater than the repetition number threshold and predicting that the response is to be transmitted by the terminal device 120, transmitting the grant of the uplink resource to the terminal device 120.
  • transmitting the grant of the uplink resource may include: determining whether a number of terminal devices served by the network device is greater than a number threshold; and in response to determining that the number is greater than the number threshold and predicting that the response is to be transmitted by the terminal device 120, transmitting the grant of the uplink resource to the terminal device 120.
  • transmitting the grant of the uplink resource may include: transmitting the grant of the uplink resource to the terminal device 120 after a period of time since the transmitting of the downlink data.
  • the communication system may include a narrowband Intemet-of-Things (NB-IoT) communication system.
  • NB-IoT narrowband Intemet-of-Things
  • FIG. 6 shows a flow chart of a communication process 600 of downlink resource scheduling at a network device side in accordance with some embodiments of the present disclosure. It would be appreciated that the process 600 may be implemented for example at the network device 110 as shown in Fig. 1. For sake of description, the process 600 will be described below with reference to Fig. 1.
  • the network device 110 receives uplink data from the terminal device 120.
  • the network device 110 predicts, based on the traffic mode of the terminal device 12, whether downlink data is to be transmitted to the terminal device 1200.
  • the network device 110 determines a period of delay time for a response to the uplink data.
  • the network device 110 determines whether the period of delay time expires and whether the network device has the downlink data to be transmitted.
  • the network device 110 transmits to the terminal device 120 at least part of the downlink data and the response using a same downlink resource.
  • the predicting may include: determining whether a traffic mode of the terminal device 120 is a Mobile Autonomous Reporting (MAR) traffic mode; and in response to determining that the traffic mode is a MAR traffic mode, predicting that the downlink data is to be transmitted to the terminal device 120.
  • MAR Mobile Autonomous Reporting
  • determining the period of delay time may include: determining that the number of repetitions associated with the terminal device 120 is greater than the repetition number threshold; and in response to determining that the number is greater than the number threshold and predicting that the downlink data is to be transmitted to the terminal device 120, determining the period of delay time.
  • determining the period of delay time may include: determining whether a number of terminal devices served by the network device 110 is greater than a number threshold; and in response to determining that the number is greater than the number threshold and predicting that the downlink data is to be transmitted to the terminal device 120, determining the period of delay time.
  • the process 600 may further include, in response to the period of delay time expiring and in absence of the downlink data to be transmitted, transmitting the response to the terminal device 120 using the downlink resource.
  • the communication system may include a narrowband Intemet-of-Things (NB-IoT) communication system.
  • NB-IoT narrowband Intemet-of-Things
  • FIG. 7 shows a flowchart of a communication process 700 of uplink resource scheduling at a terminal device side in accordance with some embodiments of the present disclosure. It would be appreciated that the process 700 may be implemented for example at the terminal device 120 as shown in Fig. 1. For sake of description, the process 700 will be described with reference to Fig. 1.
  • the terminal device 120 receives downlink data from the network device 110.
  • the terminal device 120 receives from the network device 110 a grant of an uplink resource in absence of a transmission of an uplink resource scheduling request to the network device 110, the grant of the uplink resource being transmitted by the network device in response to predicting, based on a traffic mode of the terminal device 120, that a response to the downlink data is to be transmitted by the terminal device 120.
  • the terminal device 120 transmits to the network device 110 the response to the downlink data using the uplink resource.
  • the traffic mode of the terminal device may be a network command (NC) traffic mode.
  • NC network command
  • the grant of the uplink resource may be based on at least one of: a number of repetitions associated with a transmission related to the terminal device being greater than a repetition number threshold, and a number of terminal devices served by the network device being greater than a number threshold.
  • receiving the grant of the uplink resource may include receiving, from the network device, the grant of the uplink resource after a predetermined period of time since the receiving of the downlink data.
  • the communication system may include a narrowband Intemet-of-Things (NB-IoT) communication system.
  • NB-IoT narrowband Intemet-of-Things
  • Fig. 8 is a flowchart of a communication process 800 of downlink resource scheduling at a terminal device side in accordance with some embodiments of the present disclosure. It would be appreciated that the process 800 may be implemented for example at the terminal device 120 as shown in Fig. 1. For sake of description, the process 800 will be described below with reference to Fig. 1.
  • the terminal device 120 transmits uplink data to the network device 110.
  • the terminal device 120 receives at least part of downlink data and a response to the uplink data from the network device 110 using a same downlink resource, the response being delayed by the network device 110 for the period of time based on a traffic mode of the terminal device.
  • the traffic mode of the terminal device may be a Mobile Autonomous Report (MAR) traffic mode.
  • MAR Mobile Autonomous Report
  • the response may be delayed by the network device 110 for the period of time further based on at least one of: a number of repetitions associated with a transmission related to the terminal device being greater than a repetition number threshold, and a number of terminal devices served by the network device 110 being greater that a number threshold.
  • the communication system may include a narrowband Intemet-of-Things (NB-IoT) communication system.
  • NB-IoT narrowband Intemet-of-Things
  • Fig. 9 is a simplified block diagram of a device 900 that is suitable for implementing embodiments of the present disclosure.
  • the device 700 may be provided to implement the communication device, for example the network device 110 or the terminal device 120 as shown in Fig. 1.
  • the device 900 includes one or more processors 910, one or more memories 940 coupled to the processor 910, and one or more transmitters and/or receivers (TX/RX) 940 coupled to the processor 910.
  • TX/RX transmitters and/or receivers
  • the TX/RX 940 is for bidirectional communications.
  • the TX/RX 940 has at least one antenna to facilitate communication.
  • the communication interface may represent any interface that is necessary for communication with other network elements.
  • the processor 910 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 900 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • the memory 920 may include one or more non-volatile memories and one or more volatile memories.
  • the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 924, an electrically programmable read only memory (EPROM), a flash memory, a hard disk, a compact disc (CD), a digital video disk (DVD), and other magnetic storage and/or optical storage.
  • ROM Read Only Memory
  • EPROM electrically programmable read only memory
  • flash memory a hard disk
  • CD compact disc
  • DVD digital video disk
  • the volatile memories include, but are not limited to, a random access memory (RAM) 922 and other volatile memories that will not last in the power-down duration.
  • RAM random access memory
  • a computer program 930 includes computer executable instructions that are executed by the associated processor 910.
  • the program 930 may be stored in the ROM 924.
  • the processor 910 may perform any suitable actions and processing by loading the program 930 into the RAM 922.
  • the embodiments of the present disclosure may be implemented by means of the program 930 so that the device 900 may perform any process of the disclosure as discussed with reference to Figs. 3 to 8.
  • the embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
  • the program 930 may be tangibly contained in a computer readable medium which may be included in the device 900 (such as in the memory 920) or other storage devices that are accessible by the device 900.
  • the device 900 may load the program 930 from the computer readable medium to the RAM 922 for execution.
  • the computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.
  • Fig. 10 shows an example of the computer readable medium 1000 in form of CD or DVD.
  • the computer readable medium has the program 930 stored thereon.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. For example, in some embodiments, various examples of the present disclosure (e.g., a method, apparatus or device) may be partly or fully implemented on the computer readable medium.
  • the units included in the apparatuses and/or devices of the present disclosure may be implemented in various manners, including software, hardware, firmware, or any combination thereof.
  • one or more units may be implemented using software and/or firmware, for example, machine-executable instructions stored on the storage medium.
  • parts or all of the units in the apparatuses and/or devices may be implemented, at least in part, by one or more hardware logic components.
  • illustrative types of hardware logic components include Field-programmable Gate Arrays (FPGAs), Application-specific Integrated Circuits (ASICs), Application-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
  • FPGAs Field-programmable Gate Arrays
  • ASICs Application-specific Integrated Circuits
  • ASSPs Application-specific Standard Products
  • SOCs System-on-a-chip systems
  • CPLDs Complex Programmable Logic Devices
  • embodiments of the present disclosure may be described in the context of the computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • a computer readable medium may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the computer readable medium may be a machine readable signal medium or a machine readable storage medium.
  • the computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • machine readable storage medium More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM portable compact disc read-only memory
  • magnetic storage device or any suitable combination of the foregoing.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne, selon des modes de réalisation, des procédés et des dispositifs de planification de ressource dans un système de communication. Dans une solution de planification de ressource de liaison montante, un procédé exécuté au niveau d'un dispositif réseau d'un système de communication comprend la transmission de données de liaison descendante à un dispositif terminal. Le procédé consiste également à prédire, en fonction d'un mode de trafic du dispositif terminal, si une réponse aux données de liaison descendante doit être transmise ou non par le dispositif terminal, et en réponse à la prédiction du fait que la réponse aux données de liaison descendante doit être transmise par le dispositif terminal, à transmettre une autorisation d'une ressource de liaison montante sans attendre une requête de planification de ressource de liaison montante provenant du dispositif terminal. Le procédé consiste en outre à recevoir, en provenance du dispositif terminal, la réponse aux données de liaison descendante à l'aide de la ressource de liaison montante.
PCT/EP2018/082750 2017-12-13 2018-11-28 Procédés et dispositifs de planification de ressource dans un système de communication WO2019115225A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711331017.5A CN109922532B (zh) 2017-12-13 2017-12-13 用于通信系统中的资源调度的方法和设备
CN201711331017.5 2017-12-13

Publications (2)

Publication Number Publication Date
WO2019115225A2 true WO2019115225A2 (fr) 2019-06-20
WO2019115225A3 WO2019115225A3 (fr) 2019-07-25

Family

ID=64556903

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2018/082750 WO2019115225A2 (fr) 2017-12-13 2018-11-28 Procédés et dispositifs de planification de ressource dans un système de communication

Country Status (2)

Country Link
CN (1) CN109922532B (fr)
WO (1) WO2019115225A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114995985A (zh) * 2022-08-02 2022-09-02 阿里巴巴（中国）有限公司 资源调度方法、设备和存储介质

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6845235B1 (en) * 2003-07-18 2005-01-18 Motorola, Inc. Method and apparatus in a wireless communication system for expediting a request for uplink resources
FI20031200A0 (fi) * 2003-08-26 2003-08-26 Nokia Corp Menetelmä ja tukiasema siirtoyhteyden sovituksen ja pakettiajoituksen ohjaamiseksi HSDPA-radiojärjestelmässä
HUE045919T2 (hu) * 2007-03-19 2020-01-28 Optis Wireless Technology Llc Rádiós hordozó specifikus CQI jelentés
CN101499887B (zh) * 2008-01-28 2012-04-04 电信科学技术研究院 半静态资源调度方法及系统、重传选择调度方法及系统
US10194457B2 (en) * 2013-12-17 2019-01-29 Telefonaktiebolaget Lm Ericsson (Publ) Method and device for proactive allocation of uplink resources
CN106068662B (zh) * 2014-01-30 2020-01-14 诺基亚技术有限公司 用于设备至设备发现信号传输的负载控制系统
WO2016029933A1 (fr) * 2014-08-26 2016-03-03 Telefonaktiebolaget L M Ericsson (Publ) Alignement d'attributions de liaison montante périodiques dans un réseau cellulaire
WO2016150479A1 (fr) * 2015-03-23 2016-09-29 Telefonaktiebolaget Lm Ericsson (Publ) Utilisation sélective de transmissions programmées et non programmées pour le déchargement d'un réseau cellulaire
US20170208619A1 (en) * 2016-01-14 2017-07-20 Qualcomm Incorporated Scheduling request during connected discontinuous reception off period
WO2017192082A1 (fr) * 2016-05-02 2017-11-09 Telefonaktiebolaget Lm Ericsson (Publ) Procédé permettant d'utiliser efficacement des ressources autorisées dans un système de communication sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114995985A (zh) * 2022-08-02 2022-09-02 阿里巴巴（中国）有限公司 资源调度方法、设备和存储介质
CN114995985B (zh) * 2022-08-02 2023-01-17 阿里巴巴（中国）有限公司 资源调度方法、设备和存储介质

Also Published As

Publication number Publication date
CN109922532A (zh) 2019-06-21
CN109922532B (zh) 2022-04-22
WO2019115225A3 (fr) 2019-07-25

Similar Documents

Publication Publication Date Title
CN113812184B (zh) 非连续接收中的唤醒信令处理
US11785489B2 (en) Apparatus, method and computer program for self-organizing network measurement reporting
US20240015735A1 (en) Application layer preemptive scheduling requests for ultra-low latency
WO2020227939A1 (fr) Économies d'énergie
US20240196358A1 (en) Positioning enhancement mechanism
US20220150925A1 (en) Resource Configuration for NB-IOT
US20240031091A1 (en) Positioning method, network side device and non-transitory readable storage medium
JP7449992B2 (ja) 方法、装置、及びコンピュータプログラム
WO2019115225A2 (fr) Procédés et dispositifs de planification de ressource dans un système de communication
CN109729586B (zh) 基于窗口的调度方法、设备和计算机可读介质
US20220191788A1 (en) Permissible transmission gap assistance by ue
EP2989845B1 (fr) Procédés et appareil permettant une planification des communications
CN115039481A (zh) 处于非活动模式的设备的波束管理
CN115176491A (zh) 交叉链路干扰的自适应测量
WO2024098229A1 (fr) Déclenchement d'informations de faisceau pour activation de cellule
WO2024168718A1 (fr) Procédés et appareils de radiomessagerie
WO2024212064A1 (fr) Rapport de csi pour activation de cellule
CN114631390B (zh) 无争用随机接入中的动态活动时间触发
CN114258709B (zh) 监测控制信道
WO2024164260A1 (fr) Dispositifs, procédés et appareils de transmission de petites données
WO2023000279A1 (fr) Rétroaction d'accusé de réception pour un positionnement dans un état inactif de commande de ressource radio
WO2021134502A1 (fr) Procédés, dispositifs et support pour la communication
CN115918233A (zh) 由数据传输触发的波束报告
CN117730570A (zh) 针对小数据传输过程的授权跳过
JP2024529871A (ja) 端末装置、ネットワーク装置、及び方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18811230

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18811230

Country of ref document: EP

Kind code of ref document: A2