Apparatus and method for differentiating application service running on user equipment in wireless communication system

Abstract

The present disclosure relates to a wireless communication system, and more particularly, to an apparatus and a method for differentiating application services running on a user equipment in a wireless communication system. Specifically, an operation method of a user equipment (UE) in a wireless communication system may comprise: a procedure of transmitting application service policy information (ASPI) capability (Capability) to a radio access network (RAN) or a core network (CN), and a procedure of transmitting the application service policy information (ASPI) capability (Capability) to the radio access network (CAN) or the core network (CN), and a procedure of transmitting the application service policy information (ASPI) capability (Capability) to the RAN or the core network (CN), and a procedure of transmitting the application service policy information (ASPI) capability (Capability) to the RAN or the core network (CN). A process for receiving application service policy information (ASPI)-related information from the core network (CN); a process for identifying an application service identifier (ID, identifier) on the basis of application service policy information (ASPI)-related information in a case where uplink traffic related to a specific application has occurred; in a case where there is an application service identifier (ID) corresponding to application service policy information (ASPI)-related information, the application service identifier (ID) may be included in uplink traffic.

Description

Technical Field

[0001] This disclosure relates to a wireless communication system, and more particularly to an apparatus and method for distinguishing application services running on a user device in a wireless communication system. Background Technology

[0002] Mobile telecommunication refers to a communication system that enables users to communicate data, voice, and video without location restrictions through user equipment (UE). User equipment (UE) can access a data network (DN) (e.g., the internet) by interacting with 5G access (e.g., radio access network) and 5G core network (e.g., access and mobility management function (AMF), session management function (SMF), or user plane function (UPF)). When a UE first needs to send data to the data network (DN), it executes a packet data unit (PDU) session establishment procedure, and after a successful session establishment, it sends and receives user data with the data network's server (e.g., YouTube).

[0003] In 5G, various technologies have been proposed to generate new Packet Data Unit (PDU) sessions or Quality of Service (QoS) data streams based on User Equipment (UE) or Service Type (e.g., Mobile Broadband (MBB), Ultra-Reliable Low-Latency Communication (URLCC), and Massive Machine-Type Communication (MTC)). These technologies include network slicing and User Routing Policy (URSP). However, millions of applications registered in app stores (e.g., email, social networks, and music) apply the same QoS and billing policies within the same PDU session. Various schemes have been proposed to differentiate between applications (e.g., Sponsored Identifiers and Reflective QoS). However, existing technologies have limitations in accurately differentiating UE usage patterns (e.g., distinguishing between access via an application or web browser for the same service) and in failing to reflect changes in the application server's Internet Protocol (IP) address in real time. Summary of the Invention

[0004] Technical issues

[0005] Against the backdrop of the discussion described above, this disclosure provides an apparatus and method for distinguishing application services running on a user device in a wireless communication system.

[0006] Furthermore, this disclosure provides an apparatus and method for distinguishing application services in a wireless communication system by differentiating application service identifiers (IDs) based on user traffic.

[0007] Furthermore, this disclosure provides an apparatus and method for classifying application service policy information (ASPI) based on application service identifiers (IDs) in a wireless communication system.

[0008] Furthermore, this disclosure provides an apparatus and method for executing policies and charging controls based on Application Service Policy Information (ASPI) in a wireless communication system.

[0009] Furthermore, this disclosure provides an apparatus and method for conveniently distinguishing multiple applications within the same protocol data unit (PDU) in a wireless communication system, thereby providing independent policies and charging control (PCC) for multiple applications.

[0010] Furthermore, this disclosure provides an apparatus and method for sharing Application Service Policy Information (ASPI) among user equipment (UE), radio access network (RAN), and core network (CN) in a wireless communication system.

[0011] Furthermore, this disclosure provides an apparatus and method for processing application service identifiers (IDs) in user traffic based on shared application service policy information (ASPI) in a wireless communication system.

[0012] Problem-solving methods

[0013] According to various embodiments of this disclosure, an operation method for a user equipment (UE) in a wireless communication system may include: a process of sending application service policy information (ASPI) capability to a radio access network (RAN) or a core network (CN); a process of receiving application service policy information (ASPI) related information from the core network (CN); a process of identifying an application service identifier (ID) based on the application service policy information (ASPI) related information in the event of uplink traffic related to a specific application; and a process of including the application service identifier (ID) in the uplink traffic if an application service identifier (ID) corresponding to the application service policy information (ASPI) related information exists.

[0014] According to various embodiments of this disclosure, an operation method for a radio access network (RAN) in a wireless communication system may include: a process of receiving application service policy information (ASPI) capability from user equipment (UE); a process of sending the ASPI capability to a core network (CN); a process of receiving ASPI-related information from the core network (CN); a process of identifying user traffic-related policies based on the ASPI-related information; a process of distinguishing an application service identifier (ID) when receiving user traffic from the user equipment (UE) and sending the application service identifier (ID) to a user plane function (UPF); and a process of distinguishing an application service identifier (ID) and sending the application service identifier (ID) to the user equipment (UE) when receiving user traffic from the user plane function (UPF).

[0015] According to various embodiments of this disclosure, a user equipment (UE) in a wireless communication system may include: a transceiver; a processor connected to the transceiver in an operable manner; the processor having the capability to send application service policy information (ASPI) to a radio access network (RAN) or a core network (CN), receiving application service policy information (ASPI) related information from the core network (CN), identifying an application service identifier (ID) based on the application service policy information (ASPI) related information when uplink traffic related to a specific application occurs, and including the application service identifier (ID) in the uplink traffic when an application service identifier (ID) corresponding to the application service policy information (ASPI) related information exists.

[0016] The effects of the invention

[0017] The apparatus and methods according to various embodiments of the present disclosure can identify application service policy information (ASPI) based on application service identifiers (IDs) according to user traffic, thereby executing independent policies and billing controls based on the application service policy information (ASPI).

[0018] The effects achievable through this disclosure are not limited to those mentioned above, and those skilled in the art to which this disclosure pertains should clearly understand other effects not mentioned from the following description. Attached Figure Description

[0019] Figure 1 The structure of a 5G system according to various embodiments of the present disclosure is illustrated.

[0020] Figure 2 An example related to a case where it is necessary to distinguish between multiple applications within the same Packet Data Unit (PDU) session according to various embodiments of the present disclosure is illustrated.

[0021] Figure 3 Various embodiments of the present disclosure for solving Figure 2 An example of the method in the case study is illustrated.

[0022] Figure 4 An example of a service differentiation scheme utilizing application service identifiers (IDs) according to one embodiment of the present disclosure is illustrated.

[0023] Figure 5 An example of the configuration and connection relationship of a user equipment (UE), a radio access network (RAN), an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), and a user plane function (UPF) according to an embodiment of the present disclosure is illustrated.

[0024] Figure 6 An example of an application service identifier (ID) and application service policy information according to one embodiment of the present disclosure is illustrated.

[0025] Figure 7 An operational method related to control plane processing of a user equipment (UE) according to one embodiment of the present disclosure has been illustrated.

[0026] Figure 8An operational method for uplink traffic processing on the user plane of a user equipment (UE) according to one embodiment of the present disclosure is illustrated.

[0027] Figure 9 An operation method of the control plane of a User Plane Function (UPF) according to one embodiment of the present disclosure is illustrated.

[0028] Figure 10 An operational method for uplink traffic correlation processing for User Plane Function (UPF) according to one embodiment of the present disclosure is illustrated.

[0029] Figure 11 An operational method related to uplink traffic of a User Plane Function (UPF) according to one embodiment of the present disclosure is illustrated.

[0030] Figure 12 An example of a signal flow diagram of a user equipment (UE), a radio access network (RAN), and a core network (CN) according to one embodiment of the present disclosure is illustrated.

[0031] Figure 13 Configuration diagrams of terminals in wireless communication systems according to various embodiments of the present disclosure are illustrated.

[0032] Figure 14 The configuration of network entities in a wireless communication system according to various embodiments of the present disclosure is illustrated. Detailed Implementation

[0033] The terminology used in this disclosure is for illustrative purposes only and is not intended to limit the scope of other embodiments. Singular statements may also have plural meanings unless the context clearly indicates otherwise. The meanings of terms used herein, including technical and scientific terms, are as commonly understood by one of ordinary skill in the art described in this disclosure. Terms generally defined in dictionaries may be interpreted as having the same or similar meaning in the context of the relevant art, and should not be construed as having overly idealized or exaggerated meanings unless explicitly defined herein. In some cases, even terms defined in the disclosure should not be construed as excluding embodiments of this disclosure.

[0034] The terminology used in this disclosure is for illustrative purposes only and is not intended to limit the scope of other embodiments. Singular statements may also have plural meanings unless the context clearly indicates otherwise. The meanings of terms used herein, including technical and scientific terms, are as commonly understood by one of ordinary skill in the art described in this disclosure. Terms generally defined in dictionaries may be interpreted as having the same or similar meaning in the context of the relevant art, and should not be construed as having overly idealized or exaggerated meanings unless explicitly defined herein. In some cases, even terms defined in the disclosure should not be construed as excluding embodiments of this disclosure.

[0035] The various embodiments of this disclosure described below will be illustrated using a hardware-based access method as an example. However, since the various embodiments of this disclosure include techniques that use both hardware and software, the various embodiments of this disclosure do not exclude software-based access methods.

[0036] The following disclosure relates to an apparatus and method for distinguishing application services running on a user equipment in a wireless communication system. Specifically, the disclosure will describe a technique for identifying application service policy information (ASPI) based on the application service identifier (ID) that enables user traffic in a wireless communication system, thereby enabling the execution of independent policies and charging controls based on the application service policy information (ASPI).

[0037] The terms used in the following description to refer to signals, channels, control information, network entities, and constituent elements of a device are merely illustrative examples for ease of explanation. Therefore, this disclosure is not limited to the terms described below, and other terms with equivalent technical meanings may be used.

[0038] Furthermore, while various embodiments have been described in this disclosure using terminology used in some communication standards (e.g., the 3rd Generation Partnership Project (3GPP)), these are merely illustrative examples. The various embodiments of this disclosure can also be readily adapted to other communication systems.

[0039] This disclosure relates to application quality of service (QoS) operations and related processing techniques for user equipment, and more particularly to user equipment driver operations for performing application-based QoS, policies, billing or charges, and discrete or selective processing required by user equipment in Beyond 5G (B5G) or 6G and commercial services.

[0040] Wireless communication or mobile telecommunication refers to a communication system that enables users to communicate data, voice, and video without being restricted by location through user equipment.

[0041] User equipment (UE) can access the data network (DN) (e.g., the internet) through interaction with 5G access (e.g., radio access network (RAN)) and 5G core network (CN) (e.g., access and mobility management function (AMF), session management function (SMF), and user plane function (UPF)). When the UE first needs to send data to the data network (DN), it can initiate a packet data unit (PDU) session establishment procedure. After the session is successfully established, it can send and receive user data with the data network's server (e.g., YouTube).

[0042] In 5G systems, various technologies have been proposed to generate new packet data unit (PDU) sessions or quality of service (QoS) data flows based on user equipment (UE) or service type (e.g., mobile broadband, ultra-reliable and low latency communication, massive machine-type communication). These technologies include network slicing and user plane separation (URSP). However, currently, applications registered in app stores (e.g., email, social networking services, music services) apply the same QoS or billing policy within the same PDU session. Furthermore, various schemes have been proposed to differentiate between applications (e.g., Sponsored ID and Reflective Quality of Service). QoS). However, existing technologies have limitations in accurately distinguishing user device usage patterns (e.g., for the same service, it is impossible to differentiate between access via an application or a web browser), or in reflecting changes in the application server's Internet Protocol (IP) address in real time.

[0043] Therefore, this disclosure proposes a novel linkage mechanism between user equipment (UE), radio access network (RAN), and core network (CN), and also proposes a scheme that can easily distinguish multiple applications within the same packet data unit (PDU) session and independently apply policies and charging control (PCC) to multiple applications.

[0044] To this end, this disclosure first defines application service policy information (ASPI) in a new way, and defines a scheme for transmitting, negotiating or using application service policy information (ASPI) between user equipment (UE), radio access network (RAN) and core network (CN).

[0045] Second, a novel processing method is proposed, which involves receiving Application Service Policy Information (ASPI) from the core network (CN) when the user equipment (UE) accesses the network, and including the application service identifier (ASPI) identified from the application service policy information (ASPI) into the user traffic when the user equipment (UE) performs the sending and receiving of application-related data.

[0046] Third, the Radio Access Network (RAN) or Core Network (CN) can identify Application Service Policy Information (ASPI) from the Application Service Identifier (ID) of user traffic, and execute independent policies, charging control (PCC), monitoring, and analytics based on the ASPI.

[0047] Fourth, it defines the subject, method, and composition of sending Application Service Policy Information (ASPI) to the control plane (CP) between the User Equipment (UE) and the Access and Mobility Management Function (AMF). It may include methods for selecting or executing message processing methods based on the state of the User Equipment (UE) and including the Application Service Identifier (ID) in the User Equipment (UE)'s user plane (UP) based on the message processing method, methods for mapping uplink traffic and download link traffic to the same Application Service Identifier (ID), and validity check schemes for dealing with abuse.

[0048] Detailed information related to it will be available in [the future]. Figures 2 to 4 A detailed explanation will be provided in the following section.

[0049] Figure 1 The structure of a 5G system according to various embodiments of the present disclosure is illustrated.

[0050] Figure 1 The 5G system in China is composed of an architecture based on the interaction between network functions (NFs).

[0051] The core network of a 5G system can include various entities. Specifically, the Access and Mobility Management (AMF) function manages the access and mobility of User Equipment (UE). Furthermore, the AMF manages the security of the Non-Access Stratum (NAS). Additionally, the AMF handles the mobility of UEs in idle states.

[0052] The session management function (SMF) manages sessions. Furthermore, the SMF can assign Internet Protocol (IP) addresses to user equipment (UEs) and control protocol data unit (PDU) sessions.

[0053] The policy control function (PCF) performs functions to control policies. Additionally, it may include user plane functions (UPFs) that perform user plane control. As gateway functions for data transmission and reception, the UPF can perform all or part of the user plane functions of the serving gateway (S-GW) and packet data network gateway (P-GW) in previous generation mobile communication systems (4G). Furthermore, the UPF can perform functions to process packet data units (PDUs). Additionally, it may include application functions (AFs) that control application functions. Application functions (AFs) can be functions for providing multiple services to user equipment (UE). Furthermore, it may include unified data management (UDMs) that manages unified data. The unified data management (UDM) can perform functions to manage joiner information.

[0054] User equipment (UE) can be a user equipment that receives data.

[0055] A radio access network ((R)AN) can be a component of 5GS that connects user equipment (UE) to the core network (CN) and data network (DN). The access network (AN) can refer to a broader range of access infrastructure, including both wireless and wired connections. A radio access network ((R)AN) can support a variety of services and applications.

[0056] A data network (DN) is a communication network designed for the efficient transmission and exchange of digital data. It can use packet switching to divide data into small packets and send them independently over the network.

[0057] The network slice selection function (NSSF) selects and manages the network slices that are most suitable for users or services.

[0058] Network exposure function (NFF) provides service providers with an interface to access network resources and functions, enabling them to develop and offer new services and applications.

[0059] Network repository function (NRF) can manage the location and availability information of services and resources within a network, thereby enabling other network functions to easily find the services and resources they need.

[0060] Figure 1 The interactions between network function (NF) services within a network function (NF) can be illustrated, which is described by a point-to-point reference point between two network functions (NFs).

[0061] See Figure 1 N1 can be a reference point between the User Equipment (UE) and the Access and Mobility Management Function (AMF). N2 can be a reference point between the (R)Access Network ((R)AN) and the AMF. N3 can be a reference point between the (R)Access Network ((R)AN) and the User Plane Function (UPF). N4 can be a reference point between the Session Management Function (SMF) and the UPF. N6 can be a reference point between the UPF and the Data Network (DN). N9 can be a reference point between two UPFs.

[0062] In addition, service-based interfaces (SBIs) can be defined for specific network functions. For example, the interface for Network Slice Selection Function (NSSF) can be defined as Nnssf, the interface for Network Capability Opening Function (NFF) as Nnef, the interface for Network Storage Function (NRF) as Nnrf, the interface for Policy Control Function (PCF) as Npcf, the interface for Unified Data Management (UDM) as Nudm, the interface for Application Function (AF) as Naf, the interface for Authentication Service Function (AUSF) as Nausf, the interface for Access and Mobility Management Function (AMF) as Naamf, the interface for Session Management Function (SMF) as Nsmf, and the interface for Policy Control Function (PCF) as Npcf, etc.

[0063] Figure 1 The structure illustrated herein is merely an example; the core network (CN) may include other network entities for providing mobile communication services. Furthermore, the names of the network entities and interfaces described above are also illustrative; the names and functions of network entities and the names of interfaces can be arbitrarily changed. That is, the content of this disclosure described below should not be limited to… Figure 1 The diagrams in the image provide an explanation of the definitions and descriptions of network functions and interfaces.

[0064] Figure 2 An example related to a case where it is necessary to distinguish between multiple applications within the same Packet Data Unit (PDU) session, according to various embodiments of the present disclosure, is illustrated.

[0065]

Case 1 (not shown)

[0066] Case 1 is a scenario where it is necessary to differentiate between multiple applications within the same Packet Data Unit (PDU) session. This requires differentiating services (e.g., millions of applications using an internet data network) that are subject to the same Quality of Service (QoS) without allocating a new session (PDU session).

[0067] For example, millions of applications used by current mobile users are controlled by the same Quality of Service (QoS) and receive service through a Packet Data Unit Session (PDU Session), Packet Data Network Session (PDN Session), QoS Flow, or bearer. While it is difficult to completely separate user traffic for individual applications in current networks, this disclosure allows for the implementation of differentiated policies and charging controls (PCC) by separating user traffic for each application.

[0068] Case 2 ( Figure 2 (a)

[0069] See Figure 2 (a) illustrates a scenario where services using the same service or domain name cannot be distinguished based on their access method.

[0070] An application can provide multiple services. Furthermore, it can also provide related services. However, with current technology, it's impossible to distinguish whether the service is accessed as a related service within the application or directly accessed. That is, in... Figure 2 In (a), it is impossible to distinguish between ① access via an application (app) and ② direct access via a content server. Therefore, in order to implement an independent strategy based on the method of use, it is necessary to distinguish between ① and ②.

[0071] For example, with the popularization of artificial intelligence (AI), personal AI assistant applications are emerging, which can provide related services such as weather or news. However, with existing technology, there is no way to distinguish between accessing weather services through these applications and direct access to weather services.

[0072] Case 3 Figure 2 (b)

[0073] See Figure 2 (b) illustrates a situation where services cannot be distinguished in different applications or under the same domain name (e.g., the same cache server or third-party API such as banner ads).

[0074] Figure 2In case (b), this can be equivalent to the situation where the same service is used in different applications. In cases ① where App#1 uses a third-party service and ② where App#2 uses a third-party service, to implement independent policies for App#1 and App#2, it is necessary to differentiate between ① and ②. For example, a free application generates revenue through banner ads. However, the number of advertising application programming interface (API) providers (e.g., Google) is limited, and different applications may use the same API. As another example, different applications may deploy content servers near users to provide low-latency services, and may also use cache servers from specialized content delivery network (CDN) providers or hyperscale cloud providers. In the above scenarios, even though they are different applications, because they share the same Internet Protocol (IP) address for the CDN server, there is no way to differentiate the services.

[0075]

Case 4 (not shown)

[0076] Case 4 is a situation where it is necessary to distinguish between multiple applications within the same Packet Data Unit (PDU) session. This could refer to a situation where the Internet Protocol (IP) address of an application service changes and it is impossible to distinguish them without taking individual measures.

[0077] For example, leveraging cloud resources is crucial in 5G environments, and this trend is expected to accelerate further in the 6G era. In a cloud environment, the Internet Protocol (IP) address of the application server can change at any time. While there are methods in the core network (CN) to send data from application functions (AFs) to open functions (NFFs) via network capabilities, this may need to be implemented on a per-application basis. Furthermore, when the IP address changes, data needs to be sent not only to the network functions (NFs) in the core network (CN) but, if necessary, also to the user equipment (UE) (e.g., changes to Quality of Service (QosRule)). Because this triggers paging for the UE and incurs additional signaling overhead, it is not a preferred solution.

[0078] The primary objective of this disclosure is to address the situations described in Cases 1 through 4. Firstly, user traffic can be separated by application, enabling differentiated policy and charging control (PCC). Secondly, independent policy and charging control (PCC) can be implemented by differentiating user traffic based on access method. Thirdly, independent policy and charging control (PCC) can be implemented by differentiating user traffic by application. Fourthly, functional operation can be achieved without additional signaling when the Internet Protocol (IP) address of the application service changes. Finally, from the operator's perspective, a large number of applications subject to the same Quality of Service (QoS) can be differentiated without additional capacity investment (e.g., Packet Data Unit (PDU) sessions), allowing for differentiated policy and charging based on each application. Furthermore, because monitoring by application becomes easier, troubleshooting and customer feedback (VoC) responses can be easily implemented without separate probe equipment.

[0079] Figure 3 Various embodiments of the present disclosure for solving Figure 2 An example of the method in the case study is illustrated.

[0080] Service differentiation scheme utilizing new resources ( Figure 3 (a)

[0081] Figure 3 Image (a) illustrates a service differentiation scheme (e.g., User Routing Policy (URSP) and network slicing) utilizing new resources (Packet Data Unit Sessions, PDUsessions) according to various embodiments of the present disclosure.

[0082] Figure 3 (a) in the User Plane Function (UPF) distinguishes user traffic and enforces policies and charging controls (PCC) on a per-Packet Data Unit (PDU) session basis, thus failing to address the issue. Figure 2 Case 1 described in the document states that it is impossible to distinguish services subject to the same Quality of Service (QoS) control, and the increase in Packet Data Unit (PDU) sessions will lead to the need for additional capacity investment across the User Equipment (UE), Radio Access Network (RAN), and Core Network (CN) as a whole.

[0083] Service differentiation scheme utilizing new Quality of Service (QoS) data streams ( Figure 3 (a)

[0084] Figure 3 (b) illustrates a service differentiation scheme (e.g., Reflective QoS) utilizing new Quality of Service (QoS) data streams according to various embodiments of the present disclosure.

[0085] Figure 3 (b) in the User Plane Function (UPF) classifies user traffic by Quality of Service (QoS) data stream and enforces policies and charging controls (PCC), therefore it cannot solve the problem. Figure 2 Cases 2, 3, and 4 described in the document. For example, Quality of Service (QoS) data streams can be differentiated based on 5-tuples, but this approach has the problem of not being able to immediately reflect changes in the Internet Protocol (IP) address of the service in the user equipment (UE), radio access network (RAN), or core network (CN).

[0086] Schemes for differentiating services within the core network (CN) itself ( Figure 3 (c)

[0087] Figure 3 Image (c) illustrates a scheme for differentiating services within the core network (CN) itself according to various embodiments of the present disclosure (e.g., Sponsored ID and User Plane Function (UPF) built-in techniques).

[0088] Figure 3 (c) in the User Plane Function (UPF) can differentiate user traffic and enforce policies and charging controls (PCC) based on the destination Internet Protocol (IP) address or domain name. However, because Figure 3 (c) in the User Plane Function (UPF) uses the Application Service Identifier (ID) to differentiate user traffic and enforce policies and charging controls (PCC). Therefore, for Figure 2 Cases 2 and 3 described herein cannot be solved simply by differentiating service data flows (SDFs) based on 5-tuples. Furthermore, for... Figure 2 As for Case 4 recorded in the document, although it can be reflected in real time through the Network Capability Openness Function (NFF), it requires each service provider to provide the corresponding function, so it cannot completely solve Case 4.

[0089] Figure 4 An example of a service differentiation scheme utilizing application service identifiers (IDs) according to one embodiment of the present disclosure is illustrated.

[0090] See Figure 4 Application Service Identifiers (IDs) can be transmitted across the user equipment (UE), radio access network (RAN), and user traffic segments of the UE, and services can be differentiated based on these IDs. In other words, user traffic can be differentiated and policy and charging control (PCC) can be enforced using application service identifiers (IDs) within the User Plane Function (UPF). Specifically, even with only one Packet Data Unit (PDU) session (PDU session #1) and one Quality of Service (QoS) data stream (QoS data stream #1), user traffic can be differentiated and policy and charging control (PCC) enforced within the Packet Data Unit (PDU) by assigning a first application service identifier (App service id #1) and a second application service identifier (App service #2) to the first service (service #1) and the second service (service #2) operating in the UE, respectively. Figure 4 The method described above can overcome the problem. Figure 2 The problems in Cases 1 to 4.

[0091] Next, we will focus on the contents included in Figure 4 This disclosure will be described in more detail below. Next, the User Equipment (UE) registration described in this disclosure may refer to the UE registration steps described in 3GPP TS 23.502-4.2.2. Furthermore, the Packet Data Unit (PDU) session steps described in this disclosure may refer to the Packet Data Unit (PDU) session steps described in 3GPP TS 23.502-4.3. Additionally, the 5-tuple described in this disclosure may refer to a set of values ​​used to uniquely identify a data stream in the network. The 5-tuple may contain a source IP address, a source port number, a destination IP address, a destination port number, and a transport protocol.

[0092] Furthermore, the user traffic mentioned below in this disclosure may include uplink user traffic or downlink user traffic.

[0093] Furthermore, the terms "signal plane" or "signal path" in this disclosure may be used to mean the same thing as "control plane" or "control path".

[0094] Figure 5 An example of the configuration and connection relationship of a user equipment (UE), a radio access network (RAN), an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), and a user plane function (UPF) according to an embodiment of the present disclosure is illustrated.

[0095] First refer to Figure 5 User equipment (UE) may include a control plane (CP) processing unit, an operating system / application (OS / APP) linkage processing unit, and a user plane (UP) processing unit.

[0096] According to one embodiment, the control plane processing unit of a user equipment (UE) can send Application Service Policy Information (ASPI) capability during the UE registration process and the Packet Data Unit (PDU) session process. Furthermore, it can receive ASPI from the core network (CN) and manage the generated, deleted, or modified content.

[0097] According to one embodiment, the operating system / application (OS / APP) linkage processing unit of a user equipment (UE) can map specific applications to application service identifiers (IDs) based on application service policy information (ASPI) stored or managed by the control plane processing unit.

[0098] According to one embodiment, the user plane processing unit of the user equipment (UE) can include the application service identifier (ID) in the user traffic when the application transmits user traffic, based on information mapped by the operating system / application (OS / APP) linkage processing unit. Furthermore, traffic can be sent to the application based on the application service identifier (ID) received when receiving downlink traffic.

[0099] A radio access network (RAN) may include a control plane processing unit, a policy control / analysis unit, and a user plane processing unit.

[0100] According to one embodiment, the control plane processing unit of the radio access network (RAN) can store or manage Application Service Policy Information (ASPI Capability) received from the user equipment (UE) during the user equipment (UE) registration or packet data unit (PDU) session steps and send it to the core network (CN). The control plane processing unit of the RAN can receive Application Service Policy Information (ASPI) from the core network (CN) and manage the generated, deleted, or modified content.

[0101] According to one embodiment, the policy control / analysis unit of the radio access network (RAN) can identify user traffic-related policies based on Application Service Policy Information (ASPI) stored or managed by the control plane processing unit. Based on the identified policies or the results of the analysis, specific actions (e.g., drop, pass, overload control, and priority scheduling) can be executed.

[0102] According to one embodiment, the user plane processing unit of the radio access network (RAN) can distinguish the application service identifier (ID) from user traffic received from the user equipment (UE) and send it to the user plane function (UPF). The RAN's user plane processing unit can also distinguish the application service identifier (ID) from user traffic received from the user plane function (UPF) and send it to the user equipment (UPF). The RAN's user plane processing unit can send the received and transmitted user traffic-related information to the policy control / analysis unit, thereby reflecting new policies based on the analysis results.

[0103] The User Plane Function (UPF) may include the Control Plane Processing Unit, the Policy and Charging Control Unit, the Analytics / Validation Unit, and the User Plane Processing Unit.

[0104] The control plane processing unit of the User Plane Function (UPF) can receive Application Service Policy Information (ASPI) from the Session Management Function (SMF) and process its generation, deletion, or modification. The SMF control plane processing unit can store the format and value related to the Application Service Identifier (ID) in the ASPI. Even when the Application Service Identifier (ID) sent to the User Equipment (UE) is a temporary value, the UPF control plane processing unit can manage globally unique values ​​and mapping relationships within the UPF.

[0105] User Plane Function (UPF) policies and charging controls can execute actions (e.g., drop, pass, overload control, and Quality of Service (QoS) control) based on stored Application Service Policy Information (ASPI). Furthermore, the UPF policy and charging control unit can generate charging information based on the usage of each Application Service Identifier (ID) collected by the User Plane Processing Unit and send it to the Session Management Function (SMF).

[0106] The User Plane Function (UPF) Analysis / Validation Unit can analyze usage based on the Application Service Identifier (ID) of each participant or Packet Data Unit (PDU) session, thereby redefining actions. Furthermore, Analysis / Validation can perform validity checks and traffic blocking functions in cases where the User Equipment (UE) sends incorrect (malicious) Application Service Identifiers (IDs). Validation checks can be performed through correlation analysis with user traffic from other participants, destination IP addresses, and mapping relationships between referenced Application Service Identifiers (IDs).

[0107] The User Plane Function (UPF) user plane processing unit can distinguish Application Service Identifiers (IDs) in user traffic received from the Radio Access Network (RAN). The UPF maintains a mapping between the Application Service Identifiers (IDs) received from the User Equipment (UE) and 5-tuple information. The UPF user plane processing unit can identify the Application Service Identifiers (IDs) based on this mapping when downlink traffic occurs from the Data Network (DN). The identified Application Identifiers (IDs) can be included in the traffic sent to the Radio Access Network (RAN). Furthermore, the UPF can collect usage data and send it to the Policy and Charging Control Unit and the Analysis / Effectiveness Unit. New policies can be reflected based on the analysis results from the Policy and Charging Control Unit and the Analysis / Effectiveness Unit.

[0108] Access and mobility management functions (AMF) may include a control plane processing unit.

[0109] According to one embodiment, the control plane processing unit of the Access and Mobility Management Function (AMF) can receive application service policy information from the Policy Control Function (PCF) and send it to the Radio Access Network (RAN) or User Equipment (UE). The Access and Mobility Management Function (AMF) can control whether or not to send and receive Application Service Policy Information (ASPI) based on the Application Service Policy Information Capability (ASPI).

[0110] The Session Management Function (SMF) may include a control plane processing unit and an application service ID policy decision unit.

[0111] According to one embodiment, the control plane processing unit of the Session Management Function (SMF) can receive Application Service Policy Information (ASPI) from the Policy Control Function (PCF) and send the ASPI to the Radio Access Network (RAN), User Equipment (UE), or User Plane Function (UPF). The Session Management Function (SMF) can control whether or not to send and receive the ASPI based on the ASPI Capability.

[0112] According to one embodiment, the application service identifier (ID) policy of the session management function (SMF) can perform local configuration of application service policy information (ASPI) and add, change or delete application service policy information (ASPI) received from the policy control function (PCF).

[0113] The Policy Control Function (PCF) may include a control plane processing unit and an application service ID policy decision unit.

[0114] According to one embodiment, the control plane processing unit of the policy control function (PCF) can perform the function of receiving and responding to application service policy information (ASPI) requests from the access and mobility management function (AMF) or the session management function (SMF).

[0115] According to one embodiment, the Application Service Identifier (ID) policy decision unit of the Policy Control Function (PCF) can determine the final policy based on information received from the Access and Mobility Management Function (AMF) or the Session Management Function (SMF).

[0116] According to one embodiment, the policy for the application service identifier can be configured locally or received from an external network function (NF).

[0117] According to one embodiment, the policy control function (PCF) can employ different policies based on each participant, each data network name (DNN), or each single networkslice selection assistance information (SNASSAI).

[0118] The user equipment (UE) control plane processing can perform local configuration of Application Service Policy Information (ASPI), and the radio access network (RAN) control plane processing unit can send and receive ASPI using the control path.

[0119] In addition, the control plane processing unit of the Radio Access Network (RAN) and the control plane processing unit of the Access and Mobility Management Function (AMF) can use the control path to send and receive Application Service Policy Information (ASPI).

[0120] Furthermore, the control plane processing unit of the Access and Mobility Management Function (AMF) can use the control plane processing unit of the Session Management Function (SMF) and the control path to send and receive Application Service Policy Information (ASPI), while the control plane processing unit of the Access and Mobility Management Function (AMF) can use the control plane processing unit of the Policy Control Function (PCF) and the control path to send and receive Application Service Policy Information (ASPI).

[0121] In addition, the control plane processing unit of the Session Management Function (SMF) can use the control plane processing unit of the Policy Control Function (PCF) and the control path to send and receive Application Service Policy Information (ASPI).

[0122] The application service identifier (ASPI) identified based on the application service policy information (ASPI) can be transmitted and received between the user plane processing unit of the user equipment (UE) and the user plane processing unit of the radio access network (RAN) via the data path.

[0123] In addition, the Application Service Identifier (ID) can be sent and received between the user plane processing unit of the Radio Access Network (RAN) and the user plane processing unit of the User Plane Function (UPF) via the data path.

[0124] Figure 6 An example of an application service identifier (ID) and application service policy information according to one embodiment of the present disclosure is illustrated.

[0125] See Figure 6 An application service identifier (ID) can be used to distinguish the services of an application running in a user equipment (UE). An application service identifier (ID) can be in the form of a temporary unique identifier or a permanent unique identifier.

[0126] A temporary unique identifier (ID) is a unique identifier that can identify an application and is valid within a Packet Data Unit (PDU) session or Quality of Service (QoS) data stream. The mapping between temporary unique identifiers (IDs) and applications can be managed in the Radio Access Network (RAN) and User Plane Function (UPF).

[0127] A permanently unique identifier (ID) can be a combination of a universally unique identifier (UUID) or an operating system identifier (OSId) and an application identifier (AppID). However, it is not limited to UUID or OSId, but can include multiple types of identifiers.

[0128] See Figure 6 Application service policy information (ASPI) can include policies such as the selection method, action, transport layer, and mode of application service identifiers (IDs). User equipment (UE), radio access network (RAN), and core network (CN) can share ASPI through control paths, and UE, RAN, or CN can include or process application service identifiers (IDs) when transmitting user traffic based on ASPI.

[0129] exist Figure 6 The document compiles specific details related to application service identifiers (IDs) and application service policy information.

[0130] Figure 7 An operational method related to control plane processing of a user equipment (UE) according to one embodiment of the present disclosure has been illustrated.

[0131] See Figure 7 In operation 701, a user equipment (UE) may request a UE registration or Packet Data Unit (PDU) session step from the core network (CN). According to one embodiment, receiving the UE registration or PDU session step request may be within the Access and Mobility Management Function (AMF) of the core network (CN). The UE registration mentioned in operation 701 may refer to the UE registration step described in 3GPP TS 23.502-4.2.2. The PDU session step mentioned in operation 701 may refer to the PDU session step described in 3GPP TS 24.502-4.3.

[0132] In Operation 703, the User Equipment (UE) can send Application Service Policy Information (ASPI) Capability to the Radio Access Network (RAN) or Core Network (CN).

[0133] In Operation 705, the User Equipment (UE) can receive the Application Service Policy Information (ASPI) table from the Core Network (CN).

[0134] In Operation 707, the User Equipment (UE) can store or manage the received Application Service Policy Information (ASPI) table.

[0135] Figure 8 An operational method for uplink traffic processing on the user plane of a user equipment (UE) according to one embodiment of the present disclosure is illustrated.

[0136] See Figure 8 In Operation 801, the User Equipment (UE) can identify the Applicable Application Service Policy Information (ASPI).

[0137] In operation 803, the user equipment (UE) can identify the transmission mode. According to one embodiment, the transmission mode may refer to the first uplink packet or all packets, etc.

[0138] In operation 805, the user equipment (UE) can identify the transmission mode. According to one embodiment, the transport layer may include protocols such as Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), and Internet Protocol (IP).

[0139] In operation 807, the user equipment (UE) can identify the application service type. According to one embodiment, the application service type may include a temporary identifier (ID) or a permanent identifier (ID).

[0140] In Operation 809, the User Equipment (UE) can identify the Application Service Type Identifier (ID).

[0141] In Operation 811, the user equipment (UE) may include an application service identifier (ID) in the user traffic based on at least one of the transport mode, transport layer, or application service type.

[0142] Figure 9An operation method of the control plane of a User Plane Function (UPF) according to one embodiment of the present disclosure is illustrated.

[0143] See Figure 9 In Operation 901, the User Plane Function (UPF) can receive Application Service Policy Information (ASPI) from the Session Management Function (SMF).

[0144] In operation 903, the User Plane Function (UPF) can manage the Application Service Policy Information (ASPI) table. According to one embodiment, managing the Application Service Policy Information (ASPI) table may include adding, deleting, or modifying the contents of the Application Service Policy Information (ASPI) table.

[0145] In Operation 905, the User Plane Function (UPF) can generate Application Service Policy Information (ASPI) key values ​​and mapping tables when the Application Service Identifier (ID) is a temporary unique identifier (ID).

[0146] Figure 10 An operational method for uplink traffic correlation processing for User Plane Function (UPF) according to one embodiment of the present disclosure is illustrated.

[0147] See Figure 10 In Operation 1001, the User Plane Function (UPF) can identify the Application Service Identifier (ID) in uplink packets received from the Radio Access Network (RAN).

[0148] In Operation 1003, the User Plane Function (UPF) can identify the Application Service Policy Information (ASPI) table based on the Application Service Identifier (ID).

[0149] In Operation 1005, you can perform validity or analysis related to the application service identifier (ID).

[0150] In Operation 1007, the User Plane Function (UPF) can enforce policies and billing based on the Application Service Policy Information (ASPI).

[0151] In Operation 1009, the User Plane Function (UPF) can collect the usage of each application service identifier (ID) and send it to the Session Management Function (SMF) based on the collected usage.

[0152] In operation 1011, the User Plane Function (UPF) can generate a mapping table based on the application service identifier (ID) and group-related information. According to one embodiment, the group-related information may include group-related 5-tuple information.

[0153] Figure 11 An operational method related to uplink traffic of a User Plane Function (UPF) according to one embodiment of the present disclosure is illustrated.

[0154] See Figure 11 In operation 1101, the User Plane Function (UPF) can identify the Application Service Identifier (ID) based on downlink packet-related information received from the Data Network (DN) and a mapping table. According to one embodiment, the downlink packet-related information may include 5-tuple information.

[0155] In operation 1103, the User Plane Function (UPF) can identify the Application Service Policy Information (ASPI) table based on the Application Service Identifier (ID).

[0156] In Operation 1105, the User Plane Function (UPF) can perform analysis of the application service identifier (ID).

[0157] In Operation 1107, the User Plane Function (UPF) can execute policies and billing based on the Application Service Policy Information (ASPI).

[0158] In Operation 1109, the User Plane Function (UPF) can collect usage of each application service identifier (ID) and send the collected usage to the Session Management Function (SMF).

[0159] In operation 1111, the User Plane Function (UPF) can transmit downlink traffic to the Radio Access Network (RAN). According to one embodiment, in operation 1111, when the User Plane Function (UPF) transmits downlink traffic to the Radio Access Network (RAN), it may include an Application Service Identifier (ID) for transmission.

[0160] Figure 12 An example of a signal flow diagram of a user equipment (UE), a radio access network (RAN), and a core network (CN) according to one embodiment of the present disclosure is illustrated.

[0161] See Figure 12In operation 1201, the user equipment (UE) may request a registration step or a packet data unit (PDU) session establishment step from the radio access network (RAN) or the core network (CN). According to one embodiment, in operation 1201, the request may be sent from the UE to the core network (CN) via the radio access network (RAN). According to one embodiment, the registration step or the PDU session establishment step may be received by the access and mobility management function (AMF) of the core network (CN).

[0162] In Operation 1201, when a User Equipment (UE) performs a registration procedure, the UE can send Application Service Policy Information Capability (ASPI) information, related to whether or not the Application Service Identifier (ID) is supported, to the Radio Access Network (RAN), Access and Mobility Management Function (AMF), or Policy Control Function (PCF) via the Core Network (CN). The Access and Mobility Management Services (PCF) can identify the ASPI based on the UE's ASPI Capability and the joiner profile, and then send it to the RAN or UE.

[0163] In Operation 1201, when a User Equipment (UE) requests a Packet Data Unit (PDU) session establishment step, the UE may send Application Service Policy Information Capability (ASPI) information related to whether or not the Application Service Identifier (ID) is supported to the Radio Access Network (RAN), Access and Mobility Management Function (SMF), or Policy Control Function (PCF) to the Core Network (CN).

[0164] In operation 1203, the core network (CN) can send Application Service Policy Information (ASPI) to a User Equipment (UE) or a Radio Access Network (RAN). According to one embodiment, the ASPI sent to the UE can be transmitted via the Radio Access Network (RAN). According to another embodiment, the entity transmitting the ASPI in the core network (CN) can be the Access and Mobility Management Function (AMF). The AMF can transparently transmit the ASPI value, and the Radio Access Network (RAN) or UE can store the ASPI value and perform actions based on the policy according to the ASPI value.

[0165] In operation 1205, the user equipment (UE) can identify the application service identifier when executing an application. According to one embodiment, the application service identifier (ID) can be identified based on application service policy information (ASPI) contained in the application. The process of identifying the application service identifier (ID) may include identifying the application service identifier (ID) when the user equipment (UE) application is newly running or is currently running.

[0166] In operation 1207, a user equipment (UE) can transmit uplink traffic to a radio access network (RAN) or a core network (CN). According to one embodiment, uplink traffic sent to the core network (CN) can be transmitted via the radio access network (RAN). According to one embodiment, the uplink traffic may include an application service identifier (ID).

[0167] According to one embodiment, the Application Service Identifier (ID) may be included in the Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), or other layers. That is, the Radio Access Network (RAN) can receive uplink traffic, extract the Application Service Identifier (ID) from the SDAP, PDCP, or other layers, and distinguish it from the Application Service Policy Information (ASPI). The RAN can perform operations according to the ASPI and transmit the uplink traffic to the User Plane Function (UPF). According to one embodiment, the RAN and UPF area may use the General Packet Radio Traffic Tunneling Protocol User Plane (GTP-U), and the Application Service Identifier (ID) may be included in the GTP-U or other layers.

[0168] According to other embodiments, in operation 1207, in the absence of Application Service Policy Information (ASPI) corresponding to the application, the User Equipment (UE) may not include the Application Service Identifier (ID) in the uplink traffic. Therefore, under the circumstances described above, the User Equipment (UE), Radio Access Network (RAN), or User Plane Function (UPF) can process the uplink traffic normally in the existing manner.

[0169] In operation 1209, the User Plane Function (UPF) can process uplink traffic. According to one embodiment, the UPF can extract Application Service Identifiers (IDs) from the General Packet Radio Service Tunneling Protocol User Plane (GTP-U) or other layers, and can identify Application Service Policy Information (ASPI). The UPF can enforce policy and charging control based on the ASPI and local configuration. Furthermore, operation 1209 may include a process by which the UPF manages the mapping between received packet-related information and the Application Service Identifier (ID). According to one embodiment, the packet-related information may include packet-related 5-tuples.

[0170] In operation 1211, the User Plane Function (UPF) can process downlink traffic. Operation 1211 may include a process by which the UPF, upon receiving downlink traffic, distinguishes the Application Service Identifier (ID) based on packet-related information and the mapping relationship stored in operation 1209. Furthermore, operation 1211 may include a process by which the UPF executes policy and charging control based on Application Service Policy Information (ASPI) and local configuration.

[0171] In operation 1213, the User Plane Function (UPF) can transmit downlink traffic to the Radio Access Network (RAN) or the User Equipment (UE). According to one embodiment, downlink traffic sent to the User Equipment (UE) can be transmitted to the UPF via the Radio Access Network (RAN). According to one embodiment, the downlink traffic may include an Application Service Identifier (ID).

[0172] According to one embodiment, the Radio Access Network (RAN) can extract the Application Service Identifier (ID) from the General Packet Radio Service Tunneling Protocol User Plane (GTP-U) or other layers, and identify the Application Service Policy Information (ASPI). After identifying the ASPI, the RAN can incorporate the Application Identifier (ID) into the Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), or other layers of downlink traffic.

[0173] According to other embodiments, in operation 1212, in the absence of Application Service Policy Information (ASPI) corresponding to the application, the User Equipment (UE) may not include the Application Service Identifier (ID) in the downlink traffic. Therefore, under the circumstances described above, the User Equipment (UE), Radio Access Network (RAN), or User Plane Function (UPF) can process the downlink traffic normally in the existing manner.

[0174] Figure 13 Configuration diagrams of terminals in wireless communication systems according to various embodiments of the present disclosure are illustrated. Figure 13 The configuration illustrated herein can be understood as the configuration of terminal 1300. The terms “…part” and “…device” used thereafter refer to a unit that processes at least one function or operation, which can be implemented through hardware, software, or a combination of both.

[0175] See Figure 13The user equipment (UE) may include a communication unit 1310, a storage unit 1320, and a control unit 1330.

[0176] The communication unit 1310 can perform functions for transmitting and receiving signals via a wireless channel. For example, the communication unit 1310 can perform conversion functions between baseband signals and bitstreams according to the system's physical layer standard. For example, when transmitting data, the communication unit 1310 can encode and modulate the transmitted bitstream to generate complex symbols. When receiving data, the communication unit 1310 can restore the received bitstream by demodulating and decoding the baseband signal. Furthermore, the communication unit 1310 can upconvert the baseband signal to a radio frequency (RF) band signal and transmit it through an antenna, and downconvert the RF band signal received through the antenna back to a baseband signal. For example, the communication unit 1310 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), and an analog-to-digital converter (ADC).

[0177] Furthermore, the communication unit 1310 may include multiple transceiver paths. Moreover, the communication unit 1310 may include at least one antenna array composed of multiple antenna elements. From a hardware perspective, the communication unit 1310 may be composed of digital circuits and analog circuits (e.g., radio frequency integrated circuits (RFICs)). The digital and analog circuits can be implemented in a single package. Furthermore, the communication unit 1310 may include multiple radio frequency (RF) links. Furthermore, the communication unit 1310 can perform beamforming.

[0178] The communication unit 1310 can transmit and receive signals in the manner described above. Therefore, all or part of the communication unit 1310 can be referred to as a "transmitter," a "receiver," or a "transceiver." Furthermore, in the following description, transmission and reception performed via wireless signals can be used to mean including the processing described above performed by means of the communication unit 1310.

[0179] The storage unit 1320 can store data such as basic programs, application programs, and setting information used for the operation of the user equipment (UE). The storage unit 1320 can be configured with volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. In addition, the storage unit 1320 can provide the stored data according to the request of the control unit 1330.

[0180] The control unit 1330 can control the overall operation of the user equipment (UE). For example, the control unit 1330 can transmit and receive signals through the communication unit 1310. Furthermore, the control unit 1330 can record and retrieve data in the storage unit 1320. The control unit 1330 can perform the functions of the protocol stack required by the communication standard. For this purpose, the control unit 1330 may include at least one processor or microprocessor, or a part of a processor. Furthermore, a part of the communication unit 1310 and the control unit 1330 may be referred to as a communication processor (CP).

[0181] According to various embodiments, the control unit 1330 can control the execution of various embodiments of the user equipment (UE) as described above.

[0182] Figure 14The configuration of a network entity in a wireless communication system according to various embodiments of the present disclosure is illustrated. The network entity of the present disclosure is based on the concept of a system implementation including network functions. The terms "unit" and "device," as used herein, refer to a unit that processes at least one function or operation, which can be implemented by hardware, software, or a combination of hardware and software. A 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 performs signal transmission and reception with other network entities. Therefore, all or part of the communication unit 1410 may be referred to as "transmitter 1411," "receiver 1413," or "transceiver / receiver 1410." The storage unit 1420 stores data such as basic programs, application programs, and setting information for the operation of the network entity 1400. Storage unit 1420 may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. Furthermore, storage unit 1420 provides stored data according to requests from control unit 1430. Control unit 1430 controls the overall operation of network entity 1400. For example, control unit 1430 transmits and receives signals via communication unit 1410. Furthermore, control unit 1430 records and retrieves data from storage unit 1420. Furthermore, control unit 1430 can perform the functions of the protocol stack required in communication standards. For this purpose, control unit 1430 may include a circuit, application-specific circuitry, at least one processor or microprocessor, or part of a processor. Furthermore, part of communication unit 1410 and control unit 1430 may be referred to as a communication processor (CP). Control unit 1430 can control network entity 1400 to perform one of the operations in various embodiments of this disclosure. Of course, the communication unit 1410 and the control unit 1430 do not necessarily have to be implemented as separate modules, but can be implemented as a single chip or software block within a single component. The communication unit 1410, storage unit 1420, and control unit 1430 can be electrically connected. Furthermore, the operation of the network entity 1400 can be achieved by equipping the network entity 1400 with a storage unit 1420 storing the corresponding program code. The network entity 1400 includes, for example... Figure 1The network node shown can be one of the following: Radio Access Network (RAN), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Network Function (NF), Network Capability Opening Function (NFF), Network Storage Function (NRF), Policy Control Function (PCF), Network Slice Selection Function (NSSF), Unified Data Management (UDM), Application Function (AF), Authentication Service Function (AUSF), Service Communication Agent (SCP), Unstructured Data Storage Function (UDSF), Context Storage, Operation, Management and Maintenance (OAM), Element Management System (EMS), Configuration Server, or Identifier Management Server.

[0183] According to various embodiments of this disclosure, as a method for a user equipment (UE) to share application service policy information (ASPI) between a radio access network (RAN) and a core network (CN) via the control plane, and to include the application service identifier (ID) in the user plane based on the corresponding application service policy information (ASPI), the user equipment (UE) can send the application service policy information (ASPI) to the radio access network (RAN) or the core network (CN) during the registration or packet data unit (PDU) session steps, and can then receive and manage the application service policy information (ASPI) from the core network (CN).

[0184] According to one embodiment, when uplink traffic related to a specific application occurs, the user equipment (UE) can identify the application service identifier (ID) according to the application service policy information (ASPI) policy and include the application service identifier (ID) value in the uplink traffic.

[0185] According to one embodiment, a user equipment (UE) can send traffic to a corresponding application based on an application service identifier (ID) received when receiving downlink traffic.

[0186] According to one embodiment, Application Service Policy Information (ASPI) may include application identification and method for selecting application service identifier (ID), operation when sending and receiving application service identifier (ID), transport layer or transport mode.

[0187] According to one embodiment, the Application Service Identifier (ID) is information sent to user traffic in a method for distinguishing a large number of applications subject to similar levels of Quality of Service (QoS) control within the same Packet Data Unit (PDU). In order to minimize packet size in the radio interval, a temporary unique identifier (ID) is used as the Application Service Policy Information (ASPI) as the Application Service Identifier (ID).

[0188] According to one embodiment, a temporary unique identifier (ID) can be mapped to a globally unique value.

[0189] According to one embodiment, the application service identifier (ID) can use a permanently unique identifier (ID) based on the application service policy information (ASPI).

[0190] According to various embodiments of this disclosure, as an operation of a user plane function (UPF) supporting application service policy information (ASPI) and application service identifiers (App Service IDs), the UPF receives and manages the application service policy information (ASPI) from the session management function (SMF). When the application service identifier (ID) is a temporary unique identifier (ID), the UPF manages globally unique values ​​and mapping relationships that can distinguish applications. Based on the stored application service policy information (ASPI) for executing policies and charging control, and the collected usage of each application identifier (ID), the UPF generates charging information and sends it to the session management function (SMF). This information is then used based on each joiner or each packet data unit (PDU) session. The system analyzes usage based on usage data and redefines policies and charging controls. It performs validity verification and interception as needed when receiving incorrect application service identifiers (IDs). It distinguishes application service identifiers (IDs) in user traffic received from the radio access network (RAN). It maintains the mapping relationship between 5-ruple information and application service identifiers (IDs) in uplink traffic. When downlink traffic occurs from the data network (DN), it identifies application service identifiers (IDs) based on the mapping relationship and includes the identified application service identifiers (IDs) in the information sent to the radio access network (RAN).

[0191] According to one embodiment, as an operation of the Session Management Function (SMF) for supporting Application Service Policy Information (ASPI) and Application Service Identifier (ID), the transmission and reception of Application Service Policy Information (ASPI) are controlled according to the ASPI Capability. The ASPI received from the Policy Control Function (PCF) is sent to the Radio Access Network (RAN), User Equipment (UE), or User Plane Function (UPF). The ASPI received from the User Plane Function (UPF) is added, modified, or deleted according to the local configuration.

[0192] According to one embodiment, as an operation of a radio access network (RAN) supporting Application Service Policy Information (ASPI) and Application Service Identifier (ID), the RAN stores or manages the ASPI capability received from the User Equipment (UE) during the registration or Packet Data Unit (PDU) session and sends it to the core network (CN). The RAN receives and manages the ASPI from the core network (CN), identifies user traffic-related policies based on the stored ASPI, and executes them according to the identified policies or analysis results. The RAN distinguishes application services in the user traffic received from the UE and sends the information to the User Plane Function (UPF). The RAN can also distinguish the Application Service Identifier (ID) in the user traffic received from the UPF and send it to the UPF.

[0193] According to one embodiment, as an operation of the policy control function (PCF) for supporting application service policy information (ASPI) and application service identifier (App Service ID), an application service policy information (ASPI) request can be received from the access and mobility management function (AMF) or the session management function (SMF), and the application service policy information (ASPI) can be identified according to the application service policy information capability and user profile before being sent.

[0194] According to one embodiment, as an operation of the Access and Mobility Management Function (AMF) for supporting Application Service Policy Information (ASPI) and Application Service Identifier (App Service ID), the ASPI can be received from the Policy Control Function (PCF) and sent to the Radio Access Network (RAN) or User Equipment (UE). The sending and receiving of the ASPI can also be controlled according to the ASPI Capability.

[0195] The methods according to the embodiments described in the claims or specification of this disclosure can be implemented in hardware, software, or a combination of hardware and software.

[0196] In the case of software implementation, a computer-readable storage medium may be provided for storing more than one program (software module). The more than one program stored in the computer-readable storage medium is configured for execution by more than one processor within an electronic device. The more than one program includes instructions that can be used to cause the electronic device to perform the methods according to the embodiments described in the claims or specification of this disclosure.

[0197] The program (software module, software) described above can be stored in non-volatile memory, including random access memory, flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other forms of electronic storage devices, as well as magnetic cassettes. Alternatively, it can be stored in a memory consisting of some or all of the above. Furthermore, each constituting memory may include multiple such memories.

[0198] Furthermore, the program can be stored in an attachable storage device that can be accessed via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide Area Network (WAN), Storage Area Network (SAN), or a combination thereof. The storage device described above can be connected to the device executing embodiments of this disclosure via an external port. Additionally, a separate storage device on the communication network can also be connected to the device executing embodiments of this disclosure.

[0199] In the specific embodiments of this disclosure as described above, the constituent elements included in this disclosure are expressed in a singular or plural form according to the proposed specific embodiments. However, the expression in singular or plural form is merely an appropriate choice made for the convenience of explanation based on the proposed situation, and this disclosure is not limited to singular or plural constituent elements; even constituent elements expressed as plural may be constituted in a singular form, and even constituent elements expressed as singular may be constituted in a plural form.

[0200] Furthermore, although specific embodiments have been described in the detailed description of this disclosure, various modifications can be made without departing from the scope of this disclosure. Therefore, the scope of this disclosure is not limited to the described embodiments, but should be defined within the scope of the appended claims and their equivalents.

[0201] In the detailed description and claims of this disclosure, "A or B" can mean "A only", "B only", 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 "A only", "B only", "C only", or "any combination of A, B, and C".

[0202] In the detailed description of this disclosure and in the claims, the forward slash ( / ) or comma used can mean "and / or". For example, "A / B" can mean "A and / or B". Therefore, "A / B" can mean "A only", "B only", or "both A and B". For example, "A, B, C" can mean "A, B, or C".

[0203] In the detailed description and claims of this disclosure, "at least one of A and B" can mean "only A", "only B" or "both A and B". Furthermore, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" can be interpreted as having the same meaning as "at least one of A and B".

[0204] Furthermore, in the detailed description and claims of this 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. A method, as an operation method of user equipment (UE) in a wireless communication system, comprising: The process of sending application service policy information (ASPI) capability to a radio access network (RAN) or core network (CN). The process of receiving Application Service Policy Information (ASPI) related information from the core network (CN); In the event of uplink traffic related to a specific application, the process of identifying the application service identifier (ID) based on the application service policy information (ASPI) related information; If the application service identifier (ID) corresponding to the application service policy information (ASPI) exists, the application service identifier (ID) is included in the uplink traffic.

2. The method according to claim 1, further comprising: The process of sending downlink traffic to the application corresponding to the application service identifier (ID) contained in the downlink traffic upon receipt of downlink traffic.

3. The method according to claim 1, The Application Service Policy Information (ASPI) related information includes the method for selecting the Application Service Identifier (ID), the application service identifier (ID) sending and receiving operations, and the transport layer or transport mode.

4. The method according to claim 1, If the application service identifier (ID) corresponding to the application service policy information (ASPI) does not exist, the uplink traffic will not contain the application service identifier (ID).

5. The method according to claim 1, The application service identifier (ID) is information used to distinguish different applications within the same protocol data unit (PDU) session. The application service identifier (ID) is sent via user traffic.

6. The method according to claim 1, The application service identifier (ID) is used as a temporary unique identifier based on the application service policy information (ASPI).

7. The method according to claim 1, The application service identifier (ID) is used as a permanent unique identifier based on the application service policy information (ASPI).

8. The method according to claim 2, The application service identifier (ID) is information used to distinguish different applications within the same protocol data unit (PDU) session. The application service identifier (ID) is sent via user traffic.

9. The method according to claim 2, The application service identifier (ID) is used as a temporary unique identifier based on the application service policy information (ASPI).

10. The method according to claim 2, The application service identifier (ID) is used as a permanent unique identifier based on the application service policy information (ASPI).

11. A method, as an operation method of a radio access network (RAN) in a wireless communication system, comprising: The process of receiving application service policy information (ASPI) from user equipment (UE). The process of sending the Application Service Policy Information Capability (ASPI Capability) to the core network (CN); The process of receiving Application Service Policy Information (ASPI) related information from the core network (CN); The process of identifying user traffic-related policies based on the Application Service Policy Information (ASPI) information; The process of distinguishing the application service identifier (ID) when receiving user traffic from the user equipment (UE) and sending the application service identifier (ID) to the user plane function (UPF); The process of distinguishing the application service identifier (ID) when receiving user traffic from the user plane function (UPF) and sending the application service identifier (ID) to the user equipment (UE).

12. The method according to claim 11, The process of sending the Application Service Policy Information Capability (ASPI Capability) to the core network (CN) includes the process of storing or managing the Application Service Policy Information Capability (ASPI Capability). The process of receiving the Application Service Policy Information (ASPI) related information from the core network (CN) includes the process of managing the Application Service Policy Information (ASPI) related information. The process of identifying user traffic-related policies based on Application Service Policy Information (ASPI) information, and executing policies according to the identified user traffic.

13. An apparatus for use as user equipment (UE) in a wireless communication system, comprising: Transceiver department; The control unit (processor) is operably connected to the transceiver unit; The control unit, Capability to send application service policy information (ASPI) to the radio access network (RAN) or core network (CN). Receive the Application Service Policy Information (ASPI) related information from the core network (CN). In the event of uplink traffic related to a specific application, the application service identifier (ID) is identified based on the application service policy information (ASPI). If the application service identifier (ID) corresponding to the application service policy information (ASPI) exists, the application service identifier (ID) is included in the uplink traffic.

14. The apparatus according to claim 13, Upon receiving downlink traffic, the control unit sends the traffic to the application corresponding to the application service identifier (ID) contained in the downlink traffic.

15. The apparatus according to claim 13, The Application Service Policy Information (ASPI) related information includes the method for selecting the Application Service Identifier (ID), the application service identifier (ID) sending and receiving operations, and the transport layer or transport mode.

Images