WO2018045494A1 - 用于窄带物联网系统资源分配的方法、终端和服务器 - Google Patents

用于窄带物联网系统资源分配的方法、终端和服务器 Download PDF

Info

Publication number
WO2018045494A1
WO2018045494A1 PCT/CN2016/098249 CN2016098249W WO2018045494A1 WO 2018045494 A1 WO2018045494 A1 WO 2018045494A1 CN 2016098249 W CN2016098249 W CN 2016098249W WO 2018045494 A1 WO2018045494 A1 WO 2018045494A1
Authority
WO
WIPO (PCT)
Prior art keywords
carrier
terminal
downlink
transmit power
bearer
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2016/098249
Other languages
English (en)
French (fr)
Inventor
黄晓庆
江海涛
王振凯
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Cloudminds Shenzhen Robotics Systems Co Ltd
Original Assignee
Cloudminds Shenzhen Robotics Systems Co Ltd
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 Cloudminds Shenzhen Robotics Systems Co Ltd filed Critical Cloudminds Shenzhen Robotics Systems Co Ltd
Priority to PCT/CN2016/098249 priority Critical patent/WO2018045494A1/zh
Priority to CN201680004908.7A priority patent/CN107223354B/zh
Priority to US16/347,095 priority patent/US10652916B2/en
Publication of WO2018045494A1 publication Critical patent/WO2018045494A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • 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/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/26—TPC being performed according to specific parameters using transmission rate or quality of service QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/06—TPC algorithms
    • H04W52/14—Separate analysis of uplink or downlink
    • H04W52/143—Downlink power control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/20—Negotiating bandwidth
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/22—Negotiating communication rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/26—TPC being performed according to specific parameters using transmission rate or quality of service QoS [Quality of Service]
    • H04W52/265—TPC being performed according to specific parameters using transmission rate or quality of service QoS [Quality of Service] taking into account the quality of service QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • 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/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • 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/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/26—TPC being performed according to specific parameters using transmission rate or quality of service QoS [Quality of Service]
    • H04W52/262—TPC being performed according to specific parameters using transmission rate or quality of service QoS [Quality of Service] taking into account adaptive modulation and coding [AMC] scheme

Definitions

  • the present disclosure relates to the field of narrowband Internet of Things, and in particular to a method, terminal and server for resource allocation of a narrowband Internet of Things system.
  • Narrow Band Internet of Things is an important technical means for operators and communication equipment providers to enter the emerging Internet of Things, such as car networking, smart healthcare, smart home, and robotics.
  • NB-IoT Narrow Band Internet of Things
  • the present disclosure provides a method, terminal, and server for narrowband IoT system resource allocation that is capable of meeting both service rate and communication quality requirements.
  • a method for resource allocation of a narrowband Internet of Things system comprising:
  • Obtaining a service request of the first terminal where the service request includes: (1) a downlink service rate requirement; (2) receiving strength information, where the received strength information includes a receiving strength of a primary synchronization signal of the serving base station of the first terminal, One or more of a reception strength of the secondary synchronization signal and a reception strength of the reference signal; (3) reception quality information including a reception quality of the primary synchronization signal of the serving base station and a reception quality of the secondary synchronization signal And one or more of the reception qualities of the reference signal; and (4) the service priority identification information;
  • determining, on the i-th bearer carrier, the downlink data of the first terminal is transmitted by using the determined target downlink transmit power.
  • a terminal for resource allocation of a narrowband Internet of Things system comprising:
  • a sending module configured to send a service request, where the service request includes: (1) a downlink service rate requirement; (2) receiving strength information, where the received strength information includes a receiving strength of a primary synchronization signal of the serving base station of the first terminal And one or more of a reception strength of the secondary synchronization signal and a reception strength of the reference signal; (3) reception quality information including reception quality of the primary synchronization signal of the serving base station and reception of the secondary synchronization signal One or more of quality and reception quality of the reference signal; and (4) business priority identification information;
  • a receiving module configured to receive a service response to the service request.
  • a server for narrowband IoT system resource allocation comprising:
  • a service request obtaining module configured to obtain a service request of the first terminal, where the service request includes: (1) a downlink service rate requirement; (2) receiving strength information, where the received strength information includes a serving base station of the first terminal One or more of a reception strength of a primary synchronization signal, a reception strength of a secondary synchronization signal, and a reception strength of a reference signal; (3) reception quality information including reception quality of a primary synchronization signal of the serving base station And one or more of a reception quality of the secondary synchronization signal and a reception quality of the reference signal; and (4) service priority identification information;
  • a bearer carrier determining module configured to determine, according to the candidate carrier information and the downlink service rate requirement, a bearer carrier and a number of bearer carriers N required to carry the downlink data of the first terminal, where N ⁇ 1;
  • a downlink transmit power determining module configured to determine a target downlink transmit power of each bearer carrier according to the received quality information, the determined bearer carrier, the determined number of bearer carriers, and the received strength information;
  • a processing module configured to determine, when the total downlink transmit power of the i-th carrier carrier is less than or equal to a first preset threshold, to transmit the downlink of the first terminal by using the determined target downlink transmit power on the i-th carrier carrier data.
  • the bearer carrier required to carry the downlink data of the first terminal is determined according to the candidate carrier information and the downlink service rate requirement.
  • the number of carriers is N, so this can meet the requirements of the downlink traffic rate, and then after determining the target downlink transmit power of each bearer carrier, the total downlink transmit power of the i-th bearer carrier is less than or equal to the first preset threshold. Transmitting the downlink data of the first terminal by using the determined target downlink transmit power on the i-th carrier carrier, which can meet the requirements of service coverage and communication quality, so the embodiment of the present disclosure can simultaneously ensure the service rate and the communication quality. Requirements.
  • FIG. 1 is a flow chart of a method for narrowband IoT system resource allocation, in accordance with an embodiment of the present disclosure
  • FIG. 2 is a flow chart of a method for narrowband IoT system resource allocation, in accordance with yet another embodiment of the present disclosure
  • FIG. 3 is a flowchart of a method for narrowband IoT system resource allocation, in accordance with yet another embodiment of the present disclosure
  • FIG. 4 is a flow chart of a method for narrowband IoT system resource allocation, in accordance with yet another embodiment of the present disclosure
  • FIG. 5 is a schematic block diagram of a terminal for narrowband IoT system resource allocation, in accordance with an embodiment of the present disclosure
  • FIG. 6 is a schematic block diagram of a server for narrowband IoT system resource allocation, in accordance with an embodiment of the present disclosure
  • FIG. 7 is a schematic block diagram of a server for narrowband IoT system resource allocation, according to yet another embodiment of the present disclosure.
  • FIG. 8 is a schematic block diagram of a server for narrowband IoT system resource allocation, in accordance with yet another embodiment of the present disclosure.
  • a narrowband Internet of Things typically consists of a terminal and a serving base station.
  • the emerging Internet of Things such as the Internet of Vehicles, smart healthcare, and smart home
  • the complex intelligent processing and computing functions are placed on the cloud robot server and distributed to the terminal to be controlled according to the requirements.
  • the inventor of the present disclosure has proposed a resource allocation for a narrowband Internet of Things system according to an embodiment of the present disclosure based on such a demand. Method, terminal and server.
  • Embodiments of the present disclosure provide a method for resource allocation of a narrowband Internet of Things system. As shown in FIG. 1, the method may include the following steps S1 to S4.
  • step S1 the service request of the first terminal is obtained, where the service request includes: (1) a downlink service rate requirement; (2) reception strength information, where the reception strength information includes a primary synchronization of the serving base station of the first terminal. One or more of a received strength of the signal, a received strength of the secondary synchronization signal, and a received strength of the reference signal; (3) reception quality information including a reception quality of the primary synchronization signal of the serving base station, and a secondary One or more of a reception quality of the synchronization signal and a reception quality of the reference signal; and (4) service priority identification information.
  • the first terminal may first send its service request to the serving base station of the narrowband Internet of Things, and then the serving base station reports the service request to the cloud bot server through dedicated control signaling or NAS signaling.
  • the serving base station may adopt a specific A sequence (eg, 000111000) and transmit power are known to report the service request of the first terminal.
  • the cloud robot server obtains the service request of the first terminal.
  • the known sequence 000111000 herein is merely an example, and the known sequence is also different depending on the actual service request.
  • step S2 the bearer carrier and the number of bearer carriers N required to carry the downlink data of the first terminal are determined according to the candidate carrier information and the downlink traffic rate requirement, where N ⁇ 1.
  • the candidate carrier may refer to all carriers of the serving base station that provide bearer services for the terminal.
  • the candidate carrier information may include a maximum carrier-supportable downlink transmission rate of each candidate carrier and current load information of each candidate carrier.
  • the downlink of the NB-IoT is transmitted in a 15 kHz bandwidth, and the downlink rate is about 250 kbps.
  • the single carrier bearer of each candidate carrier can support a downlink transmission rate of 250 kbps.
  • the downlink service rate requirement included in the service request of the first terminal is 500 kbps, and there are four candidate carriers in total, that is, candidate carriers 1, 2, 3, and 4, and the single carrier of the four candidate carriers
  • the maximum supported downlink transmission rate is 250 kbps, and the current loads of candidate carriers 1, 2, 3, and 4 are 50%, 10%, 20%, and 80%, respectively, which is equivalent to the highest downlink service rate currently available at 125 kbps.
  • 225 kbps, 200 kbps, and 50 kbps so that the number of bearer carriers required to carry the downlink data of the first terminal is 3, and the specific bearer carriers are candidate carriers 1, 2, and 3.
  • the number of bearer carriers is 4 and specific. It is also feasible that the carrier carriers are candidate carriers 1, 2, 3 and 4.
  • the number of the determined carrier carriers N is the minimum number of carrier carriers in the number of carrier carriers that can meet the downlink traffic rate requirement, and the example above is used as an example.
  • the determined number of bearer carriers N is 3 instead of 4 because, in the case of the same downlink traffic rate requirement, the lower the number of bearer carriers, the lower the power consumption and processing complexity of the first terminal.
  • step S3 determining a target downlink transmit power of each bearer carrier according to the received quality information, the determined bearer carrier, the determined number of bearer carriers, and the received strength information;
  • step S4 when the total downlink transmit power P sum-TX-i of the i-th carrier carrier is less than or equal to the first preset threshold, it is determined that the determined target downlink transmit power is transmitted on the i-th carrier carrier.
  • the downlink data of the first terminal is described.
  • the total downlink transmission power P sum-TX-i of the i-th carrier carrier refers to the sum of downlink transmission powers of all terminals (including the first terminal) currently carried on the i-th carrier.
  • the first preset threshold may be set to the single carrier rated transmit power of the serving base station. Of course, it is also feasible that the first preset threshold is lower than the single carrier rated transmit power of the serving base station.
  • a service request acceptance message may also be sent so that the first terminal knows that its service request is accepted.
  • the cloud bot server may send a service request admission message to the serving base station, and then the service base station forwards the service request admission message to the first terminal.
  • the method according to the embodiment of the present disclosure first determines, according to the candidate carrier information and the downlink service rate requirement, the downlink data required to carry the first terminal. Carrying the carrier and the number of carrier carriers N, so this can meet the requirements of the downlink traffic rate, and then after determining the target downlink transmit power of each bearer carrier, the total downlink transmit power P sum-TX-i of the i-th carrier carrier is smaller than And determining, by the first preset threshold, that the coverage of the downlink service of the first terminal is not limited, determining, on the i-th carrier carrier, the downlink data of the first terminal by using the determined target downlink transmit power, This can meet the requirements of service coverage and communication quality, so it can simultaneously guarantee the requirements of service rate and communication quality.
  • step S3 according to the received quality information, the determined carrier carrier, the determined number of bearer carriers, and the received strength information Determining the target downlink transmit power of each bearer carrier may include the following steps S31 to S33.
  • each of the bearer carriers is determined according to the determined bearer carrier (for example, the load condition of each bearer carrier), the determined number of bearer carriers, and the determined modulation and coding mode (for example, the highest modulation coding mode). The number and location of resource blocks on.
  • step S33 the target downlink transmit power of each of the bearer carriers is determined according to the received strength information, the determined modulation and coding scheme, and the determined number of resource blocks.
  • the target downlink transmission power of each of the carrier carriers can be effectively determined.
  • step S33 may include the following steps S331 to S333.
  • step S331 according to the transmit power information in the serving base station and the service request
  • the received strength information is used to determine a maximum coupling loss between the serving base station and the first terminal, wherein the transmit power information includes a transmit power of a primary synchronization signal of the serving base station, a transmit power of a secondary synchronization signal, and One or more of the transmit power of the reference signal.
  • the reception strength information included in the service request of the first terminal is the reception strength of the primary synchronization signal of the serving base station, that is, the reception strength (ie, the power value) of the primary synchronization signal of the first base station to the serving base station, and then the cloud
  • the bot server may first acquire the transmit power of the primary synchronization signal of the serving base station from the serving base station, and then subtract the received strength of the primary synchronization signal included in the service request of the first terminal from the transmit power of the primary synchronization signal acquired by the serving base station.
  • a maximum coupling loss between the serving base station and the first terminal is obtained, wherein the maximum coupling loss comprises a transmit antenna gain of the serving base station.
  • the cloud bot server may first acquire the transmit power of the secondary synchronization signal of the serving base station from the serving base station, and then subtract the received synchronization strength of the secondary synchronization signal included in the service request of the first terminal from the secondary synchronization signal transmission power acquired by the serving base station, The maximum coupling loss between the serving base station and the first terminal is obtained, wherein the maximum coupling loss includes a transmit antenna gain of the serving base station.
  • the cloud robot server may first acquires a reference signal transmit power of the serving base station P T-RS from a serving base station, transmission power of the reference signal from the serving base station is then obtained by subtracting the first P T-RS terminal service request of the first terminal pair comprising The received strength P R-RS of the reference signal of the serving base station is used to obtain a maximum coupling loss between the serving base station and the first terminal, wherein the maximum coupling loss includes the transmit antenna gain of the serving base station.
  • step S332 according to the determined modulation coding mode and the determined number of resource blocks. A minimum received power requirement for a resource block on each of the bearer carriers is determined.
  • the minimum received power requirement P RX-MIN-i can be determined by the following formula:
  • the SINR MIN-i is the demodulation signal-to-noise ratio required for the modulation coding mode corresponding to the resource block on the carrier i
  • the N i is the thermal noise power of the resource block on the carrier i
  • the I i is the bearer carrier i.
  • step S333 a target downlink transmit power of each of the bearer carriers is determined according to the maximum coupling loss and the minimum received power requirement.
  • the target downlink transmit power P TX-i can be obtained by the following formula:
  • the method may further include the following steps S5 and S6.
  • step S5 it is determined whether the current total downlink transmit power of the serving base station of the first terminal is less than or equal to a second preset threshold.
  • the current total downlink transmit power of the serving base station of the first terminal refers to the total downlink transmit power of all carriers supported by the serving base station at the current scheduling moment, that is, the target downlink transmit power and coverage of the restricted restricted terminal are unrestricted.
  • the cloud bot server can obtain the sum of the current downlink transmit power from the power controller of the serving base station. For example, the cloud bot server can send the total power request information to the serving base station, and then the serving base station feeds back the information of the sum of the current downlink transmit powers. Give the cloud robot server.
  • the second preset threshold may be set as the serving base station on all carriers supported by the serving base station The maximum total transmit power that can be supported. Of course, it is also feasible that the second preset threshold is lower than the maximum supported transmit power.
  • the cloud robot service can obtain the total supported transmit power maximum from the power controller of the serving base station. For example, the cloud robot server can send the total power request information to the serving base station, and then the serving base station will support the total transmit power. The maximum information is fed back to the cloud robot server.
  • step S6 when the current total downlink transmit power of the serving base station of the first terminal is less than or equal to a second preset threshold, this indicates that the available downlink transmit power of the bearer carrier i of the first terminal can be boosted, so
  • the i-th carrier carrier can transmit the downlink data of the first terminal with the determined target downlink transmit power P TX-i , which satisfies the downlink service coverage requirement of the first terminal.
  • the method may further include the following steps S7 and S8.
  • step S7 it is determined whether there is a terminal whose service priority is lower than the service priority of the first terminal among the terminals served by the serving base station.
  • the cloud bot server may first obtain the service type or service priority of all terminals served by the serving base station at the current scheduling moment from the serving base station, and then determine whether the service type or service priority is lower than the first A terminal of a service type or service priority of a terminal.
  • step S8 when there is a terminal whose service type or service priority is lower than the service type or service priority of the first terminal, it is determined to increase the available downlink transmit power of the i-th carrier carrier, so that the i-th bearer
  • the downlink data of the first terminal is transmitted on the carrier with the determined target downlink transmit power P TX-i .
  • the i-th carrier carrier can transmit the downlink data of the first terminal with the determined target downlink transmit power P TX-i , which satisfies the downlink service coverage requirement of the first terminal.
  • the cloud bot server may determine that the downlink transmission power of the terminal with the lower the service type or the service priority is lower, or the downlink data of the terminal with the lower the service type or the service priority is not scheduled at the current scheduling time, and The downlink transmit power of the i-th carrier carrier of the first terminal is upgraded to the determined target downlink transmit power P TX-i , and a service request admission message is sent.
  • the cloud bot server may forward the service request to the first terminal by using the serving base station.
  • the message may also send a service request acceptance message directly to the first terminal.
  • step S7 it is determined in step S7 that there is no terminal in the terminal served by the serving base station that has a service priority lower than the service priority of the first terminal.
  • the method can also include:
  • a service request rejection message is transmitted.
  • the cloud robot server may forward the service request rejection message to the first terminal through the serving base station, or may directly send the service request rejection message to the first terminal.
  • the serving base station in the case where the power of the i-th carrier carrier is limited, can be configured according to the current total downlink transmission power of the serving base station, the service type of all terminals, or the service priority level.
  • the downlink transmit power of the served terminal is dynamically allocated to preferentially ensure downlink data transmission of the terminal with limited coverage but high service priority, thereby effectively ensuring the service quality and rate.
  • the embodiment of the present disclosure further provides a terminal for resource allocation of a narrowband Internet of Things system.
  • the terminal may include:
  • the sending module 501 is configured to send a service request, where the service request includes: (1) a downlink service rate requirement; and (2) received strength information, where the received strength information includes a primary synchronization signal of the serving base station of the first terminal.
  • the service request includes: (1) a downlink service rate requirement; and (2) received strength information, where the received strength information includes a primary synchronization signal of the serving base station of the first terminal.
  • One or more of intensity, reception strength of the secondary synchronization signal, and reception strength of the reference signal (3) reception quality information including reception quality of the primary synchronization signal of the serving base station, and secondary synchronization signal Receiving one or more of quality and reception quality of the reference signal; and (4) service priority identification information;
  • the receiving module 502 is configured to receive a service response to the service request.
  • service response For example, business response It can indicate whether the business request is accepted or rejected.
  • the embodiment of the present disclosure further provides a server for resource allocation of a narrowband Internet of Things system.
  • the server may include a service request obtaining module 10, a bearer carrier determining module 20, a downlink transmit power determining module 30, and a processing module. 40. These modules are described in detail below.
  • the service request obtaining module 10 is configured to obtain a service request of the first terminal, where the service request includes: (1) a downlink service rate requirement; (2) receiving strength information, where the received strength information includes the serving base station of the first terminal One or more of a reception strength of a primary synchronization signal, a reception strength of a secondary synchronization signal, and a reception strength of a reference signal; (3) reception quality information including reception of a primary synchronization signal of the serving base station One or more of quality, reception quality of the secondary synchronization signal, and reception quality of the reference signal; and (4) service priority identification information.
  • the bearer carrier determining module 20 is configured to determine, according to the candidate carrier information and the downlink service rate requirement, a bearer carrier and a number of bearer carriers N required to carry downlink data of the first terminal, where N ⁇ 1.
  • the candidate carrier information may include a maximum carrier-supportable downlink transmission rate of each candidate carrier and current load information of each candidate carrier.
  • the downlink transmit power determining module 30 is configured to determine, according to the received quality information, the determined bearer carrier, the determined number of bearer carriers, and the received strength information, a target downlink transmit power of each bearer carrier;
  • the processing module 40 is configured to: when the total downlink transmit power of the i-th carrier carrier is less than or equal to a first preset threshold, determine, to transmit, by using the determined target downlink transmit power, the first terminal on the i-th carrier carrier Downstream data.
  • the downlink transmit power determining module 30 may include:
  • a modulation and coding mode determining submodule 301 configured to determine, according to the received quality information, a modulation and coding mode allowed by downlink data of the first terminal;
  • the resource block determining sub-module 302 is configured to determine, according to the determined bearer carrier, the determined number of bearer carriers, and the determined modulation and coding manner, the number and location of resource blocks on each of the bearer carriers.
  • the downlink transmit power determining submodule 303 is configured to determine a target downlink transmit power of each of the bearer carriers according to the received strength information, the determined modulation and coding mode, and the determined number of resource blocks.
  • the downlink transmit power determining submodule 303 may include:
  • a maximum coupling loss determining sub-unit 3031 configured to determine a maximum coupling loss between the serving base station and the first terminal according to the transmit power information in the serving base station and the received strength information in the service request, where
  • the transmit power information includes one or more of a transmit power of a primary synchronization signal, a transmit power of a secondary synchronization signal, and a transmit power of a reference signal of the serving base station;
  • a minimum received power requirement determining subunit 3032 configured to determine a minimum received power requirement of a resource block on each of the bearer carriers according to the determined modulation and coding mode and the determined number of resource blocks;
  • the downlink transmit power determining subunit 3033 is configured to determine a target downlink transmit power of each of the bearer carriers according to the maximum coupling loss and the minimum received power requirement.
  • the processing module 40 is further configured to: the total downlink transmit power of the i-th carrier carrier is greater than the first preset threshold, and the serving base station of the first terminal When the current total downlink transmit power is less than or equal to the second preset threshold, determining to increase the available downlink transmit power of the ith bearer carrier, so as to transmit the first target transmit power on the i-th bearer carrier Downlink data of the terminal.
  • the processing module 40 is further configured to: the total downlink transmission power of the i-th carrier carrier is greater than the first preset threshold, the serving base station It is determined that the ith carrier carrier is increased when the current total downlink transmission power is greater than the second preset threshold and the terminal served by the serving base station has a service priority lower than the service priority of the first terminal.
  • the available downlink transmit power is used to transmit the downlink data of the first terminal on the i-th bearer carrier with the determined target downlink transmit power.
  • the processing module 40 may be further configured to determine downlink transmission power of the terminal whose service priority is lower than the service priority of the first terminal, or determine downlink data of the terminal at the current scheduling time. No scheduling is done.
  • the processing module 40 is further configured to: the total downlink transmission power of the i-th carrier carrier is greater than the first preset threshold, and the current total downlink of the serving base station And sending a service request rejection message when the transmission power is greater than the second preset threshold and the terminal served by the serving base station does not have a service priority lower than the service priority of the first terminal.
  • the server according to an embodiment of the present disclosure may be a cloud robot server. Specific implementations of the operations performed by the various modules in the server according to the embodiments of the present disclosure have been described in detail in the method according to the embodiments of the present disclosure, and are not described herein again.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例属于窄带物联网领域，涉及一种用于窄带物联网系统资源分配的方法、终端和服务器，能够同时满足业务速率和通信质量的要求。该方法包括：获取第一终端的业务请求；依据候选载波信息和下行业务速率要求确定承载第一终端的下行数据所需的承载载波及承载载波数目；依据接收质量信息、所确定的承载载波、所确定的承载载波数目、接收强度信息确定各个承载载波的目标下行发射功率；以及在第i个承载载波的总下行发射功率小于等于第一预设阈值时，确定在第i个承载载波上以所确定的目标下行发射功率传输所述第一终端的下行数据。

Description

用于窄带物联网系统资源分配的方法、终端和服务器 技术领域
本公开涉及窄带物联网领域，具体地，涉及一种用于窄带物联网系统资源分配的方法、终端和服务器。
背景技术
窄带物联网(Narrow Band Internet of Things，NB-IoT)是运营商和通信设备商进入车联网、智慧医疗、智能家居、机器人等新兴物联网领域的重要技术手段。然而，目前还没有一种有效的技术能够同时满足业务速率和通信质量的要求。
发明内容
本公开提供一种用于窄带物联网系统资源分配的方法、终端和服务器，其能够同时满足业务速率和通信质量的要求。
根据本公开实施例的一个方面，提供一种用于窄带物联网系统资源分配的方法，该方法包括：
获取第一终端的业务请求，所述业务请求包括：(1)下行业务速率要求；(2)接收强度信息，该接收强度信息包括所述第一终端的服务基站的主同步信号的接收强度、辅同步信号的接收强度和参考信号的接收强度中的一者或多者；(3)接收质量信息，该接收质量信息包括所述服务基站的主同步信号的接收质量、辅同步信号的接收质量和参考信号的接收质量中的一者或多者；以及(4)业务优先级标识信息；
依据候选载波信息和所述下行业务速率要求来确定承载所述第一终端的下行数据所需的承载载波及承载载波数目N，其中，N≥1；
依据所述接收质量信息、所确定的承载载波、所确定的承载载波数目和所述接收强度信息来确定各个承载载波的目标下行发射功率；以及
在第i个承载载波的总下行发射功率小于等于第一预设阈值时，确定在第i个承载载波上以所确定的目标下行发射功率来传输所述第一终端的下行数据。
根据本公开实施例的又一方面，提供一种用于窄带物联网系统资源分配的终端，该终端包括：
发送模块，用于发送业务请求，所述业务请求包括：(1)下行业务速率要求；(2)接收强度信息，该接收强度信息包括所述第一终端的服务基站的主同步信号的接收强度、辅同步信号的接收强度和参考信号的接收强度中的一者或多者；(3)接收质量信息，该接收质量信息包括所述服务基站的主同步信号的接收质量、辅同步信号的接收质量和参考信号的接收质量中的一者或多者；以及(4)业务优先级标识信息；以及
接收模块，用于接收对所述业务请求的业务响应。
根据本公开实施例的又一方面，提供一种用于窄带物联网系统资源分配的服务器，该服务器包括：
业务请求获取模块，用于获取第一终端的业务请求，所述业务请求包括：(1)下行业务速率要求；(2)接收强度信息，该接收强度信息包括所述第一终端的服务基站的主同步信号的接收强度、辅同步信号的接收强度和参考信号的接收强度中的一者或多者；(3)接收质量信息，该接收质量信息包括所述服务基站的主同步信号的接收质量、辅同步信号的接收质量和参考信号的接收质量中的一者或多者；以及(4)业务优先级标识信息；
承载载波确定模块，用于依据候选载波信息和所述下行业务速率要求来确定承载所述第一终端的下行数据所需的承载载波及承载载波数目N，其中，N≥1；
下行发射功率确定模块，用于依据所述接收质量信息、所确定的承载载波、所确定的承载载波数目、所述接收强度信息来确定各个承载载波的目标下行发射功率；以及
处理模块，用于在第i个承载载波的总下行发射功率小于等于第一预设阈值时，确定在第i个承载载波上以所确定的目标下行发射功率来传输所述第一终端的下行数据。
通过采用上述技术方案，由于本公开实施例在获取到第一终端的业务请求之后，首先依据候选载波信息和所述下行业务速率要求确定承载所述第一终端的下行数据所需的承载载波及承载载波数目N，因此这能够满足下行业务速率的要求，然后在确定了各个承载载波的目标下行发射功率之后，在第i个承载载波的总下行发射功率小于等于第一预设阈值时才确定在第i个承载载波上以所确定的目标下行发射功率来传输所述第一终端的下行数据，这能够满足业务覆盖和通信质量的要求，因此本公开实施例能够同时保证业务速率和通信质量的要求。
本公开实施例的其他特征和优点将在随后的具体实施方式部分予以详细说明
附图说明
附图是用来提供对本公开实施例的进一步理解，并且构成说明书的一部分，与下面的具体实施方式一起用于解释本公开实施例，但并不构成对本公开实施例的限制。在附图中：
图1是根据本公开一种实施例的用于窄带物联网系统资源分配的方法的流程图；
图2是根据本公开又一实施例的用于窄带物联网系统资源分配的方法的流程图；
图3是根据本公开又一实施例的用于窄带物联网系统资源分配的方法的流程图；
图4是根据本公开再一实施例的用于窄带物联网系统资源分配的方法的流程图；
图5是根据本公开一种实施例的用于窄带物联网系统资源分配的终端的示意框图；
图6是根据本公开一种实施例的用于窄带物联网系统资源分配的服务器的示意框图；
图7是根据本公开又一实施例的用于窄带物联网系统资源分配的服务器的示意框图；以及
图8是根据本公开再一实施例的用于窄带物联网系统资源分配的服务器的示意框图。
具体实施方式
以下结合附图对本公开实施例的具体实施方式进行详细说明。应当理解的是，此处所描述的具体实施方式仅用于说明和解释本公开实施例，并不用于限制本公开实施例。
在详细描述根据本公开实施例的用于窄带物联网系统资源分配的方法、终端和服务器之前，首先介绍一下本公开实施例的应用场景。
窄带物联网通常由终端和服务基站组成。而随着车联网、智慧医疗、智能家居等新兴物联网领域中要被控制的终端的成本和复杂度的日益增加，有必要在窄带物联网中引入云端机器人服务器，以便将简单的处理功能放在本地要被控制的终端上，将复杂的智能处理和运算功能放在云端机器人服务器上并通过网络按照需求下发到要被控制的终端中。本公开的发明人正是基于这样的需求而提出了根据本公开实施例的用于窄带物联网系统资源分配的 方法、终端和服务器。
本公开实施例提供一种用于窄带物联网系统资源分配的方法，如图1所示，该方法可以包括以下步骤S1至步骤S4。
在步骤S1中，获取第一终端的业务请求，所述业务请求包括：(1)下行业务速率要求；(2)接收强度信息，该接收强度信息包括所述第一终端的服务基站的主同步信号的接收强度、辅同步信号的接收强度和参考信号的接收强度中的一者或多者；(3)接收质量信息，该接收质量信息包括所述服务基站的主同步信号的接收质量、辅同步信号的接收质量和参考信号的接收质量中的一者或多者；以及(4)业务优先级标识信息。
其中，第一终端可以首先将其业务请求发送给窄带物联网的服务基站，然后服务基站通过专用控制信令或NAS信令将该业务请求上报给云端机器人服务器，例如，服务基站可以采用特定的已知序列(例如，000111000)和发射功率来上报第一终端的业务请求。这样云端机器人服务器就获取到了第一终端的业务请求。本领域技术人员应当理解的是，这里的已知序列000111000仅是示例，根据实际业务请求的不同，该已知序列也是不同的。
在步骤S2中，依据候选载波信息和所述下行业务速率要求，来确定承载所述第一终端的下行数据所需的承载载波及承载载波数目N，其中，N≥1。
在根据本公开的方法的实施例中，候选载波可以指的是服务基站的为终端提供承载服务的所有载波。所述候选载波信息可以包括各个候选载波的单载波承载最大可支持下行传输速率和各个候选载波的当前负载信息。例如，目前NB-IoT的下行采用15kHz带宽传输，下行速率约250kbps，则各个候选载波的单载波承载最大可支持下行传输速率为250kbps。
以下对步骤S2举例说明。
假设第一终端的业务请求中包括的下行业务速率要求为500kbps，候选载波总共有四个，即候选载波1、2、3和4，而且这四个候选载波的单载波 承载最大可支持下行传输速率均为250kbps，候选载波1、2、3和4的当前负载分别为50％、10％、20％、80％，相当于其当前可用的最高下行业务速率分别为125kbps、225kbps、200kbps和50kbps，因此可以确定承载所述第一终端的下行数据所需的承载载波数目为3且具体的承载载波为候选载波1、2和3，当然，承载载波数目为4且具体的承载载波为候选载波1、2、3和4也是可行的。但是，为了降低第一终端的功耗和处理复杂度，最终确定的承载载波数目N为能够满足所述下行业务速率要求的承载载波数目中的最小承载载波数目，以上面的示例为例，最终确定的承载载波数目N为3而不是4，这是因为，在同样的下行业务速率要求的情况下，承载载波的数目越低越能够降低第一终端的功耗和处理复杂度。
在步骤S3中，依据所述接收质量信息、所确定的承载载波、所确定的承载载波数目、所述接收强度信息来确定各个承载载波的目标下行发射功率；以及
在步骤S4中，在第i个承载载波的总下行发射功率Psum-TX-i小于等于第一预设阈值时，确定在第i个承载载波上以所确定的目标下行发射功率来传输所述第一终端的下行数据。
其中，第i个承载载波的总下行发射功率Psum-TX-i指的是当前在第i个承载载波上承载的所有终端(包括第一终端)的下行发射功率之和。第一预设阈值可以被设置为服务基站的单载波额定发射功率，当然，第一预设阈值低于服务基站的单载波额定发射功率也是可行的。
另外，在步骤S4中，还可以发送业务请求接纳消息，以便第一终端知晓其业务请求被接纳。例如，云端机器人服务器可以向服务基站发送业务请求接纳消息，然后由服务基站将该业务请求接纳消息转发给第一终端。
通过采用上述技术方案，由于根据本公开实施例的方法在获取到第一终端的业务请求之后，首先依据候选载波信息和所述下行业务速率要求确定承 载所述第一终端的下行数据所需的承载载波及承载载波数目N，因此这能够满足下行业务速率的要求，然后在确定了各个承载载波的目标下行发射功率之后，在第i个承载载波的总下行发射功率Psum-TX-i小于等于第一预设阈值(这说明第一终端的下行业务的覆盖不受限)时才确定在第i个承载载波上以所确定的目标下行发射功率来传输所述第一终端的下行数据，这能够满足业务覆盖和通信质量的要求，因此能够同时保证业务速率和通信质量的要求。
根据本公开实施例的方法的又一方面，如图2所示，在步骤S3中，所述依据所述接收质量信息、所确定的承载载波、所确定的承载载波数目、所述接收强度信息来确定各个承载载波的目标下行发射功率可以包括以下步骤S31至S33。
在步骤S31中，依据所述接收质量信息来确定所述第一终端的下行数据所允许的调制编码方式，例如所允许的最高调制编码方式。例如，假设在第一终端的业务请求中包括的接收质量信息是服务基站的参考信号的接收质量SINRRS而且SINRRS＝20dB，则可以确定最高可采用64QAM 3/4调制编码方式。
在步骤S32中，依据所确定的承载载波(例如，各个承载载波的负载情况)、所确定的承载载波数目以及所确定的调制编码方式(例如，最高调制编码方式)来确定各个所述承载载波上的资源块数目和位置。
在步骤S33中，依据所述接收强度信息、所确定的调制编码方式和所确定的资源块数目来确定各个所述承载载波的目标下行发射功率。
通过步骤S31至S33，就能够有效地确定各个所述承载载波的目标下行发射功率。
根据本公开实施例的又一方面，如图3所示，步骤S33可以包括以下步骤S331至S333。
在步骤S331中，依据所述服务基站中的发射功率信息和所述业务请求 中的接收强度信息来确定所述服务基站与所述第一终端之间的最大耦合损耗，其中所述发射功率信息包括所述服务基站的主同步信号的发射功率、辅同步信号的发射功率和参考信号的发射功率中的一者或多者。
例如，假设第一终端的业务请求中包括的接收强度信息是服务基站的主同步信号的接收强度，也即第一终端对服务基站的主同步信号的接收强度(也即功率值)，则云端机器人服务器可以首先从服务基站获取该服务基站的主同步信号的发射功率，然后将从服务基站获取的主同步信号发射功率减去第一终端的业务请求中包含的主同步信号的接收强度，来获得服务基站与第一终端之间的最大耦合损耗，其中该最大耦合损耗包括服务基站的发射天线增益。
再例如，假设第一终端的业务请求中包括的接收强度信息是服务基站的辅同步信号的接收强度，也即第一终端对服务基站的辅同步信号的接收强度(也即功率值)，则云端机器人服务器可以首先从服务基站获取该服务基站的辅同步信号的发射功率，然后将从服务基站获取的辅同步信号发射功率减去第一终端的业务请求中包含的辅同步信号的接收强度，来获得服务基站与第一终端之间的最大耦合损耗，其中该最大耦合损耗包括服务基站的发射天线增益。
再例如，假设第一终端的业务请求中包括的接收强度信息是服务基站的参考信号的接收强度，也即第一终端对服务基站的参考信号的接收强度PR-RS，则云端机器人服务器可以首先从服务基站获取该服务基站的参考信号的发射功率PT-RS，然后将从服务基站获取的参考信号的发射功率PT-RS减去第一终端的业务请求中包括的第一终端对服务基站的参考信号的接收强度PR-RS，来获得服务基站与第一终端之间的最大耦合损耗，其中该最大耦合损耗包括服务基站的发射天线增益。
在步骤S332中，依据所确定的调制编码方式和所确定的资源块数目来 确定各个所述承载载波上的资源块的最低接收功率要求。
以承载载波i为例，最低接收功率要求PRX-MIN-i可以通过如下公式来确定：
PRX-MIN-i＝SINRMIN-i*(Ii+Ni)
其中，SINRMIN-i为承载载波i上的资源块对应的调制编码方式所需的解调信噪比，Ni为承载载波i上的资源块的热噪声功率，Ii为承载载波i的下行干扰功率强度。
在步骤S333中，依据所述最大耦合损耗和所述最低接收功率要求来确定各个所述承载载波的目标下行发射功率。
还是以承载载波i为例，其目标下行发射功率PTX-i可以通过如下公式获得：
PTX-I＝PRX-MIN-I+最大耦合损耗
根据本公开实施例的方法的又一方面，如图4所示，在第i个承载载波的总下行发射功率Psum-TX-i大于所述第一预设阈值时，这说明第一终端的下行业务的覆盖受限，因此在这种情况下，该方法还可以包括以下步骤S5和S6。
在步骤S5中，判断所述第一终端的服务基站的当前总下行发射功率是否小于等于第二预设阈值。
其中，第一终端的服务基站的当前总下行发射功率指的是服务基站所支持的所有载波在当前调度时刻的总下行发射功率，也即覆盖受限终端的目标下行发射功率与覆盖非受限终端的当前下行发射功率的总和。云端机器人服务器可以从服务基站的功率控制器获取到该当前下行发射功率的总和，例如，云端机器人服务器可以向服务基站发送总功率请求信息，然后服务基站会将当前下行发射功率的总和的信息反馈给云端机器人服务器。
其中，第二预设阈值可以被设置为服务基站在其所支持的所有载波上的 可支持的总发射功率最大值。当然，第二预设阈值低于该可支持的总发射功率最大值也是可行的。云端机器人服务完全可以从服务基站的功率控制器获取到该可支持的总发射功率最大值，例如，云端机器人服务器可以向服务基站发送总功率请求信息，然后服务基站会将可支持的总发射功率最大值的信息反馈给云端机器人服务器。
在步骤S6中，在所述第一终端的服务基站的当前总下行发射功率小于等于第二预设阈值时，这说明第一终端的承载载波i的可用下行发射功率能够被提升，因此在该步骤中，确定提高第i个承载载波的可用下行发射功率，以便在第i个承载载波上以所确定的目标下行发射功率PTX-i来传输所述第一终端的下行数据。这样，第i个承载载波就能够以所确定的目标下行发射功率PTX-i来传输第一终端的下行数据，满足了第一终端的下行业务覆盖需求。
根据本公开实施例的方法的又一方面，如图4所示，该方法还可以包括以下步骤S7和S8。
在步骤S7中，判断所述服务基站所服务的终端中是否存在业务优先级低于所述第一终端的业务优先级的终端。
例如，在该步骤中，云端机器人服务器可以首先从服务基站获取该服务基站在当前调度时刻所服务的所有终端的业务类型或业务优先级，并然后判断是否存在业务类型或业务优先级低于第一终端的业务类型或业务优先级的终端。
在步骤S8中，在存在业务类型或业务优先级低于所述第一终端的业务类型或业务优先级的终端时，确定提高第i个承载载波的可用下行发射功率，以便在第i个承载载波上以所确定的目标下行发射功率PTX-i来传输所述第一终端的下行数据。这样，第i个承载载波就能够以所确定的目标下行发射功率PTX-i来传输第一终端的下行数据，满足了第一终端的下行业务覆盖需求。
另外，在步骤S8中，云端机器人服务器可以确定降低业务类型或业务 优先级低的终端的下行传输功率或者在当前调度时刻对业务类型或业务优先级低的终端的下行数据不进行调度，并将第一终端的第i个承载载波的下行发射功率提升为所确定的目标下行发射功率PTX-i，并发送业务请求接纳消息，例如云端机器人服务器可以通过服务基站向第一终端转发业务请求接纳消息也可以直接向第一终端发送业务请求接纳消息。
根据本公开实施例的方法的又一方面，如图4所示，在在步骤S7中确定所述服务基站所服务的终端中没有业务优先级低于所述第一终端的业务优先级的终端时，该方法还可以包括：
在步骤S9中，发送业务请求拒绝消息。例如云端机器人服务器可以通过服务基站向第一终端转发业务请求拒绝消息也可以直接向第一终端发送业务请求拒绝消息。
因此，通过采用根据本公开实施例的方法，在第i个承载载波的功率受限情况下，能够根据服务基站的当前总下行发射功率、所有终端的业务类型或业务优先级等级等对服务基站所服务的终端的下行发射功率进行动态的功率调配，以优先保证覆盖受限但业务优先级高的终端的下行数据传输，因此有效地保证了业务质量和速率。
本公开实施例还提供一种用于窄带物联网系统资源分配的终端，如图5所示，该终端可以包括：
发送模块501，用于发送业务请求，所述业务请求包括：(1)下行业务速率要求；(2)接收强度信息，该接收强度信息包括所述第一终端的服务基站的主同步信号的接收强度、辅同步信号的接收强度和参考信号的接收强度中的一者或多者；(3)接收质量信息，该接收质量信息包括所述服务基站的主同步信号的接收质量、辅同步信号的接收质量和参考信号的接收质量中的一者或多者；以及(4)业务优先级标识信息；以及
接收模块502，用于接收对所述业务请求的业务响应。例如，业务响应 可以指示业务请求被接纳还是拒绝。
本公开实施例还提供一种用于窄带物联网系统资源分配的服务器，如图6所示，该服务器可以包括业务请求获取模块10、承载载波确定模块20、下行发射功率确定模块30和处理模块40。以下对这些模块进行详细描述。
业务请求获取模块10，用于获取第一终端的业务请求，所述业务请求包括：(1)下行业务速率要求；(2)接收强度信息，该接收强度信息包括所述第一终端的服务基站的主同步信号的接收强度、辅同步信号的接收强度和参考信号的接收强度中的一者或多者；(3)接收质量信息，该接收质量信息包括所述服务基站的主同步信号的接收质量、辅同步信号的接收质量和参考信号的接收质量中的一者或多者；以及(4)业务优先级标识信息。
承载载波确定模块20，用于依据候选载波信息和所述下行业务速率要求来确定承载所述第一终端的下行数据所需的承载载波及承载载波数目N，其中，N≥1。其中，所述候选载波信息可以包括各个候选载波的单载波承载最大可支持下行传输速率和各个候选载波的当前负载信息。以上已经结合根据本公开实施例的方法进行了详细描述，此处不再赘述。
下行发射功率确定模块30，用于依据所述接收质量信息、所确定的承载载波、所确定的承载载波数目、所述接收强度信息来确定各个承载载波的目标下行发射功率；以及
处理模块40，用于在第i个承载载波的总下行发射功率小于等于第一预设阈值时，确定在第i个承载载波上以所确定的目标下行发射功率来传输所述第一终端的下行数据。
根据本公开实施例的服务器的又一方面，如图7所示，所述下行发射功率确定模块30可以包括：
调制编码方式确定子模块301，用于依据所述接收质量信息来确定所述第一终端的下行数据所允许的调制编码方式；
资源块确定子模块302，用于依据所确定的承载载波、所确定的承载载波数目以及所确定的调制编码方式来确定各个所述承载载波上的资源块数目和位置；
下行发射功率确定子模块303，用于依据所述接收强度信息、所确定的调制编码方式和所确定的资源块数目来确定各个所述承载载波的目标下行发射功率。
根据本公开实施例的服务器的又一方面，如图8所示，所述下行发射功率确定子模块303可以包括：
最大耦合损耗确定子单元3031，用于依据所述服务基站中的发射功率信息和所述业务请求中的接收强度信息来确定所述服务基站与所述第一终端之间的最大耦合损耗，其中所述发射功率信息包括所述服务基站的主同步信号的发射功率、辅同步信号的发射功率和参考信号的发射功率中的一者或多者；
最低接收功率要求确定子单元3032，用于依据所确定的调制编码方式和所确定的资源块数目来确定各个所述承载载波上的资源块的最低接收功率要求；以及
下行发射功率确定子单元3033，用于依据所述最大耦合损耗和所述最低接收功率要求来确定各个所述承载载波的目标下行发射功率。
根据本公开实施例的服务器的又一方面，所述处理模块40还可以用于：在第i个承载载波的总下行发射功率大于所述第一预设阈值并且所述第一终端的服务基站的当前总下行发射功率小于等于第二预设阈值时，确定提高第i个承载载波的可用下行发射功率，以便在第i个承载载波上以所确定的目标下行发射功率来传输所述第一终端的下行数据。
根据本公开实施例的服务器的又一方面，所述处理模块40还可以用于：在第i个承载载波的总下行发射功率大于所述第一预设阈值、所述服务基站 的当前总下行发射功率大于所述第二预设阈值并且所述服务基站所服务的终端中存在业务优先级低于所述第一终端的业务优先级的终端时，确定提高第i个承载载波的可用下行发射功率，以便在第i个承载载波上以所确定的目标下行发射功率来传输所述第一终端的下行数据。另外，在这种情况下，处理模块40还可以用于确定降低业务优先级低于所述第一终端的业务优先级的终端的下行传输功率，或者确定在当前调度时刻对该终端的下行数据不进行调度。
根据本公开实施例的服务器的又一方面，所述处理模块40还可以用于：在第i个承载载波的总下行发射功率大于所述第一预设阈值、所述服务基站的当前总下行发射功率大于所述第二预设阈值并且所述服务基站所服务的终端中没有业务优先级低于所述第一终端的业务优先级的终端时，发送业务请求拒绝消息。
根据本公开实施例的服务器可以是云端机器人服务器。根据本公开实施例的服务器中的各个模块所执行的操作的具体实现方式已经在根据本公开实施例的方法中进行了详细描述，此处不再赘述。
以上结合附图详细描述了本公开的优选实施方式，但是，本公开并不限于上述实施方式中的具体细节，在本公开的技术构思范围内，可以对本公开的技术方案进行多种简单变型，这些简单变型均属于本公开的保护范围。
另外需要说明的是，在上述具体实施方式中所描述的各个具体技术特征，在不矛盾的情况下，可以通过任何合适的方式进行组合。为了避免不必要的重复，本公开对各种可能的组合方式不再另行说明。
此外，本公开的各种不同的实施方式之间也可以进行任意组合，只要其不违背本公开的思想，其同样应当视为本公开所公开的内容。

Claims (19)

  1. 一种用于窄带物联网系统资源分配的方法，其特征在于，该方法包括：
    获取第一终端的业务请求，所述业务请求包括：(1)下行业务速率要求；(2)接收强度信息，该接收强度信息包括所述第一终端的服务基站的主同步信号的接收强度、辅同步信号的接收强度和参考信号的接收强度中的一者或多者；(3)接收质量信息，该接收质量信息包括所述服务基站的主同步信号的接收质量、辅同步信号的接收质量和参考信号的接收质量中的一者或多者；以及(4)业务优先级标识信息；
    依据候选载波信息和所述下行业务速率要求来确定承载所述第一终端的下行数据所需的承载载波及承载载波数目N，其中，N≥1；
    依据所述接收质量信息、所确定的承载载波、所确定的承载载波数目和所述接收强度信息来确定各个承载载波的目标下行发射功率；以及
    在第i个承载载波的总下行发射功率小于等于第一预设阈值时，确定在第i个承载载波上以所确定的目标下行发射功率来传输所述第一终端的下行数据。
  2. 根据权利要求1所述的方法，其特征在于，所述依据所述接收质量信息、所确定的承载载波、所确定的承载载波数目和所述接收强度信息来确定各个承载载波的目标下行发射功率包括：
    依据所述接收质量信息来确定所述第一终端的下行数据所允许的调制编码方式；
    依据所确定的承载载波、所确定的承载载波数目以及所确定的调制编码方式来确定各个所述承载载波上的资源块数目和位置；
    依据所述接收强度信息、所确定的调制编码方式和所确定的资源块数目来确定各个所述承载载波的目标下行发射功率。
  3. 根据权利要求2所述的方法，其特征在于，所述依据所述接收强度信息、所确定的调制编码方式和所确定的资源块数目来确定各个所述承载载波的目标下行发射功率包括：
    依据所述服务基站中的发射功率信息和所述业务请求中的接收强度信息来确定所述服务基站与所述第一终端之间的最大耦合损耗，其中所述发射功率信息包括所述服务基站的主同步信号的发射功率、辅同步信号的发射功率和参考信号的发射功率中的一者或多者；
    依据所确定的调制编码方式和所确定的资源块数目来确定各个所述承载载波上的资源块的最低接收功率要求；以及
    依据所述最大耦合损耗和所述最低接收功率要求来确定各个所述承载载波的目标下行发射功率。
  4. 根据权利要求1所述的方法，其特征在于，该方法还包括：
    在第i个承载载波的总下行发射功率大于所述第一预设阈值并且所述服务基站的当前总下行发射功率小于等于第二预设阈值时，确定提高第i个承载载波的可用下行发射功率，以便在第i个承载载波上以所确定的目标下行发射功率来传输所述第一终端的下行数据。
  5. 根据权利要求4所述的方法，其特征在于，该方法还包括：
    在第i个承载载波的总下行发射功率大于所述第一预设阈值、所述服务基站的当前总下行发射功率大于所述第二预设阈值并且所述服务基站所服务的终端中存在业务优先级低于所述第一终端的业务优先级的终端时，确定 提高第i个承载载波的可用下行发射功率，以便在第i个承载载波上以所确定的目标下行发射功率来传输所述第一终端的下行数据。
  6. 根据权利要求5所述的方法，其特征在于，该方法还包括：
    确定降低业务优先级低于所述第一终端的业务优先级的终端的下行传输功率，或者确定在当前调度时刻对该终端的下行数据不进行调度。
  7. 根据权利要求5所述的方法，其特征在于，该方法还包括：
    在第i个承载载波的总下行发射功率大于所述第一预设阈值、所述服务基站的当前总下行发射功率大于所述第二预设阈值并且所述服务基站所服务的终端中没有业务优先级低于所述第一终端的业务优先级的终端时，发送业务请求拒绝消息。
  8. 根据权利要求1至7中任一权利要求所述的方法，其特征在于，所述候选载波信息包括单载波承载最大可支持下行传输速率和当前负载信息。
  9. 根据权利要求1至7中任一权利要求所述的方法，其特征在于，所述承载载波数目N为能够满足所述下行业务速率要求的承载载波数目中的最小承载载波数目。
  10. 一种用于窄带物联网系统资源分配的终端，其特征在于，该终端包括：
    发送模块，用于发送业务请求，所述业务请求包括：(1)下行业务速率要求；(2)接收强度信息，该接收强度信息包括所述第一终端的服务基站的主同步信号的接收强度、辅同步信号的接收强度和参考信号的接收强度中的一者或多者；(3)接收质量信息，该接收质量信息包括所述服务基站的主同 步信号的接收质量、辅同步信号的接收质量和参考信号的接收质量中的一者或多者；以及(4)业务优先级标识信息；以及
    接收模块，用于接收对所述业务请求的业务响应。
  11. 一种用于窄带物联网系统资源分配的服务器，其特征在于，该服务器包括：
    业务请求获取模块，用于获取第一终端的业务请求，所述业务请求包括：(1)下行业务速率要求；(2)接收强度信息，该接收强度信息包括所述第一终端的服务基站的主同步信号的接收强度、辅同步信号的接收强度和参考信号的接收强度中的一者或多者；(3)接收质量信息，该接收质量信息包括所述服务基站的主同步信号的接收质量、辅同步信号的接收质量和参考信号的接收质量中的一者或多者；以及(4)业务优先级标识信息；
    承载载波确定模块，用于依据候选载波信息和所述下行业务速率要求来确定承载所述第一终端的下行数据所需的承载载波及承载载波数目N，其中，N≥1；
    下行发射功率确定模块，用于依据所述接收质量信息、所确定的承载载波、所确定的承载载波数目和所述接收强度信息来确定各个承载载波的目标下行发射功率；以及
    处理模块，用于在第i个承载载波的总下行发射功率小于等于第一预设阈值时，确定在第i个承载载波上以所确定的目标下行发射功率来传输所述第一终端的下行数据。
  12. 根据权利要求11所述的服务器，其特征在于，所述下行发射功率确定模块包括：
    调制编码方式确定子模块，用于依据所述接收质量信息来确定所述第一 终端的下行数据所允许的调制编码方式；
    资源块确定子模块，用于依据所确定的承载载波、所确定的承载载波数目以及所确定的调制编码方式来确定各个所述承载载波上的资源块数目和位置；
    下行发射功率确定子模块，用于依据所述接收强度信息、所确定的调制编码方式和所确定的资源块数目来确定各个所述承载载波的目标下行发射功率。
  13. 根据权利要求12所述的服务器，其特征在于，所述下行发射功率确定子模块包括：
    最大耦合损耗确定子单元，用于依据所述服务基站中的发射功率信息和所述业务请求中的接收强度信息来确定所述服务基站与所述第一终端之间的最大耦合损耗，其中所述发射功率信息包括所述服务基站的主同步信号的发射功率、辅同步信号的发射功率和参考信号的发射功率中的一者或多者；
    最低接收功率要求确定子单元，用于依据所确定的调制编码方式和所确定的资源块数目来确定各个所述承载载波上的资源块的最低接收功率要求；以及
    下行发射功率确定子单元，用于依据所述最大耦合损耗和所述最低接收功率要求来确定各个所述承载载波的目标下行发射功率。
  14. 根据权利要求11所述的服务器，其特征在于，所述处理模块还用于：
    在第i个承载载波的总下行发射功率大于所述第一预设阈值并且所述服务基站的当前总下行发射功率小于等于第二预设阈值时，确定提高第i个承载载波的可用下行发射功率，以便在第i个承载载波上以所确定的目标下行 发射功率来传输所述第一终端的下行数据。
  15. 根据权利要求14所述的服务器，其特征在于，所述处理模块还用于：
    在第i个承载载波的总下行发射功率大于所述第一预设阈值、所述服务基站的当前总下行发射功率大于所述第二预设阈值并且所述服务基站所服务的终端中存在业务优先级低于所述第一终端的业务优先级的终端时，确定提高第i个承载载波的可用下行发射功率，以便在第i个承载载波上以所确定的目标下行发射功率来传输所述第一终端的下行数据。
  16. 根据权利要求15所述的服务器，其特征在于，所述处理模块还用于：确定降低业务优先级低于所述第一终端的业务优先级的终端的下行传输功率，或者确定在当前调度时刻对该终端的下行数据不进行调度。
  17. 根据权利要求15所述的服务器，其特征在于，所述处理模块还用于：在第i个承载载波的总下行发射功率大于所述第一预设阈值、所述服务基站的当前总下行发射功率大于所述第二预设阈值并且所述服务基站所服务的终端中没有业务优先级低于所述第一终端的业务优先级的终端时，发送业务请求拒绝消息。
  18. 根据权利要求11至17中任一权利要求所述的服务器，其特征在于，所述候选载波信息包括单载波承载最大可支持下行传输速率和当前负载信息。
  19. 根据权利要求11至17中任一权利要求所述的方法，其特征在于，所述承载载波数目N为能够满足所述下行业务速率要求的承载载波数目中 的最小承载载波数目。
PCT/CN2016/098249 2016-09-06 2016-09-06 用于窄带物联网系统资源分配的方法、终端和服务器 Ceased WO2018045494A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/CN2016/098249 WO2018045494A1 (zh) 2016-09-06 2016-09-06 用于窄带物联网系统资源分配的方法、终端和服务器
CN201680004908.7A CN107223354B (zh) 2016-09-06 2016-09-06 用于窄带物联网系统资源分配的方法、终端和服务器
US16/347,095 US10652916B2 (en) 2016-09-06 2016-09-06 Method, terminal and server for allocating Narrow Band Internet of Things system resources

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/098249 WO2018045494A1 (zh) 2016-09-06 2016-09-06 用于窄带物联网系统资源分配的方法、终端和服务器

Publications (1)

Publication Number Publication Date
WO2018045494A1 true WO2018045494A1 (zh) 2018-03-15

Family

ID=59927640

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/098249 Ceased WO2018045494A1 (zh) 2016-09-06 2016-09-06 用于窄带物联网系统资源分配的方法、终端和服务器

Country Status (3)

Country Link
US (1) US10652916B2 (zh)
CN (1) CN107223354B (zh)
WO (1) WO2018045494A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113692069A (zh) * 2018-10-31 2021-11-23 维沃移动通信有限公司 一种分离承载的控制方法及相关设备

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3618359B1 (en) * 2017-04-27 2021-06-23 Beijing Xiaomi Mobile Software Co., Ltd. Method and device for signaling transmission
JP6923672B2 (ja) * 2017-04-28 2021-08-25 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． 情報送信方法、受信電力測定方法、デバイス、およびシステム
CN110049540B (zh) * 2018-01-15 2021-10-08 广东电网有限责任公司电力调度控制中心 一种智能家居中用户终端协同和功率分配方法
CN110149715B (zh) * 2018-02-14 2023-01-10 大唐移动通信设备有限公司 一种信息指示方法、pt-rs传输方法及装置
CN108896242A (zh) * 2018-04-20 2018-11-27 广东亿迅科技有限公司 一种基于NB-IoT技术的水务漏损分析方法及装置
US11700601B2 (en) * 2018-08-08 2023-07-11 Lg Electronics Inc. Method by which user equipment controls transmission power of sidelink signal in wireless communication system and apparatus therefor
CN111343723B (zh) * 2020-03-04 2023-11-17 宇龙计算机通信科技(深圳)有限公司 数据传输方法及相关设备
CN114096007B (zh) * 2021-10-18 2024-06-07 中国联合网络通信集团有限公司 一种业务传输方法、装置、服务器及存储介质
CN120659138A (zh) * 2024-03-13 2025-09-16 华为技术有限公司 功率控制方法及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217497A (zh) * 2008-01-18 2008-07-09 北京邮电大学 一种无线网状网络的路径选择方法
CN102638866A (zh) * 2012-04-16 2012-08-15 东南大学 一种基于m2m业务特征的移动通信网络接入方法
US20120327787A1 (en) * 2011-06-24 2012-12-27 Jahangir Mohammed Core services platform for wireless voice, data and messaging network services
CN104937966A (zh) * 2012-10-15 2015-09-23 黑莓有限公司 无线通信系统中的设备间通信授权和数据嗅探

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101827061A (zh) 2010-03-26 2010-09-08 清华大学 正交频分复用系统下行链路子载波分配和峰均比抑制方法
EP2774284A4 (en) * 2011-11-04 2016-02-10 Intel Corp PROCESS FOR TRANSPORTING TO A GROUP OF DEVICES
CN103188685B (zh) 2011-12-27 2016-06-22 华为技术有限公司 无线资源分配方法和设备
CN104641697A (zh) * 2013-07-30 2015-05-20 华为技术有限公司 获取下行链路质量信息的方法及装置
CN104581963A (zh) 2014-12-19 2015-04-29 中国科学院上海微系统与信息技术研究所 一种基于lte的认知网络下行链路资源分配方法
CN104640217B (zh) 2015-01-27 2017-12-15 浙江大学 基于网络编码的ofdma网络上下行资源联合分配方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217497A (zh) * 2008-01-18 2008-07-09 北京邮电大学 一种无线网状网络的路径选择方法
US20120327787A1 (en) * 2011-06-24 2012-12-27 Jahangir Mohammed Core services platform for wireless voice, data and messaging network services
CN102638866A (zh) * 2012-04-16 2012-08-15 东南大学 一种基于m2m业务特征的移动通信网络接入方法
CN104937966A (zh) * 2012-10-15 2015-09-23 黑莓有限公司 无线通信系统中的设备间通信授权和数据嗅探

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113692069A (zh) * 2018-10-31 2021-11-23 维沃移动通信有限公司 一种分离承载的控制方法及相关设备

Also Published As

Publication number Publication date
US20190274150A1 (en) 2019-09-05
CN107223354A (zh) 2017-09-29
US10652916B2 (en) 2020-05-12
CN107223354B (zh) 2020-06-30

Similar Documents

Publication Publication Date Title
CN107223354B (zh) 用于窄带物联网系统资源分配的方法、终端和服务器
US10149171B2 (en) Resource allocation method and apparatus for cooperative transmission of base stations in wireless communication system
US11924817B2 (en) Wireless communications system, communications device and wireless network infrastructure
US10375748B2 (en) Method for terminal-to-terminal communication in a cellular mobile radio network, and a system therefor
WO2021109346A1 (en) Method and device for allocating resources for sidelink transmission
US11134525B2 (en) Data sending method and device
KR102099274B1 (ko) 분산 안테나 구조의 무선 통신 시스템에서 부하 분산 제어 시스템 및 부하 분산 방법
KR20230047398A (ko) 전 이중 통신을 지원하는 무선통신시스템에서 데이터를 송수신하는 방법 및 이를 위한 장치
KR101466903B1 (ko) D2d 통신을 위한 통신단말의 송신전력정보 결정방법, d2d 통신을 위한 통신단말의 자원할당방법 및 d2d 통신시스템
US8825041B2 (en) Relay device, relay device control method, and radio communication system
US20160198418A1 (en) Communication system, mobile station apparatus, and communication method
KR20230008798A (ko) 전 이중 통신을 지원하는 무선통신시스템에서 데이터를 송수신하는 방법 및 이를 위한 장치
US20210345302A1 (en) Telecommunications apparatus and methods
CN111432498A (zh) 一种车联网通信资源复用方法、装置和系统
CN111132317B (zh) 资源分配方法、终端及通信设备
WO2025042620A1 (en) Relay selected short id management for u2u sidelink relay adaptation protocol (srap)
JP2023046094A (ja) ユーザ装置、通信装置及び通信方法
US20240147506A1 (en) Dynamic sl resource allocation
CN113141658B (zh) 一种基于5g nsa语音通话的载波配置方法和装置
WO2025071922A1 (en) Short id management using pc5-rrc for u2u sidelink relay adaptation protocol (srap)
KR101499391B1 (ko) D2d 통신을 위한 통신단말의 송신전력정보 결정방법 및 d2d 통신을 위한 통신단말의 자원할당방법
CN119923926A (zh) 一种通信方法及装置
CN120390292A (zh) 一种通信方法及装置
KR101593334B1 (ko) 단말간 직접 통신을 제공하는 방법
WO2025042619A1 (en) Short id management for u2u sidelink relay adaptation protocol (srap)

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: 16915430

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC ( EPO FORM 1205A DATED 21/06/2019 )

122 Ep: pct application non-entry in european phase

Ref document number: 16915430

Country of ref document: EP

Kind code of ref document: A1