Wireless communication method and base station for extended reality services

Abstract

The present disclosure provides a method of wireless communication that can be performed in a base station. The base station configures a search space for downlink control signaling for an extended reality (XR) service in a radio resource configuration. The radio resource configuration includes a semi-persistent scheduling (SPS) or a configured grant (CG) configuration. The base station provides the radio resource configuration and transmits a downlink control signal in the search space.

Description

Technical Field

[0001] This disclosure relates to the field of communication systems, and more particularly to wireless communication methods, user equipment (UE), and base stations for Extended Reality (XR) services. Background Technology

[0002] Wireless communication systems, such as the aforementioned third-generation (3G) mobile phone standards and technologies, are well-known. These 3G standards and technologies were developed by the Third Generation Partnership Project (3GPP). Third-generation wireless communication was primarily developed to support macrocell mobile phone communication. Communication systems and networks have evolved towards broadband and mobile systems. In cellular wireless communication systems, user equipment (UE) connects to a radio access network (RAN) via a radio link. The RAN includes a set of base stations (BS) that provide radio links to the UE located in cells covered by the base stations, and interfaces connecting to a core network (CN) that provides overall network control. As is known, the RAN and CN each perform their respective functions related to the overall network. The 3rd Generation Partnership Project has developed a system called Long Term Evolution (LTE), or Evolved Universal Mobile Telecommunication System Territorial Radio Access Network (E-UTRAN), for mobile access networks, in which one or more macro cells are supported by base stations called evolved NodeBs (eNBs). More recently, LTE is evolving towards a system called 5G or New Radio (NR), in which one or more cells are supported by base stations called gNBs.

[0003] The fifth-generation (5G) wireless communication system is designed to provide enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC) services. In 5G or NR, support for eMBB, URLLC, and mMTC was introduced in release 15 and enhanced in releases 16 and 17.

[0004] Extended Reality (XR) and cloud gaming services are important media applications supported by 5G. Within 3GPP, a series of research projects have been completed and found that XR services possess some unique characteristics in terms of these service features, which current 5G systems may not support well. Some characteristics of XR services are listed below:

[0005] ● Variable-size video frames: The video stream is the most important data stream in XR services. A video stream contains a continuous sequence of video frames. Each video frame is an image encoded / compressed using a different codec mechanism (e.g., H.264 / H.265 / H.266, AV1, or an audio / video coding standard known as AVS) for efficient storage and transmission. Typically, three main frame / image types are used in encoding (i.e., I-frames, P-frames, and B-frames). Even for frames of the same type, the data size is different for each frame. During transmission, essentially, a frame can be segmented into a group of data packets. However, variable-size video frames can result in at least one variable-size data packet or a variable number of data packets for different frames.

[0006] Real-time, high data rate, and low latency: Clearly, XR service is a real-time service, and also features high data rate and low latency. For a potential service, the guaranteed data rate is approximately 100 megabits per second (Mbps), with a frame rate of 60 to 120 Hz and a video resolution of 8K. The downlink (DL) data rate can exceed 100 Mbps, and the uplink (UL) data rate can reach 50 Mbps per UE, with low latency (e.g., 2.5 milliseconds). For communication reliability, the packet error rate for UL and DL transmissions should be less than 10%. -4 and 10 -5 .

[0007] ● Non-integer periodicity: According to the XR service service model agreed upon in the XR Study Item (SI) of Release 17 (Rel-17) in 3GPP RAN1, the video stream of the XR service can be configured at 30, 60, 90, or 120 frames per second (FPS). Therefore, the XR frames will arrive at the RAN quasi-periodically at their respective periods of 1 / 60, 1 / 90, or 1 / 120 of a second, referred to as non-integer periodicity. Semi-Persistent Scheduling (SPS) or Configured Grant (CG) for periodic services can reduce control signaling overhead and can be a good option for serving XR services. However, the current SPS / CG periodicity configuration cannot match the non-integer periodicity of the XR service.

[0008] ● Jitter: Due to varying delays caused by XR data encoding, rendering, and network transmission, XR services exhibit jitter effects on the arrival time of data packets. This jitter effect makes the arrival time of specific data packets at XR service receiving devices (such as gNBs or UEs) unpredictable. Following the convention in the RAN1 XR SI study, a truncated Gaussian distribution is used to simulate the jitter of XR services. The jitter range is defined as a baseline value of [-4, 4] milliseconds (i.e., from -4 milliseconds to 4 milliseconds), with optional values ​​of [-5, 5] milliseconds (i.e., from -5 milliseconds to 5 milliseconds). Due to this jitter, it is evident that the performance of the SPS / CG cannot adequately support XR services, as the periodicity of the configuration cannot accommodate the random jitter effect.

[0009] ● Multiple Data Streams: Based on the XR service service model agreed upon in the Rel-17 XR study item (SI) in 3GPP RAN1, there are three options for the multi-stream model of downlink (DL) XR services:

[0010] ■Option 1: I-frame + P-frame;

[0011] ■Option 2: Video + Audio / Data; and

[0012] ■Option 3: Field of Vision (FOV) + ​​Omnidirectional Flow.

[0013] In Option 1, the I-frame is referred to as an intra-coded frame or independent frame, and the P-frame is referred to as a predicted frame. In the XR service, the XR service stream of Option 1 includes I-frame streams and P-frame streams. In Option 2, video, audio, and data represent the video stream, audio stream, and data stream in the XR service stream, respectively. In the XR service, the XR service stream of Option 2 includes video streams and audio / data streams. In Option 3, FOV represents the field of view stream in the XR service stream. In the XR service, the XR service stream of Option 3 includes FOV streams and omnidirectional streams.

[0014] The multi-stream model for uplink (UL) XR services also has three options:

[0015] ●Option 2: Attitude / Control + Aggregated Scene, Video, Data and Audio;

[0016] ●Option 3A: Attitude / Control + Aggregated Scene and Video Streams + Aggregated Audio and Data Streams; and

[0017] ●Option 3B: Attitude / Control + I-stream of video + P-stream of video.

[0018] In Options 2, 3A, and 3B of the UL XR service, attitude / control refers to the attitude and control information flow of the XR service stream. The term "aggregated scene, video, data, and audio" refers to the aggregated streams of scene, video, data, and audio.

[0019] XR services have both DL and UL components, both of which are periodic or quasi-periodic. The current specification lacks a mechanism to align these uplink and downlink transmissions. Besides waking up to receive or transmit services, the modem in the UE can enter a low-power state to conserve battery. If DL and UL services are received and transmitted at different times, the modem needs to wake up multiple times to handle them, requiring additional state transition time and power consumption. Furthermore, the current Discontinuous Reception (DRX) related timer operation can prolong UE wake-up time during DL or UL activity. Discontinuous DL and UL services result in longer UE wake-up times, leading to increased UE power consumption.

[0020] Therefore, a method is needed to improve at least the UE power efficiency or XR service functionality. Summary of the Invention

[0021] One object of this disclosure is to provide a user equipment (UE), a base station, and a wireless communication method.

[0022] According to a first aspect, one embodiment of the present invention provides a wireless communication method executable in a base station, comprising:

[0023] Configure a search space for downlink control signaling in the radio resource configuration, wherein the radio resource configuration includes semi-persistent scheduling (SPS) or configuration granting (CG) configuration;

[0024] Provide the aforementioned wireless resource configuration; and

[0025] Send downlink control signals in the search space.

[0026] According to a second aspect, one embodiment of the present invention provides a base station including a processor configured to invoke and run a computer program stored in a memory to cause a device equipped with the processor to perform the disclosed method.

[0027] According to a third aspect, one embodiment of the present invention provides a wireless communication method executable in a user equipment (UE), comprising:

[0028] Receive radio resource configuration, wherein the radio resource configuration includes a search space configuration for downlink control signaling, and the radio resource configuration includes semi-persistent scheduling (SPS) or configuration granting (CG) configuration; and

[0029] Receive downlink control signals in the search space.

[0030] According to a fourth aspect, one embodiment of the present invention provides a user equipment (UE) including a processor configured to invoke and run a computer program stored in a memory to cause a device equipped with the processor to perform the disclosed method.

[0031] According to a fifth aspect, one embodiment of the present invention provides a wireless communication method executable in a base station, comprising:

[0032] The threshold for obtaining the Quality of Service (QoS) factor;

[0033] Measure the value of the QoS factor;

[0034] Determine whether the measured value of the QoS factor exceeds an acceptable range defined based on the threshold of the QoS factor; and

[0035] When the measured value of the QoS factor exceeds the acceptable range, one or more specific functions are reconfigured.

[0036] According to a sixth aspect, one embodiment of the present invention provides a base station including a processor configured to invoke and run a computer program stored in a memory to cause a device equipped with the processor to perform the disclosed method.

[0037] The disclosed method can be implemented in a chip. The chip may include a processor configured to call and run a computer program stored in memory, causing a device on which the chip is mounted to perform the disclosed method.

[0038] The disclosed method can be programmed as computer-executable instructions stored in a non-transitory computer-readable medium. When loaded into a computer, the non-transitory computer-readable medium instructs the computer's processor to execute the disclosed method.

[0039] The non-transitory computer-readable medium may include at least one of the following: hard disk, CD-ROM, optical storage device, magnetic storage device, read-only memory, programmable read-only memory, erasable programmable read-only memory, EPROM, electrically erasable programmable read-only memory, and flash memory.

[0040] The disclosed method can be programmed into a computer program product that enables a computer to execute the disclosed method.

[0041] The disclosed method can be programmed into a computer program, causing a computer to execute the disclosed method.

[0042] Beneficial effects

[0043] At least one embodiment of the present invention provides a method that enables a UE to monitor the Physical Downlink Control Channel (PDCCH) during the time period of the SPS and CG resources, in order to support more flexible resource allocation.

[0044] At least one embodiment of the present invention provides a method that enables a gNB to notify a UE not to monitor multiple PDCCHs used for XR service retransmission, thereby reducing the UE's power consumption.

[0045] At least one embodiment of the present invention provides a method for handling jitter in NR, thereby facilitating more flexible radio resource scheduling. Attached Figure Description

[0046] To more clearly illustrate the embodiments or related technologies of this disclosure, the following drawings will be briefly described in the embodiments. Obviously, the drawings are merely some embodiments of this disclosure. Those skilled in the art can obtain other drawings based on these drawings without disregarding the aforementioned prerequisites.

[0047] Figure 1 A schematic diagram showing an example of a telecommunications system is provided.

[0048] Figure 2 A schematic diagram illustrating an embodiment of a network used for the disclosed wireless communication method is shown.

[0049] Figure 3 A schematic diagram illustrating a wireless communication method for defining a search space according to an embodiment of the present disclosure is shown.

[0050] Figure 4 A schematic diagram is shown illustrating a wireless communication method for reconfiguring specific functions of an XR service according to embodiments of the present disclosure.

[0051] Figure 5 A schematic diagram is shown illustrating an example of canceling retransmissions based on a delay time.

[0052] Figure 6 A schematic diagram is shown illustrating an example of canceling retransmissions based on the Block Error Rate (BLER).

[0053] Figure 7 A schematic diagram is shown illustrating an example of canceling retransmissions based on packet importance.

[0054] Figure 8 A schematic diagram shows an example of reconfiguring jitter-related special functions for a downlink flow displayed as an XR service.

[0055] Figure 9 A schematic diagram shows an example of reconfiguring jitter-related special functions for an uplink stream displayed as an XR service.

[0056] Figure 10 A schematic diagram showing a wireless communication system according to an embodiment of the present disclosure is shown. Detailed Implementation

[0057] Referring to the accompanying drawings, the technical aspects, structural features, implementation objectives, and effects of the embodiments of this disclosure are described in detail below. Specifically, the terminology used in the embodiments of this disclosure is only used to describe the purpose of the particular embodiment and is not intended to limit this disclosure.

[0058] This invention discloses a wireless communication method for processing XR services within extended reality (XR) services. XR services may include augmented reality (AR), virtual reality (VR), or mixed reality (MR).

[0059] Reference Figure 1 A telecommunications system including UE 10a, UE 10b, base station (BS) 20a and network entity equipment 30 performs the disclosed method according to embodiments of the present disclosure. Figure 1 For illustrative purposes only and not restrictive, the system may include more UE, BS, and CN entities. The diagram shows connections between devices and device components using lines and arrows. UE 10a may include processor 11a, memory 12a, and transceiver 13a. UE 10b may include processor 11b, memory 12b, and transceiver 13b. Base station 20a may include processor 21a, memory 22a, and transceiver 23a. Network entity device 30 may include processor 31, memory 32, and transceiver 33. Each of processors 11a, 11b, 21a, and 31 may be configured to implement the suggested functions, procedures, and / or methods described in the description. The layers of the wireless interface protocol may be implemented in processors 11a, 11b, 21a, and 31. Each of memories 12a, 12b, 22a, and 32 actually stores various programs and information to operate the connected processor. Each of the transceivers 13a, 13b, 23a, and 33 is actually coupled to a connected processor to transmit and / or receive wireless or wired signals. The UE 10a can communicate with the UE 10b via a sidechain. The base station 20a can be one of an eNB, gNB, or other types of wireless nodes, and can configure wireless resources for the UE 10a and UE 10b.

[0060] The network entity device 30 may be a node in the CN. The CN may include an LTE CN or a fifth-generation core network (5G Core, 5GC), which includes User Plane Function (UPF), Session Management Function (SMF), 5G Core Network Access and Mobility Management Function (AMF), Unified Data Management (UDM), Policy Control Function (PCF), Control Plane (CP) / User Plane (UP) Separation (CUPS), Authentication Server Function (AUSF), Network Slice Selection Function (NSSF), and Network Exposure Function (NEF).

[0061] Examples of UEs described in this description may include either UE 10a or UE 10b. Examples of base stations described in this description may include base station 20a. Uplink (UL) transmission of control signals or data may be a transmission operation from the UE to the base station. Downlink (DL) transmission of control signals or data may be a transmission operation from the base station to the UE. DL control signals may include Downlink Control Information (DCI) or Radio Resource Control (RRC) signals from the base station to the UE.

[0062] Figure 2This is a model of a 5G system-supported XR service transmission network. UE 10 is a 5G terminal capable of supporting XR services and XR applications, and can be referred to as a client, client terminal, or XR client. gNB 20 is a 5G radio node. The gNB 20 communicates with the UE 10 via the NR Uu interface and provides the UE with NR user plane and control plane protocol termination. The gNB 20 is connected to the 5GC 300 via the NG interface. AMF 30b is the AMF in the 5GC 300 (i.e., the 5G core network). DN 40 is a data network (DN) 40, where an XR server 41 providing XR services is located. The DN 40 can provide network operator services, internet access, or third-party services. The XR server 41 may include a processor 411, a memory 412, and a transceiver 413. The processor 411 can be configured to implement the XR service-related functions, procedures, and / or methods described in the specification. The radio interface protocol layer can be implemented in the processor 411. The memory 412 actually stores various programs and information to operate the connected processor. The transceiver 413 is actually coupled to the connected processor to send and / or receive wireless or wired signals.

[0063] Each of the processors 411, 11a, 11b, 21a, and 31 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. Each of the memories 412, 12a, 12b, 22a, and 32 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and / or other storage devices. Each of the transceivers 413, 13a, 13b, 23a, and 33 may include baseband circuitry and radio frequency (RF) circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented by modules, programs, functions, entities, etc., that perform the functions described. The modules may be stored in memory and executed by the processor. The memories may be implemented internally or externally to the processor, wherein they may be communicatively coupled to the processor in various ways known in the art. The device performing the wireless communication method may be a transmitting device that sends an XR service stream to a receiving device or a receiving device that receives the XR service stream. The XR service stream may include one or more XR streams of the XR service. For example, the device performing the wireless communication method may include the gNB 20, the XR server 41 in the data network 40, or the UE. That is, the XR server 41 in the data network 40 may operate as a transmitting device performing the wireless communication method in some XR service transmission scenarios, while the UE 10 receives the XR service stream from the transmitting device as the receiving device. Similarly, the UE 10 may perform the wireless communication method as a transmitting device in some XR service transmission scenarios, while the XR server 41 receives the XR service stream from the transmitting device as the receiving device. In addition, the transmitting device may include an intermediate device between the UE 10 and the XR server 41. The UE 10 may include embodiments of UE 10a or UE 10b. The gNB 20 may include an embodiment of the base station 20a. Note that although the gNB 20 and AMF / 5GC 30b are described as examples in the description, the wireless communication method can be performed by a base station, such as another gNB, eNB, a base station integrating eNB and gNB, or a base station using 5G technology. The AMF / 5GC 30b may include another network entity of the 5GC.

[0064] One or more steps (or modules) in the embodiments of this disclosure may be implemented as computer programs, instructions, or software modules and stored in the memory of the transmitting device, or implemented as circuits or hardware modules in the processor of the transmitting device, or implemented as IC chips, circuits, or plug-ins of the transmitting device.

[0065] The video stream of the XR service will be encoded and compressed quasi-periodically in frames at respective frame periods of 1 / 60, 1 / 90, or 1 / 120 of a second. Since the transmitting device may divide the video stream of the XR service into multiple transmission units, encapsulate and transmit each of the transmission units as a transmission data packet for transmission over the network, the transmission mechanism of the XR service is actually based on data packets rather than frames. The size of each of the data packets may be variable, the number of data packets may be variable, and they can be configured based on one or more parameters of the QoS requirements and characteristics of the XR service, such as Packet Delay Budget (PDB), Packet Error Rate (PER), Packet Loss Rate (PLR), Frame Error Rate, Frame Delay Budget, Resolution, Frame Rate, and / or Data Rate.

[0066] Reference Figure 3 and Figure 4 The UE 10 and gNB 20 execute an embodiment of the disclosed method and initiate XR services.

[0067] The gNB 20 configures a search space for downlink control signaling for Extended Reality (XR) services in its radio resource configuration, wherein the radio resource configuration includes Semi-Persistent Scheduling (SPS) or Configuration Granting (CG) configuration (201). The XR service is initiated for the UE 10 and the XR server 41.

[0068] The gNB 20 provides the radio resource configuration to the UE 10 during downlink transmission (203). The UE 10 performs discontinuous reception DRX. The UE 10 enters an active time to receive the radio resource configuration (204). The radio resource configuration includes a configuration of the search space for downlink control signaling for the XR service. For example, the radio resource configuration may be provided to the UE 10 in RRC signals or DCI.

[0069] The gNB 20 sends a downlink control signal (205) to the UE 10 in the search space. The UE 10 enters an active time to receive the downlink control signal (206) in the search space. For example, the downlink control signal may include an RRC signal or a DCI for the XR service.

[0070] Example 1:

[0071] In the current NR specification, when DRX is configured, regardless of whether the SPS resource is during the DRX ON period (also known as the active period) or the DRX OFF period (during the active period), the UE 10 needs to receive and decode the Physical Downlink Shared Channel (PDSCH) on the configured SPS resource. However, the UE 10 does not need to monitor the PDCCH during the same time. Since the UE 10 must wake up during the time period of the SPS resource, it is beneficial for the UE 10 to be able to monitor the PDCCH during the time period of the SPS resource, because more PDCCH monitoring opportunities can be used to transmit signaling related to the jitter-specific technology. Therefore, embodiments of the disclosed method enable the UE 10 to monitor the PDCCH during the time periods of the SPS resource and the CG resource. The embodiments of the disclosed method include the following features:

[0072] ● For SPS or CG configurations, a search space corresponding to the SPS or CG is configured.

[0073] ● For each SPS or CG configured with a corresponding search space, the time of the search space can be configured or defined as a part of the activity time during which the UE 10 can monitor the PDCCH according to the configured search space.

[0074] The duration of the search space can be:

[0075] ●The duration is the same as and completely overlaps with the duration of the SPS or CG resource;

[0076] ● A portion of the duration of the SPS or CG resource; or

[0077] ● Longer than, but including, the duration of the SPS or CG resources.

[0078] In one embodiment, the duration of the search space is configured or defined as a portion of the UE's active time monitoring the Physical Downlink Control Channel (PDCCH). For the search space configuration, one option is a static configuration based on RRC messages. Based on current specifications, an element of "SearchSpace" or "SearchSpaceId" in the current specifications can be introduced into the SPS or CG configuration element in the RRC message to represent the search space used for PDCCH monitoring. Alternatively, the search space corresponding to this "SearchSpaceId" can be defined and configured in other elements. Table 1 shows an example of an SPS configuration with the element "SPS-SearchSpace" and "SearchSpaceId" based on an RRC message.

[0079] Table 1: SPS Configuration Information Elements

[0080]

[0081] To enable the gNB 20 to allocate radio resources more flexibly in the time domain, when the UE 10 is able to monitor the PDCCH during the SPS or CG resource time period, the gNB 20 can send DCI on the PDCCH to allocate radio resources for XR services, reconfigure functions, or provide instructions.

[0082] ■ The downlink control signal dynamically activates one or more additional active periods during the discontinuous reception DRX shutdown time of the user equipment (UE). In this case, one or more search spaces can be configured during those additional active periods.

[0083] ■ The downlink control signal is a dynamically transmitted downlink allocation used to allocate Physical Downlink Shared Channel (PDSCH) resources to a UE (e.g., UE 10).

[0084] ■ The downlink control signal is a dynamically sent uplink grant used to allocate Physical Uplink Shared Channel (PUSCH) resources to a UE (e.g., UE 10).

[0085] ■ The downlink control signal dynamically changes one or more configuration parameters of the SPS, including the periodicity or start time of the SPS, skipping of SPS reception, and frequency domain resource allocation of the SPS. In response to the downlink control signal for skipping SPS reception, the UE 10 skips downlink signal reception in the SPS following the downlink control signal.

[0086] ■ The downlink control signal dynamically changes one or more configuration parameters of the CG, including the periodicity or start time of the CG, skipping of CG transmission, and frequency domain resource allocation of the CG. In response to the downlink control signal for skipping CG transmission, the UE 10 skips uplink signal transmission in the CG following the downlink control signal.

[0087] ■ The downlink control signal dynamically instructs the UE 10 to receive or skip downlink transmissions in one or more subsequent SPSs.

[0088] ■ The downlink control signal dynamically instructs the UE 10 to either transmit an uplink transmission in one or more subsequent CG transmissions or to skip the uplink transmission.

[0089] ■The downlink control signal dynamically activates or deactivates one or more SPSs.

[0090] ■The downlink control signal dynamically activates or deactivates one or more CGs.

[0091] Example 2:

[0092] XR services are real-time and interactive. If the data packets of the XR service are delayed too much during transmission, the data carried by the delayed data packets is meaningless to the receiver of the XR service. In examples where the packet delay budget (PDB) of the XR service data packets is very limited, it is more reasonable not to retransmit the data packets when the XR service data packet transmission fails. However, according to the current NR specification, in this case, when the timer drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is running, the UE 10 must wake up to monitor the PDCCH during that time, which wastes a significant amount of UE power. Therefore, embodiments of the disclosed method are disclosed, enabling the gNB 20 to notify the UE 10 not to monitor the Physical Downlink Control Channel (PDCCH) for XR service retransmissions.

[0093] Reference Figure 4The gNB 20 obtains a threshold (301) for the Quality of Service (QoS) factor of the Extended Reality (XR) service. The XR service is initiated for the UE 10 and the XR server 41. In one embodiment, the QoS factor includes jitter, and the threshold of the QoS factor includes a jitter threshold. In another embodiment, the QoS factor includes latency, and the threshold of the QoS factor includes a Packet Delay Budget (PDB) threshold. In another embodiment, the QoS factor includes Block Error Rate (BLER), and the threshold of the QoS factor includes a BLER threshold. In yet another embodiment, the QoS factor includes a combination of various QoS factors (e.g., a weighted sum), and the threshold of the QoS factor includes a threshold of the combination.

[0094] The gNB 20 measures the value (303) of the QoS factor of the XR service.

[0095] The gNB 20 determines whether the measured value of the QoS factor exceeds the tolerable range defined by the threshold based on the QoS factor (305).

[0096] When the measured value of the QoS factor exceeds the tolerable range, the gNB 20 reconfigures one or more specific functions of the XR service (307). The reconfiguration in step 307 may include activating / deactivating, enabling / disabling, asserting / releasing, or configuring / reconfiguring specific functions.

[0097] In one embodiment, the one or more specific functions include one or more of the following: multiple discontinuous reception DRX configurations, physical downlink control channel (PDCCH) monitoring mode, PDCCH skipping, multiple semi-persistent scheduling (SPS) configurations, and multiple configuration granting (CG) configurations.

[0098] In one embodiment, the reconfiguration of one or more specific functions of the XR service includes: sending an indication that retransmission of the Hybrid Automatic Repeat Request (HARQ) process of the XR service is disabled when the measured value of the QoS factor exceeds the tolerable range. For example, when the measured value of the QoS factor exceeds the tolerable range, the gNB 20 sends an indication to the UE 10 that retransmission of the HARQ process of the XR service is disabled. In one embodiment, the indication instructs the user equipment UE not to start or restart the timer drx-RetransmissionTimerDL for monitoring the discontinuous reception DRX activity time of the physical downlink control channel PDCCH. In another embodiment, the indication instructs the user equipment UE not to start or restart the timer drx-RetransmissionTimerUL for monitoring the discontinuous reception DRX activity time of the physical downlink control channel PDCCH.

[0099] The gNB 20 sends an indication to the UE 10 not to monitor multiple PDCCHs used for HARQ / packet retransmission for the XR service by sending a downlink allocation or uplink grant DCI. In other words, the indication can be included in the DCI.

[0100] ●For the downlink allocation sent from the gNB 20, the UE 10 accordingly receives the Physical Downlink Shared Channel (PDSCH) and does not send an ACK / NACK to the gNB 20, nor does it start or restart the timer drx-RetransmissionTimerDL used to monitor the activity time of the multiple Physical Downlink Control Channels (PDCCHs).

[0101] ● For the uplink grant sent from the gNB 20, the UE 10 correspondingly sends the Physical Uplink Shared Channel (PUSCH) and does not start or restart the timer drx-RetransmissionTimerUL used to monitor the activity time of the multiple PDCCHs.

[0102] Some examples in different use cases are detailed below.

[0103] Example 1 - Retransmission cancellation based on packet delay budget (PDB):

[0104] Reference Figure 5The gNB 20 obtains the configured PDB, corresponding offset, and latency (A101) of one or more packets for the XR service. For example, when setting up the XR service for a UE (e.g., UE 10), the configured PDB and / or the corresponding offset can be configured to the gNB 20. For example, the gNB 20 can obtain the PDB from the QoS allocated by the 5GC AMF (e.g., AMF 30b).

[0105] The gNB 20 can obtain the latency of one or more data packets of the XR service in different ways.

[0106] For the downlink of the XR service, the gNB 20 can measure the latency of one or more packets on its own and / or obtain the latency of one or more packets from the 5GC (e.g., the AMF 30b).

[0107] For the uplink of the XR service, the gNB 20 can obtain the delay time of one or more data packets from the UE (e.g., the UE 10) by receiving measurement reports, buffer status reports (BSR), uplink control information (UCI), or scheduling requests (SR) from the UE (e.g., the UE 10).

[0108] The gNB 20 determines whether the latency of one or more packets of the XR service is greater than the tolerable range (A102) defined by the configured PDB based on the corresponding offset. For example, the tolerable range is the configured PDB plus the corresponding offset or the configured PDB minus the corresponding offset.

[0109] If the delay time of one or more packets of the XR service is greater than the configured PDB adjusted according to the corresponding offset, the gNB 20 may cancel the retransmission of the HARQ process of one or more packets (A103).

[0110] If the delay time of one or more packets of the XR service is not greater than the configured PDB adjusted according to the corresponding offset, the gNB 20 may use downlink allocation or uplink authorization to perform normal retransmission for the HARQ process of one or more packets (A104).

[0111] Example 2 - Retransmission cancellation based on block error rate (BLER):

[0112] Reference Figure 6 The gNB 20 obtains the configured BLER threshold, corresponding offset, and BLER (B101) for one or more packets of the XR service. For example, when setting up the XR service for a UE (e.g., the UE 10), the configured BLER threshold and / or the corresponding offset can be configured to the gNB 20. For example, the gNB 20 can obtain the BLER threshold from the QoS allocated by the 5GC AMF (e.g., AMF 30b).

[0113] The gNB 20 can obtain the BLER of one or more data packets of the XR service in different ways.

[0114] For the downlink of the XR service, the gNB 20 can measure the BLER of one or more packets on its own and / or obtain the BLER of one or more packets from the 5GC (e.g., the AMF 30b).

[0115] For the uplink of the XR service, the gNB 20 can obtain the BLER of one or more data packets from the UE (e.g., the UE 10) by receiving measurement reports, BSRs, UCIs, or SRs from the UE (e.g., the UE 10).

[0116] The gNB 20 determines whether the BLER of one or more packets of the XR service is less than the configured BLER threshold (B102) adjusted according to the corresponding offset. For example, the tolerable range is the configured BLER threshold plus the corresponding offset or the configured BLER threshold minus the corresponding offset.

[0117] If the BLER of one or more packets of the XR service is less than the configured BLER threshold adjusted according to the corresponding offset, the gNB 20 may cancel the retransmission of the HARQ process for one or more packets (B103).

[0118] If the BLER of one or more packets of the XR service is not less than the configured BLER threshold adjusted according to the corresponding offset, the gNB 20 may use downlink allocation or uplink authorization to perform normal retransmission for the HARQ process of one or more packets (B104).

[0119] Reference Figure 7The gNB 20 obtains the configured importance threshold, corresponding offset, and importance (C101) of one or more packets for the XR service. For example, when setting up the XR service for a UE (e.g., the UE 10), the configured importance threshold and / or the corresponding offset can be configured to the gNB 20. For example, the gNB 20 can obtain the importance threshold from the QoS allocated by 5GCAMF (e.g., AMF 30b).

[0120] The gNB 20 can obtain the importance of one or more packets of the XR service in different ways. The importance of the one or more packets reflects the priority of the XR stream to which the one or more packets belong among the multiple XR streams of the XR service.

[0121] For the downlink of the XR service, the gNB 20 can independently measure the importance of one or more packets and / or obtain the importance of one or more packets from the 5GC (e.g., the AMF 30b).

[0122] For the uplink of the XR service, the gNB 20 can obtain the importance of one or more data packets from the UE (e.g., the UE 10) by receiving measurement reports, BSRs, UCIs, or SRs from the UE (e.g., the UE 10).

[0123] The gNB 20 determines whether the importance of one or more packets of the XR service is less than a configured importance threshold (C102) adjusted according to the corresponding offset. For example, the tolerable range is the configured importance threshold plus the corresponding offset or the configured importance threshold minus the corresponding offset.

[0124] If the importance of one or more packets of the XR service is less than the importance threshold of the configuration adjusted according to the corresponding offset, the gNB 20 may cancel the retransmission of the HARQ process for one or more packets (C103).

[0125] If the importance of one or more packets of the XR service is not less than the importance threshold of the configuration adjusted according to the corresponding offset, the gNB 20 may use downlink allocation or uplink authorization to perform normal retransmission for the HARQ process of one or more packets (C104).

[0126] Example 3:

[0127] The jitter characteristics of XR services significantly affect the efficiency of resource scheduling in the gNB 20 and power saving in the UE 10. However, for certain types of UEs (e.g., the UE 10), a certain level of jitter may be acceptable because certain mechanisms can be implemented in other ways, such as having more jitter buffering capabilities in the application layer. In this case, the RAN can have more flexibility in considering the jitter issue so that the RAN can more effectively schedule radio resources to transmit the XR service data. Embodiments of the disclosed method for handling jitter in NR include:

[0128] ● Configure one or more data streams for XR services to withstand jitter thresholds and / or offsets;

[0129] ● Measure the jitter of the one or more data streams;

[0130] ● Compare the measured jitter with the tolerable jitter threshold plus or minus the offset; and

[0131] ●Activate / deactivate, enable / disable, assert / release, or configure / reconfigure specific functions for the XR service.

[0132] The reconfiguration in step 307 may include activating / deactivating, enabling / disabling, asserting / releasing, or configuring / reconfiguring specific functions. The reconfiguration of one or more specific functions of the XR service is performed via Radio Resource Control (RRC) signals or Downlink Control Information (DCI). The tolerable jitter threshold plus the offset defines the tolerable range. Alternatively, the tolerable jitter threshold minus the offset defines the tolerable range.

[0133] The one or more jitter-specific functions include one or more of the following: multiple discontinuous reception DRX configurations, physical downlink control channel (PDCCH) monitoring mode, PDCCH skipping, multiple semi-persistent scheduling (SPS) configurations, and multiple configuration grant (CG) configurations.

[0134] Figure 8 An embodiment of the disclosed method for downlink flow in XR services is shown.

[0135] The gNB 20 is configured to withstand jitter thresholds and / or offsets (401a or 401b) for one or more data streams of the XR service.

[0136] In one embodiment, the gNB 20 can obtain the tolerable jitter threshold as configuration information (401b) for XR service establishment or reconfiguration from the AMF (e.g., the AMF 30b) via NG-AP protocol messages on the NG interface between the gNB 20 and the AMF.

[0137] In one embodiment, the gNB 20 can obtain the tolerable jitter threshold (401a) from the UE 10 via a Radio Resource Control (RRC) message on the Uu interface between the gNB 20 and the UE 10.

[0138] The gNB 20 measures the jitter (403) of one or more data streams of the XR service. In another embodiment, the jitter is obtained from the Mobility Management Function (AMF). Alternatively, the jitter is obtained from a Measurement Report, Buffer Status Report (BSR), Uplink Control Information (UCI), or Scheduling Request (SR) of the User Equipment (UE).

[0139] Optionally, the gNB 20 pre-configures one or more jitter-specific functions (402) to the UE 10.

[0140] The gNB 20 determines whether the measured jitter is greater than the tolerable jitter threshold plus the configured offset for one or more data streams of the XR service. When the measured jitter is greater than the tolerable jitter threshold plus the configured offset, the gNB 20 activates or configures / reconfigures the jitter-specific function.

[0141] The gNB 20 determines whether the measured jitter is less than the tolerable jitter threshold minus the configured offset for one or more data streams of the XR service. When the measured jitter is less than the tolerable jitter threshold minus the configured offset, the gNB 20 disables or releases / reconfigures the jitter-specific functionality.

[0142] In one embodiment, the gNB 20 activates / deactivates or releases or configures / reconfigures the jitter-specific function (404a) to the UE 10 via an RRC message.

[0143] In one embodiment, the gNB 20 activates / deactivates or releases or configures / reconfigures the jitter-specific function (404b) to the UE 10 via downlink control information (DCI) on the PDCCH.

[0144] Figure 9 An embodiment of the disclosed method for the uplink flow of the XR service is shown.

[0145] The gNB 20 is configured at the gNB 20 to withstand jitter thresholds and / or offsets (501a or 501b) for one or more data streams of the XR service.

[0146] In one embodiment, the gNB 20 can obtain the tolerable jitter threshold as configuration information (501b) for XR service establishment or reconfiguration from the AMF (e.g., the AMF 30b) via NG-AP protocol messages on the NG interface between the gNB 20 and the AMF.

[0147] In one embodiment, the gNB 20 can obtain the tolerable jitter threshold (501a) from the UE 10 via a Radio Resource Control (RRC) message on the Uu interface between the gNB 20 and the UE 10.

[0148] The gNB 20 configures the UE 10 to measure the jitter (503) of one or more data streams of the XR service.

[0149] Optionally, the gNB 20 pre-configures one or more jitter-specific functions (502) to the UE 10.

[0150] The UE 10 measures the jitter (504) of one or more data streams of the XR service.

[0151] The UE 10 reports the jitter of the measurement of the one or more data streams to the gNB 20.

[0152] In one embodiment, the UE 10 reports the measured jitter (505a) of the one or more data streams of the XR service to the gNB 20 via an RRC message.

[0153] In one embodiment, the UE 10 reports the measured jitter (505b) of the one or more data streams of the XR service to the gNB 20 via BSR, UCI, or SR.

[0154] The gNB 20 compares the measured jitter with the tolerable jitter threshold plus or minus the offset (506).

[0155] The gNB 20 determines whether the measured jitter is greater than the tolerable jitter threshold plus the configured offset for one or more data streams of the XR service. When the measured jitter is greater than the tolerable jitter threshold plus the configured offset, the gNB 20 activates or configures / reconfigures the jitter-specific function.

[0156] The gNB 20 determines whether the measured jitter is less than the tolerable jitter threshold minus the configured offset for one or more data streams of the XR service. When the measured jitter is less than the tolerable jitter threshold minus the configured offset, the gNB 20 disables or releases / reconfigures the jitter-specific functionality.

[0157] In one embodiment, the gNB 20 activates / deactivates or releases or configures / reconfigures the jitter-specific function to the UE 10 via an RRC message (507a).

[0158] In one embodiment, the gNB 20 activates / deactivates or releases or configures / reconfigures the jitter-specific function to the UE 10 via downlink control information (DCI) on the PDCCH (507b).

[0159] Figure 10 This is a block diagram of an example system 700 for wireless communication according to an embodiment of this disclosure. The embodiments described herein can be implemented into the system using any suitably configured hardware and / or software. Figure 10 The system 700 is shown, including a radio frequency (RF) circuit 710, a baseband circuit 720, a processing unit 730, a memory / memory 740, a display 750, a camera 760, a sensor 770, and an input / output (I / O) interface 780, all coupled to each other as shown.

[0160] The processing unit 730 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose and special-purpose processors, such as a graphics processor and an application processor. The processor may be coupled to the memory / repository and configured to execute instructions stored in the memory / repository to enable various applications and / or operating systems to run on the system.

[0161] The wireless control functions may include, but are not limited to, signal modulation, encoding, decoding, and radio frequency shifting. In some embodiments, the baseband circuitry can provide communication compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuitry can support communication with 5G NR, LTE, Evolved Universal Terrestrial Radio Access Network (EUTRAN) and / or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), and Wireless Personal Area Networks (WPAN). Embodiments of the baseband circuitry configured to support wireless communication using more than one wireless protocol may be referred to as multi-mode baseband circuitry. In various embodiments, the baseband circuitry 720 may include circuitry for processing signals that are not strictly considered to be at the baseband frequency. For example, in some embodiments, the baseband circuitry may include circuitry for processing signals having an intermediate frequency (IF) between the baseband frequency and the radio frequency.

[0162] In various embodiments, the system 700 may be a mobile computing device, such as, but not limited to, a laptop, tablet, netbook, ultrabook, or smartphone. In various embodiments, the system may have more or fewer components and / or a different architecture. Where appropriate, the methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

[0163] The embodiments described in this disclosure are combinations of technologies / processes that can be employed in 3GPP specifications for creating a final product.

[0164] If the software functional unit is implemented and used and sold as a product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions proposed in this disclosure can be implemented essentially or partially as the software product. Alternatively, a portion of the technical solution that is beneficial to the prior art can be implemented as the software product. The software product in the computer is stored in a storage medium, including multiple commands for a computing device (such as a personal computer, server, or network device) to execute all or part of the steps disclosed in the embodiments of this disclosure. The storage medium includes a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other media capable of storing program code.

[0165] While this disclosure has been described in conjunction with the most practical and preferred embodiments, it should be understood that this disclosure is not limited to the disclosed embodiments, but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.

Claims

1. A wireless communication method for jitter processing that can be executed in a base station, characterized in that, include: Receive jitter from one or more data streams from the Access and Mobility Management Function (AMF); Configure jitter measurement configurations for one or more data streams to the user equipment (UE); Jitter from receiving one or more data streams from the UE; Radio resource configuration is activated or deactivated by downlink control information (DCI) on the physical downlink control channel (PDCCH). or Based on the jitter, radio resource configuration is configured or reconfigured for the UE via Radio Resource Control (RRC) messages. The method includes: The measured jitter is compared to an acceptable jitter threshold plus or minus an offset; When the measured jitter exceeds the tolerable jitter threshold plus the configured offset, activate or configure / reconfigure the jitter-specific function; and When the measured jitter is less than the tolerable jitter threshold minus the configured offset, the jitter-specific function is disabled or released / reconfigured; The specific jitter function includes one or more of the following: Multiple discontinuous DRX configurations, Physical Downlink Control Channel (PDCCH) Monitoring Mode PDCCH skipped Multiple semi-persistent scheduling (SPS) configurations and multiple configuration-authorized CG configurations.

2. The method according to claim 1, characterized in that, The wireless resource configuration is a combination of multiple CG configurations.

3. A base station, comprising: A processor configured to invoke and run a computer program stored in memory to cause a device equipped with the processor to perform the method of any one of claims 1 to 2.

4. A chip, comprising: A processor configured to invoke and run a computer program stored in memory to cause a device on which the chip is mounted to perform the method of any one of claims 1 to 2.

5. A computer-readable storage medium storing a computer program, wherein the computer program causes a computer to perform the method of any one of claims 1 to 2.

6. A computer program product comprising a computer program, wherein the computer program causes a computer to perform the method of any one of claims 1 to 2.

7. A wireless communication method for jitter processing executable in a user equipment (UE), characterized in that, include: Jitter measurement configuration for receiving one or more data streams from a base station; The jitter of one or more data streams is measured according to the configuration described; Report the jitter of one or more data streams measured to the base station; Receive: a) Radio resource configuration or reconfiguration via Radio Resource Control (RRC) messages, or b) Activation or deactivation of radio resource configuration via Downlink Control Information (DCI) on the Physical Downlink Control Channel (PDCCH) from the base station; Specifically, when the measured jitter exceeds the tolerable jitter threshold plus the configured offset, the jitter-specific function is activated or configured / reconfigured by the base station; and When the measured jitter is less than the tolerable jitter threshold minus the configured offset, the jitter-specific function is disabled or released / reconfigured by the base station; The specific jitter function includes one or more of the following: Multiple discontinuous DRX configurations, Physical Downlink Control Channel (PDCCH) Monitoring Mode PDCCH skipped Multiple semi-persistent scheduling (SPS) configurations and multiple configuration-authorized CG configurations.

8. The method according to claim 7, characterized in that, The wireless resource configuration is a combination of multiple CG configurations.

9. A user equipment (UE), comprising: A processor configured to invoke and run a computer program stored in memory to cause a device equipped with the processor to perform the method of any one of claims 7 to 8.

10. A chip, comprising: A processor configured to invoke and run a computer program stored in memory to cause a device on which the chip is mounted to perform the method of any one of claims 7 to 8.

11. A computer-readable storage medium storing a computer program, wherein the computer program causes a computer to perform the method of any one of claims 7 to 8.

12. A computer program product comprising a computer program, wherein the computer program causes a computer to perform the method of any one of claims 7 to 8.

Images