Apple Patent Exploring 5G Real-Time Extended Reality Service Provides Efficient Resource Allocation Scheduling for XRs

CheckCitation/SourcePlease click:arstechnica

(XR Navigation Network 2024年03月01日）作为具有高速率、低时延和大连接等特点的新一代宽带移动通信技术，5G通讯是实现人机物互联的网络基础，尤其是对正在发展中的XR而言。

在名为“Scheduling request (sr) enhancements for 5g real-time extended reality (xr) services”的专利申请中，appleA scheduling request enhancement for 5G real-time extended reality services is then proposed to provide efficient resource allocation and scheduling for XR.

Apple notes that XR service characteristics are associated with periodicity, various streams, jitter, latency, and reliability. Effective resource allocation and scheduling for XR service characteristics can be provided through scheduling request enhancements used for 5G real-time extended reality services. Among other things, efficient resource allocation and scheduling can be provided using mechanisms such as semi-persistent scheduling SPS, configuration authorization, dynamic scheduling, and dynamic authorization.

In one embodiment, an example of traffic processing specific to XR services may include a buffer status reporting BSR process used by a user equipment (UE) to provide information about the amount of data the UE wishes to send to the base station in the UL direction. Based on the amount of data on the terminal waiting to be transmitted in the UL direction over the Physical Uplink Shared Channel (PUSCH), the base station may allocate a minimum amount of UL grant based on the availability of PUSCH resources.

The BSR procedure may use either a 5-bit or an 8-bit buffer size field to inform the BTS about the amount of data that the terminal is requesting from the BTS for the UL grant.The 5-bit buffer size field may be used as described in Table 6.1.3.1-1 of 3GPP Technical Specification (TS) 38.321, and the 8-bit buffer size field may be used as described in Table 6.1.3.1-2 of 3GPP TS 38.321.

After the MAC Protocol Data Unit PDU is established, the total amount of data may correspond to the data of all LCHs in an LCH group. In an example, after the LCH prioritization process, the buffer size field may have a value of zero. The amount of data may be expressed in a number of bytes. a 5-bit buffer size field may correspond to a short BSR format, and an 8-bit buffer size field may correspond to a long BSR format.

Accordingly, the invention describes solutions that can provide SR indications, using, for example, SR multiplexing, payload cascading, and the like for SR indication optimization.

FIG. 1 shows an example wireless communication system. As shown in FIG. 1, the wireless communication system 100 may include base stations 102 and 104 and a UE 106.

The UE 106 may have data associated with a stream associated with an XR service sent in the UL direction using a PUSCH. Accordingly, the UE may send an SR and be used to allocate one or more RBs. the RBs correspond to the data associated with the stream to be sent in the UL direction to the LCH or LCGThe amount of data associated with the stream associated with the XR service of the The amount of data to be sent in the UL direction from the base station 102 or 104 requesting the RBs may be expressed using one or more bits.

The UE 106 may have data associated with XR service traffic corresponding to audio streams and/or data streams at a constant bit rate. Thus, the UE 106 may use a unit SR buffer size field for the SR indication.

Similarly, for XR service traffic corresponding to a pause/control flow, which may have a constant bit rate, the UE 106 may use a single SR buffer size field to represent the SR indication. Upon receiving a single bit SR indication, the base station may allocate RBs based on a predetermined number of data bytes to be sent in the UL direction. The predetermined number of data bytes may be determined based on a constant bit rate consistent with the XR service traffic type.

However, the XR service traffic associated with the video stream may have a variable bit rate, so the UE 106 may use more than one bit in the SR indication, such as 5 bits or 8 bits. Alternatively, the XR service traffic associated with the video stream may follow a distribution of data. The SR indication may be optimized by indicating the buffer data size as a quantized buffer data size. The buffer data size may be quantized using a uniform quantizer and/or a non-uniform quantizer.

Figure 2 illustrates an example of SR multiplexing. Physical uplink control channel (PUCCH) resource sets or PUCCH resource lists may be used for SRs. as described herein, different streams may be associated with different SRs. Thus, each of the different SRs may be associated with a different amount of data or payload size. Alternatively, the UE may send data to a UL direction associated with one or more different streams.

In one embodiment, a first portion of the SR split into two parts may include a bitmap indicative of the presence or absence of an SR, and a second portion of the SR split into two parts may include a payload of connections to each of the SRs associated with the integrated SR. For example, a bitmap value "10" may indicate the presence of a separate SR-1, a bitmap value "11" may indicate the presence of SR-1 and SR-2, and so forth.

As shown in Figure 200, SR Config-3 206 contains a list of PUCCH resources PUCCH-5 206a, PUCCH-6 206b and PUCCH-7 206c. Based on the flow and/or XR service scenario, and the payload size, the UE 106 may select the PUCCH resource PUCCH-5 206a for the SR- 3210.

Thus, when the UE 106 multiplexes multiple SRs, the UE may multiplex the SRs at multiple stages. so as described herein, in addition to the 1-bit SRs, the SRs may use a plurality of bits to report more granular or additional information corresponding to the LCHs or the LCGs associated with the SRs.

Alternatively, the plurality of SRs may be mapped as a group to construct a composite SR. each SR mapped to the integral SR may be a 1-bit SR, and the integral SR may convey more information by expanding the number of bits of each 1-bit SR.

In one embodiment, a set of 1-bit SRs may be associated with the same LCH or LCG, and different SRs of a set of 1-bit SRs may be associated with different priorities, different XR service traffic flows, and/or different QoS flows, thereby allowing for finer-grained prioritization and/or identification/correlation of XR service traffic flows and improved resource allocation.

For example, a set of SRs may be associated with an LCH associated with multiple QoS flows, and each QoS flow may use its own SRs.Alternatively, the SR priority of each LCH or LCG may be assigned by the network in such a way that an LCH or LCG with subflows that require further prioritization may utilize a separate SR resource for each subflow.

FIG. 3 illustrates that QoS streams are mapped to the LCHs of various sub-streams of each individual SR based on the integrated SRs and the corresponding integrated SRs.As shown in FIG. 300, various QoS streams, such as QoS stream 1302, QoS stream 2304, QoS stream 3306, QoS stream 4308, QoS stream 5310, QoS stream 6312, QoS stream 7314, QoS stream 8316, and QoS flow 9318, may be mapped to different LCHs.

For example, QoS stream 1302, QoS stream 2304, and QoS stream 3306 may be mapped to LCH LCH 1320. similarly, QoS stream 4308 and QoS stream 5310 may be mapped to LCH LCH 322, and QoS stream 6312 and QoS stream 7314 may be mapped to LCH LCH 324.

Here, QoS streams 1-7 are sub-streams of their respective LCHs.QoS stream 8 316 and QoS stream 9 318 are mapped to LCH LCH4 326 and LCH LCH5 328 as separate streams, not as sub-streams in SR.

As shown in FIG. 300, there may be multiple SRs depending on the data to be sent in the UL direction. therefore, an SR scheduling request 330 may be generated by the terminals associated with LCH 1320 and LCH 2322.

The scheduling request 330 may be based on a plurality of SRs, the SRs corresponding to various sub-streams, such as QoS stream 1 302, QoS stream 2 304, and QoS stream 3 306 associated with LCH LCH1 320, and QoS stream 4 308 and QoS stream 5 310 associated with LCH LCH2 322.

The scheduling request 330 may be identified based on an ID of schedulingRequestResourceId, where schedulingRequestResourceId identifies a scheduling request configuration associated with one or more of the plurality of LCHs.

The scheduling request 332 may be based on a plurality of SRs, with the SRs corresponding to various sub-streams, such as the QoS stream 6 312 and the QoS stream 7 314 associated with the LCH LCH 324. sR 334 and sR 336 correspond to the LCH LCH 326 and 328, respectively, but instead of being integrated with the other SRs corresponding to the other streams, are sent as separate sRs 342 and 344, respectively. Including individual PUCCH resources identified as schedulingRequestResourceId 6 342a and schedulingRequestResourceId 7 344a.

Each QoS flow mapped to the LCH may have the same or a different priority, and its corresponding SR in the integrated SR may be sorted based on the priority associated with the QoS flow.

FIG. 8 illustrates a flowchart of operations that may be performed by a user device.

At 802, the UE may recognize multiple flows corresponding to the data to be sent in the UL direction of the uplink. The data to be sent in the UL direction will have different priorities depending on the respective XR service flow and/or QoS flow.

In 804, the UE may map a subset of the plurality of streams to a plurality of logical channels of a plurality of logical channels. For example, a subset of streams of the plurality of streams (may be mapped to LCH LCH1.

At 806,,the UE may multiplex two or more scheduling request SRs into a single integrated SR to form a set of SRs that are used to request one or more physical uplink control channel PUCCH resources. Each SR included in the integrated SR may correspond to a scheduling request for data associated with at least one stream of a subset of the plurality of streams.

FIG. 9 illustrates an example flowchart of operations that may be performed by a base station.

At 902, the base station may send to the user equipment a configuration describing a scheduling request SR priority associated with at least one logical channel of the plurality of logical channels. The at least one logical channel may be associated with a plurality of streams mapped to it or one or more streams.

At 904, the base station may receive a single scheduling request from the UE for requesting one or more physical uplink control channel resources corresponding to the plurality of streams or the one or more streams of the at least one logical channel. As described herein, said integrated SR may comprise a plurality of SRs, and each of the SRs included in said integrated SR may correspond to an SR for UL transmission of data associated with each of said plurality of streams. accordingly, a first SR and a second SR included in the integrated SR have different priorities based on their respective streams.

Thus, various embodiments described by the invention may provide improvements or enhancements to SR in various XR service scenarios.

The Apple patent application titled "Scheduling request (sr) enhancements for 5g real-time extended reality (xr) services" was originally filed in August 2022 and recently published by the U.S. Patent and Trademark Office. Patent and Trademark Office.

Generally speaking, after a U.S. patent application is examined, it will be automatically published 18 months from the filing date or priority date, or it will be published within 18 months from the filing date at the request of the applicant. Note that publication of a patent application does not mean that the patent is approved. After a patent application is filed, the USPTO requires actual review, which can take anywhere from 1 to 3 years.

In addition, this is only a patent application, which does not necessarily mean that it will be adopted, and it is also uncertain whether it will be actually commercialized and the actual results of its application.