Method and apparatus for using binded service in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. In accordance with an embodiment of the present disclosure, a policy control function (PCF) entity in a wireless communication system includes a transceiver and at least one processor. The at least one processor is configured to update a service-related policy based on a service transmission delay time according to a service flow (delay budget adjustment), where the service transmission delay time according to the service flow is transmitted to a bound device, schedule a quality of service (QoS) based on the service-related policy, and transmit a first message to a session management function (SMF) entity, where the first message is transmitted to the bound device based on the service-related policy. The first message includes a service transmission delay time according to the service flow according to the service flow, an updated service-related policy, and a QoS requirement based on the scheduled QoS according to the service flow.

Description

Technical Field

[0001] The present disclosure relates to a communication method and apparatus for using a tethering service in a wireless communication system. Background Art

[0002] 5G mobile communication technology defines a wide frequency band to achieve fast transmission speeds and new services, and can be implemented in frequencies below 6 GHz ("sub 6GHz") such as 3.5 GHz, and ultra-high frequency bands ("above 6 GHz") such as 28 GHz and 39 GHz known as millimeter waves (mmWave). In addition, 6G mobile communication technology, known as a super 5G system, is considered to be implemented in a terahertz frequency band (e.g., 95 GHz to 3 THz) to achieve a transmission speed 50 times faster than 5G mobile communication technology and ultra-low latency reduced by 1 / 10.

[0003] In the early stage of 5G mobile communication technology, standardization was carried out for beamforming and massive MIMO to mitigate propagation path loss and increase propagation distance in ultra-high frequency bands, support for various parameter sets for efficient utilization of ultra-high frequency resources (such as operation of multiple subcarrier gaps), dynamic operation of time slot formats, initial access technology for supporting multi-beam transmission and broadband, definition and operation of bandwidth part (BWP), new channel coding (such as low-density parity-check (LDPC) codes for massive data transmission and polarization codes for highly reliable transmission of control information), L2 preprocessing, and network slicing for providing dedicated networks for specific services, etc., in order to meet the performance requirements and support services for enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC) and massive machine type communication (mMTC).

[0004] Currently, improvements and performance enhancements to initial 5G mobile communication technologies are being discussed in consideration of the services that 5G mobile communication technologies are intended to support, and physical layer standardization of technologies such as vehicle-to-everything (V2X) for improving user convenience and assisting autonomous vehicles in driving decisions based on position and status information transmitted from VoNR, new radio unlicensed (NR-U) for system operations intended to match various regulatory requirements, NR UE power saving, non-terrestrial networks (NTN) that are direct communication between UEs and satellites to ensure coverage in areas where communication with terrestrial networks is impossible, and positioning technology are being conducted.

[0005] Also being standardized are radio interface architectures / protocols for the following technologies: Industrial Internet of Things (IIoT) for supporting new services through association and convergence with other industries; Integrated Access and Backhaul (IAB) for providing nodes for extending the network service area by supporting access links with radio backhaul links; Mobility enhancements including conditional handover and dual active protocol stack (DAPS) handover; 2-step RACH for NR for simplifying the random access procedure; and system architecture / service areas (e.g., service-based architecture or service-based interface) for 5G baseline architecture combining network function virtualization (NFV) and software defined network (SDN) technologies, and mobile edge computing (MEC) for receiving services based on the location of the UE.

[0006] With the commercialization of 5G mobile communication systems, a large number of connected devices will be connected to the communication network, so it is expected that the functions and performance of 5G mobile communication systems and the integrated operation of connected devices will need to be enhanced. To this end, new research will be conducted on technologies such as extended reality (XR) to effectively support augmented reality (AR), virtual reality (VR), and mixed reality (MR), as well as the use of artificial intelligence (AI) and machine learning (ML), support for AI services, support for metaverse services, and drone communications to improve 5G performance and reduce complexity.

[0007] In addition, the development of such 5G mobile communication systems can lay the foundation for the following technologies: multi-antenna transmission technology such as new waveforms, full-dimensional MIMO (FD-MIMO), array antennas and massive antennas for ensuring coverage in the terahertz band of 6G mobile communication, full-duplex technology for enhancing system network and frequency efficiency of 6G mobile communication technology, and reconfigurable smart surfaces (RIS), high-dimensional spatial multiplexing using orbital angular momentum (OAM), metamaterial-based lenses and antennas for enhancing the coverage of terahertz band signals, AI-based communication technology for achieving system optimization by embedding end-to-end AI support functions and using satellites and artificial intelligence (AI) from the design step, and next-generation distributed computing technology for realizing services with complexity that exceeds the limit of UE operating capabilities through ultra-high performance communication and computing resources. Summary of the invention

[0008] Technical Solution

[0009] The present disclosure provides a method and apparatus for transmitting data using a bonded service to at least one UE using the bonded service in a wireless communication system.

[0010] The present disclosure provides a method and apparatus for transmitting XR data within an allowable delay time considering a delay time of data transmission of at least one UE and at least one bonding device connected to the UE using a service utilizing bonding in a wireless communication system.

[0011] The present disclosure provides a method and apparatus for providing QoS information and policy information for at least one service flow using a bound same service in a wireless communication system.

[0012] According to an embodiment of the present disclosure, a policy control function (PCF) entity in a wireless communication system includes a transceiver and at least one processor. The at least one processor is configured to: update a service-related policy based on a service transmission delay time (delay budget adjustment) according to a service flow, wherein the service transmission delay time according to the service flow is transmitted to a binding device, schedule a quality of service (QoS) based on the service-related policy, and transmit a first message to a session management function (SMF) entity, the first message including the service transmission delay time according to the service flow, the updated service-related policy, and a QoS requirement based on the scheduled QoS.

[0013] According to an embodiment of the present disclosure, a session management function (SMF) entity in a wireless communication system includes a transceiver and at least one processor. The at least one processor is configured to: receive a first message from a policy control function (PCF), the first message including a service transmission delay time according to a service flow, an updated service-related policy, and a quality of service (QoS) requirement; configure the QoS of the service flow to be transmitted to a bound device based on the QoS requirement; and transmit a second message including the service transmission delay time according to the service flow to a radio access network (RAN) through an access and mobility function (AMF) entity based on the updated service-related policy.

[0014] According to an embodiment of the present disclosure, a method performed by a policy control function (PCF) entity in a wireless communication system includes: updating a service-related policy based on a service transmission delay time (delay budget adjustment) according to a service flow, wherein the service transmission delay time according to the service flow is transmitted to a binding device, scheduling quality of service (QoS) based on the service-related policy, and transmitting a first message to a session management function (SMF) entity, the first message including the service transmission delay time according to the service flow, the updated service-related policy, and a QoS requirement based on the scheduled QoS.

[0015] According to an embodiment of the present disclosure, a method performed by a session management function (SMF) entity in a wireless communication system includes: receiving a first message from a PCF, the first message including a service transmission delay time according to a service flow, an updated service-related policy, and a quality of service (QoS) requirement; configuring the QoS of the service flow to be transmitted to a bound device based on the QoS requirement; and based on the updated service-related policy, transmitting a second message including the service transmission delay time according to the service flow to a radio access network (RAN) through an access and mobility function (AMF) entity.

[0016] According to an embodiment of the present disclosure, a method performed by an application server for XR services in a wireless communication system includes: allocating identification information for identifying at least one UE using the same XR service or at least one service flow for transmitting XR data to each of the at least one UE; and providing XR service-related information to a wireless communication system connected to the at least one UE, the XR service-related information including: a delay time for XR data transmission for an XR service consisting of a UE and one or more binding devices connected to the UE, and identification information.

[0017] According to an embodiment of the present disclosure, an application server for XR services in a wireless communication system includes a transceiver and a processor, the processor being configured to: assign identification information for identifying at least one UE using the same XR service or at least one service flow for transmitting XR data to each of the at least one UE, and provide XR service-related information to a wireless communication system connected to the at least one UE through the transceiver, the XR service-related information including: information about a transmission delay time of data transmission to the UE and a bound device connected to the UE, and identification information.

[0018] According to an embodiment of the present disclosure, a method performed by a first network entity for an XR service in a wireless communication system includes: receiving policy information and QoS information related to the XR service provided from a second network entity that manages policy information and QoS information in the wireless communication system, and performing scheduling to consider the delay time of data transmission for the UE and the bound device connected to the UE, and transmitting the XR data to at least one UE and at least one bound device connected to the UE using the same XR service within an allowable delay time. The XR service-related information includes: identification information for identifying at least one service flow for transmitting XR data to at least one UE, or each of at least one UE and at least one bound device connected to the UE using the same XR service, and information related to the delay time of data transmission of the bound device for the XR service.

[0019] According to an embodiment of the present disclosure, a method performed by a first network entity for an XR service in a wireless communication system includes a transceiver and a processor, wherein the processor is configured to: receive, through the transceiver, policy information and QoS information related to the XR service provided from a second network entity that manages policy information and QoS information in the wireless communication system, and perform scheduling to consider the delay time of data transmission for a bound device, and transmit the XR data to at least one UE and at least one bound device connected to the UE using the same XR service within an allowable delay time. The XR service-related information includes: identification information for identifying at least one service flow for transmitting XR data to at least one UE, or each of at least one UE and at least one bound device connected to the UE using the same XR service, and information related to the allowable delay time for data transmission of the bound device considering the XR service.

[0020] According to an embodiment of the present disclosure, an application function (AF) entity in a wireless communication system may include a transceiver and at least one processor. The at least one processor may be configured to: determine a delay time of service transmission to a bound device based on service flow related information and transmission delay time difference information between a UE and a bound device connected to the UE, and transmit a message including the service transmission delay time to an NEF.

[0021] The service flow related information may include at least one of a General Public Subscription Identifier (GPSI), an application identifier, an IP address, and an AF group identifier of the UE.

[0022] According to an embodiment of the present disclosure, a policy control function (PCF) entity in a wireless communication system may include a transceiver and at least one processor. The at least one processor may be configured to: receive information about a delay time of service transmission to a bound device connected to a UE from an NEF, and update a service-related policy based on the service transmission delay time.

[0023] In addition, the service transmission delay time may be determined based on the service flow related information and the transmission delay time difference information between the UE and a binding device connected to the UE.

[0024] Before proceeding to the following detailed description, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprise" and their derivatives mean including but not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean including, included within, interconnected with, contained, contained within, connected to or connected with, coupled to or coupled with, communicable with, cooperating with, interwoven, juxtaposed, proximate to, bound to or bound with, having, having a property of, etc.; and the term "controller" means any device, system, or portion thereof that controls at least one operation, such device may be implemented in hardware, firmware, or software, or some combination of at least two of hardware, firmware, or software. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether local or remote.

[0025] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embedded in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or a portion thereof suitable for implementation with a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disk (DVD) or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical or other communication links that transmit instantaneous electrical signals or other signals. Non-transitory computer-readable media include media that can store data permanently, as well as media that can store data and rewrite data later, such as rewritable optical disks or erasable memory devices.

[0026] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] A more complete understanding of the present disclosure and its many related aspects will be readily obtained by reference to the following detailed description when better understood in conjunction with the accompanying drawings, in which: Figure 1AAn exemplary service transmission path using a bundled service in a wireless communication system according to an embodiment is shown; Figure 1B An exemplary service transmission path using a bundled service in a wireless communication system according to an embodiment is shown; Figure 2 and Figure 3 A scheduling method for multimodal services in a wireless communication system according to an embodiment is shown; Figure 4 and Figure 5 A scheduling method for multimodal services in a wireless communication system according to an embodiment is shown; Fig. 6A , Figure 6B , Fig. 7A and Figure 7B A scheduling method for a multimodal service for one or more UEs in a wireless communication system according to an embodiment is shown; Fig. 8A and Figure 8B A session establishment process for a multimodal service in a wireless communication system according to an embodiment is shown; Fig. 9 shows the structure of a UE according to an embodiment; and Fig.10 The structure of a network entity according to an embodiment is shown. DETAILED DESCRIPTION

[0028] Figures 1 to 2 discussed below Fig.10 The various embodiments used to describe the principles of the present disclosure in this patent document are only for illustration and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0029] Hereinafter, the operating principle of the present disclosure is described below with reference to the accompanying drawings. When it is determined that the subject matter of the present disclosure is unclear, the details of known functions or configurations can be skipped. The terms used in this article are defined in consideration of the functions in the present disclosure, and the terms can be replaced with other terms according to the intention or practice of the user or operator. Therefore, the terms should be defined based on the overall disclosure.

[0030] For the same reason, some elements may be exaggerated or schematically shown. The size of each element does not necessarily reflect the actual size of the element. In all the drawings, the same reference numerals are always used to represent the same elements.

[0031] The advantages and features of the present invention and the methods for realizing these advantages and features can be understood by the embodiments described below in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed herein, and various changes can be made thereto. The embodiments disclosed herein are provided only to inform those of ordinary skill in the art of the categories of the present disclosure. The present disclosure is limited only by the attached claims. Throughout this specification, the same reference numerals indicate the same elements.

[0032] It should be understood that the blocks in each flowchart and combination of flowcharts can be executed by computer program instructions. Since the computer program instructions can be equipped in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, the instructions executed by the processor of the computer or other programmable data processing device generate a device for performing the functions described in the blocks in conjunction with each flowchart. Since the computer program instructions can be stored in a computer-usable or computer-readable memory that can be oriented to a computer or other programmable data processing device to implement the functions in a specified manner, the instructions stored in the computer-usable or computer-readable memory can produce a product including an instruction device for performing the functions described in conjunction with the blocks in each flowchart. Since the computer program instructions can be equipped in a computer or other programmable data processing device, the instructions that generate the process executed by the computer into a series of operation steps are executed on the computer or other programmable data processing device, and the operation of the computer or other programmable data processing device can provide steps for performing the functions described in conjunction with the blocks in each flowchart.

[0033] In addition, each box can represent a part of a module, segment or code, including one or more executable instructions for performing a specified logical function. In addition, it should be noted that in some embodiments, the functions mentioned in the box can occur in different orders. For example, two boxes shown in succession can be executed substantially simultaneously or in reverse order, depending on the corresponding function.

[0034] As used herein, the term "unit" refers to a software element or a hardware element. "Unit" plays a specific role. However, "unit" is not limited to software or hardware. "Unit" can be configured in a storage medium that can be addressed or can be configured to execute one or more processors. Therefore, as an example, "unit" includes elements such as software elements, object-oriented software elements, class elements and task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays and variables. The functions provided in components and "units" can combine fewer components and "units", or can also be divided into additional components and "units". In addition, components and "units" can be implemented to execute one or more CPUs in a device or a secure multimedia card. According to an embodiment, "unit" can include one or more processors.

[0035] In the present disclosure, a User Equipment (UE) may refer to a terminal, an MS (Mobile Station), a cellular phone, a smart phone, a computer, or various electronic devices capable of performing a communication function.

[0036] The embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel forms. In addition, under the circumstances determined by those of ordinary skill in the art, the embodiments of the present disclosure may be modified within such a range that does not significantly depart from the scope of the present disclosure, and such modifications may be applicable to other communication systems.

[0037] In the specific description of the embodiments of the present disclosure, the communication system may use various wired or wireless communication systems, such as the new RAN (NR) as the radio access network and the packet core (5G system, or 5G core network, or next generation core (NG core)) as the core network according to the 5G communication standard of 3GPP, which is a radio communication standardization organization. The embodiments of the present disclosure may also be applied to communication systems with similar technical backgrounds, which only requires a small amount of changes without significantly departing from the scope of the present disclosure, and this may be possible at the discretion of a technician in the field to which the present disclosure belongs.

[0038] As used herein, for the convenience of description, terms used to identify access nodes, terms representing network entities (NEs), terms representing messages, terms representing interfaces between network functions (NFs), and terms representing various pieces of identification information are provided as examples. Therefore, the present disclosure is not limited to these terms, and these terms may be replaced with other terms representing objects having equivalent technical concepts.

[0039] The 5G system may support network slicing, and the services of different network slices may be handled by different protocol data unit (PDU) sessions. A PDU session may refer to an association between a data network and a UE that provides a PDU connection service. Network slicing may be understood as a technology for logically configuring a network with a set of network functions (NFs) to support various services with different characteristics (such as broadband communication services, massive IoT, V2X or other mission-critical services) and separating different network slices. Therefore, even when a communication failure occurs in one network slice, it will not affect the communication in other network slices, so that stable communication services can be provided. In the present disclosure, the term "slice" may be used interchangeably with "network slicing". In such a network environment, a UE may access multiple network slices when receiving various services. In addition, a network function (NF) may be a software instance running on hardware, and may be implemented as a virtualized function instantiated on a network element or an appropriate platform.

[0040] Mobile communication carriers can constitute network slices, and network resources suitable for specific services can be allocated to each network slice or each group of network slices. Network resources can refer to network functions (NFs) or logical resources provided by radio resource allocation of NFs or base stations.

[0041] For example, as described below, a mobile communication carrier may configure network slice A to provide mobile broadband services, configure network slice B to provide vehicle communication services, and configure network slice C to provide XR services. In other words, the 5G network can effectively provide corresponding services to the UE through a dedicated network slice suitable for the characteristics of each service. In a 5G system, a network slice may be represented as a single network slice selection assistance information (S-NSSAI). The S-NSSAI may include a slice / service type (SST) value and a slice differentiator (SD) value. The SST may indicate the characteristics of the services supported by the network slice (e.g., enhanced mobile broadband (eMBB), IoT, ultra-reliable low latency communication (URLLC), V2X, XR services, etc.). The SD may be a value used as an additional identifier for a specific service called an SST.

[0042] Examples of services that need to be characterized by high data rate and low latency (High Data Rate Low Latency (HDRLL) may include extended reality (XR) services, augmented reality (AR) services, virtual reality (VR) services, or cloud gaming services. VR services are services that provide a virtual environment implemented by a computer device with the help of a VR headset, etc. AR services are services that can combine a virtual environment with the real world based on location, geographic information, etc. XR services are services that can not only combine the real environment with the virtual environment but also provide users with information such as touch, hearing, and smell, thereby increasing the user's experience.

[0043] Specifically, XR / AR / VR services can use one or more devices to provide services. For example, when providing audio, video, and tactile services to users, the device providing audio, the device providing video, and the device providing tactile (achieving touch sensation by applying vibration and movement) may be different from each other, and the devices are referred to as bound devices. In this case, the XR / AR / VR data that reaches each device through the network needs to be transmitted to the user within a time suitable for the service to provide XR / AR / VR services with a high user experience. Therefore, according to an embodiment, a service that transmits different types of XR data to users within a delay time suitable for the XR service when providing XR / AR / VR services (hereinafter, for the convenience of description, collectively referred to as XR services) is referred to as a multimodal service. In the present disclosure, for the convenience of description, the term "multimodal service" is used, and various other terms may be used to indicate the transmission of one or more data to the user within a delay time suitable for the service.

[0044] In the present disclosure, although for the convenience of description, a multimodal service is described based on an XR service in an embodiment of the present disclosure, the present disclosure can also be applied to various data services and XR services that require coordination of multiple devices to provide services to one user. XR service is an example of a service using binding, which may require the connection of multiple binding devices, and in the present disclosure, XR services, XR data, etc. are not limited to those services related to XR, but include those services used for binding connection services and data for binding connection services. Therefore, it should be noted that the embodiments of the present disclosure are not limited to XR services.

[0045] Therefore, depending on the service scenario, each XR device for XR service can directly access the 5G network to provide services, or the XR device can be connected to one UE to access the 5G network through, for example, bonding to provide services.

[0046] According to the present disclosure, when various types of XR service data (such as audio, video, or tactile) are transmitted to a UE used by the same user and a bound device connected to the UE, considering the transmission delay time between the UE and the bound device, the XR service data can be transmitted to the UE at a similar time so as to be transmitted to the user within an allowable delay time, thereby enhancing the user's service experience.

[0047] In addition, according to the present disclosure, in order to schedule while considering the binding transmission delay time when transmitting various types of XR data to the UE and one or more binding devices connected to the UE so as to use the same XR service, QoS and policy information can be defined, and the relevant QoS and policy information can be transmitted to the NG-RAN and UPF to seamlessly provide multimodal services.

[0048] Figure 1A An exemplary service transmission path of a service (eg, an XR service) using bundling in a wireless communication system according to an embodiment is shown.

[0049] Figure 1A Exemplary transmission paths 11, 12, and 13 are shown, through which XR data according to the XR service is transmitted from the application function (AF) / application server (AS) 300 to one UE 100 used by the user through the UPF 260 and the next generation radio access network (NG-RAN) 210. The UE 100 can operate as bound XR devices 110a and 110b, which receive different types of XR data, such as audio data, video data, and haptic data.

[0050] Figure 1B Another exemplary service transmission path of a service (eg, an XR service) using bundling in a wireless communication system according to an embodiment is shown.

[0051] Figure 1B Exemplary transmission paths 21, 22, 23, and 24 are shown, through which XR data according to the XR service is transmitted from the AF / AS 300 through the UPFs 260a and 260b and the NG-RAN (or RAN) 210 to a plurality of XR devices 110a and 120a connected to a plurality of UEs 110 and 120 used by one user. Each of the XR devices 110a and 120a bound to the UEs 110 and 120 may receive different types of XR data, such as audio data, video data, or haptic data. The AF / AS 300 may be, for example, an application server of an external network that provides the XR service.

[0052] In the present disclosure, network technology may refer to standards defined by the International Telecommunication Union (ITU) or 3GPP (eg, TS 23.501, TS 23.502, TS 23.503, etc.), and Figure 1A and Figure 1B Each component included in the network architecture may represent a physical entity, or may represent software that performs a separate function or hardware in combination with software. Reference numerals represented by Nx in the figure, such as N1, N2, N3, ..., etc., indicate known interfaces between NFs in the 5G core network (CN), and related descriptions can be found in the standard specification (TS 23.501). Therefore, a detailed description will be omitted.

[0053] Figure 1A and Figure 1BThe wireless communication system shown may include a radio access network (NG-RAN) and a 5G core network (5GC). The NG-RAN 210 may be a base station (e.g., gNB or integrated access and backhaul (IAB)) supporting a radio access technology in a 5G system. The NG-RAN 210 may provide XR service-related information and / or data transmitted from an AF / AS 300 of an external network through the core network (i.e., 5GC) to a UE 100 connected to bound XR devices 100a and 100b or to UEs 110 and 120 including bound XR devices 110a and 120a. In addition, the NG-RAN 210 may provide the AF / AS 300 with XR service-related information and / or data received from the UE 110, 120, or 100. As shown in FIG. Figure 1B As shown in the example of , the UE (or XR device) can communicate with the AF / AS 300 using a technology that utilizes a side link, such as Prose, to directly communicate with another UE (or XR device) connected to the NG-RAN 210 without directly connecting to the NG-RAN 210, or using a non-3GPP radio access technology, such as Wi-Fi or Bluetooth. In the following embodiments of the present disclosure, the UE can be understood as Figure 1B A UE connected wirelessly or wired to one or more XR devices as shown in the example of Figure 1A As shown in the example of , when the UE includes one or more XR devices, communication is performed between the XR devices and the AS / AF via the 5G system.

[0054] exist Figure 1A and Figure 1B In the embodiment, the 5GC may include network entities such as an access and mobility management function (AMF) 220, a session management function (SMF) 230, 230a or 230b, a policy control function (PCF) 240, a network exposure function (NEF) 250, a user plane function (UPF) 260, 260a or 260b, or a unified data management (UDM) (not shown).

[0055] AMF 220 is an entity for managing access and mobility of UE. AMF 220 can be used as a UE core network endpoint through which the UE connects to other entities of 5GC through NG-RAN. As an example, AMF 220 can perform network functions such as registration, connection, reachability, mobility management, access identification, authentication, and mobility event generation of UE.

[0056] SMF 230, 230a or 230b may perform management functions of the protocol data unit (PDU) session of the UE. For example, SMF 230, 230a or 230b may perform network functions such as session management functions of establishing, modifying or releasing a session and maintaining a link between UPF 260, 260a or 260b and NG-RAN 210, functions of allocating and managing Internet Protocol (IP) addresses of terminals, selection and control of user planes, control of service processing on UPFs, and control of charging data collection.

[0057] The UPF 260, 260a, or 260b may be used to process user data (e.g., XR data) of the UE, and may play a role in processing the XR data to transmit the XR data generated by the UE to the AF / AS 300 or to transmit the data introduced from the AF / AS 300 to the UE. The UPF 260 may perform network functions such as acting as an anchor point between radio access technologies (RATs), providing a connection to a PDU session and the AF / AS 300, packet routing and forwarding, packet inspection, application of user plane policies, creation of service usage reports, or buffering.

[0058] The UDM performs functions such as generating authentication information for 3GPP security, handling user IDs, managing a list of network functions (NFs) supporting UEs, and managing subscription information. The Unified Data Repository (UDR) may perform functions of storing and providing subscription information managed by the UDM, structured data for exposure, and application data related to the Network Exposure Function (NEF) 250 or services.

[0059] PCF 240 is an NF that manages operator policy information for providing services in the 5G system. UDR can store the subscription information of the UE and can provide the subscription information to the UDM. In addition, UDR can store operator policy information and can provide operator policy information to PCF. NEF 250 can be responsible for transmitting / receiving events occurring in the 5G system and supported capabilities to the outside. For example, NEF 250 can perform various functions, such as securely supplying information about AF / AS 300 to 5GC, converting internal / external information and storing it in UDR and then redistributing information received from other NFs.

[0060] The UE may access the NG-RAN 210 and register in the 5G system. For example, the UE may access the NG-RAN 210 to perform a UE registration process with the AMF 220. During the registration process, the AMF 220 may determine a network slice available for the UE to access the NG-RAN 210 and assign it to the UE. The UE may select a network slice and establish a PDU session to communicate with the AF / AS 300. One PDU session may include one or more Quality of Service (QoS) flows, and each QoS flow may set different parameters to provide different transmission performance required for each application service.

[0061] In such Figure 1A and Figure 1B In the example communication system, considering the delay time of transmission to the bound devices 100a, 100b, 110a and 120a for providing XR services, the XR data received by each UE 100, 110 and 120 and the XR device including the bound devices 100a, 100b, 110a and 120a bound to the UE should be transmitted to each XR device bound to the UE within the allowable delay time. Therefore, when the XR data from the AF / AS 300 is transmitted to the UE including the XR device or the UE connected to the XR device through the 5G system, the required time should be within the allowable range including the delay time of transmission to the bound device. For example, when the user of the XR device touches an object in the virtual space, the sound, touch and image heard should be transmitted to the UE within the allowable delay time including the delay time of transmission to the bound device, and transmitted to the XR device wired / wirelessly connected to the UE or the XR device included in the UE, so as to enable multimodal services according to the embodiment.

[0062] To this end, according to an embodiment of the present disclosure, a scheme is described for providing QoS and a strategy for transmitting XR data to a network so as to implement a service for enhancing the user experience of XR services (i.e., multimodal services) by controlling the time required for XR data for providing XR services to users to be transmitted to each XR device directly / indirectly connected through a 5G system so that it falls within an allowable delay time including the delay time of transmission between bound devices.

[0063] Furthermore, although the embodiments of the present disclosure are described in view of a downlink in which XR data is received by at least one UE, the scheme proposed in the present disclosure may be applicable to an uplink in which XR data is transmitted by at least one UE in the same / similar manner.

[0064] refer to Figure 1A, assuming as an example that the same user uses one UE 100 connected to or including an XR device for XR service, and UE 100 receives video, audio, and tactile data 11, 12, and 13 as XR data through a transmission path from AF / AS 300 to UPF 260. XR data is data used to provide the same XR service. Considering the transmission delay time difference between the XR UE and the bound device connected to the UE (hereinafter referred to as "delay budget difference adjustment"), the present disclosure proposes policy information and / or service quality information for a service flow for transmitting XR data, which uses binding connection information (Bluetooth or Wi-Fi) about the bound device connected to the UE or at least one of the transmission delay time between the XR UE and the bound device connected to the UE measured by the UE to provide the same XR service, and proposes various procedures for providing XR services by signaling the proposed information between the AF / AS 300 and the 5G system or between network entities of the 5G system. In Figure 1A In the 5GC, the SMF 230 may perform session management in order to maintain a link between the UPF 260 transmitting the XR data and the NG-RAN 210, and the PCF 240 may provide QoS information and / or policy information considering a bound device transmission delay time (delay budget adjustment) associated with the transmission of the XR data.

[0065] In the present disclosure, as information for identifying XR data, at least one of the following (hereinafter referred to as AF-specific service flow (SF) group ID) may be used: for example, an XR application ID for providing XR services or an XR application function (AF) ID of the AF / AS 300, a user ID indicating a user to be served by the UE on an application of the XR service, or an AF-specific SF group ID indicating a group of UEs (or XR devices) receiving the XR service and / or a group of service flows related to the XR service. In addition, since it is necessary to indicate a UE ID of the UE, an IP address of the UE, or a general public subscription identifier (GPSI) assigned to the UE, or an AF-specific GPSI, at least one of a PDU session ID of a PDU session for transmitting XR data in a 5G system and an XR-specific QoS flow identifier (QFI) for identifying a QoS flow related to the XR service may be used in an embodiment of the present disclosure. In an embodiment of the present disclosure, it may be assumed that a separate QoS flow is to be allocated to the XR service to support high data rate (eMBB), ultra low latency (URLLC) services.

[0066] Furthermore, in addition to information for identifying XR data related to the same XR service (e.g., an AF-specific SF group ID), an application data unit (ADU) identifier or an ADU sequence number may be used to indicate a unit of XR data at an application layer or a media layer.

[0067] In addition, in describing the embodiments of the present disclosure, unless otherwise specified, the XR application ID, XR AF ID, application ID, and AFID may be used to indicate an application, application service, or AF related to an XR service. In addition, unless otherwise specified, a user ID and an AF-specific SF group ID may be used to identify a UE used by a user or the same XR service. In other words, in an embodiment of the present disclosure, an AF-specific SF group ID may be used to identify a group of XR service flows (or a group of multiple XR data) related to the same XR service or to identify one or more UEs (or XR devices) related to the same XR service. In addition, unless otherwise specified, the UEID, SUPI, GPSI, AF-specific GPSI, and UE IP address used to indicate the UE may be used for the same purpose.

[0068] In the following, reference Figure 2 and Figure 3 , various methods are described for transmitting at least one XR data of an XR service (which is a service using binding) to a UE and one or more bound devices connected to the UE of the same user within an allowable delay time, taking into account the difference caused by the transmission delay between the service flow of the UE and the service flow of the bound device (delay budget difference adjustment). Therefore, in the case where the UE has an XR device connected to one or more bound devices, when at least one XR data is transmitted to the bound device for the same XR service, the user's experience of the XR service can be enhanced when each XR data is received within the allowable delay time, taking into account the difference caused by the transmission delay between the service flows (delay budget difference adjustment), so that the XR service can be stably provided. To this end, QoS request information and / or policy information of the XR service flow of at least one bound device connected to the UE can be provided from the AF / AS through the PCF or SMF to the UPF and NG-RAN (hereinafter referred to as "RAN") that transmit the at least one XR data. The QoS request information and / or policy information may include information indicating the difference caused by the transmission delay between the UE and the service flow of the bound device (delay budget difference adjustment). The delay time information occurring when transmitting at least one XR service stream (or at least one XR data) transmitted to the bound device for the same XR service may be provided as the delay budget difference adjustment and the delay budget adjustment as described above. Figure 2 and Figure 3 For a basic description of the network entities (SMF, PCF, NEF, etc.) operating in the embodiments, please refer to the combined Figure 1B For the above description. Figures 2 to 3 For a basic description of messages transmitted / received between network entities in the embodiments of the present invention, reference may be made to the 3GPP NR standards (eg, TS 23.501, TS 23.502, TS 23.503, etc.).

[0069] Figure 2 and Figure 3 A method of transmitting XR data for an XR service in a wireless communication system according to an embodiment is illustrated. Figure 2 and Figure 3 The embodiment is a specific example of transmitting XR service related information from AF / AS to UPF and NG-RAN through PCF, and QoS for multimodal services using binding devices is applied. Figure 2 and Figure 3 An example is a process of sending multiple XR data for the same XR service to a binding device and transmitting each XR data within an allowable delay time, taking into account a transmission delay time between a user's UE and at least one binding device connected to the UE from an AF / AS.

[0070] refer to Figure 2 and Figure 3 , consider the case of using XR services through a user's UE (UE). Figure 2 and Figure 3 In the example of , the UE may be a UE including an XR device or connected to an XR device.

[0071] Although in Figure 2 and Figure 3 Not shown, but in Figure 2 Step S200 before step S201 in or Figure 3 In step S300 before step S301 in , basic settings for using XR services between the UE and the 5G system may be performed. For example, assume that an XR-specific S-NSSAI is configured in the UE and / or the network, which is an identifier of a dedicated network slice for the XR service. In this case, the XR-specific S-NSSAI may include an SST for the XR service or an SST for the XR service provided by a communication operator. In addition, the XR-specific S-NSSAI may include a slice differentiator (SD) for identifying a specific XR service or a specific XR service application. The UE may transmit at least one of the GPSI, application ID, IP address, service flow group ID, and delay budget difference adjustment (transmission delay time difference) of the UE to the DN (AS or AF).

[0072] In addition, the subscription information about the UE may include an XR-specific S-NSSAI corresponding to the XR service that can be received by the UE through the network, or may include an AF / AS ID, which is an ID or application ID of the AF / AS that provides the XR service to the UE and / or an AF-specific GPSI or GPSI that is an ID used by the AF / AS to define the UE. In addition, when a group of UEs (or XR devices) are predetermined to receive the XR service together, an AF-specific SF group ID or user ID or pairing information for defining the group may be included in the subscription information. Therefore, when the subscription information includes the AF-specific SF group ID, the process for configuring the AF-specific SF group between the AF / AS and the UE (e.g., UE1 or UE2) and the process for providing the AF-specific SF group ID (the AF-specific SF group ID is information indicating the configured group or user ID or pairing information) to the 5G system can be omitted, and the information can be updated by the network.

[0073] A UE for receiving XR services can access an AF / AS that provides XR services, and in this case, the UE can access the AF / AS through a 5G system or Wi-Fi. The UE can access the AF / AS using various communication schemes. The UE connected to the AF / AS can transmit information related to the XR device connected to the UE. The information may be an actual measured transmission delay value that occurs during XR transmission between the UE and the XR device connected thereto, or XR service related information may be transmitted through a binding profile of the binding device (information such as a binding device connection type or codec). The binding profile information about the binding device may include a binding service flow indication and a binding device service flow ID. The AF / AS may identify the binding device service flow based on the corresponding information, or may use an average delay information value based on information about the binding profile defined by the XR service operator.

[0074] For example, when the connection between a bound device using an XR service and a UE is made via a Bluetooth connection, and the UE does not provide the bound device latency information of a separate connection to the AF / AS, if the corresponding service flow transmission uses the aptX LL compression algorithm to provide the XR service, the AF / AS may assume that the bound transmission latency of the service flow is 34 ms based on the bound profile received through the UE, and use the latency when scheduling the bound device XR data.

[0075] In addition, during the XR service, the transmission delay time information between the UE and the bound device connected to it can be fixedly set based on the measurement at the time of initial connection or the specified binding transmission delay time, or the transmission delay time between the UE and the binding device can be re-measured periodically or irregularly according to, for example, changes in the user's environment or the user's request, and the updated information can be transmitted to the AF / AS.

[0076] For example, considering the initial binding transmission delay time of the XR UE and the bound XR UE, when the service user uses the XR service, the transmission delay time value between the UE and the bound device changes due to reasons such as changes in the user's environment. If a difference in service flow occurs between the UE and the bound device when using the service (for example, audio / video perception mismatch), the user re-measures the transmission delay time between the UE and the bound device according to the user's request, and transmits the corresponding XR service requirements to the AF / AS, thereby performing QoS scheduling of the service flow.

[0077] When supporting a multimodal service according to the present disclosure, the XR service-related information may include a value of a binding transmission delay time difference (delay budget difference adjustment) that occurs when data according to a service flow is transmitted to a UE and a binding device connected to the UE and processed. In addition, a UE ID (e.g., SUPI or GPSI or AF-specific GPSI or UE IP address) may be included in the XR service-related information to identify the UE corresponding to (belonging to) the AF-specific SF group ID while providing the XR service-related information and the AF-specific SF group ID (e.g., multimodal service ID) from the AF / AS to the 5G system. In addition, the XR service-related information may be provided from the 5G system to the corresponding UE.

[0078] XR service-related information may also be referred to as "multimodal service-related information".

[0079] The XR service-related information may be provided by the AF / AS to the NEF of the 5G system and transmitted from the NEF to the PCF. The XR service-related information transmitted from the AF / AS may include multiple parameters for QoS and scheduling, and all or part of the multiple parameters may be allowed to be applied as is, or changed and applied, in the 5G system. Therefore, when at least part of the parameters of the XR service-related information transmitted from the AF / AS to the NEF is changed in the 5G system, the XR service-related information transmitted from the PCF to the SMF, UPF, and NG-RAN may be applied in the UPF and NG-RAN. Therefore, the XR service-related information transmitted from the AF / AS to the NEF and the XR service-related information transmitted from the PCF to the SMF, UPF, and NG-RAN may be separated. However, in the embodiments of the present disclosure, for the convenience of description, they are collectively referred to as XR service-related information.

[0080] In addition, in the present disclosure, information for detecting service flows by UPF and SMF (hereinafter referred to as "service flow detection information") may include at least one of AF / AS ID, source ID address and port information about AF / AS, sequence number (SN), or ID of ADU, which is application-level packet information. The service flow detection information may be transmitted from AF / AS to PCF through NEF, and may be transmitted to UPF via PCF and SMF. SMF may transmit updated QER (QoS Enforcement Rules) to UPF.

[0081] In an embodiment of the present disclosure, when calculating a delay budget adjustment (DBA) for a service flow of a bound device to a UE, it may be determined that the DBA has a value less than the service flow from the network to the UE minus a packet delay budget (PDB) for the delay time from the UE to the bound device.

[0082] refer to Figure 2 , in S201, based on the information (GPSI, application ID, AF specific group ID (e.g., multimodal service ID) (not shown) received in S200 for identifying the service flow transmitted to the bound device) and the binding transmission delay time difference (delay budget difference adjustment) or the binding transmission delay time of each service flow (according to the binding (device) delay budget of the service flow) information, the AF 800-1 can calculate the transmission delay time (delay budget adjustment) of the service flow transmitted to the bound device.

[0083] In an embodiment, when the binding transmission delay time information is calculated using the statistical characteristic value by measuring the corresponding binding device, the binding transmission delay time information may be expressed as a binding transmission delay time difference (delay budget difference adjustment) which indicates an additional time difference occurring due to transmission from the UE to the binding device, or as a binding transmission delay time according to a service flow according to a service operator policy. In an embodiment, when a predefined network type or service characteristic (e.g., codec type) is transmitted to the AF without measuring the transmission delay time from the UE to the binding device, and the transmission delay time is mapped due to binding based on the defined value, the binding transmission delay time information may be transmitted per service flow.

[0084] In an embodiment, AF 800-1 may calculate a packet delay budget (PDB) for a service transmission delay time according to a service flow configured with a group ID identical to a multimodal service ID based on the binding device transmission delay time information, taking into account the delay time difference between the service flows. The calculated transmission delay time may be expressed as service flow transmission delay time information about one or more binding devices for each UE, which depends on the number of binding devices connected to the UE.

[0085] Thereafter, in step S202 , the AF 800 - 1 may transmit an AF session service operation generation (Nnef_AFsessionWithQoS_Create) or update (Nnef_AFsessionWithQoS_Update) request message including service flow ID information and QoS requirement information related to a bound device connection service (eg, XR service) related to a transmission delay time to the NEF 700 - 1 .

[0086] A policy authorization service generation (e.g., Npcf_PolicyAuthorization_Create) or update (e.g., Npcf_PolicyAuthorization_Update) request message including QoS requirement information related to a bound device connection service (e.g., XR service) received from AF 800-1 through S203 and S204 may be transmitted to PCF 600-1, the QoS requirement information including bound device ID information and transmission delay information about the bound device according to the service flow. In S205 and S206, the XR service-related update request-related response information of AF 800-1 received in S204 is transmitted to AF 800-1 through NEF 700-1. In an embodiment, a reliable AF 800-1 may transmit QoS requirement information related to a bound device connection service (e.g., XR service) directly to PCF 600-1 without passing through NEF 700-1.

[0087] In S207, based on the bound device connection service (e.g., XR service) related QoS requirement information (including the transmission delay time (delay budget adjustment) according to the service flow) received from the AF 800-1 to be transmitted to the bound device, the PCF 600-1 may update the corresponding service flow related policy and charging control rules (PCC rules). Basically, the default policy and charging control rules (PCC rules) according to the service flow may be generated based on the XR service related information according to the XR service flow transmitted to the UE 100-1.

[0088] In an embodiment, when considering a bound device requested by AF 800-1 in PCF 600-1, when an updated packet delay (PDB) value of a service flow to be transmitted to the bound device based on XR service-related update information has a standard 5QI characteristic value, the 5QI value of the corresponding service flow can be changed to a 5QI value having a matching QoS characteristic value, and QoS scheduling can be performed.

[0089] For example, in Figure 1AIn the XR service where the UE is composed of one or more bound devices, the default policy and charging control rules according to the service flow can be updated in the AF based on the XR service-related QoS update request information including the transmission delay time related information (delay budget difference adjustment) of each bound device in the UE, and QoS scheduling can be performed. Figure 1A As shown, it indicates that service flow 1 of the default XR service may be allowed without considering the bound transmission delay time. Figure 1A 11 and service flow 2 ( Figure 1A 12) The packet delay budget (PDB) value of the maximum time of the default delay is 150 ms and 100 ms, and based on the corresponding PDB value, the 5QI value of each service flow can be set to 1 and 2, respectively, see Table 1 below. In this case, when the transmission delay time of the bound device of the service flow 2 of the bound device based on the XR service-related QoS update request information transmitted to the PCF is 50 ms, the PCF can consider the XR service update request information and consider the PDB value QoS scheduling of the service flow 2 of the bound device to be 50 ms. When it is determined to use the standardized 5QI value for PCC rule update, the 5QI value of the service flow 2 of the bound device can be changed from 2 to 3 by referring to Table 1 below, and the policy and charging control rules of the service flow 2 can be updated. In an embodiment, when considering a bound device connection, when the additional bound device transmission delay time is expected to be greater than the delay time of the existing service QoS (for example, when the additional binding delay time connected to an interactive audio service stream is 100 ms), it may be necessary to change the delay value of the video service stream for multimodal support of packet service streams bundled to the same service on an application, such as a video service stream connected to a corresponding audio service stream, while changing the delay value of the audio service stream for the bound device connection.

[0090] In this case, in an embodiment, AF 800-1 may adjust the PDB value of the service flow not transmitted to the binding device according to the transmission delay time of the binding device when adjusting the delay value according to the service flow based on the transmission delay time of the binding device. PCF 600-1 may determine whether to perform a QoS update based on the updated PDB requirement based on the transmission delay time of the binding device transmitted from AF 800-1 as described above, and make changes for each service flow. The binding transmission delay time value may include at least one of a delay adjustment value for the service flow considering the binding device, a binding transmission delay time, and a delay time difference value considering the allowable delay time difference of the service flow between the binding device and the non-binding service flow grouped and provided service by the binding device.

[0091]

Table 1

[0092] Example of mapping standardized 5QI to QoS characteristics

[0093] Thereafter, in S208, PCF 600-1 may transmit a session management policy control update notification (Npcf_SMPolicycontrol_UpdateNotify) request message to SMF 500-1, the session management policy control update notification request message including the XR service-related policy and charging control rules according to the service flow updated based on the XR service requirements in S207 through the SM policy association modification process. In S209, SMF 500-1 may transmit a session management policy control update notification (Npcf_SMPolicycontrol_UpdateNotify) service operation response message to PCF 600-1. In S210 (S210a and S210b), the SMF 500-1 may receive the bound device connection service (e.g., XR service) related QoS requirements and the default policy and charging control rules according to the service flow received from the PCF 600-1, allocate a corresponding QFI for each service flow, and transmit service flow detection information and XR service related information and / or forwarding information to the UPF and RAN (or NG-RAN) 200-1 for each QFI. The forwarding information may be information used in the process of transmitting (forwarding) XR service flow data from each UPF 400-1 to the RAN 200-1. Based on the updated policy and charging control rules received in S208, the SMF 500-1 that receives the service flow detection information and XR service related information in S210a detects the ID of the QoS flow of the service flow, and transmits the information to be applied to the corresponding QoS flow to the UPF 400-1 through the N4 session establishment or modification process. Therefore, the information transmitted to the UPF 400-1 may include at least one of a QoS flow ID (QFI) of the XR service flow and information for detecting the QoS flow ID, such as an AF ID or an application ID or AF / AS address information, i.e., an IP address and port information or application-level packet information, i.e., an ADU ID or a sequence number (SN). In addition, the information transmitted to the UPF 400-1 in S210a may include at least one of an indicator indicating whether a multimodal service is applied to the service flow, a difference in delay time allowed when applying the multimodal service, and information such as a bound transmission delay time (delay budget adjustment) in an environment where a bound device connection is used.

[0094] Thereafter, in S210b, the SMF 500-1 may include at least one piece of SM policy information in an N2 SM message container and transmit it to the RAN 200-1.

[0095] - QFI of the service flow, -AF ID - Application ID -AF specific SF group ID - When a multimodal service using bonded devices is applied, the bonded device transmission delay time value (delay budget adjustment) In an embodiment, in S210b, when a message application uses a multimodal service of a bound device through an N1N2 message transfer (Namf_Communication _N1N2Message Transfer) service operation, the SMF 500-1 may transmit at least one of the QFI, AF ID, application ID, AF-specific SF group ID (e.g., multimodal service ID) and time-sensitive communication assistance information (TSCAI) of the service flow to the AMF 300-1, including information such as a bound device transmission delay time value (delay budget adjustment). The AMF 300-1 may transmit the TSCAI and QFI (including information such as a bound device transmission delay time value (delay budget adjustment)) received from the SMF 500-1 to the RAN 200-1 using an N2 SM message.

[0096] refer to Figure 3 , in S301, AF 800-2 can calculate the transmission delay time (delay budget adjustment) according to the service flow transmitted to the bound device based on the information (GPSI, application ID, AF specific group ID (e.g., multimodal service ID) (not shown) received in S300 for identifying the service flow transmitted to the bound device, and binding transmission delay time difference (delay budget difference adjustment) information or binding device transmission delay time information according to the service flow (including binding device connection information, such as connection type and codec information of the binding part).

[0097] The calculated transmission delay time may be expressed as transmission delay time information according to the service flow about one or more bound devices, depending on the number of bound devices connected to the UE for each UE. Thereafter, in step S302, the AF 800-2 may transmit an AF session service operation generation (Nnef_AFsessionWithQoS_Create) or update (Nnef_AFsessionWithQoS_Update) request message including service flow ID information and bound device connection service (e.g., XR service) related QoS requirement information (including transmission delay information according to the service flow of the bound device) to the NEF 700-2.

[0098] A policy authorization service generation (e.g., Npcf_PolicyAuthorization_Create) or update (e.g., Npcf_PolicyAuthorization_Update) request message including QoS requirement information related to a bound device connection service (e.g., XR service) received from AF 800-2 through S303 and S304 may be transmitted to PCF 600-2, the QoS requirement information including bound device ID information and transmission delay information about the bound device according to the service flow, including GPSI, application ID, AF specific group ID (e.g., multimodal service ID). In S305 and S306, the received response information related to the bound device connection service update request of AF 800-2 may be transmitted to AF 800-2 through NEF 700-2. In an embodiment, a reliable AF 800-2 may transmit QoS requirement information related to a bound device connection service (e.g., XR service) directly to PCF 600-2 without passing through NEF 700-2.

[0099] In S307, PCF 600-2 may determine a corresponding service flow related policy information update (PCC rule update) based on the bound device connection service (e.g., XR service) related QoS requirement information (including the transmission delay time according to the service flow (delay budget adjustment)) to be transmitted to the bound device received from AF 800-2. If the QoS based on the current default service flow can satisfy the requirements considering the corresponding bound device even when the transmission delay time information according to the service flow about the bound device received from AF 800-1 is considered according to the preset policy of the service operator or the network, the PCF 600-2 may perform the PCC rule update including considering the transmission delay time information according to the service flow of the corresponding bound device without performing a separate QoS update.

[0100] Thereafter, in S308, based on the XR service related information according to the service flow basically transmitted to the UE through the SM policy association modification process, the PCF 600-2 may transmit PCC rule update information to the SMF 500-2 using a session management policy control update notification service operation (Npcf_SMPolicycontrol_UpdateNotify) request message, the PCC rule update information including QoS update information according to the service flow based on the binding device connection service requirement of the binding device requested by the AF, the XR service default policy for each service flow QoS, and the charging control rule (default PCC rule). In addition, in S309, a message in response to the request may be transmitted from the SMF 500-2 to the PCF 600-2.

[0101] If it is determined in S307 that PCF 600-2 can meet the service requirements considering bound device connections and default QoS information according to service flows, it can be determined to update PCC rules including default QFI and QoS profiles and bound device transmission delay information according to service flows that additionally consider bound devices.

[0102] In S310, SMF 500-2 can receive service-related default policies and billing control rules and information related to the bound device connection service, including binding transmission delay time information and information for identifying the service flow transmitted to the bound device received in S308 (GPSI, application ID, AF specific group ID (e.g., multimodal service ID)), and receive corresponding service flow-related update policy information and transmit QoS scheduling information to RAN 200-2 and UPF 400-2.

[0103] In S311 (S311a and S311b), SMF 500-2 can receive the QoS requirements related to the bound device connection service (e.g., XR service) received from PCF 600-2 and allocate a corresponding QFI to each service flow according to the policy and charging control rules of the service flow, and transmit the service flow detection information and XR service-related information and / or bound device connection service-related information to UPF 400-2 and RAN (or NG-RAN) 200-2 for each QFI.

[0104] The SMF 500-2 that receives the service flow detection information and the bound device connection service related information in S311a may detect the ID of the QoS flow of the service flow based on the policy and charging control rule updated in S307 in S310, and transmit the information to be applied to the corresponding QoS flow to the UPF 400-2 through the N4 session establishment or modification process. Therefore, the information transmitted to the UPF 400-2 may include, for example, the QoS flow ID (QFI) of the service flow considering the bound device connection and information for detecting the QoS flow ID, such as the AF ID or application ID or AF / AS address information, i.e., IP address and port information or application level packet information, i.e., ADU ID or sequence number (SN). In addition, the information transmitted to the UPF 400-2 in S311a may include at least one of an indicator indicating whether to apply a multimodal service to the service flow considering the bound device connection, a difference in the delay time allowed when applying the multimodal service, and information such as a bound transmission delay time (delay budget adjustment) in an environment using the bound device connection.

[0105] Thereafter, in S311b, the SMF 500-2 may include at least one of the following information as SM policy information in an N2 SM message container and transmit it to the RAN 200-2.

[0106] - QFI of service flow

[0107] -AF ID, - Application ID, -AF specific SF Group ID (e.g. Multimodal Service ID), or - When a multimodal service using bonded devices is applied, the bonded device transmission delay time value (delay budget adjustment) In an embodiment, in S311b, the SMF 500-1 may transmit at least one of the QFI, AF ID, application ID, AF specific SF group ID (e.g., multimodal service ID), and TSCAI of the service flow to the AMF 300-2 through an N1N2 message transfer (Namf_Communication_N1N2Message Transfer) service operation message. The AMF 300-2 may transmit the TSCAI and QFI (including information such as the binding device transmission delay time value (delay budget adjustment)) received from the SMF 500-2 to the RAN 200-2 using an N2 SM message. Figure 4 and Figure 5 A method for transmitting XR data of an XR service (a service using binding) in a wireless communication system according to an embodiment is shown. Figure 4 and Figure 5 The embodiment is a specific example of transmitting XR service related information from AF / AS to UPF and NG-RAN through PCF, and applying QoS of the service considering bound device connection.

[0108] Although in Figure 4 and Figure 5 Not shown, but in Figure 4 Step S400 before step S401 in or Figure 5In step S500 before step S501 in , basic settings for using XR services between the UE and the 5G system may be performed. The UE for receiving the XR service may access the AF / AS that provides the XR service, and in this case, the UE may access the AF / AS through the 5G system or Wi-Fi. The UE may access the AF / AS using various communication schemes. According to the present disclosure, XR service-related information using a binding device based on a multimodal service may include binding transmission delay information, for example, including a value of a binding transmission delay time difference (delay budget difference adjustment) that occurs when data according to a service flow is transmitted to the UE and the binding device connected to the UE and processed. In addition, a UE ID (e.g., SUPI or GPSI or AF-specific GPSI or UE IP address) may be included in the XR service-related information to identify the UE corresponding to (belonging to) the AF-specific SF group ID while providing the XR service-related information and the AF-specific SF group ID (e.g., multimodal service ID) from the AF / AS to the 5G system. The UE may transmit at least one of information about the UE's GPSI, application ID, IP address, service flow group ID, and bound transmission delay information including delay budget difference adjustment to the DN (AS). The SMF may receive a PCC rule including QoS and bound delay information updated based on the bound transmission delay information, and based thereon transmit the updated QoS information to the UPF through, for example, QER.

[0109] refer to Figure 4 In S401, the AF 800-3 may transmit an AF session service operation generation (Nnef_AFsessionWithQoS_Create) or update (Nnef_AFsessionWithQoS_Update) request message to the NEF 700-3, the update request message including QoS requirement information according to the service flow considering the connection of the bound device, such as the binding transmission delay time information, the binding transmission delay time information including, for example, the binding transmission delay time difference (delay budget difference adjustment) and information for identifying the service flow received in S400 and transmitted to the bound device (GPSI, application ID, AF specific group ID (e.g., multimodal service ID)).

[0110] NEF 700-3 may transmit QoS requirement information according to service flow considering bound device connection (including transmission delay information and bound device service flow ID information) from AF 800-3 to PCF 700-3 through policy authorization service generation (Npcf_PolicyAuthorization_Create) or update (Npcf_PolicyAuthorization_Update) request message through S402 and S403.

[0111] In S404, the PCF 600-3 may calculate the transmission delay time (delay budget adjustment) according to the service flow transmitted to one or more bound devices based on the bound device ID information (GPSI, application ID, AF specific group ID (e.g., multimodal service ID)) and the bound device delay time information, the bound device delay time information including the information related to the transmission delay time difference (delay budget difference adjustment) according to the service flow to be transmitted to the bound device in the service-related QoS requirements considering the bound device connection received from the AF 800-3. In an embodiment, when the service flow is bundled with a separate application-level group ID (e.g., multimodal service ID), when calculating the transmission delay time (delay budget adjustment) according to the service flow based on the bound device transmission delay time received from the AF 800-3, the delay time between the service flows may be additionally considered. In an embodiment, if a separate related application-level group ID is not defined, the data packet transmission delay time (delay budget adjustment) considering the binding transmission delay according to the service flow may be calculated based on the bound device transmission delay time according to the service flow.

[0112] In S405 and S406, the service-related update request-related response information received in S403 considering the bound device connection of AF 800-3 is transmitted to AF 800-3 through NEF 700-3. In an embodiment, the reliable AF 800-3 can transmit the bound device connection service (e.g., XR service)-related QoS requirement information directly to PCF 600-3 without passing through NEF 700-3.

[0113] In S407, PCF 600-3 may update the corresponding service flow-related default policy and charging control rules (PCC rules) based on the bound device connection service (e.g., XR service)-related QoS requirement information to be transmitted to the bound device (including the bound device transmission delay time (delay budget adjustment) according to the service flow). Basically, the default policy and charging control rules (PCC rules) according to the service flow may be generated based on the XR service-related information according to the XR service flow transmitted to UE 100-3. PCF 600-3 may determine to update the QoS based on the packet transmission delay time (PDB) value taking into account the binding transmission delay and update the PCC rules including, for example, the binding transmission delay time information for the corresponding default policy and charging control rules.

[0114] Through S408, PCF 600-3 may transmit a session management policy control update notification (Npcf_SMPolicycontrol_UpdateNotify) service operation request message including the policy and charging control rules according to the service flow associated with the service considering the bound device connection updated in S407 through the SM policy association modification process to SMF 500-3. In S409, SMF 500-3 may transmit a session management policy control update notification (Npcf_SMPolicycontrol_UpdateNotify) service operation response message to PCF 600-1.

[0115] In S410 (S410a and S410b), the SMF 500-3 may receive the policy and charging control rules according to the service flow and the service-related QoS requirements in consideration of the bound device connection received from the PCF 600-3, allocate a corresponding QFI to each service flow, and transmit service flow detection information and service-related information and / or forwarding information to the UPF 400-3 and the RAN (or NG-RAN) 200-3 for each QFI. The forwarding information is information used in the process of transmitting (forwarding) the XR service flow data from each UPF 400-3 to the RAN 200-3.

[0116] The SMF 500-3 that receives the service flow detection information and the XR service related information in S410a detects the ID of the QoS flow of the service flow based on the updated policy and charging control rule received in S408, and transmits the information to be applied to the corresponding QoS flow to the UPF 400-3 through the N4 session establishment or modification process. Therefore, the information transmitted to the UPF 400-3 may include, for example, the QoS flow ID (QFI) of the XR service flow and information for detecting the QoS flow ID, such as the AF ID or application ID or AF / AS address information, i.e., IP address and port information or application level packet information, i.e., ADU ID or sequence number (SN). In addition, the information transmitted to the UPF 400-3 in S410a may include an indicator indicating whether to apply a multimodal service to the service flow, a difference in the delay time allowed when applying the multimodal service, and information such as a bound transmission delay time (delay budget adjustment) in an environment where a bound device connection is used.

[0117] Thereafter, in S410b, the SMF 500-3 may include at least one of the following information as SM policy information in an N2 SM message container and transmit it to the RAN 200-3.

[0118] - QFI of the service flow, -AF ID, - Application ID, -AF specific SF group ID, - When a multimodal service using bonded devices is applied, the bonded device transmission delay time value (delay budget adjustment) In an embodiment, in S410b, when a service using a binding device is applied, the SMF 500-3 may transmit at least one of the QFI, AF ID, application ID, AF-specific SF group ID (e.g., multimodal service ID), and TSCAI of the service flow to the AMF 300-3 via a N1N2 message transfer (Namf_Communication _N1N2Message Transfer) service operation message, including information such as a binding device transmission delay time value (delay budget adjustment).

[0119] In an embodiment, the AMF 300-3 may transmit the TSCAI and QFI (including information such as a binding device transmission delay time value (delay budget adjustment)) received from the SMF 500-3 to the RAN 200-3 using an N2 SM message.

[0120] refer to Figure 5 In S501, the AF 800-4 may transmit an AF session service operation generation (Nnef_AFsessionWithQoS_Create) or update (Nnef_AFsessionWithQoS_Update) request message to the NEF 700-4, the update request message including each bound device connection service (e.g., XR service) flow QoS requirement information, such as bound transmission delay time difference (delay budget difference adjustment) information and information for identifying the service flow transmitted to the bound device received in S500 (GPSI, application ID, AF specific group ID (e.g., multimodal service ID)) (not shown). The NEF 700-4 may transmit a policy authorization service generation (Npcf_PolicyAuthorization_Create) or update (Npcf_PolicyAuthorization_Update) request message to the PCF 600-4 through S502 and S503, the update request message including the bound device connection service (e.g., XR service) flow QoS requirement information including the bound device service flow ID information and transmission delay information received from the AF 800-4.

[0121] In S504, PCF 600-4 can calculate the transmission delay time (delay budget adjustment) of the service flow transmitted to one or more bound devices based on the bound device ID information (GPSI, application ID, AF specific group ID (e.g., multimodal service ID)) and the information related to the transmission delay time difference of the service flow to be transmitted to the bound device in the bound device connection service (e.g., XR service) related QoS requirements received from AF 800-4 (delay budget difference adjustment).

[0122] In S505 and S506, the AF's XR service-related update request-related response information received in S503 may be transmitted to the AF 800-4 via the NEF 700-4. In an embodiment, the reliable AF 800-4 may transmit the bound device connection service (e.g., XR service)-related QoS requirement information directly to the PCF 600-4 without passing through the NEF 700-4.

[0123] In S507, PCF 600-4 may determine QoS scheduling using corresponding service flow-related default policies and charging control rules (PCC rules) including a bound device transmission delay time (delay budget adjustment) to be transmitted to the bound device according to the service flow and bound device connection service (e.g., XR service)-related QoS requirement information. Here, the default policy and charging control rules (PCC rules) are XR service-related policy information that considers the QoS characteristics (PDB) between the UPF and the UE assuming that the UE receives one or more service flows. If it is determined in S507 that PCF 600-4 can meet the service requirements considering the bound device connection and the default QoS information according to the service flow, it may be determined to update the PCC rules including the default QFI and QoS profile and additionally consider the bound device transmission delay information according to the service flow of the bound device.

[0124] Through S508, PCF 600-4 transmits QoS requirements related to the bound device connection service (e.g., XR service) (including service flow transmission delay time information (delay budget adjustment) according to the bound device and default service flow policy and charging control rules related to the XR service) to SMF 500-4 through the session management policy control update notification service operation (Npcf_SMPolicycontrol_UpdateNotify) request message through the SM policy association modification process. In S509, SMF 500-4 can transmit a session management policy control update notification (Npcf_SMPolicycontrol_UpdateNotify) service operation response message to PCF 600-4.

[0125] In addition, the PCF 600-4 may transmit information for detecting a service flow (e.g., the above-mentioned service flow detection information) to the SMF 500-4 through the UPF 400-4 and the SMF 500-4. The service flow detection information may include at least one of the following items: for example, an AF ID or an application ID or application server address information (e.g., an IP address and port information) or application-level packet information (e.g., a sequence number or ID of an application data unit (ADU)).

[0126] In S510, SMF 500-4 can receive default policies and charging control rules related to XR services and information related to XR services, including binding transmission delay time information and information for identifying the service flow transmitted to the binding device received in S508 (GPSI, application ID, AF specific group ID (for example, multimodal service ID)), update the corresponding service flow related policy information (PCC rules) and perform QoS scheduling.

[0127] In S511 (S511a and S511b), the SMF 500-4 may receive the QoS requirements related to the bound device connection service (e.g., XR service) received from the PCF 600-4 and the default policy and charging control rules according to the service flow, allocate a corresponding QFI to each service flow, and transmit service flow detection information and XR service related information and / or forwarding information to the UPF 400-4 and the RAN (or NG-RAN) 200-4 for each QFI. The forwarding information is information used in the process of transmitting (forwarding) the XR service flow data from each UPF 400-4 to the RAN 200-4.

[0128] The SMF 500-4 that receives the service flow detection information and the XR service related information in S511a detects the ID of the QoS flow of the service flow based on the policy and charging control rule updated in S510, and transmits the information to be applied to the corresponding QoS flow to the UPF 400-4 through the N4 session establishment or modification process. Therefore, the information transmitted to the UPF 400-4 may include at least one of the QoS flow ID (QFI) of the XR service flow and information for detecting the QoS flow ID, such as AF ID or application ID or AF / AS address information, i.e., IP address and port information or application level packet information, i.e., ADU ID or sequence number (SN). In addition, the information transmitted to the UPF 400-4 in S511a may include an indicator indicating whether to apply a multimodal service to the service flow, a difference in delay time allowed when applying the multimodal service, and information such as a bound transmission delay time (delay budget adjustment) in an environment where a bound device connection is used.

[0129] Thereafter, in S511b, the SMF 500-4 may include at least one of the following information as SM policy information in an N2 SM message container and transmit it to the RAN 200-4.

[0130] - QFI of the service flow, -AF ID, - Application ID, -AF specific SF group ID, - When a multimodal service using bonded devices is applied, the bonded device transmission delay time value (delay budget adjustment) In an embodiment, in S511b, when a multimodal service using a bound device is applied, the SMF 500-4 may transmit at least one of the QFI, AF ID, application ID, AF-specific SF group ID (e.g., multimodal service ID) and information such as a bound device transmission delay time value (delay budget adjustment) of the service flow to the AMF 300-4 through a N1N2 message transfer (Namf_Communication _N1N2Message Transfer) service operation message.

[0131] In an embodiment, the SMF 500-4 may transmit the bound device transmission delay time value (delay budget adjustment) to the RAN 200-4 using a separate container (e.g., TSCAI) according to the policy of the network operator. In this case, the SMF 500-4 may receive operation and policy information for utilizing the corresponding separate container from the PCF 600-4 in S508. The AMF 300-4 may transmit the TSCAI and QFI (including information such as the bound device transmission delay time value (delay budget adjustment)) received from the SMF 500-4 to the RAN 200-4 using an N2 SM message.

[0132] At the same time, although each embodiment of the present disclosure describes the aspect of the UE processing downlink data while receiving XR services, the allowable delay difference can also be met, so that by including information for processing uplink data when forwarding data and XR service-related information for XR services, considering the difference in transmission delay time between the UE and the bound device connected to the UE, the difference between service flows will not produce a sense of perceived mismatch and QoS requirements in the same way as processing downlink data.

[0133] Fig. 6A , Figure 6B , Fig. 7A and Figure 7B A method for transmitting XR data of an XR service (a service using binding) in a wireless communication system according to an embodiment is shown. Fig. 6A , Figure 6B , Fig. 7A and Figure 7B An example is a process of transmitting a plurality of XR data for the same XR service within an allowable delay time considering a transmission delay time between a user's UE from an AF / AS and at least one binding device connected to one or more UEs.

[0134] Refer to Figure 6 ( Fig. 6A and Figure 6B ) and Figure 7 ( Fig. 7A and Figure 7B ), consider using an XR service through a user's UE (i.e., UE1 100-5 and 100-7 and UE2 100-6 and 100-8). In the examples of FIGS. 6 and 7, UE1 100-5 and 100-7 and UE2 100-6 and 100-8 may each include an XR device or may be a UE connected to an XR device. The examples of FIGS. 6 and 7 may be applied in the same manner even when multiple XR devices are connected to one UE, such as Figure 1A as shown in the example.

[0135] Although in Fig. 6A , Figure 6B , Fig. 7A and Figure 7B Not shown, but in Fig. 6A S600 or before S601 Fig. 7A In S700 before S701, a basic setup process for using XR services may be performed between UE1 100-5 and 100-7, UE2 100-6 and 100-8, and the 5G system. The embodiments of Figures 6 and 7 are specific examples of transmitting XR service-related information from AF / AS to UPF and NG-RAN via PCF, and QoS for multimodal services is applied. For example, assume that an XR-specific S-NSSAI is configured in the UE and / or the network, which is an identifier of a dedicated network slice for XR services. In this case, the XR-specific S-NSSAI may include an SST for XR services or an SST for XR services provided by a communication operator. In addition, the XR-specific S-NSSAI may include a slice differentiator (SD) for identifying a specific XR service or a specific XR service application.

[0136] In addition, the subscription information about the UE (e.g., UE1 or UE2) may include an XR-specific S-NSSAI corresponding to the XR service that can be received by the UE through the network, or may include an AF / AS ID, that is, an ID of the AF / AS that provides the XR service to the UE, or an application ID, and / or an AF-specific GPSI or a GPSI that is an ID used by the AF / AS to define the UE. In addition, when a group of UEs (or XR devices) are predetermined to receive the XR service together, an AF-specific SF group ID or user ID or pairing information for defining the group may be included in the subscription information. Therefore, when the subscription information includes an AF-specific SF group ID (e.g., a multimodal service ID), a process for configuring an AF-specific SF group between the AF / AS and the UE (e.g., UE1 or UE2) and a process for providing the AF-specific SF group ID (which is information indicating the configured group or user ID or pairing information) to the 5G system may be omitted, and the information may be updated by the network.

[0137] UE1 and UE2 for receiving XR services can access AF / AS that provides XR services, and in this case, UE1 and UE2 can access AF / AS through 5G system or Wi-Fi. UE1 and UE2 can use various communication schemes to access AF / AS. UE1 and UE2 connected to AF / AS can transmit information related to XR devices connected to UE. Information related to bound XR devices may include information related to delay time for XR data transmission from UE to bound devices. To this end, each UE can measure the actual delay time between the UE and the bound device connected to the UE and transmit it to AF / AS, or transmit the information to AF / AS in the form of a binding profile (connection type or codec information) of the binding device connected to each UE, and on this basis use the average delay value of the binding profile defined by the XR service operator.

[0138] In addition, for each UE, the transmission delay time information between the UE and the binding device can be fixedly set and used, or the transmission delay time between the UE and the binding device can be measured regularly or irregularly according to the user's environment, and the updated information can be transmitted to the AF / AS. The UE can transmit at least one of the UE's GPSI, application ID, IP address, service flow group ID, and delay budget difference adjustment to the DN (AS). The SMF can transmit the updated QER to the UPF.

[0139] refer to Fig. 6A and Figure 6BIn S601, the AF 800-5 may calculate the transmission delay time according to the service flow transmitted to the bound device (delay budget adjustment) for each UE (UE1 100-5 and UE2 100-6) based on the bound transmission delay time difference (delay budget difference adjustment) information transmitted to one or more UEs (UE1 100-5 and UE2 100-6) received in S600 and the information for identifying the service flow transmitted to the bound device (GPSI, application ID, AF specific group ID (e.g., multimodal service ID)) (not shown). It may be expressed as the service flow transmission delay time information about the one or more bound devices of each UE according to the number of the one or more UEs (UE1 100-5 and UE2 100-6) calculated as above and the number of bound devices connected to each UE. Thereafter, in S602, AF 800-5 may transmit an AF session service operation generation (Nnef_AFsessionWithQoS_Create) or update (Nnef_AFsessionWithQoS_Update) request message to NEF700-5, the request message including QoS requirement information related to the streaming delay time of the bound device connection service (e.g., XR service) of each UE and service flow ID information about one or more UEs and one or more bound devices of each UE.

[0140] Through S603 and S604, NEF 700-5 transmits a policy authorization service generation (Npcf_PolicyAuthorization_Create) or update (Npcf_PolicyAuthorization_Update) request message to PCF 600-5, the update request message includes each bound device connection service (e.g., XR service) flow QoS requirement information, the QoS requirement information includes, for example, transmission delay information of each bound device service flow connected to UE1 100-5 and UE2 100-6 received from AF 800-5. In S605 and S606, the XR service-related update request-related response information of AF 800-5 received in S604 can be transmitted to AF 800-5 through NEF 700-5.

[0141] In S607a, the PCF 600-5 may update the corresponding service flow related policy and charging control rules (PCC rules) based on the bound device connection service (e.g., XR service) related QoS requirement information (including the transmission delay time (delay budget adjustment) according to the service flow) to be transmitted to the bound device for each UE (UE1 100-5 and UE2 100-6) received from the AF 800-5. Basically, in an environment regardless of the bound device connected to the UE, a default policy and charging control rule according to the service flow may be generated based on the XR service related QoS information according to the XR service flow transmitted to the UE.

[0142] According to an embodiment, when the policy is determined without performing the PCF 600-5 update operation of S607a, SMF1 500-5 or SMF2 500-6 may receive XR service-related default policy and charging control rules and XR service-related information, the information including binding transmission delay time information and information for identifying the service flow transmitted to the binding device for each UE (UE1 100-5 and UE2 100-6) (GPSI, application ID, AF specific group ID (e.g., multimodal service ID)), update the service flow-related policy information, and perform QoS scheduling (S607b). When operation S607b is performed by SMF1 500-5 and / or SMF2 500-6, operation S607b may be performed after performing operations S608 and S609 between PCF 600-5 and SMF1 500-5 or SMF2 500-6. Operations S607a and S607b may be performed optionally.

[0143] Thereafter, in S608 (S608a and S608b), the policy and charging control rules according to the service flow associated with the XR service updated in S607 are transmitted to the SMF 500-5 or 500-6 through the SM policy association modification process through a session management policy control update notification service operation (Npcf_SMPolicycontrol_UpdateNotify) request message. In an embodiment, when a service user uses an XR service through one or more UEs, if each UE selects a different SMF when establishing a PDU session, in steps 608a and 608b, UE1 100-5 and UE2 100-6 may transmit a session management policy control update notification service operation (Npcf_SMPolicycontrol_UpdateNotify) request message including the policy and charging control rules according to the service flow of the XR service considering the bound device to SMF1 500-5 and SMF2 500-6, respectively, through the SM policy association modification process. In S609 ( S609 a and S609 b ), the SMF1 500 - 5 may transmit a session management policy control update notification (Npcf_SMPolicycontrol_UpdateNotify) service operation response message to the PCF 600 - 5 .

[0144] In S610 (S610a to S610d), SMF1 and SMF2 may receive the policy and charging control rules updated based on each UE XR service-related QoS requirement information, allocate a corresponding QFI to each service flow, and transmit service flow detection information and XR service-related information and / or forwarding information of the XR service to UPFs 400-5 and 400-6 and RAN (or NG-RAN) 200-5 for each QFI. The forwarding information is information used in the process of transmitting (forwarding) XR service flow data from each UPF 400-5 and 400-6 to RAN 200-5.

[0145] In an embodiment, in S607 (S607a or S607b), if the QoS scheduling information considering the update request information of each UE service flow received from the AF 800-5 can be mapped to a standardized or non-standardized 5QI, and updated policy and charging control rule information is received, each SMF 500-5, 500-6 can allocate a corresponding QFI based on the updated PCC rule, and for each QFI, service flow detection information for the XR service and XR service-related information and / or forwarding information can be transmitted to the UPF 400-5, 400-6 and the RAN 200-5.

[0146] The SMF1 500-5 that receives the service flow detection information and the XR service related information in S610a may detect the ID of the QoS flow to be applied to the PDU session of the UE1 100-5 based on the updated policy and charging control rule received in S608a, and transmit the information to be applied to the QoS flow to the UPF1 400-5 through the N4 session establishment or modification process. Therefore, the information transmitted to the UPF 400-5 may include, for example, the QoS flow ID (QFI) of the XR service flow and information for detecting the QoS flow ID, such as the AF ID or application ID or AF / AS address information, i.e., IP address and port information or application level packet information, i.e., ADU ID or sequence number (SN). In addition, the information transmitted to the UPF 400-5 in S610a may include an indicator indicating whether to apply a multimodal service to the service flow, a difference in delay time allowed when applying the multimodal service, and information such as a bound transmission delay time (delay budget adjustment) in an environment where a bound device connection is used.

[0147] Thereafter, in S610b, the SMF1 500-5 may include, in an N2 SM message container, at least one of a bound device transmission delay time value (delay budget adjustment) when a multimodal service using a bound device is applied, a QFI of a service flow of the UE1 100-5, an AF ID, an application ID, and an AF-specific SF group ID (e.g., a multimodal service ID) as SM policy information, and transmit it to the RAN 200-5.

[0148] In an embodiment, in S610b, when a multimodal service using a bound device is applied, the SMF 500-5 may transmit at least one of the QFI, AF ID, application ID, AF-specific SF group ID (e.g., multimodal service ID), and TSCAI including a bound device transmission delay time value (delay budget adjustment) of the service flow of UE1100-5 to the AMF 300-5 via a N1N2 message transfer (Namf_Communication _N1N2Message Transfer) service operation message.

[0149] The AMF 300-5 may transmit the separate container (e.g., TSCAI) and QFI (including information such as the bound device transmission delay time value (delay budget adjustment)) received from the SMF1 500-5 to the RAN 200-5 using the N2 SM message. The SMF1 500-5 may receive the device transmission delay time value (delay budget adjustment), the operation of generating or modifying the information in the container, and the related policy information using the separate container from the PCF 600-5 through S608a.

[0150] The SMF2 500-6 that receives the service flow detection information and the XR service related information in S610c may detect the ID of the QoS flow to be applied to the PDU session of the UE2 100-6 based on the updated policy and charging control rule received in S608b, and transmit the information to be applied to the QoS flow to the UPF2 400-6 through the N4 session establishment or modification process. Therefore, the information transmitted to the UPF 400-6 may include, for example, the QoS flow ID (QFI) of the XR service flow and information for detecting the QoS flow ID, such as the AF ID or application ID or AF / AS address information, i.e., IP address and port information or application level packet information, i.e., ADU ID or sequence number (SN). In addition, the information transmitted to the UPF 400-6 in S610c may include an indicator indicating whether to apply a multimodal service to the service flow, a difference in the delay time allowed when applying the multimodal service, and information such as a bound transmission delay time (delay budget adjustment) in an environment where a bound device connection is used.

[0151] Thereafter, in S610d, SMF2 500-6 may include, in an N2 SM message container, a binding device transmission delay time value (delay budget adjustment) when a multimodal service using a binding device is applied, at least one of the QFI of the service flow of UE2 100-6, the AF ID, the application ID, and the AF-specific SF group ID as SM policy information, and transmit it to RAN200-5.

[0152] In an embodiment, in S610d, when a multimodal service using a bound device is applied, SMF2 500-6 may transmit at least one of the QFI, AF ID, application ID, AF-specific SF group ID (e.g., multimodal service ID) and a separate container (e.g., TSCAI) including a bound device transmission delay time value (delay budget adjustment) of the service flow of UE2100-6 to AMF 300-5 through a N1N2 message transfer (Namf_Communication _N1N2Message Transfer) service operation message.

[0153] The AMF 300-5 may transmit the separate container (e.g., TSCAI) and QFI (including information such as the bound device transmission delay time value (delay budget adjustment)) received from the SMF2 500-6 to the RAN 200-5 using the N2 SM message. The SMF2 500-6 may receive the bound device transmission delay time value (delay budget adjustment), the operation of generating or modifying the information in the container, and the related policy information using the separate container from the PCF 600-5 through S608b.

[0154] refer to Fig. 7A and Figure 7B In S701, the AF 800-7 may transmit an AF session service operation generation (Nnef_AFsessionWithQoS_Create) or update (Nnef_AFsessionWithQoS_Update) request message to the NEF 700-7, the update request message including binding transmission delay time difference (delay budget difference adjustment) information and information for identifying the service flow transmitted to the binding device transmitted to the UE1 100-7 and the UE2 100-8 transmitted in S700 (GPSI, application ID, AF specific group ID (e.g., multimodal service ID)).

[0155] Thereafter, in S702 and S703, NEF 700-7 may transmit a policy authorization service generation (Npcf_PolicyAuthorization_Create) or update (Npcf_PolicyAuthorization_Update) request message to PCF 600-7, the update request message including bound device connection service (e.g., XR service) flow QoS requirement information, such as transmission delay time difference information (delay budget difference adjustment) according to one or more bound service flows of the UE and information for identifying the service flows of one or more bound devices of each UE and UE1 100-7 and UE2 100-8.

[0156] In S704, PCF 600-7 may calculate one or more bound device service flow transmission delay times for each UE (delay budget adjustment) based on information (GPSI, application ID, AF-specific group ID (e.g., multimodal service ID)) used to identify the service flow transmitted to the bound device and the difference in bound transmission delay time (delay budget difference adjustment) transmitted to UE1 100-7 and UE2 100-8 or based on the bound transmission delay time of the service flow.

[0157] In S705 and S706, the PCF 600-7 may transmit the XR service related update request related response information of the AF 800-7 received in S704 to the AF 800-7 through the NEF 700-7.

[0158] In S707 (S707a or S707b), PCF 600-7 can update the corresponding service flow-related policies and charging control rules (PCC rules) based on the bound device connection service (e.g., XR service) related QoS requirement information (including the transmission delay time (delay budget adjustment) of the service flow to be transmitted to the bound device) for each UE (UE1100-7 and UE2 100-8) obtained through S704.

[0159] According to an embodiment, when the policy is determined without performing the PCF 600-7 update operation of S707a, SMF1500-7 or SMF2 500-8 may receive XR service-related default policy and charging control rules and XR service-related information, including binding transmission delay time information and information for identifying the service flow transmitted to the binding device for each UE (UE1 100-5 and UE2 100-6) (GPSI, application ID, AF specific group ID (e.g., multimodal service ID)), update the service flow-related policy information, and perform QoS scheduling for each UE (UE1 100-7 and UE2 100-8) (S707b). In this case, PCF 700-7 may transmit information about one or more binding device service flow transmission delay times (delay budget adjustment) for each UE to SMF 500-7 and 500-8. When operation S707b is performed by SMF1 500-7 and / or SMF2 500-8, operation S707b may be performed after operations S708 and S709 between PCF 600-7 and SMF1 500-7 or SMF2 500-8 are performed. Operations S707a and S707b may be optionally performed.

[0160] Thereafter, in S708 (S708a and S708b), the policy and charging control rules according to the service flow according to the UE updated in S707 (S707a) may be transmitted to the SMF 500-7 or 500-8 through a session management policy control update notification service operation (Npcf_SMPolicycontrol_UpdateNotify) request message through the SM policy association modification procedure. The request message may include information related to the transmission delay time (delay budget adjustment) of the service flow to be transmitted to the bound device for each UE (UE1 100-7 and UE2 100-8).

[0161] In an embodiment, through the SM policy association modification process in S708a and S708b, when an XR service user uses the XR service through different UEs (eg, UE1 100-7 and UE2 100-8), as shown in FIG. 7 ( Fig. 7A and Figure 7B), and when each UE manages the session through different SMFs (SMF1 500-7 and SMF2 500-8), it can be transmitted to each SMF through a session management policy control update notification service operation (Npcf_SMPolicycontrol_UpdateNotify) request message, which includes the policy and charging control rules of the service flow updated for each UE. PCF 600-7 can transmit information used for detecting the service flow by UPF 400-7, 400-8 and SMF 500-7, 500-8, that is, the above-mentioned service flow detection information, to SMF 500-7 and 500-8. In S709 (S709a and S709b), SMF1 500-7 can transmit a session management policy control update notification (Npcf_SMPolicycontrol_UpdateNotify) service operation response message to PCF 600-7.

[0162] In S710 (S710a to S710d), SMF1 500-7 and SMF2 500-8 may receive a policy and charging control rule updated based on the XR service-related QoS requirement information of the UE, allocate a corresponding QFI to each service flow, and transmit service flow detection information and XR service-related information and / or forwarding information of the XR service to UPFs 400-7 and 400-8 and RAN (or NG-RAN) 200-7 for each QFI. The forwarding information is information used in the process of transmitting (forwarding) XR service flow data from each UPF 400-7 and 400-8 to RAN 200-7.

[0163] The SMF1 500-7 that receives the service flow detection information and the XR service related information in S710a detects the ID of the QoS flow to be applied to the PDU session of the UE1 100-7 based on the updated policy and charging control rule received in S708a, and transmits the information to be applied to the QoS flow to the UPF1 400-7 through the N4 session establishment or modification process. Therefore, the information transmitted to the UPF 400-7 may include, for example, the QoS flow ID (QFI) of the XR service flow and information for detecting the QoS flow ID, such as the AF ID or application ID or AF / AS address information, i.e., IP address and port information or application level packet information, i.e., ADU ID or sequence number (SN). In addition, the information transmitted to the UPF 400-7 in S710a may include an indicator indicating whether to apply a multimodal service to the service flow, a difference in delay time allowed when applying the multimodal service, and information such as a bound transmission delay time (delay budget adjustment) in an environment where a bonding device connection is used.

[0164] Thereafter, in S710b, the SMF1 500-7 may include information such as a binding device transmission delay time value (delay budget adjustment), a QFI of a service flow of the UE1 100-7, an AF ID, an application ID, and an AF-specific SF group ID (e.g., a multimodal service ID) in an N2 SM message container as SM policy information when a multimodal service using a binding device is applied, and transmit it to the RAN 200-7.

[0165] In an embodiment, in S710b, when a multimodal service using a bound device is applied, SMF1 500-7 may transmit at least one of the QFI, AF ID, application ID, AF-specific SF group ID, and a separate container (e.g., TSCAI) including a bound device transmission delay time value (delay budget adjustment) of the service flow of UE1100-7 to AMF 300-7 through a N1N2 message transfer (Namf_Communication _N1N2Message Transfer) service operation message.

[0166] The AMF 300-7 may transmit a separate container (eg, TSCAI) and a QFI (including information such as a binding device transmission delay time value (delay budget adjustment)) received from the SMF1 500-7 to the RAN 200-7 using an N2 SM message.

[0167] The SMF2 500-8 that receives the service flow detection information and the XR service related information in S710c detects the ID of the QoS flow to be applied to the PDU session of the UE2 100-8 based on the updated policy and charging control rule received in S708b, and transmits the information to be applied to the QoS flow to the UPF2 400-8 through the N4 session establishment or modification process. Therefore, the information transmitted to the UPF may include, for example, the QoS flow ID (QFI) of the XR service flow and information for detecting the QoS flow ID, such as the AF ID or application ID or AF / AS address information, i.e., IP address and port information or application level packet information, i.e., ADU ID or sequence number (SN). In addition, the information transmitted to the UPF 400-8 in S710c may include an indicator indicating whether to apply a multimodal service to the service flow, a difference in the delay time allowed when applying the multimodal service, and information such as a bound transmission delay time (delay budget adjustment) in an environment where a bonding device connection is used.

[0168] Thereafter, in S710d, SMF2 500-8 may include information such as a bound device transmission delay time value (delay budget adjustment) when a multimodal service using a bound device is applied, a QFI of a service flow of UE2 100-8, an AF ID, an application ID, and an AF-specific SF group ID in an N2 SM message container as SM policy information, and transmit it to the RAN 200-7.

[0169] In an embodiment, in S710d, when a multimodal service using a bound device is applied, SMF2 500-8 may transmit information such as QFI, AF ID, application ID, AF-specific SF group ID, and a separate container (e.g., TSCAI) including a bound device transmission delay time value (delay budget adjustment) of a service flow of UE2 100-8 to AMF 300-7 through a N1N2 message transfer (Namf_Communication _N1N2Message Transfer) service operation message.

[0170] The AMF 300-7 may transmit a separate container (eg, TSCAI) and a QFI (including information such as a binding device transmission delay time value (delay budget adjustment)) received from the SMF2 500-8 to the RAN 200-7 using an N2 SM message.

[0171] Fig. 8A and Figure 8B An exemplary method for transmitting XR data of an XR service (a service using binding) in a wireless communication system according to an embodiment is shown. Fig. 8A and Figure 8B ), the UE used by the same user may be a UE including an XR device or connected to a bound XR device. Fig. 8A and Figure 8B ) can be applied in the same way even when multiple bonded XR devices are connected to one UE, such as Figure 1A as shown in the example.

[0172] Figure 8 Fig. 8A and Figure 8B ) is a method for transmitting the QoS requirement of the binding device transmission considered for the XR service to the PCF 600-9 through the SMF 500-9 when the UE 100-9 performs the process of establishing the PDU session for the XR service. In addition, FIG. 8 ( Fig. 8A and Figure 8B) is a method for seamlessly providing multimodal services, which transmits XR service-related information of the multimodal service for the QoS requirement of the bound device connection service (e.g., XR service) of the UE to UPF 400-9 and RAN 200-9 through SMF500-9.

[0173] Although in Figure 8 ( Fig. 8A and Figure 8B ) is not shown, but in Fig. 8A In S800 before S801, basic settings for using XR services between UE 100-9 and the 5G system may be made. For example, assume that an XR-specific S-NSSAI for XR services is configured in the UE and / or the network. In this case, the XR-specific S-NSSAI may include an SST for XR services as described above, or an SST for XR services provided by a communication carrier. In addition, the XR-specific S-NSSAI may include an SD for identifying a specific XR service or a specific XR service application.

[0174] In addition, the subscription information about the UE configured in S800 may include an XR-specific S-NSSAI corresponding to the XR service that the UE can receive through the network, or may include an AF / AS ID (i.e., the ID of the AF / AS providing the XR service received by the UE), and an AF-specific GPSI or GPSI (i.e., an ID for defining the UE by the AF / AS) and an AF-specific group ID (e.g., a multimodal service ID) or a user ID for defining a group of UEs that simultaneously provide XR services to users may be included in the subscription information. In S800, the UE for receiving the XR service may access the AF / AS providing the XR service, and in this case, the UE may access the AF / AS through the 5G system or Wi-Fi. The UE may access the AF / AS using various communication schemes.

[0175] In order to identify UEs using the same XR service, the AF / AS may allocate / configure the same AF-specific SF group ID (e.g., multimodal service ID) for UE1 and UE2 through signaling with the UE. In this case, the AF-specific SF group ID may be allocated to a group of UEs receiving the same XR service and used to identify the group of UEs, or may also identify a group of service flows for providing XR data related to the same XR service to the group of UEs.

[0176] In addition, the pairing information about the UE receiving the same XR service or the user's email account or the user ID managed by the application may be used instead of the AF specific SF group ID. In the present disclosure, for the convenience of description, an embodiment using the AF specific SF group ID is described. However, the present disclosure is not limited to using the AF specific SF group ID to identify the group of UEs receiving the same XR service and / or the group of related service flows (SFs).

[0177] In S800, the AF / AS may provide the above-mentioned XR service-related information to the 5G system for application to the service flow identified by the AF-specific SF group ID. The XR service-related information provided by the AF / AS may be stored in the UDM, or in the UDR via the UDM. The XR service-related information stored in the UDR may be transmitted to the PCF for use in performing QoS and / or scheduling of multimodal services for the corresponding service flow in the 5G system. In addition, when multimodal services are supported for one or more binding devices connected to the UE according to the present disclosure, value information about the binding transmission delay time difference that occurs when transmitting / processing data of the service flow may be measured by the UE itself (delay budget difference adjustment), or the value information may be requested / received from the AF / AS using profile information according to the binding scheme.

[0178] refer to Fig. 8A and Figure 8B , in S801, the UE 100-9 to receive the XR service may include an XR-specific S-NSSAI and a data network name (DNN) together with a PDU session establishment request message even outside an N1 session management (SM) non-access stratum (NAS) container according to the 3GPP standard during the process of performing a process of establishing a PDU session for the XR service. The N1 SM NAS container may include the PDU session establishment request message.

[0179] In addition, the PDU session establishment request message may include: an application ID or AF / AS ID, which is information about an application that provides the XR service; and an AF-specific SF group ID, which is group information about UEs and bound devices to which they are connected when using the XR service obtained by UE 100-9 in S800; and transmission delay time difference information to the bound device (delay budget difference adjustment).

[0180] The AF-specific SF group ID may be included even outside the N1 SM NAS container. Therefore, the reason for additionally including the AF-specific SF group ID in a field outside the N1 SM NAS container is that the AMF 300-9 that receives the NAS message including the PDU session establishment request message may not recognize the information in the N1 SM NAS container. The UE 100-9 may include the XR-specific S-NSSAI, DNN, application ID and / or AF / AS ID, and the AF-specific SF group ID in a field outside the N1 SM container transmitted to the AMF 300-9 via the PDU session establishment request message, thereby notifying the AMF 300-9 of the XR-specific S-NSSAI and DNN, application ID or AF ID, and AF-specific SF group ID for the PDU session requested to be established.

[0181] Therefore, in S802, the AMF 300-9 that has received the NAS message (i.e., the PDU session establishment request message) may send a request to the network slice selection function (NSSF) and / or the NRF based on the XR-specific S-NSSAI and DNN received from the UE 100-9 and the application ID or the AF-specific SF group ID or the previously allocated network slice instance identifier (NSI ID), and select the SMF 500-9 suitable for the XR service of the UE. For example, the AMF 300-9 may transmit information such as the XR-specific S-NSSAI and the tracking area identifier (TAI) information of the UE to the NSSF, and receive information about the NRF existing in the network slice instance suitable for the XR service of the UE from the NSSF, or receive the NSI ID, and transmit the XR-specific S-NSSAI and DNN and the application ID or the AF-specific SF group ID and the NSI ID to the NRF based on the information received from the NSSF, and in response, receive the SMF instance suitable for the XR service from the NRF and select it.

[0182] In addition, in S802, when there is no dedicated SMF instance for the application ID or AF-specific SF group ID, the AMF300-9 can select the SMF based on the XR-specific S-NSSAI and DNN.

[0183] In S803, the AMF 300-9 may transmit a PDU session establishment request message (e.g., Nsmf_PDUSession_CreateSMContextRequest) including the transmission delay time difference information (delay budget difference adjustment) received from the UE to the selected SMF 500-9, and in S808, the SMF 500-9 that receives the PDU session establishment request message may transmit an Npcf_SMPolicyControl_Create request message to the PCF 600-9 through the SM policy association establishment procedure, the request message including not only the SUPI, DNN, S-NSSAI, and PDU session ID, but also the application ID or AF ID, AF-specific group ID, AF-specific GPSI, and binding device transmission delay information (delay budget difference adjustment). Therefore, the SMF 500-9 may send a request for XR service related information to be applied to the AF-specific SF group to the PCF 600-9, the request being information about the service flow in the XR service constituted by the UE and one or more binding devices and the UE to which the multimodal service is to be applied.

[0184] In S809 , the PCF 600 - 9 may calculate a transmission delay time value (delay budget adjustment) of the bound device service flow based on the XR service related information including the UE ID information (AF specific SF group) and the bound device transmission delay difference (delay budget difference adjustment).

[0185] In S810, PCF 600-9 can identify whether it has XR service-related information to be applied to the UE, and if there is XR service-related information, update the XR service-related policies and charging control rules based on the XR service-related request information including the transmission delay time value (delay budget adjustment) of the bound device service flow received in S809 in the XR service-related information.

[0186] In an embodiment, if the XR service related information does not exist, even though FIG. 8 ( Fig. 8A and Figure 8B ), which is not shown in S809, can request and receive from the UDR XR service-related information to be applied to the AF-specific SF group for the AF ID or application ID, and update the XR service-related policies and charging control rules based on the XR service-related request information including the transmission delay time value (delay budget adjustment) of the bound device service flow received in S809 and the received XR service-related information.

[0187] In addition, the XR service-related information may also include at least one of the following information: information indicating whether a dedicated QoS flow needs to be applied to the service flow, information indicating whether dedicated queuing is required, information indicating whether a multimodal service is applied to the service flow, a difference in delay time allowed when applying a multimodal service, and a transmission delay time value or difference when considering a bound device applying a multimodal service. In addition, PCF 600-9 may transmit information for detecting a service flow (i.e., the above-mentioned service flow detection information) to SMF 500-9 via UPF 400-9 and SMF 500-9. The service flow detection information may include, for example, an AF ID or an application ID or application server address information (i.e., an IP address and port information) or application-level packet information (i.e., a sequence number or ID of an application data unit (ADU)).

[0188] In S811, if UPF is not assigned for DNN, S-NSSAI, application ID, and AF specific SF group ID, the SMF 500-9 that receives the service flow detection information and XR service related information through the SM policy modification procedure may select a new UPF (S813), and Figure 8B In S814a, the ID of the QoS flow to be applied to the PDU session requested to be established for the UE is detected, and the information to be applied to the corresponding QoS flow (including the transmission delay time value (delay budget adjustment) of the bound device service flow) is transmitted to the UPF 400-9 through the N4 session establishment or modification process. Therefore, the information transmitted to the UPF 400-9 may include, for example, the QoS flow ID (QFI) of the XR service flow and information for detecting the QoS flow ID, such as AF ID or application ID or AF / AS address information, i.e., IP address and port information or application-level packet information, i.e., ADU ID or sequence number (SN). In addition, the information transmitted to the UPF 400-9 in S814a may include an indicator indicating whether a multimodal service is applied to the service flow and a delay time difference allowed when applying the multimodal service.

[0189] Thereafter, in S814b, the SMF 500-9 may include at least one of the following information as SM policy information in an N2 SM message container and transmit it to the RAN (or NG-RAN) 200-9.

[0190] -QFI of XR service flow, -AF ID or App ID -AF specific SF group ID - A list of UE IDs (e.g., 5G Globally Unique Temporary Identifier or 5G-S Temporary Mobile Subscriber Identity (5G-S-TMSI)) assigned to UEs belonging to an AF-specific SF group, - An indicator indicating whether a dedicated queue is required with information about the QFI of the UE serving the XR service flow -Indicator indicating whether the multimodal service is applied to the service flow - the difference in latency allowed when applying multimodal services, - Transmission delay time value of the bound device service flow (delay budget adjustment) Therefore, the above XR service related information can be provided to RAN 200-9 through the path of AF / AS => NEF => PCF => SMF => NG-RAN.

[0191] In an embodiment, in S814b, the SMF 500-9 may transmit at least one of the following information to the AMF 300-9 through a N1N2 message transfer (Namf_Communication_N1N2Message Transfer) service operation message.

[0192] -QFI of XR service flow, -AF ID, - Application ID, -AF specific SF group ID, - A list of UE IDs (e.g., 5G Globally Unique Temporary Identifier or 5G-S Temporary Mobile Subscriber Identity (5G-S-TMSI)) assigned to UEs belonging to an AF-specific SF group, - An indicator indicating whether a dedicated queue is required with information about the QFI of the UE serving the XR service flow - an indicator indicating whether a multimodal service is applied to a service flow and a difference in delay time allowed when the multimodal service is applied, - Transmission delay time value of the bound device service flow (delay budget adjustment) The AMF 300-9 may transmit a separate container (e.g., TSCAI) and a QFI (including information such as a binding device transmission delay time value (delay budget adjustment)) received from the SMF 500-9 to the RAN 200-9 using an N2 SM message. Therefore, the above XR service related information may be provided to the RAN 200-9 through a path of AF / AS => NEF => PCF => SMF => AMF => NG-RAN.

[0193] Thereafter, in S814a, according to the N4 session message received by the UPF 400-9, the UPF 400-9 allocates a dedicated queue for the dedicated QFI and performs scheduling, so that the difference in delay time required for forwarding or scheduling data packets of each XR dedicated QFI of the bound device and the UE 100-9 is less than the difference in delay time allowed in consideration of the transmission delay time of the bound device. In addition, according to the N2 SM message received by the RAN 200-9 in S814b, the NG-RAN allocates a dedicated queue for the dedicated QFI and performs scheduling, so that the difference in delay time required for forwarding or scheduling data packets of each XR dedicated QFI of the UE and the bound device is less than the difference in delay time allowed in consideration of the transmission delay time of the bound device. Therefore, the UE receiving the XR data can receive the XR service data within the delay time difference allowed in consideration of the delay time of the bound device connected to the UE, thereby smoothly supporting multimodal services to the user.

[0194] Fig. 9 FIG. 9 shows a structure of a UE 900 according to an embodiment. Fig. 9 According to an embodiment, the UE 900 may include at least one controller (or processor) 910 and a transceiver 920 including a receiver and a transmitter. The UE 900 may include a memory (not shown). The transceiver 920 and the memory may be connected to the at least one controller 910 to operate under the control of the at least one controller 910.

[0195] At least one controller 910 may control a series of processes so that the operations described in conjunction with FIG. 1 to FIG. 1 of the present disclosure may be performed. Figure 8B The operation of the UE is described. The transceiver 920 may transmit and / or receive signals to and / or from a base station or another network device (eg, 1000). The signals may include control messages and data information.

[0196] Fig.10 FIG. 1 shows a structure of a network entity 1000 according to an embodiment. The network entity 1000 may include AF, AS, DN, NEF, PCF, SMF, UPF, AMF, RAN, UDM, or UDR of FIG. 1 to FIG. 8 . Fig.10 The network entity 1000 of the present disclosure may include at least one controller (or processor) 1010 and a transceiver 1020 including a receiver and a transmitter. The network entity 1000 may include a memory (not shown). The transceiver 1020 and the memory may be connected to the at least one controller 1010 to operate under the control of the at least one controller 1010.

[0197] At least one controller 1010 may control a series of processes so that the operations described in conjunction with FIG. 1 to FIG. 1 of the present disclosure may be performed. Figure 8BThe transceiver 1020 may transmit / receive signals to / from the UE 900 or another network entity. The signals may include control messages and data information.

[0198] It should be noted that the above configuration views, exemplary views of the control / data signal transmission method, exemplary views of the operation process and configuration views are not intended to limit the scope of the present disclosure. In other words, all components, network entities or operation steps described in conjunction with the embodiments should not be interpreted as necessary components for practicing the present disclosure, but only some components can be used to implement the present disclosure without departing from the main purpose of the present disclosure. In addition, these embodiments can be practiced in combination. For example, some methods proposed herein can be combined to operate network entities and UEs.

[0199] In the above specific embodiments, the components included in the present disclosure are expressed in singular or plural form depending on the specific embodiment proposed. However, for ease of description, the singular or plural form is selected to be suitable for the proposed context, and the present disclosure is not limited to singular or plural components. As used herein, the singular forms "a", "an", and "the" are intended to include plural forms unless the context clearly indicates.

[0200] The embodiments herein are provided only for a better understanding of the present disclosure, and the present disclosure should not be limited thereto or thereby. It will be appreciated by those skilled in the art that various changes may be made to the embodiments in form and detail without departing from the scope of the present disclosure as defined by the following claims.

[0201] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A policy control function (PCF) entity in a wireless communication system, the PCF entity comprising: Transceiver; as well as at least one processor, wherein the at least one processor is configured to: updating the service-related policy based on a service transmission delay time according to the service flow (delay budget adjustment), wherein said service transmission delay time according to the service flow is transmitted to the bound device, Based on the service-related policy, the quality of service QoS is scheduled, and A first message is transmitted to a session management function SMF entity, wherein the first message includes the service transmission delay time according to the service flow, the updated service-related policy, and the QoS requirement based on the scheduled QoS.

2. The PCF entity of claim 1, wherein the service transmission delay time according to the service flow is determined based on a group identifier ID according to the service flow of a group including at least one binding device, and The service transmission delay time according to the service flow is included in time-sensitive communication assistance information TSCAI and transmitted to the radio access network RAN.

3. The PCF entity of claim 2, wherein the at least one processor is further configured to: receive a second message, the second message comprising information for distinguishing at least one service flow transmitted from the network exposure function (NEF) entity to the binding device, a binding transmission delay time difference, and connection information about the binding device, and The information used to distinguish the service flows includes the group ID according to the service flows.

4. A PCF entity as described in claim 3, wherein the service transmission delay time according to the service flow is determined based on at least one of the following: information for distinguishing the at least one service flow transmitted to the binding device, the binding transmission delay time difference, and the connection information about the binding device.

5. A session management function SMF entity in a wireless communication system, the AMF entity comprising: Transceiver; as well as at least one processor, wherein the at least one processor is configured to: receiving a first message from a policy control function PCF entity, wherein the first message includes a service transmission delay time according to a service flow, an updated service-related policy, and a quality of service QoS requirement, Based on the QoS requirements, configuring the QoS of the service flow to be transmitted to the bound device, and Based on the updated service-related policy, a second message including the service transmission delay time according to the service flow is transmitted to the radio access network RAN ​​through the access and mobility function AMF entity.

6. The SMF entity of claim 5, wherein the service transmission delay time according to the service flow is determined based on a group identifier ID according to the service flow of a group including at least one binding device.

7. The SMF entity of claim 5, wherein the at least one processor is configured to include the service transmission delay time according to the service flow in the time-sensitive communication assistance information TSCAI of the second message, and transmit the service transmission delay time to the radio access network RAN.

8. An SMF entity as described in claim 5, wherein the service transmission delay time according to the service flow is determined based on at least one of the following: information for distinguishing at least one service flow transmitted to the binding device, a binding transmission delay time difference, and connection information about the binding device.

9. A method performed by a policy control function (PCF) entity in a wireless communication system, the method comprising: updating a service-related policy based on a service transmission delay time according to a service flow (delay budget adjustment), wherein said service transmission delay time according to a service flow is transmitted to a bound device; Based on the service-related policy, scheduling quality of service QoS; and A first message is transmitted to a session management function SMF entity, wherein the first message includes the service transmission delay time according to the service flow, the updated service-related policy, and the QoS requirement based on the scheduled QoS.

10. The method of claim 9, wherein the service transmission delay time according to the service flow is determined based on a group identifier ID according to the service flow of a group including at least one bound device, and The service transmission delay time according to the service flow is included in time-sensitive communication assistance information TSCAI and transmitted to the radio access network RAN.

11. The method of claim 10, further comprising receiving a second message, the second message comprising information for distinguishing at least one service flow transmitted from a network exposure function (NEF) entity to a binding device, a binding transmission delay time difference, and connection information about the binding device, The information used to distinguish the service flows includes the group ID according to the service flows.

12. A method as claimed in claim 11, wherein the service transmission delay time according to the service flow is determined based on at least one of the following: information for distinguishing the at least one service flow transmitted to the binding device, the binding transmission delay time difference, and the connection information about the binding device.

13. A method performed by a session management function (SMF) entity in a wireless communication system, the method comprising: receiving a first message from a policy control function PCF, the first message including a service transmission delay time according to a service flow, an updated service-related policy, and a quality of service QoS requirement; configuring QoS of a service flow to be transmitted to the bound device based on the QoS requirement; and Based on the updated service-related policy, a second message including the service transmission delay time according to the service flow is transmitted to the radio access network RAN ​​through the access and mobility function AMF entity.

14. The method of claim 13, further comprising: including the service transmission delay time according to the service flow in time-sensitive communication assistance information TSCAI of the second message and transmitting the service transmission delay time to the radio access network RAN, The service transmission delay time according to the service flow is determined based on a group identifier ID according to the service flow of a group including at least one bound device.

15. The method of claim 13, wherein the service transmission delay time according to the service flow is determined based on at least one of: information for distinguishing at least one service flow transmitted to the binding device, a binding transmission delay time difference, and connection information about the binding device.

Images