US11224062B2 - Method for configuring scheduling request, network device and terminal device - Google Patents

Method for configuring scheduling request, network device and terminal device Download PDF

Info

Publication number
US11224062B2
US11224062B2 US16/646,764 US201716646764A US11224062B2 US 11224062 B2 US11224062 B2 US 11224062B2 US 201716646764 A US201716646764 A US 201716646764A US 11224062 B2 US11224062 B2 US 11224062B2
Authority
US
United States
Prior art keywords
configuration
lch
configurations
terminal device
carrier
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.)
Active, expires
Application number
US16/646,764
Other versions
US20200275467A1 (en
Inventor
Hai Tang
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.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp 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 Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Assigned to GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD. reassignment GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TANG, HAI
Publication of US20200275467A1 publication Critical patent/US20200275467A1/en
Application granted granted Critical
Publication of US11224062B2 publication Critical patent/US11224062B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H04W72/1284—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H04W72/14—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the application relates to the technical field of information processing, and particularly to a method for configuring a Scheduling Request (SR), a network device, a terminal device and a computer storage medium.
  • SR Scheduling Request
  • a Long Term Evolution (LTE) SR is a 1-bit message transmitted by a terminal on a Physical Uplink Control Channel (PUCCH) to request for an uplink grant resource.
  • a Media Access Control (MAC) entity corresponding to a terminal may be configured with one or more SR configurations. Multiple SR configurations are configured so that Secondary Cells (SCells) have corresponding SR configurations under a Carrier Aggregation (CA) condition.
  • SCells Secondary Cells
  • CA Carrier Aggregation
  • NR New Radio
  • embodiments of the application provide a method for configuring an SR, a network device, a terminal device and a computer storage medium.
  • the embodiments of the application provide a method for configuring an SR, applied to a network device, the method including:
  • an SR configuration corresponding to each of at least one carrier is configured for a terminal device, at least one SR configuration being configured for the same carrier;
  • a mapping relationship between each of at least one Logical Channel (LCH) and the at least one SR configuration is configured for the terminal device.
  • LCH Logical Channel
  • the embodiments of the application provide a method for configuring an SR, applied to a terminal device, the method including:
  • an SR configuration configured by a network side and corresponding to each of at least one carrier is received, at least one SR configuration being configured for a same carrier;
  • mapping relationship configured by the network side and between each of at least one LCH and the at least one SR configuration is received.
  • the embodiments of the application provide a network device, including:
  • a first configuration unit configured to configure, for a terminal device, an SR configuration corresponding to each of at least one carrier, at least one SR configuration being configured for a same carrier;
  • a second configuration unit configured to configure, for the terminal device, a mapping relationship between each of at least one LCH and the at least one SR configuration.
  • the embodiments of the application provide a terminal device, including:
  • a first processing unit configured to receive an SR configuration configured by a network side and corresponding to each of at least one carrier, at least one SR configuration being configured for a same carrier;
  • a second processing unit configured to receive a mapping relationship configured by the network side and between each of at least one LCH and the at least one SR configuration.
  • the embodiments of the application provide a network device, including a processor and a memory configured to store a computer program capable of running on the processor.
  • the processor may be configured to, when the computer program is running on the processor, execute the steps of the abovementioned method.
  • the embodiments of the application provide a terminal device, including a processor and a memory configured to store a computer program capable of running on the processor.
  • the processor may be configured to, when the computer program is running on the processor, execute the steps of the abovementioned method.
  • the embodiments of the application provide a computer storage medium having stored thereon computer-executable instructions that, when executed, implement the steps of the abovementioned method.
  • the SR configurations configured for the terminal device by a network and corresponding to different carriers may be received, and the SR configurations are mapped to the LCHs.
  • the terminal device may be ensured to acquire correspondences among the LCHs, the carriers and the SR configurations, so that a corresponding resource may be timely determined during scheduling requesting, and system processing efficiency is improved.
  • FIG. 1 is a first flowchart of a method for configuring an SR according to an embodiment of the application.
  • FIG. 2 is a second flowchart of a method for configuring an SR according to an embodiment of the application.
  • FIG. 3 is a composition structure diagram of a network device according to an embodiment of the application.
  • the embodiment of the application provides a method for configuring an SR, which is applied to a network device and, as shown in FIG. 1 , includes the following operations 101 to 102 .
  • an SR configuration corresponding to each of at least one carrier respectively is configured for a terminal device, at least one SR configuration being configured for the same carrier.
  • a mapping relationship between each of at least one LCH and the at least one SR configuration is configured for the terminal device.
  • the embodiment may particularly be applied to a CA scenario, and under the condition of multiple carriers, multiple carriers may be configured for the same terminal device.
  • the carrier 1 may be considered as a Primary Cell (PCell), and the carrier 2 may be considered as an SCell.
  • PCell Primary Cell
  • the terminal device provided in the embodiment may be a terminal device supporting multiple LCHs.
  • a terminal device may support four LCHs which may be designated as ⁇ LCH1, LCH2, LCH3, LCH4 ⁇ respectively.
  • the SR configuration corresponding to each of the at least one carrier is configured for the terminal device may include that: different SR configurations are configured for different carriers, different SR configurations with the same SR configuration period being configured for different carriers.
  • SR configurations are configured for different carriers respectively. Descriptions are made still with a scenario with two carriers as an example. For example, for the carrier 1, two corresponding SR configurations are SR-CONFIG-1-A and SR-CONFIG-1-B respectively; and for the carrier 2, two corresponding SR configurations are SR-CONFIG-2-A and SR-CONFIG-2-B respectively. There is made such a hypothesis that SR-CONFIG-1-A and the SR-CONFIG-2-A have the same SR configuration period and, similarly, SR-CONFIG-1-B and SR-CONFIG-2-B have the same SR configuration period, as shown in Table 1.
  • a method for configuring the mapping relationship between the LCH and the SR configuration includes the following operations.
  • SR configurations with a same SR configuration period are selected for each LCH from among the different SR configurations configured for different carriers.
  • the SR configurations with the same configuration period and corresponding to one or more carriers are configured for the same LCH.
  • the network maps two SR configurations corresponding to different carriers respectively to each LCH, as shown in Table 2.
  • a second manner the difference with the first manner is that, in this manner, it is unnecessary to set so many SR configurations, and only through relatively few SR configurations, different carriers are configured and multiple LCHs are mapped.
  • Specific processing is as follows.
  • the operation that the SR configuration corresponding to each of the at least one carrier is configured for the terminal device may include the following operation.
  • the same SR configuration is configured for different carriers of the at least one carrier.
  • At least one PUCCH resource for different carriers may be set in each SR configuration.
  • different SR configurations may have different SR periods.
  • the same SR configuration is configured for different carriers respectively.
  • a PUCCH resource corresponding to SR-CONFIG-1 is located on the carrier 1 and the carrier 2 respectively, and a PUCCH resource corresponding to SR-CONFIG-2 is located on the carrier 1 and the carrier 2 respectively.
  • SR-CONFIG-1 and SR-CONFIG-2 have different SR periods.
  • the operation that the mapping relationship between each of the at least one LCH and the at least one SR configuration is configured for the terminal device may include the following operation.
  • An SR configuration is mapped to each LCH, the SR configuration including a PUCCH resource for the at least one carrier.
  • the network configures mapping between the LCH and the SR configuration.
  • the following mapping relationship between the LCH and the SR configuration may be formed respectively based on a mapping relationship between different SR configurations and carriers: the network maps one SR configuration to each LCH, said one SR configuration including PUCCH resources of two carriers, as shown in Table 3.
  • the SR configurations configured for the terminal device by a network and corresponding to different carriers may be received, and the SR configurations are mapped to the LCHs.
  • the terminal device may be ensured to acquire correspondences among the LCHs, the carriers and the SR configurations, so that a corresponding resource may be timely determined during scheduling requesting, and system processing efficiency is improved.
  • the embodiment of the application provides a method for configuring an SR, which is applied to a terminal device and, as shown in FIG. 2 , includes the following operations 201 to 202 .
  • an SR configuration configured by a network side and corresponding to each of at least one carrier is received, at least one SR configuration being configured for the same carrier.
  • a mapping relationship configured by the network side and between each of at least one LCH and the at least one SR configuration is received.
  • the embodiment may particularly be applied to a CA scenario, and under the condition of multiple carriers, multiple carriers may be configured for the same terminal device.
  • the terminal device aggregates two carriers, i.e., a carrier 1 and a carrier 2, the carrier 1 may be considered as a PCell, and the carrier 2 may be considered as an SCell.
  • the terminal device provided in the embodiment may be a terminal device supporting multiple LCHs.
  • a terminal device may support four LCHs which may be designated as ⁇ LCH1, LCH2, LCH3, LCH4 ⁇ respectively.
  • the operation that the SR configuration, configured by the network side, corresponding to each of the at least one carrier is received may include the following operation.
  • Different SR configurations configured for different carriers by the network side are received, different SR configurations with the same SR configuration period being configured for different carriers.
  • SR configurations are configured for different carriers respectively. Descriptions are made still with a scenario with two carriers as an example. For example, for the carrier 1, two corresponding SR configurations are SR-CONFIG-1-A and SR-CONFIG-1-B respectively; and for the carrier 2, two corresponding SR configurations are SR-CONFIG-2-A and SR-CONFIG-2-B respectively. There is made such a hypothesis that SR-CONFIG-1-A and the SR-CONFIG-2-A have the same SR configuration period and, similarly, SR-CONFIG-1-B and SR-CONFIG-2-B have the same SR configuration period, as shown in Table 1.
  • the operation that the mapping relationship configured by the network side and between each of the at least one LCH and the at least one SR configuration is received may include the following operation.
  • a mapping relationship configured by the network side and between each LCH and the SR configurations corresponding to different carriers is received.
  • each LCH is mapped to the SR configurations with the same SR configuration period, which are configured for different carriers.
  • the SR configurations with the same configuration period and corresponding to one or more carriers are configured for the same LCH.
  • the network maps two SR configurations corresponding to different carriers respectively to each LCH, as shown in Table 2.
  • a second manner the difference with the first manner is that, in this manner, it is unnecessary to set so many SR configurations, and only through relatively few SR configurations, different carriers are configured and multiple LCHs are mapped.
  • Specific processing is as follows.
  • the operation that the SR configuration, configured by the network side, corresponding to each of the at least one carrier is received may include the following operation.
  • a same SR configuration configured by the network side for different carriers of the at least one carrier is received.
  • At least one PUCCH resource for different carriers may be set in each SR configuration.
  • different SR configurations may have different SR periods.
  • the same SR configuration is configured for different carriers respectively.
  • a PUCCH resource corresponding to SR-CONFIG-1 is located on the carrier 1 and the carrier 2 respectively, and a PUCCH resource corresponding SR-CONFIG-2 is located on the carrier 1 and the carrier 2 respectively.
  • SR-CONFIG-1 and SR-CONFIG-2 have different SR periods.
  • the operation that the mapping relationship configured by the network side and between each of the at least one LCH and the at least one SR configuration is received may include the following operation.
  • the network configures mapping between the LCH and the SR configuration.
  • the following mapping relationship between the LCH and the SR configuration may be formed respectively based on a mapping relationship between different SR configurations and carriers: the network maps one SR configuration to each LCH, said one SR configuration including PUCCH resources of two carriers, as shown in Table 3.
  • reporting of the SR may further be performed on a terminal device side based on a configuration condition of the network side. No matter which manner is adopted, the following processing manner is adopted when the terminal device reports the SR.
  • an LCH on which reporting of the SR is triggered is acquired.
  • the at least one SR configuration corresponding to the LCH is acquired.
  • a PUCCH resource nearest to a moment when reporting of the SR is triggered is selected based on a PUCCH resource corresponding to the at least one SR configuration, and an SR is transmitted on the selected PUCCH resource.
  • the terminal device selects the corresponding SR configuration according to the LCH on which reporting of the SR is triggered. For example, if the reporting of the SR is triggered on an LCH1, selection is performed as follows.
  • an SR corresponding to SR-CONFIG-1-A and SR-CONFIG-2-A may be selected to be selected.
  • an SR corresponding SR-CONFIG-1 may be selected to be reported.
  • the terminal device selects a PUCCH resource nearest to a moment when reporting of the SR is triggered to transmit the SR.
  • the SR configurations configured for the terminal device by a network and corresponding to different carriers may be received, and the SR configurations are mapped to the LCHs.
  • the terminal device may be ensured to acquire correspondences among the LCHs, the carriers and the SR configurations, so that a corresponding resource may be timely determined during scheduling requesting, and system processing efficiency is improved.
  • the first configuration unit 31 is configured to configure, for a terminal device, an SR configuration corresponding to each of at least one carrier, at least one SR configuration being configured for the same carrier.
  • the terminal device provided in the embodiment may be a terminal device supporting multiple LCHs.
  • a terminal device may support four LCHs which may be designated as ⁇ LCH1, LCH2, LCH3, LCH4 ⁇ respectively.
  • the first configuration unit is configured to configure different SR configurations for different carriers, different SR configurations with the same SR configuration period being configured for different carriers.
  • a method for configuring the mapping relationship between the LCH and the SR configuration includes the following operations.
  • the second configuration unit is configured to select, for each LCH, SR configurations corresponding to different carriers and establish a mapping relationship between each LCH and the selected SR configurations corresponding to different carriers.
  • the second configuration unit is configured to select, for each LCH, SR configurations with a same SR configuration period from among the different SR configurations configured for different carriers.
  • a second manner the difference with the first manner is that, in this manner, it is unnecessary to set so many SR configurations, and only through relatively few SR configurations, different carriers are configured and multiple LCHs are mapped.
  • Specific processing is as follows.
  • the first configuration unit is configured to configure the same SR configuration for different carriers of the at least one carrier.
  • At least one PUCCH resource for different carriers may be set in each SR configuration.
  • different SR configurations may have different SR periods.
  • the network configures mapping between the LCH and the SR configuration.
  • the following mapping relationship between the LCH and the SR configuration may be formed respectively based on a mapping relationship between different SR configurations and carriers: the network maps one SR configuration to each LCH, said one SR configuration including PUCCH resources of two carriers, as shown in Table 3.
  • the SR configurations configured for the terminal device by a network and corresponding to different carriers may be received, and the SR configurations are mapped to the LCHs.
  • the terminal device may be ensured to acquire correspondences among the LCHs, the carriers and the SR configurations, so that a corresponding resource may be timely determined during scheduling requesting, and system processing efficiency is improved.
  • the embodiment of the application provides a terminal device, which, as shown in FIG. 4 , includes a first processing unit 41 and a second processing unit 42 .
  • the first processing unit 41 is configured to receive an SR configuration configured by a network side and corresponding to each of at least one carrier, at least one SR configuration being configured for the same carrier.
  • the second processing unit 42 is configured to receive a mapping relationship configured by the network side and between each of at least one LCH and the at least one SR configuration.
  • the embodiment may particularly be applied to a CA scenario, and under the condition of multiple carriers, multiple carriers may be configured for the same terminal device.
  • the carrier 1 may be considered as a PCell, and the carrier 2 may be considered as an SCell.
  • the terminal device provided in the embodiment may be a terminal device supporting multiple LCHs.
  • a terminal device may support four LCHs which may be designated as ⁇ LCH1, LCH2, LCH3, LCH4 ⁇ respectively.
  • the first processing unit is configured to receive different SR configurations configured for different carriers by the network side, different SR configurations with the same SR configuration period being configured for different carriers.
  • SR configurations are configured for different carriers respectively. Descriptions are made still with a scenario with two carriers as an example. For example, for the carrier 1, two corresponding SR configurations are SR-CONFIG-1-A and SR-CONFIG-1-B respectively; and for the carrier 2, two corresponding SR configurations are SR-CONFIG-2-A and SR-CONFIG-2-B respectively. There is made such a hypothesis that SR-CONFIG-1-A and the SR-CONFIG-2-A have the same SR configuration period and, similarly, SR-CONFIG-1-B and SR-CONFIG-2-B have the same SR configuration period, as shown in Table 1.
  • the second processing unit is configured to receive a mapping relationship configured by the network side and between each LCH and the SR configurations corresponding to different carriers.
  • each LCH is mapped to the SR configurations with the same SR configuration period, which are configured for different carriers.
  • the SR configurations with the same configuration period and corresponding to one or more carriers are configured for the same LCH.
  • the network maps two SR configurations corresponding to different carriers respectively to each LCH, as shown in Table 2.
  • a second manner the difference with the first manner is that, in this manner, it is unnecessary to set so many SR configurations, and only through relatively few SR configurations, different carriers are configured and multiple LCHs are mapped.
  • Specific processing is as follows.
  • the first processing unit is configured to receive the same SR configuration configured by the network side for different carriers of the at least one carrier.
  • At least one PUCCH resource for different carriers may be set in each SR configuration.
  • different SR configurations may have different SR periods.
  • the same SR configuration is configured for different carriers respectively.
  • a PUCCH resource corresponding to SR-CONFIG-1 is located on the carrier 1 and the carrier 2 respectively, and a PUCCH resource corresponding to SR-CONFIG-2 is located on the carrier 1 and the carrier 2 respectively.
  • SR-CONFIG-1 and SR-CONFIG-2 have different SR periods.
  • the second processing unit is configured to receive the SR configuration configured for each LCH by the network side, the SR configuration including a PUCCH resource for the at least one carrier.
  • reporting of the SR may further be performed on a terminal device side based on a configuration condition of the network side. No matter which manner is adopted, the following processing manner is adopted when the terminal device reports the SR.
  • the terminal device may further include a transmission unit 43 .
  • the transmission unit 43 is configured to, when the SR is reported, acquire an LCH on which reporting of the SR is triggered, acquire the at least one SR configuration corresponding to the acquired LCH, select, based on a PUCCH resource corresponding to the at least one SR configuration, a PUCCH resource nearest to a moment when reporting of the SR is triggered, and transmit an SR on the selected PUCCH resource.
  • the terminal device selects the corresponding SR configuration according to the LCH on which reporting of the SR is triggered. For example, if the reporting of the SR is triggered on an LCH1, selection is performed as follows.
  • an SR corresponding SR-CONFIG-1 may be selected to be reported.
  • the terminal device selects a PUCCH resource nearest to a moment when reporting of the SR is triggered to transmit the SR.
  • the embodiments of the application also provide a hardware composition architecture of a terminal device, which, as shown in FIG. 5 , includes at least one processor 51 , a memory 52 and at least one network interface 53 . Each component is coupled together through a bus system 54 . It can be understood that the bus system 54 is configured to implement connection communication between these components.
  • the bus system 54 includes a data bus and further includes a power bus, a control bus and a state signal bus. However, for clear description, various buses in FIG. 5 are marked as the bus system 54 .
  • the memory 52 in the embodiment of the application may be a volatile memory or a nonvolatile memory, or may include both the volatile and nonvolatile memories.
  • the memory 52 stores the following elements, executable modules or data structures, or a subset thereof or an extended set thereof:
  • the terminal device may process the steps of the method in the first embodiment and will not be elaborated herein.
  • the embodiments of the application provide a terminal device, which includes a processor and a memory configured to store a computer program capable of running on the processor.
  • the processor is configured to, when the computer program is running on the processor, execute the steps of the method in the second embodiment. No more elaborations will be made herein.
  • the device of the embodiments of the application may also be stored in a computer-readable storage medium.
  • the technical solutions of the embodiments of the application substantially or parts making contributions to the conventional art may be embodied in form of software product, and the computer software product is stored in a storage medium, including a plurality of instructions configured to enable a computer device (which may be a personal computer, a server, a network device or the like) to execute all or part of the method in each embodiment of the application.
  • the storage medium includes: various media capable of storing program codes such as a U disk, a mobile hard disk, a Read Only Memory (ROM), a magnetic disk or an optical disk.
  • ROM Read Only Memory
  • the embodiments of the application are not limited to any specific hardware and software combination.
  • the embodiments of the application also provide a computer storage medium having stored thereon a computer program, the computer program being configured to execute the data scheduling method of the embodiments of the application.

Abstract

Disclosed are a method for configuring a scheduling request, a network device, a terminal device, and a computer storage medium. The method comprises: configuring for a terminal device configuration parameters of a scheduling request respectively corresponding to each carrier in at least one carrier, wherein the configuration parameters of at least one scheduling request are configured for the same carrier; and configuring for the terminal device a mapping relation between each logical channel in at least one logical channel and the configuration parameters of at least one scheduling request.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
The present application is a U.S. National Phase Entry of International PCT Application No. PCT/CN2017/101864 filed on Sep. 15, 2017, and named after “METHOD FOR CONFIGURING SCHEDULING REQUEST, NETWORK DEVICE AND TERMINAL DEVICE”, the content of which is hereby incorporated by reference in its entirety.
TECHNICAL FIELD
The application relates to the technical field of information processing, and particularly to a method for configuring a Scheduling Request (SR), a network device, a terminal device and a computer storage medium.
BACKGROUND
A Long Term Evolution (LTE) SR is a 1-bit message transmitted by a terminal on a Physical Uplink Control Channel (PUCCH) to request for an uplink grant resource. In LTE, a Media Access Control (MAC) entity corresponding to a terminal may be configured with one or more SR configurations. Multiple SR configurations are configured so that Secondary Cells (SCells) have corresponding SR configurations under a Carrier Aggregation (CA) condition. In New Radio (NR) discussions, it has been agreed that multiple SR configurations will be configured for a MAC entity of a terminal device. In such a scenario, there exists a problem to be solved of how to prevent multiple-carrier user equipment from failing to correctly send an SR due to a failure of the mapping relationship, when the SR is performed by the user equipment.
SUMMARY
For solving the foregoing technical problem, embodiments of the application provide a method for configuring an SR, a network device, a terminal device and a computer storage medium.
The embodiments of the application provide a method for configuring an SR, applied to a network device, the method including:
an SR configuration corresponding to each of at least one carrier is configured for a terminal device, at least one SR configuration being configured for the same carrier; and
a mapping relationship between each of at least one Logical Channel (LCH) and the at least one SR configuration is configured for the terminal device.
The embodiments of the application provide a method for configuring an SR, applied to a terminal device, the method including:
an SR configuration configured by a network side and corresponding to each of at least one carrier is received, at least one SR configuration being configured for a same carrier; and
a mapping relationship configured by the network side and between each of at least one LCH and the at least one SR configuration is received.
The embodiments of the application provide a network device, including:
a first configuration unit configured to configure, for a terminal device, an SR configuration corresponding to each of at least one carrier, at least one SR configuration being configured for a same carrier; and
a second configuration unit configured to configure, for the terminal device, a mapping relationship between each of at least one LCH and the at least one SR configuration.
The embodiments of the application provide a terminal device, including:
a first processing unit configured to receive an SR configuration configured by a network side and corresponding to each of at least one carrier, at least one SR configuration being configured for a same carrier; and
a second processing unit configured to receive a mapping relationship configured by the network side and between each of at least one LCH and the at least one SR configuration.
The embodiments of the application provide a network device, including a processor and a memory configured to store a computer program capable of running on the processor.
Herein, the processor may be configured to, when the computer program is running on the processor, execute the steps of the abovementioned method.
The embodiments of the application provide a terminal device, including a processor and a memory configured to store a computer program capable of running on the processor.
Herein, the processor may be configured to, when the computer program is running on the processor, execute the steps of the abovementioned method.
The embodiments of the application provide a computer storage medium having stored thereon computer-executable instructions that, when executed, implement the steps of the abovementioned method.
According to the technical solutions of the embodiments of the application, the SR configurations configured for the terminal device by a network and corresponding to different carriers may be received, and the SR configurations are mapped to the LCHs. In such a manner, the terminal device may be ensured to acquire correspondences among the LCHs, the carriers and the SR configurations, so that a corresponding resource may be timely determined during scheduling requesting, and system processing efficiency is improved.
BRIEF DESCRIPTION OF DRAWINGS
FIG. 1 is a first flowchart of a method for configuring an SR according to an embodiment of the application.
FIG. 2 is a second flowchart of a method for configuring an SR according to an embodiment of the application.
FIG. 3 is a composition structure diagram of a network device according to an embodiment of the application.
FIG. 4 is a composition structure diagram of a terminal device according to an embodiment of the application.
FIG. 5 is a schematic diagram of a hardware architecture according to an embodiment of the application.
 DETAILED DESCRIPTION
In order to make the characteristics and technical contents of the embodiments of the application understood in more detail, implementation of the embodiments of the application will be described below in combination with the drawings in detail. The drawings are only adopted for description as references and not intended to limit the embodiments of the application.
First Embodiment
The embodiment of the application provides a method for configuring an SR, which is applied to a network device and, as shown in FIG. 1, includes the following operations 101 to 102.
In 101, an SR configuration corresponding to each of at least one carrier respectively is configured for a terminal device, at least one SR configuration being configured for the same carrier.
In 102, a mapping relationship between each of at least one LCH and the at least one SR configuration is configured for the terminal device.
The embodiment may particularly be applied to a CA scenario, and under the condition of multiple carriers, multiple carriers may be configured for the same terminal device.
If the terminal device aggregates two carriers, i.e., a carrier 1 and a carrier 2, the carrier 1 may be considered as a Primary Cell (PCell), and the carrier 2 may be considered as an SCell.
In addition, the terminal device provided in the embodiment may be a terminal device supporting multiple LCHs. For example, a terminal device may support four LCHs which may be designated as {LCH1, LCH2, LCH3, LCH4} respectively.
Two manners in which the network side configures at least one SR configuration for the terminal device will be described below respectively.
A First Manner
operation that the SR configuration corresponding to each of the at least one carrier is configured for the terminal device may include that: different SR configurations are configured for different carriers, different SR configurations with the same SR configuration period being configured for different carriers.
That is, different SR configurations are configured for different carriers respectively. Descriptions are made still with a scenario with two carriers as an example. For example, for the carrier 1, two corresponding SR configurations are SR-CONFIG-1-A and SR-CONFIG-1-B respectively; and for the carrier 2, two corresponding SR configurations are SR-CONFIG-2-A and SR-CONFIG-2-B respectively. There is made such a hypothesis that SR-CONFIG-1-A and the SR-CONFIG-2-A have the same SR configuration period and, similarly, SR-CONFIG-1-B and SR-CONFIG-2-B have the same SR configuration period, as shown in Table 1.
TABLE 1
Carrier1 SR-CONFIG-1-A SR-CONFIG-1-B
Carrier2 SR-CONFIG-2-A SR-CONFIG-2-B
Correspondingly, in this manner, a method for configuring the mapping relationship between the LCH and the SR configuration includes the following operations.
The SR configurations corresponding to different carriers are selected for each LCH.
A mapping relationship between each LCH and the selected SR configurations corresponding to different carriers is established.
Specifically, SR configurations with a same SR configuration period are selected for each LCH from among the different SR configurations configured for different carriers.
That is, during LCH mapping, the SR configurations with the same configuration period and corresponding to one or more carriers are configured for the same LCH.
For example, according to a first mapping manner between SR configurations and carriers, the network maps two SR configurations corresponding to different carriers respectively to each LCH, as shown in Table 2.
TABLE 2
LCH1 SR-CONFIG-1-A; SR-CONFIG-2-A
LCH2 SR-CONFIG-1-B; SR-CONFIG-2-B
LCH3 SR-CONFIG-1-A; SR-CONFIG-2-A
LCH4 SR-CONFIG-1-B; SR-CONFIG-2-B
A second manner: the difference with the first manner is that, in this manner, it is unnecessary to set so many SR configurations, and only through relatively few SR configurations, different carriers are configured and multiple LCHs are mapped. Specific processing is as follows.
The operation that the SR configuration corresponding to each of the at least one carrier is configured for the terminal device may include the following operation.
The same SR configuration is configured for different carriers of the at least one carrier.
In this scenario, at least one PUCCH resource for different carriers may be set in each SR configuration. Moreover, different SR configurations may have different SR periods.
Specifically, the same SR configuration is configured for different carriers respectively. For example, there are totally two SR configurations: {SR-CONFIG-1, SR-CONFIG-2}.
For example, a PUCCH resource corresponding to SR-CONFIG-1 is located on the carrier 1 and the carrier 2 respectively, and a PUCCH resource corresponding to SR-CONFIG-2 is located on the carrier 1 and the carrier 2 respectively. SR-CONFIG-1 and SR-CONFIG-2 have different SR periods.
Correspondingly, the operation that the mapping relationship between each of the at least one LCH and the at least one SR configuration is configured for the terminal device may include the following operation.
An SR configuration is mapped to each LCH, the SR configuration including a PUCCH resource for the at least one carrier.
The network configures mapping between the LCH and the SR configuration. The following mapping relationship between the LCH and the SR configuration may be formed respectively based on a mapping relationship between different SR configurations and carriers: the network maps one SR configuration to each LCH, said one SR configuration including PUCCH resources of two carriers, as shown in Table 3.
TABLE 3
LCH1 SR-CONFIG-1
LCH2 SR-CONFIG-2
LCH3 SR-CONFIG-1
LCH4 SR-CONFIG-2
Thus it can be seen that, with adoption of the solution, the SR configurations configured for the terminal device by a network and corresponding to different carriers may be received, and the SR configurations are mapped to the LCHs. In such a manner, the terminal device may be ensured to acquire correspondences among the LCHs, the carriers and the SR configurations, so that a corresponding resource may be timely determined during scheduling requesting, and system processing efficiency is improved.
Second Embodiment
The embodiment of the application provides a method for configuring an SR, which is applied to a terminal device and, as shown in FIG. 2, includes the following operations 201 to 202.
In 201, an SR configuration configured by a network side and corresponding to each of at least one carrier is received, at least one SR configuration being configured for the same carrier.
In 202, a mapping relationship configured by the network side and between each of at least one LCH and the at least one SR configuration is received.
The embodiment may particularly be applied to a CA scenario, and under the condition of multiple carriers, multiple carriers may be configured for the same terminal device.
If the terminal device aggregates two carriers, i.e., a carrier 1 and a carrier 2, the carrier 1 may be considered as a PCell, and the carrier 2 may be considered as an SCell.
In addition, the terminal device provided in the embodiment may be a terminal device supporting multiple LCHs. For example, a terminal device may support four LCHs which may be designated as {LCH1, LCH2, LCH3, LCH4} respectively.
Two manners in which the network side configures at least one SR configuration for the terminal device will be described below respectively.
A First Manner
The operation that the SR configuration, configured by the network side, corresponding to each of the at least one carrier is received may include the following operation.
Different SR configurations configured for different carriers by the network side are received, different SR configurations with the same SR configuration period being configured for different carriers.
That is, different SR configurations are configured for different carriers respectively. Descriptions are made still with a scenario with two carriers as an example. For example, for the carrier 1, two corresponding SR configurations are SR-CONFIG-1-A and SR-CONFIG-1-B respectively; and for the carrier 2, two corresponding SR configurations are SR-CONFIG-2-A and SR-CONFIG-2-B respectively. There is made such a hypothesis that SR-CONFIG-1-A and the SR-CONFIG-2-A have the same SR configuration period and, similarly, SR-CONFIG-1-B and SR-CONFIG-2-B have the same SR configuration period, as shown in Table 1.
TABLE 1
Carrier1 SR-CONFIG-1-A SR-CONFIG-1-B
Carrier2 SR-CONFIG-2-A SR-CONFIG-2-B
Correspondingly, in this manner, the operation that the mapping relationship configured by the network side and between each of the at least one LCH and the at least one SR configuration is received may include the following operation.
A mapping relationship configured by the network side and between each LCH and the SR configurations corresponding to different carriers is received.
Herein, each LCH is mapped to the SR configurations with the same SR configuration period, which are configured for different carriers.
That is, during LCH mapping, the SR configurations with the same configuration period and corresponding to one or more carriers are configured for the same LCH.
For example, according to a first mapping manner between SR configurations and carriers, the network maps two SR configurations corresponding to different carriers respectively to each LCH, as shown in Table 2.
TABLE 2
LCH1 SR-CONFIG-1-A; SR-CONFIG-2-A
LCH2 SR-CONFIG-1-B; SR-CONFIG-2-B
LCH3 SR-CONFIG-1-A; SR-CONFIG-2-A
LCH4 SR-CONFIG-1-B; SR-CONFIG-2-B
A second manner: the difference with the first manner is that, in this manner, it is unnecessary to set so many SR configurations, and only through relatively few SR configurations, different carriers are configured and multiple LCHs are mapped. Specific processing is as follows.
The operation that the SR configuration, configured by the network side, corresponding to each of the at least one carrier is received may include the following operation.
A same SR configuration configured by the network side for different carriers of the at least one carrier is received.
In this scenario, at least one PUCCH resource for different carriers may be set in each SR configuration. Moreover, different SR configurations may have different SR periods.
Specifically, the same SR configuration is configured for different carriers respectively. For example, there are totally two SR configurations: {SR-CONFIG-1, SR-CONFIG-2}.
For example, a PUCCH resource corresponding to SR-CONFIG-1 is located on the carrier 1 and the carrier 2 respectively, and a PUCCH resource corresponding SR-CONFIG-2 is located on the carrier 1 and the carrier 2 respectively. SR-CONFIG-1 and SR-CONFIG-2 have different SR periods.
Correspondingly, the operation that the mapping relationship configured by the network side and between each of the at least one LCH and the at least one SR configuration is received may include the following operation.
The SR configuration configured for each LCH by the network side is received, the SR configuration including a PUCCH resource for the at least one carrier.
The network configures mapping between the LCH and the SR configuration. The following mapping relationship between the LCH and the SR configuration may be formed respectively based on a mapping relationship between different SR configurations and carriers: the network maps one SR configuration to each LCH, said one SR configuration including PUCCH resources of two carriers, as shown in Table 3.
TABLE 3
LCH1 SR-CONFIG-1
LCH2 SR-CONFIG-2
LCH3 SR-CONFIG-1
LCH4 SR-CONFIG-2
In the scenario provided in the embodiment, reporting of the SR may further be performed on a terminal device side based on a configuration condition of the network side. No matter which manner is adopted, the following processing manner is adopted when the terminal device reports the SR.
When the terminal device reports the SR, an LCH on which reporting of the SR is triggered is acquired.
The at least one SR configuration corresponding to the LCH is acquired.
A PUCCH resource nearest to a moment when reporting of the SR is triggered is selected based on a PUCCH resource corresponding to the at least one SR configuration, and an SR is transmitted on the selected PUCCH resource.
Specifically, the terminal device selects the corresponding SR configuration according to the LCH on which reporting of the SR is triggered. For example, if the reporting of the SR is triggered on an LCH1, selection is performed as follows.
For the first manner: an SR corresponding to SR-CONFIG-1-A and SR-CONFIG-2-A may be selected to be selected.
For the second manner: an SR corresponding SR-CONFIG-1 may be selected to be reported.
For the two methods, the terminal device selects a PUCCH resource nearest to a moment when reporting of the SR is triggered to transmit the SR.
Thus it can be seen that, with adoption of the solution, the SR configurations configured for the terminal device by a network and corresponding to different carriers may be received, and the SR configurations are mapped to the LCHs. In such a manner, the terminal device may be ensured to acquire correspondences among the LCHs, the carriers and the SR configurations, so that a corresponding resource may be timely determined during scheduling requesting, and system processing efficiency is improved.
Third Embodiment
The embodiment of the application provides a network device, which, as shown in FIG. 3, includes a first configuration unit 31 and a second configuration unit 32.
The first configuration unit 31 is configured to configure, for a terminal device, an SR configuration corresponding to each of at least one carrier, at least one SR configuration being configured for the same carrier.
The second configuration unit 32 is configured to configure, for the terminal device, a mapping relationship between each of at least one LCH and the at least one SR configuration.
The embodiment may particularly be applied to a CA scenario, and under the condition of multiple carriers, multiple carriers may be configured for the same terminal device.
If the terminal device aggregates two carriers, i.e., a carrier 1 and a carrier 2, the carrier 1 may be considered as a PCell, and the carrier 2 may be considered as an SCell.
In addition, the terminal device provided in the embodiment may be a terminal device supporting multiple LCHs. For example, a terminal device may support four LCHs which may be designated as {LCH1, LCH2, LCH3, LCH4} respectively.
Two manners in which the network side configures at least one SR configuration for the terminal device will be described below respectively.
A First Manner
The first configuration unit is configured to configure different SR configurations for different carriers, different SR configurations with the same SR configuration period being configured for different carriers.
That is, different SR configurations are configured for different carriers respectively. Descriptions are made still with a scenario with two carriers as an example. For example, for the carrier 1, two corresponding SR configurations are SR-CONFIG-1-A and SR-CONFIG-1-B respectively; and for the carrier 2, two corresponding SR configurations are SR-CONFIG-2-A and SR-CONFIG-2-B respectively. There is made such a hypothesis that SR-CONFIG-1-A and the SR-CONFIG-2-A have the same SR configuration period and, similarly, SR-CONFIG-1-B and SR-CONFIG-2-B have the same SR configuration period, as shown in Table 1.
TABLE 1
Carrier1 SR-CONFIG-1-A SR-CONFIG-1-B
Carrier2 SR-CONFIG-2-A SR-CONFIG-2-B
Correspondingly, in this manner, a method for configuring the mapping relationship between the LCH and the SR configuration includes the following operations.
The second configuration unit is configured to select, for each LCH, SR configurations corresponding to different carriers and establish a mapping relationship between each LCH and the selected SR configurations corresponding to different carriers.
The second configuration unit is configured to select, for each LCH, SR configurations with a same SR configuration period from among the different SR configurations configured for different carriers.
That is, during LCH mapping, the SR configurations with the same configuration period and corresponding to one or more carriers are configured for the same LCH.
For example, according to a first mapping manner between SR configurations and carriers, the network maps two SR configurations corresponding to different carriers respectively to each LCH, as shown in Table 2.
TABLE 2
LCH1 SR-CONFIG-1-A; SR-CONFIG-2-A
LCH2 SR-CONFIG-1-B; SR-CONFIG-2-B
LCH3 SR-CONFIG-1-A; SR-CONFIG-2-A
LCH4 SR-CONFIG-1-B; SR-CONFIG-2-B
A second manner: the difference with the first manner is that, in this manner, it is unnecessary to set so many SR configurations, and only through relatively few SR configurations, different carriers are configured and multiple LCHs are mapped. Specific processing is as follows.
The first configuration unit is configured to configure the same SR configuration for different carriers of the at least one carrier.
In this scenario, at least one PUCCH resource for different carriers may be set in each SR configuration. Moreover, different SR configurations may have different SR periods.
Specifically, the same SR configuration is configured for different carriers respectively. For example, there are totally two SR configurations: {SR-CONFIG-1, SR-CONFIG-2}.
For example, a PUCCH resource corresponding to SR-CONFIG-1 is located on the carrier 1 and the carrier 2 respectively, and a PUCCH resource corresponding to SR-CONFIG-2 is located on the carrier 1 and the carrier 2 respectively. SR-CONFIG-1 and SR-CONFIG-2 have different SR periods.
Correspondingly, the second configuration unit is configured to map one SR configuration to each LCH, said one SR configuration including a PUCCH resource for the at least one carrier.
The network configures mapping between the LCH and the SR configuration. The following mapping relationship between the LCH and the SR configuration may be formed respectively based on a mapping relationship between different SR configurations and carriers: the network maps one SR configuration to each LCH, said one SR configuration including PUCCH resources of two carriers, as shown in Table 3.
TABLE 3
LCH1 SR-CONFIG-1
LCH2 SR-CONFIG-2
LCH3 SR-CONFIG-1
LCH4 SR-CONFIG-2
Thus it can be seen that, with adoption of the solution, the SR configurations configured for the terminal device by a network and corresponding to different carriers may be received, and the SR configurations are mapped to the LCHs. In such a manner, the terminal device may be ensured to acquire correspondences among the LCHs, the carriers and the SR configurations, so that a corresponding resource may be timely determined during scheduling requesting, and system processing efficiency is improved.
Fourth Embodiment
The embodiment of the application provides a terminal device, which, as shown in FIG. 4, includes a first processing unit 41 and a second processing unit 42.
The first processing unit 41 is configured to receive an SR configuration configured by a network side and corresponding to each of at least one carrier, at least one SR configuration being configured for the same carrier.
The second processing unit 42 is configured to receive a mapping relationship configured by the network side and between each of at least one LCH and the at least one SR configuration.
The embodiment may particularly be applied to a CA scenario, and under the condition of multiple carriers, multiple carriers may be configured for the same terminal device.
If the terminal device aggregates two carriers, i.e., a carrier and a carrier 2, the carrier 1 may be considered as a PCell, and the carrier 2 may be considered as an SCell.
In addition, the terminal device provided in the embodiment may be a terminal device supporting multiple LCHs. For example, a terminal device may support four LCHs which may be designated as {LCH1, LCH2, LCH3, LCH4} respectively.
Two manners in which the network side configures at least one SR configuration for the terminal device will be described below respectively.
A First Manner
The first processing unit is configured to receive different SR configurations configured for different carriers by the network side, different SR configurations with the same SR configuration period being configured for different carriers.
That is, different SR configurations are configured for different carriers respectively. Descriptions are made still with a scenario with two carriers as an example. For example, for the carrier 1, two corresponding SR configurations are SR-CONFIG-1-A and SR-CONFIG-1-B respectively; and for the carrier 2, two corresponding SR configurations are SR-CONFIG-2-A and SR-CONFIG-2-B respectively. There is made such a hypothesis that SR-CONFIG-1-A and the SR-CONFIG-2-A have the same SR configuration period and, similarly, SR-CONFIG-1-B and SR-CONFIG-2-B have the same SR configuration period, as shown in Table 1.
TABLE 1
Carrier1 SR-CONFIG-1-A SR-CONFIG-1-B
Carrier2 SR-CONFIG-2-A SR-CONFIG-2-B
Correspondingly, in this manner, the second processing unit is configured to receive a mapping relationship configured by the network side and between each LCH and the SR configurations corresponding to different carriers.
Herein, each LCH is mapped to the SR configurations with the same SR configuration period, which are configured for different carriers.
That is, during LCH mapping, the SR configurations with the same configuration period and corresponding to one or more carriers are configured for the same LCH.
For example, according to a first mapping manner SR configurations and carriers, the network maps two SR configurations corresponding to different carriers respectively to each LCH, as shown in Table 2.
TABLE 2
LCH1 SR-CONFIG-1-A; SR-CONFIG-2-A
LCH2 SR-CONFIG-1-B; SR-CONFIG-2-B
LCH3 SR-CONFIG-1-A; SR-CONFIG-2-A
LCH4 SR-CONFIG-1-B; SR-CONFIG-2-B
A second manner: the difference with the first manner is that, in this manner, it is unnecessary to set so many SR configurations, and only through relatively few SR configurations, different carriers are configured and multiple LCHs are mapped. Specific processing is as follows.
The first processing unit is configured to receive the same SR configuration configured by the network side for different carriers of the at least one carrier.
In this scenario, at least one PUCCH resource for different carriers may be set in each SR configuration. Moreover, different SR configurations may have different SR periods.
Specifically, the same SR configuration is configured for different carriers respectively. For example, there are totally two SR configurations: {SR-CONFIG-1, SR-CONFIG-2}.
For example, a PUCCH resource corresponding to SR-CONFIG-1 is located on the carrier 1 and the carrier 2 respectively, and a PUCCH resource corresponding to SR-CONFIG-2 is located on the carrier 1 and the carrier 2 respectively. SR-CONFIG-1 and SR-CONFIG-2 have different SR periods.
Correspondingly, the second processing unit is configured to receive the SR configuration configured for each LCH by the network side, the SR configuration including a PUCCH resource for the at least one carrier.
The network configures mapping between the LCH and the SR configuration. The following mapping relationship between the LCH and the SR configuration may be formed respectively based on a mapping relationship between different SR configurations and carriers: the network maps one SR configuration to each LCH, said one SR configuration including PUCCH resources of two carriers, as shown in Table 3.
TABLE 3
LCH1 SR-CONFIG-1
LCH2 SR-CONFIG-2
LCH3 SR-CONFIG-1
LCH4 SR-CONFIG-2
In the scenario provided in the embodiment, reporting of the SR may further be performed on a terminal device side based on a configuration condition of the network side. No matter which manner is adopted, the following processing manner is adopted when the terminal device reports the SR.
The terminal device may further include a transmission unit 43.
The transmission unit 43 is configured to, when the SR is reported, acquire an LCH on which reporting of the SR is triggered, acquire the at least one SR configuration corresponding to the acquired LCH, select, based on a PUCCH resource corresponding to the at least one SR configuration, a PUCCH resource nearest to a moment when reporting of the SR is triggered, and transmit an SR on the selected PUCCH resource.
Specifically, the terminal device selects the corresponding SR configuration according to the LCH on which reporting of the SR is triggered. For example, if the reporting of the SR is triggered on an LCH1, selection is performed as follows.
For the first manner: an SR corresponding to SR-CONFIG-1-A and SR-CONFIG-2-A may be selected to be selected.
For the second manner: an SR corresponding SR-CONFIG-1 may be selected to be reported.
For the two methods, the terminal device selects a PUCCH resource nearest to a moment when reporting of the SR is triggered to transmit the SR.
Thus it can be seen that, with adoption of the solution, the SR configurations configured for the terminal device by a network and corresponding to different carriers may be received, and the SR configurations are mapped to the LCHs. In such a manner, the terminal device may be ensured to acquire correspondences among the LCHs, the carriers and the SR configurations, so that a corresponding resource may be timely determined during scheduling requesting, and system processing efficiency is improved.
The embodiments of the application also provide a hardware composition architecture of a terminal device, which, as shown in FIG. 5, includes at least one processor 51, a memory 52 and at least one network interface 53. Each component is coupled together through a bus system 54. It can be understood that the bus system 54 is configured to implement connection communication between these components. The bus system 54 includes a data bus and further includes a power bus, a control bus and a state signal bus. However, for clear description, various buses in FIG. 5 are marked as the bus system 54.
It can be understood that the memory 52 in the embodiment of the application may be a volatile memory or a nonvolatile memory, or may include both the volatile and nonvolatile memories.
In some implementation modes, the memory 52 stores the following elements, executable modules or data structures, or a subset thereof or an extended set thereof:
an operating system 521 and an application program 522.
Herein, the processor 51 is configured to configure, for each terminal device, an SR configuration corresponding to each of at least one carrier, at least one SR configuration being configured for the same carrier; and
configure, for the terminal device, a mapping relationship between each of at least one LCH and the at least one SR configuration.
Specifically, the terminal device may process the steps of the method in the first embodiment and will not be elaborated herein.
The embodiments of the application provide a terminal device, which includes a processor and a memory configured to store a computer program capable of running on the processor.
Herein, the processor is configured to, when the computer program is running on the processor, execute the steps of the method in the second embodiment. No more elaborations will be made herein.
An embodiment of the application provides a computer storage medium having stored thereon computer-executable instructions that, when executed, implement the steps of the method in the first or second embodiment.
When being implemented in form of software functional module and sold or used as an independent product, the device of the embodiments of the application may also be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of the embodiments of the application substantially or parts making contributions to the conventional art may be embodied in form of software product, and the computer software product is stored in a storage medium, including a plurality of instructions configured to enable a computer device (which may be a personal computer, a server, a network device or the like) to execute all or part of the method in each embodiment of the application. The storage medium includes: various media capable of storing program codes such as a U disk, a mobile hard disk, a Read Only Memory (ROM), a magnetic disk or an optical disk. As a consequence, the embodiments of the application are not limited to any specific hardware and software combination.
Correspondingly, the embodiments of the application also provide a computer storage medium having stored thereon a computer program, the computer program being configured to execute the data scheduling method of the embodiments of the application.
Although the preferred embodiments of the application have been disclosed for the exemplary purposes, those skilled in the art may realize that it is also possible to make various improvements, additions and replacements. Therefore, the scope of the application should not be limited to the abovementioned embodiments.

Claims (14)

The invention claimed is:
1. A method for configuring a Scheduling Request (SR) applied to a network device, the method comprising:
configuring, for a terminal device, an SR configuration corresponding to each of at least one carrier, at least one SR configuration being configured for a same carrier; and
configuring, for the terminal device, a mapping relationship between each of at least one Logical Channel (LCH) and the at least one SR configuration,
wherein configuring, for the terminal device, the SR configuration corresponding to each of the at least one carrier comprises:
configuring different SR configurations for different carriers, different SR configurations with a same SR configuration period being configured for different carriers,
wherein configuring, for the terminal device, the mapping relationship between each of the at least one LCH and the at least one SR configuration comprises:
selecting, for each LCH, SR configurations corresponding to different carriers; and
establishing a mapping relationship between each LCH and the selected SR configurations corresponding to different carriers.
2. The method of claim 1, wherein selecting, for each LCH, the SR configurations corresponding to different carriers comprises:
selecting, for each LCH, SR configurations with a same SR configuration period from among the different SR configurations configured for different carriers.
3. A method for configuring a Scheduling Request (SR) applied to a terminal device, the method comprising:
receiving an SR configuration configured by a network side and corresponding to each of at least one carrier, at least one SR configuration being configured for a same carrier; and
receiving a mapping relationship configured by the network side and between each of at least one Logical Channel (LCH) and the at least one SR configuration,
wherein the method further comprises:
when the terminal device reports the SR, acquiring an LCH on which reporting of the SR is triggered;
acquiring the at least one SR configuration corresponding to the acquired LCH; and
selecting, based on a Physical Uplink Control Channel (PUCCH) resource corresponding to the at least one SR configuration, a PUCCH resource nearest to a moment when the reporting of the SR is triggered, and transmitting the SR on the selected PUCCH resource,
wherein the mapping relationship between each of the at least one LCH and the at least one SR configuration is configured by:
selecting, for each LCH, SR configurations corresponding to different carriers; and
establishing the mapping relationship between each LCH and the selected SR configurations corresponding to different carriers.
4. The method of claim 3, wherein receiving the SR configuration configured by the network side and corresponding to each of the at least one carrier comprises:
receiving different SR configurations configured for different carriers by the network side, different SR configurations with a same SR configuration period being configured for different carriers.
5. The method of claim 4, wherein receiving the mapping relationship configured by the network side and between each of the at least one LCH and the at least one SR configuration comprises:
receiving a mapping relationship configured by the network side and between each LCH and the SR configurations corresponding to different carriers,
wherein each LCH is mapped to the SR configurations with the same SR configuration period, which are configured for different carriers.
6. The method of claim 3, wherein receiving the SR configuration configured by the network side and corresponding to each of the at least one carrier comprises:
receiving a same SR configuration configured by the network side for different carriers of the at least one carrier.
7. The method of claim 6, wherein receiving the mapping relationship configured by the network side and between each of the at least one LCH and the at least one SR configuration comprises:
receiving one SR configuration configured for each LCH by the network side, said one SR configuration comprising a PUCCH resource for the at least one carrier.
8. A network device, comprising:
a memory storing processor-executable instructions; and
a processor arranged to execute the stored processor-executable instructions to perform operations of:
configuring, for a terminal device, a Scheduling Request (SR) configuration corresponding to each of at least one carrier, at least one SR configuration being configured for a same carrier; and
configuring, for the terminal device, a mapping relationship between each of at least one Logical Channel (LCH) and the at least one SR configuration,
wherein configuring, for the terminal device, the SR configuration corresponding to each of the at least one carrier comprises:
configuring different SR configurations for different carriers, different SR configurations with a same SR configuration period being configured for different carriers,
wherein configuring, for the terminal device, the mapping relationship between each of the at least one LCH and the at least one SR configuration comprises:
selecting, for each LCH, SR configurations corresponding to different carriers; and
establishing a mapping relationship between each LCH and the selected SR configurations corresponding to different carriers.
9. The network device of claim 8, wherein configuring, for the terminal device, the mapping relationship between each of the at least one LCH and the at least one SR configuration comprises:
selecting, for each LCH, SR configurations corresponding to different carriers; and establishing a mapping relationship between each LCH and the selected SR configurations corresponding to different carriers.
10. The network device of claim 9, wherein selecting, for each LCH, the SR configurations corresponding to different carriers comprises:
selecting, for each LCH, SR configurations with a same SR configuration period from among the different SR configurations configured for different carriers.
11. A terminal device, comprising:
a memory storing processor-executable instructions; and
a processor arranged to execute the stored processor-executable instructions to perform operations of:
receiving a Scheduling Request (SR) configuration configured by a network side and corresponding to each of at least one carrier, at least one SR configuration being configured for a same carrier; and
receiving a mapping relationship configured by the network side and between each of at least one Logical Channel (LCH) and the at least one SR configuration, wherein the processor is arranged to execute the stored processor-executable instructions to further perform operations of:
when the SR is reported, acquiring an LCH on which reporting of the SR is triggered;
acquiring the at least one SR configuration corresponding to the acquired LCH; and
selecting, based on a Physical Uplink Control Channel (PUCCH) resource corresponding to the at least one SR configuration, a PUCCH resource nearest to a moment when the reporting of the SR is triggered, and transmit the SR on the selected PUCCH resource,
wherein configuring, for the terminal device, the mapping relationship between each of the at least one LCH and the at least one SR configuration comprises:
selecting, for each LCH, SR configurations corresponding to different carriers; and
establishing a mapping relationship between each LCH and the selected SR configurations corresponding to different carriers.
12. The terminal device of claim 11, wherein receiving the SR configuration configured by the network side and corresponding to each of the at least one carrier comprises:
receiving different SR configurations configured for different carriers by the network side, different SR configurations with a same SR configuration period being configured for different carriers.
13. The terminal device of claim 11, wherein receiving the SR configuration configured by the network side and corresponding to each of the at least one carrier comprises:
receiving a same SR configuration configured by the network side for different carriers of the at least one carrier.
14. The terminal device of claim 13, wherein receiving the mapping relationship configured by the network side and between each of the at least one LCH and the at least one SR configuration comprises:
receiving one SR configuration configured for each LCH by the network side, said one SR configuration comprising a PUCCH resource for the at least one carrier.
US16/646,764 2017-09-15 2017-09-15 Method for configuring scheduling request, network device and terminal device Active 2037-11-22 US11224062B2 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/101864 WO2019051765A1 (en) 2017-09-15 2017-09-15 Method for configuring scheduling request, network device and terminal device

Publications (2)

Publication Number Publication Date
US20200275467A1 US20200275467A1 (en) 2020-08-27
US11224062B2 true US11224062B2 (en) 2022-01-11

Family

ID=65723149

Family Applications (1)

Application Number Title Priority Date Filing Date
US16/646,764 Active 2037-11-22 US11224062B2 (en) 2017-09-15 2017-09-15 Method for configuring scheduling request, network device and terminal device

Country Status (7)

Country Link
US (1) US11224062B2 (en)
EP (1) EP3684022B1 (en)
JP (1) JP2020537374A (en)
KR (1) KR20200054283A (en)
CN (1) CN110710179A (en)
AU (1) AU2017431900A1 (en)
WO (1) WO2019051765A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111108796B (en) * 2017-09-28 2024-04-05 三星电子株式会社 Method and network node for performing data transmission and measurement on multiple bandwidth parts

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140010182A1 (en) * 2010-12-30 2014-01-09 Zte Corporation Method and Device for Data Transmission
CN104811892A (en) 2014-01-29 2015-07-29 中兴通讯股份有限公司 Resource allocation method, device and system
CN105075146A (en) 2013-01-07 2015-11-18 三星电子株式会社 Methods and apparatus for inter-enb carrier aggregation
US20160066328A1 (en) * 2013-05-10 2016-03-03 Huawei Technologies Co., Ltd. Scheduling method, user equipment, and base station
CN107040351A (en) 2016-02-03 2017-08-11 中兴通讯股份有限公司 A kind of method and device for realizing carrier aggregation
US20180295540A1 (en) * 2017-04-10 2018-10-11 Qualcomm Incorporated Transmission of buffer status reports on multiple component carriers
US20190098626A1 (en) * 2016-04-26 2019-03-28 Lg Electronics Inc. Method and apparatus for configuring frame structure for new radio access technology in wireless communication system
US20190289513A1 (en) * 2017-11-16 2019-09-19 Comcast Cable Communications, Llc Power Control for Bandwidth Part Switching
US20200059953A1 (en) * 2017-11-15 2020-02-20 Telefonaktiebolaget Lm Ericsson (Publ) Method and Apparatus for Uplink Transmission
US20200137528A1 (en) * 2016-09-29 2020-04-30 Zte Corporation Multicast service service information and service information change notification method and apparatus
US20200213066A1 (en) * 2017-08-11 2020-07-02 Vivo Mobile Communication Co.,Ltd. Bandwidth part configuration method, network device and user equipment
US20200267594A1 (en) * 2017-09-29 2020-08-20 Huawei Technologies Co., Ltd. Scheduling request processing method and terminal device
US20200288494A1 (en) * 2017-09-28 2020-09-10 Apple Inc. Communication network apparatus for uplink scheduling
US20200305181A1 (en) * 2017-09-28 2020-09-24 Vivo Mobile Communication Co., Ltd. Scheduling request processing method and user equipment

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140010182A1 (en) * 2010-12-30 2014-01-09 Zte Corporation Method and Device for Data Transmission
CN105075146A (en) 2013-01-07 2015-11-18 三星电子株式会社 Methods and apparatus for inter-enb carrier aggregation
US20160066328A1 (en) * 2013-05-10 2016-03-03 Huawei Technologies Co., Ltd. Scheduling method, user equipment, and base station
CN104811892A (en) 2014-01-29 2015-07-29 中兴通讯股份有限公司 Resource allocation method, device and system
CN107040351A (en) 2016-02-03 2017-08-11 中兴通讯股份有限公司 A kind of method and device for realizing carrier aggregation
US20190098626A1 (en) * 2016-04-26 2019-03-28 Lg Electronics Inc. Method and apparatus for configuring frame structure for new radio access technology in wireless communication system
US20200137528A1 (en) * 2016-09-29 2020-04-30 Zte Corporation Multicast service service information and service information change notification method and apparatus
US20180295540A1 (en) * 2017-04-10 2018-10-11 Qualcomm Incorporated Transmission of buffer status reports on multiple component carriers
US20200213066A1 (en) * 2017-08-11 2020-07-02 Vivo Mobile Communication Co.,Ltd. Bandwidth part configuration method, network device and user equipment
US20200288494A1 (en) * 2017-09-28 2020-09-10 Apple Inc. Communication network apparatus for uplink scheduling
US20200305181A1 (en) * 2017-09-28 2020-09-24 Vivo Mobile Communication Co., Ltd. Scheduling request processing method and user equipment
US20200267594A1 (en) * 2017-09-29 2020-08-20 Huawei Technologies Co., Ltd. Scheduling request processing method and terminal device
US20200059953A1 (en) * 2017-11-15 2020-02-20 Telefonaktiebolaget Lm Ericsson (Publ) Method and Apparatus for Uplink Transmission
US20190289513A1 (en) * 2017-11-16 2019-09-19 Comcast Cable Communications, Llc Power Control for Bandwidth Part Switching

Non-Patent Citations (18)

* Cited by examiner, † Cited by third party
Title
Asustek. Consideration on multiple SR configurations. 3GPP TSG-RAN WG2 NR Ad Hoc #2 R2-1706932. Jun. 29, 2017(Jun. 29, 2017), entire document.
First Office Action of the Chinese application No. 201780091671.5, dated Jul. 2, 2021. 12 pages with English translation.
First Office Action of the European application No. 17925009.7, dated Jan. 22, 2021.
HTC: "Discussion on LCG and SR configuration", 3GPP DRAFT; R2-1709420, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Berlin, Germany; 20170821 - 20170825, R2-1709420, 20 August 2017 (2017-08-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051319148
HTC: "Discussion on LCG and SR configuration", 3GPP Draft; R2-1709420, 3rd Generation PartnershipProject(3GPP), Mobile Competence Centre; 650, Route des Lucioles; F-06921 Sophia-Antipolis Cedex; France vol. RAN WG2, No. Berlin, Germany; Aug. 21, 2017-Aug. 25, 2017 Aug. 20, 2017(Aug. 20, 2017), XP051319148.
INTEL CORPORATION: "Handling of multiple SR configurations", 3GPP DRAFT; R2-1708789, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, R2-1708789 multiple SRs, 25 August 2017 (2017-08-25), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 4, XP051318593
Intel Corporation: "Handling of multiple SR configurations", 3GPP Draft; R2-1708789 Multiple SRS, SRD Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route des Lucioles; F-06921 Sophia-Antipolis Cedex; France vol. RAN WG2, No. Berlin, Germany; Aug. 21, 2017-Aug. 25, 2017 Aug. 20, 2017(Aug. 20, 2017), XP051318593.
International Search Report in the international application No. PCT/CN2017/101864, dated May 30, 2018.
Mediatek Inc. SR design for multiple numerologies. 3GPP TSG-RAN WG2 NR Ad Hoc #2 R2-1707267. Jun. 29, 2017(Jun. 29, 2017), sections 1 and 2.
NEC. SR on PUCCH SCell. 3GPP TSG RAN WG2 Meeting #89b R2-151430. Apr. 24, 2015 (Apr. 24, 2015), entire document.
Second Office Action of the European application No. 17925009.7, dated Jul. 19, 2021. 7 pages.
Supplementary International Search Report in the international application No. PCT/CN2017/101864, dated Dec. 4, 2019.
VICE-CHAIRWOMAN (INTERDIGITAL): "Report from NR User Plane Break-Out Session", 3GPP DRAFT; NR-UP-BREAK-OUT CHAIR NOTES-2017-06-29_18-30, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Quingdao, China; 20170627 - 20170629, NR-UP-break-out chair notes-2017-06-29_18-30, 29 June 2017 (2017-06-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051307576
Vice-Chairwoman (Interdigital): "Report from NR User Plane Break-Out Session", 3GPP Draft; NR-Up-Break-Out Chair Notes—Jun. 29, 2017_18-30, 3rd Generation Partnership Project(3GPP), Mobile Competence Centre; 650, Route des Lucioles; F-06921 Sophia-Antipolis Cedex; France vol. Ran WG2, No. Quingdao, China; Jun. 27, 2017-Jun. 29, 2017 Jun. 29, 2017 (Jun. 29, 2017), XP051307576.
Written Opinion of the International Search Authority in the international application No. PCT/CN2017/101864, dated May 30, 2018.
ZTE. Consideration on the SR in NR. 3GPP TSG-RAN WG2 #99 R2-1708146. Aug. 25, 2017 (Aug. 25, 2017), sections 1 and 2.
ZTE: "Consideration on the SR in NR", 3GPP DRAFT; R2-1706641 CONSIDERATION ON THE SR IN NR, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Qingdao, China; 20170627 - 20170629, R2-1706641 Consideration on the SR in NR, 26 June 2017 (2017-06-26), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051301143
ZTE:"Consideration on the SR in NR", 3GPP DRAFT;R2-1706641 Consideration on the SR in NR, 3rd Generation Partnership Project (3GPP), Mobilecompetence Centre; 650, Route des Lucioles; F-06921 Sophia-Antipolis Cedex; France vol. RAN WG2, No. Qingdao, China Jun. 27, 2017-Jun. 29, 2017; Jun. 26, 2017(Jun. 26, 2017), XP051301143.

Also Published As

Publication number Publication date
CN110710179A (en) 2020-01-17
US20200275467A1 (en) 2020-08-27
EP3684022B1 (en) 2022-12-14
EP3684022A1 (en) 2020-07-22
JP2020537374A (en) 2020-12-17
WO2019051765A1 (en) 2019-03-21
KR20200054283A (en) 2020-05-19
AU2017431900A1 (en) 2020-05-07

Similar Documents

Publication Publication Date Title
US10440706B2 (en) Systems and methods for PUCCH resource allocation and HARQ-ACK reporting with processing time reduction
US11310785B2 (en) Channel transmission method, terminal device, and network device
US10834633B2 (en) Transport block generation method and apparatus
US20170019915A1 (en) User equipments, base stations and methods for license assisted access (laa)
US11582011B2 (en) Method for configuring scheduling request, network device and terminal device
US11388702B2 (en) Resource determining method, apparatus, network element, and system
US20220182899A1 (en) Pucch transmission method, user equipment, and network device
CN110505711B (en) Method, device, apparatus and medium for processing scheduling request
US20220070895A1 (en) Information transmission method, apparatus and device
US20220361024A1 (en) Method for indicating to skip pdcch monitoring and apparatus
US11178622B2 (en) Data processing method, terminal, and base station
US20230318689A1 (en) Information indication method, node, and storage medium
US20230299918A1 (en) Method for monitoring control channels and determining transmission configuration indication, and terminal
US20230044303A1 (en) Uplink transmission sending method and device, uplink transmission receiving method and device, terminal, service node, and medium
US9564995B2 (en) Retransmission method for time division duplexing self-adaptive frame structure, and network side device
US20220039075A1 (en) Communication method and apparatus
US11224062B2 (en) Method for configuring scheduling request, network device and terminal device
KR20200083948A (en) Resource indication method, user device, network device and computer storage medium
WO2019128805A1 (en) Method and device for transmitting and receiving phase tracking reference signal
EP3627892A1 (en) Method for activating and deactivating cell, terminal equipment and computer storage medium
US20240129918A1 (en) Cooperative communication implementation method, device, and storage medium
US20230199777A1 (en) Method for transmitting uplink control information, communication apparatus, and related device
KR20230150758A (en) Device and Method for Handling a Multi-cell Scheduling

Legal Events

Date Code Title Description
AS Assignment

Owner name: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD., CHINA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TANG, HAI;REEL/FRAME:052098/0104

Effective date: 20200305

FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: AWAITING TC RESP., ISSUE FEE NOT PAID

STPP Information on status: patent application and granting procedure in general

Free format text: AWAITING TC RESP., ISSUE FEE NOT PAID

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCF Information on status: patent grant

Free format text: PATENTED CASE