CN117500072A - Scheduling request transmission method and device, terminal equipment, network equipment and chip - Google Patents
Scheduling request transmission method and device, terminal equipment, network equipment and chip Download PDFInfo
- Publication number
- CN117500072A CN117500072A CN202210873196.XA CN202210873196A CN117500072A CN 117500072 A CN117500072 A CN 117500072A CN 202210873196 A CN202210873196 A CN 202210873196A CN 117500072 A CN117500072 A CN 117500072A
- Authority
- CN
- China
- Prior art keywords
- scheduling request
- data characteristic
- different
- data
- resource
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 92
- 230000005540 biological transmission Effects 0.000 title claims abstract description 69
- 239000000872 buffer Substances 0.000 claims description 88
- 238000004891 communication Methods 0.000 claims description 63
- 238000004590 computer program Methods 0.000 claims description 26
- 125000004122 cyclic group Chemical group 0.000 claims description 25
- 230000010363 phase shift Effects 0.000 claims description 14
- 238000011084 recovery Methods 0.000 claims description 7
- 230000009286 beneficial effect Effects 0.000 abstract description 9
- 239000012464 large buffer Substances 0.000 description 30
- 230000006870 function Effects 0.000 description 25
- 238000012545 processing Methods 0.000 description 25
- 230000003139 buffering effect Effects 0.000 description 13
- 238000001228 spectrum Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 9
- 102100022734 Acyl carrier protein, mitochondrial Human genes 0.000 description 8
- 101000678845 Homo sapiens Acyl carrier protein, mitochondrial Proteins 0.000 description 8
- 238000007726 management method Methods 0.000 description 7
- 238000011144 upstream manufacturing Methods 0.000 description 7
- 235000019800 disodium phosphate Nutrition 0.000 description 6
- 230000006978 adaptation Effects 0.000 description 4
- 230000001427 coherent effect Effects 0.000 description 4
- 230000009977 dual effect Effects 0.000 description 4
- 230000007774 longterm Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000013468 resource allocation Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 230000011664 signaling Effects 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 2
- 230000003111 delayed effect Effects 0.000 description 2
- 238000006073 displacement reaction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 2
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 1
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000013144 data compression Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The application discloses a scheduling request transmission method and device, terminal equipment, network equipment and a chip; the method comprises the following steps: the terminal equipment sends a scheduling request which is used for reporting the data characteristic requirement of the service; correspondingly, the network device receives the scheduling request. The method and the device report the data characteristic requirements of the service to the network through the scheduling request, so that the enhancement of the scheduling request is realized. Therefore, the network can decide how to better schedule uplink resources required by uplink data of the service according to the data characteristic requirements, so that the decision made can be beneficial to avoiding the uplink data from exceeding the time delay requirements, meeting the data volume requirements of the uplink data, improving the reliability of the uplink data transmission and the like.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a method and apparatus for transmitting a scheduling request, a terminal device, a network device, and a chip.
Background
Currently, the standard protocol specified by the third generation partnership project organization (3rd Generation Partnership Project,3GPP) involves a scheduling request (scheduling request). The SR may be used to request uplink resources required for uplink data, and the SR needs to be sent on the SR resources.
However, there are problems with the uplink resources currently requested by SR, for example, SR cannot tell when the requested uplink resources can be provided, so that the uplink data of the terminal device may exceed the latency requirement, and even affect the performance of the previously transmitted data packet; the SR cannot inform the data amount of the requested uplink resource that needs to be carried, and influences the decision of the network device for scheduling the resource, so that the uplink resource scheduled by the network device may not meet the data amount requirement of the uplink data, and the reliability of the uplink data transmission is reduced. Therefore, there is a need for further enhancements to the SR to address the above issues.
Disclosure of Invention
The application provides a scheduling request transmission method and device, terminal equipment, network equipment and a chip, so as to expect to realize scheduling request enhancement.
In a first aspect, a method for transmitting a scheduling request according to the present application includes:
and sending a scheduling request, wherein the scheduling request is used for reporting the data characteristic requirement of the service.
Therefore, the data characteristic requirements of the service are reported to the network through the scheduling request, and the scheduling request enhancement is realized. In this way, the network can decide how to better schedule the uplink resources required by the uplink data of the service according to the data characteristic requirement, so that the decision made can be beneficial to avoiding the uplink data from exceeding the time delay requirement, meeting the data quantity requirement of the uplink data, and the like, thereby improving the reliability of the uplink data transmission, and the like.
In a second aspect, a method for transmitting a scheduling request according to the present application includes:
and receiving a scheduling request, wherein the scheduling request is used for reporting the data characteristic requirement of the service.
In a third aspect, a scheduling request transmission apparatus according to the present application includes:
and the sending unit is used for sending a scheduling request, wherein the scheduling request is used for reporting the data characteristic requirement of the service.
A fourth aspect is a scheduling request transmission apparatus according to the present application, including:
and the receiving unit is used for receiving a scheduling request, wherein the scheduling request is used for reporting the data characteristic requirement of the service.
In a fifth aspect, the steps in the method as designed in the first aspect are applied to a terminal device or a terminal device.
In a sixth aspect, the steps in the method according to the second aspect are applied in a network device or a network device.
A seventh aspect is a terminal device according to the present application, comprising a processor, a memory and a computer program or instructions stored on the memory, wherein the processor executes the computer program or instructions to implement the steps in the method designed in the first aspect.
An eighth aspect is a network device according to the present application, including a processor, a memory, and a computer program or instructions stored on the memory, where the processor executes the computer program or instructions to implement the steps in the method designed in the second aspect.
A ninth aspect is a chip of the present application, including a processor and a communication interface, where the processor performs the steps in the method designed in the first aspect or the second aspect.
In a tenth aspect, the present application is a chip module, including a transceiver component and a chip, where the chip includes a processor, and the processor executes the steps in the method designed in the first aspect or the second aspect.
An eleventh aspect is a computer readable storage medium of the present application, in which a computer program or instructions are stored, which when executed, implement the steps in the method devised in the first aspect or the second aspect.
A twelfth aspect is a computer program product according to the present application, comprising a computer program or instructions, wherein the computer program or instructions, when executed, implement the steps of the method devised in the first aspect or the second aspect.
A thirteenth aspect is a communication system of the present application, including the terminal device in the seventh aspect and the network device in the eighth aspect.
The technical effects of the second to thirteenth aspects may be seen by the technical effects of the first aspect, and are not described here again.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments or the prior art will be briefly described below.
Fig. 1 is a schematic architecture diagram of a communication system according to an embodiment of the present application;
fig. 2 is a flow chart of a scheduling request transmission method according to an embodiment of the present application;
fig. 3 is a functional unit block diagram of a scheduling request transmission apparatus according to an embodiment of the present application;
fig. 4 is a functional unit block diagram of still another scheduling request transmitting apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a terminal device according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a network device according to an embodiment of the present application.
Detailed Description
It should be understood that the terms "first," "second," and the like, as used in embodiments of the present application, are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, software, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.
Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.
In the embodiment of the application, "and/or", the association relation of the association objects is described, which means that three relations can exist. For example, a and/or B may represent three cases: a alone; both A and B are present; b alone. Wherein A, B can be singular or plural.
In the embodiment of the present application, the symbol "/" may indicate that the associated object is an or relationship. In addition, the symbol "/" may also denote a divisor, i.e. performing a division operation. For example, A/B may represent A divided by B.
In the embodiments of the present application, "at least one item(s)" or the like means any combination of these items, including any combination of single item(s) or plural item(s), meaning one or more, and plural means two or more. For example, at least one (one) of a, b or c may represent the following seven cases: a, b, c, a and b, a and c, b and c, a, b and c. Wherein each of a, b, c may be an element or a set comprising one or more elements.
The 'equal' in the embodiment of the application can be used with the greater than the adopted technical scheme, can also be used with the lesser than the adopted technical scheme, and is applicable to the lesser than the adopted technical scheme. When the combination is equal to or greater than the combination, the combination is not less than the combination; when the value is equal to or smaller than that used together, the value is not larger than that used together.
In the embodiments of the present application, "of", "corresponding" and "indicated" may be used in a mixed manner. It should be noted that the meaning of what is meant is consistent when de-emphasizing the differences.
In the embodiment of the present application, "connection" refers to various connection modes such as direct connection or indirect connection, so as to implement communication between devices, which is not limited in any way.
The "network" in the embodiments of the present application may be expressed as the same concept as the "system", i.e. the communication system is a communication network.
The "correspondence" in the embodiments of the present application may be mixed with "association" or "mapping" or the like sometimes. It should be noted that the meaning of what is meant is consistent when de-emphasizing the differences.
The "ignore" in the embodiments of the present application may be sometimes mixed with "skip", "cancel" or "release", etc. It should be noted that the meaning of what is meant is consistent when de-emphasizing the differences.
The following describes related content, concepts, meanings, technical problems, technical solutions, advantageous effects and the like related to the embodiments of the present application.
1. Communication system, terminal device and network device
1. Communication system
The technical solution of the embodiment of the application can be applied to various communication systems, for example: general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, long term evolution advanced (Advanced Long Term Evolution, LTE-a) system, new Radio (NR) system, evolution system of NR system, LTE-based Access to Unlicensed Spectrum on unlicensed spectrum (LTE-U) system, NR-based Access to Unlicensed Spectrum on unlicensed spectrum (NR-U) system, non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, wi-Fi), 6th Generation (6 th-Generation, 6G) communication system, or other communication system, etc.
It should be noted that, the number of connections supported by the conventional communication system is limited and easy to implement. However, with the development of communication technology, the communication system may support not only a conventional communication system, but also, for example, a device-to-device (D2D) communication, a machine-to-machine (machine to machine, M2M) communication, a machine type communication (machine type communication, MTC), an inter-vehicle (vehicle to vehicle, V2V) communication, an internet of vehicles (vehicle to everything, V2X) communication, a narrowband internet of things (narrow band internet of things, NB-IoT) communication, and so on, so the technical solution of the embodiment of the present application may also be applied to the above-described communication system.
In addition, the technical solution of the embodiment of the present application may be applied to beamforming (beamforming), carrier aggregation (carrier aggregation, CA), dual connectivity (dual connectivity, DC), or independent (SA) deployment scenarios, and the like.
In this embodiment of the present application, the spectrum used for communication between the terminal device and the network device, or the spectrum used for communication between the terminal device and the terminal device may be an authorized spectrum or an unlicensed spectrum, which is not limited. In addition, unlicensed spectrum may be understood as shared spectrum, and licensed spectrum may be understood as unshared spectrum.
Since the embodiments of the present application describe various embodiments in connection with terminal devices and network devices, the terminal devices and network devices involved will be specifically described below.
2. Terminal equipment
In this embodiment of the present application, the terminal device may be a device with a transceiver function, and may also be referred to as a terminal, a User Equipment (UE), a remote terminal device (remote UE), a relay device (relay UE), an access terminal device, a subscriber unit, a subscriber station, a mobile station, a remote station, a mobile device, a user terminal device, an intelligent terminal device, a wireless communication device, a user agent, or a user equipment. The relay device is a terminal device capable of providing a relay service to other terminal devices (including a remote terminal device).
In some possible implementations, the terminal device may be deployed on land, including indoors or outdoors, hand-held, wearable, or vehicle-mounted; can be deployed on the water surface (such as ships, etc.); may be deployed in the air (e.g., aircraft, balloons, satellites, etc.).
In some possible implementations, the terminal device may be a mobile phone (mobile phone), a tablet (Pad), a computer with wireless transceiving functionality, a Virtual Reality (VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned autopilot, a wireless terminal device in telemedicine (remote media), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (smart city), or a wireless terminal device in smart home (smart home), etc.
In addition, the terminal device may also be a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a next generation communication system (e.g., NR communication system, 6G communication system) or a terminal device in a future evolved public land mobile communication network (public land mobile network, PLMN), etc., without being limited in particular.
In some possible implementations, the terminal device may include means for wireless communication functions, such as a chip system, a chip module. By way of example, the system-on-chip may include a chip, and may include other discrete devices.
3. Network equipment
In this embodiment of the present application, the network device may be a device with a transceiver function, which is configured to communicate with the terminal device. For example, the network device may be responsible for radio resource management (radio resource management, RRM), quality of service (quality of service, qoS) management, data compression and encryption, data transceiving, etc. on the air side. The network device may be a Base Station (BS) in a communication system or a device deployed in a radio access network (radio access network, RAN) for providing wireless communication functions. For example, an evolved node B (evolutional node B, eNB or eNodeB) in the LTE communication system, a next generation evolved node B (next generation evolved node B, ng-eNB) in the NR communication system, a next generation node B (next generation node B, gNB) in the NR communication system, a Master Node (MN) in the dual connectivity architecture, a second node or Secondary Node (SN) in the dual connectivity architecture, and the like are not particularly limited thereto.
In some possible implementations, the network device may also be a device in a Core Network (CN), such as an access and mobility management function (access and mobility management function, AMF), a user plane function (user plane function, UPF), etc.; but also Access Points (APs) in a wireless local area network (wireless local area network, WLAN), relay stations, communication devices in a future evolved PLMN network, communication devices in an NTN network, etc.
In some possible implementations, the network device may include a device, such as a system-on-chip, a chip module, having means to provide wireless communication functionality for the terminal device. The chip system may include a chip, for example, or may include other discrete devices.
In some possible implementations, the network device may communicate with an internet protocol (Internet Protocol, IP) network. Such as the internet, a private IP network or other data network, etc.
In some possible implementations, the network device may be a single node to implement the functionality of the base station or the network device may include two or more separate nodes to implement the functionality of the base station. For example, network devices include Centralized Units (CUs) and Distributed Units (DUs), such as gNB-CUs and gNB-DUs. Further, in other embodiments of the present application, the network device may further comprise an active antenna unit (active antenna unit, AAU). Wherein a CU implements a portion of the functions of the network device and a DU implements another portion of the functions of the network device. For example, a CU is responsible for handling non-real-time protocols and services, implementing the functions of a radio resource control (radio resource control, RRC) layer, a service data adaptation (service data adaptation protocol, SDAP) layer, and a packet data convergence (packet data convergence protocol, PDCP) layer. The DUs are responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (radio link control, RLC), medium access control (medium access control, MAC) and Physical (PHY) layers. In addition, the AAU can realize partial physical layer processing function, radio frequency processing and related functions of the active antenna. Since the information of the RRC layer eventually becomes or is converted from the information of the PHY layer, in this network deployment, higher layer signaling (e.g., RRC signaling) may be considered to be transmitted by the DU or transmitted by both the DU and the AAU. It is understood that the network device may include at least one of CU, DU, AAU. In addition, the CU may be divided into network devices in the RAN, or may be divided into network devices in the core network, which is not particularly limited.
In some possible implementations, the network device may be any one of multiple sites that perform coherent cooperative transmission with the terminal device, or other sites outside the multiple sites, or other network devices that perform network communication with the terminal device, which is not limited specifically. The multi-site coherent joint transmission may be a multi-site coherent joint transmission, or different data belonging to the same physical downlink shared channel (Physical Downlink Shared Channel, PDSCH) are sent from different sites to the terminal device, or the multiple sites are virtualized into one site for transmission, and names with the same meaning specified in other standards are also applicable to the application, i.e. the application does not limit the names of the parameters. The stations in the multi-station coherent joint transmission may be remote radio heads (Remote Radio Head, RRH), transmission receiving points (transmission and reception point, TRP), network devices, and the like, which are not particularly limited.
In some possible implementations, the network device may be any one of multiple sites that perform incoherent cooperative transmission with the terminal device, or other sites outside the multiple sites, or other network devices that perform network communication with the terminal device, which is not limited specifically. The multi-site incoherent joint transmission may be a multi-site joint incoherent transmission, or different data belonging to the same PDSCH are sent from different sites to the terminal device, and other standards prescribe the same meaning of the names are also applicable to the application, i.e. the application does not limit the names of the parameters. The stations in the multi-station incoherent joint transmission may be RRHs, TRPs, network devices, etc., which are not particularly limited.
In some possible implementations, the network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (high elliptical orbit, HEO) satellite, or the like. Alternatively, the network device may be a base station disposed on land, in a water area, or the like.
In some possible implementations, the network device may serve a cell, and terminal devices in the cell may communicate with the network device over transmission resources (e.g., spectrum resources). The cells may be macro cells (macro cells), small cells (small cells), urban cells (metro cells), micro cells (micro cells), pico cells (pico cells), femto cells (femto cells), and the like.
4. Description of the examples
An exemplary description of a communication system according to an embodiment of the present application is provided below.
Exemplary, a network architecture of a communication system according to an embodiment of the present application may refer to fig. 1. As shown in fig. 1, communication system 10 may include a network device 110 and a terminal device 120. The network device 110 and the terminal device 120 may communicate wirelessly.
Fig. 1 is merely an illustration of a network architecture of a communication system, and the network architecture of the communication system according to the embodiments of the present application is not limited thereto. For example, in the embodiment of the present application, a server or other device may also be included in the communication system. For another example, in an embodiment of the present application, a communication system may include a plurality of network devices and/or a plurality of terminal devices.
2. Reporting (reporting) of uplink control information (uplink control information, UCI) in a physical uplink control channel (physical uplink control channel, PUCCH)
The types of UCI reported in PUCCH may include hybrid automatic repeat request acknowledgement (Hybrid Automatic Repeat request-ACK, HARQ-ACK) information, scheduling request (Scheduling request, SR), link recovery request (link recovery request, LRR), and channel state information (channel state information, CSI).
UCI bits may include HARQ-ACK information bits (if any), SR information bits (if any), LRR information bits (if any), and CSI bits (if any). Wherein the HARQ-ACK information bits may correspond to a HARQ-ACK codebook. Any description of the SR may apply to the SR and/or the LRR.
When the terminal device has uplink data to be transmitted but no uplink resource, the terminal device may apply for the uplink resource to the network through the SR, and the SR needs to be transmitted on the SR resource.
In the MAC configuration, a logical channel may correspond to one SR configuration, and different SR configurations may be distinguished by a scheduling request identification (scheduling request id). Thus, one logical channel corresponds to at most one schedulingRequestID, and a plurality of logical channels may correspond to the same schedulingRequestID. For example, the logical channel configuration (LogicalChannelConfig) contains a schedulingRequestID.
In addition, SRs need to be transmitted on SR resources, SR resources can be distinguished by scheduling request resource identification (schedulingRequestResourceID), and different schedulingRequestResourceID can correspond to different schedulingRequestID. For example, the scheduling request resource configuration (schedulingRequestResourceConfig) includes schedulingRequestResourceID and schedulingRequestResourceID.
The type (type)/state (state) of the SR includes: active SR, passive SR. Since the terminal device does not always have a need to transmit SR, the active SR can be understood that the terminal device has SR transmission; the negative SR is understood to mean that the terminal device does not transmit an SR.
1. PUCCH resource set
If the terminal device does not provide a dedicated PUCCH resource configuration by a PUCCH resource set (PUCCH-resource) in a PUCCH configuration (PUCCH-Config), the PUCCH resource set is provided by PUCCH resource common (PUCCH-resource common).
2. PUCCH format (format) for transmitting UCI
If the terminal device does not transmit PUSCH and the terminal device is transmitting UCI, then
If transmission exceeds 1 or 2 symbols, the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK/SR bit number) is 1 or 2, the terminal device uses PUCCH format 0 in PUCCH;
if more than 4 symbols are transmitted, the number of HARQ-ACK/SR bits is 1 or 2, the terminal device uses PUCCH format 1 in PUCCH;
if more than 1 or 2 symbols are transmitted, the UCI number of bits is greater than 2, and the terminal device uses PUCCH format 2 in PUCCH;
if more than 4 symbols are transmitted, the UCI number of bits is greater than 2, the PUCCH resource does not contain an orthogonal cover code (orthogonal cover code), or the terminal device is provided with an interleaved PUCCH-PUSCH (useiiterlaceucch-PUSCH) in BWP uplink dedicated (BWP-uplink dedicated), the terminal device uses PUCCH format 3 in PUCCH;
if more than 4 symbols are transmitted, the UCI number of bits is greater than 2, and the PUCCH resource contains an orthogonal cover code, the terminal device uses PUCCH format 4 in PUCCH.
The terminal device may configure a set of configurations for SRs in a PUCCH transmission by scheduling request resource configuration (scheduling request resource configuration), and the PUCCH transmission uses PUCCH format0 or PUCCH format 1.
3. Reporting HARQ-ACK
If the terminal device transmits a PUCCH carrying HARQ-ACK information using PUCCH format0, the terminal device determines m 0 Is a value of (Sequence cyclic shift) m cs Is a value of (a).
Wherein m is 0 And m cs Can be used to determine the cyclic displacement α;
m 0 may be provided by an initial cyclic shift (initial cyclic shift) of PUCCH-format 0; alternatively, if notWith provision of the initial cyclicshift, then m 0 Provided by an initial cyclic shift index;
m cs can be determined by the value of one HARQ-ACK information bit (i.e., HARQ-ACK value), as shown in table 1; alternatively, m cs May be determined by the values of two HARQ-ACK information bits as shown in table 2.
Table 1 maps the value of one HARQ-ACK information bit to the sequence of PUCCH format0
| HARQ-ACK values | 0 | 1 |
| Value of cyclic shift of sequence | m CS ＝0 | m CS ＝6 |
Table 2 maps the values of two HARQ-ACK information bits to the sequence of PUCCH format0
| HARQ-ACK values | {0,0} | {0,1} | {1,1} | {1,0} |
| Value of cyclic shift of sequence | m CS ＝0 | m CS ＝3 | m CS ＝6 | m CS ＝9 |
If the terminal device transmits a PUCCH carrying HARQ-ACK information using PUCCH format 1, the terminal device determines m 0 Is a value of (a). m is m 0 May be provided by an initial cyclicshift of PUCCH-format 1; alternatively, if the initial CycloclShift is not provided, then m 0 Provided by the initial cyclic shift index.
4. Reporting SR
When the terminal device transmits a positive SR, the terminal device transmits a PUCCH in a PUCCH resource (i.e. SR resource) configured for the SR.
For positive SR transmission using PUCCH format0, the terminal device obtains m 0 Set m cs Transmit pucch=0.
For positive SR transmission using PUCCH format1, the terminal device transmits PUCCH by setting b (0) =0.
5. Reporting multiple UCI types
When multiplexing (multiplexing) HARQ-ACKs and SRs on the PUCCH, if the terminal device is to transmit the PUCCH having a positive SR and at most two HARQ-ACK information bits in the resource using PUCCH format0, the terminal device transmits the PUCCH using the resource of HARQ-ACK information. Terminal device determines m 0 The sum of the values of m cs Is a value of (a). That is, the network device passes through m cs The value of (2) can determine whether the PUCCH format0 resource has both a positive SR and HARQ-ACK information bits.
Wherein m is 0 And m cs Can be used to determine the cyclic displacement α;
m 0 may be provided by an initial cyclic shift (initial cyclic shift) of PUCCH-format 0;
m cs May be determined by the value of one HARQ-ACK information bit (i.e., a 1-bit HARQ-ACK value), as shown in table 3; alternatively, m cs Can be determined by the value of two HARQ-ACK information bits (i.e., 2-bit HARQ-ACK value), as shown in table 4.
Table 3 maps the values of one HARQ-ACK information bit and the positive SR to the sequence of PUCCH format 0
| HARQ-ACK values | 0 | 1 |
| Value of cyclic shift of sequence | m CS ＝3 | m CS ＝9 |
Table 4 maps the values of two HARQ-ACK information bits and the positive SR to the sequence of PUCCH format 0
| HARQ-ACK values | {0,0} | {0,1} | {1,1} | {1,0} |
| Value of cyclic shift of sequence | m CS ＝1 | m CS ＝4 | m CS ＝7 | m CS ＝10 |
If the terminal device is to transmit the negative SR and the PUCCH having at most two HARQ-ACK information bits in the resource using PUCCH format 0, the terminal device transmits the PUCCH using the resource of HARQ-ACK information.
If the terminal device transmits a positive or negative SR in the resource using PUCCH format 0 and transmits HARQ-ACK information bits in the resource using PUCCH format 1, the terminal device transmits only the PUCCH having HARQ-ACK information bits in the resource using PUCCH format 1. That is, the terminal device transmits only HARQ-ACK information bits, and does not transmit a positive or negative SR.
If the terminal device transmits a positive SR in a first resource using PUCCH format 1 and transmits a maximum of two HARQ-ACK information bits in a second resource using PUCCH format 1, the terminal device transmits a PUCCH having HARQ-ACK information bits in the first resource using PUCCH format 1. That is, the terminal device transmits HARQ-ACK information bits using the resources of the positive SR
3. Scheduling Request (SR) transmission method
Since there are problems with the uplink resources currently requested by SR, for example, SR cannot tell when the requested uplink resources can be provided; the SR cannot tell the amount of data, etc., that the uplink resource requested to be scheduled needs to carry, thereby reducing reliability, etc., of uplink data transmission.
Based on this, the application needs to further enhance the SR, that is, report/feed back the data feature requirement of the service to the network through the SR. Therefore, the network can decide how to better schedule the uplink resources required by the uplink data of the service according to the data characteristic requirements, and avoid the uplink data of the terminal equipment from exceeding the time delay requirements, so that the scheduled uplink resources can meet the data quantity requirements of the uplink data, and the like, thereby being beneficial to improving the reliability of the uplink data transmission. In particular implementation, the present application may implement the data feature requirement of reporting/feeding back a service to a network through an SR according to the following scheme. It should be noted that, each of the multiple schemes is not necessarily independent, and may be combined/combined with each other to obtain a new scheme, and the new scheme also falls within the scope of protection claimed in the present application, which is not specifically limited and described in detail.
Scheme one:
unlike SR resource allocation in the current protocol, the present application introduces data feature requirements that correspond to SR resources, and the data feature requirements may be of one or more types. Wherein, the corresponding relation between the data characteristic requirement and the SR resource can be defined by network configuration, pre-configuration or protocol.
In this way, the terminal device can determine the data feature requirement according to the uplink data of the service to be transmitted, where the data feature requirement has one or more types, determine the corresponding SR resource according to the data feature requirement, and send the SR according to the corresponding SR resource.
Correspondingly, the network device can determine the corresponding data characteristic requirement according to the SR resource for receiving the SR, and report/feed back the data characteristic requirement through the SR, so that the network device can decide how to schedule the uplink resource required by the uplink data according to the data characteristic requirement, for example, the uplink data is prevented from exceeding the time delay requirement, the data volume requirement of the uplink data is met, and the like.
Scheme II:
the method adopts the SR resource allocation mode in the current protocol, but compared with the SR type/state of the current protocol, the method introduces more new types of SRs, so that the new types of SRs can support the data characteristic requirements, the new types of SRs can carry the data characteristic information, and the data characteristic information has one or more types.
In this way, the terminal device can determine the data characteristic information according to the uplink data of the service to be transmitted, one type of data characteristic information is used for indicating one type of data characteristic requirement, and then the SR carrying the data characteristic information is sent according to the SR resource.
Correspondingly, the network device can acquire the carried data characteristic information according to the received SR, and then determine the data characteristic requirement according to the data characteristic information, so as to report/feed back the data characteristic requirement through the SR, so that the network device can decide how to schedule the uplink resources required by the uplink data according to the data characteristic requirement, such as avoiding the uplink data from exceeding the time delay requirement, meeting the data volume requirement of the uplink data, and the like.
The technical schemes, beneficial effects, concepts and the like related to the embodiments of the present application are specifically described below.
1. Service
The service of the embodiment of the application may include at least one of the following: delay sensitive traffic, delay sensitive and data volume large traffic, low delay high reliability and data volume large traffic or data volume large traffic, etc.
For example, the service may include at least one of an Extended Reality (XR) service, a Virtual Reality (VR) service, an online video service, an online live service, an online voice service, and the like, which is not particularly limited.
It should be noted that XR service is mainly video service, and data of the video service is in burst mode, that is, the data of the XR service may be periodically generated, and typically, 60 frames of video data are provided in 1 second. That is, one video frame is generated every 16.6 ms. Since the size of the data amount in one video frame may be too large, it may be fragmented into several tens of IP packets. That is, for a network to transmit XR traffic, tens of IP packets need to be transmitted every 16.6ms, and the arrival time of the IP packets has uncertainty, roughly ranging within [ -4,4] ms, or [ -5,5] ms, and obeying a truncated gaussian distribution.
2. Uplink data of service
In the embodiment of the present application, the uplink data of the service may be generated by an application in an application layer of the terminal device. Wherein the data generated by the same (certain) or different (certain) applications may be uplink data of the service.
For example, taking uplink data generated by XR service each time as an example, an XR application in an application layer of the terminal device may periodically generate a frame of video. Multiple packets of the same frame of video may form a burst (burst), i.e., each burst contains multiple packets, which collectively arrive at the access layer awaiting transmission over the air. The XR application may periodically generate 60 frames of video every second, that is, every 16.67ms has a burst to be transmitted, where each burst includes multiple data packets, and the data amount of each burst may fluctuate within a certain range.
It should be noted that, data generated by an application in the application layer may be processed by some protocol layers.
For example, the data transmission procedure in a fifth generation (5G) new air interface (NR) communication system is exemplified.
In the 5G NR communication system, data transmission may be performed through a user plane protocol stack of a service data adaptation protocol (service data adaptation protocol, SDAP) layer, a packet data convergence protocol (packet data convergence protocol, PDCP) layer, a radio link control (radio link control, RLC) layer, a medium access control (medium access control, MAC) layer, a Physical (PHY) layer, and the like between a network device and a terminal device.
During data transfer, the SDAP layer maps IP packets to different Radio Bearers (RBs). In general, data entities from or to a higher protocol layer are called service data units (service data unit, SDUs) and data entities from or to a lower protocol layer are called protocol data units (protocol data unit, PDUs). Thus, the SDAP layer outputs SDAP PDUs to the PDCP layer by adding SDAP headers to the IP packets, and the PDCP layer outputs PDCP SDUs to the SDAP layer, which are equivalent to the PDCP SDUs.
Similarly, the PDCP layer outputs PDCP PDUs to the RLC layer by adding PDCP headers to the SDAP PDUs. The RLC layer outputs RLC PDUs to the MAC layer by adding RLC headers to the PDCP PDUs.
Finally, the MAC layer multiplexes multiple RLC PDUs and adds a MAC header to form a Transport Block (TB), and finally the PHY layer performs processes such as channel coding, modulation, multi-antenna processing, and resource mapping on the TB for transmission.
The application described herein may be referred to as an Application (APP). An application is a program that runs on an operating system to perform a specific task or tasks or to have a function, and can run on an application layer to interact with a user, with a visual user interface.
3. Data characteristic requirements of business (data feature requirement)
1) Definition of the definition
In the embodiment of the application, a certain data characteristic requirement exists in uplink data of a service. The data characteristic requirements may be used to represent, among other things, requirements/demands of upstream data passing through the traffic on at least one of packet delay budget (packet delay budget, PDB), buffer size (buffer size), delay jitter (jitter), etc.
2) Type(s)
In the embodiment of the present application, the type of the data feature requirement of the service may include at least one of the following: PDB, buffer size, delay jitter.
1)PDB
The PDB is an indicator in the quality of service class indicator (Quality of Service Class Identifier, QCI) that defines the upper limit of the time that a packet of upstream data of a service can be delayed between a terminal device and a network device (e.g., UPF), i.e., the upper limit of the delay.
For a certain 5QI (5G QCI), the value of PDB is the same in both uplink and downlink. In the case of 3GPP access, PDB is used to support the configuration of scheduling and link layer functions. For guaranteed bit rate (Guaranteed Bit Rate, GBR) QoS flows using Delay-critical (Delay-critical) resource types, packets delayed beyond the PDB are considered lost if the data burst size does not exceed the maximum data burst size (Maximum Data Burst Volume, MDBV) and the QoS flow does not exceed the guaranteed traffic bit rate (Guaranteed Flow Bit Rate, GFBR) during the PDB. For GBR QoS flows with GBR resource types not exceeding GFBR, the delay of 98% of the packet packets will not experience PDBs exceeding 5 QI.
2) Cache size
The buffer size may represent a data size (data size) of uplink data of the service. Therefore, the buffer size can also be said to be the data amount, which is not particularly limited.
The data amount may be data indicating how much traffic is generated. It should be noted that, uplink data generated by each service may be composed of a plurality of data packets, and the data packets have a certain data volume.
For example, with the above example, an XR application may periodically generate 60 frames of video every second, i.e., every 16.67ms has a burst to be transmitted, which may be considered as the amount of data or bursty data.
3) Delay jitter
In network transmission, the delay of the uplink data of the service is different from the terminal device to the network device each time, and delay jitter can be used to measure the difference.
4. Reporting/feeding back data characteristic requirements of services to a network via SR
In connection with the above description, the above "scheme one" and "scheme two" are specifically described below.
Scheme one:
1) Data characteristic requirements correspond to SR resources
The current protocol configures SR resources by higher layer parameters (e.g., schedulingRequestResourceConfig) without any corresponding association of SR resources with traffic.
In the scheme one, different from the SR resource allocation mode in the current protocol, the method introduces data characteristic requirements to correspond to SR resources. In this way, the terminal device of the present application may send the SR according to the data characteristic requirement for the corresponding SR resource. Correspondingly, the network device may receive the SR according to the data characteristic requiring the corresponding SR resource.
2) Different types of data characteristics require corresponding different SR resources
In some possible implementations, different types of data characteristic requirements may correspond to different SR resources. Wherein different SR resources may be distinguished according to schedulingrequestirourceid, and different schedulingrequestimurceid may correspond to different schedulingRequestID.
For example, SR resources corresponding to PDBs are different from SR resources corresponding to buffer sizes.
3) Different types of data characteristics require corresponding to the same SR resources
In some possible implementations, different types of data characteristic requirements may correspond to the same SR resource. Wherein the same SR resource may have the same schedulingrequestiresourceid, and the schedulingrequestidreichid may correspond to the schedulingRequestID.
4) First scheduling request resource or first SR resource
For convenience of description and distinction, the SR resource corresponding to the data feature requirement in the "scheme one" is referred to as "first scheduling request resource or first SR resource" in this application, and of course, other terms may be used for description, which is not limited specifically.
In some possible implementations, the first SR resource may be a PUCCH using PUCCH format 0 or PUCCH format 1.
5) How the first SR resources corresponding to different types of data characteristic requirements distinguish different types
In the embodiment of the present application, the first SR resources corresponding to different types of data feature requirements may be differentiated according to the following manner. It should be noted that, the various modes are not necessarily independent of each other, and may be combined/combined with each other to obtain a new mode, and the new mode also falls within the scope of protection claimed in the present application, which is not specifically limited and described in detail.
Mode a:
in some possible implementations, the different first SR resources may be distinguished according to schedulingrequestirourceid, and the different schedulingrequestirourceid may correspond to different schedulingRequestID, which may be used to distinguish SRs.
Mode B:
in some possible implementations, the different first SR resources may be distinguished by a time domain location and/or a frequency domain location in the PUCCH.
For example, one data characteristic requires that the corresponding first SR resource occupy one or more symbols in the PUCCH, while another data characteristic requires that the corresponding first SR resource occupy another one or more symbols in the PUCCH;
For another example, one data characteristic requires that the corresponding first SR Resource be one or more Resource Blocks (RBs) in the PUCCH, and another data characteristic requires that the corresponding first SR Resource be another one or more RBs in the PUCCH.
Mode C:
in some possible implementations, the different first SR resources may be distinguished by PUCCH format configuration.
For example, one data characteristic requires that the corresponding first SR resource uses PUCCH format 0, while another data characteristic requires that the corresponding first SR resource uses PUCCH format 1.
6) How the first SR resources corresponding to different types of data characteristic requirements are identical
In some possible implementations, the different types of data features require corresponding first SR resources, and the time domain position and the frequency domain position in the PUCCH are the same.
For example, different types of data features require that corresponding first SR resources occupy the same symbols and RBs in the PUCCH.
In some possible implementations, different types of data characteristics require that the corresponding first SR resources use the same PUCCH format.
7) The same type of data characteristic requirements include multiple levels (levels)
It should be noted that the present application may introduce multiple levels for the same type of data characteristic requirements to meet different requirements/demands.
Example one:
taking the type of data feature requirement as PDB as an example, if the PBD required by the uplink data of the service is small, the time delay required by the uplink data is small, so the service can be regarded as a time delay sensitive service or a low time delay service, and the service needs to be transmitted in an emergency/quick/priority manner;
if the PBD required by the uplink traffic of the traffic is large, the traffic can be regarded as a non-delay sensitive traffic, and no emergency/fast/prioritized transmission of the traffic is required.
In this regard, multiple levels may be introduced into the PDB, that is, the time delay requirement may be divided into multiple levels to meet different time delay requirements, such as short time delay (short/low delay), normal time delay (normal delay), long time delay (long/high delay), etc.; or, high level, medium level, low level; alternatively, urgent (urgent), normal, non-urgent (non-urgent), etc.; alternatively, the high priority (high priority), medium priority (middle priority), low priority (low priority), and the like are not particularly limited.
The short delay can be understood that the PBD required by the uplink data is very small; high-level, it can be understood that the PBD required for upstream data is small; emergency, it can be understood that the PBD required for the upstream data is small; high priority, it is understood that the PBD required for upstream data is small, etc.
Example two:
taking the type of the data characteristic requirement as an example of the buffer size, if the buffer size required by the uplink data of the service is small, the data size of the uplink data of the service is small;
if the buffer memory size required by the uplink service of the service is large, the data volume of the uplink data of the service is large.
In this regard, the present application may introduce multiple levels to the cache size, that is, the data size requirement is divided into multiple levels to meet different data size requirements, such as a large cache (big/large buffer), a normal delay (normal buffer), a small cache (small buffer), etc.; alternatively, high (high/huge/big/large level), medium (middle level), low (low/small level), and the like are not particularly limited.
The large buffer memory can be understood as that the size of the PBD buffer memory required by the uplink data is large; high level, it is understood that the PBD buffer size required for upstream data is large, etc.
Example three:
taking the type of the data characteristic requirement as an example of delay jitter, if the delay jitter required by the uplink data of the service is small, the delay of the uplink data is relatively stable each time, the time of the uplink data reaching the network equipment each time is equal, and the like;
If the delay jitter required by the uplink data of the service is large, the delay of the uplink data is unstable each time, and the time for the uplink data to reach the network equipment each time is different, and the like.
In this regard, the present application may introduce multiple levels to the delay jitter, that is, the jitter requirement is divided into multiple levels to meet different jitter requirements, such as high delay jitter, normal delay jitter, high delay jitter, etc.; or, high, medium, low, etc., and is not particularly limited.
The high delay jitter is understood as that the delay jitter required by the uplink data is large/high; high level, it is understood that the delay jitter required for upstream data is large/high.
8) Different classes of data characteristic requirements of the same type correspond to different first SR resources
It should be noted that, different levels of the data feature requirement of the same type and different first SR resources also have a corresponding relationship, so that the network device can determine which level is required by the data feature of the same type according to the first SR resources and the corresponding relationship.
For example, the first SR resource corresponding to the short latency of the PDB may be different from the first SR resource corresponding to the normal latency of the PDB, where the difference may be different from the schedulingRequestResourceID, may be different from the time domain location and/or the frequency domain location of the SR resource, may be different from the PUCC format of the SR resource, and so on.
9) The hierarchical combinations of the data characteristic requirements of different types correspond to the same first SR resources
It should be noted that the level combinations of the data feature requirements of different types correspond to the same first SR resource, so that the level combinations of the data feature requirements of different types can be reported simultaneously through one first SR resource.
For example, the first SR resource corresponding to the short latency of the PDB is the same as the first SR resource corresponding to the large cache of the cache size. Thus, the short latency of the PDB and the large cache of the cache size may be reported simultaneously by one first SR resource.
10 Different levels of data characteristic requirements of the same type correspond to different schedulingRequestIDs
It should be noted that, since different levels correspond to different first SR resources, different first SR resources are distinguished according to schedulingRequestResourceID, and different schedulingRequestResourceID corresponds to different schedulingRequestID. Thus, different levels will also correspond to different schedulingRequestIDs.
11 A) the schedulingRequestID corresponding to different levels of the same type of data characteristic requirements corresponds to the same logical channel
It should be noted that, since the schedulingRequestID corresponding to different levels corresponds to the same logical channel, the present application may enable one LogicalChannelConfig to include the schedulingRequestID corresponding to different levels, so that one LogicalChannelConfig may include multiple SR configurations, unlike the conventional one including the schedulingRequestID.
12 How to implement the correspondence between the data characteristic requirements and the first SR resource
It should be noted that, the correspondence between the data feature requirement and the first SR resource in the present application may be specified by a network configuration, a pre-configuration, or a protocol.
For example, taking network configuration as an example, the corresponding relationship between the first SR resource and the second SR resource is required through configuration data features such as higher layer parameters/higher layer signaling/system information in the processes of cell search, cell residence, uplink and downlink synchronization, cell handover, random access, and the like.
13 Type of SR
Note that, the types of SRs in the "scheme one" may include a positive SR and a negative SR. The positive SR may be understood that there is an SR transmission on the first SR resource corresponding to the data feature requirement; the negative SR may be understood that the data feature requires that no SR be transmitted on the corresponding first SR resource.
14 Description of the examples
In summary, the following illustrates "scheme one
Illustration 1:
the method and the device are classified into three grades according to the PDB requirements of the service, namely short time delay (namely emergency service), normal time delay (namely general emergency service) and high time delay (namely non-emergency service).
For this, the network device may configure SR resources corresponding to each of the three levels of the PDB to the terminal device. Wherein, the logicalChannelConfig contains 3 schedulingRequestIDs, that is, the LCH may contain 3 SR configurations, which respectively correspond to the three grades of SR resources of the PDB.
When the PDB requirement of the service is short time delay, the terminal equipment can send the SR according to the SR resources corresponding to the short time delay. Correspondingly, the network device can determine that the PDB requirement of the service is a short delay according to the SR resource of the SR. In this way, the network device can schedule uplink resources required by the service according to the short delay.
Illustration 2:
the method and the device are divided into three levels according to the requirement of the buffer size of the service, namely, large buffer (namely, large data volume), normal buffer (namely, normal data volume) and small buffer (namely, large data volume).
For this, the network device may configure SR resources corresponding to each of the three levels of the buffer size to the terminal device. The logicalChannelConfig contains 3 schedulingRequestIDs, that is, the LCH may contain 3 SR configurations, which respectively correspond to three levels of SR resources of the buffer size.
When the buffer size requirement of the service is a large buffer, the terminal device can send SR according to the SR resource corresponding to the large buffer. Correspondingly, the network device can determine that the buffer size requirement of the service is large buffer according to the SR resource of the SR. In this way, the network device can schedule uplink resources required by the service according to the large buffer.
Illustration 3:
in the embodiment of the application, the PDB requirements of the service are divided into three levels, namely a short time delay (i.e. emergency service), a normal time delay (i.e. general emergency service), a high time delay (i.e. non-emergency service), and the requirements of the buffer size of the service are divided into three levels, namely a large buffer (i.e. large data volume), a normal buffer (i.e. normal data volume) and a small buffer (i.e. small data volume),
for this, the network device may configure the terminal device with SR resources corresponding to the three levels of the PDB and the three levels of the buffer size after being combined, for a total of 9 SR resources, that is, SR resources corresponding to the short latency and the large buffer, SR resources corresponding to the short latency and the normal buffer, SR resources corresponding to the short latency and the small buffer, and so on.
Wherein, the logicalChannelConfig contains 9 schedulingRequestIDs, that is, the LCH may contain 9 SR configurations, which respectively correspond to the 9 SR resources.
When the service requirement is short delay and large buffer, the terminal equipment can send SR according to the SR resources corresponding to the short delay and large buffer. Correspondingly, the network device can determine that the service requirement is short latency and large cache according to the SR resource of the SR. In this way, the network device can schedule uplink resources required by the service according to the short latency and large buffer.
Scheme II:
1) Novel type of SR
The current protocol configures SR resources through higher layer parameters (e.g., schedulingRequestResourceConfig), but the SR resources do not have any corresponding association with traffic, and the types of SRs include active SR, negative SR.
The scheme II can adopt an SR resource allocation mode in the current protocol, but not only the positive SR and the negative SR, but more new types of SRs are introduced for the SRs belonging to the positive SR, and the SRs of different new types can support the data characteristic requirements of different types or the same type.
For example, one SR may support PDB, one SR may support buffer size, and one SR may support delay jitter.
For another example, one SR may support PDB and buffer size, and one SR may support delay jitter.
In addition, similar to scheme one described above, the same type of data characteristic requirements may include multiple levels. For this, different new types of SRs may also support different levels of data feature requirements for the same type.
For example, one SR may support a short latency of PDB, one SR may support a normal latency of PDB, one SR may support a long latency of PDB, and so on.
In some possible implementations, different new types of SRs may support a hierarchical combination of different types of data feature requirements.
For example, one SR may support a short latency and buffer size large buffer of the PDB, one SR may support a normal latency and buffer size small buffer of the PDB, and so on.
In some possible implementations, different new types of SR resources may be distinguished according to schedulingRequestResourceID, and different schedulingRequestResourceID may correspond to different schedulingRequestID.
2) Novel SR carrying data characteristic information
In contrast to the SR of the current protocol, the new type of SR of the present application may carry data characteristic information having one or more types, and one type of data characteristic information is used to indicate one type of data characteristic requirement.
In some possible implementations, the type of data characteristic information may include at least one of: packet delay budget information, buffer size information, and delay jitter information.
Wherein the packet delay budget information may be used to indicate a packet delay budget/class of packet delay budget; the buffer size information may be used to indicate a buffer size/a level of data/a data amount; the delay jitter information may be used to indicate delay jitter/the level of delay jitter.
In some possible implementations, the new type of SR may carry at least one of: packet delay budget information, buffer size information, and delay jitter information.
It should be noted that which type or types of information the new type of SR carries may be related to the type of SR.
For example, if the SR supports PDB, the SR may carry packet delay budget information.
For another example, if the SR supports short latency of the PDB, the SR may carry packet latency budget information.
For another example, if the SR supports PDB and buffer size, the SR may carry packet delay budget information and buffer size information.
In some possible implementations, different new types of SRs may carry different or the same types of data characteristic information.
For example, one SR carries packet delay budget information, one SR carries buffer size information, and one SR carries delay jitter information.
For another example, one SR carries packet delay budget information, buffer size information, and one SR carries delay jitter information.
3) Second scheduling request resource or second SR resource
For convenience of description and distinction, the SR resource in the "scheme two" is referred to as "second scheduling request resource or second SR resource" in this application, and of course, other terms may also be used for description, which is not limited in particular.
In some possible implementations, the second SR resource may be one of PUCCH format 0, PUCCH of PUCCH format 1, PUCCH of PUCCH format 2, PUCCH of PUCCH format 3, PUCCH of PUCCH format 4.
It should be noted that, the second SR resource is PUCCH with PUCCH format 0, which may be understood that SR adopts PUCCH transmission with PUCCH format 0; the second SR resource is PUCCH with PUCCH format 1, and it can be understood that SR is transmitted in PUCCH format 1, and the rest is the same.
4) Different new types of SR correspond to different m CS
In combination with the content in the above "3, report HARQ-ACK", since the application introduces multiple types of SRs, the application can introduce different SR values (the SR value may also be the value of the SR information bit) to indicate different types of SRs, and introducing different types of SRs can correspond to different m CS To map SR values to a PDCCH sequence.
Example 1:
taking 2 new types of SRs as an example, the 2 new types of SRs exist as follows:
the type 1 SR supports the normal latency of PDB, i.e., the SR required for latency, or the positive+delay SR, which is not particularly limited;
the type 2 SR supports the buffer size, i.e., the SR required for buffering, or the active+buffer SR, which is not particularly limited;
Each SR value is used to indicate a new type of SR, and the SR value is 1 bit; wherein, if the SR value is "0", the SR value indicates the 1 st type of SR; if the SR value is "1", the SR value indicates the type 2 SR.
The 2 new types of SRs can respectively correspond to one m CS As shown in table 5; wherein, if the SR value is "0", corresponding m CS =3; if the SR value is "1", corresponding m CS ＝6。
Table 5 maps SR values to PDCCH sequences
| SR value | 0 | 1 |
| Value of cyclic shift of sequence | m CS ＝3 | m CS ＝6 |
Example 2:
taking 2 new types of SRs as an example, the 2 new types of SRs exist as follows:
the type 1 SR supports the normal delay of the PDB, i.e., the SR required by the normal delay, or the SR required by non-emergency, or the positive+non-urgent SR, which is not particularly limited;
the type 2 SR supports low latency of PDB, i.e., low latency required SR, or urgent required SR, or active+urgent SR, which is not particularly limited;
each SR value is used to indicate a new type of SR, and the SR value is 1 bit; wherein, if the SR value is "0", the SR value indicates the 1 st type of SR; if the SR value is "1", the SR value indicates the type 2 SR.
The 2 new types of SRs can respectively correspond to one m CS As shown in table 5; wherein, if the SR value is "0", corresponding m CS =3; if the SR value is "1", corresponding m CS ＝6。
Example 3:
taking 2 new types of SRs as an example, the 2 new types of SRs exist as follows:
the type 1 SR supports normal buffering of the buffer size, i.e., SR required by normal buffering, or SR of normal data volume, or active+normal buffer SR, which is not particularly limited;
the type 2 SR supports a large buffer of buffer size, i.e., an SR required for a large buffer, or an SR of a large data amount, or a positive+huge buffer SR, which is not particularly limited;
each SR value is used to indicate a new type of SR, and the SR value is 1 bit; wherein, if the SR value is "0", the SR value indicates the 1 st type of SR; if the SR value is "1", the SR value indicates the type 2 SR.
The 2 new types of SRs can respectively correspond to one m CS As shown in table 5; wherein, if the SR value is "0", corresponding m CS =3; if the SR value is "1", corresponding m CS ＝6。
Example 4:
taking 4 new types of SRs as an example, the 4 new types of SRs exist as follows:
the type 1 SR supports normal latency and normal buffer of the buffer size of the PDB, i.e., SR of normal latency requirement and normal buffer requirement, or SR of non-urgent requirement and normal buffer requirement, or positive+non-urgent+normal buffer SR, which is not particularly limited;
The type 2 SR supports the normal delay of the PDB and the large buffer of the buffer size, i.e., the SR of the normal delay requirement and the large buffer requirement, or the SR of the non-urgent requirement and the large buffer requirement, or the positive+non-urgent+huge buffer SR, which is not particularly limited;
the type 3 SR supports normal buffering of low latency and buffer size of the PDB, i.e., SR of low latency requirement and normal buffering requirement, or SR of urgent requirement and normal buffering requirement, or active+urgent+normal buffer SR, which is not particularly limited;
the type 4 SR supports low latency and large buffer size of PDB, i.e., low latency and large buffer request SR, or urgent and large buffer request SR, or active+urgent+hue buffer SR, without specific limitation;
each SR value is used to indicate a new type of SR, and the SR value is 2 bits; wherein, if the SR value is "{0,0}", the SR value indicates the 1 st type of SR; if the SR value is "{0,1}", the SR value indicates a type 2 SR; if the SR value is "{1,0}", the SR value indicates the 3 rd type of SR; if the SR value is "{1,1}", the SR value indicates a 4 th type of SR;
The 4 new types of SRs can respectively correspond to one m CS Such asTable 6 shows; wherein, if the SR value is "{0,0}", corresponding m CS =0, and the rest are known in the same manner.
Table 6 maps SR values to PDCCH sequences
| SR value | {0,0} | {0,1} | {1,1} | {1,0} |
| Value of cyclic shift of sequence | m CS ＝0 | m CS ＝3 | m CS ＝6 | m CS ＝9 |
In some possible implementations, if the second SR resource is PUCCH with PUCCH format 0, different new types of SRs may correspond to different m CS 。
It should be noted that if the terminal device transmits a new type of SR using PUCCH of PUCCH format 0, the terminal device may determine m cs So that the SR value of the new type of SR can be mapped to the sequence of PUCCH format 0.
5) Modulation of data characteristic information
It should be noted that, the present application may modulate the data characteristic information by one of the following: quadrature phase shift keying (Quadrature Phase Shift Keying, QPSK) modulation, binary phase shift keying (Binary Phase Shift Keying, BPSK) modulation, quadrature amplitude modulation (Quadrature Amplitude Modulation, QAM) modulation. In this way, the transmission of the data characteristic information can be ensured by modulation.
In addition, the data characteristic information may be modulated by adjusting an SR value corresponding to a new type of SR carrying the data characteristic information.
For example, in the above-described "example 1" to "example 4", the SR value is modulated.
In some possible implementations, the number of bits of the SR value may be used to determine which to select for modulation.
For example, in the above-described "example 1" to "example 3", the SR value is 1 bit, and thus the SR value may be BPSK modulated.
For another example, in the above "example 4", the SR value is 2 bits, and thus the SR value may be subjected to QPSK modulation.
For another example, if the SR value is greater than 2 bits, the SR value may be QAM (e.g., 16 QAM) modulated.
In some possible implementations, if the second SR resource is a PUCCH of PUCCH format 1, the data characteristic information is modulated by one of: QPSK modulation, BPSK modulation, QAM modulation.
In order to ensure that the PUCCH format 1 is used to transmit the new type of SR, the present application may perform one of QPSK modulation, BPSK modulation, and QAM modulation on the data characteristic information carried by the new type of SR.
For example, according to the sequence modulation of PUCCH format 1, the present application may obtain a complex-valued symbol (d (0)) after QPSK modulating the data characteristic information, and multiply d (0) by a sequence according to the following formula
Wherein,representing a low peak-to-average power ratio (low-PAPR) sequence;
the scheduling bandwidth of uplink transmission is represented by the number of RBs;
the number of subcarriers per RB is indicated. />
For another example, in the above "example 1" to "example 3", the SR value is 1 bit, and thus the SR value may be BPSK modulated to obtain d (0).
For another example, in the above "example 4", since the SR value is 2 bits, the SR value can be subjected to QPSK modulation to obtain d (0).
For another example, if the SR value is greater than 2 bits, the SR value may be QAM (e.g., 16 QAM) modulated to obtain d (0).
6) Sequential generation of bit sequences of different types of data characteristic information
It should be noted that, since the data characteristic information has different types, the new type of SR may carry at least one of packet delay budget information, buffer size information, and delay jitter information, so that the data characteristic information carried by the new type of SR has multiple types and includes too many bits (e.g. greater than 2 bits). Thus, to guarantee a new type of SR transmission carrying too many bits and too many information types, the present application may generate bit sequences in order of different types of data characteristic information.
For example, if the new SR carries packet delay budget information, buffer size information, and delay jitter information, the packet delay budget information, the buffer size information, and the delay jitter information may be sequentially generated into a bit sequence according to the sequence, and then transmitted.
In some possible implementations, if the second SR resource is PUCCH format 2/3/4, different types of data characteristic information generate bit sequences in order.
It should be noted that if the data characteristic information carried by the new type of SR includes too many information types and too many bits, the SR may not be transmitted using PUCCH format 0/1. In order to guarantee that the SR is transmitted using PUCCH format 2/3/4, the present application requires different types of data characteristic information to be sequentially generated into bit sequences.
In addition, the bit sequence is generated in sequence according to different types of the data characteristic information, namely the SR value is generated in sequence according to the data characteristic requirement, and each bit in the bit sequence corresponds to the data characteristic requirement of different types.
For example, the SR value is 3 bits, 1 bit corresponds to urgent or non-urgent PDB request, 1 bit corresponds to large buffer or normal buffer with buffer size request, and 1 bit corresponds to high delay jitter or low delay jitter with delay jitter request. Wherein, after the SR generates the bit sequence in sequence, the bit sequence exists as follows:
Bit 1 corresponds to the PDB requirement; the value of 1 st bit is "1" to indicate emergency, and the value of 1 st bit is "0" to indicate non-emergency;
bit 2 corresponds to the buffer size requirement; the value of the 2 nd bit is 1 to indicate large cache, and the value of the 2 nd bit is 0 to indicate normal cache;
bit 3 corresponds to the delay jitter requirement; the 3 rd bit has a value of "1" representing high-delay jitter, and the 2 nd bit has a value of "0" representing low-delay jitter;
thus, if the bit sequence is "101" or "{1,0,1}", then this indicates urgent, normal buffered and high latency jitter; if the bit sequence is "001" or "{0, 1}", indicating non-urgent, normal buffered and high-delay jitter; and so on.
7) New types of SR multiplexing with other UCI
It should be noted that, the present application may multiplex the new type SR with other UCI, where the other UCI includes at least one of HARQ-ACK information, CSI, and LRR, so that reporting the new type SR and other UCI at the same time may be implemented.
8) New type of SR and other UCI joint corresponds to m CS
It should be noted that, in combination with the content of "5, reporting multiple UCI types", different new types of SRs and combinations of different types of other UCI types may be introduced to correspond to different m CS So that the new type of SR and the other UCI are mapped to the PDCCH sequence.
Example a:
taking 2 new types of SRs as an example, the 2 new types of SRs exist as follows:
the type 1 SR supports the normal latency of PDB, i.e., the SR required for latency, or the positive+delay SR, which is not particularly limited;
the type 2 SR supports the buffer size, i.e., the SR required for buffering, or the active+buffer SR, which is not particularly limited;
each SR value is used to indicate a new type of SR, and the SR value is 1 bit; wherein, if the SR value is "0", the SR value indicates the 1 st type of SR; if the SR value is "1", the SR value indicates the type 2 SR.
If the HARQ-ACK information is 1 bit, the 2 new types of SRs and the HARQ-ACK information can be respectively combined to correspond to one m CS As shown in table 7; wherein, if the SR value is "0" and the HARQ-ACK value is 0, corresponding to m CS =3, if the SR value is "1" and the HARQ-ACK value is 0, corresponding to m CS ＝6。
TABLE 7 New types of SRs and one HARQ-ACK information bit are jointly mapped to PDCCH sequences
| HARQ-ACK value=0 | HARQ-ACK value=1 | |
| SR value = {0} | m CS ＝3 | m CS ＝6 |
| SR value = {1} | m CS ＝2 | m CS ＝8 |
Example B:
taking 2 new types of SRs as an example, the 2 new types of SRs exist as follows:
The type 1 SR supports the normal delay of the PDB, i.e., the SR required by the normal delay, or the SR required by non-emergency, or the positive+non-urgent SR, which is not particularly limited;
the type 2 SR supports low latency of PDB, i.e., low latency required SR, or urgent required SR, or active+urgent SR, which is not particularly limited;
each SR value is used to indicate a new type of SR, and the SR value is 1 bit; wherein, if the SR value is "0", the SR value indicates the 1 st type of SR; if the SR value is "1", the SR value indicates the type 2 SR.
If the HARQ-ACK information is 1 bit, the 2 new types of SRs and the HARQ-ACK information can be respectively combined to correspond to one m CS As shown in table 7.
Example C:
taking 2 new types of SRs as an example, the 2 new types of SRs exist as follows:
the type 1 SR supports normal buffering of the buffer size, i.e., SR required by normal buffering, or SR of normal data volume, or active+normal buffer SR, which is not particularly limited;
the type 2 SR supports a large buffer of buffer size, i.e., an SR required for a large buffer, or an SR of a large data amount, or a positive+huge buffer SR, which is not particularly limited;
Each SR value is used to indicate a new type of SR, and the SR value is 1 bit; wherein, if the SR value is "0", the SR value indicates the 1 st type of SR; if the SR value is "1", the SR value indicates the type 2 SR.
If the HARQ-ACK information is 1 bit, the 2 new types of SRs and the HARQ-ACK information can be respectively combined to correspond to one m CS As shown in table 7.
Example D:
taking 4 new types of SRs, and other UCI including HARQ-ACK information as an example, there are the following:
the type 1 SR supports normal latency and normal buffer of the buffer size of the PDB, i.e., SR of normal latency requirement and normal buffer requirement, or SR of non-urgent requirement and normal buffer requirement, or positive+non-urgent+normal buffer SR, which is not particularly limited;
the type 2 SR supports normal latency of the buffer size PDB and large buffer of the buffer size, i.e., SR of normal latency requirement and large buffer requirement, or SR of non-urgent requirement and large buffer requirement, or positive+non-urgent+hub buffer SR, which is not particularly limited;
the type 3 SR supports normal buffering of low latency and buffering size of the data amount PDB, i.e., SR of low latency requirement and normal buffering requirement, or SR of urgent requirement and normal buffering requirement, or positive+urgent+normal buffer SR, which is not particularly limited;
The type 4 SR supports low latency and large buffer size of PDB, i.e., low latency and large buffer request SR, or urgent and large buffer request SR, or active+urgent+hue buffer SR, without specific limitation;
each SR value is used to indicate a new type of SR, and the SR value is 2 bits; wherein, if the SR value is "{0,0}", the SR value indicates the 1 st type of SR; if the SR value is "{0,1}", the SR value indicates a type 2 SR; if the SR value is "{1,0}", the SR value indicates the 3 rd type of SR; if the SR value is "{1,1}", the SR value indicates a 4 th type of SR;
if the HARQ-ACK information is 1 bit, the 4 new types of SRs and the HARQ-ACK information can be respectively combined to correspond to one m CS As shown in table 8; if the SR value is "{0,0}" and the HARQ-ACK value is 0, corresponding m CS =3, the rest is known in the same way.
Table 8 new types of SRs and one HARQ-ACK information bit are jointly mapped to PDCCH sequences
| HARQ-ACK value=0 | HARQ-ACK value=1 | |
| SR value = {0,0} | m CS ＝3 | m CS ＝9 |
| SR value = {0,1} | m CS ＝2 | m CS ＝8 |
| SR value = {1,1} | m CS ＝1 | m CS ＝7 |
| SR value = {1,0} | m CS ＝0 | m CS ＝6 |
If the HARQ-ACK information is 2 bits, the 4 new types of SRs and the HARQ-ACK information can be respectively combined to correspond to one m CS As shown in table 9; if the SR value is "{0,0}" and the HARQ-ACK value is "{0,0}", corresponding m CS =1, the rest is known in the same way.
Table 9 new types of SRs and two HARQ-ACK information bits are jointly mapped to PDCCH sequences
In some possible implementations, if the new type of SR is transmitted in PUCCH format 0/1 and the other UCI is transmitted in PUCCH format 0, then the different new types of SR and the different types of other UCI may jointly correspond to different m CS 。
It should be noted that if the terminal device transmits a new type of SR using PUCCH format 0/1 and transmits other UCI using PUCCH format 0, the terminal device may determine m cs And thus, the SR value and other UCI of the new type of SR can be mapped to the sequence, thereby ensuring transmission of the new type of SR and other UCI.
9) Joint coding of data characteristic information and other UCIs
It should be noted that, the present application may perform joint encoding on the data characteristic information and other UCI, and perform modulation in QPSK, BPSK, QAM after joint encoding, so as to ensure transmission when the new type of SR multiplexes other UCI.
For example, in the jointly encoded bits, the high order bits correspond to other UCI, and the low order bits correspond to a new type of SR.
Taking other UCI including 1-bit HARQ-ACK information and 2 new types of SRs as an example, the HARQ-ACK information and the 2 new types of jointly encoded bits are shown in table 10. If the bit of the joint coding is "10", the high-order 1 corresponds to "ACK" in the HARQ-ACK information, and the low-order 0 corresponds to the data characteristic information carried by the 2 nd type SR.
Table 10 jointly encoded bits
| ACK | NACK | |
| Type 1 SR | 11 | 01 |
| Type 2 SR | 10 | 00 |
In some possible implementations, if the new type of SR is transmitted in PUCCH format 1 and the other UCI is transmitted in PUCCH format 1, the data characteristic information and the other UCI are jointly encoded and one of the modulations QPSK, BPSK, QAM is performed after the joint encoding.
It should be noted that, if the terminal device transmits the new type of SR and other UCI using PUCCH format 1, the terminal device may perform joint coding of the data characteristic information and other UCI and perform one of modulation QPSK, BPSK, QAM after the joint coding, thereby ensuring that the new type of SR and other UCI is transmitted using PUCCH format 1.
10 Data characteristic information and other UCI in sequence to generate bit sequence
It should be noted that, the present application may encode the data characteristic information with other UCI to generate a bit sequence, so as to ensure transmission when the new type SR multiplexes other UCI.
For example, taking other UCI including HARQ-ACK information and CSI as an example, the present application may place data characteristic information sequentially after HARQ-ACK information and before CSI.
For another example, in generating the bit sequence, the present application may modify the current ceil (log 2 (k+1)) to ceil (log 2 ((n×k+1))), where N represents the number of types of SR of the new type.
5. Exemplary illustrations of a method of scheduling request Transmission
In connection with the above description, the following embodiments of the present application take interaction between a terminal device and a network device as an example, and an example description is given to a scheduling request transmission method in the embodiments of the present application. The terminal device may be a chip, a chip module, a module, or the like for the execution subject of the method. That is, the method is applied to a terminal device or a terminal device. Correspondingly, for the execution subject of the method, the network device may also be a chip, a chip module or a module, etc. That is, the method is applied to a network device or among network devices.
Fig. 2 is a schematic flow chart of a scheduling request transmission method according to an embodiment of the present application, which specifically includes the following steps:
s210, the terminal equipment sends a scheduling request, wherein the scheduling request is used for reporting the data characteristic requirement of the service.
Correspondingly, the network device receives the scheduling request.
It should be noted that, the details of the "scheduling request", "service", "data feature requirement", etc. are described in the foregoing or other related content, and will not be repeated.
Therefore, the data characteristic requirements of the service are reported to the network through the scheduling request, and the scheduling request enhancement is realized. Therefore, the network can decide how to better schedule uplink resources required by uplink data of the service according to the data characteristic requirements, so that the decision made can be beneficial to avoiding the uplink data from exceeding the time delay requirements, meeting the data volume requirements of the uplink data, improving the reliability of the uplink data transmission and the like.
In some possible implementations, the scheduling request may be sent or received according to a first scheduling request resource corresponding to the data characteristic requirement, the data characteristic requirement being of one or more types.
It should be noted that, in combination with the "scheme one" in the "4" data feature requirement of reporting/feeding back a service to a network through an SR ", the present application introduces a data feature requirement corresponding to an SR resource.
In this way, the terminal device of the present application may send the SR according to the data characteristic requirement for the corresponding SR resource. Correspondingly, the network device can receive the SR according to the SR resources corresponding to the data characteristic requirements, and the data characteristic requirements are reported through the SR.
In some possible implementations, the scheduling request may be sent or received in accordance with a second scheduling request resource, and the scheduling request carries data characteristic information of different types, one type of data characteristic information indicating one type of data characteristic requirement.
It should be noted that, in combination with the "scheme two" in the above "4" of reporting/feeding back the data feature requirement of the service to the network through the SR, "more new types of SRs are introduced in the present application, so that the new types of SRs can support the data feature requirement, and the new types of SRs can carry the data feature information, where the data feature information has one or more types.
In this way, the terminal device can determine the data characteristic information according to the uplink data of the service to be transmitted, one type of data characteristic information is used for indicating one type of data characteristic requirement, and then the SR carrying the data characteristic information is sent according to the SR resource. Correspondingly, the network device can receive the SR resource of the SR to determine the corresponding data feature requirement thereof, so as to report/feed back the data feature requirement through the SR, so that the network device decides how to schedule the uplink resource required by the uplink data according to the data feature requirement, for example, determines the time of issuing the scheduled uplink resource, schedules the appropriate uplink resource, and the like.
In some possible implementations, the same type of data characteristic requirements correspond to different or the same first scheduling request resources.
It should be noted that, in combination with the content that "2) different types of data feature requirements correspond to different SR resources" and "3) different types of data feature requirements correspond to the same SR resource", the present application may introduce a correspondence between different types of data feature requirements and different or the same first scheduling request resources, so that it is possible to distinguish which type of first scheduling request resource is according to the type of the data feature requirement, so that the network device may determine which type of data feature requirement is reported according to the first scheduling request resource.
In some possible implementations, each type of data characteristic requirement includes multiple levels, and different levels of the same type of data characteristic requirement correspond to different first scheduling request resources.
It should be noted that, in combination with the content in the foregoing "8)" that different levels of the data feature requirements of the same type correspond to different first SR resources ", the present application may introduce a correspondence between different levels and different first scheduling request resources, so that it may be implemented which first scheduling request resource is distinguished according to the levels, so that the network device may determine which level is required by the reported data feature according to the first scheduling request resource.
In some possible implementations, different first scheduling request resources are distinguished according to scheduling request resource identifiers, and the different scheduling request resource identifiers correspond to different scheduling request identifiers, and the scheduling request identifiers are used for distinguishing scheduling requests;
different levels of data characteristic requirements of the same type correspond to different scheduling request identifications.
It should be noted that, in connection with the above "10), different levels of data feature requirements of the same type correspond to contents in different schedulingRequestID", and the present application may distinguish different levels of data feature requirements of the same type according to the schedule request identifier.
In some possible implementations, the scheduling request identifiers corresponding to different levels of the same type of data characteristic requirements correspond to the same logical channel.
It should be noted that, in conjunction with the above "11) the contents of the same logical channel" corresponding to the schedulingRequestIDs corresponding to the different levels of the data feature requirements, the present application may enable one LogicalchannelConfig to include multiple SR configurations by including the schedulingRequestIDs corresponding to the different levels in one LogicalchannelConfig, which is different from the conventional one including the schedulingRequestID.
In some possible implementations, the correspondence between the data characteristic requirement and the first scheduling request resource is network configuration, pre-configuration, or protocol specified.
It should be noted that, in connection with the above "12)" how to implement the correspondence between the data feature requirement and the first SR resource ", the present application may implement the correspondence in a network configuration, a pre-configuration, or a protocol specified manner.
In some possible implementations, the type of scheduling request sent by the first scheduling request resource includes a positive scheduling request, a negative scheduling request; or,
the scheduling request sent by the second scheduling request resource belongs to an active scheduling request, the type of the scheduling request comprises a plurality of types, the scheduling requests of different types carry data characteristic information of different or same types, and the scheduling requests of different types support data characteristic requirements of different or same types.
It should be noted that, in combination with the content of the above "scheme two", more types of SRs are introduced for SRs belonging to the active SR, and different types of SRs may support different or same types of data feature requirements, and different types of SRs may carry different or same types of data feature information, so that the data feature requirements are reported through the new types of SRs.
In some possible implementations, different types of scheduling requests sent by the second scheduling request resource correspond to different values of the sequence cyclic shift.
It should be noted that the different new types of SR in combination with the above "4") correspond to different m CS "in the present application, different new types of SRs can be introduced to correspond to different m CS So that different new types of SRs map to the PDCCH sequence.
In some possible implementations, the data characteristic information is modulated by one of: quadrature phase shift keying, QPSK, modulation, binary phase shift keying, BPSK, modulation, quadrature amplitude modulation, QAM, modulation.
In connection with the content of "5) modulation of data characteristic information", the present application can ensure transmission of the data characteristic information by modulation.
In some possible implementations, if the second scheduling request resource is one of PUCCH format 2, PUCCH format 3, PUCCH format 4, different types of data characteristic information generate bit sequences in order.
It should be noted that, in combination with the content in the "different types of in-order generated bit sequences of the data characteristic information of the" 6 ") above, in order to ensure that the new types of SR transmissions carrying the excessive bits and the excessive information types, the present application may generate the different types of in-order generated bit sequences of the data characteristic information.
In some possible implementations, the scheduling request is multiplexed with other uplink control information UCI, the type of other UCI including at least one of hybrid automatic repeat request acknowledgement, HARQ-ACK, information on channel state, CSI, link recovery request, LRR.
It should be noted that, in combination with the content in the above "7) multiplexing of the SR of the new type with other UCI", the present application may multiplex the SR of the new type with other UCI, so as to implement reporting of the SR of the new type and other UCI at the same time.
In some possible implementations, different types of scheduling requests sent by the second scheduling request resource and different types of other UCI are combined to correspond to different values of the sequence cyclic shift.
It should be noted that the combination of the SR of the new type of "8) and other UCI corresponds to m CS By way of example, the present application may introduce different new types of SRs and different types of UCI of the other UCI that jointly correspond to different m CS So that the new type of SR and the other UCI are mapped to the PDCCH sequence.
In some possible implementations, the data characteristic information is jointly encoded with other UCI and one of the modulations QPSK, BPSK, QAM is performed after the joint encoding.
It should be noted that, in combination with the content of "9) performing joint coding on the data feature information and other UCI", the present application may perform joint coding on the data feature information and other UCI, and perform modulation in QPSK, BPSK, QAM after joint coding, so as to ensure transmission when the new type SR multiplexes other UCI.
In some possible implementations, the data characteristic information generates a bit sequence in order with other UCI.
It should be noted that, in combination with the content in the "10) data feature information and other UCI generating bit sequences" described above, the present application may encode the data feature information and other UCI to generate bit sequences, so as to ensure transmission when the new type SR multiplexes other UCI.
In some possible implementations, the type of data characteristic requirements includes at least one of: packet delay budget, buffer size, delay jitter.
In connection with the content of "3, the data feature requirement of the service", since the data feature requirement may be used to indicate the requirement/need of the uplink data passing through the service on at least one of PDB, buffer size, delay jitter, etc., the type of the data feature requirement includes at least one of the following: packet delay budget, buffer size, delay jitter.
4. An illustration of a scheduling request transmission apparatus
The foregoing description of the embodiments of the present application has been presented primarily from a method-side perspective. It will be appreciated that the terminal device or network device, in order to implement the above-described functions, includes corresponding hardware structures and/or software modules that perform the respective functions. Those of skill in the art will readily appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described functionality using different approaches for each particular application, but such implementation is not to be considered as outside the scope of this application.
The embodiment of the application can divide the functional units of the terminal equipment or the network equipment according to the method example. For example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated in one processing unit. The integrated units described above may be implemented either in hardware or in software program modules. It should be noted that, in the embodiment of the present application, the division of the units is schematic, but only one logic function is divided, and another division manner may be implemented in actual implementation.
In the case of using integrated units, fig. 3 is a functional unit block diagram of a scheduling request transmitting apparatus according to an embodiment of the present application. The scheduling request transmitting apparatus 300 includes: a transmitting unit 301.
In some possible implementations, the transmitting unit 301 may be a module unit for processing signals, data, information, and the like, which is not particularly limited.
In some possible implementations, the scheduling request transmitting apparatus 300 may further include a storage unit for storing computer program code or instructions executed by the scheduling request transmitting apparatus 300. The memory unit may be a memory.
In some possible implementations, the scheduling request transmitting apparatus 300 may be a chip or a chip module.
In some possible implementations, the transmitting unit 301 may be integrated in one unit.
For example, the transmitting unit 301 may be integrated in a communication unit. The communication unit may be a communication interface, transceiver circuit, etc.
For another example, the transmitting unit 301 may be integrated in a processing unit. The processing unit may be a processor or a controller, and may be, for example, a baseband processor, a baseband chip, a central processing unit (central processing unit, CPU), a general purpose processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (field programmable gate array, FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various exemplary logical blocks, modules, and circuits described in connection with the present disclosure. The processing unit may also be a combination that implements computing functionality, e.g., comprising one or more microprocessor combinations, a combination of DSPs and microprocessors, etc.
In some possible implementations, the sending unit 301 is configured to perform any step performed by a terminal device, a chip module, etc. in the above-described method embodiments. The following is a detailed description.
A sending unit 301, configured to send a scheduling request, where the scheduling request is used to report a data feature requirement of a service.
Therefore, the data characteristic requirements of the service are reported to the network through the scheduling request, and the scheduling request enhancement is realized. Therefore, the network can decide how to better schedule uplink resources required by uplink data of the service according to the data characteristic requirements, so that the decision made can be beneficial to avoiding the uplink data from exceeding the time delay requirements, meeting the data quantity requirements of the uplink data and the like, and the reliability of the uplink data transmission and the like is improved.
It should be noted that, the specific implementation of each operation in the embodiment shown in fig. 3 may be described in detail in the method embodiment shown in fig. 2, which is not described in detail herein.
In some possible implementations, the scheduling request may be sent according to a first scheduling request resource corresponding to the data characteristic requirement, the data characteristic requirement being of one or more types.
It should be noted that, in combination with the "scheme one" in the "4" data feature requirement of reporting/feeding back a service to a network through an SR ", the present application introduces a data feature requirement corresponding to an SR resource.
In this way, the terminal device of the present application may send the SR according to the data characteristic requirement for the corresponding SR resource. Correspondingly, the network device can receive the SR according to the SR resources corresponding to the data characteristic requirements, and the data characteristic requirements are reported through the SR.
In some possible implementations, the scheduling request may be sent according to a second scheduling request resource, and the scheduling request carries data characteristic information having one or more types, one type of data characteristic information indicating one type of data characteristic requirement.
It should be noted that, in combination with the "scheme two" in the above "4" of reporting/feeding back the data feature requirement of the service to the network through the SR, "more new types of SRs are introduced in the present application, so that the new types of SRs can support the data feature requirement, and the new types of SRs can carry the data feature information, and the data feature information has different types.
In this way, the terminal device can determine the data characteristic information according to the uplink data of the service to be transmitted, one type of data characteristic information is used for indicating one type of data characteristic requirement, and then the SR carrying the data characteristic information is sent according to the SR resource. Correspondingly, the network device can receive the SR resource of the SR to determine the corresponding data feature requirement thereof, so as to report/feed back the data feature requirement through the SR, so that the network device decides how to schedule the uplink resource required by the uplink data according to the data feature requirement, for example, determines the time of issuing the scheduled uplink resource, schedules the appropriate uplink resource, and the like.
In some possible implementations, different types of data characteristic requirements correspond to different or the same first scheduling request resources.
It should be noted that, in combination with the content that "2) different types of data feature requirements correspond to different SR resources" and "3) different types of data feature requirements correspond to the same SR resource", the present application may introduce a correspondence between different types of data feature requirements and different or the same first scheduling request resources, so that it is possible to distinguish which type of first scheduling request resource is according to the type of the data feature requirement, so that the network device may determine which type of data feature requirement is reported according to the first scheduling request resource.
In some possible implementations, each type of data characteristic requirement includes multiple levels, and different levels of the same type of data characteristic requirement correspond to different first scheduling request resources.
It should be noted that, in combination with the content in the foregoing "8)" that different levels of the data feature requirements of the same type correspond to different first SR resources ", the present application may introduce a correspondence between different levels and different first scheduling request resources, so that it may be implemented which first scheduling request resource is distinguished according to the levels, so that the network device may determine which level is required by the reported data feature according to the first scheduling request resource.
In some possible implementations, different first scheduling request resources are distinguished according to scheduling request resource identifiers, and the different scheduling request resource identifiers correspond to different scheduling request identifiers, and the scheduling request identifiers are used for distinguishing scheduling requests;
different levels of data characteristic requirements of the same type correspond to different scheduling request identifications.
It should be noted that, in connection with the above "10), different levels of data feature requirements of the same type correspond to contents in different schedulingRequestID", and the present application may distinguish different levels of data feature requirements of the same type according to the schedule request identifier.
In some possible implementations, the scheduling request identifiers corresponding to different levels of the same type of data characteristic requirements correspond to the same logical channel.
It should be noted that, in conjunction with the above "11) the contents of the same logical channel" corresponding to the schedulingRequestIDs corresponding to the different levels of the data feature requirements, the present application may enable one LogicalchannelConfig to include multiple SR configurations by including the schedulingRequestIDs corresponding to the different levels in one LogicalchannelConfig, which is different from the conventional one including the schedulingRequestID.
In some possible implementations, the correspondence between the data characteristic requirement and the first scheduling request resource is network configuration, pre-configuration, or protocol specified.
It should be noted that, in connection with the above "12)" how to implement the correspondence between the data feature requirement and the first SR resource ", the present application may implement the correspondence in a network configuration, a pre-configuration, or a protocol specified manner.
In some possible implementations, the type of scheduling request sent by the first scheduling request resource includes a positive scheduling request, a negative scheduling request; or,
the scheduling request sent by the second scheduling request resource belongs to an active scheduling request, the type of the scheduling request comprises a plurality of types, the scheduling requests of different types carry data characteristic information of different or same types, and the scheduling requests of different types support data characteristic requirements of different or same types.
It should be noted that, in combination with the content of the above "scheme two", more types of SRs are introduced for SRs belonging to the active SR, and different types of SRs may support different or same types of data feature requirements, and different types of SRs may carry different or same types of data feature information, so that the data feature requirements are reported through the new types of SRs.
In some possible implementations, different types of scheduling requests sent by the second scheduling request resource correspond to different values of the sequence cyclic shift.
It should be noted that the different new types of SR in combination with the above "4") correspond to different m CS "in the present application, different new types of SRs can be introduced to correspond to different m CS So that different new types of SRs map to the PDCCH sequence.
In some possible implementations, the data characteristic information is modulated by one of: quadrature phase shift keying, QPSK, modulation, binary phase shift keying, BPSK, modulation, quadrature amplitude modulation, QAM, modulation.
In connection with the content of "5) modulation of data characteristic information", the present application can ensure transmission of the data characteristic information by modulation.
In some possible implementations, if the second scheduling request resource is one of PUCCH format 2, PUCCH format 3, PUCCH format 4, different types of data characteristic information generate bit sequences in order.
It should be noted that, in combination with the content in the "different types of in-order generated bit sequences of the data characteristic information of the" 6 ") above, in order to ensure that the new types of SR transmissions carrying the excessive bits and the excessive information types, the present application may generate the different types of in-order generated bit sequences of the data characteristic information.
In some possible implementations, the scheduling request is multiplexed with other uplink control information UCI, the type of other UCI including at least one of hybrid automatic repeat request acknowledgement, HARQ-ACK, information on channel state, CSI, link recovery request, LRR.
It should be noted that, in combination with the content in the above "7) multiplexing of the SR of the new type with other UCI", the present application may multiplex the SR of the new type with other UCI, so as to implement reporting of the SR of the new type and other UCI at the same time.
In some possible implementations, different types of scheduling requests sent by the second scheduling request resource and different types of other UCI are combined to correspond to different values of the sequence cyclic shift.
It should be noted that the combination of the SR of the new type of "8) and other UCI corresponds to m CS By way of example, the present application may introduce different new types of SRs and different types of UCI of the other UCI that jointly correspond to different m CS So that the new type of SR and the other UCI are mapped to the PDCCH sequence.
In some possible implementations, the data characteristic information is jointly encoded with other UCI and one of the modulations QPSK, BPSK, QAM is performed after the joint encoding.
It should be noted that, in combination with the content of "9) performing joint coding on the data feature information and other UCI", the present application may perform joint coding on the data feature information and other UCI, and perform modulation in QPSK, BPSK, QAM after joint coding, so as to ensure transmission when the new type SR multiplexes other UCI.
In some possible implementations, the data characteristic information generates a bit sequence in order with other UCI.
It should be noted that, in combination with the content in the "10) data feature information and other UCI generating bit sequences" described above, the present application may encode the data feature information and other UCI to generate bit sequences, so as to ensure transmission when the new type SR multiplexes other UCI.
In some possible implementations, the type of data characteristic requirements includes at least one of: packet delay budget, buffer size, delay jitter.
In connection with the content of "3, the data feature requirement of the service", since the data feature requirement may be used to indicate the requirement/need of the uplink data passing through the service on at least one of PDB, buffer size, delay jitter, etc., the type of the data feature requirement includes at least one of the following: packet delay budget, buffer size, delay jitter.
5. Yet another exemplary illustration of a scheduling request transmitting apparatus
In the case of using integrated units, fig. 4 is a functional unit block diagram of still another scheduling request transmitting apparatus according to an embodiment of the present application. The scheduling request transmitting apparatus 400 includes: a receiving unit 401.
In some possible implementations, the receiving unit 401 may be a module unit for processing signals, data, information, and the like, which is not particularly limited.
In some possible implementations, the scheduling request transmitting apparatus 400 may further include a storage unit for storing computer program code or instructions executed by the scheduling request transmitting apparatus 400. The memory unit may be a memory.
In some possible implementations, the scheduling request transmitting apparatus 400 may be a chip or a chip module.
In some possible implementations, the receiving unit 401 may be integrated in one unit.
For example, the receiving unit 401 may be integrated in a communication unit. The communication unit may be a communication interface, transceiver circuit, etc.
As another example, the receiving unit 401 may be integrated in a processing unit. The processing unit may be a processor or a controller, and may be, for example, a baseband processor, a baseband chip, a central processing unit (central processing unit, CPU), a general purpose processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (field programmable gate array, FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various exemplary logical blocks, modules, and circuits described in connection with the present disclosure. The processing unit may also be a combination that implements computing functionality, e.g., comprising one or more microprocessor combinations, a combination of DSPs and microprocessors, etc.
In some possible implementations, the receiving unit 401 is configured to perform any step performed by a terminal device, a chip module, etc. in the above-described method embodiments. The following is a detailed description.
A receiving unit 401, configured to receive a scheduling request, where the scheduling request is used to report a data feature requirement of a service.
Therefore, the data characteristic requirements of the service are reported to the network through the scheduling request, and the scheduling request enhancement is realized. Therefore, the network can decide how to better schedule uplink resources required by uplink data of the service according to the data characteristic requirements, so that the decision made can be beneficial to avoiding the uplink data from exceeding the time delay requirements, meeting the data quantity requirements of the uplink data and the like, and the reliability of the uplink data transmission and the like is improved.
It should be noted that, the specific implementation of each operation in the embodiment shown in fig. 4 may be described in detail in the method embodiment shown in fig. 2, which is not described in detail herein.
In some possible implementations, the scheduling request may be received according to a first scheduling request resource corresponding to the data characteristic requirement, the data characteristic requirement being of one or more types.
It should be noted that, in combination with the "scheme one" in the "4" data feature requirement of reporting/feeding back a service to a network through an SR ", the present application introduces a data feature requirement corresponding to an SR resource.
In this way, the terminal device of the present application may send the SR according to the data characteristic requirement for the corresponding SR resource. Correspondingly, the network device can receive the SR according to the SR resources corresponding to the data characteristic requirements, and the data characteristic requirements are reported through the SR.
In some possible implementations, the scheduling request may be received in accordance with a second scheduling request resource, and the scheduling request carries data characteristic information of different types, one type of data characteristic information indicating one type of data characteristic requirement.
It should be noted that, in combination with the "scheme two" in the above "4" of reporting/feeding back the data feature requirement of the service to the network through the SR, "more new types of SRs are introduced in the present application, so that the new types of SRs can support the data feature requirement, and the new types of SRs can carry the data feature information, and the data feature information has different types.
In this way, the terminal device can determine the data characteristic information according to the uplink data of the service to be transmitted, one type of data characteristic information is used for indicating one type of data characteristic requirement, and then the SR carrying the data characteristic information is sent according to the SR resource. Correspondingly, the network device can receive the SR resource of the SR to determine the corresponding data feature requirement thereof, so as to report/feed back the data feature requirement through the SR, so that the network device decides how to schedule the uplink resource required by the uplink data according to the data feature requirement, for example, determines the time of issuing the scheduled uplink resource, schedules the appropriate uplink resource, and the like.
In some possible implementations, the same type of data characteristic requirements correspond to different or the same first scheduling request resources.
It should be noted that, in combination with the content that "2) different types of data feature requirements correspond to different SR resources" and "3) different types of data feature requirements correspond to the same SR resource", the present application may introduce a correspondence between different types of data feature requirements and different or the same first scheduling request resources, so that it is possible to distinguish which type of first scheduling request resource is according to the type of the data feature requirement, so that the network device may determine which type of data feature requirement is reported according to the first scheduling request resource.
In some possible implementations, each type of data characteristic requirement includes multiple levels, and different levels of the same type of data characteristic requirement correspond to different first scheduling request resources.
It should be noted that, in combination with the content in the foregoing "8)" that different levels of the data feature requirements of the same type correspond to different first SR resources ", the present application may introduce a correspondence between different levels and different first scheduling request resources, so that it may be implemented which first scheduling request resource is distinguished according to the levels, so that the network device may determine which level is required by the reported data feature according to the first scheduling request resource.
In some possible implementations, different first scheduling request resources are distinguished according to scheduling request resource identifiers, and the different scheduling request resource identifiers correspond to different scheduling request identifiers, and the scheduling request identifiers are used for distinguishing scheduling requests;
different levels of data characteristic requirements of the same type correspond to different scheduling request identifications.
It should be noted that, in connection with the above "10), different levels of data feature requirements of the same type correspond to contents in different schedulingRequestID", and the present application may distinguish different levels of data feature requirements of the same type according to the schedule request identifier.
In some possible implementations, the scheduling request identifiers corresponding to different levels of the same type of data characteristic requirements correspond to the same logical channel.
It should be noted that, in conjunction with the above "11) the contents of the same logical channel" corresponding to the schedulingRequestIDs corresponding to the different levels of the data feature requirements, the present application may enable one LogicalchannelConfig to include multiple SR configurations by including the schedulingRequestIDs corresponding to the different levels in one LogicalchannelConfig, which is different from the conventional one including the schedulingRequestID.
In some possible implementations, the correspondence between the data characteristic requirement and the first scheduling request resource is network configuration, pre-configuration, or protocol specified.
It should be noted that, in connection with the above "12)" how to implement the correspondence between the data feature requirement and the first SR resource ", the present application may implement the correspondence in a network configuration, a pre-configuration, or a protocol specified manner.
In some possible implementations, the type of scheduling request sent by the first scheduling request resource includes a positive scheduling request, a negative scheduling request; or,
the scheduling request sent by the second scheduling request resource belongs to an active scheduling request, the type of the scheduling request comprises a plurality of types, the scheduling requests of different types carry data characteristic information of different or same types, and the scheduling requests of different types support data characteristic requirements of different or same types.
It should be noted that, in combination with the content of the above "scheme two", more types of SRs are introduced for SRs belonging to the active SR, and different types of SRs may support different or same types of data feature requirements, and different types of SRs may carry different or same types of data feature information, so that the data feature requirements are reported through the new types of SRs.
In some possible implementations, different types of scheduling requests sent by the second scheduling request resource correspond to different values of the sequence cyclic shift.
It should be noted that the different new types of SR in combination with the above "4") correspond to different m CS "in the present application, different new types of SRs can be introduced to correspond to different m CS So that different new types of SRs map to the PDCCH sequence.
In some possible implementations, the data characteristic information is modulated by one of: quadrature phase shift keying, QPSK, modulation, binary phase shift keying, BPSK, modulation, quadrature amplitude modulation, QAM, modulation.
In connection with the content of "5) modulation of data characteristic information", the present application can ensure transmission of the data characteristic information by modulation.
In some possible implementations, if the second scheduling request resource is one of PUCCH format 2, PUCCH format 3, PUCCH format 4, different types of data characteristic information generate bit sequences in order.
It should be noted that, in combination with the content in the "different types of in-order generated bit sequences of the data characteristic information of the" 6 ") above, in order to ensure that the new types of SR transmissions carrying the excessive bits and the excessive information types, the present application may generate the different types of in-order generated bit sequences of the data characteristic information.
In some possible implementations, the scheduling request is multiplexed with other uplink control information UCI, the type of other UCI including at least one of hybrid automatic repeat request acknowledgement, HARQ-ACK, information on channel state, CSI, link recovery request, LRR.
It should be noted that, in combination with the content in the above "7) multiplexing of the SR of the new type with other UCI", the present application may multiplex the SR of the new type with other UCI, so as to implement reporting of the SR of the new type and other UCI at the same time.
In some possible implementations, different types of scheduling requests sent by the second scheduling request resource and different types of other UCI are combined to correspond to different values of the sequence cyclic shift.
It should be noted that the combination of the SR of the new type of "8) and other UCI corresponds to m CS By way of example, the present application may introduce different new types of SRs and different types of UCI of the other UCI that jointly correspond to different m CS So that the new type of SR and the other UCI are mapped to the PDCCH sequence.
In some possible implementations, the data characteristic information is jointly encoded with other UCI and one of the modulations QPSK, BPSK, QAM is performed after the joint encoding.
It should be noted that, in combination with the content of "9) performing joint coding on the data feature information and other UCI", the present application may perform joint coding on the data feature information and other UCI, and perform modulation in QPSK, BPSK, QAM after joint coding, so as to ensure transmission when the new type SR multiplexes other UCI.
In some possible implementations, the data characteristic information generates a bit sequence in order with other UCI.
It should be noted that, in combination with the content in the "10) data feature information and other UCI generating bit sequences" described above, the present application may encode the data feature information and other UCI to generate bit sequences, so as to ensure transmission when the new type SR multiplexes other UCI.
In some possible implementations, the type of data characteristic requirements includes at least one of: packet delay budget, buffer size, delay jitter.
In connection with the content of "3, the data feature requirement of the service", since the data feature requirement may be used to indicate the requirement/need of the uplink data passing through the service on at least one of PDB, buffer size, delay jitter, etc., the type of the data feature requirement includes at least one of the following: packet delay budget, buffer size, delay jitter.
6. Example illustration of terminal equipment
Referring to fig. 5, fig. 5 is a schematic structural diagram of a terminal device according to an embodiment of the present application. Wherein the terminal device 500 comprises a processor 510, a memory 520 and a communication bus for connecting the processor 510 and the memory 520.
In some possible implementations, memory 520 includes, but is not limited to, random access memory (random access memory, RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or portable read-only memory (compact disc read-only memory, CD-ROM), memory 520 for storing program code and transmitted data for execution by terminal device 500.
In some possible implementations, the terminal device 500 also includes a communication interface for receiving and transmitting data.
In some possible implementations, the processor 510 may be one or more Central Processing Units (CPUs), which may be a single-core Central Processing Unit (CPU) or a multi-core Central Processing Unit (CPU) in the case where the processor 510 is one.
In some possible implementations, the processor 510 may be a baseband chip, a Central Processing Unit (CPU), a general purpose processor, DSP, ASIC, FPGA, or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof.
In particular implementation, the processor 510 in the terminal device 500 is configured to execute the computer program or instructions 521 stored in the memory 520, and perform the following operations:
And sending a scheduling request, wherein the scheduling request is used for reporting the data characteristic requirement of the service.
Therefore, the data characteristic requirements of the service are reported to the network through the scheduling request, and the scheduling request enhancement is realized. Therefore, the network can decide how to better schedule uplink resources required by uplink data of the service according to the data characteristic requirements, so that the decision made can be beneficial to avoiding the uplink data from exceeding the time delay requirements, meeting the data quantity requirements of the uplink data and the like, and the reliability of the uplink data transmission and the like is improved.
It should be noted that, the specific implementation of each operation may be described in the above-illustrated method embodiment, and the terminal device 500 may be used to execute the method embodiment of the present application, which is not described herein.
7. An illustration of a network device
Referring to fig. 6, fig. 6 is a schematic structural diagram of a network device according to an embodiment of the present application. Wherein the network device 600 comprises a processor 610, a memory 620 and a communication bus for connecting the processor 610, the memory 620.
In some possible implementations, memory 620 includes, but is not limited to, RAM, ROM, EPROM or CD-ROM, memory 620 being used to store related instructions and data.
In some possible implementations, the network device 600 also includes a communication interface for receiving and transmitting data.
In some possible implementations, the processor 610 may be one or more Central Processing Units (CPUs), which may be a single-core Central Processing Unit (CPU) or a multi-core Central Processing Unit (CPU) in the case where the processor 610 is one.
In some possible implementations, the processor 610 may be a baseband chip, a Central Processing Unit (CPU), a general purpose processor, DSP, ASIC, FPGA, or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof.
In some possible implementations, the processor 610 in the network device 600 is configured to execute the computer program or instructions 621 stored in the memory 620 to perform the following operations:
and receiving a scheduling request, wherein the scheduling request is used for reporting the data characteristic requirements of the service.
Therefore, the data characteristic requirements of the service are reported to the network through the scheduling request, and the scheduling request enhancement is realized. Therefore, the network can decide how to better schedule uplink resources required by uplink data of the service according to the data characteristic requirements, so that the decision made can be beneficial to avoiding the uplink data from exceeding the time delay requirements, meeting the data quantity requirements of the uplink data and the like, and the reliability of the uplink data transmission and the like is improved.
It should be noted that, the specific implementation of each operation may be described in the foregoing method embodiment, and the network device 600 may be used to execute the foregoing method embodiment of the present application, which is not described herein again.
8. Other related exemplary illustrations
In some possible implementations, the above method embodiments may be applied in a terminal device. That is, the execution body of the above-described method embodiment may be a terminal device, and may be a chip, a chip module, a module, or the like, which is not particularly limited.
In some possible implementations, the above-described method embodiments may be applied in a network device. That is, the execution body of the above-mentioned method embodiment may be a network device, and may be a chip, a chip module or a module, which is not limited in particular.
The embodiment of the application also provides a chip, which comprises a processor, a memory and a computer program or instructions stored on the memory, wherein the processor executes the computer program or instructions to realize the steps described in the embodiment of the method.
The embodiment of the application also provides a chip module, which comprises a transceiver component and a chip, wherein the chip comprises a processor, a memory and a computer program or instructions stored on the memory, and the processor executes the computer program or instructions to realize the steps described in the embodiment of the method.
The present application also provides a computer-readable storage medium storing a computer program or instructions that, when executed, implement the steps described in the method embodiments above.
Embodiments of the present application also provide a computer program product comprising a computer program or instructions which, when executed, implement the steps described in the method embodiments above.
For the above embodiments, for simplicity of description, the same is denoted as a series of combinations of actions. It will be appreciated by those skilled in the art that the present application is not limited by the illustrated ordering of acts, as some steps may be performed in other order or concurrently in embodiments of the present application. In addition, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred embodiments, and that the acts, steps, modules, units, etc. that are referred to are not necessarily required in the embodiments of the application.
In the foregoing embodiments, the descriptions of the embodiments of the present application are focused on each embodiment, and for a portion of one embodiment that is not described in detail, reference may be made to the related descriptions of other embodiments.
The steps of a method or algorithm described in the embodiments of the present application may be implemented in hardware, or may be implemented by executing software instructions by a processor. The software instructions may be comprised of corresponding software modules that may be stored in RAM, flash memory, ROM, erasable programmable read-only memory (erasable programmable ROM, EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disk, a removable disk, a compact disc read-only memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may be located in a terminal device or a management device. The processor and the storage medium may reside as discrete components in a terminal device or management device.
Those of skill in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application may be implemented, in whole or in part, in software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.
The respective apparatuses and the respective modules/units included in the products described in the above embodiments may be software modules/units, may be hardware modules/units, or may be partly software modules/units, and partly hardware modules/units. For example, for each device or product applied to or integrated on a chip, each module/unit included in the device or product may be implemented in hardware such as a circuit, or at least part of the modules/units may be implemented in software program, where the software program runs on a processor integrated inside the chip, and the rest (if any) of the modules/units may be implemented in hardware such as a circuit; for each device and product applied to or integrated in the chip module, each module/unit contained in the device and product can be realized in a hardware manner such as a circuit, different modules/units can be located in the same component (such as a chip, a circuit module and the like) or different components of the chip module, or at least part of the modules/units can be realized in a software program, the software program runs on a processor integrated in the chip module, and the rest (if any) of the modules/units can be realized in a hardware manner such as a circuit; for each device, product, or application to or integrated with the terminal device, each module/unit included in the device may be implemented in hardware such as a circuit, and different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components in the terminal device, or at least some modules/units may be implemented in a software program, where the software program runs on a processor integrated within the terminal device, and the remaining (if any) part of the modules/units may be implemented in hardware such as a circuit.
The foregoing embodiments have been provided for the purpose of illustrating the embodiments of the present application in further detail, and it should be understood that the foregoing embodiments are merely illustrative of the embodiments of the present application and are not intended to limit the scope of the embodiments of the present application, and any modifications, equivalents, improvements, etc. made on the basis of the technical solutions of the embodiments of the present application are included in the scope of the embodiments of the present application.
Claims (38)
1. A method for transmitting a scheduling request, comprising:
and sending a scheduling request, wherein the scheduling request is used for reporting the data characteristic requirement of the service.
2. The method of claim 1, wherein the scheduling request is sent according to a first scheduling request resource corresponding to the data characteristic requirement, the data characteristic requirement being of one or more types; or,
the scheduling request is sent according to a second scheduling request resource, and the scheduling request carries data characteristic information, wherein the data characteristic information is of one or more types, and one type of the data characteristic information is used for indicating one type of the data characteristic requirement.
3. The method of claim 2, wherein different types of the data characteristic requirements correspond to different or the same first scheduling request resources.
4. The method of claim 2, wherein the data characteristic requirements of the same type comprise a plurality of levels, and different levels of the data characteristic requirements of the same type correspond to different ones of the first scheduling request resources.
5. The method of claim 4, wherein different ones of the first scheduling request resources are distinguished according to scheduling request resource identifiers, and wherein different ones of the scheduling request resource identifiers correspond to different ones of the scheduling request identifiers, the scheduling request identifiers being used to distinguish the scheduling requests;
different levels of the data characteristic requirements of the same type correspond to different ones of the scheduling request identifications.
6. The method of claim 5, wherein the scheduling request identifiers corresponding to different levels of the data characteristic requirements of the same type correspond to the same logical channel.
7. The method of claim 2, wherein the correspondence between the data characteristic requirement and the first scheduling request resource is network configuration, pre-configuration, or protocol specified.
8. The method of claim 2, wherein the type of scheduling request sent by the first scheduling request resource comprises a positive scheduling request, a negative scheduling request; or,
the scheduling request sent by the second scheduling request resource belongs to an active scheduling request, the type of the scheduling request comprises a plurality of types, the scheduling requests of different types carry the data characteristic information of different or same types, and the scheduling requests of different types support the data characteristic requirements of different or same types.
9. The method of claim 2, wherein different types of the scheduling request sent by the second scheduling request resource correspond to different values of the sequence cyclic shift.
10. The method of claim 2, wherein the data characteristic information is modulated by one of: quadrature phase shift keying, QPSK, modulation, binary phase shift keying, BPSK, modulation, quadrature amplitude modulation, QAM, modulation.
11. The method of claim 2, wherein if the second scheduling request resource is one of PUCCH format 2, PUCCH format 3, PUCCH format 4, different types of the data characteristic information generate bit sequences in sequence.
12. The method of claim 2, wherein the scheduling request is multiplexed with other uplink control information UCI, and wherein the other UCI type includes at least one of hybrid automatic repeat request acknowledgement, HARQ-ACK, information, channel state information, CSI, and link recovery request, LRR.
13. The method of claim 12, wherein the different types of scheduling requests sent by the second scheduling request resource and the different types of UCI are combined to correspond to different values of the sequence cyclic shift.
14. The method of claim 12 wherein the data characteristic information is jointly encoded with the other UCI and one of the modulations QPSK, BPSK, QAM is performed after the joint encoding.
15. The method of claim 12, wherein the data characteristic information and the other UCI generate a bit sequence in order.
16. The method according to any of claims 1-15, wherein the type of data characteristic requirements comprises at least one of: packet delay budget, buffer size, delay jitter.
17. A method for transmitting a scheduling request, comprising:
And receiving a scheduling request, wherein the scheduling request is used for reporting the data characteristic requirement of the service.
18. The method of claim 17, wherein the scheduling request is received in accordance with a first scheduling request resource corresponding to the data characteristic requirement, the data characteristic requirement being of one or more types; or,
the scheduling request is received according to a second scheduling request resource, and the scheduling request carries data characteristic information, the data characteristic information being of one or more types, one type of the data characteristic information being used to indicate one type of the data characteristic requirement.
19. The method of claim 18, wherein different types of the data characteristic requirements correspond to different or the same first scheduling request resources.
20. The method of claim 18, wherein the data characteristic requirements of a same type comprise a plurality of levels, and different levels of the data characteristic requirements of a same type correspond to different ones of the first scheduling request resources.
21. The method of claim 20, wherein different ones of the first scheduling request resources are distinguished based on scheduling request resource identifiers, and wherein different ones of the scheduling request resource identifiers correspond to different ones of the scheduling request identifiers, the scheduling request identifiers being used to distinguish the scheduling requests;
Different levels of the data characteristic requirements of the same type correspond to different ones of the scheduling request identifications.
22. The method of claim 21, wherein the scheduling request identifiers corresponding to different levels of the data characteristic requirements of the same type correspond to the same logical channel.
23. The method of claim 18, wherein the correspondence between the data characteristic requirement and the first scheduling request resource is network configuration, pre-configuration, or protocol specified.
24. The method of claim 18, wherein the type of scheduling request received by the first scheduling request resource comprises a positive scheduling request, a negative scheduling request; or,
the scheduling request received by the second scheduling request resource belongs to an active scheduling request, the type of the scheduling request comprises a plurality of types, the scheduling requests of different types carry the data characteristic information of different or same types, and the scheduling requests of different types support the data characteristic requirements of different or same types.
25. The method of claim 18, wherein different types of the scheduling requests sent by different second scheduling request resources correspond to different values of the sequence cyclic shift.
26. The method of claim 18, wherein the data characteristic information is modulated by one of: quadrature phase shift keying, QPSK, modulation, binary phase shift keying, BPSK, modulation, quadrature amplitude modulation, QAM, modulation.
27. The method of claim 18, wherein if the second scheduling request resource is one of PUCCH format 2, PUCCH format 3, PUCCH format 4, different types of the data characteristic information generate bit sequences in sequence.
28. The method of claim 18, wherein the scheduling request is multiplexed with other uplink control information UCI, and wherein the other UCI type includes at least one of hybrid automatic repeat request acknowledgement, HARQ-ACK, information, channel state information, CSI, and link recovery request, LRR.
29. The method of claim 28, wherein the different types of scheduling requests sent by the second scheduling request resource and the different types of UCI are combined to correspond to different values of the sequence cyclic shift.
30. The method of claim 28 wherein the data characteristic information is jointly encoded with the other UCI types and one of the modulations QPSK, BPSK, QAM is performed after the joint encoding.
31. The method of claim 28, wherein at least one of the data characteristic information and the other UCI generate a bit sequence.
32. The method according to any of claims 17-31, wherein the type of data characteristic requirements comprises at least one of: packet delay budget, buffer size, delay jitter.
33. A scheduling request transmission apparatus, comprising:
and the sending unit is used for sending a scheduling request, wherein the scheduling request is used for reporting the data characteristic requirement of the service.
34. A scheduling request transmission apparatus, comprising:
and the receiving unit is used for receiving a scheduling request, wherein the scheduling request is used for reporting the data characteristic requirement of the service.
35. A terminal device comprising a processor, a memory and a computer program or instructions stored on the memory, characterized in that the processor executes the computer program or instructions to carry out the steps of the method according to any one of claims 1-16.
36. A network device comprising a processor, a memory and a computer program or instructions stored on the memory, wherein the processor executes the computer program or instructions to implement the steps of the method of any one of claims 17-32.
37. A chip comprising a processor and a communication interface, wherein the processor performs the steps of the method of any of claims 1-16 or 17-32.
38. A computer readable storage medium, characterized in that it stores a computer program or instructions which, when executed, implement the steps of the method of any one of claims 1-16 or 17-32.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210873196.XA CN117500072A (en) | 2022-07-22 | 2022-07-22 | Scheduling request transmission method and device, terminal equipment, network equipment and chip |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210873196.XA CN117500072A (en) | 2022-07-22 | 2022-07-22 | Scheduling request transmission method and device, terminal equipment, network equipment and chip |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117500072A true CN117500072A (en) | 2024-02-02 |
Family
ID=89676975
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210873196.XA Pending CN117500072A (en) | 2022-07-22 | 2022-07-22 | Scheduling request transmission method and device, terminal equipment, network equipment and chip |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117500072A (en) |
-
2022
- 2022-07-22 CN CN202210873196.XA patent/CN117500072A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN115553005A (en) | Side feedback resource configuration method, terminal equipment and network equipment | |
| CN115242355B (en) | Wireless communication method and device | |
| CN114788204B (en) | Method, device and equipment for determining state of HARQ (hybrid automatic repeat request) process | |
| EP4210408A1 (en) | Method and device used in node for wireless communication | |
| WO2021217378A1 (en) | Wireless communication method, terminal device and network device | |
| CN116097600A (en) | Sounding reference signal configuration method and device, terminal and network equipment | |
| WO2023273869A1 (en) | Method and apparatus for determining priority of channel state information report, and related device | |
| CN114391230A (en) | Method and device for multiplexing transmission of uplink control information | |
| WO2022141106A1 (en) | Method and device for repeatedly transmitting data channel | |
| WO2022036523A1 (en) | Data transmission method and device | |
| CN113498179B (en) | Method and device used in node of wireless communication | |
| CN117500072A (en) | Scheduling request transmission method and device, terminal equipment, network equipment and chip | |
| WO2024012561A1 (en) | Method and apparatus for determining demodulation reference signal port, terminal device, and network device | |
| WO2024017233A1 (en) | Communication method and apparatus, terminal device, network device, and chip | |
| WO2022205390A1 (en) | Information processing method and terminal device | |
| WO2023208198A1 (en) | Communication method and apparatus, terminal device, network device, and chip | |
| WO2023232038A1 (en) | Communication methods and apparatus, terminal device, network device, and chip | |
| WO2023279399A1 (en) | Sidelink transmission resource determination method and sending method and apparatus, device, and medium | |
| WO2022246824A1 (en) | Wireless communication method, terminal device, and network device | |
| US20240040573A1 (en) | Information transmission method, apparatus, and system | |
| WO2023245426A1 (en) | Wireless communication methods, terminal devices and network devices | |
| WO2023123399A1 (en) | Wireless communication method, terminal device, and network device | |
| WO2023138622A1 (en) | Resource configuration method and apparatus, network device and terminal device | |
| WO2023070375A1 (en) | Resource indication method, terminal device, and network device | |
| CN117015040A (en) | Frequency domain resource determining method and device, terminal equipment, network equipment and chip |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |