Apparatus and method for identifying service of application executed on user equipment in wireless communication system

Abstract

The present disclosure generally relates to a wireless communication system and, more specifically, to an apparatus and method for identifying a service of an application executed on a user equipment in a wireless communication system. Specifically, an operating method of a user equipment (UE) in a wireless communication system may comprise the steps of: transmitting application service policy information (ASPI) capability to a radio access network (RAN) or a core network (CN); receiving information about ASPI from the CN; and if uplink traffic has occurred on a specific application, identifying an application service identifier (ID) on the basis of the information about the ASPI, wherein, if there is the application service ID corresponding to the information about the ASPI, the uplink traffic may include the application service ID.

Description

Device and method for distinguishing services of applications running on user devices in wireless communication systems

[0001] The present disclosure relates generally to wireless communication systems, and more particularly to devices and methods for distinguishing services of applications running on user devices in wireless communication systems.

[0002] Mobile telecommunication refers to a communication system that grants mobility to users so that they can communicate data, voice, video, etc. without being restricted by location through UE. User equipment (UE) can access a data network (DN) (e.g., the Internet) through interworking with 5G Access (e.g., radio access network (RAN)) and 5G core network (e.g., access and mobility management function (AMF), session management function (SMF), or user plane function (UPF)). When a UE needs to transmit data to a DN for the first time, it performs a packet data unit (PDU) session creation procedure, and if the session is successfully established, it can transmit and receive user data with a server of the DN (e.g., YouTube).

[0003] In 5G, various technologies have been introduced (e.g., network slicing, URSP) that create new PDU sessions or QoS flows depending on the UE or service type (e.g., MBB, URLCC, MTC). However, millions of applications currently registered in app stores (e.g., email, social networks, music) are subject to the same QoS and charging policies in a single PDU session, and various methods to distinguish each application are also being introduced (e.g., Sponsored ID, Reflective QoS). However, existing technologies have the disadvantage of not being able to accurately distinguish the UE's usage pattern (e.g., not being able to distinguish between accesses via apps or web browsers for the same service) or being unable to reflect changes in the application server IP in real time.

[0004] Based on the discussion described above, the present disclosure provides a device and method for distinguishing services of applications running on a user device in a wireless communication system.

[0005] In addition, the present disclosure provides a device and method for distinguishing application services by distinguishing application service IDs according to user traffic in a wireless communication system.

[0006] Additionally, the present disclosure provides a device and method for identifying ASPI (application service policy information) based on an application service ID in a wireless communication system.

[0007] Additionally, the present disclosure provides a device and method for performing policy and charging control based on ASPI in a wireless communication system.

[0008] In addition, the present disclosure provides a device and method for easily distinguishing various applications within the same PDU (protocol data unit) in a wireless communication system and providing independent PCC (policy and charging control) for multiple applications.

[0009] In addition, the present disclosure provides a device and method for sharing ASPI between a user equipment (UE), a radio access network (RAN), and a core network (CN) in a wireless communication system.

[0010] In addition, the present disclosure provides a device and method for processing user traffic by including an application service ID based on a shared ASPI in a wireless communication system.

[0011] According to various embodiments of the present disclosure, a method of operating a user equipment (UE) in a wireless communication system includes the steps of transmitting an ASPI (application service policy information) Capability to a radio access network (RAN) or a core network (CN), receiving information about the ASPI from the CN, identifying an application service identifier (ID) based on the information about the ASPI when uplink traffic for a specific application occurs, and including the application service ID in the uplink traffic when there is an application service ID corresponding to the information about the ASPI.

[0012] According to various embodiments of the present disclosure, a method of operating a radio access network (RAN) in a wireless communication system may include a process of receiving application service policy information (ASPI) Capability from a user equipment (UE), a process of transmitting the ASPI Capability to a core network (CN), a process of receiving information about ASPI from the CN, a process of identifying a policy for user traffic based on the information about ASPI, a process of distinguishing an application service ID and transmitting the application service ID to a user plane function (UPF) when user traffic is received from the UE, and a process of distinguishing an application service ID and transmitting the application service ID to the UE when user traffic is received from the UPF.

[0013] According to various embodiments of the present disclosure, in a wireless communication system, a user equipment (UE) includes a transceiver and a processor operably connected to the transceiver, and the processor transmits an application service policy information (ASPI) Capability to a radio access network (RAN) or a core network (CN), receives information about the ASPI from the CN, identifies an application service identifier (ID) based on the information about the ASPI when uplink traffic for a specific application occurs, and includes the application service ID in the uplink traffic when there is an application service ID corresponding to the information about the ASPI.

[0014] The device and method according to various embodiments of the present disclosure enable independent policy and charging control according to ASPI by identifying ASPI (application service policy information) based on an application service identifier (ID) according to user traffic.

[0015] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0016] FIG. 1 illustrates the structure of a 5G system according to various embodiments of the present disclosure.

[0017] FIG. 2 illustrates an example of a case where different applications within the same PDU session must be distinguished, according to various embodiments of the present disclosure.

[0018] FIG. 3 illustrates an example of a method for solving the case of FIG. 2 according to various embodiments of the present disclosure.

[0019] FIG. 4 illustrates an example of a service classification method using an application service ID according to one embodiment of the present disclosure.

[0020] FIG. 5 illustrates an example of the configuration and connection relationship of a UE, a RAN, an AMF, an SMF, a PCF, and a UPF according to an embodiment of the present disclosure.

[0021] FIG. 6 illustrates an example of application service ID and application service policy information according to one embodiment of the present disclosure.

[0022] FIG. 7 illustrates an operation method for control plane processing of a UE according to one embodiment of the present disclosure.

[0023] FIG. 8 illustrates an operational method for processing uplink traffic in a user plane of a UE according to one embodiment of the present disclosure.

[0024] FIG. 9 illustrates an operation method of a control plane of a UPF according to an embodiment of the present disclosure.

[0025] FIG. 10 illustrates an operation method for processing uplink traffic of a UPF according to an embodiment of the present disclosure.

[0026] FIG. 11 illustrates an operation method for downlink traffic of a UPF according to an embodiment of the present disclosure.

[0027] FIG. 12 illustrates an example of a signal flow diagram of a UE, a RAN, and a CN according to an embodiment of the present disclosure.

[0028] FIG. 13 illustrates a configuration diagram of a terminal in a wireless communication system according to various embodiments of the present disclosure.

[0029] FIG. 14 illustrates a configuration of a network entity in a wireless communication system according to various embodiments of the present disclosure.

[0030] The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.

[0031] The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.

[0032] The various embodiments of the present disclosure described below illustrate a hardware-based approach as an example. However, since the various embodiments of the present disclosure include techniques utilizing both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.

[0033] The present disclosure relates to a device and method for distinguishing services of applications running on a user device in a wireless communication system. Specifically, the present disclosure describes a technique for performing independent policy and charging control according to ASPI (Application Service Policy Information) by identifying ASPI based on an application service ID (ASPID) corresponding to user traffic in a wireless communication system.

[0034] The terms used in the following description, including terms referring to signals, channels, control information, network entities, and device components, are provided for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms with equivalent technical meanings may be used.

[0035] Additionally, while this disclosure describes various embodiments using terminology used in certain communication standards (e.g., 3rd Generation Partnership Project (3GPP)), these are merely illustrative examples. The various embodiments of this disclosure can be easily modified and applied to other communication systems.

[0036] The present disclosure relates to an application quality of service operation of a user device, and related processing techniques, and to an operation of a user device that executes application-based QoS (Quality of Service), policy, charging, or fee, and separation or selection processing required for B5G (beyond 5G), 6G, and commercial services.

[0037] Wireless communication, or mobile telecommunication, is a communication system that allows users to communicate data, voice, and video regardless of location through their devices.

[0038] A user equipment (UE) can access a data network (DN) (e.g., the Internet) through interworking with a 5G access (e.g., a radio access network (RAN)) and a 5G core network (CN) (e.g., an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), etc.). When a UE needs to transmit data to a DN for the first time, it performs a packet data unit (PDU) session creation procedure, and if the session is successfully established, it can transmit and receive user data with a server of the DN (e.g., YouTube).

[0039] In the 5G system, various technologies (e.g., network slicing, URSP (user plane separation)) are being introduced to create new PDU sessions or QoS flows depending on the type of UE or service (e.g., MBB (mobile broadband), URLCC (ultra-reliable and low latency communication), MTC (massive machine type communication)). However, applications currently registered in app stores (e.g., email, social network service, music service application, etc.) are subject to the same QoS or charging policy in one PDU session, and various methods (e.g., Sponsored ID, Reflective QoS) are being introduced to distinguish each application. However, existing technologies have the disadvantage of not being able to accurately distinguish the usage pattern of user devices (e.g., not being able to distinguish between accesses via apps or web browsers for the same service), or it being difficult to reflect in real time when the application server IP (internet protocol) changes.

[0040] Accordingly, the present disclosure proposes a new interworking method between UE, RAN, and CN, and can present a method for easily distinguishing various applications within the same PDU session and independently applying PCC (policy and charging control) to multiple applications.

[0041] To this end, the present disclosure first newly defines ASPI (application service policy information) and defines a method for transmitting, negotiating, or utilizing ASPI between UE, RAN, and CN.

[0042] Second, we propose a new processing method in which the UE receives ASPI from the CN when connecting to the network, and the UE includes the application service ID identified based on the ASPI in user traffic when transmitting or receiving application-related data.

[0043] Third, the RAN or CN can identify the ASPI from the application service ID of the user traffic and perform independent policy and charging control (PCC), monitoring, and analytics based on the ASPI.

[0044] Fourth, it may include defining the subject, method, and configuration for transmitting ASPI to the control plane (CP) between the UE and the AMF, selecting or performing a message processing method according to the state of the UE, including a method for including an application service ID in the user plane (UP) of the UE based on the message processing method, a method for mapping uplink traffic and downlink traffic to the same application service ID, and a validation check method for preventing illegal use.

[0045] A detailed explanation related to this is provided in Figures 2 to 4.

[0046] FIG. 1 illustrates the structure of a 5G system according to various embodiments of the present disclosure.

[0047] The 5G system of Fig. 1 is composed of an architecture based on interaction between network functions (NFs).

[0048] The core network of a 5G system may include various entities. Specifically, the Access and Mobility Management Function (AMF) can manage the access and mobility of UEs. Furthermore, the AMF can perform functions such as managing non-access stratum (NAS) security. Furthermore, the AMF can handle the mobility of UEs in an idle state.

[0049] The session management function (SMF) can manage sessions. Additionally, the SMF can allocate UE IP (Internet protocol) addresses and control PDU (protocol data unit) sessions.

[0050] The policy control function (PCF) can perform a policy control function. It may also include a user plane function (UPF) that performs a user plane control function. The UPF, as a gateway for transmitting and receiving data, can perform all or part of the user plane functions of the serving gateway (S-GW) and packet data network gateway (P-GW) of previous mobile communication systems (4G). The UPF can also perform a PDU handling function. It may also include an application function (AF) that controls application functions. The AF can be a function for providing multiple services to the UE. It may also include a unified data management (UDM) that manages integrated data. Here, the UDM can perform a function for managing subscriber information.

[0051] The UE (user equipment) may be a UE that receives data.

[0052] (R)AN ((radio) access network) may be a component of 5GS that connects UEs to CNs and DNs. AN may refer to a broader access infrastructure that includes both wireless and wired networks. (R)AN may enable various services and applications.

[0053] A DN (data network) is a communications network designed to efficiently transmit and exchange digital data. It uses packet switching to divide data into small packets and transmit them independently over the network.

[0054] NSSF (network slice selection function) selects and manages the most suitable network slice for a user or service through network slicing.

[0055] NEF (network exposure function) provides service providers with an interface to access network resources and functions, enabling the development and delivery of new services and applications.

[0056] NRF (network repository function) manages the location and availability information of services and resources within the network, enabling other network functions to easily find the services and resources they need.

[0057] Figure 1 can illustrate the interaction between network functions (NFs) and NF services within NFs described by point-to-point reference points between the two NFs.

[0058] Referring to Figure 1, N1 may be a reference point between the UE and the AMF. N2 may be a reference point between the (R)AN and the AMF. N3 may be a reference point between the (R)AN and the UPF. N4 may be a reference point between the SMF and the UPF. N6 may be a reference point between the UPF and the DN. N9 may be a reference point between two UPFs.

[0059] Additionally, service-based interfaces (SBIs) are defined for specific network functions, for example, the NSSF interface can be defined as Nnssf, the NEF interface as Nnef, the NRF interface as Nnrf, the PCF interface as Npcf, the UDM interface as Nudm, the AF interface as Naf, the AUSF interface as Nausf, the AMF interface as Namf, the SMF interface as Nsmf, and the PCF interface as Npcf.

[0060] The structure illustrated in FIG. 1 is merely an example, and a CN may include a greater number of other network entities for providing mobile communication services. Furthermore, the names of the network entities and interfaces described above are merely examples, and the names and functions of the network entities and the names of the interfaces may be designated with any number of different names. In other words, the contents of the present disclosure described below should not be construed as limited to the definitions and descriptions of the network functions and interfaces illustrated in FIG. 1.

[0061] FIG. 2 illustrates an example of a case where different applications within the same PDU session must be distinguished, according to various embodiments of the present disclosure.

[0062] [Case 1 (not shown)]

[0063] Case 1 is when different applications within the same PDU session need to be distinguished, i.e. services controlled by the same QoS (e.g. millions of apps using the internet data network) need to be distinguished without allocating a new session (PDU session).

[0064] For example, millions of applications currently used by mobile users are subject to the same QoS control and are serviced as a single PDU Session, PDN Session, QoS Flow, or bearer. Currently, it is difficult to completely separate user traffic for each application in a network, but the present disclosure separates user traffic for each application and enables differentiated policy and charging control (PCC).

[0065] [Case 2 ((a) in Fig. 2)]

[0066] Referring to (a) of Fig. 2, it illustrates a case where services using the same service or domain name cannot be distinguished according to the access method.

[0067] A single application can provide multiple services. It can also provide linked services. However, current technology doesn't allow for distinguishing between accessing a linked service from directly accessing a service. In other words, in Figure 2 (a), it's impossible to distinguish between ① access via the application (app) and ② direct access to the content server. Therefore, distinguishing between ① and ② is necessary to establish independent policies based on usage method.

[0068] For example, the proliferation of AI has led to the emergence of personal AI assistant applications that can provide linked services such as weather or news. However, current technology does not allow for a way to distinguish between accessing weather services through these applications and directly accessing them.

[0069] [Case 3 ((b) of Fig. 2)]

[0070] Referring to (b) of Fig. 2, it illustrates a case where services cannot be distinguished when they have different applications or the same domain name (e.g., the same cache server, or a 3rd party API such as an advertising banner).

[0071] When different applications use the same service, it may correspond to (b) in Figure 2. ① When App#1 uses a third-party service and ② When App#2 uses a third-party service, ① and ② need to be distinguished to ensure independent policies for App#1 and App#2. For example, free applications generate revenue through advertising banners. However, advertising API providers (e.g., Google) are limited, and different applications can use the same API. As another example, different applications may place content servers near users for low-latency services and may use cache servers from specialized content delivery network (CDN) providers or hyperscalers. In this case, even though they are different applications, they share the same CDN server IP, making it impossible to distinguish between services.

[0072] [Case 4 (not shown)]

[0073] Case 4 is a case where it is necessary to distinguish between various applications within the same PDU session, and this may mean that it is impossible to distinguish between them without taking separate measures when the application server IP changes.

[0074] For example, leveraging cloud resources is crucial in 5G environments, and this trend is expected to accelerate further in the 6G era. In cloud environments, the IP address of application servers can change frequently. While CNs can transmit their IP address from AF to NEF, this may require specific functional implementation for each application. Furthermore, when IP addresses change, they must be transmitted to the CN's NF as well as to the UE as needed (e.g., QosRule changes). This is not a preferred approach, as it results in UE paging and additional signaling.

[0075] The present disclosure primarily aims to address Cases 1 through 4. First, differentiated PCC can be performed by separating user traffic by application. Second, independent PCC can be performed by separating user traffic by access method. Third, independent PCC can be performed by separating user traffic by application. Fourth, functional operation can be enabled without additional signaling when application service IPs change. Finally, from the operator's perspective, numerous applications controlled by the same QoS can be distinguished without additional capacity investment (e.g., PDU sessions), and differentiated policies and billing can be implemented for each application. Furthermore, by facilitating monitoring for each application, troubleshooting and voice of customer (VoC) response can be facilitated without separate probe equipment.

[0076] FIG. 3 illustrates an example of a method for solving the case of FIG. 2 according to various embodiments of the present disclosure.

[0077] [Service classification method using new resources (Fig. 3 (a))]

[0078] FIG. 3 (a) illustrates a service classification scheme (e.g., URSP, network slice) using a new resource (PDU session) according to various embodiments of the present disclosure.

[0079] Figure 3 (a) cannot solve Case 1 described in Figure 2 because it performs PCC by classifying user traffic by PDU session unit in UPF. That is, it is problematic because it is impossible to distinguish services subject to the same QoS control, and an increase in PDU sessions requires additional capacity investment in the UE, RAN, and CN.

[0080] [Service classification method using new QoS flow (Fig. 3 (b))]

[0081] FIG. 3 (b) illustrates a service classification scheme (e.g., Reflective QoS) using a new QoS flow according to various embodiments of the present disclosure.

[0082] Figure 3 (b) cannot resolve cases 2, 3, and 4 described in Figure 2 because it performs PCC by classifying user traffic by QoS flow unit in UPF. For example, it is possible to classify QoS flows based on 5-tuple, and there is a problem that it is difficult to immediately reflect a change in service IP in UE, RAN, or CN.

[0083] [CN's own method for distinguishing services ((c) of Figure 3)]

[0084] Figure 3 (c) illustrates a method for distinguishing services on its own in CN (e.g., Sponsored ID, UPF self-embedded technology) according to various embodiments of the present disclosure.

[0085] Fig. 3 (c) can perform PCC by distinguishing user traffic by the destination IP or domain name of the user traffic in the UPF. However, since Fig. 3 (c) performs PCC by distinguishing user traffic by the application service ID in the UPF, Cases 2 and 3 described in Fig. 2 cannot be resolved by distinguishing the service data flow (SDF) based on 5-tuple alone. In addition, Case 4 described in Fig. 2 can be reflected in real time through NEF, but each service provider must provide the function, so Case 4 cannot be completely resolved.

[0086] FIG. 4 illustrates an example of a service classification method using an application service ID according to one embodiment of the present disclosure.

[0087] Referring to FIG. 4, application service IDs can be transmitted in user traffic sections of UE, RAN, and UPF, and services can be distinguished based on the application service IDs. In other words, PCC can be performed by distinguishing user traffic with application service IDs in UPF. Specifically, even in the case of one PDU session (PDU session #1) and one QoS flow (QoS flow #1), by assigning a first application service ID (App service id #1) and a second application service ID (App service id #2) to a first service (service #1) and a second service (service #2) operating in the UE, respectively, PCC can be performed by distinguishing user traffic with the first and second application service IDs in UPF. Through the method of FIG. 4, the problems of cases 1 to 4 of FIG. 2 can be overcome.

[0088] Hereinafter, the drawings describe the present disclosure included in FIG. 4 in more detail. Hereinafter, the UE registration referred to in the present disclosure may be the UE registration procedure described in 3GPP TS 23.502-4.2.2. In addition, the PDU session procedure referred to in the present disclosure may be the PDU session procedure described in 3GPP TS 23.502-4.3. In addition, the 5-tuple referred to in the present disclosure may mean a set of values ​​for uniquely identifying a data flow in a network. The 5-tuple may include a source IP address, a source port number, a destination IP address, a destination port number, and a transmission protocol.

[0089] Additionally, in the present disclosure below, user traffic may include uplink user traffic or downlink user traffic.

[0090] Additionally, in the present disclosure below, a signal plane or a signal path may be used with the same meaning as a control plane or a control path.

[0091] FIG. 5 illustrates an example of the configuration and connection relationship of a UE, a RAN, an AMF, an SMF, a PCF, and a UPF according to an embodiment of the present disclosure.

[0092] Referring to FIG. 5, the UE may include a control plane (CP) processing unit, an OS / APP interworking processing unit, and a user plane (UP) processing unit.

[0093] In one embodiment, the control plane processing unit of the UE may transmit ASPI Capability in the UE registration procedure and PDU session procedure. In addition, the control plane processing unit may receive ASPI information from the CN and manage the creation, deletion, or modification of the information.

[0094] In one embodiment, the OS / APP interworking processing unit of the UE may map a specific application and application service ID based on ASPI information stored or managed by the control plane processing unit.

[0095] In one embodiment, the user plane processing unit of the UE may include an application service ID in user traffic transmitted by an application based on information mapped by the OS / App interworking processing unit. Furthermore, when receiving downlink traffic, the UE may transmit traffic to the application based on the received application service ID.

[0096] The RAN may include a control plane processing unit, a policy control / analitics unit, and a user plane processing unit.

[0097] According to one embodiment, the control plane processing unit of the RAN may store or manage ASPI Capabilities transmitted from the UE during the UE's registration or PDU session procedure and transmit them to the CN. The control plane processing unit of the RAN may receive ASPI information from the CN and manage the content being created, deleted, or changed.

[0098] In one embodiment, the RAN's policy control / analysis unit can identify policies for user traffic based on ASPI information stored or managed by the control plane processing unit. Based on the identified policy or analysis results, specific actions (e.g., drop or pass, overload control, priority scheduling) can be performed.

[0099] In one embodiment, the user plane processing unit of the RAN can identify an application service ID from user traffic received from the UE and transmit it to the UPF. The user plane processing unit of the RAN can identify an application service ID from user traffic received from the UPF and transmit it to the UE. The user plane processing unit of the RAN can transmit information about the transmitted and received user traffic to the policy control / analysis unit, so that new policies can be reflected based on the analysis results.

[0100] The UPF may include a control plane processing unit, a policy and charging control unit, an analytics / validation unit, and a user plane processing unit.

[0101] The control plane processing unit of the UPF can receive ASPI information from the SMF and process creation, deletion, or modification. The control plane processing unit of the SMF can store the format and value of the application service ID of the ASPI. The control plane processing unit of the UPF can manage the mapping relationship with a globally unique value within the UPF when the application service ID transmitted to the UE is a temporary value.

[0102] UPF's policy and charging control can perform actions (e.g., drop, pass, overload control, QoS control, etc.) based on stored ASPIs. Furthermore, UPF's policy and charging control unit can generate charging information based on usage by application service ID collected by the user plane processing unit and transmit it to the SMF.

[0103] The UPF's analytics / validation unit can analyze usage based on application service IDs per subscriber or per PDU session, thereby redefining actions. Furthermore, analytics / validation can perform validation checks and block traffic if a UE transmits an incorrect (malicious) application service ID. Validity checks can be performed through correlation analysis with user traffic from other subscribers, destination IP addresses, and application service ID mapping relationships.

[0104] The user plane processing unit of the UPF can distinguish application service IDs from user traffic received from the RAN. The user plane processing unit can maintain a mapping relationship between the application service ID received from the UE and 5-tuple information. The user plane processing unit of the UPF can identify the application service ID based on the mapping relationship when downlink traffic occurs from the DN. The identified application ID can be included when traffic is transmitted to the RAN. In addition, the user plane processing unit can collect usage data and send it to the policy and charging control unit and the analysis / validation unit. New policies can be reflected based on the analysis results of the policy and charging control unit and the analysis / validation unit.

[0105] AMF may include a control plane processing unit.

[0106] In one embodiment, the control plane processing unit of the AMF may receive APSI information from the PCF and transmit it to the RAN or UE. The control plane processing unit of the AMF may control whether to transmit or receive ASPI information based on ASPI Capability.

[0107] The SMF may include a control plane processing unit and an application service ID policy decision unit.

[0108] According to one embodiment, the control plane processing unit of the SMF may receive ASPI information from the PCF and transmit the ASPI information to the RAN, the UE, or the UPF. The control plane processing unit of the SMF may control whether to transmit or receive ASPI information based on ASPI Capability.

[0109] In one embodiment, the application service ID policy decision of the SMF may locally configure ASPI information and may add, change, or delete ASPI information received from the PCF.

[0110] The PCF may include a control plane processing unit and an application service ID policy decision unit.

[0111] In one embodiment, the control plane processing unit of the PCF may receive ASPI requests from the AMF or SMF and perform a response role.

[0112] In one embodiment, the application service ID policy decision unit of the PCF may determine the final policy based on information transmitted from the AMF or SMF.

[0113] In one embodiment, the policy of the application service ID can be configured locally and can also be transmitted from an external NF.

[0114] In one embodiment, PCF may have policies per subscriber, per data network name (DNN), or per single network slice selection assistance information (SNASSAI).

[0115] The control plane processing of the UE and the control plane processing unit of the RAN can transmit and receive ASPI using the control path.

[0116] Additionally, the control plane processing unit of the RAN and the control plane processing unit of the AMF can transmit and receive ASPI using the control path.

[0117] In addition, the control plane processing unit of the AMF can transmit and receive ASPI using the control plane processing unit and control path of the SMF, and the control plane processing unit of the AMF can transmit and receive ASPI using the control plane processing unit and control path of the PCF.

[0118] Additionally, the control plane processing unit of the SMF can transmit and receive ASPI using the control plane processing unit of the PCF and the control path.

[0119] The application service ID identified based on ASPI can be transmitted and received through the data path between the user plane processing unit of the UE and the user plane processing unit of the RAN.

[0120] Additionally, the application service ID can be transmitted and received through the data path between the user plane processing unit of the RAN and the user plane processing unit of the UPF.

[0121] FIG. 6 illustrates an example of application service ID and application service policy information according to one embodiment of the present disclosure.

[0122] Referring to FIG. 6, the application service ID may be used to distinguish the service of an application running on the UE. The application service ID may be in the form of a temporary unique ID or a permanent unique ID.

[0123] A temporary unique ID is a unique ID that can identify a single application and can be valid within a PDU session or QoS flow. The RAN and UPF can manage the mapping between temporary unique IDs and applications.

[0124] A persistent unique ID can be a universally unique identifier (UUID), or a combination of an operating system ID (OSId) and an application ID (AppID). However, it is not limited to just a UUID or OSId and can include various other forms.

[0125] Referring to FIG. 6, application service policy information may be policies such as application service ID selection methods, actions, transmission layers, and patterns. The UE, RAN, and CN share ASPI with each other through a control path, and the UE, RAN, or CN may include or process the application service ID when transmitting user traffic based on the ASPI.

[0126] Specific details about the application service ID and application service policy information are summarized in Figure 6.

[0127] FIG. 7 illustrates an operation method for control plane processing of a UE according to one embodiment of the present disclosure.

[0128] Referring to FIG. 7, a UE may request a UE registration or PDU session procedure from a CN (701). In one embodiment, the UE registration or PDU session procedure request may be received by an AMF included in the CN. The UE registration referred to in operation (701) may be the UE registration procedure described in 3GPP TS 23.502-4.2.2. The PDU session procedure referred to in operation (701) may be the PDU session procedure described in 3GPP TS 24.502-4.3.

[0129] In operation (703), the UE may transmit ASPI Capability to the RAN or CN.

[0130] In operation (705), the UE may receive an ASPI table from the CN.

[0131] In operation (707), the UE may store or manage the received ASPI table.

[0132] FIG. 8 illustrates an operational method for processing uplink traffic in a user plane of a UE according to one embodiment of the present disclosure.

[0133] Referring to FIG. 8, the UE can identify applicable ASPI (801).

[0134] In operation (803), the UE may identify a transmission pattern (803). In one embodiment, the transmission pattern may refer to a first uplink packet, all packets, etc.

[0135] In operation (805), the UE may identify a transport layer. According to one embodiment, the transport layer may include service data adaptation protocol (SDAP), packet data convergence protocol (PDCP), internet protocol (IP), etc.

[0136] In operation (807), the UE may identify an application service type. In one embodiment, the application service type may include a temporary ID or a permanent ID.

[0137] In operation (809), the UE can identify the application service ID.

[0138] In operation (811), the UE may include an application service ID in user traffic based on at least one of a transmission pattern, a transmission layer, or an application service type.

[0139] FIG. 9 illustrates an operation method of a control plane of a UPF according to an embodiment of the present disclosure.

[0140] Referring to FIG. 9, UPF can receive ASPI values ​​from SMF (901).

[0141] UPF can manage ASPI tables (903). In one embodiment, managing ASPI tables may include adding, deleting, or modifying the contents of ASPI tables.

[0142] UPF can form an ASPI key value and a mapping table when the application service ID is a temporary unique ID (905).

[0143] FIG. 10 illustrates an operation method for processing uplink traffic of a UPF according to an embodiment of the present disclosure.

[0144] Referring to FIG. 10, the UPF can identify an application service ID from an uplink packet received from the RAN (1001).

[0145] UPF can identify ASPI tables based on application service ID (1003).

[0146] UPF can perform validation or analysis on application service IDs (1005).

[0147] UPF can implement policies and actions based on ASPI's actions (1007).

[0148] UPF can collect usage by application service ID and transmit to SMF based on the collected usage (1009).

[0149] UPF can generate a mapping table based on information about the application service ID and packet (1011). In one embodiment, the information about the packet may include 5-tuple information about the packet.

[0150] FIG. 11 illustrates an operation method for downlink traffic of a UPF according to an embodiment of the present disclosure.

[0151] Referring to FIG. 11, the UPF can identify an application service ID based on information about a downlink packet received from a DN and a mapping table (1101). According to one embodiment, the information about the downlink packet may include 5-tuple information.

[0152] In operation (1103), UPF can identify the ASPI table based on the application service ID (1103).

[0153] In operation (1105), UPF can perform analysis on application service ID (1105).

[0154] In operation (1107), UPF can perform policies and charges according to ASPI's actions (1107).

[0155] In operation (1109), UPF can collect usage by application service ID and transmit the collected usage to SMF (1109).

[0156] In operation (1111), the UPF may transmit downlink traffic to the RAN. According to one embodiment, when the UPF transmits downlink traffic to the RAN, it may transmit it including an application service ID (1111).

[0157] FIG. 12 illustrates an example of a signal flow diagram of a UE, a RAN, and a CN according to an embodiment of the present disclosure.

[0158] Referring to FIG. 12, the US may request a registration procedure or a PDU session establishment procedure from the RAN or CN (1201). In one embodiment, operation (1201) may be requested from the UE to the CN via the RAN. In one embodiment, the registration procedure or the PDU session establishment procedure may be received by the AMF of the CN.

[0159] In operation (1201), when the UE performs a registration procedure, the UE may transmit ASPI Capability information regarding whether the CN supports the application service ID to the RAN, AMF, or PCF. The access and mobility management services of the PCF may identify the ASPI based on the ASPI Capability and subscriber profile of the UE and transmit it to the RAN or the UE.

[0160] In operation (1201), when the UE requests a PDU session establishment procedure, the UE may transmit ASPI Capability information about whether the CN supports the application service ID to the RAN, SMF, or PCF.

[0161] The CN may transmit ASPI from the UE or the RAN (1203). In one embodiment, the ASPI transmitted to the UE may be transmitted to the UE via the RAN. In one embodiment, the entity transmitting the ASPI from the CN may be the AMF. The AMF may transparently transmit the ASPI value, and the RAN or the UE may store the ASPI value and perform actions according to policies based on the ASPI value.

[0162] The UE can identify the application service ID when executing an application (1205). In one embodiment, the application service ID can be identified based on ASPI information contained within the application. The process of identifying the application service ID may include identifying the application service ID when the UE executes a new or existing application.

[0163] The UE may transmit uplink traffic to the RAN or CN (1207). In one embodiment, the uplink traffic transmitted to the CN may be transmitted via the RAN. In one embodiment, the uplink traffic may include an application service ID.

[0164] In one embodiment, the application service ID may be included in SDAP, PDCP, or another layer. That is, the RAN may receive uplink traffic, extract the application service ID from SDAP, PDCP, or another layer, and identify the ASPI. The RAN may perform an operation according to the ASPI and transmit the uplink traffic to the UPF. In one embodiment, the RAN and UPF sections may use GTP-U, and the application service ID may be included in GTP-U or another layer.

[0165] In another embodiment, if there is no ASPI corresponding to the application, the UE may not include the application service ID in the uplink traffic. Accordingly, in this case, the UE, RAN, or UPF may normally process the uplink traffic according to the existing method.

[0166] The UPF can process uplink traffic (1209). In one embodiment, the UPF can extract the application service ID from GTP-U or another layer and identify the ASPI. The UPF can perform policy and charging control based on the ASPI and local configuration. Furthermore, operation (1209) can include a process in which the UPF manages a mapping relationship between information about a received packet and the application service ID. In one embodiment, the information about the packet can include a 5-tuple for the packet.

[0167] The UPF can process downlink traffic (1211). Operation (1211) may include a process in which the UPF, upon receiving downlink traffic, distinguishes an application service ID based on information about the packet and the mapping relationship stored in operation (1209). In addition, operation (1211) may include a process in which the UPF performs policy and charging control based on ASPI and local configuration.

[0168] The UPF may transmit downlink traffic to the RAN or the UE (1213). In one embodiment, the downlink traffic transmitted to the UE may be transmitted to the UPF via the RAN. In one embodiment, the downlink traffic may include an application service ID.

[0169] In one embodiment, the RAN may extract the application service ID from the GTP-U or other layer and identify the ASPI. After identifying the ASPI, the RAN may include the application ID in the SDAP, PDCP, or other layer of the downlink traffic.

[0170] In another embodiment, if there is no ASPI corresponding to the application, the UE may not include the application service ID in the downlink traffic. Accordingly, in this case, the UE, RAN, or UPF may normally process the downlink traffic according to the existing method.

[0171] FIG. 13 illustrates a configuration diagram of a terminal in a wireless communication system according to various embodiments of the present disclosure. The configuration illustrated in FIG. 13 may be understood as the configuration of a terminal (1300). Terms such as "... unit" and "... unit" used hereinafter refer to a unit that processes at least one function or operation, and may be implemented using hardware, software, or a combination of hardware and software.

[0172] Referring to FIG. 13, the UE may include a communication unit (1310), a storage unit (1320), and a control unit (1330).

[0173] The communication unit (1310) may perform functions for transmitting and receiving signals via a wireless channel. For example, the communication unit (1310) may perform a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the communication unit (1310) may generate complex symbols by encoding and modulating a transmission bit stream. When receiving data, the communication unit (1310) may restore a reception bit stream by demodulating and decoding the baseband signal. In addition, the communication unit (1310) may upconvert a baseband signal to an RF band signal and transmit it through an antenna, and downconvert an RF band signal received through the antenna to a baseband signal. For example, the communication unit (1310) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.

[0174] Additionally, the communication unit (1310) may include multiple transmit / receive paths. Furthermore, the communication unit (1310) may include at least one antenna array composed of multiple antenna elements. In terms of hardware, the communication unit (1310) may be composed of digital circuits and analog circuits (e.g., a radio frequency integrated circuit (RFIC)). Here, the digital circuits and analog circuits may be implemented in a single package. Additionally, the communication unit (1310) may include multiple RF chains. Furthermore, the communication unit (1310) may perform beamforming.

[0175] The communication unit (1310) transmits and receives signals as described above. Accordingly, all or part of the communication unit (1310) may be referred to as a "transmitter," a "receiver," or a "transceiver." Furthermore, in the following description, transmission and reception performed via a wireless channel may be used to mean that the communication unit (1310) performs the processing described above.

[0176] The storage unit (1320) can store data such as basic programs, application programs, and configuration information for the operation of the UE. The storage unit (1320) can be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the storage unit (1320) can provide stored data upon request from the control unit (1330).

[0177] The control unit (1330) can control the overall operations of the UE. For example, the control unit (1330) can transmit and receive signals through the communication unit (1310). In addition, the control unit (1330) can record and read data in the storage unit (1320). The control unit (1330) can perform the functions of the protocol stack required by the communication standard. To this end, the control unit (1330) can include at least one processor or microprocessor, or can be a part of a processor. In addition, a part of the communication unit (1310) and the control unit (1330) can be referred to as a communication processor (CP).

[0178] According to various embodiments, the control unit (1330) can control to perform operations according to various embodiments of the UE described above.

[0179] FIG. 14 illustrates the configuration of a network entity in a wireless communication system according to various embodiments of the present disclosure. The network entity of the present disclosure is a concept that includes a network function depending on the system implementation. The terms “unit” and “unit” used hereinafter mean a unit that processes at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software. The network entity (1400) according to various embodiments of the present disclosure may include a communication unit (1410), a storage unit (1420), and a control unit (1430) that controls the overall operation of the network entity (1400). The communication unit (1410) transmits and receives signals with other network entities. Accordingly, all or part of the communication unit (1410) may be referred to as a 'transmitter (1411)', a 'receiver (1413)', or a 'transceiver / transceiver (1410)'. The storage unit (1420) stores data such as basic programs, application programs, and setting information for the operation of the network entity (1400). The storage unit (1420) may be configured as a volatile memory, a non-volatile memory, or a combination of volatile memory and non-volatile memory. In addition, the storage unit (1420) provides the stored data according to a request of the control unit (1430). The control unit (1430) controls the overall operations of the network entity (1400). For example, the control unit (1430) transmits and receives signals through the communication unit (1410). Additionally, the control unit (1430) records and reads data in the storage unit (1420). In addition, the control unit (1430) can perform the functions of the protocol stack required by the communication standard.To this end, the control unit (1430) may include a circuit, an application-specific circuit, at least one processor or microprocessor, or may be a part of a processor. In addition, a part of the communication unit (1410) and the control unit (1430) may be referred to as a CP (communication processor). The control unit (1430) may control the network entity (1400) to perform any one of the operations of various embodiments of the present disclosure. The communication unit (1410) and the control unit (1430) do not necessarily have to be implemented as separate modules, but may of course be implemented as a single component in the form of a single chip or software block. The communication unit (1410), the storage unit (1420), and the control unit (1430) may be electrically connected. In addition, the operations of the network entity (1400) can be realized by providing a storage unit (1420) storing the corresponding program code within the network entity (1400). The network entity (1400) includes a network node illustrated in FIG. 1, and may be any one of RAN, AMF, SMF, UPF, NF, NEF, NRF, CF, NSSF, UDM, AF, AUSF, SCP, UDSF, context storage, OAM, EMS, configuration server, and ID (identifier) ​​management server.

[0180] According to various embodiments of the present disclosure, a UE can transmit ASPI Capability to a RAN or CN during a registration or PDU session procedure, and can receive and manage ASPI information from a CN, in a manner that the UE shares ASPI (app service policy information) with a RAN or CN through a control plane, and includes an application service ID in a user plane based on the ASPI.

[0181] In one embodiment, the UE may identify an application service ID according to an ASPI policy when generating uplink traffic for a specific application and include the application service ID value in the uplink traffic.

[0182] According to one embodiment, the UE may transmit traffic to a corresponding application based on the received application service ID when receiving downlink traffic.

[0183] In one embodiment, the ASPI may identify an application and include a method for selecting an application service ID, actions taken when transmitting and receiving an application service ID, a transport layer, or a transport pattern.

[0184] In one embodiment, the Application Service ID is a method for distinguishing multiple applications subject to similar levels of QoS control within the same PDU session, and as information transmitted to user traffic of the UE, RAN, or Core, the Application Service ID may use a temporary unique ID according to ASPI to minimize the packet size of the radio section.

[0185] In one embodiment, a temporary unique ID can be mapped to a globally unique value.

[0186] In one embodiment, the application service ID may use a persistent unique ID according to ASPI.

[0187] According to various embodiments of the present disclosure, the operation of the UPF to support ASPI and App Service ID includes receiving and managing ASPI information from an SMF, managing a globally unique value and a mapping relationship that can distinguish applications when the application service ID is a temporary unique ID, performing policy and charging control based on stored ASPI, generating charging information based on usage by collected application ID and transmitting it to the SMF, analyzing usage based on usage based on application service ID by subscriber or PDU session and redefining policy and charging control, validating and, if necessary, blocking when receiving an incorrect application service ID, distinguishing application service ID from user traffic received from a RAN, maintaining a mapping relationship between 5-tuple information and application service ID from uplink user traffic, identifying application service ID based on the mapping relationship when downlink traffic occurs from a DN, and including the identified application service ID when transmitting to the RAN.

[0188] In one embodiment, the operation of the SMF to support ASPI and application service ID may control whether to transmit or receive ASPI information according to ASPI Capability, transmit ASPI received from PCF to RAN, UE, or UPF, and add, change, or delete ASPI information received from PCF according to local configuration.

[0189] According to one embodiment, the operation of the RAN to support ASPI and application service ID may include storing or managing ASPI Capability transmitted from a UE during a registration or PDU session procedure and transmitting it to a CN, receiving and managing ASPI information from the CN, identifying a policy for user traffic based on the stored ASPI information and executing it according to the identified policy or analysis result, distinguishing an application service from user traffic received from the UE, and transmitting it to a UPF. An application service ID may be distinguished from user traffic received from a UPF, and transmitted to the UE.

[0190] In one embodiment, as an operation of PCF to support ASPI and App Service ID, ASPI requests can be sent to AMF or SMF, and ASPI can be identified and sent based on ASPI Capability and user profile.

[0191] In one embodiment, the operation of AMF to support ASPI and App Service ID may include receiving ASPI information from PCF, transmitting it to RAN or UE, and controlling whether to transmit or receive ASPI information according to ASPI Capability.

[0192] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0193] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present disclosure.

[0194] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0195] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0196] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0197] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

[0198] In the detailed description and claims of this disclosure, “A or B” can mean “only A,” “only B,” or “both A and B.” In other words, in the detailed description and claims of this disclosure, “A or B” can be interpreted as “A and / or B.” For example, in this specification, “A, B, or C” can mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.”

[0199] The slash ( / ) or comma used in the detailed description and claims of this disclosure may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B, or C."

[0200] In the detailed description and claims of this disclosure, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted as equivalent to “at least one of A and B.”

[0201] Additionally, in the detailed description and claims of the present disclosure, “at least one of A, B, and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.” Additionally, “at least one of A, B, or C” or “at least one of A, B, and / or C” can mean “at least one of A, B, and C.”

Claims

1. In a method of operating a user equipment (UE) in a wireless communication system, The process of transmitting ASPI (application service policy information) Capability to RAN (radio access network) or CN (core network), The process of receiving information about the ASPI from the CN, When uplink traffic for a specific application occurs, the process of identifying the application service ID (identifier) ​​based on the information about the ASPI; A method of including an application service ID in the uplink traffic, if there is an application service ID corresponding to the information about the ASPI 2. In claim 1, A method further comprising the step of transmitting traffic to an application corresponding to the application service ID included in the downlink traffic when downlink traffic is received.

3. In claim 1, the information about the ASPI includes a method for selecting an application service ID, an application service ID transmission and reception operation, a transmission layer, or a transmission pattern.

4. In claim 1, A method of not including the application service ID in the uplink traffic if there is no application service ID corresponding to the information about the ASPI.

5. In claim 1, The above application service ID is information for distinguishing different applications within the same PDU (protocol data unit) session. The above application service ID is transmitted by user traffic, 6. In claim 1, A method in which the above application service ID is used as a temporary unique ID based on information about the above ASPI.

7. In claim 1, A method in which the above application service ID is used as a permanent unique ID based on information about the above ASPI.

8. In claim 2, The above application service ID is information for distinguishing different applications within the same PDU (protocol data unit) session. The above application service ID is transmitted by user traffic, 9. In claim 2, The above application service ID is used as a temporary unique ID based on information about the above ASPI.

10. In claim 2, The above application service ID is used as a permanent unique ID based on information about the above ASPI.

11. In a wireless communication system, a method of operating a RAN (radio access network), The process of receiving ASPI (application service policy information) Capability from a user equipment (UE), The process of transmitting the above ASPI Capability to the core network (CN), The process of receiving information about the ASPI from the CN; A process for identifying policies for user traffic based on information about the above ASPI, When receiving user traffic from the above UE, the process of distinguishing the application service ID and transmitting the application service ID to the UPF (user plane function), A method comprising: when receiving user traffic from the UPF, distinguishing the application service ID and transmitting the application service ID to the UE; 12. In claim 11, the process of transmitting the ASPI Capability to a core network (CN) includes a process of storing or managing the ASPI Capability, The process of receiving information about the ASPI from the CN includes a process of managing information about the ASPI, The process of identifying a policy for user traffic based on the information about the above ASPI is a method of executing a policy according to the identified user traffic.

13. In a wireless communication system, in a user equipment (UE), Transceiver and A control unit (processor) operably connected to the above transceiver, The above control unit, Transmit ASPI (application service policy information) Capability to RAN (radio access network) or CN (core network), Receive information about the ASPI from the CN; When uplink traffic for a specific application occurs, the application service ID (identifier) ​​is identified based on the information about the ASPI. A device that includes the application service ID in the uplink traffic, if there is an application service ID corresponding to the information about the ASPI.

14. In claim 13, the control unit is a device that, when receiving downlink traffic, transmits traffic to an application corresponding to the application service ID included in the downlink traffic.

15. In claim 13, the information on the ASPI includes a method for selecting an application service ID, an application service ID transmission and reception operation, a transmission layer, or a transmission pattern,

Images