CN119013936A - Base station, user equipment and augmented reality processing method - Google Patents

Abstract

The present disclosure provides a base station, a user equipment (UE) and an extended reality (eXtended reality, XR) processing method. The UE initiates an XR service and reports the XR traffic model of the XR service to the base station. The XR service includes one or more XR streams. The base station configures radio resources for the XR service based on the XR traffic pattern. The XR traffic pattern associated with the XR stream is specified by traffic pattern parameters, which include frame rate settings representing the XR stream and packet intervals between packets in a packet burst of the XR stream. Configuring the configured radio resources for the XR service includes at least one of a time domain configuration or a frequency domain configuration.

Description

Base station, user equipment and augmented reality processing method

Technical Field

The present disclosure relates to the field of communication systems, and more particularly, to a base station, a user equipment, and an Extended Reality (XR) processing method.

Background

Wireless communication systems, such as third generation (3G) mobile telephone standards and technologies are well known. These 3G standards and technologies have been developed by the Third Generation partnership project (Third Generation)

PARTNERSHIP PROJECT,3 GPP). The third generation wireless communications have generally been developed to support macrocell mobile telephone communications. Communication systems and networks have evolved towards broadband and mobile systems. In a cellular wireless communication system, a User Equipment (UE) is connected to a radio access network (Radio Access Network, RAN) through a radio link. The RAN includes a set of Base Stations (BSs) that provide radio links for the UEs located in cells covered by the Base stations, and an interface to a Core Network (CN) that provides overall Network control. As is appreciated, the RAN and CN each perform respective functions for the overall network. The third generation partnership project has developed the so-called long term evolution (Long Term Evolution, LTE) system, an evolved universal mobile telecommunications system terrestrial radio access network (Evolved UMTS Terrestrial Radio Access Network, E-UTRAN), as a mobile access network in which one or more macro cells are supported by base stations called evolved node bs or enbs. Recently, LTE is further moving towards the so-called 5G or New air interface (New

Radio, NR) system development in which one or more cells are supported by base stations called gnbs.

Technical problem

The 5G wireless Communication system is designed to provide enhanced mobile broadband (Enhanced Mobile Broadband, eMBB), ultra-reliable low-latency Communication (Ultra Reliable and Low Latency Communication, URLLC), and large-scale machine type Communication (MASSIVE MACHINE TYPE Communication, mMTC) services. In 5G or new air interface (NR), the functions supporting emmbb, URLLC, and mMTC were introduced in 15 th edition and enhanced in 16 th and 17 th edition.

Extended Reality (XR) and cloud gaming services are important media applications for 5G implementations. In 3GPP, a series of research projects have been completed, and XR services are found to have some unique features in terms of the traffic pattern, while the current 5G systems may not support XR services well. Some features of XR traffic are listed below:

● Video streams for XR services may be configured to have variable packet sizes and periodicity, such as per second

30. 60, 90 Or 120 frames (FRAMES PER second, FPS). Thus, the XR frames will arrive at the Radio Access Network (RAN) quasi-periodically with a respective periodicity of 1/60, 1/90 or 1/120 seconds, which is referred to as a non-integer periodicity. Semi-persistent scheduling (Semi- -

PERSISTENT SCHEDULING, SPS) or Configured Grant (CG) may reduce control signaling overhead, which is a good choice for serving XR traffic in the RAN. However, what is

The configuration of the current SPS/CG periodicity may not match the non-integer periodicity of the XR traffic. ● On the other hand, a set (also called number) of protocol data units (Protocol Data Unit, PDU)

Packet burst) is a very important feature in XR services, representing a set of packets carrying a frame (e.g., video frame, also called slice or block) payload of an XR service. There is an inherent dependency between packets in a burst of packets associated with a frame of the XR stream that should be handled as a whole at the application layer. For example, the receiving device (e.g., gNB) may only decode and decompress the frame if the receiving device successfully receives all of the data packets in the burst of data packets of the frame. Only when the previous I frame or the previous P frame is prior to the P frame

After the P-frame is successfully decoded and decompressed, the P-frame can be decoded and decompressed.

Therefore, a method is needed to solve the radio resource allocation problem of the XR service.

Disclosure of Invention

One object of the present disclosure is to propose a User Equipment (UE), a base station and an augmented reality (XR) processing method.

In a first aspect, an embodiment of the invention provides an augmented reality (XR) processing method executable in a base station, comprising:

Determining an XR traffic model associated with an XR stream of an XR service, wherein said XR traffic model associated with said XR stream is specified by traffic pattern parameters including frame rate settings indicative of said XR stream and packet spacing between packets in a burst of packets of said XR stream;

determining a configuration of radio resources configured for the XR service based on the XR traffic pattern, wherein configuring the configured radio resources for the XR service comprises at least one of a time domain configuration of the configured radio resources or a frequency domain configuration of the configured radio resources; and

The configured radio resources are allocated for the XR service.

In a second aspect, one embodiment of the invention provides a base station comprising a processor configured to invoke and run a computer program stored in a memory to cause a device in which the processor is installed to perform the disclosed method.

In a third aspect, one embodiment of the invention provides an augmented reality (XR) processing method executable in a User Equipment (UE), comprising:

Determining an XR traffic model associated with an XR stream of an XR service, wherein said XR traffic model associated with said XR stream is specified by traffic pattern parameters including frame rate settings indicative of said XR stream and packet spacing between packets in a burst of packets of said XR stream;

Reporting the XR traffic pattern; and

Receiving a configuration of radio resources configured for the XR service, wherein the configuration of the configured radio resources is based on the XR traffic pattern, wherein configuring the configured radio resources for the XR service comprises at least one of a time domain configuration of the configured radio resources or a frequency domain configuration of the configured radio resources.

In a fourth aspect, one embodiment of the invention provides a User Equipment (UE) comprising a processor configured to invoke and run a computer program stored in a memory to cause the device in which the processor is installed to perform the disclosed method.

The disclosed methods may be implemented in a chip. The chip may include a processor configured to invoke and run a computer program stored in memory to cause a device on which the chip is installed to perform the disclosed methods.

The disclosed methods may be programmed as computer-executable instructions stored in a non-transitory computer-readable medium. The non-transitory computer readable medium, when loaded into a computer, instructs a processor of the computer to perform the disclosed methods.

The non-transitory computer readable medium may include at least one of the group consisting of:

Hard disk, CD-ROM, optical storage, magnetic storage, read-only memory, programmable read-only memory, erasable programmable read-only memory (Erasable Programmable ReadOnly Memory, EPROM), electrically erasable programmable read-only memory (ElectricallyErasable Programmable Read Only Memory, EEPROM), and flash memory.

The disclosed methods can be programmed as a computer program product that causes a computer to perform the disclosed methods.

The disclosed methods can be programmed as a computer program that causes a computer to perform the disclosed methods.

Advantageous effects

Embodiments of the invention provide the following benefits:

● One embodiment of the disclosed method provides a method of perceiving XR traffic in a Radio Access Network (RAN). Detection and information sharing of XR traffic models and/or XR traffic aware parameter types is very helpful for the RAN to efficiently schedule radio resources and transmit XR traffic.

● One embodiment of the disclosed method provides a method of alignment between the semi-persistent scheduling (SPS)/Configuration Grant (CG) and a burst of data packets. Misalignment between SPS/CG and data packet bursts may introduce additional delays in XR traffic transmissions.

● One embodiment of the disclosed method provides a method for the packet dropping. The gNB may allocate dynamic scheduling for uplink transmission with reference to the latest Buffer Status Report (BSR) to increase the capacity of the new air-interface (NR) system.

Drawings

In order to more clearly illustrate the embodiments of the present disclosure or related art, the drawings that will be described in the embodiments below will be briefly introduced. It is apparent that the illustrations are merely some of the embodiments of the disclosure. Other illustrations can be obtained from these illustrations by one of ordinary skill in the art without taking the premise.

Fig. 1 shows a schematic diagram of an example of a telecommunication system.

Fig. 2 shows a schematic diagram of a network embodiment for the disclosed augmented reality (XR) processing method.

Fig. 3 shows a schematic diagram of an example of the augmented reality (XR) processing method performed by a User Equipment (UE) according to one embodiment of the disclosure.

Fig. 4 shows a schematic diagram of an example of the augmented reality (XR) processing method performed by a base station according to one embodiment of the disclosure.

Fig. 5 shows a schematic diagram of a first XR traffic pattern example.

Fig. 6 shows a schematic diagram of a second XR traffic pattern example.

Fig. 7 shows a schematic diagram of a third XR traffic pattern example.

Fig. 8 shows a schematic diagram of an XR traffic pattern signaling procedure.

Fig. 9 shows a schematic diagram of an example of a radio resource configuration of an XR service.

Fig. 10 shows a schematic diagram of an example of radio resources that are not aligned with a data packet of an XR service.

Fig. 11 shows a schematic diagram of an example of a radio resource configuration according to a time offset measured at the gNB.

Fig. 12 shows a schematic diagram of an example of a radio resource configuration according to a time offset measured at a User Equipment (UE).

Fig. 13 shows a schematic diagram of a wireless communication system according to one embodiment of the present disclosure.

Detailed Description

Technical matters, structural features, achieved objects and effects of the embodiments of the present disclosure are described in detail below with reference to the accompanying drawings. In particular, the terminology used in the embodiments of the disclosure is for the purpose of describing certain embodiments only and is not intended to be limiting of the disclosure.

The invention discloses an Extended Reality (XR) processing method flow to enhance the radio resource allocation (e.g. Semi-PERSISTENT SCHEDULING (SPS), configuration grant (Configured) in a 5G wireless communication system (new air interface NR)

Grant, CG) and/or dynamic authorization (DYNAMIC GRANT, DG)) to support extended reality (XR) services. XR services may include augmented reality (Augment Reality,), virtual reality (Virtual

Ready, VR) or Mixed Reality (MR).

Referring to fig. 1, a telecommunications system including a UE 10a, a UE 10b, a Base Station (BS) 20a and a network entity apparatus 30 performs the disclosed method according to one embodiment of the present disclosure. Fig. 1 is for illustrative purposes only and is not limiting, and the system may include more UEs, BSs and core network entities. The connections between devices and between device components are represented in the figures by lines and arrows. The UE 10a may include a processor 11a, a memory 12a, and a transceiver 13a. The UE 10b may include a processor 11b, a memory 12b, and a transceiver 13b. The base station 20a may include a processor 21a, a memory 22a, and a transceiver 23a. The network entity device 30 may comprise a processor 31, a memory 32 and a transceiver 33. Each of the processors 11a, 11b, 21a, and 31 may be configured to implement the proposed functions, processes, and/or methods described in the specification. The radio interface protocol layers may be implemented in the processors 11a, 11b, 21a and 31. Each of the memories 12a, 12b, 22a and 32 operatively stores various programs and information to operate the connected processors. Each of the transceivers 13a, 13b, 23a and 33 is operatively coupled to a connected processor, transmitting and/or receiving radio signals or wired signals. The UE 10a may communicate with the UE 10b via a side chain. The base station 20a may be one of an eNB, a gNB or other type of radio node and may configure radio resources for the UE 10a and UE 10 b.

The network entity device 30 may be a node in the CN. The CN may include an LTE CN or 5G core (5 GC) including a User Plane function (User Plane Function, UPF), a session management function (Session Management Function, SMF), a mobility management function (Mobility Management Function, AMF), a Unified data management (Unified DATA MANAGEMENT, UDM), a policy Control function (Policy Control Function, PCF), a Control Plane (CP)/User Plane (UP) separation (CP/UP separation, CUPS), an authentication server (Authentication Server, AUSF), a network slice selection function (Network Slice Selection Function, NSSF), and a network exposure function (Network Exposure Function, NEF).

Examples of the UE in the description may include one of the UE 10a or UE 10 b. Examples of the base station described in the description may include the base station 20a. Uplink (UL) transmission of control signals or data may be a transmission operation from a UE to a base station. The Downlink (DL) transmission of the control signal or data may be a transmission operation from the base station to the UE. The Control signal may include a media access Control (Medium Access Control, MAC) Control Element (CE), downlink Control information (downlink Control information, DCI), or a radio resource Control (radio resource Control, RRC) signal.

Fig. 2 is a network of XR services supported by a 5G system. The UE 10 is a 5G terminal that can support XR services and XR applications. The gNB 20 is a 5G radio node in a radio access network (Radio Access Network, RAN) 200. The gNB 20 communicates with the UE 10 over a new air interface (NR) Uu interface and provides NR user plane and control plane protocol termination to the UE. The gNB 20 is connected to the 5GC 300 via the NG interface. AMF 30b is the AMF in the 5gc 300 (i.e., 5G core network). The Data Network (DN) 40 is a Data Network where an XR server 41 providing an XR service 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 may be configured to implement the XR service related functions, procedures and/or methods described in the description. The radio interface protocol layer may be implemented in the processor 411. The memory 412 is operative to store various programs and information to operate the connected processors. The transceiver 413 is operatively coupled to the connected processor to transmit and/or receive radio signals or wired signals.

Each of the processors 411, 11a, 11b, 21a, and 31 may include Application-specific integrated circuits (ASICs), 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 (Random Access Memory, RAM), flash Memory, memory cards, storage mediums, and/or other storage devices. Each of the transceivers 413, 13a, 13b, 23a, and 33 may include a baseband circuit and a Radio Frequency (RF) circuit to process Radio Frequency signals. When the embodiments are implemented in software, the techniques described herein may be implemented with modules, procedures, functions, entities, and so on that perform the functions. The modules may be stored in memory and executed by the processor. The memories may be implemented within or external to the processor in that they may be communicatively coupled to the processor in various means as is known in the art. The device performing the augmented reality (XR) processing method may be a transmitting device transmitting an XR traffic stream of an XR service to a receiving device, or a receiving device receiving an XR traffic stream, or an intermediate device processing the XR traffic stream. For example, the device performing the augmented reality (XR) processing method may comprise the gNB 20, an XR server 41 in a data network 40, or a UE. That is, the XR server 41 in the data network 40 may operate as a transmitting device for performing an augmented reality (XR) processing method in certain XR traffic delivery scenarios. Similarly, the UE 10 may operate as a transmitting device to perform an augmented reality (XR) processing method in some XR traffic delivery scenarios. Or the sending device may comprise an intermediary device between the UE 10 and the XR server 41. The UE 10 may include one embodiment of the UE 10a or UE 10 b. The gNB 20 may include one embodiment of the base station 20 a. Note that although the gNB 20 and AMF/5gc 30b are described as examples in the description, the augmented reality (XR) processing method may be performed by a base station, such as another gNB, eNB, base station integrating eNB and gNB, or a base station for a 5G later technology. The AMF/5GC 30b may include another network entity of 5 GC. The network entity in the illustration may be an embodiment of the network entity 30.

For example, an XR service 5 is established between the UE 10 and the XR server 40. The XR service 5 comprises a downlink 51 and an uplink 52. The gNB 20 transmits data packets of the XR service 5 between the UE 10 and XR server 40.

One or more steps (or modules) in embodiments of the present disclosure may be implemented as a computer program, instructions, software modules, stored in a memory of the device performing the augmented reality (XR) processing method, or as circuitry or hardware modules in a processor of the device, or as an integrated circuit chip, circuitry or plug-in of the device.

Referring to fig. 3 and 4, the UE initiates XR services (block 101). The UE 10 determines an XR traffic model associated with an XR flow of an XR service (e.g., XR service 5) (block 102). The XR flow model associated with the XR flow is specified by flow pattern parameters including frame rate settings indicative of the XR flow and packet spacing between packets in a burst of packets of the XR flow.

The UE 10 reports the XR traffic model to the gNB 20 (block 103). The XR traffic model may be included in and carried by the control signals sent to the gNB 20. The control signal may be sent from the UE 10 to the gNB 20. Or the control signal may be sent from the UE 10 to a core network entity (e.g., AMF 30 b) and then from the core network entity (e.g., AMF 30 b) to the gNB 20. In some embodiments, the XR flow model may be in the NG-

An AP protocol message, a non-access stratum (NAS) protocol message, a Radio Resource Control (RRC) message, or a Medium Access Control (MAC) Control Element (CE).

The gNB20 receives the XR traffic model and determines the XR traffic model associated with the XR flow for the XR service (block 201). In one embodiment, the XR flow model may be represented by an index into a row of a lookup table, each row of the lookup table including one of a plurality of options of selectable XR flow patterns in the lookup table.

The gNB 20 determines the configuration of radio resources configured for the XR service based on the XR traffic model (block 203) and allocates the configured radio resources for the XR service (block 205). The configuration of the configured radio resources is based on the XR traffic pattern. Configuring the configured radio resources for the XR service includes at least one of a time domain configuration or a frequency domain configuration of the configured radio resources. The UE 10 receives a configuration of radio resources configured for the XR service (block 105).

In one embodiment, the time domain configuration of the configured radio resources comprises one or more of:

● An interval of periodic blocks in the radio resource configured for the XR service; and

● An interval of a plurality of radio resource groups among the radio resources configured for the XR service.

Each of the plurality of radio resource groups includes a number of periodic blocks in the radio resources configured for the XR service. Each of the periodic blocks in the radio resources configured for the XR service includes a semi-persistent scheduling (SPS) allocation or Configuration Grant (CG) for the XR service. The interval of the periodic blocks in the radio resources configured for the XR service is configured according to the packet interval between packets in the burst of packets of the XR stream. The intervals of the plurality of radio resource groups are configured according to the frame rate representative setting of the XR stream (i.e., the intervals between data packet bursts of the XR stream).

The radio resources configured for the XR service may be configured based on quality of service (Quality Of Service, qoS) requirements of the XR service. The QoS requirements of the XR service may include a Packet delay Budget (PACKET DELAY bridge, PDB), a Packet error Rate (Packet Error Rate, PER), a Packet Loss Rate (PLR), a frame error Rate, a frame delay Budget, a resolution, a frame Rate, a frame size, or a data Rate.

The configuration of the configured radio resources may remain consistent throughout the session of the XR service. For example, the first pair of adjacent radio resource groups in the XR stream may be spaced the same as the second pair of adjacent radio resource groups in the XR stream. The configuration of the configured radio resources may change during the entire session of the XR service. For example, the spacing of a first pair of adjacent radio resource groups in the XR stream before the change may be different from the spacing of a second pair of adjacent radio resource groups in the XR stream after the change.

The radio resources configured for the XR service may be configured or reconfigured by the gNB 20 based on a measured time offset between an allocation time of the configured radio resources and a start time of a first data packet of a data packet burst of the XR service. The first data packet of the burst of data packets may be in an uplink or a downlink of the XR stream of the XR service. In one embodiment, the start time of the first packet of the burst of packets may be obtained from XR service setup/reconfiguration configuration information of the XR service. In some embodiments, the measured time offset is determined by the gNB 20 or received in an uplink report from the UE 10.

In one embodiment, the frequency domain configuration of the configured radio resources comprises a bandwidth configuration of the periodic blocks in the radio resources configured for the XR service. In the bandwidth configuration, a bandwidth of a periodic block in the radio resource configured for the XR service is configured according to a packet size of each packet in the burst of packets of the XR stream.

The XR traffic pattern and XR traffic awareness in RAN:

for XR traffic, and in particular video streams of the XR traffic, each video frame (also referred to as a slice or block) in the video stream may typically be partitioned into one or more data packets, transported by the network (e.g., the RAN), and then individually arrived at the gNB 20 over a period of time. The plurality of packets of video frames in an XR service (e.g., XR service 5) have a periodic characteristic, the periodicity of the packets being dependent on the periodicity or frame rate of the video frames of the XR service. The periodicity or frame rate of video frames of the XR service may be referred to as a frame rate representative setting of the XR stream.

The data packets belonging to a frame may be defined as a data packet burst or a set of Protocol Data Units (PDUs). Since an XR service (e.g., XR service 5) may include multiple frames, multiple bursts (or sets of PDUs) of data packets may be transmitted in an XR stream (i.e., an XR traffic stream) of the XR service.

In another aspect, the size of the encoded and compressed video frames of XR traffic is variable, and therefore the number of packets in a PDU set and/or the packet size of each packet is variable.

Various XR traffic patterns may be specified by different types of the XR traffic parameters. Based on the XR traffic characteristics of the XR service, especially for the video frames, the XR traffic can be modeled using a combination of XR traffic parameters. The model of XR flow may be referred to as an XR flow model or XR flow pattern. The XR flow parameters may include:

● The periodicity/frame rate of the data,

● The number of data packets in a data packet burst,

● The size of each of the data packets is,

● Packet interval, and

● The total size of the entire frame.

The XR flow parameters may be divided into static parameters and dynamic parameters. Some examples of the XR flow model are described in detail below. The static parameter may be referred to as a static XR flow parameter and the dynamic parameter may be referred to as a dynamic XR flow parameter.

In one embodiment, the XR traffic model associated with the XR flow belongs to a first XR traffic pattern (e.g., XR traffic pattern 1), and the traffic pattern parameters of the XR traffic model associated with the first XR traffic pattern further comprise a number of packets in the burst of packets of the XR flow. The number of periodic blocks of each of the radio resource groups configured for the XR service is configured according to the number of data packets in the data packet burst of the XR stream.

In one embodiment, the XR traffic model associated with the XR flow belongs to a second XR traffic pattern (e.g., XR traffic pattern 2), and the traffic pattern parameters of the XR traffic model associated with the second XR traffic pattern further comprise a packet size of each packet in the burst of packets of the XR flow. The bandwidth of the periodic blocks in the radio resources configured for the XR service is configured according to the packet size of each packet in the burst of packets of the XR stream.

In one embodiment, the XR traffic model associated with the XR stream belongs to a third XR traffic model (e.g., XR traffic model 3), and the traffic model parameters of the XR traffic model associated with the third XR traffic model include only the frame rate representative setting and the packet interval.

Mode 1 (type 1 XR flow parameters)

As shown in fig. 5, an XR service (e.g., XR service 5) belonging to XR traffic pattern 1 (i.e., XR traffic pattern 1) is identified by an XR traffic index and specified by a static XR traffic parameter, including:

● The periodicity/frame rate of the data,

● Number of data packets in a data packet burst, and

● Packet interval.

The periodicity/frame rate is the periodicity of the frame rate of the XR service. The number of packets in the burst of packets is the number of packets in each burst of packets of the XR service. The packet interval is a packet interval of a packet in the XR service.

The static XR flow parameter is an XR flow characteristic representing an XR flow of the XR service. For XR services with XR traffic pattern 1, a transmitting device (e.g., the UE 10 in uplink or the XR server 41 in downlink) keeps the static XR traffic parameters relatively stable during an XR service session of the XR service while allowing dynamic parameters of the XR service (e.g., the size of each data packet) to be variable.

Furthermore, depending on different XR service requirements, a plurality of selectable XR traffic models belonging to the XR traffic pattern 1 may also be preconfigured as options in a look-up table, wherein each selectable XR traffic model has an index (referred to as an XR traffic index or an XR traffic model index) and is associated with a combination of XR traffic parameters. Table 1 is an example of the look-up table containing a plurality of selectable XR traffic patterns belonging to the XR traffic model 1.

TABLE 1 static XR flow parameters for mode 1

Each row of the lookup table represents an alternative XR flow model, with a combination of index and XR flow parameters. Each of the AMF 30b, XR server 41, the UE 10 and the gNB 20 may contain a copy of the look-up table. The sending device (e.g., the UE 10 in uplink or the XR server 41 in downlink) may inform the gNB 20 of an optional XR traffic model selected for XR service (e.g., XR service 5) between the sending device and receiving device (e.g., the XR server 41 in uplink or the UE 10 in downlink). For example, the sending device may notify the gNB 20 of an optional XR traffic model with an XR traffic index of i for the XR service by sending a control message carrying the index i to the gNB 20. The control message may include a Radio Resource Control (RRC) message or a Medium Access Control (MAC) Control Element (CE). The variable i is an integer variable defined in the field of the XR traffic index.

Mode 2 (type 2 XR flow parameters)

As shown in fig. 6, an XR service (e.g., XR service 5) belonging to XR traffic pattern 2 (i.e., XR traffic pattern 2) is identified by an XR traffic index and specified by a static XR traffic parameter, including:

● The periodicity/frame rate of the data,

● A packet size of each packet in the burst of packets, and

● Packet interval.

The periodicity/frame rate is the periodicity of the frame rate of the XR service. The packet size of each packet in the burst of packets is the packet size of each packet in each burst of packets of the XR service. The packet interval is a packet interval of a packet in the XR service.

The static XR flow parameter is an XR flow characteristic representing an XR flow of the XR service. For XR services with XR traffic pattern 2, the transmitting device (e.g. the UE 10 in uplink or the XR server 41 in downlink) keeps the static XR traffic parameters relatively stable during an XR service session of the XR service while allowing the dynamic parameters of the XR service (e.g. the number of packets in a burst of packets) to be variable.

Furthermore, depending on different XR service requirements, a plurality of selectable XR traffic models belonging to the XR traffic pattern 2 may also be preconfigured as options in a look-up table, wherein each selectable XR traffic model has an index (referred to as an XR traffic index or an XR traffic model index) and is associated with a combination of XR traffic parameters. Table 2 is an example of the lookup table containing a plurality of selectable XR traffic models belonging to the XR traffic pattern 2.

TABLE 2 static XR flow parameters for mode 2

Each row of the lookup table represents an alternative XR flow model, with a combination of index and XR flow parameters. Each of the AMF 30b, XR server 41, the UE 10 and the gNB 20 may contain a copy of the look-up table. The sending device (e.g., the UE 10 in uplink or the XR server 41 in downlink) may inform the gNB 20 of an optional XR traffic model selected for XR service between the sending device and receiving device (e.g., the XR server 41 in uplink or the UE 10 in downlink). For example, the sending device may notify the gNB 20 of an optional XR traffic model with an XR traffic index of i for the XR service by sending a control message carrying the index i to the gNB 20. The control message may include an RRC message or a MAC CE.

Mode 3 (type 3 XR flow parameters)

As shown in fig. 7, an XR service (e.g., XR service 5) belonging to XR traffic pattern 3 (i.e., XR traffic pattern 3) is identified by an XR traffic index and specified by static XR traffic parameters, including:

● Periodicity/frame rate, and

● Packet interval.

The periodicity/frame rate is the periodicity of the frame rate of the XR service. The packet interval is a packet interval of a packet in the XR service.

The static XR flow parameter is an XR flow characteristic representing an XR flow of the XR service. For XR services with XR traffic pattern 3, a transmitting device (e.g., the UE 10 in uplink or the XR server 41 in downlink) keeps the static XR traffic parameters relatively stable during an XR service session of the XR service while allowing dynamic parameters of the XR service (e.g., the number of packets in a burst of packets) to be variable.

Furthermore, depending on different XR service requirements, a plurality of selectable XR traffic models belonging to the XR traffic pattern 3 may also be preconfigured as options in a look-up table, wherein each selectable XR traffic model has an index (referred to as an XR traffic index or an XR traffic pattern index) and is associated with a combination of XR traffic parameters. Table 3 is an example of the lookup table containing a plurality of selectable XR traffic models belonging to the XR traffic pattern 3.

The XR service requirements include quality of service (QoS) requirements. The QoS requirements of the XR service include a Packet Delay Budget (PDB), a Packet Error Rate (PER), a Packet Loss Rate (PLR), a frame error rate, a frame delay budget, a resolution, a frame rate, a frame size, or a data rate. The gNB 20 may obtain information about QoS requirements and characteristics of the XR service from an uplink Radio Resource Control (RRC) message or a NG-AP message from an AMF in 5 GC. The gNB 20 may send a configuration of radio resources configured for the XR service to the UE 10 in Downlink Control Information (DCI) or a downlink RRC message.

The gNB 20 may activate or deactivate radio resources configured for the XR service by sending DCI, a downlink RRC message, or a downlink Medium Access Control (MAC) message to the UE 10.

TABLE 3 static XR flow parameters for mode 3

Each row of the lookup table represents an alternative XR flow model, with a combination of index and XR flow parameters. Each of the AMF 30b, XR server 41, the UE 10 and the gNB 20 may contain a copy of the look-up table. The sending device (e.g., the UE 10 in uplink or the XR server 41 in downlink) may inform the gNB 20 of an optional XR traffic model selected for XR service (e.g., XR service 5) between the sending device and receiving device (e.g., the XR server 41 in uplink or the UE 10 in downlink). For example, the sending device may notify the gNB 20 of an optional XR traffic model with an XR traffic index of i for the XR service by sending a control message carrying the index i to the gNB 20. The control message may include an RRC message or a MAC CE.

In another embodiment, all of the XR flow models (or XR flow patterns) and their associated static XR flow parameters may be summarized in a table, as shown in Table 4 below.

TABLE 4 model or type and related static XR flow parameters

From the perspective of XR service awareness in a RAN (e.g., the RAN 200), the RAN 200 (e.g., the gNB 20) may be informed of the XR traffic model (or the XR traffic pattern) representing the statically related XR traffic parameters and/or dynamic parameters of the XR service (e.g., XR service 5) as such information is very helpful to the RAN 200 in scheduling radio resources for XR traffic. NA indicates inapplicability.

As shown in fig. 8, the XR traffic model (or the XR traffic pattern) and/or the associated static XR traffic parameters may be transmitted from the AMF 30b to the gNB 20 as the configuration information for service session establishment or reconfiguration of the XR service by control messages (e.g., NG-AP protocol messages over the NG interface between the gNB 20 and AMF 30 b). The configuration information may include the XR traffic model (or the XR traffic pattern) and/or the static XR traffic parameters of the XR traffic model (or the XR traffic pattern), which may be represented by an index in one of the look-up tables. The control message may be referred to as an XR traffic model notification or an XR traffic model notification from the AMF 30b to the gNB 20.

The AMF 30b may obtain the XR traffic model (or the XR traffic pattern) and/or the associated static XR traffic parameters from the UE 10 by a control message (e.g., a non-access stratum (NAS) protocol message) or another type of message from another function of the 5gc 300 that may communicate with the XR server 41. For the former, a UE (e.g., the UE 10) should transmit the XR traffic pattern and/or the type and/or the associated static XR traffic parameters to an AMF for establishment or reconfiguration of XR services. The control message may be referred to as an XR traffic model notification or an XR traffic model notification from the UE 10 to the AMF 30 b.

Furthermore, if the XR traffic of the XR service (e.g., XR service 5) has multiple XR flows (or traffic flows), the XR traffic model notification transmitted to the gNB 20 may also include the number of XR flows, the importance of each XR flow, and inter-flow dependencies associated with the XR service.

In one embodiment, for the downlink of the XR service (e.g., XR service 5), the information of the dynamic parameters and/or the information of the XR traffic model (or the XR traffic pattern) and/or the associated static XR traffic parameters may be transmitted to the gNB 20 by a Control Plane (CP) protocol layer message.

In another embodiment, for the downlink of the XR service (e.g., XR service 5), the information of the dynamic parameters and/or the information of the XR traffic model (or the XR traffic pattern) and/or the associated static XR traffic parameters may be transmitted to the gNB20 via SDUs of a User Plane (UP) protocol layer. For example, the information is contained in a header (header) of an SDU of a packet data convergence protocol (PACKET DATA Convergence Protocol, PDCP) protocol. In this case, it may be more preferable to use the index of the XR flow model (or the XR flow pattern) indicated in the table and/or the associated static XR flow parameters.

In another embodiment, for the downlink of the XR service (e.g., XR service 5), the information of the dynamic parameters may be transmitted to the gNB 20 by SDUs of an UP protocol layer, while the information of the XR traffic model (or the XR traffic pattern) and/or the associated static XR traffic parameters may be transmitted to the gNB 20 by messages of a CP protocol layer.

In another embodiment, for the uplink of the XR service (e.g., XR service 5), the dynamic parameters and/or the XR traffic model or the information of the type and/or the related static XR traffic parameters may be transmitted by a UE (e.g., the UE 10) to a gNB (e.g., the gNB 20) through RRC messages and/or MAC CEs (control elements), similar to the aforementioned BSR.

Alignment between the SPS/CG and data packet bursts:

Due to the periodic nature of XR services, SPS and CG are assumed to be basic transmission solutions in the RAN for XR services in downlink (from the XR server 41 to the XR clients in the UE 10) and uplink (from the XR clients in the UE 10 to the XR server 41). On the other hand, the size of the frame is variable and may be communicated in the form of a burst of packets containing multiple packets, the current semi-statically configured CG and SPS radio resource allocations based on fixed periodicity and grant size may not be sufficient to support XR traffic. As shown in fig. 9, two possible SPS/CG-based enhancement solutions may be used to support XR traffic. In the example of fig. 9, the XR traffic pattern 1 of XR traffic is taken as an example.

Solution 1 multiple SPS/CG:

In this solution, the periodic data packet bursts of XR traffic may be configured with corresponding configured radio resource groups (e.g., SPS or CG radio resources). All of the data packets in the burst of data packets of the XR stream are allocated blocks of the configuration radio resources (e.g., SPS or CG radio resources).

Referring to fig. 9, in one embodiment of the present disclosure, the gNB 20 configures radio resources (e.g., SPS and/or CG) for the XR services (e.g., XR service 5) in NR by configuring radio resource blocks (e.g., SPS and/or CG) in groups in the time domain to carry the data packets of the XR services. The radio resource blocks may be referred to as radio resource blocks. Configuring the radio resources (e.g., SPS and/or CG) for the XR service may include:

● Configuring the number of groups of the radio resource blocks (e.g., SPS and/or CG), and if a plurality of groups are configured, configuring an interval between two adjacent radio resource block groups (referred to as T1); and

● The number of radio resource blocks (e.g., SPS and/or CG) in each of the groups is configured, as well as the spacing between two adjacent radio resource blocks (e.g., SPS and/or CG) (referred to as T2).

The group of the radio resource blocks may be referred to as a radio resource group. The interval (T1) between two radio resource groups may be configured based on the frame period (T1) of the XR service. The frame period (T1) is the interval between two data packet bursts (i.e. two PDU sets). The interval (T2) between two adjacent radio resource blocks (e.g., SPS and/or CG) in a group may be configured based on the packet period (T2) of the XR service. The packet period (T2) is the interval between two packets. T1 and T2 may be determined taking into account one or more parameters of quality of service (QoS) requirements and characteristics of the XR service. The one or more parameters of the QoS requirements of the XR service may include one or more of a Packet Delay Budget (PDB), a Packet Error Rate (PER), a Packet Loss Rate (PLR), a frame error rate, a frame delay budget, a resolution, a frame rate, a frame size, and a data rate.

Solution 2 sps/cg+ds/DG (dynamic scheduling/dynamic grant):

In this solution, the data packets of XR traffic may be supported using configured radio resources (e.g., SPS or CG radio resources), and one or more additional dynamic radio resources (e.g., dynamic scheduling (DYNAMICALLY SCHEDULED, DS) or dynamic grant (DYNAMIC GRANT, DG) radio resources) may be used to support one or more video frames having a large frame size and a variable frame size. The gNB 20 allocates blocks of the configuration radio resources to a first portion of the data packets in the data packet bursts of the XR stream and allocates blocks of the Dynamic Grant (DG) radio resources to a second portion of the data packets in the data packet bursts of the XR stream. The gNB 20 allocates the Dynamic Grant (DG) radio resources to the second portion of the packets in the burst of packets of the XR flow based on a Buffer Status Report (BSR) sent in response to a packet drop event associated with the packets of the XR flow.

Referring to fig. 9, for example, the gNB 20 allocates a block 110 of the configuration radio resources to a first one of the data packet bursts of the XR stream and a block 112 of the Dynamic Grant (DG) radio resources to the remaining data packets of the data packet burst of the XR stream.

However, according to the configuration procedure and parameters of the current related service session establishment, the gNB 20 should allocate the SPS/CG radio resources for the XR service without knowing when the burst of data packets of the XR service (e.g., XR service 5) will reach the gNB 20. As a result, as shown in fig. 10, the arrival time of the data packet burst at the gNB 20 does not coincide with the allocation time of configured radio resources (e.g., SPS or CG radio resources) SPS/CG radio resources. Thus, the transmission of XR traffic will introduce additional delay.

To address this problem and align the configuration of the SPS/CG radio resources with the data packet bursts of the XR stream in the time domain, one solution is described in detail below and illustrated in fig. 11 and 12. The burst of packets described below is one burst of packets in an XR stream of the XR service (e.g., XR service 5).

The gNB 20 may configure or reconfigure the configuration radio resources of the XR service based on a measured time offset between an allocation time of the configuration radio resources and a start time of a first data packet of a data packet burst of the XR service. The first data packet of the burst of data packets may be in an uplink or a downlink of the XR stream of the XR service. In one embodiment, the start time of the first data packet burst (i.e. the start time of the first data packet burst) may be obtained from XR service setup/reconfiguration configuration information of the XR service. In some embodiments, the measured time offset is determined by the gNB 20 or received in an uplink report from the UE 10.

Referring to fig. 11 and 12, one example of a time offset-based radio resource allocation procedure. In the procedure related to XR service session establishment or reconfiguration of the XR service, the gNB 20 receives an optional start time of a first packet burst of the downlink (e.g., the downlink 51) and/or an optional start time of a first packet burst of the uplink (e.g., the uplink 52), respectively.

For example, similar to the example in fig. 8, the gNB 20 receives the start time of the first packet burst of the downlink and the start time of the first packet burst of the uplink from AMF 30b in an NG-AP protocol message over an NG interface between the gNB 20 and AMF 30b as the configuration information for XR service (e.g., the XR service 5) setup/reconfiguration. The AMF 30b may acquire the start time of the first data packet burst of the downlink and the start time of the first data packet burst of the uplink from the UE 10 through signaling of NAS protocol messages. Or the AMF 30b may obtain the start time of the first data packet burst of the downlink and the start time of the first data packet burst of the uplink through signaling of other types of messages of other functions of the 5gc 300 that may communicate with the XR server 41. For the former, the UE should establish or reconfigure the start time of the first packet burst of the downlink and the start time of the first packet burst of the uplink for XR service to be transmitted to AMF. For the start time of the first data packet burst of the uplink, the UE may transmit the start time of the first data packet burst, while the gNB may obtain the start time of the first data packet burst through an RRC message and/or a MAC CE (control element), similar to the BSR explained in the previous embodiments.

The gNB 20 configures SPS/CG radio resources with reference to the start time of the first data packet burst of the downlink and the start time of the first data packet burst of uplink.

The gNB 20 configures SPS/CG radio resources for the XR flow of the XR service. The SPS/CG radio resources include one or more SPS/CG radio resources. Each of the SPS/CG radio resources has an allocated time and bandwidth. The gNB 20 obtains a time offset between the allocation time of SPS/CG radio resources and the start time of the first packet of a burst of packets. The gNB 20 reconfigures the SPS/CG radio resources according to the measured time offset between the allocation time of the SPS/CG radio resources and the start time of the first data packet of a data packet burst.

■ For the downlink:

as shown in fig. 11, the gNB 20 measures a time offset between an allocation time of SPS/CG radio resources and an arrival time of a packet burst (e.g., a first packet of a packet burst) to reach the gNB 20.

If the time offset does not meet the XR service requirements of the XR service, the gNB 20 reconfigures the SPS/CG radio resources. The threshold for the time offset may be configured. The threshold may be referred to as a time offset threshold. The gNB 20 determines whether the measured time offset satisfies the XR service requirement by comparing the measured time offset to the threshold. The gNB 20 determines that the measured time offset meets the XR service requirement when the measured time offset does not exceed the threshold, and the gNB 20 determines that the measured time offset does not meet the XR service requirement when the measured time offset exceeds the threshold.

The gNB 20 may reconfigure the SPS/CG radio resources in an SPS/CG configuration and inform the UE 10 of the reconfigured SPS/CG configuration by a Radio Resource Control (RRC) message.

Or the gNB 20 may reconfigure the SPS/CG radio resources in an SPS/CG configuration and inform the UE 10 of the reconfigured SPS/CG configuration via a downlink control information (Downlink Control Information, DCI) message on a physical downlink control channel (Physical Downlink Control Channel, PDCCH). The signaling to reconfigure the SPS/CG radio resources may be DCI-based SPS/CG activation and/or SPS CG deactivation on PDCCH.

■ For the uplink:

as shown in fig. 12, the UE 10 measures a time offset between an allocation time of SPS/CG radio resources and an arrival time of a data packet burst (e.g., the first data packet of a data packet burst) to the UE 10.

The UE 10 reports the measured time offset to the gNB 20. The UE 10 may be configured with a threshold value for the time offset. The threshold may be referred to as a time offset threshold. The UE 10 compares the measured time offset to the threshold to determine whether to report the measured time offset.

The gNB 20 receives the measured time offset. If the time offset does not meet the XR service requirements of the XR service, the gNB 20 reconfigures the SPS/CG radio resources. The threshold for the time offset may be configured. The gNB 20 determines whether the measured time offset satisfies the XR service requirement by comparing the measured time offset to the threshold. The gNB 20 determines that the measured time offset meets the XR service requirement when the measured time offset does not exceed the threshold, and the gNB 20 determines that the measured time offset does not meet the XR service requirement when the measured time offset exceeds the threshold. Or when the UE 10 has performed the determination as to whether the measured time offset exceeds the threshold, the UE 10 may report the result of the determination to the gNB 20, and the gNB 20 may receive and accept the determination instead of performing the determination itself.

The gNB 20 may reconfigure the SPS/CG radio resources in an SPS/CG configuration and inform the UE 10 of the reconfigured SPS/CG configuration by means of an RRC message.

Or the gNB 20 may reconfigure the SPS/CG radio resources in an SPS/CG configuration and inform the UE 10 of the reconfigured SPS/CG configuration through a DCI message on the PDCCH. The signaling to reconfigure the SPS/CG radio resources may be DCI-based SPS/CG activation and/or SPS CG deactivation on PDCCH.

Buffer Status Report (BSR) of the packet discard

Because of the inherent interdependence of the packets in a burst of packets, the packets in a burst of packets associated with a frame of the XR stream should be handled as a whole in the application layer. For example, the gNB 20 may be able to decode and decompress the frame only if the gNB 20 successfully receives all of the data packets in the burst of data packets of the frame.

XR services, on the other hand, can be affected by packet dropping. XR services are time sensitive and the bursts of data packets should be transmitted within a predefined delay. Packets with delays exceeding the predefined delay need not be transmitted and should be discarded as outdated packets as soon as possible. Transmitting the outdated data packet is meaningless and consumes the capacity of the NR system.

For the uplink, the UE 10 reports the buffer status regarding uplink buffering of the UE 10 to the gNB 20 using a BSR, which the gNB 20 may allocate DG radio resources to the UE 10 for uplink transmission according to the BSR.

Based on the above requirements, a method for packet dropping and BSR triggering is provided as follows:

The UE 10 discards the outdated data packet in the uplink.

The UE 10 may trigger a BSR to the gNB 20 in response to a packet discard event associated with the XR stream's packets. The UE 10 transmits a BSR in response to a packet discard event associated with the XR stream's packets. The UE 10 issues the packet drop event when the change in uplink buffer exceeds a BSR related threshold. In one embodiment, the UE 10 may be configured with a threshold for a change in buffer size of the uplink buffer, the UE 10 triggering a BSR if the change in buffer size due to the packet discard associated with the XR stream is greater than the threshold. The threshold may be referred to as a BSR correlation threshold.

Fig. 13 is a block diagram of a wireless communication example system 700 according to one embodiment of the disclosure. The embodiments described herein may be implemented into the system using any suitably configured hardware and/or software. Fig. 13 shows the system 700, including Radio Frequency (RF) circuitry 710, baseband circuitry 720, processing unit 730, memory/storage 740, display 750, camera 760, sensor 770, and input/output (I/O) interface 780, coupled to one another as shown.

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 with the memory/storage and configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems running on the system.

The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency conversion, and the like. In some embodiments, the baseband circuitry may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communications with 5G NR, LTE, evolved universal terrestrial radio access network (Evolved Universal Terrestrial Radio Access Network, EUTRAN) and/or other wireless metropolitan area networks (Wireless Metropolitan Area Network, WMAN), wireless local area network (Wireless Local Area Network, WLAN), wireless personal area network (Wireless Personal Area Network, WPAN). An embodiment of the baseband circuitry configured to support radio communications of multiple wireless protocols may be referred to as a multimode baseband circuitry. In various embodiments, the baseband circuitry 720 may include circuitry to operate signals that are not strictly considered to be at baseband frequencies. For example, in some embodiments, the baseband circuitry may include circuitry to operate signals having an intermediate frequency that is between the baseband frequency and the radio frequency.

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

The described embodiments of the present disclosure are a combination of techniques/procedures that may be employed in the 3GPP specifications to create the end product.

If the software functional unit is implemented and sold as a product, it may be stored in a computer readable storage medium. Based on this understanding, the technical solutions proposed by the present disclosure may be implemented in essence or partly in the form of a software product. Or a portion of the described technical solutions that are advantageous for the conventional techniques may be implemented in the form of a software product. The software product in the computer is stored in a storage medium comprising a plurality of commands for a computing device (e.g., a personal computer, a server, or a network device) to execute all or part of the steps disclosed in the embodiments of the present disclosure. The storage medium includes a universal serial bus (Universal Serial Bus, USB) disk, a removable hard disk, a Read Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a floppy disk, or other medium capable of storing program code.

In the described embodiments of the present disclosure, the video frames of the XR service may be partitioned into one or more data packets for periodic transmission over the network. In one embodiment of the disclosed method, the gNB configures and data packet radio resources (e.g., SPS and CG) in the time domain for XR service in NR according to the XR traffic model of the XR service to carry video frames of the XR service. The UE transmits and receives the XR service data packets using the configuration and data packet radio resources (e.g., SPS and CG).

One embodiment of the disclosed method provides related signaling to support enhanced radio resource allocation for XR services and to improve the radio resource efficiency in NR.

While the present disclosure has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the present disclosure is not to be limited to the disclosed embodiment, but is intended to cover various arrangements made without departing from the broadest interpretation of the appended claims.

Claims (56)

1. An augmented reality XR processing method executable in a base station, comprising:

Determining an XR traffic model associated with an XR stream of an XR service, wherein said XR traffic model associated with said XR stream is specified by traffic pattern parameters including frame rate settings indicative of said XR stream and packet spacing between packets in a burst of packets of said XR stream;

Determining a configuration of radio resources configured for the XR service based on the XR traffic model, wherein the radio resources configured for the XR service comprise at least one of a time domain configuration or a frequency domain configuration of the configured radio resources; and

The configured radio resources are allocated for the XR service.

2. The method of claim 1, wherein the XR traffic model associated with the XR flow belongs to a first XR traffic model, the traffic model parameters of the XR traffic model associated with the first XR traffic model further comprising a number of packets in the burst of packets of the XR flow.

3. The method of claim 2, wherein the number of periodic blocks of each of the radio resource groups in the radio resources configured for the XR service is configured according to the number of packets in the burst of packets of the XR stream.

4. The method of claim 1, wherein the XR traffic model associated with the XR stream belongs to a second XR traffic model, the traffic model parameters of the XR traffic model associated with the second XR traffic model further comprising a packet size of each packet in the burst of packets of the XR stream.

5. The method of claim 4, wherein a bandwidth of periodic blocks in the radio resources configured for the XR service is configured according to the packet size of each packet in the burst of packets of the XR stream.

6. The method of claim 1, wherein the XR traffic model associated with the XR stream belongs to a third XR traffic model, the traffic model parameters of the XR traffic model associated with the third XR traffic model including only the frame rate representative setting and the packet interval.

7. The method of claim 1, wherein the XR traffic model is represented by an index into a row of a lookup table, each row of the lookup table comprising one of a plurality of options of selectable XR traffic models in the lookup table.

8. The method of claim 1, wherein the XR traffic model is carried in an NG-AP protocol message, a non-access stratum NAS protocol message, a radio resource control, RRC, message, or a medium access control, MAC, control element, CE.

9. The method of claim 1, wherein the XR traffic model is carried in a control message, the control message further comprising an XR flow number in the XR service.

10. The method according to claim 1, characterized in that the time domain configuration of the configured radio resources comprises one or more of the following:

An interval of periodic blocks in the radio resource configured for the XR service; and

An interval of a plurality of radio resource groups among the radio resources configured for the XR service;

Wherein the interval of the periodic blocks in the radio resource configured for the XR service is configured according to the packet interval between packets in the burst of packets of the XR stream;

each of the plurality of radio resource groups comprises a number of periodic blocks in the radio resources configured for the XR service, the intervals of the plurality of radio resource groups being configured according to the frame rate representative setting of the XR stream.

11. The method according to claim 10, characterized in that the frequency domain configuration of the configured radio resources comprises:

a bandwidth configuration of the periodic block in the radio resources configured for the XR service;

Wherein in the bandwidth configuration, the bandwidth of the periodic blocks in the radio resources configured for the XR service is configured according to the packet size of each packet in the burst of packets of the XR stream.

12. The method of claim 10, wherein each of the periodic blocks in the radio resources configured for the XR service comprises a semi-persistent scheduling, SPS, allocation or configuration grant, CG, for the XR service.

13. The method of claim 10, wherein the radio resources configured for the XR service are configured or reconfigured based on a measured time offset between an allocation time of the configured radio resources and a time of a first data packet of a data packet burst of the XR service and/or the start time of the first data packet burst.

14. The method of claim 13, wherein the first data packet of the first data packet burst and/or the first data packet of the data packet burst is in an uplink or a downlink of the XR stream of the XR service.

15. The method of claim 13, wherein the start time of the first burst of data packets is obtained from XR service setup/reconfiguration configuration information of the XR service.

16. The method of claim 13, wherein the measured time offset is determined by the base station or received from an uplink report.

17. The method of claim 13, characterized in that the reconfiguration of radio resources configured for the XR service is carried in downlink control information, DCI, or downlink RRC message.

18. The method of claim 1, wherein all of the data packets in the burst of data packets of the XR stream are allocated blocks of the configured radio resources.

19. The method of claim 1, wherein a first portion of the data packets in the burst of data packets of the XR stream are allocated blocks of the configured radio resources and a second portion of the data packets in the burst of data packets of the XR stream are allocated blocks of the dynamically granted DG radio resources.

20. The method of claim 19, wherein the dynamically granted DG radio resources are allocated to the second portion of the data packets in the data packet burst of the XR stream according to a buffer status report BSR.

21. The method of claim 1, wherein the configured radio resources configured for the XR service are carried in downlink control information, DCI, or a downlink RRC message.

22. The method of claim 1, wherein the configured radio resources are activated or deactivated for the XR service is signaled in a downlink control information, a downlink RRC message, or a downlink Medium Access Control (MAC) message.

23. A base station, comprising:

A processor configured to invoke and run a computer program stored in a memory to cause a device in which the processor is installed to perform the method of any of claims 1 to 22.

24. A chip, comprising:

a processor configured to invoke and run a computer program stored in a memory to cause a device on which the chip is installed to perform the method of any of claims 1 to 22.

25. A computer readable storage medium having stored therein a computer program for causing a computer to perform the method of any one of claims 1 to 22.

26. A computer program product comprising a computer program for causing a computer to perform the method of any one of claims 1 to 22.

27. A computer program for causing a computer to perform the method of any one of claims 1 to 22.

28. An extended reality (XR) processing method executable in a User Equipment (UE), comprising:

Determining an XR traffic model associated with an XR stream of an XR service, wherein said XR traffic model associated with said XR stream is specified by traffic pattern parameters including frame rate settings indicative of said XR stream and packet spacing between packets in a burst of packets of said XR stream;

Reporting the XR traffic model; and

A configuration of radio resources configured for the XR service is received, wherein the configuration of the configured radio resources is based on the XR traffic model, wherein configuring the configured radio resources for the XR service comprises at least one of a time domain configuration or a frequency domain configuration of the configured radio resources.

29. The method of claim 28, wherein the XR traffic model associated with the XR flow belongs to a first XR traffic model, the traffic model parameters of the XR traffic model associated with the first XR traffic model further comprising a number of packets in the burst of packets of the XR flow.

30. The method of claim 29, wherein a number of periodic blocks of each of the radio resource groups in the radio resources configured for the XR service corresponds to the number of data packets in the data packet burst of the XR flow.

31. The method of claim 28, wherein the XR traffic model associated with the XR stream belongs to a second XR traffic model, the traffic model parameters of the XR traffic model associated with the second XR traffic model further comprising a packet size of each packet in the burst of packets of the XR stream.

32. The method of claim 31, wherein a bandwidth of a periodic block in the radio resource configured for the XR service corresponds to the packet size of each packet in the burst of packets of the XR stream.

33. The method of claim 28, wherein the XR traffic model associated with the XR stream belongs to a third XR traffic model, the traffic model parameters of the XR traffic model associated with the third XR traffic model including only the frame rate representative setting and the packet interval.

34. The method of claim 28, wherein the XR traffic model is represented by an index into a row of a lookup table, each row of the lookup table comprising one of a plurality of options of selectable XR traffic models in the lookup table.

35. The method of claim 28, wherein the XR traffic model is carried in an NG-AP protocol message, a non-access stratum (NAS) protocol message, a Radio Resource Control (RRC) message, or a Medium Access Control (MAC) Control Element (CE).

36. The method of claim 28, wherein the XR traffic model is carried in a control message, the control message further comprising an XR flow number in the XR service.

37. The method according to claim 28, characterized in that the time domain configuration of the configured radio resources comprises one or more of the following:

An interval of periodic blocks in the radio resource configured for the XR service; and

An interval of a plurality of radio resource groups among the radio resources configured for the XR service;

Wherein the interval of the periodic blocks in the radio resources configured for the XR service corresponds to the packet interval between packets in the burst of packets of the XR stream;

each of the plurality of radio resource groups includes a number of periodic blocks in the radio resources configured for the XR service, the spacing of the plurality of radio resource groups corresponding to the frame rate representative setting of the XR stream.

38. The method according to claim 37, characterized in that the frequency domain configuration of the configured radio resources comprises:

a bandwidth configuration of the periodic block in the radio resources configured for the XR service;

wherein in the bandwidth configuration, a bandwidth of a periodic block in the radio resource configured for the XR service corresponds to a packet size of each packet in the burst of packets of the XR stream.

39. The method of claim 37, wherein each of the periodic blocks in the radio resources configured for the XR service comprises a semi-persistent scheduling (SPS) allocation or Configuration Grant (CG) for the XR service.

40. The method of claim 37, wherein the spacing of the first pair of adjacent radio resource groups is the same as or different from the spacing of the second pair of adjacent radio resource groups.

41. The method of claim 37, wherein the radio resources configured for the XR service are configured or reconfigured based on a measured time offset between an allocation time of the configured radio resources and a time of a first data packet of a data packet burst of the XR service and/or the start time of the first data packet burst.

42. The method of claim 41, wherein the first packet of the first burst of packets and/or the first packet of a burst of packets is in an uplink or a downlink of the XR stream of the XR service.

43. The method of claim 41, wherein the start time of the first burst of data packets is obtained from configuration information of an XR service setup of the XR service.

44. The method of claim 41, wherein the measured time offset is reported in an uplink report.

45. The method of claim 41, wherein the reconfiguration of radio resources configured for the XR service is carried in Downlink Control Information (DCI) or a downlink RRC message.

46. The method of claim 28, wherein all of the data packets in the burst of data packets of the XR stream are allocated blocks of the configured radio resources.

47. The method of claim 28, wherein a first portion of the data packets in the burst of data packets of the XR stream are allocated blocks of the configured radio resources and a second portion of the data packets in the burst of data packets of the XR stream are allocated blocks of the dynamically granted DG radio resources.

48. The method of claim 47, wherein the Dynamic Grant (DG) radio resources are allocated to the second portion of the data packets in the burst of data packets of the XR stream based on a Buffer Status Report (BSR) sent in response to a data packet drop event associated with the data packets of the XR stream.

49. The method of claim 48, wherein the packet discard event is issued when a change in uplink buffering exceeds a BSR-related threshold.

50. The method of claim 28, wherein the configured radio resources configured for the XR service are carried in Downlink Control Information (DCI) or a downlink RRC message.

51. The method of claim 28, wherein the configured radio resources are activated or deactivated for the XR service is signaled in downlink control information, a downlink RRC message, or a downlink Medium Access Control (MAC) message.

52. A User Equipment (UE), comprising:

a processor configured to invoke and run a computer program stored in a memory to cause a device in which the processor is installed to perform the method of any of claims 28 to 51.

53. A chip, comprising:

A processor configured to invoke and run a computer program stored in a memory to cause a device on which the chip is installed to perform the method of any of claims 28 to 51.

54. A computer readable storage medium having stored therein a computer program for causing a computer to perform the method of any one of claims 28 to 51.

55. A computer program product comprising a computer program for causing a computer to perform the method of any one of claims 28 to 51.

56. A computer program for causing a computer to perform the method of any one of claims 28 to 51.