KR20240110361A - Apparatus and method for providing power saving assistance information of user equipment in communication system - Google Patents

Abstract

This disclosure relates to 5G or 6G communication systems to support higher data rates. A method of operating a policy control function (PCF) in a wireless communication system according to an embodiment of the present disclosure includes a power saving service support indicator, jitter range information, and period information transmitted from an application function (AF). Based on the operation of receiving through (network exposure function) and the jitter range information and the period information, a PCC (PCC) including a policy for N6 jitter measurement and QoS (quality of service) monitoring parameter information for 5GC jitter measurement policy and charging control) rules, and the updated PCC rules are sent to the session management function (SMF) so that jitter-related information and rules for jitter range measurement for the power saving service are transmitted to the user plane function (UPF). ) includes the operation of transmitting.

Description

Method and device for providing terminal power saving support information in a communication system {APPARATUS AND METHOD FOR PROVIDING POWER SAVING ASSISTANCE INFORMATION OF USER EQUIPMENT IN COMMUNICATION SYSTEM}

This disclosure relates to a method and device for providing information to support power saving of a terminal in a communication system.

5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and includes sub-6 GHz ('Sub 6GHz') bands such as 3.5 gigahertz (3.5 GHz) as well as millimeter wave (mm) bands such as 28 GHz and 39 GHz. It is also possible to implement it in the ultra-high frequency band ('Above 6GHz') called Wave. In addition, in the case of 6G mobile communication technology, which is called the system of Beyond 5G, Terra is working to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced to one-tenth. Implementation in Terahertz bands (e.g., 95 GHz to 3 THz) is being considered.

In the early days of 5G mobile communication technology, there were concerns about ultra-wideband services (enhanced Mobile BroadBand, eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). With the goal of satisfying service support and performance requirements, efficient use of ultra-high frequency resources, including beamforming and massive array multiple input/output (Massive MIMO) to alleviate radio wave path loss and increase radio wave transmission distance in ultra-high frequency bands. Various numerology support (multiple subcarrier interval operation, etc.) and dynamic operation of slot format, initial access technology to support multi-beam transmission and broadband, definition and operation of BWP (Band-Width Part), large capacity New channel coding methods such as LDPC (Low Density Parity Check) codes for data transmission and Polar Code for highly reliable transmission of control information, L2 pre-processing, and dedicated services specialized for specific services. Standardization of network slicing, etc., which provides networks, has been carried out.

Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology, considering the services that 5G mobile communication technology was intended to support, based on the vehicle's own location and status information. V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience, and NR-U (New Radio Unlicensed), which aims to operate a system that meets various regulatory requirements in unlicensed bands. ), NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with the terrestrial network is impossible, positioning, etc. Physical layer standardization for technology is in progress.

In addition, IAB (IAB) provides a node for expanding the network service area by integrating intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, and wireless backhaul links and access links. Integrated Access and Backhaul, Mobility Enhancement including Conditional Handover and DAPS (Dual Active Protocol Stack) handover, and 2-step Random Access (2-step RACH for simplification of random access procedures) Standardization in the field of wireless interface architecture/protocol for technologies such as NR) is also in progress, and a 5G baseline for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technology Standardization in the field of system architecture/services for architecture (e.g., Service based Architecture, Service based Interface) and Mobile Edge Computing (MEC), which provides services based on the location of the terminal, is also in progress.

When this 5G mobile communication system is commercialized, an explosive increase in connected devices will be connected to the communication network. Accordingly, it is expected that strengthening the functions and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, eXtended Reality (XR) and Artificial Intelligence to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR). , AI) and machine learning (ML), new research will be conducted on 5G performance improvement and complexity reduction, AI service support, metaverse service support, and drone communication.

In addition, the development of these 5G mobile communication systems includes new waveforms, full dimensional MIMO (FD-MIMO), and array antennas to ensure coverage in the terahertz band of 6G mobile communication technology. , multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, Full Duplex technology, satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design stage and end-to-end. -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI support functions, and next-generation distributed computing technology that realizes services of complexity beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could be the basis for .

Meanwhile, 3GPP, which is in charge of cellular mobile communication standards, has named a new Core Network structure as 5G Core (5GC) and is standardizing it in order to evolve from the 4G LTE system to the 5G system.

5GC supports the following differentiated functions compared to the Evolved Packet Core (EPC), the network core for 4G.

First, in 5GC, the Network Slice function is introduced. As a requirement of 5G, 5GC must support a variety of terminal types and services; e.g., enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), massive Machine Type Communications (mMTC). These terminals/services each have different requirements for the core network. For example, eMBB service requires a high data rate, and URLLC service requires high stability and low delay. The proposed technology to satisfy these various service requirements is the Network Slice method.

Network slicing is a method of creating multiple logical networks by virtualizing one physical network, and each Network Slice Instance (NSI) can have different characteristics. Each NSI can satisfy various service requirements by having a network function (NF) suited to its characteristics. Multiple 5G services can be efficiently supported by allocating an NSI that matches the characteristics of the service required for each terminal.

Second, 5GC can facilitate network virtualization paradigm support through separation of mobility management function and session management function. In 4G LTE, all terminals can receive services from the network through signaling exchange with a single core device called the Mobility Management Entity (MME), which is responsible for registration, authentication, mobility management, and session management functions. In 5G, as the number of terminals increases explosively and the mobility and traffic/session characteristics that must be supported depending on the type of terminal are subdivided, when all functions are supported by a single device such as MME, scalability is achieved by adding entities for each required function. This has no choice but to fall. Therefore, various functions are being developed based on a structure that separates the mobility management function and session management function to improve scalability in terms of signaling load and functional/implementation complexity of the core equipment responsible for the control plane.

In the case of metaverse and extended reality (XR) applications, the terminal must transmit a large amount of traffic through downlink/uplink, so unlike existing applications, important technical issues are required to effectively process traffic. It must be resolved.

Unlike existing studies that have mainly focused on effectively transmitting downlink traffic to the terminal, Metaverse/XR traffic requires downlink traffic to be effectively processed by considering the service characteristics of each packet. There is a need. XR devices require large amounts of traffic processing, but due to limitations such as the weight of wearable devices, the battery capacity of the device may be limited and efficient power management of the device may be required when providing XR services.

According to an embodiment of the present disclosure, an apparatus and method for generating related information to support a power saving service in consideration of network characteristics in a communication system may be provided.

According to an embodiment of the present disclosure, an apparatus and method for providing related information for a power saving service based on network and service characteristic information provided by an application server or functional entity in a communication system may be provided.

According to an embodiment of the present disclosure, when jitter is generated by the network environment in a communication system, the jitter range information of the network measured through the above process is transmitted to the RAN and the characteristics of the power saving service (DRX parameters) delivered to the UE ), an apparatus and method for scheduling packets for power saving can be provided.

According to an embodiment of the present disclosure, a method of operating a policy control function (PCF) in a wireless communication system includes a power saving service support indicator, jitter range information, and period information transmitted from an application function (AF). A PCC that includes a receiving operation through a network exposure function (NEF), a policy for N6 jitter measurement, and QoS (quality of service) monitoring parameter information for 5GC jitter measurement, based on the jitter range information and the period information. An operation of updating (policy and charging control) rules, and the updated PCC rules are set to session management (SMF) so that jitter-related information and rules for jitter range measurement for the power saving service are transmitted to the user plane function (UPF). It may include an operation to transmit to a function).

According to an embodiment of the present disclosure, a method of operating a user plane function (UPF) in a wireless communication system includes jitter-related information and rules for measuring jitter range to support a power saving service transmitted from a policy control function (PCF). An operation of receiving updated policy and charging control (PCC) rules from a session management function (SMF), including a real-time transport protocol (RTP) transmitted through an application server (AS) based on the updated PCC rules. ) Checking the timestamp in the header of the packet and measuring jitter in the N6 section using the time difference between received packets, and performing QoS monitoring service for jitter measurement values in the N6 section and jitter measurement in 5GC. It may include transmitting the packet transmission delay value measured through to the SMF.

According to an embodiment of the present disclosure, a policy control function (PCF) in a wireless communication system includes a transceiver; and a control unit. The control unit may receive a power saving service support indicator, jitter range information, and period information transmitted from an application function (AF) through a network exposure function (NEF). The control unit updates policy and charging control (PCC) rules including a policy for N6 jitter measurement and QoS (quality of service) monitoring parameter information for 5GC jitter measurement based on the jitter range information and the period information. can do. The control unit may control transmission of the updated PCC rules to a session management function (SMF) so that jitter-related information and rules for measuring the jitter range for the power saving service are transmitted to the user plane function (UPF). .

According to an embodiment of the present disclosure, a user plane function (UPF) in a wireless communication system includes a transceiver; and a control unit. The control unit receives updated policy and charging control (PCC) rules, including jitter-related information and rules for jitter range measurement, from a session management function (SMF) to support power saving services transmitted from a policy control function (PCF). You can receive it. Based on the updated PCC rule, the control unit checks the timestamp in the header of the RTP (real-time transport protocol) packet delivered through the AS (application server) and uses the time difference between received packets. Thus, the jitter of the N6 section can be measured. The control unit may control to transmit to the SMF the jitter measurement value of the N6 section and the packet transmission delay value measured through QoS monitoring service performance for jitter measurement within 5GC.

According to an embodiment of the present disclosure, AF can manage a battery saving policy considering the network according to the characteristics of the service.

A network entity (PCF or NWDAF) according to an embodiment of the present disclosure measures jitter in 5GC using a QoS monitoring service in UPF to measure transmission jitter on an actual network based on network jitter requirements for battery saving policy management, and Based on the jitter measurement value of the N6 section, the jitter range value of the measured network can be statistically analyzed.

According to an embodiment of the present disclosure, when the threshold value of the corresponding jitter range is exceeded, the PCF reports the jitter range value for power saving service support to the RAN, and the RAN reports the jitter range value indicating a change in the characteristics of traffic served in the actual network. Depending on the value, service characteristics can be changed (DRX parameter update).

According to an embodiment of the present disclosure, when servicing high-frame and high-capacity application traffic such as XR service, appropriate power saving service function according to network changes by adjusting service characteristics (DRX parameters) based on packet transmission delay and jitter in the actual network. can be provided. According to an embodiment of the present disclosure, an apparatus and method that can provide an efficient XR service application service can be provided.

Figure 1 shows the network structure and interface of a 5G system according to an embodiment of the present disclosure.
Figure 2 shows an operation when applying a packet delay measurement policy and operation through QoS monitoring in a PCF in a wireless communication system according to an embodiment of the present disclosure.
Figure 3 illustrates a packet reception operation of a terminal due to a difference in packet reception time according to a jitter of transmission delay on the network when the terminal receives a packet in a wireless communication system according to an embodiment of the present disclosure.
FIG. 4 is a diagram illustrating an operation of performing battery saving in a wireless communication system according to an embodiment of the present disclosure.
FIGS. 5A and 5B are flowcharts showing a process in which DRX parameters are updated based on updated jitter range information in a wireless communication system according to an embodiment of the present disclosure.
FIGS. 6A and 6B are flowcharts showing a process in which DRX parameters are updated based on updated jitter range information in a wireless communication system according to another embodiment of the present disclosure.
Figure 7 shows the structure of a terminal according to an embodiment of the present disclosure.
Figure 8 shows the structure of a network device according to an embodiment of the present disclosure.

Hereinafter, an embodiment of the present disclosure will be described in detail with reference to the attached drawings.

In describing the present disclosure, description of technical content that is well known in the technical field to which the present disclosure belongs and that is not directly related to the present disclosure will be omitted. This is to convey the gist of the present disclosure more clearly without obscuring it by omitting unnecessary explanation. In addition, the terms described below are terms defined in consideration of the functions in the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification.

For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically shown. Additionally, the size of each component does not entirely reflect its actual size. In each drawing, identical or corresponding components are assigned the same reference numbers.

The advantages and features of the present disclosure and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms, and the present embodiments are merely intended to ensure that the disclosure is complete and are within the scope of common knowledge in the technical field to which the present disclosure pertains. It is provided to fully inform those who have the scope of the disclosure, and the disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification. Additionally, when describing the present disclosure, if it is determined that a detailed description of a related function or configuration may unnecessarily obscure the gist of the present disclosure, the detailed description will be omitted. In addition, the terms described below are terms defined in consideration of the functions in the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification.

Hereinafter, a base station (BS) is an entity that performs resource allocation for a terminal, such as gNode B, eNode B, Node B, (or xNode B (where x is an alphabet including g and e)), a wireless access unit. , it may be at least one of a base station controller, a satellite, an airborn, or a node on a network. Terminal (user equipment: UE) may include a MS (Mobile Station), vehicle, satellite, airborn, cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. You can. In this disclosure, downlink (DL) refers to the wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. Additionally, a sidelink (SL), which refers to a wireless transmission path of a signal transmitted from a terminal to another terminal, may exist.

In addition, although the LTE, LTE-A or 5G system may be described below as an example, embodiments of the present disclosure can also be applied to other communication systems with similar technical background or channel type. For example, this may include 5G-Advance or NR-Advance or the 6th generation mobile communication technology (6G) developed after 5G mobile communication technology (or new radio, NR), and 5G hereinafter refers to existing LTE, LTE- It may be a concept that includes A and other similar services. In addition, this disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person with skilled technical knowledge.

At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions. These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory The instructions stored in may also produce manufactured items containing instruction means that perform the functions described in the flow diagram block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative execution examples it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially simultaneously, or it is possible for the blocks to be performed in reverse order depending on the corresponding function.

At this time, the term '~unit' used in this embodiment refers to software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and '~unit' performs certain roles. do. However, '~part' is not limited to software or hardware. The '~ part' may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Therefore, as an example, '~ part' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and 'parts' may be combined into a smaller number of components and 'parts' or may be further separated into additional components and 'parts'. Additionally, components and 'parts' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card. Additionally, in an embodiment, '~ part' may include one or more processors.

Wireless communication systems have moved away from providing early voice-oriented services to, for example, 3GPP's HSPA (High Speed Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), and LTE-Advanced. Broadband wireless that provides high-speed, high-quality packet data services such as communication standards such as (LTE-A), LTE-Pro, 3GPP2's High Rate Packet Data (HRPD), UMB (Ultra Mobile Broadband), and IEEE's 802.16e. It is evolving into a communication system.

As a representative example of the broadband wireless communication system, the LTE system adopts Orthogonal Frequency Division Multiplexing (OFDM) in the downlink (DL), and Single Carrier Frequency Division Multiplexing (SC-FDMA) in the uplink (UL). Access) method is adopted. Uplink refers to a wireless link through which a terminal transmits data or control signals to a base station, and downlink refers to a wireless link through which a base station transmits data or control signals to a terminal. The above multiple access method usually distinguishes each user's data or control information by allocating and operating the time-frequency resources to carry data or control information for each user so that they do not overlap, that is, orthogonality is established. You can.

As a future communication system after LTE, that is, the 5G communication system must be able to freely reflect the various requirements of users and service providers, so services that simultaneously satisfy various requirements must be supported. Services considered for the 5G communication system include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC). There is.

eMBB aims to provide more improved data transmission speeds than those supported by existing LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20Gbps in the downlink and 10Gbps in the uplink from the perspective of one base station. In addition, the 5G communication system must provide the maximum transmission rate and at the same time provide increased user perceived data rate. In order to meet these requirements, improvements in various transmission and reception technologies are required, including more advanced multi-antenna (Multi Input Multi Output, MIMO) transmission technology. In addition, while LTE transmits signals using a maximum of 20MHz transmission bandwidth in the 2GHz band, the 5G communication system uses a frequency bandwidth wider than 20MHz in the 3~6GHz or above 6GHz frequency band to transmit the data required by the 5G communication system. Transmission speed can be satisfied.

mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. In order to efficiently provide the Internet of Things, mMTC requires support for access to a large number of terminals within a cell, improved coverage of terminals, improved battery time, and reduced terminal costs. Since the Internet of Things provides communication functions by attaching various sensors and various devices, it must be able to support a large number of terminals (for example, 1,000,000 terminals/km ² ) within a cell. Due to the nature of the service, terminals that support mMTC are likely to be located in shaded areas that cannot be covered by cells, such as the basement of a building, so they may require wider coverage than other services provided by the 5G communication system. Terminals that support mMTC must be composed of low-cost terminals, and since it is difficult to frequently replace the terminal's battery, a very long battery life time, such as 10 to 15 years, may be required.

URLLC is a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency situations. Services used for emergency alerts, etc. can be considered. Therefore, the communication provided by URLLC must provide very low latency and very high reliability. For example, a service that supports URLLC must satisfy an air interface latency of less than 0.5 milliseconds and has a packet error rate of less than 10-5. Therefore, for services that support URLLC, the 5G system must provide a smaller Transmit Time Interval (TTI) than other services, and at the same time, it is a design that must allocate wide resources in the frequency band to ensure the reliability of the communication link. Specifications may be required.

The three services of 5G, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted in one system. At this time, different transmission/reception techniques and transmission/reception parameters can be used between services to satisfy the different requirements of each service. Of course, 5G is not limited to the three services mentioned above.

5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and includes sub-6 GHz ('Sub 6GHz') bands such as 3.5 gigahertz (3.5 GHz) as well as millimeter wave (mm) bands such as 28 GHz and 39 GHz. It is also possible to implement it in the ultra-high frequency band ('Above 6GHz') called Wave. In addition, in the case of 6G mobile communication technology, which is called the system of Beyond 5G, Terra is working to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced to one-tenth. Implementation in Terahertz bands (e.g., 95 GHz to 3 THz) is being considered.

In the early days of 5G mobile communication technology, there were concerns about ultra-wideband services (enhanced Mobile BroadBand, eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). With the goal of satisfying service support and performance requirements, efficient use of ultra-high frequency resources, including beamforming and massive array multiple input/output (Massive MIMO) to alleviate radio wave path loss and increase radio wave transmission distance in ultra-high frequency bands. Various numerology support (multiple subcarrier interval operation, etc.) and dynamic operation of slot format, initial access technology to support multi-beam transmission and broadband, definition and operation of BWP (Band-Width Part), large capacity New channel coding methods such as LDPC (Low Density Parity Check) codes for data transmission and Polar Code for highly reliable transmission of control information, L2 pre-processing, and dedicated services specialized for specific services. Standardization of network slicing, etc., which provides networks, has been carried out.

Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology, considering the services that 5G mobile communication technology was intended to support, based on the vehicle's own location and status information. V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience, and NR-U (New Radio Unlicensed), which aims to operate a system that meets various regulatory requirements in unlicensed bands. ), NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is not possible, positioning, etc. Physical layer standardization for technology is in progress.

In addition, IAB (IAB) provides a node for expanding the network service area by integrating intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, and wireless backhaul links and access links. Integrated Access and Backhaul, Mobility Enhancement including Conditional Handover and DAPS (Dual Active Protocol Stack) handover, and 2-step Random Access (2-step RACH for simplification of random access procedures) Standardization in the field of wireless interface architecture/protocol for technologies such as NR) is also in progress, and a 5G baseline for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technology Standardization in the field of system architecture/services for architecture (e.g., Service based Architecture, Service based Interface) and Mobile Edge Computing (MEC), which provides services based on the location of the terminal, is also in progress.

When this 5G mobile communication system is commercialized, an explosive increase in connected devices will be connected to the communication network. Accordingly, it is expected that strengthening the functions and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, eXtended Reality (XR) and Artificial Intelligence to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR). , AI) and machine learning (ML), new research will be conducted on 5G performance improvement and complexity reduction, AI service support, metaverse service support, and drone communication.

In addition, the development of these 5G mobile communication systems includes new waveforms, full dimensional MIMO (FD-MIMO), and array antennas to ensure coverage in the terahertz band of 6G mobile communication technology. , multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, Full Duplex technology, satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design stage and end-to-end. -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI support functions, and next-generation distributed computing technology that realizes services of complexity beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could be the basis for .

3GPP, which is in charge of cellular mobile communication standards, has named a new Core Network structure as 5G Core (5GC) and is standardizing it in order to evolve from the 4G LTE system to the 5G system. 5GC supports the following differentiated functions compared to the Evolved Packet Core (EPC), the network core for 4G.

In 5GC, the Network Slice function is introduced. As a requirement of 5G, 5GC must support a variety of terminal types and services; e.g., enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), massive Machine Type Communications (mMTC). These terminals/services each have different requirements for the core network. For example, an eMBB service may require a high data rate, and a URLLC service may require high stability and low delay. To satisfy these various service requirements, network slice technology was proposed.

Network slicing may refer to a method of virtualizing one physical network to create multiple logical networks (for example, network slices). An activated network slice may be referred to as a network slice instance, and each network slice instance (NSI) may have different characteristics. Mobile communication service providers can satisfy various service requirements depending on the terminal/service by configuring a network function (NF) suited to the characteristics of each NSI. For example, mobile communication service providers can efficiently support multiple 5G services (e.g. eMBB, URLLC, or mMTC) by allocating an NSI that matches the characteristics of the service required for each terminal.

5GC can facilitate network virtualization paradigm support through separation of mobility management function and session management function. In 4G LTE, all terminals can receive services from the network through signaling exchange with a single core entity called a mobility management entity (MME), which is responsible for registration, authentication, mobility management, and session management functions. In 5G, as the number of terminals (including, for example, MTC terminals) increases explosively and the mobility and traffic/session characteristics that must be supported according to the type of terminals are segmented, a single entity (e.g., MME) must support all functions. If this happens, the scalability of adding entities for each required function will inevitably decline. Therefore, various functions are being developed based on a structure that separates the mobility management function and session management function to improve scalability in terms of signaling load and functional/implementation complexity of the core entity responsible for the control plane.

Hereinafter, embodiments of the present invention will be described in detail with the accompanying drawings. Additionally, when describing the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the gist of the present invention, the detailed description will be omitted. The terms described below are defined in consideration of the functions in the present invention, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification. For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically shown. Additionally, the size of each component does not entirely reflect its actual size. In each drawing, identical or corresponding components are assigned the same reference numbers. The advantages and features of the technical idea according to the present disclosure and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. The present embodiments are merely provided to ensure that the present disclosure is complete and to those skilled in the art to which the present disclosure pertains. It is provided to fully inform the person of the scope of the invention, and the present disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification. Additionally, when describing the present disclosure, if it is determined that a detailed description of a related function or configuration may unnecessarily obscure the gist of the technical idea according to the present disclosure, the detailed description will be omitted. In addition, the terms described below are terms defined in consideration of the functions in the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification.

Hereinafter, the base station is the entity that performs resource allocation for the terminal, such as eNode B, Node B, BS (Base Station), RAN (Radio Access Network), AN (Access Network), RAN node, radio access unit, base station controller, or It can be at least one of the nodes on the network. A terminal may include a UE (User Equipment), MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. In the present invention, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, embodiments of the present disclosure will be described below using the LTE or LTE-A system as an example, but the embodiments of the present disclosure may also be applied to other communication systems with similar technical background or channel type. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included in a system to which embodiments of the present disclosure can be applied, and 5G hereinafter refers to existing LTE, LTE-A, and It may be a concept that includes other similar services. In addition, the embodiments of the present disclosure can be applied to other communication systems through some modifications without significantly departing from the scope of the present invention at the discretion of a person with skilled technical knowledge. At this time, it will be understood that each block of the processing flow diagram diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions.

These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory The instructions stored in may also produce manufactured items containing instruction means that perform the functions described in the flow diagram block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative execution examples it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially simultaneously, or it is possible for the blocks to be performed in reverse order depending on the corresponding function. At this time, the term '~unit' used in the embodiments of the present disclosure refers to software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and '~unit' refers to any Can perform roles. However, '~part' is not limited to software or hardware. The '~ part' may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Therefore, as an example, '~ part' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and 'parts' may be combined into a smaller number of components and 'parts' or may be further separated into additional components and 'parts'. Additionally, components and 'parts' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card. Additionally, in an embodiment, '~ part' may include one or more processors.

FIG. 1 is a diagram illustrating the network structure and interface of a 5G system according to an embodiment of the present disclosure.

A network entity included in the network structure of the 5G system in FIG. 1 may include a network function (NF) depending on system implementation.

Referring to FIG. 1, the network structure of the 5G system 100 may include various network entities. As an example, the 5G system 100 includes an authentication server function (AUSF) entity 108, an access and mobility management function (AMF) entity 103, a session management function ( session management function (SMF) entity (105), policy control function (PCF) entity (106), application function (AF) entity (107), unified data management (UDM) Entity 109, data network (DN) 110, network exposure function (NEF) entity 113, network slicing selection function (NSSF) entity 114, edge Application service domain repository (EDR), edge application server (EAS), EAS discovery function (EASDF), user plane function (UPF) entities 104 , (radio) access network (R)AN) 102, and a terminal, for example, a user equipment (UE) 101.

Each NF entity of the 5G system 100 supports the following functions.

AUSF 108 processes and stores data for authentication of UE 101.

The AMF 103 provides functions for UE-level access and mobility management, and each UE can be basically connected to one AMF. Specifically, the AMF 103 supports CN inter-node signaling for mobility between 3GPP access networks, termination of a radio access network (RAN) CP interface (i.e., N2 interface), and non-access stratum (NAS) ) Endpoint of signaling (N1), NAS signaling security (NAS ciphering and integrity protection), AS security control, registration management (registration area management), connection management, idle mode UE accessibility ( reachability (including control and performance of paging retransmissions), mobility management controls (subscriptions and policies), intra-system mobility and inter-system mobility support, support for network slicing, SMF selection, lawful intercept (AMF events and (for interface to LI system), providing delivery of session management (SM) messages between UE and SMF, transparent proxy for SM message routing, access authentication, roaming authority check It supports functions such as access authorization, providing delivery of SMS messages between the UE and SMSF, security anchor function (SAF), and/or security context management (SCM). Some or all of the functions of AMF entity 103 may be supported within a single instance of one AMF entity.

DN 110 means, for example, an operator service, Internet access, or a third party service. The DN 110 transmits a downlink protocol data unit (PDU) to the UPF entity 104 or receives the PDU transmitted from the UE 101 from the UPF entity 104.

The PCF entity 106 receives information about packet flow from the application server and provides the function of determining policies such as mobility management and session management. Specifically, the PCF entity 106 supports a unified policy framework to govern network behavior, and provides policy support so that control plane functional entity(s) (e.g., AMF entities, SMF entities, etc.) can enforce policy rules. It supports functions such as providing rules and implementing a front end to access relevant subscription information for policy decisions within a user data repository (UDR).

The SMF entity 105 provides a session management function, and when the UE 101 has multiple sessions, each session may be managed by a different SMF entity. Specifically, the SMF entity 105 performs session management (e.g., session establishment, modification, and termination, including maintaining a tunnel between the UPF entity 104 and the (R)AN 102 node), UE IP address, and Allocation and management (optionally including authentication), selection and control of UP functions, establishment of traffic steering to route traffic to appropriate destinations in UPF entity 104, interface to policy control functions. Termination, enforcement of policy and control portion of quality of service (QoS), lawful intercept (for SM events and interface to LI system), termination of SM portion of NAS messages, downlink data notification. notification), initiator of AN-specific SM information (delivered to (R)AN 102 via N2 via AMF entity 103), determination of session and service continuity (SSC) mode of session, roaming function, etc. Supports. Some or all of the functionality of the SMF entity 105 may be supported within a single instance of one SMF entity.

The UDM entity 109 stores the user's subscription data, policy data, etc. The UDM entity 109 includes two parts: an application front end (FE) (not shown) and a user data repository (UDR) (not shown).

The FE includes the UDM FE, which is responsible for location management, subscription management, and credential processing, and the PCF entity, which is responsible for policy control. The UDR stores the data required for the functions provided by the UDM-FE and the policy profile required by the PCF entity. Data stored within the UDR includes user subscription data and policy data, including subscription identifiers, security credentials, access and mobility-related subscription data, and session-related subscription data. UDM-FE accesses subscription information stored in UDR and supports functions such as authentication credential processing, user identification handling, access authentication, registration/mobility management, subscription management, and SMS management. do.

The UPF entity 104 delivers the downlink PDU received from the DN 110 to the UE 101 via the (R)AN 102, and from the UE 101 via the (R)AN 102. The received uplink PDU is delivered to the DN (110). Specifically, the UPF entity 104 is an anchor point for intra/inter RAT mobility, an external PDU session point for interconnect to the Data Network, packet routing and forwarding, and packet inspection. User plane portion of inspection and policy rule enforcement, lawful intercept, traffic usage reporting, and uplink classifier to support routing of traffic flows to the data network, multi-homed ) Branching points to support PDU sessions, QoS handling for the user plane (e.g. packet filtering, gating, uplink/downlink rate enforcement), uplink traffic verification (service It supports functions such as data flow (service data flow (SDF) mapping between SDF and QoS flow), transport level packet marking in uplink and downlink, downlink packet buffering, and downlink data notification triggering function. Some or all of the functions of UPF entity 104 may be supported within a single instance of one UPF.

The AF entity 107 provides services (e.g., supports functions such as application influence on traffic routing, access to network capability exposure, and interaction with policy frameworks for policy control). Interoperates with the 3GPP core network.

(R)AN 102 supports both evolved E-UTRA (evolved E-UTRA), which is an evolved version of 4G radio access technology, and new radio (NR) (e.g., gNB). A general term for a new wireless access network.

The gNB provides functions for radio resource management (i.e., radio bearer control, radio admission control, connection mobility control, dynamic provision of resources to the UE in uplink/downlink). dynamic allocation of resources (i.e. scheduling), Internet protocol (IP) header compression, encryption and integrity protection of user data streams, routing to AMF is not determined from the information provided to the UE. In this case, selection of AMF upon attachment of the UE, user plane data routing to UPF(s), control plane information routing to AMF, connection setup and teardown, scheduling and transmission of paging messages (originating from AMF), system Scheduling and transmission of broadcast information (from AMF or operating and maintenance (O&M)), setting up measurements and measurement reporting for mobility and scheduling, transport level packet marking in the uplink, Session management, support of network slicing, QoS flow management and data mapping to radio bearers, support of UE in inactive mode, distribution function of NAS messages, NAS node selection function, radio access network sharing, dual connectivity ( Supports features such as dual connectivity and tight interworking between NR and E-UTRA.

UE 101 refers to a user device. A user device may be referred to by terms such as terminal, mobile equipment (ME), mobile station (MS), etc. Additionally, the user device may be a portable device such as a laptop, a mobile phone, a personal digital assistant (PDA), a smartphone, or a multimedia device, or it may be a non-portable device such as a personal computer (PC) or a vehicle-mounted device.

NEF 111 is provided by 3GPP network functions, e.g., 3rd party, internal exposure/re-exposure, application functions, edge computing. Provides a means to safely expose services and capabilities for NEF 111 receives information (based on the exposed capability(s) of the other NF(s)) from other NF(s). NEF 111 may store received information as structured data using standardized interfaces to data storage network functions. The stored information may be re-exposed by the NEF entity 111 to other NF entity(s) and AF entity(s) and used for other purposes such as analysis.

The EASDF (112) is an NF that can add an ECS option for each FQDN, which can be expressed as the address of the DNS server that will forward the terminal's DNS request, and the IP subnet address that must be added when forwarding the terminal's DNS request. The EASDF (112) receives EAS domain setting information from the EDR (113) and processes the DNS request message received from the terminal according to the received information. In addition, the EASDF (112) receives the terminal IP address, location information of the terminal within 3GPP, DNS message processing rules, and DNS message reporting rules from the SMF (105), DNS Query message received from the terminal, and received from the DNS server. It is an NF that processes a DNS response message and transmits the information in the DNS message and the processed statistical information to the SMF 105 according to the DNS message reporting rules.

For clarity of explanation, the NF repository function (NRF) is not shown in FIG. 1, but all NFs shown in FIGS. 5A and 5B can interact with the NRF as needed.

NRF supports service discovery functions. An NF discovery request is received from the NF instance, and information on the discovered NF instance is provided to the NF instance. It also maintains available NF instances and the services they support.

Meanwhile, FIG. 1 illustrates a reference model for a case where the UE 101 accesses one DN 110 using one PDU session for convenience of explanation, but the present disclosure is not limited thereto.

UE 101 can simultaneously access two (ie, local and central) data networks using multiple PDU sessions. At this time, two SMFs may be selected for different PDU sessions. However, each SMF may have the ability to control both the local UPF and the central UPF within the PDU session.

Additionally, UE 101 may simultaneously access two (ie, local and central) data networks provided within a single PDU session.

In the 3GPP system, the conceptual link connecting NFs in the 5G system is defined as a reference point. As an example, the reference point(s) included in the 5G system 100 of FIG. 1 are as follows.

- N1: Reference point between UE (101) and AMF (103)

- N2: Reference point between (R)AN (102) and AMF (103)

- N3: Reference point between (R)AN (102) and UPF (104)

- N4: Reference point between SMF (105) and UPF (104)

- N5: Reference point between PCF (106) and AF (107)

- N6: Reference point between UPF (104) and DN (110)

- N7: Reference point between SMF (105) and PCF (106)

- N8: Reference point between UDM (109) and AMF (103)

- N9: Reference point between the two core UPFs 104

- N10: Reference point between UDM (109) and SMF (105)

- N11: Reference point between AMF (103) and SMF (105)

- N12: Reference point between AMF (103) and AUSF (108)

- N13: Reference point between UDM (109) and AUSF (108)

- N14: Reference point between two AMFs 103

- N15: Reference point between PCF and AMF for non-roaming scenarios, reference point between PCF and AMF in visited network for roaming scenarios

- Nx: Reference point between SMF (105) and EASDF (112)

- Ny: Reference point between NEF (EDF) (111) and EASDF (112)

Figure 2 illustrates an operation when applying a packet delay measurement policy and operation through QoS monitoring in a PCF in a wireless communication system according to an embodiment of the present disclosure.

Referring to FIG. 2, it can be assumed that the 5G network and the terminal (or UE) are configured to support a UE power saving function using at least one DRX-related information.

In FIG. 2, the terminal can know that packets will be delivered periodically based on information included in the RCC connection configuration (eg, at least one DRX parameter).

The terminal operates in a DRX cycle cycle, and the DRX Cycle can have a Long or Short cycle value. When the terminal starts receiving packets such as PDCCH and transmits the period for receiving the packet to the terminal as an on-durtation parameter, the terminal receives the packet and enters wake up mode during the on-duration period to receive the packet. You can. When the terminal starts receiving packets, information about how long the terminal will operate in wake up mode can be transmitted to the terminal through the DRX parameter using a timer.

When the timer or on-duration time ends, the terminal enters sleep mode to reduce battery consumption of the terminal. The DRX parameter indicating the sleep mode can be expressed as Opportunity for DRX or off duration shown in FIG. 2, and among the DRX parameter values, the period excluding the onDurationTimer value from the DRX Cycle value can be calculated.

To reduce battery consumption of the terminal, parameters defining the operation cycle (wake-up and sleep mode) of the terminal can be transmitted and received between the terminal and the RAN through an RRC connection configuration message at the beginning of the connection. Afterwards, when the parameter value defining the operation cycle of the terminal is updated, the updated value is delivered to the terminal through an RRC connection reconfiguration message and the DRX parameter values set in the terminal are updated again to configure the terminal based on the updated parameters. A packet transmission/reception operation cycle for battery saving can be set.

Figure 3 illustrates a packet reception operation of a terminal due to a difference in packet reception time according to a jitter of transmission delay on the network when the terminal receives a packet in a wireless communication system according to an embodiment of the present disclosure.

In FIG. 3, the UE can receive DRX parameters set through an RRC connection configuration message from the RAN and perform periodic operations (wake-up and sleep mode) for packet reception.

However, depending on the actual network situation, the packet is received by the terminal faster than the periodic operation period (packet reception pattern indicated as "Reception Early" in Figure 3) or received by the terminal later than the periodic operation period (packet reception pattern indicated as "Reception Early" in Figure 3). packet reception pattern indicated as “Late”).

If the terminal receives packets according to the packet reception pattern indicated as "Reception Late", the period of the terminal's sleep mode pattern may decrease and efficiency may decrease.

When the terminal receives a packet according to a packet reception pattern marked as "Reception Early", the wake-up cycle of the terminal for packet reception operation is faster than the operation prediction cycle (DRX cycle) within the DRX parameters previously received from the RAN. If the terminal switches from sleep mode to wake up mode before the DRX cycle, this may cause prediction errors in the operation pattern for battery efficiency of the terminal and prevent efficient battery saving operations.

If the terminal repeatedly receives packets according to the packet reception pattern marked as "Reception Early", the terminal or RAN determines when the terminal will switch to sleep mode or whether to perform periodic operations using DRX parameters, such as whether the current DRX cycle is incorrect. decisions can be difficult.

According to an embodiment of the present disclosure, UPF measures jitter-related information that occurs during N6 section transmission, and PCF or NWDAF can derive statistical jitter-related information using the measured jitter-related information. As shown in Figure 3, the pattern of packets arriving late or early to the terminal can be defined as a jitter range.

The following three functions can be supported to perform updates to DRX parameters such as DRX cycle based on the defined jitter range.

First, the measurement of the difference (Jitter) between transmission delays between packets in the N6 section between UPF and AS is determined according to the AF request or operator policy, and the measured transmission delay difference (Jitter) between packets is set to default. If it exceeds the set jitter range (Defualt jitter Range), this can be transmitted to the RAN and DRX parameters can be updated based on this.

Second, if a temporary increase in jitter value occurs due to the movement of the terminal, this can be excluded when calculating the statistical characteristics of jitter to prevent DRX parameter updates due to temporary exceedance of the jitter range due to the occurrence of exceptional situations. there is.

Third, considering the characteristics of the content delivered through the XR service, DRX parameters can be set by setting the basic jitter range based on this.

Among the packets that make up service traffic in the XR service, packets with the same traffic characteristics can be defined in units of PDU sets, and multiple packets can be configured within one PDU set. For example, in the case of a service floor composed of video traffic, each PDU set may be composed of an I frame, a B frame, or a P frame.

When providing a service in units of a PDU set, if the content characteristics are dynamic (e.g., a sports game), the number of content packets constituting the PDU set is large, and the content duration may be long accordingly. If the content characteristics are static (eg, documentary or drama), the number of content packets constituting the content may be small.

The jitter range varies depending on the content characteristics, and the DRX parameter settings suitable for the content characteristics can be updated by adjusting the onDurationTimer in the DRX parameters based on the information.

The above functions include the following AF request, NEF service provision, N6 jitter monitoring policy for measuring transmission delay difference (jitter) between packets transmitted in N6 section from PCF entity, N6 jitter monitoring reporting policy, and battery between RAN and UE. DRX parameters can be updated and delivered to the UE based on at least one of the AF requirements for providing saving services.

According to one embodiment, the SMF entity may generate information for jitter monitoring of the N4 rule and N6 section and transmit it to the UPF entity.

According to one embodiment, the PCF entity or NWDAF entity analyzes the statistical characteristics of the information of the received N6 section, and if it exceeds the basic jitter range, the AMF entity may transmit the result reporting to the RAN.

According to one embodiment, when the NWDAF entity analyzes statistical characteristics of information in the N6 section, the NWDAF entity may report statistical jitter result information to the PCF entity.

According to one embodiment, the SMF entity may transmit the N6 section jitter monitoring result received from the UPF entity to the NWDAF entity.

According to one embodiment, the NWDAF entity may determine a policy for statistical analysis based on the amount of change (jitter) in the packet transmission delay value using the N6 section jitter monitoring result value received from the SMF entity. According to one embodiment, a reporting function may be provided to the PCF entity when the basic jitter range threshold is exceeded.

According to one embodiment, if there is no difference in transmission delay (jitter) between packets between N3 and RAN and UE, it can be assumed that only jitter monitoring in the N6 section is used. If jitter occurs during packet transmission in 5GC through actual QoS monitoring, the jitter range can be set by adding the actual jitter value of 5GC through QoS monitoring to the jitter measurement value of the N6 section, and this is transmitted to the RAN to determine the DRX parameters in the RAN. It can be used when updating.

FIG. 4 is a diagram illustrating an operation of performing battery saving in a wireless communication system according to an embodiment of the present disclosure.

Referring to FIG. 4, the wireless communication system 400 includes UE 401, NG-RAN 402, AMF 403, UPF 404, SMF 405, PCF 406, and network data analytics (NWDAF). It may include function, 407), AF (408), and AS (application server, 409).

The AF (408) may decide to implement a policy for performing the battery saving service and may transmit battery saving-related requirement information to the PCF (406) for this purpose. Through the PCC rule update, the UPF 404 may perform QoS monitoring for 5GC jitter measurement and/or N6 jitter measurement, and/or N6 jitter monitoring operations. Based on the corresponding QoS monitoring and N6 jitter reporting values, the NWDAF 407 may perform statistical analysis of jitter and report this to the PCF 406.

The operation of transmitting the updated jitter range based on the 5GC and N6 jitter monitoring values to the NG-RAN 402 is based on the operation of transmitting the updated jitter range information based on the control plane. Depending on changes in network conditions or traffic characteristics, determine the jitter range based on the jitter of the N6 section and/or 5GC (N3 and Uu section) to update the jitter range and determine whether to forward it to the NG-RAN (402) It may include actions such as:

The operation of updating the jitter range and determining whether to transmit may be performed through the PCF (406) or NDWAF (407).

The UE 401 can use the XR service through RAN (e.g., NG-RAN 402) in a general environment that does not consider battery saving or based on DRX parameters basically provided by the service provider. Depending on the user's choice, the battery status of the terminal, or the status of the network currently being serviced, the XR service currently being used may not support general DRX functions.

In the XR service based on the default DRX parameter provided by the service or network operator, a battery saving service that takes into account 5GC and/or N6 jitter information in consideration of the actual network environment (e.g. DRX parameter update based on service characteristic (Contents type) or network condition (N6 jitter etc.) can be performed.

Unlike general data-based services, XR services may require processing large amounts of data. In the case of video traffic, service traffic characteristics that require transmission of high-capacity data in a certain pattern (e.g. frame rate, etc.) may appear. Additionally, in the case of video traffic, the size of the data constituting the traffic may appear differently depending on the characteristics of the content, so the size and number of packets constituting the traffic packets may vary.

Even in services that have traffic characteristics that show a certain pattern, such as video traffic, the pattern (periodicity or DRX cycle in DRX parameter) of the service traffic may change when the UE (401) receives the packet depending on the network environment and/or service characteristics. This may occur, and there is a need to update the service traffic pattern in consideration of the above changes. The transmission delay and/or difference in transmission delay of packets for each section transmitted on an actual network may be measured. Based on the measurement, service traffic pattern information is updated and can be used for battery saving services that use the information.

The AF 408 may decide to transmit battery (or power) saving support information to the PCF 406 to provide a terminal battery saving service. The AF 408 may generate battery (Power) saving assistance information and transmit it to the PCF 406.

The PCF 406 may receive battery saving support information and perform necessary operations to support battery saving for the corresponding service. At this time, the relevant battery saving support information includes battery saving support indication (power saving support indication), period information of traffic currently being serviced through TSCAI (time sensitive communication assistance information) message, and battery saving information using 5GC and N6 jitter. It may include at least one of the judgment information on whether to use it or not.

According to one embodiment, if there are no separate 5GC and N6 jitter requirements in the battery saving service request message, only the periodicity information in TSCAI is referred to and this is transmitted to the NG-RAN 402 to perform the DRX cycle based on information reflecting only the service characteristics. Parameter updates may be performed.

According to one embodiment, if a jitter range requirement is included in the battery saving support information, the PCF 406 may know that measurement of jitter in the 5GC and/or N6 section is required in the UPF 404. And the information and requirements information for the corresponding N6 measurement can be transmitted to the SMF (405) through PCC rule update.

When using a battery saving service that considers jitter in the 5GC and/or N6 sections, the PCF (406) provides a jitter range (default jitter range) defined in advance through the service operator and/or provider received from the AF (408) and the corresponding service. The periodicity (preodicity) information can be transmitted to the NG-RAN 402, and DRX parameter update can be performed using service periodicity information considering the basic jitter range based on the information. The UE 401 that has received the updated DRX parameters can provide services based on the updated DRX parameters.

The jitter range requirement delivered from AF (408) is a basic jitter range with a long range or short range based on the content type provided by the basic service. value, and the condition for transmitting the jitter range to the RAN for a DRX parameter update request (updated jitter range reporting condition), the requirement for measuring the corresponding jitter in the UPF (N6 jitter measurement period, QoS monitoring period for 5GC packet delay measurement, RTP timestamp sampling rate, notification uri for reporting, etc.), and NF information (jitter range management supporting network function for calculate statistics jitter range) for calculating statistical characteristics of N6 jitter and updating the jitter range through this. there is.

The SMF 405 may receive updated PCC rules based on battery saving support information from the PCF 406 and, based on this, transmit rules for measuring 5GC packet delay and/or jitter in the N6 section to the UPF 404. .

According to one embodiment, the existing connected UPF checks whether the 5GC QoS monitoring and/or N6 jitter monitoring function is supported, and if the function is currently supported by the UPF 404, packets through 5GC QoS monitoring are updated through the N4 rule. Can communicate rules and requirements for delay measurements and/or N6 jitter measurements.

According to one embodiment, when the SMF 405 checks the currently connected UPF 404 function and does not support the function for packet delay measurement and/or N6 jitter measurement through 5GC QoS monitoring, reselection of UPF (reallocation) ) process is performed, and the rules and requirements for N6 jitter measurement can be delivered through the N4 rule creation process with the changed UPF.

The UPF 404 measures the jitter of the N6 section between the UPF 404 and the AS 409 based on packet transmission delay measurement and/or N6 jitter measurement requirements through QoS monitoring received through the SMF 405. The packet delay between the UPF 404 and the UE 401 can be measured through QoS monitoring and delivered to the SMF 405 through an N4 reporting message.

The SMF 405 uses the QoS monitoring and/or N6 jitter reporting values received from the UPF 404 as NF information (jitter range management supporting network function) for processing 5GC and N6 jitter within the jitter range requirement. Depending on the information, it can be delivered to PCF (406) or NWDAF (407).

The PCF 406 or NWDAF 407, which has received the 5GC and/or N6 jitter measurement values, measures 5GC and/or based on at least one of basic jitter information within the jitter range requirements, a jitter calculation method based on statistical characteristics, and information in reporting conditions. Alternatively, calculation operations in the N6 jitter range can be performed. At this time, if the 5GC and/or N6 measurement value is outside the jitter range based on the basic jitter range information, it is immediately reported and the value of the jitter range is transmitted to the NG-RAN (402) to set the DRX parameters based on the value. Jitter range information calculation operations and updates can be performed based on the reporting conditions to be updated.

If the jitter reporting condition is a certain jitter value (number of jitter value) or a certain time-based statistical jitter range calculation (measurement period based statistics jitter range), the statistical characteristics of jitter over a certain period of time. Based on this, the update of the jitter range can be determined. If this is calculated in the PCF (406), it is transmitted to the NG-RAN (402) through the AMF (403). If the NDWAF (407) calculates the statistical jitter range and determines whether to update it, this is sent to the PCF (406). The updated jitter range may be transmitted from the PCF 406 to the NG-RAN 402 via the AMF 403.

The NG-RAN 402, which has received the updated jitter range, can decide to update DRX parameters based on the information. If the NG-RAN 402 decides to update the DRX parameters, it can transmit this to the UE 401 through an RRC connection reconfiguration message to update the DRX parameters for the battery saving service operation of the XR service.

FIGS. 5A and 5B are flowcharts showing a process in which DRX parameters are updated based on updated jitter range information in a wireless communication system according to an embodiment of the present disclosure.

Referring to FIGS. 5A and 5B, the AF may determine policy implementation for providing and requesting a battery saving service considering 5GC and/or N6 jitter network jitter in the XR service. AF transmits QoS monitoring for 5GC jitter measurement and N6 jitter-related requirements information to PCF, and performs QoS monitoring and N6 jitter monitoring operations to measure jitter values of packets coming from AS in UPF through PCC rule update. .

The UPF delivers the relevant QoS monitoring and N6 jitter monitoring reporting values to the PCF, and the PCF determines whether the jitter range is updated based on the jitter value and N6 jitter value based on the QoS monitoring packet transmission delay value reported by the UPF and sends this to the RAN. I can tell you. The RAN performs a DRX parameter update based on the updated jitter range information and sends an RRC Connection reconfiguration message to the UE, which can be used for XR services based on the updated DRX information.

In step 501, the AF provides jitter range information and traffic periodicity information according to the user's selection, service provider's policy, or terminal status (e.g., battery level and/or terminal type). You can use this to decide whether to support battery saving service.

The periodicity information of the traffic is information indicating the interval between two burst packets. For example, in the case of video traffic, it may indicate the interval between each frame. In the case of video traffic, periodicity information can be defined based on the frame rate value indicating the frame interval of the video traffic.

In the XR service, one frame can consist of multiple packets, and when a group of packets is defined as a PDU set, the periodicity information of traffic in the XR service can be defined as the interval between PDU sets (packet groups). . In the corresponding XR service, the periodicity information of traffic can be transmitted as a periodicity value in TSCAI information or separately transmitted to PCF through battery saving assistance information.

Jitter range information to be used for the battery saving service can be determined using the difference between packet transmission delay values measured through a QoS monitoring service to minimize jitter of 5GC and the jitter values of the N6 section between UPF and AS.

In steps 502 and 503, the AF may transmit battery saving support information for the battery saving service using the jitter range and traffic periodicity information generated based on the decision in step 501 to the PCF through the NEF. Battery saving support information for the battery saving service using the generated jitter range and traffic periodicity information may be included in the AF session-related QoS requirement (AFsessionWithQoS Create request) message transmitted from the AF entity to the NEF entity.

Battery saving assistance information is related to jitter range, including Battery saving support indication, packet periodicity information, and policy and requirement information for 5GC and N6 jitter measurements in UPF. Information (jitter range requirement) and, additionally, at least one of End of burst information indicating that reception of packets of the PDU set has been completed based on information on the last packet of the PDU set for each frame.

Policy and requirement information for jitter measurement includes information on whether 5GC (QoS monitoring supported or not indication for 5GC jitter measurement) and N6 jitter (N6 jitter supported or not indication) will be additionally measured and supported in the battery saving service, UPF QoS monitoring and N6 jitter measurement and reporting period (Jitter measurement and reporting period) and characteristic values for jitter measurement (e.g. RTP timestamp sampling rate), jitter range considering the characteristics of traffic services (Long jitter for dynamic contents or Short jitter for static contetns), default jitter range for starting a battery saving service using the jitter range and packet periodicity information, and a threshold for determining whether to report the jitter range based on the measured jitter (jitter) range threshold), whether to immediately report when the jitter range threshold is exceeded or to determine whether the threshold is exceeded based on statistical characteristics (Jitter range reporting frequency); exceptional jitter considering traffic characteristics Jitter reporting condition (Jitter range reporting condition), which includes conditions for determining when a value is measured and excluding statistical calculation of the exceptional jitter value, calculating the jitter and determining the threshold based on the above information. It may include at least one of the type of network entity (NF for statistics jitter calculation and update / resporing decision based on jitter range reporting condition) information.

If 5GC and additional N6 jitter are not used or supported in the battery saving service using jitter, the jitter range can be determined using the jitter value based on the QoS monitoring service. If the N6 jitter utilization requirement and the UPF system support this, the jitter range information can be determined by additionally considering the jitter of the N6 section in addition to the basic jitter information between the UPF and the UE.

If the jitter measurement value exceeds the threshold according to the jitter reporting cycle value, it is immediately reported (reporting based on Instantaneous jitter value), and this is immediately transmitted to the RAN to adjust the jitter value considering the jitter of the actual network or to use the jitter measurement value as a statistical method. By analyzing the characteristic value, it can be determined whether the jitter threshold is exceeded through reporting based on statistical jitter value, and based on this, it can be set whether to transmit the updated jitter range to the RAN.

In step 504, the NEF may transmit jitter assistance information (Battery saving assistance information) to be used when supporting a battery saving service considering the transmission range and traffic cycle from the AF to the PCF entity using a PolicyAuthorization message. According to one embodiment, if a separate policy authorization service process has not been performed through the existing XR service, the policy authorization creation message (Npcf_PolicyAuthorization_Create) request is received, or if there is an existing service process, the policy authorization update (Npcf_PolicyAuthorization_Update) request message is received. XR service-related battery saving service support information can be delivered to the PCF entity.

According to one embodiment, in order to receive additional service-related reporting, the corresponding event reporting may be requested through a policy authorization subscription (Npcf_PolicyAuthorization_Subscribe) message in order to receive messages related to jitter-related reporting events occurring in the PCF. To this end, PCF defines a new event ID related to jitter range reporting (e.g. Jitter range reporting based on jitter measurement) that considers packet delay-based jitter measured through QoS monitoring and jitter in the N6 section to receive reporting related to jitter support information. You can.

In step 505, the PCF may perform a PCC rule update based on requirements for jitter range measurement using the N6 or 5GC-based jitter information. For jitter monitoring and measurement within 5GC, PCF requires separate QoS rule data (qos monitoring id ('qmid'), Reporting Frequency ('repFreqs'), reporting period ('repPeriod) for jitter monitoring and measurement in addition to the existing QoS monitoring request. A separate QoS monitoring request can be made through ') etc. in QOSMonitoringData).

According to one embodiment, the PCF may update the packet generation cycle for QoS monitoring based on the N6 jitter measurement cycle for N6 jitter measurement when updating QoS parameters for jitter monitoring measurement in the 5GC. According to one embodiment, the PCF may additionally request a QoS monitoring service for measuring jitter within 5GC for battery saving, separately from the QoS monitoring parameters and service ID of the service to minimize jitter of 5GC.

When measuring the jitter of 5GC using the separate QoS monitoring service for battery saving, whenever a packet delay measurement related to QoS monitoring occurs to measure the jitter range, it is transmitted to the PCF through SMF, and the PCF sends it to the PCF. Based on this, 5GC-related jitter-related information can be measured.

For jitter measurement in the N6 section, a PCC rule update for separate rules and policies for N6 jitter measurement can be performed in the UPF based on the jitter range requirements within the battery saving support information received through step 504. For example, when the XR service is provided through RTP packets, jitter can be measured in UPF using the timestamp in the RTP header. At this time, since the RTP timestamp value has a random value, the amount of change between the timestamp values of the first or last packets of the packets is used for each measurement period based on the sampling rate information within the jitter range requirements. The jitter value can be calculated.

Since the methods for measuring jitter in the 5GC and N6 sections are different as described above, the PCF receives jitter measurement parameters through step 504 to calculate the jitter range value within the battery saving support information and measures the jitter measurement parameters in each section. PCC rules can be updated based on related information for jitter measurement (Modified QoS monitoring parameter for 5GC jitter measurement, N6 jitter calculation related parameter for N6 jitter measurement).

In step 506, the PCF sends the updated PCC rules, including the policy and operation rules for N6 jitter measurement determined in step 505 and QoS monitoring parameter information for 5GC jitter measurement, through a session policy adjustment update notification (Npcf_SMPolicyControl_UpdateNotify) request message. It can be forwarded to SMF.

In steps 507 and 508, the SMF receives the updated PCC rule containing jitter-related information and rules for measuring the jitter range for supporting the battery saving service received through the PCF in the above step and modifies the N4 session (N4 session) Modification) can be delivered to UPF through a request message. In the request message, QoS monitoring related parameter information for 5GC jitter measurement for jitter range measurement according to AF request (Modified QoS monitoring parameter for 5GC jitter measurement) and related parameter for jitter measurement in N6 section (N6 jitter calculation related parameter for To receive reporting of 5GC jitter value or packet delay value based on the QoS monitoring service and jitter monitoring performance results of N6 section from UPF through SRR (session reporting rule) based on updated PCC rules reflecting N6 jitter measurement) Information can be conveyed.

In step 509, the PCF determines the PCC rule update for the battery saving service in step 505, and then updates the DRX parameters received in step 504 based on the network characteristics (e.g. jitter range) and traffic characteristics (Preodicity) received from AF. The default jitter range and periodicity information within the battery saving support information can be transmitted to AMF through the N1N2 message transfer (Namf_Communication_N1N2MessageTransfer) request message.

In step 510, the AMF may transmit to the RAN through an N2 message for DRX parameter update applying the network (e.g. jitter range) and traffic characteristics (preodicity) received in step 509. The RAN, which has received the jitter range and traffic periodicity information in step 510, can determine whether to update DRX parameters.

If in step 510 the RAN performed a DRX parameter update based on the jitter range and traffic periodicity information transmitted from the PCF through AMF, in step 511, the RAN transmits the updated DRX parameter information to the UE through an RRC Connection Reconfiguration request message. You can. The UE that has received the updated DRX parameters can perform an RRC connection reconfiguration operation based on the information and use the XR service based on the updated DRX parameter information.

In step 513a, the UPF can measure the jitter value of the N6 section. UPF can calculate the jitter of the N6 section using the timestamp in the header of the RTP packet delivered through AS and the difference between received packets.

In step 513b, the UPF may measure the N3 packet delay value between RANs. If the UPF and RAN are time synchronized, the UPF can measure the packet transmission delay of the N3 section using the QoS monitoring-related parameter information for 5GC measurement received in step 507. In a temporally synchronized QoS monitoring service, the UPF can transmit the packet by marking the packet transmission time (T1) from the UPF to the RAN in the GTP-U header to measure the packet transmission delay.

The RAN can mark the packet reception time (T2) received from the UPF and transmit it again through the uplink packet along with the uplink packet transmission time (T3). At this time, in addition to T3 and T2-T1 times, the RAN can separately perform the packet transmission delay (RAN side DL/UL packet delay) between the RAN and the UE and transmit it to the UPF including this. Through the above process, UPF can calculate the transmission delay between UPF and UE (T4 - T3 + T2 - T1 + RAN side DL/UL packet delay) based on the above information.

In step 513c, the UPF may measure the jitter value of the N6 section in step 513a and then transmit it to the PCF based on reporting conditions. Additionally, to measure jitter within 5GC, the packet delay value measured in step 513b can be transmitted to the PCF based on the reporting condition in the QoS monitoring parameters.

In step 514, the UPF performs a QoS monitoring service for jitter measurement in 5GC and transmits a QoS monitoring report including packet transmission delay values measured and jitter measurement values in the N6 section to the SMF through an N4 session reporting message.

In step 515, the SMF may transmit the QoS monitoring report received in step 514 and reporting values including the jitter measurement value of the N6 section to the PCF using a session management rule control update (Npcf_SMPolicyControl_Update) request message.

In step 516, the PCF may calculate the jitter of each section based on the jitter-related QoS monitoring report received in the above step and the report information including the jitter measurement value of the N6 section. PCF can calculate the average value of jitter by calculating the jitter value over a certain period of time in order to use the statistical characteristics of the sections of each network, and use this to set the jitter range.

At this time, the jitter range value can be set to the time before the statistical jitter value (onDurationTimer - statistics jitter value) and the time behind the statistical jitter (onDurationTimer + statistics jitter value) based on the DRX cycle. The jitter range reporting condition can be received through the jitter range reporting condition in the battery saving support information received in step 504, and the PCF determines the jitter threshold value based on the jitter value using the reporting condition and statistical characteristics. If it exceeds, it can be decided whether to transmit the exceeded statistical jitter value to the RAN (jitter range reporting code).

When calculating the statistical jitter value of an abnormal jitter measurement section, the conditions for statistical jitter measurement (statistical jitter calculation method/formula, statistical jitter measurement cycle, etc.) are delivered to the PCF through reporting conditions, and based on this, the statistical jitter value of each network section is transmitted to the PCF. It can be used when calculating jitter.

In step 517, the PCF determines the reporting of the jitter range based on the reporting conditions for updating the jitter range determined in step 516, and when the DRX parameter update is determined, the PCF transmits the updated jitter range information to the N1N2 message ( Namf_Communication_N1N2MessageTransfer) It can be transmitted to AMF through a request message.

In step 518, the AMF may transmit the updated jitter range information for updating the DRX parameters in step 517 to the RAN through an N2 message. The RAN, which has received the updated jitter range information in the above step, can determine whether to update the DRX parameters.

If in step 518 the RAN decides to perform a DRX parameter update based on the updated jitter range information based on statistical jitter information considering the jitter of the network transmitted from the PCF through AMF, in step 519 the RAN updates the updated DRX Parameter information can be delivered to the UE through an RRC Connection Reconfiguration request message. The UE that has received the updated DRX parameters can perform an RRC connection reconfiguration operation based on the information and use the XR service based on the updated DRX parameter information.

FIGS. 6A and 6B are flowcharts showing a process in which DRX parameters are updated based on updated jitter range information in a wireless communication system according to another embodiment of the present disclosure.

Referring to FIGS. 6A and 6B, the AF may determine policy implementation for providing and requesting a battery saving service considering N6 jitter network jitter in the XR service. To this end, AF delivers N6 jitter-related requirements and information for 5GC jitter measurement to PCF, and through PCC rule updates, UPF performs N6 jitter monitoring operation to measure jitter values of packets coming from AS and 5GC using QoS monitoring service. Packet delay measurements can be performed to obtain jitter information.

UPF transmits the corresponding 5GC packet delay value and N6 jitter monitoring reporting value to NWDAF through SMF, and NWDAF determines whether to update the jitter range based on the 5GC packet delay value and N6 jitter value reported by UPF and sets this as the jitter range reporting condition. When satisfied, this can be notified to the RAN through the PCF. RAN can perform DRX parameter update based on the updated jitter range information and send an RRC Connection reconfiguration message to the UE to use it for XR service based on the updated DRX information.

In step 601, the AF generates jitter range information and traffic periodicity information according to the user's selection, service provider's policy, or terminal status (e.g., battery level and/or terminal type). You can use this to decide whether to support battery saving service.

Here, the traffic periodicity information is information indicating the interval between two burst packets. For example, in the case of video traffic, it may indicate the interval between each frame. In the case of video traffic, periodicity information can be defined based on the frame rate value indicating the frame interval of the video traffic. In the XR service, one frame can consist of multiple packets, and when a group of packets is defined as a PDU set, the periodicity information of traffic in the XR service can be defined as the interval between PDU sets (packet groups). .

In the corresponding XR service, the periodicity information of traffic can be transmitted as a periodicity value in TSCAI information or separately transmitted to the PCF through battery saving assistance information. Jitter range information can be used to determine the jitter range to be used for the battery saving service by using the difference between packet transmission delay values measured through the QoS monitoring service to minimize jitter of 5GC and the jitter values of the N6 section between UPF and AS.

In steps 602 and 603, the AF may transmit battery saving support information for the battery saving service using the jitter range and traffic periodicity information generated based on the decision in step 601 to the PCF through the NEF. Battery saving support information for the battery saving service using the generated jitter range and traffic periodicity information may be included in the AF session-related QoS requirements (AFsessionWithQoS) message transmitted from the AF entity to the NEF entity.

Battery saving assistance information is related to jitter range, including Battery saving support indication, packet periodicity information, and policy and requirement information for 5GC and N6 jitter measurements in UPF. Information (jitter range requirement) and, additionally, End of burst information indicating that reception of packets of the PDU set has been completed based on information on the last packet of the PDU set for each frame may be included.

Policy and requirement information for jitter measurement includes information on whether 5GC (QoS monitoring supported or not indication for 5GC jitter measurement) and N6 jitter will be additionally measured and supported in the battery saving service (N6 jitter supported or not indication), QoS monitoring and N6 jitter measurement and reporting period measured by UPF, characteristic values for jitter measurement (e.g. RTP timestamp sampling rate), and jitter range considering the characteristics of traffic services (Long jitter for dynamic contents or Short jitter for static contetns), Default jitter range for starting battery saving service using jitter range and packet periodicity information, threshold to determine whether to report the jitter range based on measured jitter ( jitter range threshold), jitter range reporting frequency (jitter range reporting frequency), whether to report immediately when the jitter range exceeds the threshold or determine whether the threshold has been exceeded based on statistical characteristics; Jitter range reporting condition, which includes conditions for determining when a jitter value is measured and excluding statistical calculation of the exceptional jitter value, and determining whether to calculate the jitter and determine the threshold based on the above information. It may include at least one of the type of network entity performing (NF for statistics jitter calculation and update / resporing decision based on jitter range reporting condition) information.

According to one embodiment, if 5GC and additional N6 jitter are not used or supported in a battery saving service using jitter, the jitter range may be determined using the jitter value based on the QoS monitoring service. According to one embodiment, if the system supports the N6 jitter utilization requirements and UPF, the jitter range information can be determined by additionally considering the jitter of the N6 section in addition to the basic jitter information between the UPF and the UE.

According to one embodiment, when the jitter measurement value exceeds the threshold according to the jitter reporting cycle value, if it is reported immediately (reporting based on Instantaneous jitter value), this is immediately transmitted to the RAN to adjust the jitter value considering the jitter of the actual network. By analyzing the statistical characteristic value of the jitter measurement value, it is determined whether the jitter threshold is exceeded through reporting based on statistical jitter value, and based on this, it is set whether to transmit the updated jitter range to the RAN. It can be.

In step 604, the NEF may transmit jitter assistance information (Battery saving assistance information) to be used when supporting a battery saving service considering the transmission range and traffic cycle from the AF to the PCF entity using a PolicyAuthorization message.

According to one embodiment, a separate policy authorization service process is not performed through the existing XR service and is delivered through a policy authorization creation message (Npcf_PolicyAuthorization_Create) request or, if there is an existing service process, a policy authorization update (Npcf_PolicyAuthorization_Update) request message. The received battery saving service support information related to the XR service may be transmitted to the PCF entity.

According to one embodiment, in order to receive additional service-related reporting, the corresponding event reporting may be requested through a policy authorization subscription (Npcf_PolicyAuthorization_Subscribe) message in order to receive messages related to jitter-related reporting events occurring in the PCF. To this end, in order to receive reporting related to jitter support information in the PCF, a new event ID related to jitter range reporting (e.g. Jitter range reporting based on jitter measurement) will be defined considering packet delay-based jitter measured through QoS monitoring and jitter in the N6 section. You can.

In step 605, the PCF may perform a PCC rule update based on the requirements for jitter range measurement using the N6 and 5GC-based jitter information received in the above step.

According to one embodiment, in addition to the existing QoS monitoring request for jitter monitoring and measurement within 5GC, separate QoS rule data (qos monitoring id ('qmid'), Reporting Frequency ('repFreqs'), reporting for jitter monitoring and measurement A separate QoS monitoring request can be performed through period ('repPeriod') etc. in QOSMonitoringData).

According to one embodiment, when updating QoS parameters for jitter monitoring measurement in the 5GC, the packet generation cycle for QoS monitoring may be updated based on the N6 jitter measurement cycle for N6 jitter measurement. According to one embodiment, separate from the QoS monitoring parameters and service ID of the service to minimize jitter of 5GC, a QoS monitoring service for measuring jitter within 5GC for battery saving may be additionally requested.

According to one embodiment, when measuring the jitter of 5GC using a separate QoS monitoring service for battery saving as described above, whenever a QoS monitoring-related packet delay measurement occurs to measure the jitter range, it is measured by NWDAF through SMF. NWDAF can measure 5GC-related jitter-related information.

According to one embodiment, in order to measure jitter in the N6 section, a PCC rule update for separate rules and policies for N6 jitter measurement is required in the UPF based on the jitter range requirements within the battery saving support information received through step 604. It can be done. For example, when the XR service is provided through RTP packets, UPF can measure jitter using the timestamp in the RTP header. At this time, because the RTP timestamp value has a random value, the jitter value is calculated using the amount of change between the timestamp values of the first or last packets in each measurement cycle based on the sampling rate information within the jitter range requirement. You can.

Since the methods for measuring jitter in the 5GC and N6 sections are different as described above, the PCF receives jitter measurement parameters through step 604 to calculate the jitter range value in the battery saving support information, and The PCC rules can be updated based on related information for jitter measurement (Modified QoS monitoring parameter for 5GC jitter measurement, N6 jitter calculation related parameter for N6 jitter measurement).

In step 606, the PCF sends the updated PCC rules, including the policy and operation rules for N6 jitter measurement determined in step 605 and QoS monitoring parameter information for 5GC jitter measurement, through a session policy adjustment update notification (Npcf_SMPolicyControl_UpdateNotify) request message. It can be delivered via SMF.

In step 607, the PCF uses NWDAF to calculate statistical characteristics of jitter information on the network based on the 5GC packet delay value and N6 jitter value measured in UPF, determines the calculation of the statistical jitter information value, and updates the corresponding value. In order to receive the jitter range, the Nnwdaf_AnalyticsSubscription_Subscribe message is sent to NWDAF to calculate the statistical jitter information value, or when a reporting event occurs because the statistical jitter information value exceeds the jitter range threshold, information about this can be received. .

In step 608, the NWDAF transmits the Nsmf_EventExposer_Subscribe message to the SMF to collect data such as the packet delay reporting value and N6 jitter value of the 5GC through the SMF for statistical jitter analysis using the network-side jitter value requested in step 607. If reporting values are delivered, transmission of the data can be requested.

In steps 609 and 610, the SMF receives the updated PCC rules including jitter-related information and rules for measuring the jitter range to support the battery saving service received through the PCF in the above steps and modifies the N4 session (N4 session) Modification) can be delivered to UPF through a request message. In the request message, QoS monitoring related parameter information for 5GC jitter measurement for jitter range measurement according to AF request (Modified QoS monitoring parameter for 5GC jitter measurement) and related parameter for jitter measurement in N6 section (N6 jitter calculation related parameter for To receive reporting of 5GC jitter value or packet delay value based on the QoS monitoring service and jitter monitoring performance results of N6 section from UPF through SRR (Session Reporting Rule) based on updated PCC rules reflecting N6 jitter measurement) Information can be conveyed.

In step 611, the PCF determines the PCC rule update for the battery saving service in step 605 and then updates the DRX parameters received in step 604 based on the network characteristics (e.g. jitter range) and traffic characteristics (Preodicity) received from AF. The default jitter range and periodicity information in the battery saving support information can be transmitted to AMF through the N1N2 message transfer (Namf_Communication_N1N2MessageTransfer) request message.

In step 612, the AMF may transmit to the RAN through an N2 message for DRX parameter update applying the network (e.g. jitter range) and traffic characteristics (preodicity) received in step 611. The RAN, which has received the jitter range and traffic periodicity information in the above step, can determine whether to update DRX parameters.

If in step 612 the RAN performed a DRX parameter update based on the jitter range and traffic periodicity information transmitted from the PCF through AMF, in step 613, the RAN transmits the updated DRX parameter information to the UE through an RRC Connection Reconfiguration request message. You can. The UE that has received the updated DRX parameters can perform an RRC connection reconfiguration operation based on the information and use the XR service based on the updated DRX parameter information.

In step 615a, the UPF can measure the jitter value of the N6 section. UPF can calculate the jitter of the N6 section using the timestamp in the header of the RTP packet delivered through AS and the difference between received packets.

In step 615b, the UPF may measure the N3 packet delay value between RANs. If the UPF and RAN are time synchronized, the UPF can measure packet transmission delay in the N3 section using the QoS monitoring-related parameter information for 5GC measurement received at 507. In a temporally synchronized QoS monitoring service, the UPF can transmit the packet to the RAN by marking the packet transmission time (T1) from the UPF to the RAN in the GTP-U header to measure the packet transmission delay.

The RAN can mark the packet reception time (T2) received from the UPF and transmit it again through the uplink packet along with the uplink packet transmission time (T3). At this time, in addition to T3 and T2-T1 times, the RAN can separately perform the packet transmission delay (RAN side DL/UL packet delay) between the RAN and the UE and transmit it to the UPF including this. Through the above process, UPF can calculate the transmission delay between UPF and UE (T4 - T3 + T2 - T1 + RAN side DL/UL packet delay) based on the above information.

In step 615c, the UPF may measure the jitter value of the N6 section and then transmit it to the PCF based on reporting conditions. Additionally, to measure jitter within 5GC, the packet delay value measured in step 615b can be determined to be transmitted to the PCF based on the reporting condition in the QoS monitoring parameters.

In step 616, the UPF performs a QoS monitoring service for jitter measurement in 5GC and transmits a QoS monitoring report including packet transmission delay values measured and jitter measurement values in the N6 section to the SMF through an N4 session reporting message.

In step 617, the SMF may transmit the QoS monitoring report received in step 616 and reporting values including the jitter measurement value of the N6 section to the NWDAF using the Nsmf_EventExposer_Notify message.

In step 618, NWDAF may calculate the jitter of each section based on the jitter-related QoS monitoring report received in the above step and the report information including the jitter measurement value of the N6 section. PCF can calculate the average value of jitter by calculating the jitter value over a certain period of time in order to use the statistical characteristics of the sections of each network, and use this to set the jitter range. At this time, the jitter range value can be set to the time before the statistical jitter value (onDurationTimer - statistics jitter value) and the time behind the statistical jitter (onDurationTimer + statistics jitter value) based on the DRX cycle.

The jitter range reporting condition can be received through the jitter range reporting condition in the battery saving support information received in step 604, and the PCF uses the jitter value based on the reporting condition and statistical characteristics to determine the jitter threshold. If the value is exceeded, it can be decided whether to transmit the exceeded statistical jitter value to the PCF (jitter range reporting condition).

When calculating the statistical jitter value of an abnormal jitter measurement section, conditions for statistical jitter measurement (statistical jitter calculation method/formula, statistical jitter measurement cycle, etc.) are delivered to NWDAF through reporting conditions, and based on this, the It can be used when calculating statistical jitter.

If statistical jitter characteristics are calculated through step 618 and reporting is determined based on jitter range update reporting conditions, in step 619, NWDAF uses the Nnwdaf_AnalyticsSubscription_Notify message to transmit the updated jitter range reporting value to PCF.

The PCF, which received the updated jitter range value of the updated jitter range from NWDAF through steps 618 and 619, receives the updated jitter range information in step 620 to request a DRX parameter update based on the information. It can be delivered to AMF through the N1N2 Message Transfer (Namf_Communication_N1N2MessageTransfer) request message.

In step 621, the AMF may transmit the updated jitter range information for updating the DRX parameters in step 620 to the RAN through an N2 message.

In step 622, the RAN that has received the updated jitter range information may determine whether to update the DRX parameters.

If in step 622 the RAN decides to perform a DRX parameter update based on the updated jitter range information based on statistical jitter information considering the jitter of the network transmitted by NWDAF through AMF and PCF, in step 623, the RAN performs the update. The DRX parameter information can be delivered to the UE through an RRC Connection Reconfiguration request message. The UE that has received the updated DRX parameters can perform an RRC connection reconfiguration operation based on the information and use the XR service based on the updated DRX parameter information.

Figure 7 shows the structure of a terminal according to an embodiment of the present disclosure.

The terminal in FIG. 7 may be any one of the terminals (or UEs) shown in FIGS. 1 to 6B. Referring to FIG. 7, the terminal may include a transceiver 710, a control unit 720, and a storage unit 730. In the present disclosure, the control unit may be defined as a circuit or application-specific integrated circuit or at least one processor.

The transceiver 710 can transmit and receive signals with a base station or network entity, and may also be called a transceiver.

The control unit 720 can control the overall operation of the terminal according to the embodiment proposed in this disclosure, and may also be called a processor. For example, the control unit 720 may control signal flow between each block to perform operations according to the flowchart described above. Specifically, the control unit 720 may control, for example, the operation of the terminal (or UE) described with reference to FIGS. 1 to 6B.

Figure 8 shows the structure of a network device according to an embodiment of the present disclosure.

The network device in FIG. 8 may be either a base station (or RAN; or NG-RAN) or a network entity shown in FIGS. 1 to 6B. The network entity may be implemented as any one of AMF, UFP, SMF, PCF, NWDAF, NEF, and AF.

Referring to FIG. 8, the network device may include a transceiver 810, a control unit 820, and a storage unit 830. In the present disclosure, the control unit may be defined as a circuit or application-specific integrated circuit or at least one processor.

The transmitting and receiving unit 810 can transmit and receive signals with a terminal or other entity, and may also be called a transceiver.

The control unit 820 can control the overall operation of the network device according to the embodiment proposed in this disclosure, and may also be called a processor. For example, the control unit 820 may control signal flow between each block to perform operations according to the flowchart described above. Specifically, the control unit 820 may control, for example, the operation of a base station (or RAN; or NG-RAN) or network entity described with reference to FIGS. 1 to 6B.

According to an embodiment of the present disclosure, the PCF includes a transmitting and receiving unit 810; and a control unit 820. The control unit 820 may receive a power saving service support indicator, jitter range information, and period information transmitted from AF through NEF. Based on the jitter range information and the period information, the control unit 820 creates a policy and charging control (PCC) rule including a policy for N6 jitter measurement and quality of service (QoS) monitoring parameter information for 5GC jitter measurement. It can be updated. The control unit 820 may control transmission of the updated PCC rule to the SMF so that jitter-related information and rules for jitter range measurement for the power saving service are transmitted to the UPF.

According to one embodiment, the jitter range information is based on the difference between packet transmission delay values measured through a QoS monitoring service to minimize jitter of the 5GC and jitter values of the N6 section between the UPF and AS (application server). PCF, characterized in that it is determined. According to one embodiment, the control unit 820 calculates a statistical jitter range value based on the network measurement information generated by the UPF, and provides the updated jitter range information based on the calculation result using an access and mobility management function (AMF). ) can be controlled to transmit to the base station.

According to an embodiment of the present disclosure, the UPF includes a transceiver 810; and a control unit 820. The control unit 820 may receive updated policy and charging control (PCC) rules including jitter-related information and rules for measuring the jitter range to support the power saving service transmitted from the PCF from the SMF. Based on the updated PCC rule, the control unit 820 checks the timestamp in the header of the RTP (real-time transport protocol) packet delivered through the AS (application server) and determines the time difference between received packets. You can use this to measure the jitter of the N6 section. The control unit 820 may control the jitter measurement value of the N6 section and the packet transmission delay value measured through QoS monitoring service for jitter measurement within 5GC to be transmitted to the SMF.

Meanwhile, the embodiments of the present disclosure disclosed in the specification and drawings are merely provided as specific examples to easily explain the technical content of the present disclosure and aid understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it is obvious to those skilled in the art that other modifications based on the technical idea of the present disclosure can be implemented. Additionally, each embodiment may be operated in combination with each other as needed. Although the present disclosure has been described with reference to example embodiments, various changes and modifications may be suggested to those skilled in the art. This disclosure is intended to cover changes and modifications that fall within the scope of the appended claims. Nothing in the detailed description of this application should be read to imply that any particular element, process, or function is an essential element that must be included within the scope of the claims. The scope of patentable subject matter is defined by the claims.

Claims (12)

In a method of operating a PCF (policy control function) in a wireless communication system,
An operation of receiving a power saving service support indicator, jitter range information, and period information transmitted from an application function (AF) through a network exposure function (NEF);
Based on the jitter range information and the period information, updating a policy and charging control (PCC) rule including a policy for N6 jitter measurement and quality of service (QoS) monitoring parameter information for 5GC jitter measurement; and
An operation of transmitting the updated PCC rules to a session management function (SMF) so that jitter-related information and rules for jitter range measurement for the power saving service are transmitted to a user plane function (UPF). method. According to paragraph 1,
The jitter range information is determined based on the difference between packet transmission delay values measured through a QoS monitoring service to minimize jitter of the 5GC and the jitter values of the N6 section between the UPF and AS (application server). How to. According to paragraph 1,
Calculating a statistical jitter range value based on network measurement information generated from the UPF; and
The method further includes transmitting updated jitter range information based on the calculation result to the base station through an access and mobility management function (AMF). In a method of operating UPF (user plane function) in a wireless communication system,
An operation of receiving updated policy and charging control (PCC) rules including jitter-related information and rules for jitter range measurement to support power saving services transmitted from a policy control function (PCF) from a session management function (SMF);
Based on the updated PCC rules, the timestamp in the header of the RTP (real-time transport protocol) packet delivered through the AS (application server) is checked and the time difference between received packets is used to determine the N6 section. Actions that measure jitter; and
A method comprising transmitting the jitter measurement value of the N6 section and the packet transmission delay value measured through QoS monitoring service for jitter measurement within 5GC to the SMF. According to paragraph 4,
The PCC rule is updated based on jitter range information and period information transmitted from an application function (AF),
The PCC rule includes a policy for measuring the N6 jitter and quality of service (QoS) monitoring parameter information for measuring the 5GC jitter. According to paragraph 4,
A method characterized in that a statistical jitter range value is calculated based on the network measurement information generated by the UPF, and the updated jitter range information is transmitted to the base station based on the calculation result. In PCF (policy control function) in a wireless communication system,
Transmitter and receiver; and
Includes a control unit, the control unit,
Receive power saving service support indicator, jitter range information, and period information transmitted from AF (application function) through NEF (network exposure function),
Based on the jitter range information and the period information, update policy and charging control (PCC) rules including a policy for N6 jitter measurement and QoS (quality of service) monitoring parameter information for 5GC jitter measurement,
A PCF characterized in that it controls transmission of the updated PCC rules to a session management function (SMF) so that jitter-related information and rules for jitter range measurement are transmitted to a user plane function (UPF) for the power saving service. In clause 7,
The jitter range information is determined based on the difference between packet transmission delay values measured through a QoS monitoring service to minimize jitter of the 5GC and the jitter values of the N6 section between the UPF and AS (application server). PCF that does. The method of claim 7, wherein the control unit,
Calculate a statistical jitter range value based on the network measurement information generated by the UPF,
A PCF that controls transmission of updated jitter range information based on the calculation results to the base station through an access and mobility management function (AMF). In UPF (user plane function) in a wireless communication system,
Transmitter and receiver; and
Includes a control unit, the control unit,
Receive updated policy and charging control (PCC) rules including jitter-related information and rules for measuring jitter range to support power saving service transmitted from policy control function (PCF) from session management function (SMF),
Based on the updated PCC rules, the timestamp in the header of the RTP (real-time transport protocol) packet delivered through the AS (application server) is checked and the time difference between received packets is used to determine the N6 section. measure jitter,
A UPF characterized by controlling to transmit to the SMF the jitter measurement value of the N6 section and the packet transmission delay value measured through QoS monitoring service performance for jitter measurement within 5GC. According to clause 10,
The PCC rule is updated based on jitter range information and period information transmitted from an application function (AF),
The PCC rule includes a policy for measuring the N6 jitter and quality of service (QoS) monitoring parameter information for measuring the 5GC jitter. According to clause 11,
A UPF, characterized in that a statistical jitter range value is calculated based on network measurement information generated by the UPF, and the updated jitter range information is transmitted to the base station based on the calculation result.

Images