COMMUNICATION CONTROL METHOD, USER EQUIPMENT, NETWORK NODE, COMMUNICATION SYSTEM, PROGRAM, AND CHIPSET

Abstract

To provide an XR (eXtended Reality) traffic communication control method, user equipment, a network B node, a program, and a chipset in a mobile communication system.SOLUTION: A communication control method in a mobile communication system includes: a base station 200 transmitting, to user equipment, setting information including a QoS (Quality of Service) follow identifier corresponding to XR (eXtended Reality) traffic and a session ID linked to the QoS follow identifier; and the user equipment transmitting XR assist information to the base station based on the setting information.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present disclosure relates to a communication control method in a mobile communication system. [Background technology]

[0002] XR (eXtended Reality) has been approved for Release 18 of the specifications of 3GPP (The Third Generation Partnership Project) (registered trademark; the same applies hereinafter), a mobile communications system standardization project. XR is a broad term that includes virtual reality (VR), augmented reality (AR), and mixed reality (MR), and describes an environment that blends the real world with virtual space. XR describes a combined environment of real space and virtual space generated by computer technology and wearable devices, and represents the interaction between humans and machines. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] RP-213587, 3GPP TSG RAN Meeting #94e, “Study on XR Enhancements for NR”, Nokia, Dec.6-17,2021 [Non-patent document 2] 3GPP TR 38.838 V17.0.0 (2021-12) Summary of the Invention

[0004] A communication control method according to one aspect is a communication control method in a mobile communication system. The communication control method includes a step in which a user device transmits XR (eXtended Reality) assist information related to XR to a base station. Here, the XR includes virtual reality (VR), augmented reality (AR), and mixed reality (MR), and represents an environment in which the real world and a virtual space are integrated.

[0005] A communication control method according to one aspect is a communication control method in a mobile communication system, the communication control method including a step of transmitting XR assist information related to XR to a base station by an access mobility management device, where XR includes virtual reality, augmented reality, and mixed reality, and represents an environment that combines the real world and virtual space. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a mobile communication system according to the first embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the configuration of a UE (user equipment) according to the first embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example configuration of a gNB (base station) according to the first embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of the configuration of a protocol stack related to a user plane according to the first embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of the configuration of a protocol stack related to the control plane according to the first embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of operation according to the first embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of operation according to the first modification of the first embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of operation according to the second modification of the first embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of operation according to the third modification of the first embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of operation according to the second embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of operation according to the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0007] An object of one aspect of the present disclosure is to provide a communication control method that enables communication using XR to be carried out appropriately.

[0008] A mobile communication system according to an embodiment will be described with reference to the drawings. In the description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

[0009] [First embodiment] (Configuration of a mobile communication system) FIG. 1 is a diagram illustrating the configuration of a mobile communication system according to a first embodiment. The mobile communication system 1 conforms to the 3GPP standard 5th Generation System (5GS). In the following description, 5GS is used as an example, but the mobile communication system may also be at least partially based on an LTE (Long Term Evolution) system. Alternatively, the mobile communication system may also be at least partially based on a sixth generation (6G) system.

[0010] The mobile communication system 1 includes a user equipment (UE) 100, a 5G radio access network (NG-RAN) 10, and a 5G core network (5GC) 20. Hereinafter, the NG-RAN 10 may be simply referred to as the RAN 10. The 5GC 20 may be simply referred to as the core network (CN) 20.

[0011] The UE 100 is a mobile wireless communication device. The UE 100 may be any device that is used by a user. For example, the UE 100 may be a mobile phone terminal (including a smartphone), a tablet terminal, a laptop PC, a communication module (including a communication card or a chipset), a sensor or a device provided in a sensor, a vehicle or a device provided in a vehicle (Vehicle UE), or an aircraft or a device provided in an aircraft (Aerial UE).

[0012] The UE 100 includes an XR device. The XR device is, for example, a device capable of XR processing. Specific examples of XR devices include a head-mounted display (HMD) that can be worn on a human head, eyeglass-type AR glasses (or smart glasses), a handheld mobile handset, a wristwatch-type device (smart watch), and a smartphone. These XR devices may also be called wearable devices. The HMD includes a display, lenses, a tracking sensor, a camera, a control unit (such as a central processing unit (CPU) or a graphics processing unit (GPU)) that performs XR-related processing, and a communication function. The AR glasses have a function of transmitting images. The mobile handset may include various sensors such as a tracking sensor. The HMD, AR glasses, wristwatch-type device, and mobile handset have a communication function that supports a 5G system, etc. In the following, the UE 100 will be described as including such an XR device.

[0013] The NG-RAN 10 includes a base station (called "gNB" in the 5G system) 200. The gNBs 200 are connected to each other via an Xn interface, which is an interface between base stations. The gNB 200 manages one or more cells. The gNB 200 performs wireless communication with a UE 100 that has established a connection with its own cell. The gNB 200 has a radio resource management (RRM) function, a routing function for user data (hereinafter simply referred to as "data"), a measurement control function for mobility control and scheduling, etc. The term "cell" is used to indicate the smallest unit of a wireless communication area. The term "cell" is also used to indicate a function or resource that performs wireless communication with a UE 100. One cell belongs to one carrier frequency (hereinafter simply referred to as "frequency").

[0014] In addition, gNBs can also connect to the Evolved Packet Core (EPC), which is the LTE core network. LTE base stations can also connect to 5GC. LTE base stations and gNBs can also be connected via a base station-to-base station interface.

[0015] The 5GC20 includes an Access and Mobility Management Function (AMF) and a User Plane Function (UPF) 300. The AMF performs various mobility controls for the UE 100. The AMF manages the mobility of the UE 100 by communicating with the UE 100 using NAS (Non-Access Stratum) signaling. The UPF controls data forwarding. The AMF and UPF are connected to the gNB 200 via an NG interface, which is an interface between a base station and a core network.

[0016] 2 is a diagram showing the configuration of a UE 100 (user equipment) according to the first embodiment. The UE 100 includes a receiving unit 110, a transmitting unit 120, and a control unit 130. The receiving unit 110 and the transmitting unit 120 constitute a wireless communication unit that performs wireless communication with the gNB 200.

[0017] The receiving unit 110 performs various types of reception under the control of the control unit 130. The receiving unit 110 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 130.

[0018] The transmitting unit 120 performs various transmissions under the control of the control unit 130. The transmitting unit 120 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 130 into a radio signal and transmits it from the antenna.

[0019] The control unit 130 performs various controls and processes in the UE 100. Such processes include processes in each layer, which will be described later. The control unit 130 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processes by the processor. The processor may include a baseband processor and a CPU (Central Processing Unit). The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processes. Note that the control unit 130 may perform each process or operation in the UE 100 in each of the embodiments described below.

[0020] 3 is a diagram showing the configuration of a gNB200 (base station) according to the first embodiment. The gNB200 includes a transmitter 210, a receiver 220, a controller 230, and a backhaul communication unit 240. The transmitter 210 and the receiver 220 constitute a wireless communication unit that performs wireless communication with the UE 100. The backhaul communication unit 240 constitutes a network communication unit that performs communication with the CN20.

[0021] The transmission unit 210 performs various transmissions under the control of the control unit 230. The transmission unit 210 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 230 into a radio signal and transmits it from the antenna.

[0022] The receiving unit 220 performs various types of reception under the control of the control unit 230. The receiving unit 220 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 230.

[0023] The control unit 230 performs various controls and processes in the gNB 200. Such processes include processes in each layer, which will be described later. The control unit 230 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processes by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals, etc. The CPU executes programs stored in the memory to perform various processes. Note that the control unit 230 may perform each process or operation in the gNB 200 in each of the embodiments described below.

[0024] The backhaul communication unit 240 is connected to neighboring base stations via an Xn interface, which is an interface between base stations. The backhaul communication unit 240 is connected to the AMF / UPF 300 via an NG interface, which is an interface between a base station and a core network. Note that the gNB 200 may be configured (i.e., functionally divided) with a CU (Central Unit) and a DU (Distributed Unit), and both units may be connected via an F1 interface, which is a fronthaul interface.

[0025] FIG. 4 is a diagram showing the configuration of a protocol stack of a radio interface of a user plane that handles data.

[0026] The user plane radio interface protocol includes a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer.

[0027] The PHY layer performs encoding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping. Data and control information are transmitted between the PHY layer of UE100 and the PHY layer of gNB200 via a physical channel. The PHY layer of UE100 receives downlink control information (DCI) transmitted from gNB200 on a physical downlink control channel (PDCCH). Specifically, UE100 performs blind decoding of the PDCCH using a radio network temporary identifier (RNTI) and acquires successfully decoded DCI as DCI addressed to the UE. The DCI transmitted from gNB200 has CRC parity bits scrambled by the RNTI added.

[0028] The MAC layer performs data priority control, retransmission processing using Hybrid Automatic Repeat reQuest (HARQ), random access procedures, etc. Data and control information are transmitted between the MAC layer of UE100 and the MAC layer of gNB200 via transport channels. The MAC layer of gNB200 includes a scheduler, which determines the uplink and downlink transport format (transport block size, modulation and coding scheme (MCS)) and the resource blocks to be allocated to UE100.

[0029] The RLC layer transmits data to the RLC layer on the receiving side using the functions of the MAC layer and PHY layer. Data and control information are transmitted between the RLC layer of the UE 100 and the RLC layer of the gNB 200 via logical channels.

[0030] The PDCP layer performs header compression / decompression, encryption / decryption, etc.

[0031] The SDAP layer maps IP flows, which are the units for Quality of Service (QoS) control by the core network, to radio bearers, which are the units for QoS control by the Access Stratum (AS). Note that if the RAN is connected to the EPC, SDAP is not necessary.

[0032] FIG. 5 is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that handles signaling (control signals).

[0033] The protocol stack of the radio interface of the control plane has a Radio Resource Control (RRC) layer and a Non-Access Stratum (NAS) instead of the SDAP layer shown in FIG.

[0034] RRC signaling for various settings is transmitted between the RRC layer of UE100 and the RRC layer of gNB200. The RRC layer controls logical channels, transport channels, and physical channels according to the establishment, re-establishment, and release of radio bearers. When there is a connection (RRC connection) between the RRC of UE100 and the RRC of gNB200, UE100 is in an RRC connected state. When there is no connection (RRC connection) between the RRC of UE100 and the RRC of gNB200, UE100 is in an RRC idle state. When the connection between the RRC of UE100 and the RRC of gNB200 is suspended, UE100 is in an RRC inactive state.

[0035] The NAS, which is located above the RRC layer, performs session management, mobility management, etc. NAS signaling is transmitted between the NAS of the UE 100 and the NAS of the AMF 300. Note that the UE 100 has an application layer and the like in addition to the radio interface protocol. The layer below the NAS is called an AS (Access Stratum).

[0036] (About XR) As described above, XR is a broad term that includes, for example, virtual reality (VR), augmented reality (AR), and mixed reality (MR), and describes an environment that combines the real world and virtual space. XR is also, for example, a general term for such various types of realities. XR is also, for example, a general term for technologies that combine the real world and virtual space to enable perception of things that do not exist in reality.

[0037] In XR, human-to-machine and human-to-human communication is performed with the assistance of a portable or wearable end-user device, the UE 100. Such communication enables XR to be applied in various application domains, such as entertainment, healthcare, or education.

[0038] Along with XR, cloud gaming (CG) is one of the use cases in future mobile systems. Cloud gaming is a general term for use cases in which, for example, most of the calculations related to games are offloaded to an edge server or a remote server. In cloud gaming, the UE 100 transmits information related to pose and / or control. The cloud performs calculations related to video data and the like based on this information and provides the UE 100 with video and other game-related data.

[0039] Virtual reality (VR) refers to the creation of an environment that is not the original (or real world) but is essentially functionally the same as the original by stimulating the user's senses. In virtual reality (VR), the user typically wears an HMD, which replaces the user's field of vision with simulated visual elements and provides accompanying audio to the user through headphones. Virtual spaces are designed to mimic sensory stimuli such as sight and hearing in the real world as naturally as possible. Virtual reality (VR) can also include the metaverse, a virtual space (or service) built on a computer or computer network that is different from the real world.

[0040] Augmented reality (AR) is a technology that displays a virtual world overlaid on the real world. AR also provides additional information (artificially generated items or content) overlaid on the user's real environment. The additional information can be perceived directly without sensors or indirectly via sensors.

[0041] Furthermore, mixed reality (MR) is a technology that combines and / or blends the real world and virtual space to create a space where they interact with each other in real time. Mixed reality (MR) is an advanced form of augmented reality (AR) and is constructed with the intention of inserting virtual elements into a physical scene to give the illusion that they are part of the actual scene.

[0042] Typical forms of XR include virtual reality (VR), augmented reality (AR), and mixed reality (MR), but areas that interpolate between these may also be included in XR.

[0043] Many XR and cloud gaming (CG) use cases are characterized by video stream traffic in the DL direction and a combination of pose and / or control traffic and video stream traffic in the UL direction. The video stream has a higher data rate than other use cases, and pose and / or control data is updated frequently. XR and cloud gaming (CG) also have the characteristic that DL traffic and UL traffic are more sensitive to latency than other use cases.

[0044] (XR traffic model) The following explains the traffic model of XR. There are two types of traffic models for XR: (1) a general traffic model and (2) a specific traffic model. First, we will explain the (1) general traffic model. The (1) general traffic model includes (1.1) a traffic model for the DL direction and (1.2) a traffic model for the UL direction.

[0045] (1) General traffic model

[0046] (1.1) Traffic model for DL ​​direction There are two traffic models for the DL direction: a single-stream DL traffic model and a multi-stream DL traffic model. The two traffic models can be summarized as follows:

[0047] (1.1.1) Single-stream DL traffic model: a sequence of video frames

[0048] (1.1.2) Multi-stream DL traffic model:

[0049] (1.1.2.1) Option #1: Two streams, the first stream being an I (Intra-coded) stream and the second stream being a P (Predicted) stream. Option #1 includes a slice-based traffic model (Option #1A) and a GOP (Group-Of-Picture)-based traffic model (Option #1B).

[0050] (1.1.2.1A) Option #1A (Slice-based): The first stream is an I slice (I stream), and the second stream is a P slice (P stream). Here, an I slice is, for example, a slice in which all macroblocks included in the I slice are coded by intra-frame prediction. A P slice is, for example, a slice in which all macroblocks included in the P slice are coded by intra-frame prediction or inter-frame prediction. When a video frame is sliced ​​into N slices, one slice may be an I slice, and the remaining (N-1) slices may be P slices.

[0051] (1.1.2.1B) Option #1B (GOP-based): The first stream is an I-frame (I-stream), and the second stream is a P-slice (P-stream). Here, an I-frame is a frame encoded using a video frame without using other video frames. A P-frame is a frame encoded using a video frame preceding it in time. If the GOP size is K frames, an I-frame is transmitted every K frames. A GOP includes one I-frame and (K-1) P-frames.

[0052] (1.1.2.2) Option #2: A traffic model with two streams, where the first stream is video and the second stream is audio and / or data.

[0053] (1.1.2.3) Option #3: A traffic model in which the first stream is a field of view (FOV) and the second stream is an omnidirectional view. For example, the FOV is video data from the user's line of sight, and the omnidirectional view is omnidirectional video data centered on the user, including video data from the user's line of sight.

[0054] (1.2) UL traffic model The traffic model in the UL direction includes an attitude and / or control stream traffic model, in which the UE 100 transmits data related to attitude and / or control.

[0055] (2) Specific traffic model Specific traffic models include (2.1) virtual reality (VR), (2.2) augmented reality (AR), and (2.3) computer gaming (CG) traffic models.

[0056] (2.1) Virtual Reality (VR) Traffic Model The traffic model for virtual reality (VR) can be summarized as follows:

[0057] (2.1.1) DL Stream: Single-stream model: Same as above (1.1.1) "Single-stream DL traffic model" (series of video frames) Multi-stream model: Same as above (1.1.2.2) "Option #2" (first stream is video, second stream is audio and / or data)

[0058] (2.1.2) UL stream: Same as (1.2) "Traffic model in UL direction" above

[0059] (2.2) Augmented Reality (AR) Traffic Model The Augmented Reality (AR) traffic model can be summarized as follows:

[0060] (2.2.1) DL stream: same as (2.1.1) above

[0061] (2.2.2) UL Stream: Model #1:1 Stream Model Model #2: Two-stream model: First stream is attitude and / or control, second stream is scene (e.g., continuous video), video, data, and audio combined. Model #3A: 3-stream Model A: 1st stream is attitude and / or control, 2nd stream is a single stream combining scene stream and video stream, 3rd stream is a single stream combining audio and data Model #3B: 3-stream Model B: 1st stream is attitude and / or control, 2nd stream is I-stream of video, 3rd stream is P-stream of video

[0062] (2.3) Computer Gaming (CG) Traffic Model The traffic model for computer gaming (CG) can be summarized as follows:

[0063] (2.3.1) DL Stream Single-stream model: Same as above (1.1.1) "Single-stream DL traffic model" (series of video frames) Multi-stream model: Same as above (1.1.2) "Multi-stream DL traffic model"

[0064] (2.3.2) UL stream: Same as (1.2) "Traffic model in UL direction" above

[0065] (Communication control method according to the first embodiment) In the first embodiment, the purpose is to appropriately perform communication using XR in the mobile communication system 1, taking into consideration such characteristics related to XR traffic.

[0066] Therefore, a user device (e.g., UE 100) transmits XR assist information related to XR to a base station (e.g., gNB 200). Here, XR includes virtual reality (VR), augmented reality (AR), and mixed reality (MR), and represents an environment that combines the real world and virtual space.

[0067] Since the XR assist information is transmitted to the gNB 200, the gNB 200 can make appropriate settings for communication using XR to the UE 100 based on the XR assist information. Therefore, in the mobile communication system 1, it is possible to appropriately perform communication using XR through such settings.

[0068] Here, the XR assist information includes traffic information related to the traffic characteristics of the XR traffic. In the first embodiment, an example in which the XR assist information includes traffic information will be described.

[0069] (Operation example according to the first embodiment) FIG. 6 is a diagram illustrating an example of operation according to the first embodiment.

[0070] As shown in FIG. 6, in step S10, the AS of the UE 100 receives traffic information from an upper layer (for example, an application layer or a NAS layer).

[0071] In step S11, the UE100 transmits XR assist information including traffic information to the gNB200. The XR assist information is assist information related to XR. The XR assist information may be information that the UE100 expects to make optimal settings for communication related to XR in the gNB200 by transmitting the information to the gNB200. Note that, prior to step S11, the gNB200 may request the UE100 to notify the gNB200 of the XR assist information. The request may be transmitted, for example, in an RRC message or a MAC CE.

[0072] The UE 100 may include the XR assist information in an RRC message and transmit it to the gNB 200. In this case, the UE 100 may transmit the XR assist information as UE assist information. Alternatively, the UE 100 may transmit the XR assist information as a new message (for example, XR Assistance Information). Furthermore, the UE 100 may include the XR assist information in a MAC CE and transmit it instead of an RRC message, or may include the XR assist information in a PDCP Control PDU (Protocol Data Unit) and transmit it. Furthermore, if there is a Control PDU dedicated to the XR layer, the UE 100 may include the XR assist information in the PDU and transmit it.

[0073] Examples of traffic information included in the XR assist information include the following:

[0074] First, the traffic information may be a logical channel ID (LCID) used to transmit XR traffic. The traffic information may be a bearer ID of a bearer used to transmit XR traffic. Alternatively, the traffic information may be an RLC channel ID of an RLC channel used to transmit XR traffic. The traffic information may be represented by an RNTI (Radio Network Temporary Identifier). For example, the traffic information may be a CS-RNTI (Configured Scheduling Radio Network Temporary Identifier) ​​used when transmitting XR traffic using CS (Configured Scheduling). Note that CS (Configured Scheduling) is a scheduling method that, once radio resources are allocated for the UL direction, enables transmission in the UL direction periodically using those radio resources thereafter. Also, for example, if there is an RNTI dedicated to XR, the RNTI may be the traffic information. If there is an XR session ID, the traffic information may be the XR session ID. In other words, the traffic information may be identification information related to the transmission path that transmits XR traffic.

[0075] Second, the traffic information may be the throughput of XR traffic. The traffic information may be the number of transmission bits per burst. In this case, the number of transmission bits may be the transport block size. The traffic information may be the throughput per burst. The traffic information may be the average throughput.

[0076] Thirdly, the traffic information may be a packet delay budget (PDB), which is a Quality of Service (QoS) parameter that indicates an upper limit of packet delay between the UE 100 and the UPF, for example.

[0077] Fourth, the traffic information may be a traffic pattern. Specifically, the traffic pattern may be a transmission period and / or a reception period. The transmission period and / or the reception period may represent the duration of one burst or the burst interval. The traffic pattern may be represented by a video frame generation rate (frames per second (fps) or Hz).

[0078] Fifth, the traffic information may be an identifier indicating the transmission direction (UL direction or DL ​​direction) of the XR traffic. This takes into consideration that the traffic pattern of the XR traffic may differ between the UL direction and the DL direction. The UE 100 may transmit traffic information for the UL direction and traffic information for the DL direction. For example, the throughput in the UL direction may be XX and the delay tolerance may be YY, and the throughput in the DL direction may be ZZ and the delay tolerance may be UU.

[0079] Sixth, the traffic information may be represented by a QoS value. The QoS value may represent the base characteristic of XR traffic. The base characteristic may be represented by 5QI. For example, if the QoS value of the traffic information is represented by "5" of 5QI, the QoS represented by "5" of 5QI may be the base characteristic of XR traffic. The QoS value may also be combined with the above-mentioned delay tolerance. For example, if the QoS value is represented by "5" of 5QI and the delay tolerance is represented by 2 ms, it can be expressed as XR traffic with a base characteristic of "5" of 5QI and a delay tolerance of 2 ms.

[0080] Seventh, the traffic information may be the time difference between the assigned CG (Configured Grant) setting and the actual arrival time of a packet. Specifically, the traffic information may be the difference between the transmission start timing in the CG set by the CG setting (or the start timing of DRX active time indicating the time during which UE 100 monitors the PDCCH) and the timing at which a packet is actually received from a higher layer in the AS of UE 100. The traffic information may be the difference between the transmission start timing in the CG and the timing at which a packet from a higher layer becomes queued for transmission (for example, the timing at which PDCP processing is completed). In UE 100, the smaller this difference is, the more likely it is that transmission with low delay will be possible.

[0081] Eighth, when multi-stream transmission is performed in XR traffic, the XR assist information may include traffic information for each stream. In the traffic model of XR traffic described above, multi-streams include two-stream transmission using an I stream and a P stream (above (1.1.2.1)). The XR assist information may include traffic information for the I stream, traffic information for the P stream, etc. In this case, the XR assist information may represent traffic information for each stream in list form. The number of streams may be implicitly represented by the number of entries in the list. Information representing the association between streams may be included in the XR assist information. For example, when two streams are used as an XR session, the information may represent that the two streams are linked to one XR session. When each stream in the multi-stream is linked to a QoS flow ID, a bearer ID, or an LCID, the XR assist information may include information representing the association between each QoS flow ID, a bearer ID, or an LCID.

[0082] In step S12, the gNB 200 performs configuration for the UE 100 based on the XR assist information. For example, the gNB 200 configures a C-DRX (Connected mode-Discontinuous Reception) configuration (or an SPS (Semi-Persistent Scheduling) configuration) in the DL direction and a CG configuration in the UL direction. Note that C-DRX is a technology that performs intermittent operation while the UE 100 maintains an RRC connected state. Furthermore, SPS is a scheduling method that, once DL direction radio resources are allocated, enables DL direction transmissions thereafter using the allocated radio resources periodically. Here, the gNB 200 may perform scheduling based on the XR assist information. The scheduling may be dynamic scheduling (e.g., allocation of radio resources for each PDSCH) in addition to SPS or CG.

[0083] In step S13, the gNB 200 transmits the configuration information to the UE 100. The gNB 200 may transmit the configuration information by including it in an RRC message such as an RRC Setup message. Alternatively, the gNB 200 may transmit the configuration information by including it in a dedicated RRC message. The gNB 200 may transmit the configuration information by including it in a MAC CE or DCI. Note that, if the gNB 200 is unable to configure the UE 100 in step S12, it may transmit an error notification to the UE 100 in step S13. The gNB 200 may transmit an RRC message, a MAC CE, a DCI, or the like, including the error notification, similar to the configuration information. The error notification may include time information when the configuration information is usable (or the configuration information can be transmitted). The time information may be expressed as an elapsed time from the current time (e.g., three hours later). Alternatively, the time information may be expressed as time information (e.g., 24:00, etc.).

[0084] In step S14, UE 100 applies the configuration information. The AS of UE 100 may output transmission timing and / or reception timing information for XR-related communication to a higher layer (e.g., an application layer) based on the configuration information. The higher layer may appropriately adjust the resolution, bit rate, etc. of the XR application according to the configuration information.

[0085] (Modification 1 of the first embodiment) As explained in the first embodiment, there are various types of XR traffic models. For example, in an augmented reality (AR) UL stream, the first stream is for posture and / or control, the second stream is a single stream that combines a scene stream and a video stream, and the third stream is a single stream that combines audio and data (model #3A). As described in Non-Patent Document 2, different performance requirements exist depending on the type.

[0086] In the first modification of the first embodiment, an example will be described in which the information included in the XR assist information includes information on the type of XR traffic. Specifically, the information on the type of XR traffic includes the number of streams and transmission information for each stream.

[0087] This allows the gNB 200 to grasp, for example, what type of stream the UE 100 transmits to the gNB 200 or what type of stream the UE 100 can receive from the gNB 200, and to make settings according to such types for the UE 100. Therefore, in the mobile communication system 1, it becomes possible to appropriately perform communication using XR.

[0088] FIG. 7 is a diagram illustrating an example of operation according to the first modification of the first embodiment.

[0089] 7, in step S20, the UE 100 transmits XR assist information including information on the type of traffic. Note that, similar to the first embodiment, the gNB 200 may request the UE 100 to notify the gNB 200 of the XR assist information prior to step S20.

[0090] The information about the type of traffic is, for example, as follows:

[0091] First, the information may be identification information of a transmission path used to transmit XR traffic. The identification information of the transmission path may be an LCID or the like, as in the first embodiment.

[0092] Second, the information may be information indicating the number of streams.

[0093] Third, the information may be transmission information for each stream. The transmission information may be information indicating at least one of attitude, control, scene, video, audio, data, an I (Intra-coded) video stream, and a P (Predicted) video stream. The transmission information may be QoS information for each stream. The transmission information may be identification information that distinguishes each XR traffic model described in the first embodiment from others. For example, the identification information for the single-stream model in the DL stream of (2.2.1) virtual reality (VR) above is "XXX," and the identification information for model #3A in the UL stream of (2.2.2) augmented reality (AR) above is "YYY." Such traffic model or type identification information may be determined by specifications.

[0094] Fourth, the XR assist information may include information indicating a desire for resources for XR traffic.

[0095] Step S12 and subsequent steps are the same as in the first embodiment.

[0096] (Modification 2 of the first embodiment) In the first embodiment, an example in which traffic information is included in the XR assist information is described, and in the first modification, an example in which information on the type of XR traffic is included in the XR assist information is described, but the present invention is not limited to these. For example, the XR assist information may include upper layer information on the upper layer.

[0097] FIG. 8 is a diagram illustrating an example of operation according to the second modification of the first embodiment.

[0098] As shown in Fig. 8, in step S30, UE100 transmits XR assist information including upper layer information to gNB200. The AS of UE100 may include the upper layer information received from an upper layer (e.g., an application layer) in the XR assist information and transmit it to gNB200. Note that, similar to the first embodiment, gNB200 may request UE100 to notify gNB200 of the XR assist information prior to step S30.

[0099] Examples of upper layer information include the following:

[0100] First, the upper layer information may be information representing any one of virtual reality (VR), augmented reality (AR), and cloud gaming (CG). Also, the upper layer information may be information representing any one of virtual reality (VR), augmented reality (AR), cloud gaming (CG), and mixed reality (MR).

[0101] Second, the upper layer information may be the type of device (i.e., UE100) that executes XR and / or the product name (or model number) of the device. This is because, in particular, the performance or communication content of augmented reality (AR) is expected to differ depending on the device. The gNB200 that receives the upper layer information can ascertain traffic characteristics from the device model number information, etc., and can also configure the UE100 according to the traffic characteristics. Furthermore, the gNB200 can also ascertain QoS information required for each device from the device model number information, etc., and can also configure the UE100 according to the QoS characteristics.

[0102] Third, the upper layer information may be the type of traffic model (or the type of encoding). For example, the type of traffic model may be identification information indicating GOP-based I-frames and P-frames. Alternatively, the type of traffic model may be identification information indicating slice-based I-slices and P-slices. Alternatively, the type of traffic model may be identification information that identifies each of the XR traffic models described in the first embodiment.

[0103] Step S12 and subsequent steps are the same as in the first embodiment.

[0104] (Modification 3 of the first embodiment) In the first embodiment, the UE 100 is described as transmitting the XR assist information to the gNB 200. However, this is not limiting. For example, the CN 20 may transmit the XR assist information to the gNB 200.

[0105] Specifically, an access mobility management device (e.g., AMF 300) transmits XR assist information related to XR to a base station (e.g., gNB 200). The XR assist information may be transmitted from a session management device (e.g., SMF (Session Management Function)) to AMF 300 or gNB 200. Here, XR includes virtual reality, augmented reality, and mixed reality, and represents an environment that combines the real world and virtual space.

[0106] In the third modification, the gNB 200 can also configure the UE 100 for XR communication based on the XR assist information. Therefore, similar to the first embodiment, the mobile communication system 1 can appropriately perform XR-related communication. However, since the XR assist information is transmitted from the CN 20 to the gNB 200, the UE 100 does not need to transmit the XR assist information. Therefore, it is possible to use the radio resources used for transmitting the XR assist information for other radio communication.

[0107] FIG. 9 is a diagram illustrating an example of operation according to the third modification of the first embodiment.

[0108] As shown in Fig. 9, in step S40, the CN 20 may receive traffic information from the XR application server 400. The XR application server 400 performs XR-related communication with the UE 100 via the CN 20 and the gNB 200 of the mobile communication system 1. Therefore, the XR application server 400 can hold traffic information related to XR traffic. The traffic information of the third modification may include the same information as the traffic information described in the first embodiment.

[0109] In step S41, the CN20 (e.g., the AMF300) transmits XR assist information to the gNB200. The XR assist information includes traffic information. The traffic information may be traffic information received from the XR application server 400. The traffic information includes identification information related to the transmission path that transmits the XR traffic, similar to the traffic information in the first embodiment. The identification information may be represented by any one of a QoS flow ID, a PDU session ID, an MBS session ID, and an XR session ID. The XR assist information may include information related to the type of traffic described in the first modification. Alternatively, the XR assist information may include upper layer information related to the upper layer described in the second modification. Prior to step S41, the gNB200 may request the CN20 to transmit the XR assist information to the gNB200. The request may be transmitted, for example, included in an NG message.

[0110] In step S42, based on the XR assist information, the gNB 200 performs settings related to XR communication on the UE 100. As in the first embodiment, the settings may also be C-DRX (or SPS) settings for DL ​​and CG settings for UL.

[0111] In the third modification, an example has been described in which XR assist information is transmitted from CN20 to gNB200. Furthermore, the XR assist information may be transferred from the handover source gNB200-1 (or source cell) to the handover destination gNB200-2 (or target cell) during handover. Specifically, the XR assist information is transmitted from the handover source gNB200-1 (or source cell) or AMF300 to the handover destination gNB200-2 (or target cell) together with a message requesting handover.

[0112] [Second embodiment] In the third modification of the first embodiment, an example has been described in which the CN 20 transmits XR assist information to the gNB 200. In this case, the gNB 200 can set up a bearer (DRB: Data Radio Bearer) between the CN 200 and the UE 100 based on the XR assist information.

[0113] In the second embodiment, an example will be described in which, for example, when a bearer is set up, the gNB 200 transmits setting information including information related to the setting to the UE 100.

[0114] Specifically, first, a base station (e.g., gNB 200) sets up a transmission path for transmitting XR traffic. Second, the base station transmits setting information related to the set transmission path to a user device (e.g., UE 100). Third, the user device transmits XR assist information including identification information related to the transmission path to the base station based on the setting information. Here, the setting information includes information linking the identification information with an XR session ID.

[0115] This allows the UE 100 to transmit XR assist information including a bearer ID (for example, identification information related to a transmission path) to the gNB 200, as described in the first embodiment, for example. Therefore, in the mobile communication system 1, it becomes possible to appropriately perform communication related to XR.

[0116] The operations performed in the second embodiment may be performed before the operations performed in the first embodiment. However, the second embodiment does not necessarily require the operations of the first embodiment as a prerequisite, and may be performed independently.

[0117] FIG. 10 is a diagram illustrating an example of operation according to the second embodiment.

[0118] 10, in step S50, the gNB 200 sets up a transmission path for XR transmission for the UE. The transmission path setting includes, for example, the following:

[0119] First, the transmission path setting may include information linking a bearer ID and an XR session ID. For example, when the gNB 200 links a bearer set between the gNB 200 and the UE 100 to an XR session set between the gNB 200 and the UE 100, information linking the XR session ID of the XR session and the bearer ID of the bearer may be included in the transmission path setting. The bearer ID may be replaced by an LCID, an RLC channel ID, or an RNTI. The bearer ID may also be replaced by a QoS flow ID. The XR session ID may be the stream ID of each stream in the XR traffic. Alternatively, the XR session ID may be the traffic type assigned to each stream (such as an I stream, a P stream, or a type of posture and / or control). Alternatively, the XR session ID may be an identifier that simply indicates that it is used for an XR session. Alternatively, set information of multiple bearers (or linking information of multiple bearers) may be included in the transmission path setting. For example, this is binding information for binding two bearers together to be used for one XR transmission, or binding information for binding a bearer for an I stream with a bearer for a P stream.

[0120] Second, the transmission path setting may include information linking a Temporary Mobile Group Identity (TMGI) with an XR session ID. However, when the UE 100 uses Multicast and Broadcast Services (MBS), the gNB 200 may set the linking information. Therefore, for example, the gNB 200 may set the linking information after the UE 100 transmits MSB interest information or the like to the gNB 200. In the DL direction, when increasing capacity using MBS, linking a TMGI with an XR session ID may be effective. Note that instead of the TMGI, an MRB ID (MBS Radio Bearer ID), an LCID, or an RLC channel ID may be used. Furthermore, instead of the TMGI, an RNTI such as a Group-RNTI (G-RNTI) or a Group Configured Scheduling RNTI (G-CS-RNTI) may be used.

[0121] Third, the transmission path setting may include information linking the DRX setting with the XR session ID. In this case, too, when the gNB200 performs DRX setting in the DL direction for XR transmission, the linking information may be included in the transmission path setting. Furthermore, the transmission path setting may include information linking the SPS setting with the XR session ID. In this case, too, when the gNB200 performs SPS setting in the DL direction for XR transmission, the linking information may be included in the transmission path setting.

[0122] Fourth, the transmission path setting may include information linking the CG (Configured Grant) setting with the XR session ID. During the CG setting period, only data transmission for the XR session may be permitted. In this case, too, when the gNB 200 sets the CG in the UL direction for XR transmission, the linking information may be included in the transmission path setting.

[0123] Fifth, the transmission path setting may include information linking identification information of the transmission path, such as a bearer ID, with the type of XR traffic. For example, the information may be information linking bearer #1 with an I stream (or an I frame), or information linking bearer #2 with a P stream (or a P frame). As in the first modification of the first embodiment, the gNB 200 can transmit the type of traffic used in the transmission path to the UE 100.

[0124] In step S51, the gNB 200 transmits configuration information to the UE 100. The gNB 200 may transmit an RRC message (for example, an RRC Setup message) including the configuration information. Alternatively, the gNB 200 may transmit a MAC CE including the configuration information.

[0125] In step S52, UE100 applies the transmission path settings set by gNB200 by applying the received setting information.

[0126] [Third embodiment] As explained in the first embodiment, XR transmission may include the transmission of video data (or a video stream). Therefore, a larger volume of data may be transmitted than in other cases. In this case, a large number of wireless resources may be required for wireless transmission of XR. On the other hand, when XR transmission has ended, it may be better to release the wireless resources used for the XR transmission as quickly as possible.

[0127] Therefore, in the third embodiment, an example will be described in which, when the transmission of XR traffic is terminated or the transmission of XR traffic is temporarily suspended, the UE 100 notifies the gNB 200 of this fact. Specifically, the user equipment (for example, the UE 100) transmits to the base station (for example, the gNB 200) either termination information indicating that the transmission of XR traffic is terminated or suspension information indicating that the transmission of XR traffic is suspended. Note that the third embodiment may be implemented after the XR assist information described in the first embodiment is transmitted from the UE 100 to the gNB 200 and settings related to XR are performed. However, the third embodiment may be implemented without assuming the first embodiment.

[0128] FIG. 11 is a diagram illustrating an example of operation according to the third embodiment.

[0129] 11, in step S60, settings for an XR session are made to the UE 100. Examples of settings for an XR session include a DRX (or SPS) setting for XR transmission in the DL direction and a CG (Configured Grant) setting for XR transmission in the UL direction. As settings for an XR session, the transmission path setting for XR transmission described in the second embodiment may be made.

[0130] In step S61, the AS of UE 100 receives a notification of the end of the XR application from a higher layer (for example, an application layer). The AS of UE 100 may receive a notification of the end of the XR session from a higher layer. Alternatively, the AS of UE 100 may receive a notification of the end of XR transmission from a higher layer. Alternatively, the AS of UE 100 may receive a notification of the suspension of XR transmission (or the XR session, or the XR application) from a higher layer.

[0131] In step S62, the UE 100 transmits, to the gNB 200, termination information indicating that the XR session has ended. The UE 100 may transmit, to the gNB 200, request information requesting de-configuration of the XR session. Alternatively, the UE 100 may transmit, to the gNB 200, suspend information indicating that transmission of XR traffic will be temporarily suspended. The termination information, request information, or suspend information may include identification information of a transmission path associated with the XR session. As in the first embodiment, the identification information may be any of an LCID, a bearer ID, an RLC channel ID, an RNTI, and an XR session ID. The UE 100 may transmit, to the gNB 200, an RRC message including the termination information, request information, or suspend information. Furthermore, the UE 100 may transmit, to the gNB 200, a MAC CE including the termination information, request information, or suspend information. Furthermore, UE100 may send a DCI including termination information, request information, or suspend information to gNB200.

[0132] In step S63, the gNB 200 de-configures the XR session in response to receiving the termination information. The gNB 200 may temporarily suspend the XR session in response to receiving the suspend information.

[0133] Note that, before starting (or resuming) communication by XR, the UE 100 may transmit to the gNB 200 a notice that the XR communication will be started (or resumed). That is, when communication by XR is started (or resumed), information indicating that an XR session has been started (or information indicating that it has been resumed, or information indicating that the start and / or resume will be performed in the near future) may be notified from the UE 100 to the gNB 200. The notification may be a setting request for the XR session. The notification may include information on a transmission path associated with the XR session. When the notification indicates that the start and / or resume will be performed in the near future, the notification may include information indicating the time of start and / or resume (for example, the start time or the time until the start). The notification may be included in an RRC message, a MAC CE, or the like, and transmitted from the UE 100 to the gNB 200.

[0134] [Other embodiments] A program may be provided that causes a computer to execute each process performed by the UE 100 or the gNB 200. The program may be recorded on a computer-readable medium. Using the computer-readable medium, the program can be installed on a computer. Here, the computer-readable medium on which the program is recorded may be a non-transitory recording medium. The non-transitory recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM.

[0135] In addition, circuits that execute each process performed by UE100 or gNB200 may be integrated, and at least a portion of UE100 or gNB200 may be configured as a semiconductor integrated circuit (chip set, SoC: System on a chip).

[0136] Although one embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to the above, and various design changes can be made within the scope of the gist. Furthermore, it is also possible to combine all or part of each embodiment, each operation, each process, and each step within the scope of consistent combinations.

[0137] As used in this disclosure, the terms "based on" and "depending on" do not mean "based only on" or "depending only on," unless expressly stated otherwise. The term "based on" means both "based only on" and "based at least in part on." Similarly, the term "depending on" means both "depending only on" and "depending at least in part on." Furthermore, the terms "include," "comprise," and variations thereof do not mean including only the listed items, but may mean including only the listed items or may include additional items in addition to the listed items. Furthermore, the term "or," as used in this disclosure, is not intended to mean an exclusive or. Furthermore, any reference to elements using designations such as "first," "second," etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used herein as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way. In this disclosure, where articles are added by translation, such as a, an, and the in English, these articles shall include the plural unless the context clearly indicates otherwise.

[0138] This application claims priority from Japanese Patent Application No. 2022-070308 (filed April 21, 2022), the entire contents of which are incorporated herein by reference.

[0139] (Addendum) In one embodiment, (Supplementary Note 1) a communication control method in a mobile communication system, comprising a step in which a user device transmits XR assist information relating to XR (eXtended Reality) to a base station, the XR including virtual reality (VR), augmented reality (AR), and mixed reality (MR), representing an environment in which the real world and virtual space are integrated.

[0140] (Supplementary Note 2) In the communication control method of (Supplementary Note 1) above, the XR assist information may include traffic information regarding traffic characteristics of XR traffic.

[0141] (Appendix 3) In the communication control method of (Appendix 1) or (Appendix 2) above, the traffic information can represent at least one of identification information regarding the transmission path that transmits the XR traffic, the throughput of the XR traffic, the delay tolerance of the XR traffic, the traffic pattern of the XR traffic, an identifier indicating the transmission direction of the XR traffic, a QoS (Quality of Service) value, and a difference between a CG (Configured Grant) setting and the timing at which a packet is received from an upper layer.

[0142] (Supplementary Note 4) In any of the communication control methods of (Supplementary Note 1) to (Supplementary Note 3) above, the identification information may be any one of a logical channel ID, a bearer ID, an RLC channel ID, an RNTI (Radio Network Temporary Identifier), and an XR session ID that transmits the XR traffic.

[0143] (Supplementary Note 5) In any of the communication control methods described above in (Supplementary Note 1) to (Supplementary Note 4), if the XR traffic is multi-stream, the XR assist information may include the traffic information for each stream.

[0144] (Supplementary Note 6) In any of the communication control methods described above in (Supplementary Note 1) to (Supplementary Note 5), the XR assist information may include information regarding the type of XR traffic.

[0145] (Supplementary Note 7) In any of the communication control methods described above in (Supplementary Note 1) to (Supplementary Note 6), the information regarding the type of XR traffic may include the number of streams and transmission information for each stream.

[0146] (Supplementary Note 8) In any of the communication control methods described above in (Supplementary Note 1) to (Supplementary Note 7), the transmission information may be information indicating, for each stream, at least one of attitude, control, scene, video, audio, data, an I (Intra-coded) stream of video, and a P (Predicted) stream of video.

[0147] (Supplementary Note 9) In any of the communication control methods described above in (Supplementary Note 1) to (Supplementary Note 8), the XR assist information may include upper layer information related to an upper layer.

[0148] (Appendix 10) In any of the communication control methods described above in (Appendix 1) to (Appendix 9), the upper layer information may include at least one of information representing the virtual reality, the augmented reality, and cloud gaming, information relating to the type and product name of the user device, and information representing a traffic model.

[0149] (Appendix 11) Any of the communication control methods of (Appendix 1) to (Appendix 10) above may further include a step in which the base station configures the transmission path for transmitting the XR traffic, and a step in which the base station transmits configuration information regarding the transmission path to the user device, wherein the step of transmitting the XR assist information to the base station includes a step in which the user device transmits the XR assist information including the identification information to the base station based on the configuration information, and the configuration information may include information linking the identification information with an XR session ID.

[0150] (Supplementary Note 12) In any of the communication control methods described above in (Supplementary Note 1) to (Supplementary Note 11), the method may further include a step in which the user device transmits to the base station either end information indicating that transmission of XR traffic is to be terminated, or suspend information indicating that transmission of the XR traffic is to be temporarily suspended.

[0151] Also, in one embodiment, (Supplementary Note 13) a communication control method in a mobile communication system, comprising a step in which an access mobility management device transmits XR assist information related to XR to a base station, wherein the XR includes virtual reality, augmented reality, and mixed reality, and represents an environment in which the real world and virtual space are combined.

[0152] (Supplementary Note 14) In the communication control method of (Supplementary Note 13) above, the XR assist information includes identification information regarding the transmission path that transmits XR traffic, and the identification information can be represented by any one of a QoS flow ID, a PDU (Protocol Data Unit) session ID, an MBS (Multicast and Broadcast Services) session ID, and an XR session ID. [Explanation of symbols]

[0153] 1: Mobile communication system 20 :CN 100:UE 110: Receiving unit 120: Transmitter 130: Control unit 200 :gNB 210: Transmission unit 220: Receiving unit 230: Control unit 300:AMF

Claims

1. A communication control method in a mobile communication system, comprising: A network node transmits, to a user device, configuration information including an identifier of a Quality of Service (QoS) flow corresponding to extended reality (XR) traffic and a session ID associated with the identifier of the QoS flow; and transmitting, by the user equipment, XR assist information to the network node based on the configuration information. Communication control method.

2. The XR assist information includes a period of the XR traffic. The communication control method according to claim 1 .

3. The XR assist information includes a delay tolerance of the XR traffic. The communication control method according to claim 1 .

4. and transmitting a logical channel ID for the XR traffic to the network node. The communication control method according to claim 1 .

5. The method further comprises transmitting, to the network node, a difference between a setting from the network node and a timing at which the user equipment receives a packet from an upper layer. The communication control method according to claim 1 .

6. and the user equipment includes the difference in a MAC CE. The communication control method according to claim 5.

7. and the access mobility management device transmits a delay tolerance for the XR traffic to the network node. The communication control method according to claim 1 .

8. A user device, a receiving unit that receives, from a network node, configuration information including an identifier of a Quality of Service (QoS) flow corresponding to extended Reality (XR) traffic and a session ID associated with the identifier of the QoS flow; a transmitter that transmits XR assist information to the network node based on the setting information. User equipment.

9. A network node for use in a mobile communication system, comprising: a transmitter configured to transmit, to a user device, configuration information including an identifier of a Quality of Service (QoS) flow corresponding to extended reality (XR) traffic and a session ID associated with the identifier of the QoS flow; a receiving unit that receives XR assist information from the user device. Network node.

10. A mobile communication system, A network node transmits, to a user device, configuration information including an identifier of a Quality of Service (QoS) flow corresponding to extended reality (XR) traffic and a session ID associated with the identifier of the QoS flow; The user device transmits XR assist information to the network node based on the setting information. Mobile communication system.

11. To the user device, receiving, from a network node, configuration information including an identifier of a Quality of Service (QoS) flow corresponding to extended reality (XR) traffic and a session ID associated with the identifier of the QoS flow; and transmitting XR assist information to the network node based on the setting information. program.

12. A chipset for a user device, comprising: receiving, from a network node, configuration information including an identifier of a Quality of Service (QoS) flow corresponding to extended reality (XR) traffic and a session ID associated with the identifier of the QoS flow; transmitting XR assist information to the network node based on the setting information. Chipset.

Images