WO2022098053A1 - Qos 플로우에 관련된 측정 - Google Patents
Qos 플로우에 관련된 측정 Download PDFInfo
- Publication number
- WO2022098053A1 WO2022098053A1 PCT/KR2021/015697 KR2021015697W WO2022098053A1 WO 2022098053 A1 WO2022098053 A1 WO 2022098053A1 KR 2021015697 W KR2021015697 W KR 2021015697W WO 2022098053 A1 WO2022098053 A1 WO 2022098053A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- qos flow
- access
- measurement
- upf
- qos
- Prior art date
Links
- 238000005259 measurement Methods 0.000 title claims abstract description 321
- 238000000034 method Methods 0.000 claims abstract description 163
- 238000004891 communication Methods 0.000 claims abstract description 77
- 230000006870 function Effects 0.000 claims description 113
- 230000015654 memory Effects 0.000 claims description 56
- 238000013507 mapping Methods 0.000 claims description 40
- 230000004044 response Effects 0.000 claims description 36
- 238000010295 mobile communication Methods 0.000 claims description 14
- 238000003860 storage Methods 0.000 claims description 13
- 239000010410 layer Substances 0.000 description 62
- 238000005516 engineering process Methods 0.000 description 34
- 238000010586 diagram Methods 0.000 description 25
- 238000007726 management method Methods 0.000 description 22
- 238000012545 processing Methods 0.000 description 22
- 230000011664 signaling Effects 0.000 description 21
- 230000008569 process Effects 0.000 description 19
- 230000005540 biological transmission Effects 0.000 description 9
- 230000004048 modification Effects 0.000 description 9
- 238000012986 modification Methods 0.000 description 9
- 238000013473 artificial intelligence Methods 0.000 description 8
- 230000000694 effects Effects 0.000 description 8
- 238000001994 activation Methods 0.000 description 7
- 230000004913 activation Effects 0.000 description 5
- 230000003190 augmentative effect Effects 0.000 description 5
- 230000001419 dependent effect Effects 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 5
- 238000012546 transfer Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 4
- 230000004224 protection Effects 0.000 description 4
- 230000007704 transition Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000009826 distribution Methods 0.000 description 3
- 230000007774 longterm Effects 0.000 description 3
- 238000010801 machine learning Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 239000002699 waste material Substances 0.000 description 3
- 241000700159 Rattus Species 0.000 description 2
- 208000027418 Wounds and injury Diseases 0.000 description 2
- 230000000903 blocking effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000002485 combustion reaction Methods 0.000 description 2
- 230000000295 complement effect Effects 0.000 description 2
- 230000006378 damage Effects 0.000 description 2
- 230000009849 deactivation Effects 0.000 description 2
- 230000036541 health Effects 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 208000014674 injury Diseases 0.000 description 2
- 238000013468 resource allocation Methods 0.000 description 2
- 241000760358 Enodes Species 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 230000003466 anti-cipated effect Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000004888 barrier function Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000036772 blood pressure Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 238000012517 data analytics Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000004069 differentiation Effects 0.000 description 1
- 201000010099 disease Diseases 0.000 description 1
- 208000037265 diseases, disorders, signs and symptoms Diseases 0.000 description 1
- 230000005611 electricity Effects 0.000 description 1
- 238000005265 energy consumption Methods 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 239000000446 fuel Substances 0.000 description 1
- 230000008571 general function Effects 0.000 description 1
- 238000010438 heat treatment Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 239000002346 layers by function Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000002156 mixing Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000035935 pregnancy Effects 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 230000008054 signal transmission Effects 0.000 description 1
- 239000010454 slate Substances 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 230000003595 spectral effect Effects 0.000 description 1
- 230000005641 tunneling Effects 0.000 description 1
- 238000005406 washing Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
- H04W28/0236—Traffic management, e.g. flow control or congestion control based on communication conditions radio quality, e.g. interference, losses or delay
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/08—Testing, supervising or monitoring using real traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0823—Errors, e.g. transmission errors
- H04L43/0829—Packet loss
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/12—Shortest path evaluation
- H04L45/121—Shortest path evaluation by minimising delays
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/12—Shortest path evaluation
- H04L45/123—Evaluation of link metrics
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/70—Routing based on monitoring results
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/24—Multipath
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/52—Multiprotocol routers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
Definitions
- This specification relates to mobile communication.
- 3rd generation partnership project (3GPP) long-term evolution (LTE) is a technology that enables high-speed packet communications. Many initiatives have been proposed for LTE goals, including those aimed at reducing user and provider costs, improving service quality, and expanding and improving coverage and system capacity. 3GPP LTE requires lower cost per bit, improved service availability, flexible use of frequency bands, simple structure, open interface, and appropriate power consumption of the terminal as upper-level requirements.
- NR New Radio
- 3GPP has successfully launched a new Radio Access Technology (RAT) that meets both urgent market needs and long-term requirements set out in the International Mobile Telecommunications (ITU-R) international mobile telecommunications (IMT)-2020 process.
- RAT Radio Access Technology
- ITU-R International Mobile Telecommunications
- IMT international mobile telecommunications
- the technical components needed to standardize should be identified and developed.
- NR must be able to use a spectral band in the range of at least 100 GHz that can be used for wireless communications even further into the future.
- NR aims to be a single technology framework that covers all usage scenarios, requirements and deployment scenarios, including enhanced mobile broadband (eMBB), massive machine-type-communications (mMTC), ultra-reliable and low latency communications (URLLC), and more. do. NR may be forward compatible in nature.
- eMBB enhanced mobile broadband
- mMTC massive machine-type-communications
- URLLC ultra-reliable and low latency communications
- NR may be forward compatible in nature.
- a Multi-Access (MA) Protocol Data Unit (PDU) session was introduced in 5G.
- multiple Quality of Service (QoS) Flow may be used.
- QoS Quality of Service
- measurements for multiple QoS flows may be performed.
- a method for efficiently performing measurement of multiple QoS flows has not been discussed in the prior art.
- Multiple QoS Flow may be mapped to one radio resource (eg, radio bearer).
- radio resource eg, radio bearer
- measurement is performed for each QoS Flow included in the Multiple QoS Flow, which causes a problem in that radio resources and computing resources are wasted.
- PLR packet loss ratio
- an object of the present disclosure is to propose a method for solving the above-described problems.
- one disclosure of the present specification provides a method for a UE to perform measurement related communication.
- the method includes performing an access measurement for a first QoS flow; determining that an access measure for the first QoS flow applies to a second QoS flow; and determining not to perform access measurement for the second QoS flow.
- the UE includes at least one processor; and at least one memory for storing instructions and operably electrically connectable with the at least one processor, wherein the operations performed based on the instructions being executed by the at least one processor include: a first performing access measurements for QoS flows; determining that an access measure for the first QoS flow applies to a second QoS flow; and determining not to perform access measurement for the second QoS flow.
- the apparatus includes at least one processor; and at least one memory for storing instructions and operably electrically connectable with the at least one processor, wherein the operations performed based on the instructions being executed by the at least one processor include: a first performing access measurements for QoS flows; determining that an access measure for the first QoS flow applies to a second QoS flow; and determining not to perform access measurement for the second QoS flow.
- one disclosure of the present specification provides a non-transitory computer-readable storage medium recording instructions.
- the instructions when executed by one or more processors, cause the one or more processors to: perform an access measurement for a first QoS flow; determining that an access measure for the first QoS flow applies to a second QoS flow; and determining not to perform access measurement for the second QoS flow.
- one disclosure of the present specification provides a method for a UPF node to perform measurement-related communication.
- the method includes performing an access measurement for a first QoS flow; determining that an access measure for the first QoS flow applies to a second QoS flow; and determining not to perform access measurement for the second QoS flow.
- the UPF node includes at least one processor; and at least one memory for storing instructions and operably electrically connectable with the at least one processor, wherein the operations performed based on the instructions being executed by the at least one processor include: a first performing access measurements for QoS flows; determining that an access measure for the first QoS flow applies to a second QoS flow; and determining not to perform access measurement for the second QoS flow.
- FIG. 1 shows an example of a communication system to which an implementation of the present specification is applied.
- FIG. 2 shows an example of a wireless device to which the implementation of the present specification is applied.
- FIG 3 shows an example of a wireless device to which the implementation of the present specification is applied.
- FIG 4 shows an example of a network node to which the implementation of the present specification is applied.
- 5 shows an example of a 5G system architecture to which the implementation of the present specification is applied.
- FIG. 6 is another exemplary diagram showing the structure of a radio interface protocol (Radio Interface Protocol) between the UE and the gNB.
- Radio Interface Protocol Radio Interface Protocol
- FIG. 9 is a diagram illustrating an example of a steering function of a UE.
- FIG 10 shows an example of the conventional RTT measurement and the improved RTT measurement.
- 11 shows an example of packet loss ratio measurement.
- 12A and 12B show a first example of an operation according to a seventh example of the disclosure of the present specification.
- 13A and 13B show a second example of an operation according to a seventh example of the disclosure of the present specification.
- multiple access systems include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, a system, and a single SC-FDMA (single) system. It includes a carrier frequency division multiple access) system, and a multicarrier frequency division multiple access (MC-FDMA) system.
- CDMA may be implemented over a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000.
- TDMA may be implemented through a radio technology such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE).
- GSM global system for mobile communications
- GPRS general packet radio service
- EDGE enhanced data rates for GSM evolution
- OFDMA may be implemented through a wireless technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or E-UTRA (evolved UTRA).
- IEEE Institute of Electrical and Electronics Engineers
- Wi-Fi Wi-Fi
- WiMAX WiMAX
- IEEE 802.20 IEEE 802.20
- E-UTRA evolved UTRA
- UTRA is part of the universal mobile telecommunications system (UMTS).
- 3rd generation partnership project (3GPP) long-term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA.
- 3GPP LTE uses OFDMA in downlink (DL) and SC-FDMA in uplink (UL).
- Evolution of 3GPP LTE includes LTE-A (advanced), LTE-A Pro, and/or 5G NR (new radio).
- the implementation of the present specification is mainly described in relation to a 3GPP-based wireless communication system.
- the technical characteristics of the present specification are not limited thereto.
- the following detailed description is provided based on a mobile communication system corresponding to the 3GPP-based wireless communication system, but aspects of the present specification that are not limited to the 3GPP-based wireless communication system may be applied to other mobile communication systems.
- a or B (A or B) may mean “only A”, “only B” or “both A and B”.
- a or B (A or B)” may be interpreted as “A and/or B (A and/or B)”.
- A, B or C(A, B or C) herein means “only A”, “only B”, “only C”, or “any and any combination of A, B and C ( any combination of A, B and C)”.
- a slash (/) or a comma (comma) used herein may mean “and/or”.
- A/B may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”.
- A, B, C may mean “A, B, or C”.
- At least one of A and B may mean “only A”, “only B”, or “both A and B”.
- the expression “at least one of A or B” or “at least one of A and/or B” means “A and can be construed the same as “at least one of A and B”.
- “at least one of A, B and C” means “only A”, “only B”, “only C”, or “A, B and C” Any combination of A, B and C”.
- “at least one of A, B or C” or “at least one of A, B and/or C” means It may mean “at least one of A, B and C”.
- parentheses used herein may mean “for example”. Specifically, when displayed as “control information (PDCCH)”, “PDCCH” may be proposed as an example of “control information”. In other words, “control information” in the present specification is not limited to “PDCCH”, and “PDCCH” may be proposed as an example of “control information”. Also, even when displayed as “control information (ie, PDCCH)”, “PDCCH” may be proposed as an example of “control information”.
- UE user equipment
- ME mobile equipment
- the illustrated UE may be referred to as a terminal, mobile equipment (ME), or the like.
- the UE may be a portable device such as a notebook computer, a mobile phone, a PDA, a smart phone, a multimedia device, or the like, or a non-portable device such as a PC or a vehicle-mounted device.
- the UE is used as an example of a wireless communication device (or a wireless device, or a wireless device) capable of wireless communication.
- An operation performed by the UE may be performed by a wireless communication device.
- a wireless communication device may also be referred to as a wireless device, a wireless device, or the like.
- AMF may mean an AMF node
- SMF may mean an SMF node
- UPF may mean a UPF node.
- a base station generally refers to a fixed station that communicates with a wireless device, and an evolved-NodeB (eNodeB), an evolved-NodeB (eNB), a BTS (Base Transceiver System), an access point ( Access Point), it may be called another term such as gNB (Next generation NodeB).
- eNodeB evolved-NodeB
- eNB evolved-NodeB
- BTS Base Transceiver System
- Access Point Access Point
- gNB Next generation NodeB
- FIG. 1 shows an example of a communication system to which an implementation of the present specification is applied.
- the 5G usage scenario shown in FIG. 1 is only an example, and the technical features of the present specification may be applied to other 5G usage scenarios not shown in FIG. 1 .
- the three main requirements categories for 5G are (1) enhanced mobile broadband (eMBB) category, (2) massive machine type communication (mMTC) category, and (3) ultra-reliable, low-latency communication. (URLLC; ultra-reliable and low latency communications) category.
- eMBB enhanced mobile broadband
- mMTC massive machine type communication
- URLLC ultra-reliable, low-latency communications
- Partial use cases may require multiple categories for optimization, while other use cases may focus on only one key performance indicator (KPI).
- KPI key performance indicator
- eMBB goes far beyond basic mobile Internet access and covers rich interactive work and media and entertainment applications in the cloud and augmented reality.
- Data is one of the key drivers of 5G, and dedicated voice services may not be provided for the first time in the 5G era.
- voice processing will be simplified as an application that utilizes the data connection provided by the communication system.
- the main reason for the increase in traffic is the increase in the size of content and the increase in applications that require high data transfer rates.
- streaming services audio and video
- video chat video chat
- mobile Internet access will become more prevalent. Many of these applications require an always-on connection to push real-time information and alerts for users.
- Cloud storage and applications are rapidly increasing in mobile communication platforms and can be applied to both work and entertainment.
- Cloud storage is a special use case that accelerates the increase in uplink data transfer rates.
- 5G is also used for remote work in the cloud. When using tactile interfaces, 5G requires much lower end-to-end latency to maintain a good user experience.
- entertainment such as cloud gaming and video streaming is another key factor driving demand for mobile broadband capabilities.
- Smartphones and tablets are essential for entertainment in all places, including in highly mobile environments such as trains, vehicles, and airplanes.
- Another use example is augmented reality for entertainment and information retrieval. In this case, augmented reality requires very low latency and instantaneous data volumes.
- one of the most anticipated 5G use cases relates to the ability to seamlessly connect embedded sensors in all fields, namely mMTC.
- mMTC Internet-of-things
- Industrial IoT is one of the key roles enabling smart cities, asset tracking, smart utilities, agriculture, and security infrastructure through 5G.
- URLLC includes ultra-reliable, low-latency links such as autonomous vehicles and new services that will change the industry through remote control of the main infrastructure. Reliability and latency are essential to controlling smart grids, automating industries, achieving robotics, and controlling and coordinating drones.
- 5G is a means of delivering streaming rated at hundreds of megabits per second at gigabits per second, and can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS). Such high speeds are needed to deliver TVs with resolutions above 4K (6K, 8K and above), as well as virtual and augmented reality.
- Virtual reality (VR) and augmented reality (AR) applications include highly immersive sports games. Certain applications may require special network configuration. For VR games, for example, game companies should integrate core servers into network operators' edge network servers to minimize latency.
- Automobiles are expected to be an important new motivating force in 5G, with many use cases for in-vehicle mobile communications. For example, entertainment for passengers requires broadband mobile communications with high simultaneous capacity and high mobility. This is because users continue to expect high-quality connections in the future, regardless of location and speed.
- Another use case in the automotive sector is AR dashboards.
- the AR dashboard allows the driver to identify an object in a dark place other than the one visible from the front window, and displays the distance to the object and the movement of the object by overlapping information transfer to the driver.
- wireless modules will enable communication between vehicles, information exchange between vehicles and supporting infrastructure, and information exchange between vehicles and other connected devices, such as those accompanied by pedestrians.
- Safety systems lower the risk of accidents by guiding the driver through alternative courses of action to make driving safer.
- the next step will be remotely controlled or autonomous vehicles. This requires very high reliability and very fast communication between different autonomous vehicles and between vehicles and infrastructure. In the future, autonomous vehicles will perform all driving activities and drivers will only focus on traffic unless the vehicle can identify them. The technological requirements of autonomous vehicles require ultra-low latency and ultra-high reliability to increase traffic safety to a level unattainable by humans.
- Smart cities and smart homes/buildings will be embedded in high-density wireless sensor networks.
- a distributed network of intelligent sensors will identify conditions for cost- and energy-efficient maintenance of a city or house.
- a similar configuration can be performed for each household. All temperature sensors, window and heating controllers, burglar alarms and appliances will be connected wirelessly. Many of these sensors typically have low data rates, power, and cost. However, real-time HD video may be required by certain types of devices for monitoring.
- the smart grid uses digital information and communication technology to collect information and connect sensors to operate according to the collected information. As this information can include the behavior of suppliers and consumers, smart grids can improve the distribution of fuels such as electricity in ways such as efficiency, reliability, economics, production sustainability, automation and more.
- the smart grid can also be considered as another low-latency sensor network.
- Mission-critical applications are one of the 5G usage scenarios.
- the health section contains many applications that can benefit from mobile communications.
- the communication system may support telemedicine providing clinical care from a remote location. Telemedicine can help reduce barriers to distance and improve access to health care services that are not consistently available in remote rural areas. Telemedicine is also used in emergency situations to perform critical care and save lives.
- a wireless sensor network based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.
- Wireless and mobile communications are becoming increasingly important in industrial applications. Wiring is expensive to install and maintain. The possibility of replacing cables with reconfigurable radio links is therefore an attractive opportunity for many industries.
- a wireless connection with similar latency, reliability and capacity as a cable must be established and the management of the wireless connection needs to be simplified.
- 5G connection When a 5G connection is required, low latency and very low error probability are new requirements.
- Logistics and freight tracking are important use cases for mobile communications that use location-based information systems to enable inventory and package tracking from anywhere.
- Logistics and freight applications typically require low data rates, but require location information with a wide range and reliability.
- a communication system 1 includes wireless devices 100a to 100f , a base station (BS) 200 , and a network 300 .
- BS base station
- 1 illustrates a 5G network as an example of a network of the communication system 1, the implementation of the present specification is not limited to the 5G system, and may be applied to future communication systems beyond the 5G system.
- Base station 200 and network 300 may be implemented as wireless devices, and certain wireless devices may act as base station/network nodes in relation to other wireless devices.
- the wireless devices 100a to 100f represent devices that perform communication using a radio access technology (RAT) (eg, 5G NR or LTE), and may also be referred to as a communication/wireless/5G device.
- RAT radio access technology
- the wireless devices 100a to 100f are not limited thereto, and the robot 100a, the vehicles 100b-1 and 100b-2, the extended reality (XR) device 100c, the portable device 100d, and home appliances are not limited thereto.
- It may include a product 100e, an IoT device 100f, and an artificial intelligence (AI) device/server 400 .
- a vehicle may include a vehicle with a wireless communication function, an autonomous vehicle, and a vehicle capable of performing vehicle-to-vehicle communication.
- Vehicles may include unmanned aerial vehicles (UAVs) (eg drones).
- XR devices may include AR/VR/mixed reality (MR) devices, and may include head-mounted devices (HMDs) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, and the like. mounted device) or HUD (head-up display).
- Portable devices may include smartphones, smart pads, wearable devices (eg, smart watches or smart glasses), and computers (eg, laptops).
- Home appliances may include TVs, refrigerators, and washing machines.
- IoT devices may include sensors and smart meters.
- the wireless devices 100a to 100f may be referred to as user equipment (UE).
- the UE is, for example, a mobile phone, a smartphone, a notebook computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, an autonomous driving function.
- the UAV may be an aircraft that does not have a person on board and is navigated by a radio control signal.
- the VR device may include a device for realizing an object or a background of a virtual environment.
- the AR device may include a device implemented by connecting an object or background in a virtual world to an object or background in the real world.
- the MR apparatus may include a device implemented by merging the background of an object or virtual world with the background of the object or the real world.
- the hologram device may include a device for realizing a 360-degree stereoscopic image by recording and reproducing stereoscopic information using an interference phenomenon of light generated when two laser lights called a hologram meet.
- the public safety device may include an image relay device or an image device that can be worn on a user's body.
- MTC devices and IoT devices may be devices that do not require direct human intervention or manipulation.
- MTC devices and IoT devices may include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors.
- a medical device may be a device used for the purpose of diagnosing, treating, alleviating, treating, or preventing a disease.
- a medical device may be a device used to diagnose, treat, alleviate, or correct an injury or injury.
- a medical device may be a device used for the purpose of examining, replacing, or modifying structure or function.
- the medical device may be a device used for pregnancy control purposes.
- a medical device may include a device for treatment, a device for driving, an (ex vivo) diagnostic device, a hearing aid, or a device for a procedure.
- a security device may be a device installed to prevent a risk that may occur and to maintain safety.
- the security device may be a camera, closed circuit television (CCTV), recorder or black box.
- the fintech device may be a device capable of providing financial services such as mobile payment.
- a fintech device may include a payment device or a POS system.
- the weather/environment device may include a device for monitoring or predicting the weather/environment.
- the wireless devices 100a to 100f may be connected to the network 300 through the base station 200 .
- AI technology may be applied to the wireless devices 100a to 100f , and the wireless devices 100a to 100f may be connected to the AI server 400 through the network 300 .
- the network 300 may be configured using a 3G network, a 4G (eg, LTE) network, a 5G (eg, NR) network, and a 5G or later network.
- the wireless devices 100a to 100f may communicate with each other through the base station 200/network 300, but communicate directly without going through the base station 200/network 300 (eg, sidelink communication) You may.
- the vehicles 100b-1 and 100b-2 may perform direct communication (eg, vehicle-to-vehicle (V2V)/vehicle-to-everything (V2X) communication).
- the IoT device eg, a sensor
- the IoT device may communicate directly with another IoT device (eg, a sensor) or other wireless devices 100a to 100f.
- Wireless communications/connections 150a , 150b , 150c may be established between the wireless devices 100a - 100f and/or between the wireless devices 100a - 100f and the base station 200 and/or between the base station 200 .
- the wireless communication/connection includes uplink/downlink communication 150a, sidelink communication 150b (or device-to-device (D2D) communication), inter-base station communication 150c (eg, relay, integrated access and backhaul), etc.), and may be established through various RATs (eg, 5G NR).
- the wireless devices 100a to 100f and the base station 200 may transmit/receive wireless signals to/from each other through the wireless communication/connections 150a, 150b, and 150c.
- the wireless communication/connection 150a , 150b , 150c may transmit/receive signals through various physical channels.
- various configuration information setting processes for transmission/reception of radio signals various signal processing processes (eg, channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.), and at least a part of a resource allocation process and the like may be performed.
- AI refers to a field that studies artificial intelligence or methodologies that can make it
- machine learning refers to a field that defines various problems dealt with in the field of artificial intelligence and studies methodologies to solve them.
- Machine learning is also defined as an algorithm that improves the performance of a certain task through constant experience.
- a robot can mean a machine that automatically handles or operates a task given by its own capabilities.
- a robot having a function of recognizing an environment and performing an operation by self-judgment may be referred to as an intelligent robot.
- Robots can be classified into industrial, medical, home, military, etc. depending on the purpose or field of use.
- the robot may be provided with a driving unit including an actuator or a motor to perform various physical operations such as moving the robot joints.
- the movable robot includes a wheel, a brake, a propeller, and the like in the driving unit, and may travel on the ground or fly in the air through the driving unit.
- Autonomous driving refers to a technology that drives itself, and an autonomous driving vehicle refers to a vehicle that runs without or with minimal user manipulation.
- autonomous driving includes technology that maintains a driving lane, technology that automatically adjusts speed such as adaptive cruise control, technology that automatically drives along a set route, and technology that automatically sets a route when a destination is set. Technology, etc. may all be included.
- the vehicle includes a vehicle having only an internal combustion engine, a hybrid vehicle having both an internal combustion engine and an electric motor, and an electric vehicle having only an electric motor, and may include not only automobiles, but also trains, motorcycles, and the like.
- Autonomous vehicles can be viewed as robots with autonomous driving capabilities.
- Expanded reality refers to VR, AR, and MR.
- VR technology provides only CG images of objects or backgrounds in the real world
- AR technology provides virtual CG images on top of images of real objects
- MR technology provides CG by mixing and combining virtual objects with the real world.
- technology MR technology is similar to AR technology in that it shows both real and virtual objects.
- AR technology a virtual object is used in a form that complements a real object
- MR technology a virtual object and a real object are used with equal characteristics.
- NR supports multiple numerology or subcarrier spacing (SCS) to support various 5G services. For example, when SCS is 15 kHz, it supports wide area in traditional cellular band, and when SCS is 30 kHz/60 kHz, dense-urban, lower latency and wider area are supported. It supports a wider carrier bandwidth, and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome the phase noise.
- SCS subcarrier spacing
- the NR frequency band may be defined as two types of frequency ranges (FR1, FR2).
- the numerical value of the frequency range may change.
- the frequency ranges of the two types (FR1, FR2) may be as shown in Table 1 below.
- FR1 may mean "sub 6GHz range”
- FR2 may mean “above 6GHz range”
- mmW millimeter wave
- FR1 may include a band of 410 MHz to 7125 MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, a frequency band of 6GHz (or 5850, 5900, 5925 MHz, etc.) or higher included in FR1 may include an unlicensed band.
- the unlicensed band can be used for a variety of purposes, for example, for communication for vehicles (eg, autonomous driving).
- the wireless communication technology implemented in the wireless device of the present specification may include narrowband IoT (NB-IoT, narrowband IoT) for low-power communication as well as LTE, NR, and 6G.
- NB-IoT narrowband IoT
- the NB-IoT technology may be an example of a low power wide area network (LPWAN) technology, and may be implemented in standards such as LTE Cat NB1 and/or LTE Cat NB2, and is not limited to the above-mentioned name.
- LPWAN low power wide area network
- the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology.
- the LTE-M technology may be an example of an LPWAN technology, and may be called by various names such as enhanced MTC (eMTC).
- eMTC enhanced MTC
- LTE-M technology is 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE MTC , and/or 7) may be implemented in at least one of various standards such as LTE M, and is not limited to the above-described name.
- the wireless communication technology implemented in the wireless device of the present specification may include at least one of ZigBee, Bluetooth, and/or LPWAN in consideration of low-power communication, and limited to the above-mentioned names it is not
- the ZigBee technology can create PAN (personal area networks) related to small/low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.
- FIG. 2 shows an example of a wireless device to which the implementation of the present specification is applied.
- the first wireless device 100 and the second wireless device 200 may transmit/receive radio signals to/from an external device through various RATs (eg, LTE and NR).
- various RATs eg, LTE and NR.
- ⁇ first wireless device 100 and second wireless device 200 ⁇ are ⁇ radio devices 100a to 100f and base station 200 ⁇ in FIG. 1, ⁇ wireless device 100a to 100f ) and wireless devices 100a to 100f ⁇ and/or ⁇ base station 200 and base station 200 ⁇ .
- the first wireless device 100 may include at least one transceiver, such as a transceiver 106 , at least one processing chip, such as a processing chip 101 , and/or one or more antennas 108 .
- Processing chip 101 may include at least one processor, such as processor 102 , and at least one memory, such as memory 104 .
- the memory 104 is exemplarily shown to be included in the processing chip 101 . Additionally and/or alternatively, the memory 104 may be located external to the processing chip 101 .
- the processor 102 may control the memory 104 and/or the transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. For example, the processor 102 may process information in the memory 104 to generate first information/signal, and transmit a wireless signal including the first information/signal through the transceiver 106 . The processor 102 may receive a radio signal including the second information/signal through the transceiver 106 , and store information obtained by processing the second information/signal in the memory 104 .
- Memory 104 may be operatively coupled to processor 102 .
- Memory 104 may store various types of information and/or instructions.
- the memory 104 may store software code 105 that, when executed by the processor 102 , implements instructions that perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
- the software code 105 may implement instructions that, when executed by the processor 102 , perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
- software code 105 may control processor 102 to perform one or more protocols.
- software code 105 may control processor 102 to perform one or more air interface protocol layers.
- the processor 102 and memory 104 may be part of a communication modem/circuit/chip designed to implement a RAT (eg, LTE or NR).
- the transceiver 106 may be coupled to the processor 102 to transmit and/or receive wireless signals via one or more antennas 108 .
- Each transceiver 106 may include a transmitter and/or a receiver.
- the transceiver 106 may be used interchangeably with a radio frequency (RF) unit.
- the first wireless device 100 may represent a communication modem/circuit/chip.
- the second wireless device 200 may include at least one transceiver, such as a transceiver 206 , at least one processing chip, such as a processing chip 201 , and/or one or more antennas 208 .
- the processing chip 201 may include at least one processor, such as a processor 202 , and at least one memory, such as a memory 204 .
- the memory 204 is exemplarily shown included in the processing chip 201 . Additionally and/or alternatively, the memory 204 may be located external to the processing chip 201 .
- the processor 202 may control the memory 204 and/or the transceiver 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. For example, the processor 202 may process the information in the memory 204 to generate third information/signal, and transmit a wireless signal including the third information/signal through the transceiver 206 . The processor 202 may receive a radio signal including the fourth information/signal through the transceiver 206 , and store information obtained by processing the fourth information/signal in the memory 204 .
- Memory 204 may be operatively coupled to processor 202 .
- Memory 204 may store various types of information and/or instructions.
- the memory 204 may store software code 205 that, when executed by the processor 202 , implements instructions that perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
- software code 205 may implement instructions that, when executed by processor 202 , perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
- software code 205 may control processor 202 to perform one or more protocols.
- software code 205 may control processor 202 to perform one or more air interface protocol layers.
- the processor 202 and the memory 204 may be part of a communication modem/circuit/chip designed to implement a RAT (eg, LTE or NR).
- the transceiver 206 may be coupled to the processor 202 to transmit and/or receive wireless signals via one or more antennas 208 .
- Each transceiver 206 may include a transmitter and/or a receiver.
- the transceiver 206 may be used interchangeably with the RF unit.
- the second wireless device 200 may represent a communication modem/circuit/chip.
- one or more protocol layers may be implemented by one or more processors 102 , 202 .
- the one or more processors 102, 202 may include one or more layers (eg, a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, A functional layer such as a radio resource control (RRC) layer and a service data adaptation protocol (SDAP) layer) may be implemented.
- layers eg, a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, A functional layer such as a radio resource control (RRC) layer and a service data adaptation protocol (SDAP) layer
- PHY physical
- MAC media access control
- RLC radio link control
- PDCP packet data convergence protocol
- RRC radio resource control
- SDAP service data adaptation protocol
- the one or more processors 102, 202 may be configured to perform one or more protocol data units (PDUs or packet data units) and/or one or more service data units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein. unit) can be created.
- One or more processors 102 , 202 may generate messages, control information, data, or information in accordance with the descriptions, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein.
- the one or more processors 102, 202 may configure a signal including a PDU, SDU, message, control information, data or information (eg, a baseband signal) and provide it to one or more transceivers 106 , 206 .
- the one or more processors 102 , 202 may receive signals (eg, baseband signals) from one or more transceivers 106 , 206 , and may be described, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein.
- PDU, SDU, message, control information, data or information may be acquired according to
- One or more processors 102 , 202 may be referred to as controllers, microcontrollers, microprocessors, and/or microcomputers.
- One or more processors 102 , 202 may be implemented by hardware, firmware, software, and/or a combination thereof.
- ASICs application specific integrated circuits
- DSPs digital signal processors
- DSPDs digital signal processing devices
- PLDs programmable logic devices
- FPGAs field programmable gates
- the descriptions, functions, procedures, proposals, methods, and/or flow diagrams disclosed herein may be implemented using firmware and/or software, and the firmware and/or software may be implemented to include modules, procedures, and functions. .
- Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein may be included in one or more processors 102 , 202 , or stored in one or more memories 104 , 204 to provide one It may be driven by the above processors 102 and 202 .
- the descriptions, functions, procedures, proposals, methods, and/or flow diagrams disclosed herein may be implemented using firmware or software in the form of code, instructions, and/or sets of instructions.
- One or more memories 104 , 204 may be coupled with one or more processors 102 , 202 , and may store various forms of data, signals, messages, information, programs, code, instructions, and/or instructions.
- the one or more memories 104 and 204 may include read-only memory (ROM), random access memory (RAM), erasable programmable ROM (EPROM), flash memory, hard drives, registers, cache memory, computer readable storage media and/or these may be composed of a combination of One or more memories 104 , 204 may be located inside and/or external to one or more processors 102 , 202 . Additionally, one or more memories 104 , 204 may be coupled to one or more processors 102 , 202 through various technologies, such as wired or wireless connections.
- the one or more transceivers 106, 206 may transmit user data, control information, wireless signals/channels, etc. referred to in the descriptions, functions, procedures, suggestions, methods, and/or flow charts disclosed herein to one or more other devices. .
- the one or more transceivers 106, 206 may receive user data, control information, radio signals/channels, etc. referred to in the descriptions, functions, procedures, suggestions, methods, and/or flow charts disclosed herein, from one or more other devices. there is.
- one or more transceivers 106 , 206 may be coupled to one or more processors 102 , 202 and may transmit and receive wireless signals.
- one or more processors 102 , 202 may control one or more transceivers 106 , 206 to transmit user data, control information, wireless signals, etc. to one or more other devices.
- one or more processors 102 , 202 may control one or more transceivers 106 , 206 to receive user data, control information, wireless signals, etc. from one or more other devices.
- One or more transceivers 106 , 206 may be coupled to one or more antennas 108 , 208 .
- One or more transceivers 106, 206 may be connected via one or more antennas 108, 208 to user data, control information, radio signals/channels referred to in the descriptions, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein. It may be set to transmit and receive, etc.
- the one or more antennas 108 and 208 may be a plurality of physical antennas or a plurality of logical antennas (eg, antenna ports).
- One or more transceivers are configured to process received user data, control information, radio signals/channels, etc., using one or more processors (102, 202), such as received user data, control information, radio signals/channels, and the like. etc. can be converted from an RF band signal to a baseband signal.
- One or more transceivers 106 , 206 may convert user data, control information, radio signals/channels, etc. processed using one or more processors 102 , 202 from baseband signals to RF band signals.
- one or more transceivers 106 , 206 may include (analog) oscillators and/or filters.
- one or more transceivers 106, 206 up-convert OFDM baseband signals to OFDM signals via (analog) oscillators and/or filters under the control of one or more processors 102, 202; , an up-converted OFDM signal may be transmitted at a carrier frequency.
- One or more transceivers 106, 206 receive the OFDM signal at the carrier frequency and down-convert the OFDM signal to an OFDM baseband signal through an (analog) oscillator and/or filter under the control of one or more processors 102, 202. can be down-converted.
- the UE may operate as a transmitting device in an uplink (UL) and a receiving device in a downlink (DL).
- the base station may operate as a receiving device in the UL and a transmitting device in the DL.
- a processor 102 coupled to, mounted on, or shipped with the first wireless device 100 may perform UE operations in accordance with implementations of the present disclosure or may configure the transceiver 106 to perform UE operations in accordance with implementations of the present disclosure.
- a processor 202 coupled to, mounted on, or shipped to the second wireless device 200 is configured to perform a base station operation according to an implementation of the present specification or to control the transceiver 206 to perform a base station operation according to an implementation of the present specification. can be
- a base station may be referred to as a Node B (Node B), an eNode B (eNB), or a gNB.
- Node B Node B
- eNB eNode B
- gNB gNode B
- FIG 3 shows an example of a wireless device to which the implementation of the present specification is applied.
- the wireless device may be implemented in various forms according to usage examples/services (refer to FIG. 1 ).
- the wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 , and may be configured by various components, devices/parts and/or modules.
- each wireless device 100 , 200 may include a communication device 110 , a control device 120 , a memory device 130 , and an additional component 140 .
- the communication device 110 may include communication circuitry 112 and a transceiver 114 .
- communication circuitry 112 may include one or more processors 102 , 202 of FIG. 2 and/or one or more memories 104 , 204 of FIG. 2 .
- transceiver 114 may include one or more transceivers 106 , 206 of FIG.
- the control device 120 is electrically connected to the communication device 110 , the memory device 130 , and the additional component 140 , and controls the overall operation of each wireless device 100 , 200 .
- the control device 120 may control the electrical/mechanical operation of each of the wireless devices 100 and 200 based on the program/code/command/information stored in the memory device 130 .
- the control device 120 transmits information stored in the memory device 130 to the outside (eg, other communication devices) via the communication device 110 through a wireless/wired interface, or a communication device ( 110), information received from an external (eg, other communication device) may be stored in the memory device 130 .
- the additional component 140 may be variously configured according to the type of the wireless device 100 or 200 .
- the additional components 140 may include at least one of a power unit/battery, input/output (I/O) devices (eg, audio I/O ports, video I/O ports), drive units, and computing devices.
- I/O input/output
- Wireless devices 100 and 200 include, but are not limited to, robots (100a in FIG. 1 ), vehicles ( 100b-1 and 100b-2 in FIG. 1 ), XR devices ( 100c in FIG. 1 ), and portable devices ( FIG. 1 ). 100d), home appliances (100e in FIG. 1), IoT devices (100f in FIG.
- the wireless devices 100 and 200 may be used in a moving or fixed location according to usage examples/services.
- all of the various components, devices/parts and/or modules of the wireless devices 100 and 200 may be connected to each other via a wired interface, or at least some of them may be wirelessly connected via the communication device 110 .
- the control device 120 and the communication device 110 are connected by wire, and the control device 120 and the first device (eg, 130 and 140 ) are communication devices. It may be connected wirelessly through 110 .
- Each component, device/portion, and/or module within the wireless device 100, 200 may further include one or more elements.
- the control device 120 may be configured by one or more processor sets.
- control device 120 may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphic processing device, and a memory control processor.
- AP application processor
- ECU electronice control unit
- the memory device 130 may be configured by RAM, DRAM, ROM, flash memory, volatile memory, non-volatile memory, and/or a combination thereof.
- UE's shows an example.
- the UE 100 may correspond to the first wireless device 100 of FIG. 2 and/or the wireless device 100 or 200 of FIG. 3 .
- UE 100 includes processor 102 , memory 104 , transceiver 106 , one or more antennas 108 , power management module 110 , battery 112 , display 114 , keypad 116 , SIM a (subscriber identification module) card 118 , a speaker 120 , and a microphone 122 .
- the processor 102 may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
- the processor 102 may be configured to control one or more other components of the UE 100 to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
- a layer of air interface protocol may be implemented in the processor 102 .
- the processor 102 may include an ASIC, other chipset, logic circuitry, and/or data processing device.
- the processor 102 may be an application processor.
- the processor 102 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator).
- DSP digital signal processor
- CPU central processing unit
- GPU graphics processing unit
- modem modulator and demodulator
- Examples of the processor 102 include SNAPDRAGONTM series processors made by Qualcomm®, EXYNOSTM series processors made by Samsung®, A series processors made by Apple®, HELIOTM series processors made by MediaTek®, ATOMTM series processors made by Intel®, or a corresponding next-generation processor. It can be found in the processor.
- the memory 104 is operatively coupled to the processor 102 , and stores various information for operating the processor 102 .
- Memory 104 may include ROM, RAM, flash memory, memory cards, storage media, and/or other storage devices.
- modules eg, procedures, functions, etc.
- Modules may be stored in memory 104 and executed by processor 102 .
- the memory 104 may be implemented within the processor 102 or external to the processor 102 , in which case it may be communicatively coupled with the processor 102 through various methods known in the art.
- the transceiver 106 is operatively coupled with the processor 102 and transmits and/or receives wireless signals.
- the transceiver 106 includes a transmitter and a receiver.
- the transceiver 106 may include baseband circuitry for processing radio frequency signals.
- the transceiver 106 controls one or more antennas 108 to transmit and/or receive wireless signals.
- the power management module 110 manages power of the processor 102 and/or the transceiver 106 .
- the battery 112 supplies power to the power management module 110 .
- the display 114 outputs the result processed by the processor 102 .
- Keypad 116 receives input for use by processor 102 .
- the keypad 116 may be displayed on the display 114 .
- the SIM card 118 is an integrated circuit for securely storing an international mobile subscriber identity (IMSI) and associated keys, and is used to identify and authenticate a subscriber in a mobile phone device such as a mobile phone or computer. You can also store contact information on many SIM cards.
- IMSI international mobile subscriber identity
- the speaker 120 outputs sound related results processed by the processor 102 .
- Microphone 122 receives sound related input for use by processor 102 .
- the 5G system (5GS; 5G system) structure consists of the following network functions (NF; network functions).
- Data Network e.g. operator services, Internet access or third-party services
- 5 shows the 5G system structure of a non-roaming case using a reference point representation that shows how various network functions interact with each other.
- UDSF, NEF and NRF are not described for clarity of the point-to-point diagram. However, all network functions shown can interact with UDSF, UDR, NEF and NRF as needed.
- connection between UDRs and other NFs is not shown in FIG. 5 .
- connection between NWDAF and other NFs is not shown in FIG. 5 .
- the 5G system architecture includes the following reference points.
- - N1 the reference point between the UE and the AMF.
- the reference point between the PCF and the AMF in the roaming scenario, indicates the reference point between the AMF and the PCF of the visited network.
- AF by a third party other than an operator may be connected to 5GC through NEF.
- the air interface protocol is based on the 3GPP radio access network standard.
- the air interface protocol is horizontally composed of a physical layer, a data link layer, and a network layer, and vertically a user plane for data information transmission and control. It is divided into a control plane for signal transmission.
- the protocol layers are L1 (first layer), L2 (second layer), and L3 (third layer) based on the lower three layers of the Open System Interconnection (OSI) reference model widely known in communication systems. ) can be distinguished.
- OSI Open System Interconnection
- the first layer provides an information transfer service using a physical channel.
- the physical layer is connected to an upper medium access control layer through a transport channel, and data between the medium access control layer and the physical layer is transmitted through the transport channel. And, data is transferred between different physical layers, that is, between the physical layers of the transmitting side and the receiving side through a physical channel.
- the second layer includes a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer.
- MAC Medium Access Control
- RLC Radio Link Control
- PDCP Packet Data Convergence Protocol
- the third layer includes radio resource control (hereinafter abbreviated as RRC).
- RRC radio resource control
- the RRC layer is defined only in the control plane and is related to the establishment (establishment), re-establishment (Re-establishment) and release (Release) of radio bearers (Radio Bearer; abbreviated as RB) of logical channels, transport channels and physical channels. responsible for control In this case, the RB means a service provided by the second layer for data transfer between the UE and the E-UTRAN.
- the NAS (Non-Access Stratum) layer performs functions such as connection management (session management) and mobility management (Mobility Management).
- the NAS layer is divided into a NAS entity for MM (Mobility Management) and a NAS entity for SM (session management).
- the NAS entity for MM provides the following general functions.
- NAS procedures related to AMF including the following.
- AMF supports the following functions.
- the NAS entity for SM performs session management between the UE and the SMF.
- SM signaling messages are processed, ie, generated and processed in the NAS-SM layer of the UE and SMF.
- the content of the SM signaling message is not interpreted by the AMF.
- the NAS entity for MM creates a NAS-MM message that derives how and where to forward the SM signaling message with a security header indicating the NAS transmission of the SM signaling, additional information about the receiving NAS-MM.
- the NAS entity for SM Upon reception of SM signaling, the NAS entity for SM performs an integrity check of the NAS-MM message, and interprets additional information to derive a method and a place to derive the SM signaling message.
- the RRC layer, the RLC layer, the MAC layer, and the PHY layer located below the NAS layer are collectively referred to as an access layer (Access Stratum: AS).
- a network system (ie, 5GC) for next-generation mobile communication (ie, 5G) also supports non-3GPP access.
- An example of the non-3GPP access is typically a WLAN access.
- the WLAN access may include both a trusted WLAN and an untrusted WLAN.
- AMF performs registration management (RM: Registration Management) and connection management (CM: Connection Management) for 3GPP access as well as non-3GPP access.
- RM Registration Management
- CM Connection Management
- a Multi-Access (MA) PDU session using both 3GPP access and non-3GPP access may be used.
- the MA PDU session is a PDU session that can be serviced simultaneously with 3GPP access and non-3GPP access using one PDU session.
- the MA PDU session is a session that can be serviced simultaneously with 3GPP access and non-3GPP access using one PDU session.
- the MA PDU session is one PDU session in FIG. 7 and has a separate session tunnel for each access. One is established on 3GPP access, and the other PDU session is established on untrusted non-3GPP access (eg WLAN AN).
- untrusted non-3GPP access eg WLAN AN
- the MA PDU session Since it is one session in the MA-PDU session, the MA PDU session has the following characteristics.
- one PDU type eg, IPv6
- the MA-PDU session enables a multipath data link between the UE and UPF-A. This may be implemented below the IP layer.
- a MA-PDU session may be established through one of the following procedures.
- (ii) may be established through one MA PDU session establishment procedure. That is, the MA PDU session is simultaneously established in two accesses with one session creation request. This is called binding establishment.
- SM Session Management
- a MA PDU session may be established through two separate PDU session establishment procedures. For example, the UE may establish a MA PDU session on 3GPP access, and then perform a PDU session establishment procedure to add non-3GPP access to the MA PDU session created on 3GPP access on non-3GPP access.
- the request type in the establishment request message for adding the second access may be set to "MA PDU Request".
- a MA PDU session may be established for 3GPP access and non-3GPP access at the same time through one procedure.
- One such procedure may be referred to as a MA PDU session establishment procedure by UE request.
- the above procedure may be useful when the UE intends to establish a MA PDU session while the UE is already registered with 5GC through two accesses. Instead of performing two separate PDU session establishment procedures, the UE may establish a MA PDU session by performing one MA PDU session establishment procedure.
- ATSSS Access Traffic Steering, Switching and Splitting
- the ATSSS function may be an optional feature supported by the UE and the 5GC network.
- the ATSSS function may enable a multi-access PDU Connectivity Service.
- the ATSSS function uses one 3GPP access network and one non-3GPP access network simultaneously, and uses two independent N3/N9 tunnels between the PSA and RAN/AN, between the UE and the data network. PDUs can be exchanged.
- the multi-access PDU connection service can be realized by establishing a Multi-Access PDU (MA PDU) Session.
- the MA PDU session may be, for example, a PDU session with user-plane resources in two access networks.
- the UE may request a MA PDU session.
- the UE uses network-provided policies (eg, ATSSS rules) ) and exchange local conditions (eg network interface availability, signal loss conditions, user preferences, etc.).
- network-provided policies eg, ATSSS rules
- local conditions eg network interface availability, signal loss conditions, user preferences, etc.
- the UPF anchor of the MA PDU session applies the network provision policy (eg N4 rule) and feedback information received from the UE through the user plane (eg access network unavailability or availability) to direct downlink traffic to two N3 / N9 tunnel and can decide how to distribute to two access networks.
- the UE sets the ATSSS rule applicable, and local conditions may be taken into account.
- the MA PDU session type may be, for example, one of IPv4, IPv6, IPv4v6, and Ethernet. Unstructured types may not be supported in the current version.
- ATSSS functionality can be supported over any type of access network.
- all types of access networks may include untrusted non-3GPP access networks and trusted non-3GPP access networks, wireline 5G access networks, and the like.
- the ATSSS function may be supported over any type of access network.
- MA PDU sessions can be managed using the session management function with the following additions and modifications:
- the UE may send a PDU session establishment request message including "MA PDU Request" through one of the two accesses.
- the AMF may inform the SMF that the UE is registered via both accesses. Informing the SMF by the AMF may trigger establishment of user-plane resources in both accesses and two N3/N9 tunnels between the PDU session anchor (PSA) and the RAN/AN.
- PSA PDU session anchor
- the UE may transmit a PDU session establishment request message including "MA PDU Request" through one of the two accesses.
- the UE sends a PDU session establishment request message including "MA PDU Request" and the same PDU session ID to the other access can be transmitted via User-plane resources in both accesses and two N3/N9 tunnels between PSA and RAN/AN may be established.
- the UE may transmit a PDU session establishment request message including the "MA PDU Request" indication through the access in which the UE is registered.
- One N3/N9 tunnel between PSA and RAN/AN and user-plane resources in this access may be established.
- the UE may establish user-plane resources in the second access.
- the UE may provide ATSSS capability information of the UE.
- ATSSS capabilities (capabilities) information may include information about the steering mode and steering functionalities supported by the UE.
- the network sends the UE measurement assistance information (Measurement Assistance Information) may be provided to the UE. And, the network may provide one or more ATSSS rules to the UE.
- ATSSS-LL Low Layer
- the UE may support MPTCP functions in any steering mode, may support ATSSS-LL functions only in Active-Standby steering mode, and may accept the network to activate these functions;
- the network provides MPTCP proxy information to the UE, and provides one IP address/prefix for the MA PDU session and two additional IP addresses/prefix called "link-specific multipath" to the UE can be assigned to Additionally, the network may provide the UE with UE measurement assistance information and provide the UE with one or more ATSSS rules, including ATSSS rules for non-MPTCP traffic.
- ATSSS rules for non-MPTCP traffic can use the ATSSS-LL function and Active-Standby steering mode to indicate how non-MPTCP traffic is transmitted over 3GPP access and non-3GPP access in the uplink direction.
- the network sends MPTCP proxy information to the UE can provide
- the network may allocate one IP address/prefix for the MA PDU session and two additional IP addresses/prefix called "link-specific multipath" to the UE.
- the network may provide UE measurement assistance information and one or more ATSSS rules to the UE.
- S-NSSAI shall be allowed in both accesses. Otherwise, the MA PDU session may not be established.
- the SMF may determine ATSSS capabilities provided by the UE and ATSSS capabilities supported for the MA PDU session based on the DNN configuration of the SMF. SMF can perform the following actions:
- the MA PDU session is (1) MPTCP and ATSSS-LL available for all steering modes in downlink, (2) uplink MPTCP and ATSSS-LL may be enabled in Active-Standby mode; or
- MA PDU session is MPTCP and ATSSS-LL in Active-Standby mode in uplink and downlink This may be possible.
- ATSSS-LL functionality with any steering mode
- the MA PDU session will be available for all steering modes in uplink and downlink. As a result, ATSSS-LL may be possible.
- the MA PDU session is MPTCP and ATSSS-LL may be possible with all steering modes in uplink and downlink.
- the SMF may provide the ATSSS capability of the MA PDU session to the PCF while the PDU session establishment procedure is being performed.
- PCC rules provided by the PCF may include ATSSS control information.
- the PCC rule and ATSSS control information may be used by the SMF to derive the ATSSS rule for the UE and the N4 rule for the UPF.
- SMF sends ATSSS rule and N4 rule to UE and UPF, respectively, based on local configuration (eg, local configuration based on DNN or S-NSSAI).
- the UE may receive the ATSSS rule from the SMF.
- the ATSSS rule may indicate how to route uplink traffic through 3GPP access and non-3GPP access.
- the UPF may receive the N4 rule from the SMF.
- the N4 rule may indicate how to route downlink traffic through 3GPP access and non-3GPP access.
- the SMF When the SMF receives the PDU session establishment request message including the "MA PDU Request" indication, and UP security protection is required for the PDU session, the SMF requires 3GPP access UP security The establishment of the MA PDU session can only be confirmed when protection can be enforced. The SMF need not check whether it can enforce UP security protections that require non-3GPP access.
- a MA PDU session may have user-plane resources in both 3GPP access and non-3GPP access, may have user-plane resources in only one access, or may have user-plane resources in any access It may not have planar resources.
- AMF, SMF, PCF and UPF can maintain their MA PDU session contexts if the UE is registered with another access
- the AMF may inform the SMF that the access type for the MA PDU session has become unavailable. Thereafter, the SMF may inform the UPF that the access type of the deregistered access has become unavailable and that the N3/N9 tunnel for the corresponding access type has been released.
- the UE When the UE wants to add a user-plane resource in one access of the MA PDU session (eg, based on access network performance measurement and/or ATSSS rules), the UE sends a PDU session establishment request message can be transmitted over this access.
- the PDU session establishment request message may include a PDU session ID of the MA PDU session and an "MA PDU Request" indication. For this access, if N3/N9 does not exist, N3/N9 for this access may be established.
- the UE When the UE wants to re-activate a user-plane resource in one access of the MA PDU session (eg, based on access network performance measurements and/or ATSSS rules), the UE requests a UE trigger service through this access Procedure (UE Triggered Service Request procedure) can be started.
- UE Triggered Service Request procedure UE Triggered Service Request procedure
- the network may initiate a Network Triggered Service Request procedure.
- a MA PDU session may also be established in one of the following cases:
- the UE requests a single-access PDU session, but the network decides to establish the MA PDU session instead, the MA PDU session may be established.
- This example may correspond to an optional scenario, where a UE that requires single access for a PDU session has requested a single-access PDU session, but a policy (e.g. UE route selection policy (URSP) rule) and when there are no local restrictions.
- URSP UE route selection policy
- a MA PDU session may be established while the PDU session modification procedure is performed.
- An ATSSS-capable UE may decide to request a MA PDU session based on the provided URSP rule.
- the URSP rule triggers the UE to establish a new PDU session, and the access type preference component of the URSP rule indicates "Multi-Access", the UE may request an MA PDU session when the UE applies the URSP rule. there is.
- the PCF may perform ATSSS policy determination and create a PCC rule including ATSSS policy control information.
- the ATSS policy control information may be used to determine how uplink traffic and downlink traffic of the MA PDU session are distributed through 3GPP access and non-3GPP access.
- the SMF may receive the PCC rule together with the ATSSS policy control information from the PCF. And, the SMF may map these rules to (a) the ATSSS rule transmitted to the UE and (b) the N4 rule transmitted to the UPF.
- the ATSSS rule may be a prioritized list of rules that the UE applies to enforce the ATSSS policy in the uplink direction.
- the N4 rule may be applied by the UPF to enforce the ATSSS policy in the downlink direction.
- the ATSSS rule When a MA PDU session is created or the MA PDU session is updated by the SMF (for example, after the SMF receives an updated (or new) PCC rule from the PCF), the ATSSS rule will be sent to the UE along with the NAS message. can Similarly, the N4 rule may be sent to the UPF when a MA PDU session is created or the MA PDU session is updated by the SMF.
- QoS Quality of Service
- QoS support QoS support
- the 5G QoS model for single access PDU session can also be applied to MA PDU session.
- the QoS flow may be the finest granularity of QoS differentiation in the MA PDU session.
- the MA PDU session there may be separate user plane tunnels between the AN and the PSA, and each user plane tunnel has a specific access (either 3GPP access or non-3GPP access). ) is associated with
- QoS flows may not be associated with a particular access. That is, since QoS flows are not dependent on access, the same QoS can be supported when traffic is distributed through 3GPP access and non-3GPP access.
- SMF can provide the same QoS Flow ID (QFI) in 3GPP access and non-3GPP access, so that the same QoS is supported in both access.
- QFI QoS Flow ID
- Access Network Performance Measurements may be supported. Hereinafter, Access Network Performance Measurements will be described.
- the network may provide measurement assistance information to the UE.
- the measurement assistance information may be used to determine the measurement the UE should perform in both accesses, and the measurement assistance information may be used to determine whether the UE needs to send a measurement report to the network.
- the measurement support information may include addressing information of a Performance Measurement Function (PMF) in UPF, and the UE may transmit a PMF protocol message in the following manner:
- PMF Performance Measurement Function
- measurement support information may include one IP address for PMF, User Datagram Protocol (UDP) port related to 3GPP access, and other UDP port related to non-3GPP access;
- UDP User Datagram Protocol
- the measurement support information may include one MAC address related to 3GPP access and another MAC address related to non-3GPP access.
- a PMF protocol message may be exchanged between the UE and the PMF as in the following example:
- RTT Round Trip Time
- the UE may transmit a message for reporting whether access availability / unavailability to the UPF.
- PMF protocol messages exchanged between UE and UPF may use QoS Flow related to default QoS rules for available access(s).
- the QoS Flow related to the basic QoS rule for the MA PDU session may be a Non-GBR QoS Flow.
- the UE does not apply ATSSS rules, and UPF does not apply Multimedia-Authentication-Request (MAR) rules.
- MAR Multimedia-Authentication-Request
- the UE requests a MA PDU session, and may indicate that the UE can support the MPTCP function in all steering modes and can support the ATSSS-LL function only in the Active-Standby steering mode.
- the network may transmit measurement assistance information for the UE to the UE so that the UE can transmit an access availability/unavailability report to the UPF.
- the UE and the UPF may use the measurement available in the MPTCP layer, the UE and the UPF do not perform RTT measurement using the PMF.
- RTT measurement may be performed independently by the UE and the UPF. There may be no measurement reports from one side to the other. RTT measurement can be defined to support "least delay" Steering Mode.
- RTT estimation by UE and UPF may be based on the following mechanism:
- the PMF of the UE transmits the PMF-Echo Request message to the PMF of the UPF through the user plane, and the PMF of the UPF may respond to each with a PMF-Echo Response message.
- the PMF of the UPF may send a PMF-Echo Request message to the PMF of the UE through the user plane, and the PMF of the UE may respond with a PMF-Echo Response message for each.
- the PMF of the UE may send a PMF message to the PMF of the UPF through UDP/IP.
- the destination IP address may be an IP address included in the measurement support information, and the destination UDP port may be one of two UDP ports included in the measurement support information. One UDP port can be used to send PMF messages to UPF over 3GPP access, and the other UDP port can be used to send PMF messages to UPF over non-3GPP access.
- the source IP address may be an IP address assigned to the UE for the MA PDU session, and the source UDP port may be a UDP port dynamically assigned by the UE for PMF communication. This source UDP port of the UE may remain the same for the entire lifetime of the MA PDU session.
- the PMF of the UPF may send a PMF message to the PMF of the UE through UDP/IP.
- the source IP address may be the same IP address provided in the measurement support information, and the source UDP port may be one of the two UDP ports provided in the measurement support information.
- One UDP port may be used to send PMF messages to the UE via 3GPP access, and the other UDP port may be used to send PMF messages to the UE via non-3GPP access.
- the destination IPv4 address may be an IPv4 address assigned to the UE for the MA PDU session (if any), and the destination IPv6 address may be an IPv6 address selected by the UE from the IPv6 prefix assigned to the MA PDU session (if any).
- the destination UDP port is a UDP port dynamically allocated by the UE, and may be included in all PMF messages received from the UE.
- the UE may inform the network via the user plane about the UE's dynamically assigned UDP port and IPv6 address (if IPv6 is used for PMF messages). This makes it possible for the UPF to know the IPv6 address (if applicable) and the dynamically assigned UDP port as soon as the UE's MA PDU session is established.
- the PMF of the UE may send a PMF message to the PMF of the UPF through Ethernet.
- Ethertype may be an Ethertype included in the measurement support information
- the destination MAC address may be one of two MAC addresses included in the measurement support information.
- One MAC address can be used to send PMF messages to UPF over 3GPP access
- the other MAC address can be used to send PMF messages to UPF over non-3GPP access.
- the source MAC address may be the MAC address of the UE that remains the same for the entire lifetime of the MA PDU session.
- the PMF of the UPF can send a PMF message to the PMF of the UE through Ethernet.
- the Ethertype is the same Ethertype as provided in the measurement support information, and the source MAC address may be one of the two MAC addresses provided in the measurement support information.
- One MAC address may be used to send PMF messages to the UE via 3GPP access, and the other MAC address may be used to send PMF messages to the UE via non-3GPP access.
- the destination MAC address may be the MAC address of the UE included in all PMF messages received from the UE.
- the UE shall inform the network through the user plane about the MAC address of the UE so that the UPF can know the MAC address of the UE as soon as the MA PDU session is established.
- the UE and UPF may average the RTT measurements obtained through this access to derive an estimate of the average RTT for the access type.
- the Steering function may be supported.
- the Steering function will be described.
- ATSSS capable UE can steer (coordinate), switch, and split the traffic of the MA PDU session through 3GPP access and non-3GPP access of ATSSS capable UE (ATSSS-capable UE)
- the functionality can be referred to as "steering functionality".
- An ATSSS capable UE may support one or more of the following types of steering functions:
- a high-layer steering function that operates above the Internet Protocol (IP) layer may be supported.
- IP Internet Protocol
- a high-layer steering function "MPTCP functionality" applying a Multipath Transmission Control Protocol (MPTCP) protocol may be supported.
- MPTCP functionality can be applied to steer, switch, and split the TCP traffic of applications that are allowed to use MPTCP.
- the MPTCP function of the UE may communicate with the associated MPTCP Proxy function of the UPF via the 3GPP user plane and/or the non-3GPP user plane.
- a low-layer steering function that operates below the IP layer may be supported.
- a low-layer steering function called "ATSSS Low-Layer functionality" or ATSSS-LL functionality may be supported.
- this steering function (“ATSSS Low-Layer functionality" or ATSSS-LL functionality) can steer any type of traffic (including TCP traffic, User Datagram Protocol (UDP) traffic, Ethernet traffic, etc.); It can be applied to switch, and split (split).
- ATSSS-LL functionality must be mandatory in an Ethernet-type MA PDU session. In the network, one UPF supporting ATSSS-LL must exist in the data path of the MA PDU session.
- the UE may indicate to the network the steering function and steering mode supported by the UE by including one of the following in the UE ATSSS Capability:
- ATSSS-LL functionality with any steering mode.
- the UE may indicate that it can steer, switch and split all traffic of the MA PDU session by using the ATSSS-LL function with all steering modes.
- the UE may indicate:
- the UE may use the MPTCP function with all steering modes to coordinate, switch and split the MPTCP traffic of the MA PDU session.
- the UE may use the ATSSS-LL function together with the active-standby steering mode to coordinate, switch and split all other traffic (eg, non-MPTCP traffic) of the MA PDU session.
- traffic eg, non-MPTCP traffic
- the MPTCP function with all steering modes and the ATSSS-LL function with all steering modes may be supported.
- the UE may indicate:
- the UE may use the MPTCP function with all steering modes to coordinate, switch and split the MPTCP traffic of the MA PDU session.
- UE can use the ATSSS-LL function with any steering mode to coordinate, divert and split all other traffic (i.e. non-MPTCP traffic) in the MA PDU session.
- FIG. 9 shows an exemplary model for an ATSSS-capable UE supporting the MPTCP function and the ATSSS-LL function.
- Degree 9 is UE's It is a diagram showing an example of a steering function.
- MPTCP flow may indicate traffic of an application to which MPTCP can be applied.
- IP addresses eg, IP@1, IP@2, IP@3 are shown in the UE.
- the "Low-Layer” in this figure may contain functions operating below the IP layer (eg other network interfaces of the UE), and the “High-Layer” may contain functions operating above the IP layer.
- the MPTCP function may be used to steer the MPTCP flow, and at the same time, all other flows may be steered using the ATSSS-LL function.
- one steering function can be used for the same packet flow.
- All steering functions of the UE may use the same set of ATSSS rules to make ATSSS decisions (eg, how to steer, switch, split traffic).
- all ATSSS decisions in UPF can be performed by applying the same set of N4 rules supporting ATSSS.
- the ATSSS rule and the N4 rule supporting ATSSS may be provided to each of the UE and the UPF when the MA PDU session is established.
- the UE may determine a steering function to be applied to a specific packet flow by using the provided ATSSS rule.
- the UE may receive a priority list of ATSSS rules from the SMF.
- An example of the structure of the ATSSS rule is shown in Table 3 below.
- Scope Rule Precedence Determines the order in which the ATSSS rule is evaluated in the UE
- Mandatory Yes PDU context traffic descriptor (Traffic Descriptor)
- This part defines the traffic descriptor component of the ATSSS rule.
- Mandatory NOTE 2
- application descriptor Application descriptors
- Contains one or more application IDs that identify the application generating the traffic NOTE 3
- Optional Yes PDU context IP descriptor NOTE 4) One or more 5-tuples that identify the destination of IP traffic.
- Optional Yes PDU context Non-IP descriptors (NOTE 4) Contains one or more descriptors to identify the destination of non-IP traffic, such as Ethernet traffic.
- Optional Yes PDU context access selection descriptor (Access Selection Descriptor) This part defines the access selection descriptor component of the ATSSS rule.
- Mandatory Steering Mode Identifies the Steering mode that can be applied to matching traffic
- Mandatory Yes PDU context Steering Functionality For matching traffic Identifies whether the MPTCP function or the ATSSS-LL function can be applied.
- the application ID may include OSId (Operating System Id) and an OSAppId (Operating System Application Id).
- the UE may evaluate the ATSSS rules according to priority order.
- Each ATSSS rule may include a traffic descriptor (eg, including one or more components described in the example in Table 3) that may determine when the rule is applicable. When all components of the traffic descriptor match the considered service data flow (SDF), the ATSSS rule may be determined to be applicable.
- a traffic descriptor eg, including one or more components described in the example in Table 3
- the traffic descriptor may include components such as the following examples:
- the traffic descriptor may include an application descriptor and/or an IP descriptor.
- the traffic descriptor may include an application descriptor and/or a non-IP descriptor.
- One ATSSS rule may be provided to the UE with a "match all" traffic descriptor that matches all SDFs. If this ATSSS rule is provided, this ATSSS rule may have the lowest Rule Precedence value. This ATSSS rule may be evaluated last by the UE.
- Each ATSSS rule may include an access selection descriptor that includes components such as the following examples:
- Steering Mode can determine how the matched SDF should be distributed over 3GPP access and non-3GPP access. Steering Modes such as the following examples may be supported:
- Active-Standby can be used to steer the SDF in one access (Active access) (if this access is available). And, when the active access is unavailable (unavailable), Active-Standby can be used to switch the SDF to another available access (Standby access). When active access becomes available again, the SDF can be switched back to active access. If standby access is not defined, SDF is allowed only for active access and cannot be transmitted to other accesses.
- Smallest Delay can be used to steer the SDF to the access determined to have the smallest Round-Trip Time (RTT). Measurements may be performed by the UE and UPF to determine RTT over 3GPP access and non-3GPP access. Also, if one access becomes unavailable, SDF traffic can be switched to another available access, if allowed by the PCC rule.
- RTT Round-Trip Time
- Load-Balancing can be used to split the SDF through both accesses when both accesses are available. Load-Balancing may include a percentage of SDF traffic transmitted through 3GPP access and non-3GPP access. Load-balancing can only be applied to non-GBR (Guaranteed Bit Rate) QoS flows. Also, if one access becomes unavailable, all SDF traffic may be switched to another available access, as if the percentage of SDF traffic over the other available access is 100%.
- Priority-based can be used to steer the traffic of SDF with high priority access. Priority-based may be used to steer the traffic of the SDF to high priority access until it is determined that the high priority access is congested. When it is determined that the high-priority access is congested, the traffic of the SDF may be transmitted even with the low-priority access. That is, SDF traffic may be split through two accesses. Also, if high priority access becomes unavailable, all SDF traffic may be switched over low priority access. How the UE and the UPF determine when congestion occurs in access may vary by implementation.
- Steering Functionality can be used to identify whether the MPTCP function or the ATSSS-LL function can be used to steer the traffic of the matching SDF. Steering Functionality may be used when the UE supports multiple functions for ATSSS.
- ATSSS rule An example of an ATSSS rule that may be provided to a UE is described as follows:
- This ATSSS rule steers UDP traffic with destination IP address 1.2.3.4 to active access (3GPP access) when "active access (3GPP access) is available. When active access is unavailable, standby access (Non-3GPP access)".
- ATSSS rules may include "Traffic Descriptor: TCP, DestPort 8080", and "Steering Mode: Smallest Delay":
- This ATSSS rule may mean "steer TCP traffic with destination port 8080 to access with minimal delay”.
- the UE may measure the RTT over both accesses to determine the access with the least delay.
- This ATSSS rule may mean "Using the MPTCP function, transmit 20% of application-1's traffic through 3GPP access, and transmit 80% of application-1's traffic through non-3GPP access" .
- Steering Modes eg Active-Standby, Smallest Delay, Load-Balancing, Priority-based, etc.
- Steering Modes eg Active-Standby, Smallest Delay, Load-Balancing, Priority-based, etc.
- the issue of which additional Steering Mode can be further supported is being discussed as follows.
- the conventional PMF may support RTT measurement and access availability report per PDU session.
- RTT measurement a default QoS flow may be used to transmit measurement traffic.
- the RTT value detected (or detected) in this QoS flow may be processed as an RTT for this PDU session through this access.
- this RTT value cannot reflect the exact RTT for all traffic of this PDU session over this access.
- it is necessary to measure RTT for each QoS flow.
- measurement of loss ratio and jitter is also important, so better traffic steering/switching/splitting may be possible.
- some thresholds corresponding to these parameters are dependent on RAN assistance information (e.g., RAN assistance information defined for 3GPP access) may be sent to UE and UPF to trigger traffic coordination/switching/segmentation.
- RAN assistance information e.g., RAN assistance information defined for 3GPP access
- the network may provide measurement support information to the UE.
- the RTT measurement for each QoS flow may be independently triggered by the UE or UPF.
- the measurement support information may include a QFI to which RTT measurement is applied.
- the RTT measurement frequency is determined at the network side, and the RTT measurement frequency may be transmitted to the UE through measurement assistance information.
- the PMF of the UE may send a PMF message through one QoS flow to the PMF of the UPF through UDP/IP.
- the destination IP address and UDP port may be as previously defined. That is, the destination IP address is the PMF IP address and the UDP port number may correspond to the access this message is being sent to.
- the UPF may identify the PMF message based on the destination IP address.
- the - PMF of UPF can send PMF message to PMF of UE through UDP/IP.
- the source IP address may be the same IP address provided in the measurement assistance information, and the source UDP port may be one of two UDP ports provided in the measurement assistance information.
- the destination IP address is the MA PDU session IP address allocated by the UE, and after establishing the MA PDU session, the UDP port may be transmitted by the UE through the user plane.
- the UE may identify the PMF message based on the source IP address of the PMF.
- PMF of UE can send PMF message to PMF of UPF via Ethernet.
- the destination MAC address may be included in the measurement support information.
- the UPF can then identify the PMF message based on the destination MAC address.
- PMF of UPF can send PMF message to PMF of UE through Ethernet.
- the source MAC address and the destination MAC address may be as previously defined.
- the UE can then identify the PMF message based on the source MAC address.
- the UE and UPF may average the RTT measurements obtained through this access to derive an estimate of the average RTT for the access type.
- Per PDU for RTT written in the lower part shows an example of RTT measurement according to a conventional method.
- Period QoS flow for RTT written in the upper part shows an example of improved RTT measurement.
- the improved RTT measurement (eg, Per QoS flow for RTT of FIG. 10) can make RTT measurement more accurately.
- the packet delay budget e.g, refer to TS 23.501 Table 5.7.4-1.
- the UE and the UPF may exchange packet counting information at regular intervals to calculate a packet loss ratio in a path performance measurement procedure.
- the UE calculates the number of UL packets transmitted through one QoS flow between the time when one PMF request message is transmitted and the time when the previous PMF request message is transmitted, and sends the result to the UPF through this PMF request message can provide
- the UPF may also calculate the number of UL packets received through one QoS flow between the time point when one PMF request message is received and the time point at which the previous PMF request message is received.
- the UPF may calculate a UL packet loss ratio based on the local counting result and the number of UL packets transmitted by the UE.
- the UPF may send the result of the UL packet loss rate to the UE through a PMF response message.
- the UPF may also include information counting the number of DL packets in the same message.
- the UE may count the number of DL packets received between the point in time when one PMF response message is received and the point in time when the previous PMF response message is received.
- the UE may calculate the DL packet loss rate based on the local counting result and the number of DL packets sent by the UPF, and send the DL packet loss rate to the UPF through a subsequent PMF message.
- the PMF message applied to calculate the packet loss rate may be the same as the PMF message used to measure the RTT. If the number of packets and/or packet loss rate IE(s) is added to the PMF message used to measure the RTT, this PMF message can be applied to calculate the packet loss rate.
- the PMF request message from the UE and the corresponding PMF response message from the UPF eg, Transaction ID is used to identify the request/response message
- the number of packets and the packet loss rate are the number of packets and the packet loss rate. It can be applied to transmit Referring to the example of FIG. 11 below, an example of measuring the casserole loss ratio is shown.
- 11 shows an example of packet loss ratio measurement.
- FIG. 11 an example of measuring a packet loss ratio for UL traffic is illustrated.
- the PMF request message transmitted by the UE includes TI (Transaction ID) information and the number of packets transmitted by the UE (eg, the number of UL packets between the time when one PMF request message is transmitted and the time when the previous PMF request message is transmitted) ) may be included.
- the TI information may be used to distinguish the PMF message.
- the TI information may be an extended procedure transaction identity (EPTI).
- EPTI extended procedure transaction identity
- the UE may know which PMF request message the corresponding PMF message is a response message to, etc. Whenever a PMF request message is transmitted, the value of the EPTI may be increased.
- procedure transaction identity may also be used for message transmission based on the NAS layer. Since the transmission of PMF messages occurs more frequently than the transmission of messages based on the NAS layer, EPTI was defined.
- the UF may count the number of UL packets. For example, the UPF may also calculate the number of UL packets received through one QoS flow between a time point at which one PMF request message is received and a time point at which a previous PMF request message is received. In addition, the UPF may calculate the UL packet loss rate based on the local counting result (eg, the number of UL packets calculated by the UPF) and the number of UL packets transmitted by the UE.
- the PMF response message transmitted by the UPF may include TI information and information on a UL packet loss ratio.
- - SMF may support selecting a UPF that supports a new Steering Mode.
- SDF Service Data Flow
- the UE can support the new Steering Mode and PMF enhancement.
- radio bearer may be interpreted as Internet Key Exchange (IKE) tunneling (Child security association (SA)) in non-3GPP access as well as radio bearer of 3GPP access.
- IKE Internet Key Exchange
- SA Channel security association
- measurements for multiple QoS flows may be performed.
- a method for efficiently performing measurement of multiple QoS flows has not been discussed in the prior art.
- Multiple QoS Flow may be mapped to one radio resource (eg, radio bearer).
- measurement is performed for each QoS Flow included in the Multiple QoS Flow, which causes a problem in that radio resources and computing resources are wasted.
- PLR packet loss ratio
- measurement of multiple QoS flows may be performed in the MA PDU Session.
- multiple QoS Flows are mapped to one radio resource (e.g. radio bearer)
- radio resource e.g. radio bearer
- PLR measurement may be performed for multiple QoS flows. In this case, it is necessary to check how many packets are transmitted based on the actual transmitted data. To this end, the UE and the UPF may continuously count transmitted packets. If this operation is performed for each of multiple QoS Flows, many resources may be required.
- a first example of the disclosure of the present specification describes an example of a method in which the SMF requests the access network (AN) to allocate a separate radio bearer for each QoS flow.
- the SMF may inform the access network (AN) of information not to map to one radio bearer for QoS flows that require access measurement per QoS flow (per QoS flow).
- the SMF may identify QoS flows that require access measurement for each QoS flow (per QoS flow).
- the SMF may transmit information to the AN not to map these QoS flows to one radio bearer to the AN. Accordingly, the AN may map these QoS flows to a plurality of radio bearers without mapping them to one radio bearer.
- the SMF transmits N2 information to the AN, while transmitting N2 information to the AN for QoS flow.
- N2 information may indicate whether it is necessary to create only one radio bearer by binding with other QoS flows. This may inform that each QoS flow is possible for each QoS flow, or indicate whether all QoS flows are possible for each PDU Session.
- the SMF may inform the AN of whether it is necessary to generate only one radio bearer together with other QoS flows for a specific QoS flow.
- the SMF may inform whether one radio bearer may be created by binding with other QoS flows for each QoS flow, or may indicate whether one radio bearer may be created by binding with other QoS flows for all QoS flows for each PDU session.
- the AN can map multiple QoS flows to one radio bearer only when the SMF allows multiple QoS flows to be mapped to one radio bearer. Conversely, if the SMF does not allow this, the AN may create a radio bearer 1:1 (eg, one radio bearer per one QoS flow).
- the radio bearer generation related information provided by the SMF to the AN may include information on whether access measurement is performed for QoS flow(s). Alternatively, information on whether access measurement is performed on QoS flow(s) may be provided together with the radio bearer generation related information.
- the second example of the disclosure of the present specification describes an example of a method in which, when multiple QoS flows are mapped to one radio bearer, the UE does not perform a measurement report for QoS flows mapped to one radio bearer, respectively. .
- the second example of the disclosure of the present specification describes a method in which, when multiple QoS flows are mapped to one radio bearer through RRC signaling, the UE does not perform a measurement report for bundled QoS flows, respectively. do.
- the UE may check whether QoS flows are mapped to one radio bearer. For example, the UE may check whether QoS flows for which per QoS flow measurement is currently required in the AN are mapped to one radio bearer based on configuration information for measurement received from the SMF.
- the UE may receive mapping information between a QoS flow and a radio bearer through access network signaling (e.g. RRC signaling, IKE signaling). Accordingly, the UE may determine whether a QoS flow requiring per QoS flow measurement is mapped to one radio bearer.
- access network signaling e.g. RRC signaling, IKE signaling
- the UE may inform the network of this. In this case, the UE may inform which QoS flows are mapped to one radio bearer. Alternatively, the UE may inform the network of the QoS flow and the mapping information of the radio bearer itself. The UE may inform the UPF and/or SMF of mapping-related information (eg, information on which QoS flows are mapped to one radio bearer or mapping information between QoS flows and radio bearer, etc.). For example, the UE uses the newly defined PMF message to retrieve this (eg, information about which QoS flows are mapped to one radio bearer or information related to mapping such as mapping information between QoS flows and radio bearers).
- mapping-related information eg, information on which QoS flows are mapped to one radio bearer or mapping information between QoS flows and radio bearer, etc.
- the SMF may inform it again through the UPF.
- the UPF may inform the corresponding information through the SMF.
- the UPF can measure only one of several QoS flows tied to one radio bearer based on this information.
- the UE may request the UPF to measure a specific QoS flow.
- the SMF may update the measurement configuration based on information received from the terminal or the UPF. That is, the SMF may perform measurement on only one of QoS flows mapped to one radio bearer.
- performing measurement on only one QoS flow may mean that the measurement performed on this QoS flow is also applied to other QoS flows sharing a radio bearer (eg, Data Radio Bearer (DRB)).
- a radio bearer eg, Data Radio Bearer (DRB)
- the UE and/or the UPF may perform measurement for only one QoS flow.
- the UE and/or UPF may equally apply the performed measurement to other QoS flows sharing a radio bearer (eg, DRB).
- DRB Data Radio Bearer
- This eg, measurement configuration
- the SMF may inform the UE that access measurement is performed explicitly or implicitly.
- the operation of mapping the QoS flow to the radio bearer in the AN may be performed differently for each base station and according to the resource situation of each base station. Therefore, whenever a procedure such as handover / Idle to connected transition / PDU Session activation occurs, the terminal may check the changed mapping information again and notify it to the network. Also, when UPF performs measurement in idle mode or PDU session deactivation state, the mapping information may be updated later because the measurement packet itself causes a transition to PDU session activation or connected mode. For example, when the UE is in IDLE mode or the PDU session used by the UE is in an inactive state, a measurement packet may be generated. In this case, since the terminal updates the mapping information after the terminal enters the connected mode or after the PDU session used by the terminal is activated, the mapping information may be updated later.
- the UE may update the measurement configuration provided by the SMF and inform the SMF of the updated measurement configuration.
- SMF can also inform UPF of this updated measurement configuration.
- the operation of mapping the QoS flow to the radio bearer in the AN may be performed differently for each base station and according to the resource situation of each base station. Therefore, whenever procedures such as handover / Idle to connected transition / PDU Session activation occur, the UE checks the changed mapping information again, updates the configuration for access measurement accordingly, and can notify this to the network. In addition, when measurement is performed in UPF in idle mode or PDU session deactivation state, the configuration for access measurement may be updated later because the measurement packet itself causes PDU session activation or connected mode transition.
- a third example of the disclosure of the present specification describes an example of a method in which the Access Network (AN) informs the SMF of mapping information of a QoS flow and a radio bearer.
- AN Access Network
- the AN may inform the SMF of mapping information of a QoS flow and a radio bearer.
- the SMF may transmit N2 information to the AN.
- the AN may transmit information on mapping information of a QoS flow and a radio bearer or information on a QoS flow mapped to one radio bearer to the SMF.
- the SMF may newly update the measurement configuration in consideration of mapping information in the AN.
- the SMF may perform measurement on only one QoS flow for QoS flows (eg, QoS flows mapped to one radio bearer) tied to one radio bearer in the AN.
- the SMF may transmit the updated measurement configuration to the UE and/or UPF.
- the UE and/or UPF may transmit QoS flows tied to one radio bearer (eg, QoS flow mapped to one radio bearer). ), measurement can be performed for only one QoS flow.
- Performing measurement on only one QoS flow may mean that measurement performed on this QoS flow is also applied to other QoS flows sharing DRB.
- this QoS flow The measurement for may be equally applied to other QoS flows sharing a radio bearer.
- the UE and/or the UPF measure one QoS flow among QoS flows tied to one radio bearer (eg, QoS flows mapped to one radio bearer) other QoS flows. It can be determined that it can be reused for (that is, other QoS flows sharing a radio bearer). Accordingly, the UE and/or the UPF may not perform measurement for other QoS flows sharing the radio bearer.
- a fourth example of the disclosure of the present specification describes an example of an operation in which the terminal transmits a message to the UPF.
- the terminal when the terminal receives the PMF message from the UPF, the terminal may transmit a PMF response to the received PMF message to the UPF.
- the UE may inform the UPF that measurement of the corresponding QoS flow is unnecessary.
- the UE may transmit a PMF response message including information that measurement of the corresponding QoS flow is unnecessary to the UPF.
- the UE may inform the UPF of information on the QoS flow determined to perform measurement (information on one of the QoS flows tied to the same radio bearer) to the UPF.
- the UPF may no longer perform measurement on the corresponding QoS flow.
- the UE transmits a PMF message including information on the QoS flow for which measurement is stopped to the UPF, thereby resuming measurement of the corresponding QoS flow.
- the UE transmits a PMF message by including information indicating that the QoS flow mapping information is changed and performs measurement again, or even if the UE simply transmits a PMF message, the UPF implicitly performs measurement on the corresponding QoS flow again. It can also be interpreted as meaning.
- a fifth example of the disclosure of the present specification describes an example of QoS flow measurement.
- the UE and the UPF When the UE performs measurement for each QoS flow using the PMF message, the UE and the UPF must transmit the PMF message through the target QoS flow. There are two possible ways to support this:
- the SMF may provide the necessary QoS rule(s) and N4 rule(s) to the UE and the UPF.
- the UE and the UPF may ignore the QoS rule(s) and N4 rule(s) for the PMF message, and transmit the PMF message through the target QoS flow.
- Option 1 is more consistent with the overall QoS design, but each PMF message sent through the QoS flow must use different PMF address information (eg, different address or port number). This means that the UE or UPF must allocate a different PMF IP address or port for each QoS flow.
- the information may be sent to the network, based on the information the SMF needs to create the QoS rule and the N4 rule. However, this may result in additional NAS signaling. Therefore, it may make sense for UPF to allocate a different address.
- Option 2 may be a simpler approach because the UE and UPF do not need to manage different PMF addresses for each QoS flow. However, this is not consistent with the general QoS framework. The UE and the UPF may ignore the existing QoS rule(s) and N4 rule(s) when sending a PMF message through the QoS flow. In addition, when the 3GPP access leg is established through the EPC, transmission of the PMF message through the dedicated bearer may not be supported by the existing modem. Therefore, if one of the 3GPP access legs is established in the EPC, this option may not be supported.
- multiple QoS flows can be mapped to a single radio bearer of NG-RAN. If this mapping is performed by the NG-RAN, the measurement per QoS flow level does not provide much benefit because end-to-end performance is highly dependent on radio performance. Considering that there is no existing mechanism for preventing the NG-RAN from combining multiple QoS flows into one radio bearer, so that QoS flows that require measurement for each QoS flow are not mapped to a single radio bearer, additional information needs to be defined. However, this method may have a large impact on the RAN. Another possible method is that the UE reports mapping information between a radio bearer and a QoS flow to the UPF, so that measurement can be performed on only one of the QoS flows mapped to a single radio bearer.
- a sixth example of the disclosure of the present specification describes an example of a method for improving PMF in order to support QoS Flow measurement (eg, RTT measurement, Packet Loss Rate (PLR) measurement, etc.).
- QoS Flow measurement eg, RTT measurement, Packet Loss Rate (PLR) measurement, etc.
- a sixth example of the disclosure of the present specification describes an example of improvement of PMF to support RTT measurement and PLR measurement for each QoS flow.
- Access Network Performance Measurements may be supported. Hereinafter, Access Network Performance Measurements will be described.
- the network may provide measurement assistance information to the UE.
- the measurement assistance information may be used to determine the measurement that the UE should perform in both accesses, and the measurement assistance information may be used to determine whether the UE needs to send a measurement report to the network.
- the measurement support information may include addressing information of a Performance Measurement Function (PMF) in UPF, and the UE may transmit a PMF protocol message in the following manner:
- PMF Performance Measurement Function
- measurement support information may include one IP address for PMF, User Datagram Protocol (UDP) port related to 3GPP access, and other UDP port related to non-3GPP access;
- UDP User Datagram Protocol
- the measurement support information may include one MAC address related to 3GPP access and another MAC address related to non-3GPP access.
- Access measurement for multiple QoS flows may be performed.
- the SMF may indicate whether access measurement for multiple QoS flows is supported in measurement support information.
- the UE and the UPF may transmit a PMF message through the QoS flow that the UE and the UPF want to measure.
- UPF can find out that multiple QoS flows are mapped to one AN resource by analogy without signaling from the UE. For example, UPF may perform measurement for each QoS Flow. As a result of the measurement, if measurement of some QoS Flows shows almost similar results, the UPF may determine that the corresponding QoS Flows are mapped to one AN resource. In addition, in the case of the terminal, the terminal may directly know mapping information (eg, mapping information between QoS flow and AN resource). When multiple QoS Flows are mapped to the same AN resource, when the UE performs access measurement, the UE may perform measurement on only one QoS Flow. thus. Based on the access measurement performed by the UE, the UPF may infer that the QoS Flow for which the UE does not perform measurement is mapped to the same AN resource as other QoS Flows.
- mapping information eg, mapping information between QoS flow and AN resource
- the UE and the UPF may perform the same operation as in the example related to “Packet Loss Rate measurement” described below.
- PLR Packet Loss Rate
- the UE may not transmit a counting request for PLR measurement for this QoS flow to the UPF.
- the UE may stop PLR measurement by not transmitting a counting request for QoS Flow that does not require measurement.
- the UE may transmit a counting request to the UPF to perform PLR measurement. In this way, since packet counting for PLR can be performed only for QoS flows that require measurement, there is an advantage in that overheads of the UE and UPF can be reduced.
- the UPF may perform an operation of determining whether QoS Flows are mapped to the same AN resource as in the following example. For example, based on the implementation-dependent timer, UPF determines that QoS flows are mapped to the same AN resource when measurement results for QoS flows are similar or identical during the timer operation period. there is. For example, UPF is based on an implementation-dependent timer (eg, 1 minute), and when the measurement results of a certain number of QoS flows are similar or the same during the timer operation period, QoS flows are sent to the same AN resource. It can also be judged that it is mapped. This determination method may also be used by the UE.
- UPF determines that QoS flows are mapped to the same AN resource when measurement results for QoS flows are similar or identical during the timer operation period.
- an implementation-dependent timer eg, 1 minute
- the SMF and/or PCF may instruct the UE for which QoS flow measurement should be performed.
- the target QoS flow for which the UE and/or the UPF perform measurement may be determined according to the UE implementation and/or the UPF implementation.
- Addressing information of the PMF in the UPF may be retrieved by the SMF during the N4 session establishment procedure.
- the following PMF protocol messages may be exchanged between the UE and the PMF:
- RTT Round Trip Time
- the PMF protocol message for access availability/unavailability reporting exchanged between the UE and the UPF may use a QoS flow related to a default QoS rule for available access(s).
- the PMF protocol message for access measurement exchanged between the UE and the UPF may use the QoS flow of the access for which the measurement is performed.
- the QoS Flow related to the basic QoS rule for the MA PDU session may be a Non-GBR QoS Flow.
- the UE does not apply ATSSS rules, and UPF does not apply Multimedia-Authentication-Request (MAR) rules.
- MAR Multimedia-Authentication-Request
- the UE requests a MA PDU session, and may indicate that the UE can support the MPTCP function in all steering modes and can support the ATSSS-LL function only in the Active-Standby steering mode.
- the network may transmit measurement assistance information for the UE to the UE so that the UE can transmit an access availability/unavailability report to the UPF.
- the UE and the UPF may use the measurement available in the MPTCP layer, the UE and the UPF do not perform RTT measurement using the PMF.
- RTT measurement can be defined to support "Minimum Delay” or “Load Balancing” Steering Mode.
- both the UE and the UPF may include the QFI in the PMF message.
- the method in which the PMF message is transmitted through a specific QoS flow is not specifically defined.
- the UE and UPF use different PMF addresses for each QoS flow, or UE and UPF use special processing so that QoS rules and/or N4 rules are not applied. can In the latter case, the QFI information should be included in the PMF message.
- the PLR measurement can be calculated by exchanging the number of packets transmitted between the UE and the UPF.
- the UE and UPF may report the calculated PLR from one side to the other.
- RTT measurements can be defined to support a "load balancing" steering mode.
- PLR calculation by UE and UPF may be based on the following mechanism:
- the UE may send a PMF message to request the UPF to count the number of received UL packets.
- the UPF may start counting the QoS Flow in which the PMF message is received and the UL packets received through the access network in which the PMF message is received.
- the UE may start counting the QoS flow through which the PMF message is transmitted and the UL packet transmitted through the access network;
- the UE may request the UPF to report the number of received UL packets.
- the UPF may report the counted number of packets received between the PMF message for the counting request and the PMF message for the counting report. For example, the UPF may count packets received between the time when the PMF message for counting request is received and the time when the PMF message for counting report is received, and report the number of counted packets to the UE.
- the PMF message for counting report may instruct the UPF to count packets.
- the UE may calculate the UL Packet Loss Rate based on the local counting result of the number of transmitted UL packets and the number of received UL packets reported from the UPF.
- the local counting result may mean a result of counting the number of UL packets transmitted by the UE.
- the UPF may request the UE to count the number of DL packets received.
- the UE may start counting the QoS Flow where the PMF message was received and the DL packet received through the access network where the MF message was received.
- the UPF may start calculating the QoS flow through which the PMF message is transmitted and the DL packet transmitted through the access network through which the PMF message is transmitted.
- the UPF may request the UE to report the number of UL packets received.
- the UE may report the counted number of packets received between the PMF message for the counting request and the PMF message for the counting report. For example, the UE counts packets received between the time when the PMF message for counting request is received and the time when the PMF message for counting report is received, and reports the number of counted packets to the UPF.
- the PMF message for counting report may instruct the UE to count packets.
- the UPF can calculate the DL Packet Loss Rate based on the local counting result of the number of transmitted DL packets and the number of received DL packets reported from the UE.
- the local counting result may mean a result of counting the number of DL packets transmitted by the UPF.
- the UE and the UPF may average the PLR measurements obtained through this access to derive an estimate of the average PLR per QoS flow for the access type.
- 12A and 12B are diagrams of the disclosure of the present specification; in the 7th example A first example of an operation according to the following is shown.
- FIGS. 12A and 12B are only examples, and the scope of the disclosure is not limited by the operations illustrated in FIGS. 12A and 12B .
- the operations described in the first to sixth examples of the disclosure of the present specification may be performed.
- 12A and 12B show examples of how the SMF allocates different resources for each QoS Flow. 12A and 12B , the SMF may perform an operation for requesting different resource allocation for each QoS Flow.
- the UE may transmit a UL NAS Transport message for transmitting a PDU Session Establishment Request to create (or establish) a MA PDU Session.
- the UE may transmit the message by setting the UL Request Type of the UL NAS Transport message to “MA PDU request” indicating that the MA PDU Session is a request.
- the UE may transmit the message by including the ATSSS capability information in the PDU Session Establishment Request message.
- the ATSSS capability information may be capability information on whether the terminal can perform the ATSSS-related operation described above through various examples.
- the AMF may transmit the PDU Session Establishment Request message transmitted by the UE to the SMF.
- the SMF may transmit the ATSSS capability information transmitted by the UE to the PCF.
- the PCF may generate a PCC rule based on ATSSS capability information of the terminal.
- the PCF may transmit the generated PCC rule to the SMF.
- the SMF may generate an ATSSS rule to be transmitted to the terminal and an N4 rule to be transmitted to the UPF based on the PCC rule received from the PCF (or based on information configured in the SMF if the PCF is not used).
- the SMF may transmit the generated ATSSS rule into the PDU Session Establishment Accept message to the UE.
- the SMF may also transmit an N2 message for allocating resources for the MA PDU Session in 3GPP access.
- the SMF may transmit an indication requesting allocation of a different resource for each QoS flow to the UPF together.
- AMF may transmit N2 message and PDU Session Establishment Accept message transmitted by SMF to NG-RAN.
- the NG-RAN may perform a process of allocating resources necessary for the MA PDU Session while exchanging AN signaling with the UE. In addition, the NG-RAN may transmit a PDU Session Establishment Accept message to the terminal along with this process. If the SMF makes a request to allocate different resources for each QoS Flow, the NG-RAN may perform an operation of mapping each QoS Flow to a different radio bearer.
- the NG-RAN may inform the SMF that the 3GPP access resource has been successfully allocated via the AMF.
- the AMF may deliver the message transmitted by the NG-RAN to the SMF.
- SMF can perform UPF and N4 Session Modification procedures.
- the SMF may transmit the response message for step 11) to the AMF.
- SMF may transmit an N2 message for allocating resources for MA PDU Session in non-3GPP access.
- the SMF may transmit an indication requesting to allocate a different resource for each QoS flow to the UPF together.
- the AMF may transmit the N2 message received from the SMF to the N3IWF.
- the N3IWF may perform a process of allocating resources required for the MA PDU Session while exchanging AN signaling with the UE. If the SMF requests to allocate different resources for each QoS Flow, the N3IWF may create different Internet Protocol security (IPsec) tunnels for each QoS Flow in order to map it to a different AN resource for each QoS Flow.
- IPsec Internet Protocol security
- the N3IWF may transmit an "indication to request allocation of a different resource for each QoS Flow" received from the SMF by including it in the Additional QoS Information. The terminal receiving this may request a QoS resource of non-3GPP access in consideration of the indication.
- the N3IWF may inform the SMF that the non-3GPP access resource has been successfully allocated through the AMF.
- the AMF may deliver the message transmitted by the NG-RAN to the SMF.
- SMF can perform UPF and N4 Session Modification procedures to update tunnel information transmitted by N3IWF.
- the SMF may transmit the response message for step 18) to the AMF.
- the UE and the UPF may perform measurement for each QoS flow based on the information transmitted by the SMF.
- FIG. 13A and 13B are diagrams of the disclosure of the present specification; in the 7th example A second example of the following operation is shown.
- FIGS. 13A and 13B are only examples, and the scope of the disclosure is not limited by the operations illustrated in FIGS. 13A and 13B .
- the operations described in the first to sixth examples of the disclosure of the present specification may be performed.
- FIGS. 13A and 13B show an example of a method for the UE to determine based on mapping information between an AN resource and a QoS Flow.
- the UE may perform an operation of determining based on mapping information between the AN resource and the QoS Flow.
- 1) to 6) may be performed in the same manner as 1) to 6) in the example of FIGS. 12A and 12B .
- the SMF may transmit the generated ATSSS rule into the PDU Session Establishment Accept message to the UE.
- the SMF may also transmit an N2 message for allocating resources for the MA PDU Session in 3GPP access.
- AMF may transmit N2 message and PDU Session Establishment Accept message transmitted by SMF to NG-RAN.
- the NG-RAN may perform a process of allocating resources required for the MA PDU Session while exchanging AN signaling with the UE.
- the NG-RAN may transmit a PDU Session Establishment Accept message to the terminal along with this process.
- the UE may receive mapping information between a radio bearer of 3GPP access and a QoS Flow.
- the NG-RAN may inform the SMF that the 3GPP access resource has been successfully allocated via the AMF.
- the AMF may deliver the message transmitted by the NG-RAN to the SMF.
- SMF can perform UPF and N4 Session Modification procedures.
- the SMF may transmit the response message for step 11) to the AMF.
- SMF may transmit an N2 message for allocating resources for MA PDU Session in non-3GPP access.
- the AMF may transmit the N2 message received from the SMF to the N3IWF.
- the N3IWF may perform a process of allocating resources required for the MA PDU Session while exchanging AN signaling with the UE.
- the UE may receive mapping information between a radio bearer of 3GPP access and a QoS Flow.
- the N3IWF may inform the SMF that the non-3GPP access resource has been successfully allocated through the AMF.
- the AMF may deliver the message transmitted by the NG-RAN to the SMF.
- SMF can perform UPF and N4 Session Modification procedures to update tunnel information transmitted by N3IWF.
- the SMF may transmit the response message for step 18) to the AMF.
- the terminal receives the AN resource-QoS Flow mapping information in 3GPP access received in steps 9) and 16), AN resource-QoS Flow mapping information in non-3GPP access, and the measurement assistance information transmitted by the SMF.
- the measurement assistance information may be included in the PDU session establishment acceptance message, and the UE may receive the measurement assistance information in step 9).
- the UE may perform measurement on only one of the QoS Flows mapped to the same AN resource.
- the UE may apply the measurement result for one QoS Flow to QoS Flows mapped to the same AN resource as the corresponding QoS Flow. Because the AN resource-QoS Flow mapping in 3GPP access and non-3GPP access may be different from each other, the UE determines for each access (eg, a determination to perform measurement on only one of the QoS Flows mapped to the same AN resource) , judgment applied to QoS Flows mapped to the same AN resource as the corresponding QoS Flow, etc.) can be performed.
- An eighth example of the disclosure of the present specification describes an example of operation of a terminal (eg, UE) and/or a network according to various examples of the disclosure of the present specification described above.
- the operation of the terminal and/or the operation of the network (eg, UPF) described in the eighth example of the disclosure of the present specification is merely an example, and the scope of the disclosure of the present specification is from the eighth example of the disclosure of the present specification. It is not limited by what is described.
- the terminal and/or the network may perform the operations described in the first to seventh examples of the disclosure above, even if not described in the eighth example of the disclosure of the present specification.
- FIG. 14 is a diagram according to the disclosure of the present specification. UE's action and/or UPF's An example of an operation is shown.
- the operation of the UE and/or the operation of the UPF illustrated in the example of FIG. 14 is merely an example, and the scope of the disclosure is not limited by the operation illustrated in FIG. 14 .
- the UE and/or the UPF may perform the operations described in Examples 1 to 7 of the present disclosure, even if the operation is not shown in FIG. 14 .
- the operation illustrated in the example of FIG. 14 may be an operation performed by the UE.
- the UPF may also perform the operation shown in the example of FIG. 14 .
- the example of FIG. 14 will be described focusing on the operation of the UE, and the operation of the UPF will also be described.
- the UE may perform access measurement for the first QoS flow.
- the UE may perform Access Network Performance Measurements for the first QoS flow.
- the UE may perform Packet Loss Ration (PLR) measurement for the first QoS flow.
- PLR Packet Loss Ration
- the UE may determine that the access measurement for the first QoS flow may be applied to the second QoS flow. For example, the UE may determine, based on the mapping between the AN resource and the QoS flow, that the access measurement for the first QoS flow may be applied to the second QoS flow. For example, when the first QoS flow and the second QoS flow are mapped to the same AN resource, it may be determined that an access measurement for the first QoS flow can be applied to the second QoS flow.
- the UE may decide not to perform access measurement for the second QoS flow.
- the first QoS flow and the second QoS flow may correspond to the same MA PDU session.
- the UE needs to perform access measurement for each QoS flow, but can reuse the access measurement for the first QoS flow for the second QoS flow, then the UE performs the access measurement for the second QoS flow. may not perform.
- the UE may apply the same access measurement for the first QoS flow to the second QoS flow.
- the operations illustrated in the example of FIG. 14 may also be performed by the UPF.
- the UPF may perform access measurement for the first QoS flow.
- the UPF may determine that the access measurement for the first QoS flow may be applied to the second QoS flow.
- the UPF may decide not to perform access measurement for the second QoS flow.
- PLR An example of an operation related to measurement is shown.
- the operation related to the PLR measurement illustrated in the example of FIG. 15 is merely an example, and the scope of the disclosure is not limited by the operation illustrated in FIG. 15 .
- An operation related to PLR measurement according to the example of FIG. 15 may be included in step S1401 of the example of FIG. 14 .
- the operation related to the PLR measurement described in the first to seventh examples of the disclosure of the present specification may be performed.
- steps S1501 to S1504 are examples of operations related to UL PLR measurement.
- steps S1505 to S1508 are examples of operations related to DL PLR measurement.
- An operation related to UL PLR measurement and an operation related to DL PLR measurement may be selectively performed or both may be performed.
- steps S1501 to S1504 may be performed, or only operations related to DL PLR measurement (steps S1505 to S1508) may be performed.
- steps S1505 to S1508 may be performed.
- steps S1505 to S1508 may be performed after an operation related to UL PLR measurement (eg, step S1501 to step S1504) is performed.
- an operation related to DL PLR measurement (step S1505 to step S1508)) may be performed. .
- an operation related to DL PLR measurement (steps S1505 to S1508) is performed, an operation related to UL PLR measurement (eg, steps S1501 to S1504)) may be performed.
- an operation related to DL PLR measurement (steps S1505 to S1508) and an operation related to UL PLR measurement (eg, steps S1501 to S1504) may be simultaneously performed.
- the UE may transmit a count request message to the UPF.
- the count request message may be, for example, a request message for requesting the UPF to count the number of UL packets received through a target QoS flow (eg, a first QoS flow).
- the request message may be a Performance Measurement Function (PMF) based message.
- PMF Performance Measurement Function
- the UPF may transmit a response message indicating that the count request message has been received to the terminal.
- the UPF may count the number of UL packets received through the target QoS flow (eg, the first QoS flow). For example, the UPF may count the number of UL packets received through a target QoS flow (eg, a first QoS flow), that is, an access network in which a count request message is received.
- the UE may count the number of UL packets transmitted through the target QoS flow (eg, the first QoS flow). For example, the UE may count the number of UL packets transmitted through the target QoS flow (eg, the first QoS flow), that is, the access network to which the count request message is transmitted.
- the UE may transmit a report request message to the UPF.
- the report request message is a message requesting the UPF to report the number of UL packets (eg, the number of UL packets counted by the UPF) received through the target QoS flow (eg, the first QoS flow).
- the report request message may also be a PMF-based message.
- the UPF may transmit a report response message to the UE.
- the report response message includes information on the number of UL packets that have been counted since the UPF last sent a count response message (eg, a message requesting to count the number of UL packets received through the target QoS flow).
- the UE After receiving the report response message, the UE receives the "number of UL packets received" from the UPF and the number of UL packets transmitted by the UE (eg, after the UE sends a report request message, the UE counts Based on the number of UL packets), the UL PLR may be calculated.
- the UPF may transmit a count request message to the UE.
- the request message may be, for example, a request message requesting the UE to count the number of DL packets received through the target QoS flow (eg, the first QoS flow).
- the count request message may be a PMF-based message.
- the UE may transmit a response message indicating that the count request message has been received to the UPF.
- the UE may count the number of UL packets received through the target QoS flow (eg, the first QoS flow). For example, the UE may count the target QoS flow (eg, the first QoS flow), that is, the number of DL packets received through the access network in which the request message is received.
- the UPF may count the number of DL packets transmitted through the target QoS flow (eg, the first QoS flow). For example, the UPF may count the number of DL packets transmitted through the target QoS flow (eg, the first QoS flow), that is, the access network to which the count request message is transmitted.
- the UPF may transmit a report request message to the UE.
- the report request message is a message requesting the UE to report the number of DL packets (eg, the number of DL packets counted by the UPF) received through the target QoS flow (eg, the first QoS flow).
- the report request message may also be a PMF-based message.
- the UPF may transmit a report response message to the UE.
- the report response message includes information on the number of DL packets counted since the UE last sent a count response message (eg, a message requesting to count the number of DL packets received through the target QoS flow).
- the UPF After receiving the report response message, the UPF counts the "number of DL packets received" received from the UE and the number of DL packets transmitted by the UPF (e.g., after the UPF sends a report request message, the UPF counts Based on the number of DL packets), a DL PLR may be calculated.
- the SMF may perform an operation indicating whether QoS flows may be mapped to one radio bearer during user plane resource setup to the AN.
- the UE may determine a QoS flow that does not require per QoS flow measurement based on the mapping information between the QoS flow received from the AN and the radio bearer, and may perform an operation of notifying the QoS flow to the network.
- the SMF requests user plane resource setup to the AN
- the AN may perform an operation of notifying the QoS flow and mapping information of the radio bearer to the SMF. Based on the mapping information between the QoS flow received by the UE from the AN and the radio bearer, it may be determined that per QoS flow measurement is not required.
- the terminal receives a PMF message for a QoS flow that is determined not to require per QoS flow measurement, the terminal may perform an operation informing that measurement of the corresponding QoS flow is not necessary while transmitting a response to this.
- the operation of the terminal (eg, UE) described in this specification may be implemented by the devices of FIGS. 1 to 4 described above.
- the terminal eg, UE
- the terminal may be the first device 100 or the second device 200 of FIG. 2 .
- an operation of a terminal (eg, UE) described herein may be processed by one or more processors 102 or 202 .
- the operation of the terminal described in this specification may be stored in one or more memories 104 or 204 in the form of an instruction/program (e.g. instruction, executable code) executable by one or more processors 102 or 202 .
- an instruction/program e.g. instruction, executable code
- One or more processors 102 or 202 control one or more memories 104 or 204 and one or more transceivers 105 or 206 , and execute instructions/programs stored in one or more memories 104 or 204 as disclosed herein. It is possible to perform the operation of the terminal (eg, UE) described in .
- instructions for performing an operation of a terminal (eg, UE) described in the disclosure of the present specification may be stored in a non-volatile computer-readable storage medium in which it is recorded.
- the storage medium may be included in one or more memories 104 or 204 .
- the instructions recorded in the storage medium may be executed by one or more processors 102 or 202 to perform the operation of the terminal (eg, UE) described in the disclosure of the present specification.
- a network node eg, N3IWF, AMF, SMF, UPF, PCF, etc.
- a base station eg, NG-RAN, gNB, eNB, RAN, E-UTRAN, etc.
- 1 to 3 may be implemented.
- the network node or base station may be the first apparatus 100 or the second apparatus 200 of FIG. 2 .
- the operation of a network node or base station described herein may be handled by one or more processors 102 or 202 .
- the operation of the terminal described in this specification may be stored in one or more memories 104 or 204 in the form of an instruction/program (e.g.
- processors 102 or 202 control one or more memories 104 or 204 and one or more transceivers 106 or 206 , and execute instructions/programs stored in one or more memories 104 or 204 as disclosed herein. It is possible to perform the operation of the network node or the base station described in .
- the instructions for performing the operation of the network node or the base station described in the disclosure of the present specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium recording.
- the storage medium may be included in one or more memories 104 or 204 .
- the instructions recorded in the storage medium may be executed by one or more processors 102 or 202 to perform the operations of the network node or the base station described in the disclosure of the present specification.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
주파수 범위 정의 | 주파수 범위 | 부반송파 간격 |
FR1 | 450MHz - 6000MHz | 15, 30, 60kHz |
FR2 | 24250MHz - 52600MHz | 60, 120, 240kHz |
주파수 범위 정의 | 주파수 범위 | 부반송파 간격 |
FR1 | 410MHz - 7125MHz | 15, 30, 60kHz |
FR2 | 24250MHz - 52600MHz | 60, 120, 240kHz |
Information name | Description | Category | SMF가 PDU 컨텍스트에서 수정할 수 있는지 여부 (SMF permitted to modify in a PDU context) |
Scope |
Rule Precedence | UE에서 ATSSS 규칙이 평가되는 순서를 결정함 (Determines the order in which the ATSSS rule is evaluated in the UE) | Mandatory (NOTE 1) |
Yes | PDU context |
트래픽 설명자 (Traffic Descriptor) |
이 부분은 ATSSS 규칙의 트래픽 설명자 컨포넌트를 정의함 | Mandatory (NOTE 2) |
||
어플리케이션 설명자 (Application descriptors) |
트래픽을 생성하는 어플리케이션을 식별하는 하나 이상의 어플리케이션 ID를 포함함 (NOTE 3). |
Optional | Yes | PDU context |
IP 설명자 (NOTE 4) |
IP 트래픽의 목적지를 식별하는 하나 이상의 5-튜플을 포함함(One or more 5-tuples that identify the destination of IP traffic.) | Optional | Yes | PDU context |
Non-IP 설명자 (NOTE 4) |
이더넷 트래픽과 같은 비-IP 트래픽의 목적지를 식별하기 위한 하나 이상의 설명자를 포함. | Optional | Yes | PDU context |
액세스 선택 설명자 (Access Selection Descriptor) |
이 부분은 ATSSS 규칙의 액세스 선택 설명자 컴포넌트를 정의함 | Mandatory | ||
Steering Mode | 매칭되는 트래픽에 적용될 수 있는 Steering mode를 식별함 | Mandatory | Yes | PDU context |
Steering Functionality | 매칭되는 트래픽에 대해, MPTCP 기능 또는 ATSSS-LL 기능이 적용될 수 있는지 여부를 식별함. | Optional (NOTE 5) |
Yes | PDU context |
Claims (19)
- User Equipment (UE)가 측정에 관련된 통신을 수행하는 방법으로서,제1 Quality of Service (QoS) 플로우에 대한 액세스 측정을 수행하는 단계;상기 제1 QoS 플로우에 대한 액세스 측정이 제2 QoS 플로우에 적용된다고 결정하는 단계; 및상기 제1 QoS 플로우에 대한 액세스 측정이 제2 QoS 플로우에 적용되는 것에 기초하여, 상기 제2 QoS 플로우에 대한 액세스 측정을 수행하지 않기로 결정하는 단계를 포함하는 방법.
- 제1항에 있어서,Access Network (AN) 자원과 QoS 플로우 사이의 맵핑에 기초하여, 상기 제1 QoS 플로우에 대한 액세스 측정이 제2 QoS 플로우에 적용된다고 결정되는 것을 특징으로 하는 방법.
- 제1항에 있어서,상기 제1 QoS 플로우에 대한 액세스 측정은, 상기 제1 QoS 플로우에 대한 패킷 손실 률(Packet Loss Rate: PLR) 측정을 포함하는 것을 특징으로 하는 방법.
- 제1항에 있어서,상기 액세스 측정을 수행하는 단계는,상기 제1 QoS 플로우를 통해 수신된 상향링크(Uplink: UL) 패킷의 수를 카운트할 것을 요청하는 요청 메시지를 User Plane Function (UPF)에게 전송하는 단계를 더 포함하는 방법.
- 제4항에 있어서,상기 액세스 측정을 수행하는 단계는,상기 수신된 UL 패킷의 수를 보고할 것을 요청하는 보고 요청 메시지를 상기 UPF에게 전송하는 단계를 더 포함하는 방법.
- 제5항에 있어서,상기 액세스 측정을 수행하는 단계는,상기 수신된 UL 패킷의 수에 대한 정보를 포함하는 보고 응답 메시지를 상기 UPF로부터 수신하는 단계를 더 포함하는 방법.
- 제6항에 있어서,상기 액세스 측정을 수행하는 단계는,상기 UPF로부터 수신한 상기 수신된 UL 패킷의 수와 상기 UE에 의해 전송된 UL 패킷의 수에 기초하여, 패킷 손실 률(Packet Loss Rate: PLR)을 계산하는 단계를 더 포함하는 것을 특징으로 하는 방법.
- 측정에 관련된 통신을 수행하는 User Equipment (UE)에 있어서,적어도 하나의 프로세서; 및명령어(instructions)를 저장하고, 상기 적어도 하나의 프로세서와 동작가능하게(operably) 전기적으로 연결가능한, 적어도 하나의 메모리를 포함하고,상기 명령어가 상기 적어도 하나의 프로세서에 의해 실행되는 것에 기초하여 수행되는 동작은:제1 Quality of Service (QoS) 플로우에 대한 액세스 측정을 수행하는 단계;상기 제1 QoS 플로우에 대한 액세스 측정이 제2 QoS 플로우에 적용된다고 결정하는 단계; 및상기 제1 QoS 플로우에 대한 액세스 측정이 제2 QoS 플로우에 적용되는 것에 기초하여, 상기 제2 QoS 플로우에 대한 액세스 측정을 수행하지 않기로 결정하는 단계를 포함하는 UE.
- 제8항에 있어서,상기 UE는 이동 단말기, 네트워크 및 상기 UE 이외의 자율 주행 차량 중 적어도 하나와 통신하는 자율 주행 장치인 것을 특징으로 하는 UE.
- 이동통신에서의 장치(apparatus)로서,적어도 하나의 프로세서; 및명령어(instructions)를 저장하고, 상기 적어도 하나의 프로세서와 동작가능하게(operably) 전기적으로 연결가능한, 적어도 하나의 메모리를 포함하고,상기 명령어가 상기 적어도 하나의 프로세서에 의해 실행되는 것에 기초하여 수행되는 동작은:제1 Quality of Service (QoS) 플로우에 대한 액세스 측정을 수행하는 단계;상기 제1 QoS 플로우에 대한 액세스 측정이 제2 QoS 플로우에 적용된다고 결정하는 단계; 및상기 제1 QoS 플로우에 대한 액세스 측정이 제2 QoS 플로우에 적용되는 것에 기초하여, 상기 제2 QoS 플로우에 대한 액세스 측정을 수행하지 않기로 결정하는 단계를 포함하는 장치.
- 명령어들을 기록하고 있는 비일시적(non-transitory) 컴퓨터 판독가능 저장 매체(computer readable medium)로서,상기 명령어들은, 하나 이상의 프로세서들에 의해 실행될 때, 상기 하나 이상의 프로세서들로 하여금:제1 Quality of Service (QoS) 플로우에 대한 액세스 측정을 수행하는 단계;상기 제1 QoS 플로우에 대한 액세스 측정이 제2 QoS 플로우에 적용된다고 결정하는 단계; 및상기 제1 QoS 플로우에 대한 액세스 측정이 제2 QoS 플로우에 적용되는 것에 기초하여, 상기 제2 QoS 플로우에 대한 액세스 측정을 수행하지 않기로 결정하는 단계를 수행하도록 하는 컴퓨터 판독가능 저장매체.
- User Plane Function (UPF) 노드가 측정에 관련된 통신을 수행하는 방법으로서,제1 Quality of Service (QoS) 플로우에 대한 액세스 측정을 수행하는 단계;상기 제1 QoS 플로우에 대한 액세스 측정이 제2 QoS 플로우에 적용된다고 결정하는 단계; 및상기 제1 QoS 플로우에 대한 액세스 측정이 제2 QoS 플로우에 적용되는 것에 기초하여, 상기 제2 QoS 플로우에 대한 액세스 측정을 수행하지 않기로 결정하는 단계를 포함하는 방법.
- 제12항에 있어서,상기 제1 QoS 플로우에 대한 액세스 측정과 상기 제2 QoS 플로우에 대한 액세스 측정이 매우 유사한 측정 결과를 가지거나, 또는 동일한 측정 결과를 가지는 것이 탐지된 것에 기초하여, 상기 제1 QoS 플로우에 대한 액세스 측정이 제2 QoS 플로우에 적용된다고 결정되는 것을 특징으로 하는 방법.
- 제12항에 있어서,상기 제1 QoS 플로우에 대한 액세스 측정은, 상기 제1 QoS 플로우에 대한 패킷 손실 률(Packet Loss Rate: PLR) 측정을 포함하는 것을 특징으로 하는 방법.
- 제12항에 있어서,상기 액세스 측정을 수행하는 단계는,상기 제1 QoS 플로우를 통해 수신된 하향링크(Downlink: DL) 패킷의 수를 카운트할 것을 요청하는 요청 메시지를 User Equipment (UE)에게 전송하는 단계를 더 포함하는 방법.
- 제15항에 있어서,상기 액세스 측정을 수행하는 단계는,상기 수신된 DL 패킷의 수를 보고할 것을 요청하는 보고 요청 메시지를 상기 UE에게 전송하는 단계를 더 포함하는 방법.
- 제15항에 있어서,상기 액세스 측정을 수행하는 단계는,상기 수신된 DL 패킷의 수에 대한 정보를 포함하는 보고 응답 메시지를 상기 UE로부터 수신하는 단계를 더 포함하는 방법.
- 제17항에 있어서,상기 액세스 측정을 수행하는 단계는,상기 UE로부터 수신한 상기 수신된 DL 패킷의 수와 상기 UPF에 의해 전송된 DL 패킷의 수에 기초하여, 패킷 손실 률(Packet Loss Rate: PLR)을 계산하는 단계를 더 포함하는 것을 특징으로 하는 방법.
- 측정에 관련된 통신을 수행하는 User Plane Function (UPF) 노드에 있어서,적어도 하나의 프로세서; 및명령어(instructions)를 저장하고, 상기 적어도 하나의 프로세서와 동작가능하게(operably) 전기적으로 연결가능한, 적어도 하나의 메모리를 포함하고,상기 명령어가 상기 적어도 하나의 프로세서에 의해 실행되는 것에 기초하여 수행되는 동작은:제1 Quality of Service (QoS) 플로우에 대한 액세스 측정을 수행하는 단계;상기 제1 QoS 플로우에 대한 액세스 측정이 제2 QoS 플로우에 적용된다고 결정하는 단계; 및상기 제1 QoS 플로우에 대한 액세스 측정이 제2 QoS 플로우에 적용되는 것에 기초하여, 상기 제2 QoS 플로우에 대한 액세스 측정을 수행하지 않기로 결정하는 단계를 포함하는 UPF 노드.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US18/035,382 US20240015562A1 (en) | 2020-11-05 | 2021-11-02 | Qos flow-related measurement |
CN202180074660.2A CN116548006A (zh) | 2020-11-05 | 2021-11-02 | QoS流相关测量 |
KR1020237003847A KR102637605B1 (ko) | 2020-11-05 | 2021-11-02 | Qos 플로우에 관련된 측정 |
EP21889518.3A EP4243482A1 (en) | 2020-11-05 | 2021-11-02 | Qos flow-related measurement |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR10-2020-0146895 | 2020-11-05 | ||
KR20200146895 | 2020-11-05 | ||
KR20210018478 | 2021-02-09 | ||
KR10-2021-0018478 | 2021-02-09 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022098053A1 true WO2022098053A1 (ko) | 2022-05-12 |
Family
ID=81458092
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2021/015697 WO2022098053A1 (ko) | 2020-11-05 | 2021-11-02 | Qos 플로우에 관련된 측정 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20240015562A1 (ko) |
EP (1) | EP4243482A1 (ko) |
KR (1) | KR102637605B1 (ko) |
WO (1) | WO2022098053A1 (ko) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP7361504B2 (ja) * | 2019-06-17 | 2023-10-16 | シャープ株式会社 | Ue及びsmf |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019245344A1 (en) * | 2018-06-21 | 2019-12-26 | Samsung Electronics Co., Ltd. | Method and system for hplmn-based traffic control when ue is registered on different plmns |
US20200336940A1 (en) * | 2018-05-22 | 2020-10-22 | Lenovo (Singapore) Pte. Ltd. | Measuring access network performance for a multi-access data connection |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9306853B2 (en) * | 2006-07-06 | 2016-04-05 | Alcatel Lucent | Maintaining quality of service for multi-media packet data services in a transport network |
CN108811153A (zh) * | 2017-05-05 | 2018-11-13 | 华为技术有限公司 | 通信方法、集中式单元、分布式单元、基站及终端设备 |
EP4250868A3 (en) * | 2017-05-08 | 2023-11-01 | Huawei Technologies Co., Ltd. | Method and apparatus for moving between communications systems |
KR102115213B1 (ko) * | 2018-10-29 | 2020-05-26 | 에스케이텔레콤 주식회사 | 기지국장치 및 단말장치와, QoS 제어방법 |
-
2021
- 2021-11-02 US US18/035,382 patent/US20240015562A1/en active Pending
- 2021-11-02 EP EP21889518.3A patent/EP4243482A1/en active Pending
- 2021-11-02 WO PCT/KR2021/015697 patent/WO2022098053A1/ko active Application Filing
- 2021-11-02 KR KR1020237003847A patent/KR102637605B1/ko active IP Right Grant
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20200336940A1 (en) * | 2018-05-22 | 2020-10-22 | Lenovo (Singapore) Pte. Ltd. | Measuring access network performance for a multi-access data connection |
WO2019245344A1 (en) * | 2018-06-21 | 2019-12-26 | Samsung Electronics Co., Ltd. | Method and system for hplmn-based traffic control when ue is registered on different plmns |
Non-Patent Citations (3)
Title |
---|
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on access traffic steering, switch and splitting support in the 5G system architecture (Release 16)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.793, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V16.0.0, 19 December 2018 (2018-12-19), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 114, XP051591224 * |
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture Phase 2 (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.700-93, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V1.1.0, 29 October 2020 (2020-10-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 97, XP051961579 * |
ERICSSON, APPLE: "KI#1: Evaluation and interim conclusions for KI#1 (Steering Modes)", 3GPP DRAFT; S2-2008076, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Elbonia; 20201012 - 20201023, 25 October 2020 (2020-10-25), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051948274 * |
Also Published As
Publication number | Publication date |
---|---|
EP4243482A1 (en) | 2023-09-13 |
US20240015562A1 (en) | 2024-01-11 |
KR102637605B1 (ko) | 2024-02-19 |
KR20230037585A (ko) | 2023-03-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020080913A1 (ko) | 무선 통신 시스템에서 독립적인 네트워크 슬라이스별로 분리된 데이터 전송을 지원하는 방법 | |
WO2022050659A1 (ko) | 트래픽 제어 | |
WO2021162393A1 (ko) | 멀티 액세스 pdu 세션과 관련된 통신 | |
WO2020256425A1 (en) | Method and apparatus for supporting redundant pdu sessions | |
WO2020166881A1 (ko) | Ma pdu 세션 방법 및 장치 | |
WO2020149522A1 (ko) | Pdu 세션을 수립하는 ue 및 twif | |
WO2020060007A1 (ko) | 5g 이동통신에서 pdu 세션을 핸들링하는 방법 및 무선 기기 | |
WO2021225317A1 (ko) | 혼잡 제어에 관련된 통신 | |
WO2021177716A2 (ko) | 멀티캐스트와 관련된 통신 | |
WO2021162500A1 (ko) | 멀티 액세스 pdu 세션과 관련된 통신 | |
WO2021020933A1 (ko) | Plmn을 변경하기 위한 방안 | |
WO2021167304A1 (ko) | Ps 데이터 오프와 관련된 통신 | |
WO2020022716A1 (ko) | 무선 통신 시스템에서 데이터 전송 상태를 제어하는 방법 및 이를 위한 장치 | |
WO2020067733A1 (ko) | 비-3gpp 액세스에서 등록을 수행한 단말 및 그에 의해서 수행되는 방법 | |
WO2021187783A1 (en) | Support of service continuity between snpn and plmn | |
WO2022075562A1 (ko) | 멀티캐스트와 관련된 통신 | |
WO2021187881A1 (en) | Network support indication for ue provided pdu session pair information | |
WO2021187936A1 (ko) | 네트워크 슬라이스에 의한 통신 방법 | |
WO2021177734A1 (en) | Support of service continuity for handover between snpn and plmn | |
WO2021025246A1 (en) | Method and apparatus for handling security information between a wireless device and a network for a fast rrc release procedure in a wireless communication system | |
WO2020159286A1 (en) | Provision of rach related information for connection failure detection | |
WO2022035204A1 (ko) | 네트워크 슬라이스와 관련된 통신 | |
WO2021235779A1 (ko) | 멀티캐스트와 관련된 통신 | |
WO2020171312A1 (ko) | 5gs에서 always-on pdu 세션을 요청하는 방법 | |
WO2022098053A1 (ko) | Qos 플로우에 관련된 측정 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21889518 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 20237003847 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18035382 Country of ref document: US Ref document number: 202180074660.2 Country of ref document: CN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2021889518 Country of ref document: EP Effective date: 20230605 |