KR102803899B1 - DATA GATEWAY DEVICE AND QoS CONTROL METHOD IN THE DEVICE, TERMINAL DEVICE - Google Patents

Abstract

The present invention proposes a method for improving service quality by providing flexible service quality for a service (e.g., cloud service) by realizing a specific technical configuration capable of performing fixed address-based QoS control for data traffic of a service (e.g., cloud service) using a dynamic address.

Description

DATA GATEWAY DEVICE AND QoS CONTROL METHOD IN THE DEVICE, TERMINAL DEVICE

The present invention relates to QoS control technology, and more specifically, to technology that enables QoS control for data traffic of a service using a dynamic address.

In 5G, a network structure is defined to support terminals, base stations (access), cores, and servers end to end, and the functions of control signaling and data transmission and reception that were performed complexly by a single node (e.g. S-GW, P-GW, etc.) in the existing LTE (4G) are separated, defining a network structure that divides the area of control signaling functions (Control Plane) and the area of data transmission and reception functions (User Plane).

At this time, the nodes of the Control Plane (CP) in 5G can be defined as the Access and Mobility Management Function (AMF) that controls the wireless section access of the terminal, the Policy Control Function (PCF) that manages/controls terminal information, terminal-specific subscription service information, charging policies, etc., the Session Management Function (SMF) that controls/manages sessions for data service use by terminal, the Network Exposure Function (NEF) that is in charge of information sharing with external networks, the Unified Data Management / AUthentication Function (UDM/AUSF) that manages/controls the user's subscriber DB and authentication, the Network Repository Function (NRF) that manages/controls information on each NF (Network Function) within the network, and the CHF (CHarging Function) that processes the subscriber's charging.

And, in 5G, the User Plane (UP) node can be defined as a UPF (User Plane Function) that transmits and receives data between a terminal and a server on an external service network (e.g., the Internet) through a session with the terminal based on the control (interlocking) of the SMF.

Meanwhile, as the emergence of cloud-based IT services (hereinafter, “Cloud services”) continues, the need to flexibly provide/control service quality for such services is increasing.

Companies providing cloud services have a large number of public IPs (access addresses) and assign dynamic IPs to cloud services, so there are a lot of addresses for each cloud service, and the address of the cloud service responding may be different depending on the time/region/terminal.

Accordingly, a terminal that wishes to use a Cloud service can first obtain the address (dynamic IP) of the Cloud service through a DNS Request/DNS Response, and then communicate with the Cloud service based on the obtained address (dynamic IP).

Meanwhile, according to the 3GPP standard, 5G Core will process QoS quality control based on transmission speed, usage monitoring, and other charges by applying Policy Rules per session or per detailed SDF (Service Data Flow) within the session.

However, from the perspective of 5G Core (UPF/SPGW-U), since Cloud services use dynamic IPs that can change each time, and it is practically impossible to implement a procedure to update these dynamic IPs frequently in terms of operation/status, it is impossible to process QoS quality control, usage monitoring, and other charges for data traffic of Cloud services, i.e., communication between terminals and Cloud services.

Ultimately, mobile communication networks are unable to realistically control quality (QoS) for the continuously increasing number of cloud services, and various additional services based on quality control are also impossible.

Accordingly, the present invention proposes a new technical method that enables QoS control, such as QoS quality control based on transmission speed, usage monitoring, and other charging, for data traffic of a cloud service using a dynamic address.

The present invention has been created in consideration of the above circumstances, and the problem to be solved by the present invention is to realize a new technical solution that enables QoS control for data traffic of a service (e.g., cloud service) using a dynamic address.

According to a first aspect of the present invention for achieving the above object, a data gateway device includes: a conversion unit which changes an actual address of a specific service into a specific virtual destination address in an address response returned to a terminal in response to an address request for a specific service from the terminal; and a control unit which supports communication between the terminal and the specific service by transferring uplink data of the terminal received to the specific virtual destination address to the actual address of the specific service through an address conversion function, and which performs QoS (Quality of Service) control based on the specific virtual destination address for the communication.

Specifically, the QoS control may include at least one of quality control based on transmission speed for communication between the terminal and the specific service, usage measurement, and billing processing.

Specifically, the actual address of the specific service may include at least one dynamic address dynamically allocated to the specific service, and the specific virtual destination address may be a fixed address allocated to the specific service.

Specifically, the conversion unit assigns a virtual destination address based on a preset virtual destination table according to at least one of the session of the terminal and the identifier of the specific service to be used for changing the address response, and the virtual destination table can be preset and transmitted by a control device that manages/controls sessions for each terminal.

Specifically, the virtual destination address may be configured to include at least one of v(virtual)IP, vTag, vInterface, vTEID(Tunnel Endpoint Identifier), vDSCP(Differentiated Service Code Point), vLocation, and vContext.

Specifically, the conversion unit may forward the address request to a specific node that holds real-time floating addresses for a number of services, change the address response obtained from the specific node to the specific virtual destination address, and then send it back to the terminal, or, if an address request identical to the address request of the specific service is determined to be present in the previously stored service address request/address response history, extract the address response changed to the specific virtual destination address from the service address request/address response history, and send it back to the terminal.

Specifically, the uplink data of the terminal received to the specific virtual destination address can be detected at the N3, S1U, N9 Interface between the RAN (Radio Access Network) and the data gateway device.

Specifically, the control unit manages a virtual destination mapping table in conjunction with the conversion unit, and the virtual destination mapping table may be configured to include at least one of session and address information of the terminal, an identifier of the service, an actual address of the service, a virtual destination address assigned to the service, and an external address assigned to be used as an address of the terminal by mapping with the actual address of the service in the address conversion function.

According to a second aspect of the present invention for achieving the above object, a terminal device includes: an address request unit for requesting an address for a specific service; and a data transmission/reception unit for performing data transmission/reception with the specific service by using the address of the specific service confirmed from an address response returned in response to the address request; the address of the specific service confirmed from the address response may be an actual address of the specific service, or a specific virtual destination address changed by a data gateway device involved in the data transmission/reception.

According to a third aspect of the present invention for achieving the above object, a QoS control method performed in a data gateway device includes a conversion step of changing an actual address of a specific service into a specific virtual destination address in an address response returned to a terminal in response to an address request for a specific service from a terminal; and a control step of transmitting uplink data of the terminal received to the specific virtual destination address to the actual address of the specific service through an address conversion function to support communication between the terminal and the specific service, while performing QoS (Quality of Service) control based on the specific virtual destination address for the communication.

Specifically, the QoS control may include at least one of quality control based on transmission speed for communication between the terminal and the specific service, usage measurement, and billing processing.

Specifically, the actual address of the specific service may include at least one dynamic address dynamically allocated to the specific service, and the specific virtual destination address may be a fixed address allocated to the specific service.

Specifically, the virtual destination address may be configured to include at least one of v(virtual)IP, vTag, vInterface, vTEID(Tunnel Endpoint Identifier), vDSCP(Differentiated Service Code Point), vLocation, and vContext.

Specifically, the uplink data of the terminal received to the specific virtual destination address can be detected at the N3, S1U, N9 Interface between the RAN (Radio Access Network) and the data gateway device.

According to the data gateway device of the present invention and the QoS control method and terminal device performed in the device, a specific technical configuration capable of performing fixed address-based QoS control for data traffic of a service (e.g., cloud service) using a dynamic address is realized.

Accordingly, according to the present invention, QoS control is enabled for data traffic of a service (e.g., a cloud service) using a dynamic address, thereby improving the service quality through flexible service quality provision for the service (e.g., a cloud service).

Figure 1 is an example diagram conceptually showing the (address-based) data traffic flow of an existing Cloud service.
Figure 2 is an exemplary diagram conceptually showing the (address-based) data traffic flow of a cloud service according to the present invention.
FIG. 3 is a block diagram showing the configuration of a data gateway device and a terminal device according to one embodiment of the present invention.
FIG. 4 is an exemplary diagram showing an embodiment of a method for explaining allocation of a fixed address (virtual destination address) for QoS control in the present invention.
FIG. 5 is an exemplary diagram showing one embodiment of realizing QoS control based on a fixed address (virtual destination address) in the present invention.
FIG. 6 is an exemplary diagram showing another embodiment of realizing QoS control based on a fixed address (virtual destination address) in the present invention.
Figure 7 is an example diagram showing the configuration of a virtual destination mapping table in the present invention.
FIGS. 8 to 10 are flowcharts showing examples of control scenarios in which the QoS control method of the present invention is performed.

Hereinafter, various embodiments of the present invention will be described with reference to the attached drawings.

The present invention relates to a technology that enables QoS control for data traffic of a service (e.g., cloud service) using a dynamic address.

In 5G, a network structure is defined to support terminals, base stations (access), cores, and servers end to end, and the functions of control signaling and data transmission and reception that were performed complexly by a single node (e.g. S-GW, P-GW, etc.) in the existing LTE (4G) are separated, defining a network structure that divides the area of control signaling functions (Control Plane) and the area of data transmission and reception functions (User Plane).

At this time, the nodes of the Control Plane (CP) in 5G can be defined as the Access and Mobility Management Function (AMF) that controls the wireless section access of the terminal, the Policy Control Function (PCF) that manages/controls terminal information, terminal-specific subscription service information, charging policies, etc., the Session Management Function (SMF) that controls/manages sessions for data service use by terminal, the Network Exposure Function (NEF) that is in charge of information sharing with external networks, the Unified Data Management / AUthentication Function (UDM/AUSF) that manages/controls the user's subscriber DB and authentication, the Network Repository Function (NRF) that manages/controls information on each NF (Network Function) within the network, and the CHF (CHarging Function) that processes the subscriber's charging.

And, in 5G, the User Plane (UP) node can be defined as a UPF (User Plane Function) that transmits and receives data between a terminal and a server on an external service network (e.g., the Internet) through a session with the terminal based on the control (interlocking) of the SMF.

Meanwhile, as the emergence of cloud-based IT services (hereinafter, “Cloud services”) continues, the need to flexibly provide/control service quality for such services is increasing.

Companies providing cloud services have a large number of public IPs (access addresses) and assign dynamic IPs to cloud services, so there are a lot of addresses for each cloud service, and the address of the cloud service responding may be different depending on the time/region/terminal.

Accordingly, a terminal that wishes to use a Cloud service can perform communication with the Cloud service based on the acquired address (dynamic IP) by transmitting a DNS Request requesting the address of the Cloud service it wishes to use to a specific node (e.g. DNS) and obtaining the address (dynamic IP) of the Cloud service through a DNS Response.

Accordingly, as illustrated in FIG. 1, the terminal uses multiple dynamic IPs to use the cloud service while establishing a session (e.g., PDU Session: APN/DNN = 5g.sktelecom.com) with the 5G Core (UPF/SPGW-U), and from the perspective of the 5G Core (UPF/SPGW-U), the data traffic (e.g., a), b), c)) sent by the terminal for each dynamic IP can be forwarded to each dynamic IP (e.g., a), b), c)), thereby supporting communication between the terminal and the cloud service.

Meanwhile, according to the 3GPP standard, 5G Core will process QoS quality control based on transmission speed, usage monitoring, and other charges by applying Policy Rules per session or per detailed SDF (Service Data Flow) within the session.

However, from the perspective of 5G Core (UPF/SPGW-U), since the destination address (dynamic IP) transmitted and received by terminals using the Cloud service is very large and changes frequently because the Cloud service uses dynamic IPs that can change each time, and it is practically impossible to manage/procedure such as frequent updates for these numerous dynamic 1Ps per terminal, there is a limitation in that it cannot handle QoS quality control, usage monitoring, and other charges for communication between the terminal and the Cloud service, i.e. data traffic of the Cloud service.

Ultimately, mobile communication networks are unable to realistically control quality (QoS) for the continuously increasing number of cloud services, and various additional services based on quality control are also impossible.

Accordingly, the present invention proposes a new technical method that enables QoS control, such as QoS quality control based on transmission speed, usage monitoring, and other charging, for data traffic of a cloud service using a dynamic address.

First, the concept of the technical solution proposed in the present invention will be briefly explained with reference to FIG. 2.

In the present invention, 5G Core (UPF/SPGW-U) monitors an address request/address response (e.g., DNS Request/DNS Response) transmitted by a terminal to a specific node (e.g., DNS) to determine whether it is a subject of the QoS control of the present invention, and if it is a subject of the QoS control, changes the actual address (e.g., dynamic IP) of the cloud service in the address response (e.g., DNS Response) transmitted to the terminal to a specific virtual destination address and then transmits the response.

This process of changing the address in an address response (e.g. DNS Response) and then replying can be called a "dictation operation" that causes the terminal to forward data traffic of the cloud service to a specific virtual destination address in the form of a fixed address.

Accordingly, the terminal will send and receive data to the cloud service using the changed specific virtual destination address, i.e., the address of the cloud service confirmed from the address response (e.g., DNS Response).

During this process, the 5G Core (UPF/SPGW-U) of the present invention supports communication between the terminal and the corresponding Cloud service by transferring uplink data of the terminal received to a specific virtual destination address to the actual address (e.g., dynamic IP) of the corresponding Cloud service through an address conversion function, and can perform QoS control based on the specific virtual destination address for communication between the terminal and the corresponding Cloud service, i.e., data traffic of the Cloud service.

Here, the address translation function that the present invention can use can adopt a general Proxy/NAT operation, and any operation that enables conversion of a real address <-> a virtual destination address can be adopted without limitation.

Here, referring to FIG. 2 to explain an example, when a terminal establishes a session (e.g. PDU Session: APN/DNN = 5g.sktelecom.com) with 5G Core (UPF/SPGW-U), for each address request (e.g. DNS Request) for the same Cloud service, an address response (e.g. DNS Response) changed to a specific virtual destination address is received, and the Cloud service can be used using the specific virtual destination address.

At this time, from the 5G Core (UPF/SPGW-U) perspective, data traffic of a specific virtual destination address sent by the terminal can be transferred to each dynamic IP through the address translation function (e.g. a), b), c)), to support communication between the terminal and cloud service.

Ultimately, according to the present invention, the terminal performs communication with the cloud service based on a specific virtual destination address in the form of a fixed address regardless of the actual address (e.g., dynamic IP) of the cloud service by means of the 5G Core (UPF/SPGW-U), and from the perspective of the 5G Core (UPF/SPGW-U), not only is there no need to manage/procedure multiple dynamic 1Ps for each terminal using the cloud service, but also QoS control such as QoS quality control, usage monitoring, and other charging can be performed based on the virtual destination address for each cloud service.

As such, the present invention features a specific technical configuration that enables QoS control based on a virtual destination address having a fixed address format for data traffic of a service (e.g., cloud service) using a dynamic address.

Hereinafter, with reference to FIG. 3, we will explain specific technical details for implementing the technology proposed in the present invention, that is, the QoS control method based on a virtual destination address.

Specifically, the present invention proposes a data gateway device and a terminal device that realize the proposed technology, that is, a QoS control method based on a virtual destination address, and FIG. 3 shows the configurations of the data gateway device and the terminal device, respectively.

First, the data gateway device (100) of the present invention will be described in detail.

The data gateway device (100) of the present invention may be at least one of UPF and SPGW-U, and these may be collectively referred to as GW-U.

As shown in FIG. 3, the data gateway device (100) of the present invention is configured to include a conversion unit (110) and a control unit (120).

The entire tactical configuration of the data gateway device (100) or at least a part thereof may be implemented in the form of a hardware module or a software module, or may also be implemented in the form of a combination of hardware modules and software modules.

Here, a software module may be understood as, for example, a command executed by a processor that controls operations within a data gateway device (100), and such a command may have a form loaded into a memory within the data gateway device (100).

Ultimately, the data gateway device (100) of the present invention realizes, through the aforementioned configuration, a technology proposed in the present invention, that is, a technology that enables QoS control based on a virtual destination address in the form of a fixed address for data traffic of a service (e.g., a cloud service) using a dynamic address (e.g., a dynamic IP). Hereinafter, each configuration in the data gateway device (100) for realizing this will be described in more detail.

The conversion unit (110) is responsible for changing the actual address of a specific service to a specific virtual destination address in an address response sent to the terminal (10) in response to a request for an address of a specific service from the terminal (10).

Here, the actual address of a specific service includes at least one dynamic address dynamically allocated to the specific service, and the specific virtual destination address means a fixed address allocated to the specific service.

That is, a specific service to which the present invention can be applied means a service to which at least one floating address is allocated, and there is no limitation on the type or kind of the service, but as an example, in the following description, a Cloud service (20) using a floating address will be mentioned and explained.

That is, the conversion unit (110) can change the actual address of a specific Cloud service (20) to a specific virtual destination address in the address response returned to the terminal (10) in response to an address request from the terminal (10), i.e., an address request for a specific service (hereinafter, a specific Cloud service (20)) using a dynamic address.

To explain one embodiment more specifically, the conversion unit (110) can forward an address request from a terminal (10) to a specific node (30) that holds real-time floating addresses for a number of services, and change the actual address of a specific cloud service (20) to a specific virtual destination address in an address response obtained from a specific node (30) and then send it back to the terminal (10).

At this time, a specific node (30) is a node having a function of holding a real-time dynamic address (e.g., dynamic IP) for each of a plurality of services to which the present invention can be applied, for example, a plurality of cloud services, and as can be seen in FIG. 3, a DNS ( ^{Domain Name System)} , an NRF ^{(Network Repository Function)} , an EASDF ^{(Edge Application Service Discovery Function)} , etc. may correspond to this.

Companies providing cloud services can periodically notify a specific node (30) of their list of accessible addresses (e.g., a list of dynamic IPs) or according to a set event.

Accordingly, when the conversion unit (110) receives an address request (e.g., DNS Request) requesting the address of a specific Cloud service (20) from the terminal (10), it transmits the request to a specific node (30) and obtains an address response (e.g., DNS Response) containing the actual address (e.g., dynamic IP) of the specific Cloud service (20) from the specific node (30).

And, the conversion unit (110) can change the actual address (e.g., dynamic IP) of a specific cloud service (20) to a specific virtual destination address in an address response (e.g., DNS Response) obtained from a specific node (30) and then send it back to the terminal (10).

In the present invention, monitoring an address request/address response (e.g., DNS Request/DNS Response) as described above and changing the actual address (e.g., dynamic IP) of a Cloud service in an address response (e.g., DNS Response) to a specific virtual destination address and then sending a reply can be called a "dictation operation" that causes a terminal to transmit data traffic of a Cloud service to a specific virtual destination address in the form of a determined fixed address.

Accordingly, the terminal (10) will transmit and receive data to a specific Cloud service (20) by using the address of the specific Cloud service (20) confirmed from the address response (e.g., DNS Response), that is, the specific virtual destination address changed by the present invention.

In this way, by the dictation operation of the present invention, the terminal (10) performs communication with a specific Cloud service (20) based on a specific virtual destination address in the form of a fixed address, regardless of the actual address (e.g., dynamic IP) of the specific Cloud service (20). This will be described in more detail later.

Furthermore, the conversion unit (110) can monitor the address request/address response (e.g., DNS Request/DNS Response) of the terminal (10) to determine whether it is a subject of the QoS control of the present invention, and if it is a subject of the QoS control, can specifically allocate a virtual destination address to be used for address change (real address of a specific cloud service (20) -> virtual destination address) in the address response (e.g., DNS Response).

Specifically, the data gateway device (100) of the present invention can receive and retain a virtual destination table set by a control device (e.g., SMF/SPGW-C) that manages/controls sessions for each terminal.

To be more specific, the control device (e.g., SMF/SPGW-C) can check resources for managing Cloud service domain names and fixed IP ^{virtual destination address} resources for each UPF/SPGW-U during the PFCP Association process performed upon initial connection with the data gateway device (100, e.g., UPF/SPGW-U) of the present ^invention and manage them together with other information (e.g., Capability, Service Location, SNSSAI, etc.) of the UPF/SPGW-U. This corresponding information can be used as a factor for selecting the UPF/SPGW-U during the session setup/establishment process of the terminal in the future in the control device (e.g., SMF/SPGW-C).

And, the control device (e.g., SMF/SPGW-C) can set up a virtual destination table to be used as a criterion for allocating a virtual destination address based on the session of the terminal set/established under its control and the identifier (e.g., domain name) of the cloud service, and provide it to the data gateway device (100, e.g., UPF/SPGW-U) involved in the session.

To explain a more specific example, the virtual destination table set by the control device (e.g., SMF/SPGW-C) can be set in detail according to the session status and service mode of the terminal.

The setting contents at this time are elements used to specify/select a virtual destination address to be assigned to a terminal and/or cloud service in the data gateway device (100, e.g. UPF/SPGW-U) of the present invention, and specification/selection may be possible by the following factors.

- Location of the terminal's linked base station/cell, physical actual location of the terminal, status of the terminal/session, capability of the terminal, LTE/NSA/SA mode of the terminal, interfaces available to the data gateway device (e.g. UPF/SPGW-U), virtual IP pools available to the data gateway device (e.g. UPF/SPGW-U), etc.

In addition, the session status of the terminal mentioned in the above description is based on the subscriber profile for the terminal (subscriber) and the type and status of the actual session, and may be as shown in the example below.

·Identify session Idle/Active, H/O status, N/W slice ID

·Subscribers are identified by terminal IP, phone number (IMSI, MSISDN, SUPI, GPSI), etc.

·Identification of subscriber service/product-based status matching the subscriber’s identification

·Identify triggering status when a subscriber enters/exits a specific area (location)

Accordingly, the data gateway device (100, e.g., UPF/SPGW-U) of the present invention can maintain a virtual destination table for terminals/sessions that it participates in data transmission and reception, and the conversion unit (110) can monitor the current address request/address response (e.g., DNS Request/DNS Response) of the terminal (10) based on this virtual destination table to determine whether it is a target of the QoS control of the present invention.

The conversion unit (110) monitors the address request/address response (e.g., DNS Request/DNS Response) and, if it is determined to be a target of QoS control, specifies a virtual destination address based on the virtual destination table according to at least one of the session of the terminal (10) and the identifier (e.g., domain name) of a specific cloud service (20) and allocates it to be used for address change in the current address response (e.g., DNS Response).

Accordingly, in the present invention, the virtual destination address can be allocated differently depending on the status of the terminal/session even when different terminals/sessions access the same cloud service.

And, as described above, the conversion unit (110) can specify/assign a virtual destination address based on the session of the terminal (10) and the identifier (e.g., domain name) of a specific Cloud service (20), and then change the actual address (e.g., dynamic IP) of the Cloud service in the current address response (e.g., DNS Response) to the assigned specific virtual destination address and then send it back to the terminal (10).

Meanwhile, the configuration/structure of the virtual destination address allocated in the present invention may vary.

For example, the virtual destination address allocated in the present invention may be configured to include at least one of v(virtual)IP, vTag, vInterface, vTEID (Tunnel Endpoint Identifier), vDSCP (Differentiated Service Code Point), vLocation, and vContext.

(v)IP enables address separation for the interface of a data gateway device (e.g. UPF/SPGW-U), (v)Tag enables pkt stream differentiation for each protocol, (v)TEID enables identification of a tunneling end point between a data gateway device (e.g. UPF/SPGW-U) and a base station, (v)DSCP enables link QoS control for packet flow, (v)Location enables differentiation of the physical address of each system used for processing the corresponding packet and the location information of the actual terminal, and (v)Context enables specifying the form of a pre-defined packet processing method used for session processing so that the internal processing method can be determined by a patterned operation.

As such, in the present invention, in addition to the identification factors including the aforementioned (v)IP, as a virtual destination address, any identifiable factor that can be allocated and used by a data gateway device (e.g., UPF/SPGW-U) for internal and base station interconnection may be utilized.

Accordingly, the data gateway device (100, e.g., UPF/SPGW-U) of the present invention can identify a virtual destination address for received uplink data.

Figure 4 schematically shows an example of allocating/specifying a virtual destination address in the form of a fixed address in the present invention.

As illustrated in FIG. 4, according to one example, in the present invention, a control device (e.g., SMF) may link with a core node (e.g., AF, NEF, UDM/HLR, PCF/PCRF) to obtain a rate plan product (e.g., Product A) and a Cloud service product (e.g., Cloud Service #1, #2, ...) determined for each rate plan product, and may provide information (e.g., virtual destination table) to be reflected in specifying/selecting a virtual destination address in a data gateway device (e.g., UPF).

And, in the present invention, the data gateway device (e.g., UPF) can internally specify/select and allocate a virtual destination address based on the domain name of the cloud service, and in this process, can manage information (a “virtual destination mapping table” described below) that maps the actual address of the cloud service (e.g., dynamic IP) and the allocated specific virtual destination address (e.g., fixed vIP).

Accordingly, as illustrated in Fig. 4, in the case of a Cloud service having a domain name of "TMAP.CO.KR", the actual IP address may be a dynamic IP such as X, Y, Z, E, T, etc., but may be changed/delivered to a specific virtual destination address, i.e. a fixed vIP, internally allocated to the terminal by a data gateway device (e.g. UPF).

Meanwhile, the data gateway device (100) of the present invention can store/cache the monitored address request/address response (e.g., DNS Request/DNS Response) as described above and manage it as a history (hereinafter, service address request/address response history).

Accordingly, the data gateway device (100) of the present invention, when receiving an address request (e.g., DNS Request) from a terminal (10), can obtain an address response from a specific node (30) only when necessary based on the previously stored service address request/address response history.

Specifically, when receiving an address request (e.g., DNS Request) from a terminal (10), the conversion unit (110) can, only when it is determined that there is no address request identical to the current address request (e.g., DNS Request) in the previously stored service address request/address response history, transmit the current address request (e.g., DNS Request) to a specific node (30) as described above, obtain an address response (e.g., DNS Response), change the internal address, and then return the address response (e.g., DNS Response) to the terminal (10).

At this time, whether there is an "identical address request" in the service address request/address response history (e.g. DNS Request) can be determined through analysis of the details below.

- Same location, terminal session status, same time (within the period), same terminal prefix, etc.

- Identifiers of the same Cloud service (e.g. domain name)

That is, when receiving an address request (e.g., DNS Request) from a terminal (10), the conversion unit (110) can determine whether there is an address request for the same terminal/session/cloud service as the current address request (e.g., DNS Request) in the service address request/address response history through analysis of the above details.

And, when the conversion unit (110) receives an address request (e.g., DNS Request) from the terminal (10), if it is determined that there is an address request identical to the current address request (e.g., DNS Request) in the previously stored service address request/address response history, the conversion unit (110) may not forward the current address request (e.g., DNS Request) to a specific node (30).

Instead, the conversion unit (110) can extract an address response (e.g., DNS Response) that was previously replied to the current address request (e.g., DNS Request) from the service address request/address response history, i.e., an address response (e.g., DNS Response) that was replied to by changing the internal address (real address -> specific virtual destination address) for the same address request in the past, and immediately reply to the terminal (10).

The control unit (120) supports communication between a terminal (10) and a specific cloud service (20) by transferring uplink data of a terminal (10) received at a specific virtual destination address to the actual address of a specific cloud service (20) through an address conversion function, and is responsible for performing QoS (Quality of Service) control based on a specific virtual destination address for communication between the terminal (10) and the specific cloud service (20).

Here, the address translation function can adopt general Proxy/NAT operation, and any operation that enables conversion of real address (e.g. IP/Port) <-> virtual destination address (e.g. IP/Port) can be adopted without limitation.

Meanwhile, the control unit (120), in conjunction with the conversion unit (110), can generate/manage mapping information according to the content of allocation and transmission of a specific virtual destination address to the terminal session and Cloud service, that is, information (a “virtual destination mapping table” described below) that maps the actual address (e.g., dynamic IP) of the Cloud service and the allocated specific virtual destination address.

This virtual destination mapping table may be configured to include at least one of session and address information of a terminal, an identifier (e.g., domain name) of a service (e.g., cloud service), a real address (e.g., dynamic address) of the service (e.g., cloud service), a virtual destination address assigned to the service (e.g., cloud service), and an external address (e.g., external IP between GW and service) assigned to be used as an address of the terminal by mapping with a real address of the service (e.g., cloud service) in an address translation function.

FIG. 7 illustrates an example of a virtual destination mapping table managed in a data gateway device (100, e.g., UPF/SPGW-U) of the present invention.

As illustrated in FIG. 7, the virtual destination mapping table can be configured/managed to include terminal/session and Src. (Source) IP as items representing terminal session and address information, Dst. (Destination) IP as an item representing the actual address of the Cloud service, and an item representing the virtual destination address mapped to the actual address of the Cloud service.

And, as explained above, the virtual destination address can be allocated/mapped in the form of a fixed address that combines at least one of vIP, vTag, vInterface, vTEID, vDSCP, vLoc., and vContext.

In this way, the data gateway device (100, e.g., UPF/SPGW-U) of the present invention can specify/set the virtual destination address of the uplink of the data gateway device (100, e.g., UPF/SPGW-U) connected to the RAN according to the source address (e.g., IP/Port) and session of the terminal and send it to the terminal. Accordingly, as can be seen in FIG. 7, information such as QoS control and terminal status (location, etc.) information, including actual physical interface information and virtual interface information, can be maintained/managed in the form of a table.

For example, it is possible to force a terminal to connect to a number of real dynamic IPs (Dst. IPs) by specifying/changing them to connect to a virtual destination address (e.g. vIP, vIF, ...). Through this, in the present invention, a "dictation operation" can be performed so that the terminal communicates with a virtual destination address (e.g. vIP, vIF, ...) in the form of a (changed) fixed address, as in the following examples.

Example 1: Specify the virtual destination address vIP (10.0.0.1) for the terminal (Sec. IP A/Session A) and assign it to the terminal -> The terminal (Sec. IP A/Session A) sends and receives data to 10.0.0.1.

Example 2: Specify virtual destination address vIF (S1U_#1) for terminal (Sec. IP A/Session A) -> Terminal (Sec. IP A/Session A) transmits and receives data to S1U_#1

That is, even if the terminal attempts to connect to a service server having an actual physical IP (e.g., X1, Y1, Z1, ...), the terminal may recognize that it is communicating with a fixed address (e.g., 10.0.0.1) changed by the data gateway device (100, e.g., UPF/SPGW-U) of the present invention and attempt to transmit and receive data. Afterwards, data communication to the actual physical IP (e.g., X1, Y1, Z1, ...) of the service server may become possible according to the address conversion function of the data gateway device (100, e.g., UPF/SPGW-U) of the present invention.

Meanwhile, in addition to the example illustrated in FIG. 7, the virtual destination mapping table may be configured/managed to further include an item indicating the domain name of the corresponding Cloud service and an item indicating an external address (e.g., an external IP between GW and service) mapped and allocated for each actual address of the corresponding Cloud service.

In addition, uplink data of a terminal (10) received to a specific virtual destination address can be detected/identified at the N3, S1U, N9 Interface between a RAN (Radio Access Network) and a data gateway device (100, e.g., UPF/SPGW-U).

Here, the function of the control unit (120) will be described in detail again. The control unit (120) can determine whether data received from the N3, S1U, and N9 interfaces, i.e., uplink data, is subject to the QoS control of the present invention based on the virtual destination mapping table managed as described above.

For example, if the control unit (120) confirms, based on the virtual destination mapping table, the source address and/or session information of data received from the N3, S1U, and N9 interfaces, that is, uplink data, the address and/or session of a terminal (e.g., 10) that has applied the “dictation operation” to the destination address, and a specific virtual destination address, the control unit (120) can determine the corresponding uplink data as a QoS control target of the present invention, more specifically, “uplink data of a terminal (10) received to a specific virtual destination address.”

Accordingly, the control unit (120) can support communication between the terminal (10) and the specific Cloud service (20) by transferring the uplink data of the terminal (10) received at a specific virtual destination address assigned to a specific Cloud service (20) and transferred to the terminal (10) to the actual address (e.g., dynamic IP) of the specific Cloud service (20) through an address conversion function.

For example, the control unit (120) may perform the address conversion function directly, but the address conversion function may be performed in a transceiver as shown in FIG. 3.

That is, within the data gateway device (100, e.g., UPF/SPGW-U) of the present invention, the transceiver directly performs an address conversion function to connect communication between a terminal and an actual cloud service. The role of this transceiver is a data traffic processing technology of a general Proxy/NAT operation, and will be explained again in the description with reference to FIG. 6 below.

Meanwhile, the control unit (120) can perform QoS control based on a specific virtual destination address for communication between a terminal (10) and a specific Cloud service (20) based on the "dictation operation" of the present invention and the role of connecting communication between a terminal and an actual Cloud service.

Here, QoS control includes at least one of transmission speed-based quality control, usage measurement, and billing processing for communication between a terminal and a specific service (e.g., cloud service).

That is, the data gateway device (100, e.g., UPF/SPGW-U) of the present invention performs QoS control based on a virtual destination address for service-related communication based on a floating address used by a terminal, thereby performing QoS control such as QoS quality control/usage/charging processing based on transmission speed for the uplink of the terminal in virtual EndPoint units (utilizing a virtual destination address).

As described above, the data gateway device (100, e.g., UPF/SPGW-U) of the present invention controls N3, S1U, N9 Interfaces coming from RAN, and this control criterion is a virtual destination mapping table in which terminal addresses and/or sessions, Cloud service identifiers (e.g., domain names), actual addresses, virtual destination addresses, etc. are mapped/managed in relation to the "dictation operation". That is, a virtual destination address is assigned to each interface.

Accordingly, the data gateway device (100, e.g., UPF/SPGW-U) of the present invention can manage one destination virtual address per Cloud service within a terminal session based on a virtual destination mapping table. Accordingly, when processing data traffic between the terminal and the Cloud, the terminal performs data transmission and reception using one (virtual) EndPoint as a destination address, and can utilize communication with an actual Cloud service server controlled/adjusted according to QoS control performed per (virtual) EndPoint in the present invention.

Below, the terminal device (10) of the present invention will be described in detail with reference to FIG. 3.

As shown in Figure 3, the terminal device (10) of the present invention is configured to include an address request unit (11), a data transmission/reception unit (110), and a control unit (120).

The entire tactical configuration of such terminal device (10) or at least a part thereof may be implemented in the form of a hardware module or a software module, or may also be implemented in the form of a combination of hardware modules and software modules.

Here, a software module may be understood as, for example, a command executed by a processor that controls operations within a terminal device (10), and such a command may have a form loaded into a memory within the terminal device (10).

Ultimately, the terminal device (10) of the present invention realizes, through the aforementioned configuration, the technology proposed in the present invention, that is, a technology that enables QoS control based on a virtual destination address in the form of a fixed address for data traffic of a service (e.g., a cloud service) using a dynamic address (e.g., a dynamic IP). Hereinafter, each configuration in the terminal device (10) for realizing this will be described in more detail.

The address request section (11) can request an address for a specific service.

Here, the actual address of a specific service includes at least one dynamic address dynamically allocated to the specific service, and the specific virtual destination address means a fixed address allocated to the specific service.

That is, a specific service to which the present invention can be applied means a service to which at least one floating address is allocated, and there is no limitation on the type or kind of the service, but as an example, a Cloud service (20) using a floating address will be mentioned in the following description.

When a terminal device (10) wishes to use a specific service (hereinafter, a specific Cloud service (20)) that uses a floating address, the address request unit (11) requests an address for the specific Cloud service (20).

Typically, a terminal device (10) transmits an address request to a specific node (30, e.g., DNS Server, NRF, EASDF, ...) that holds a real-time dynamic address (e.g., dynamic IP) for each of a number of cloud services.

Accordingly, in the present invention, a terminal device (10, address request unit (11)) can perform a pre-operation so that it can transmit an address request to a data gateway device (100, e.g., UPF/SPGW-U) of the present invention.

For example, in the present invention, when setting up/establishing a session for a terminal device (10), the control device (e.g., SMF/SPGW-C) may include information to use a data gateway device (100, e.g., UPF/SPGW-U) involved in the session when requesting an address of a specific service (e.g., Cloud service) in the PCO ^{Protocol Configuration Options} or EPCO ^{Extended Protocol Configuration Options} and transmit it to the terminal device (10).

Accordingly, when a terminal device (10) wishes to use a specific Cloud service (20) that uses a dynamic address, the address request unit (11) can transmit an address request (e.g., DNS Request) for a specific Cloud service (20) to the data gateway device (100, e.g., UPF/SPGW-U) of the present invention based on information obtained during the session setup/establishment process.

The data transmission and reception unit (12) is responsible for the function of performing data transmission and reception with a specific Cloud service (20) by using the address of the specific Cloud service (20) confirmed from an address response (e.g., DNS Response) returned in response to an address request (e.g., DNS Request).

That is, the data transmission/reception unit (12) can communicate with a specific Cloud service (20) by transmitting uplink data using the address of a specific Cloud service (20) confirmed from an address response (e.g., DNS Response) as a destination address, and then receiving next link data in which the address of the specific Cloud service (20) is used as a source address.

At this time, the address of a specific service, such as a specific Cloud service (20), identified from an address response (e.g., DNS Response) may be the actual address of the specific Cloud service (20) or a specific virtual destination address changed by a data gateway device involved in the data transmission and reception.

As described above, the data gateway device (100, e.g., UPF/SPGW-U) of the present invention monitors the current address request/address response (e.g., DNS Request/DNS Response) of the terminal device (10) to determine whether it is a target of the QoS control of the present invention, and if it determines that it is not a target of the QoS control, it can reply to the terminal device (10) as is without changing the address in the address response (e.g., DNS Response).

In this case, the address of a specific Cloud service (20) confirmed from an address response (e.g., DNS Response) will be the actual address (e.g., dynamic 1P) of the specific Cloud service (20), and the data transmission/reception unit (12) can use the address of the specific Cloud service (20) confirmed from the address response (e.g., DNS Response), i.e., the actual address (e.g., dynamic 1P), as a destination address to communicate with the specific Cloud service (20).

Meanwhile, the data gateway device (100, e.g., UPF/SPGW-U) of the present invention monitors the current address request/address response (e.g., DNS Request/DNS Response) of the terminal device (10) to determine whether it is a target of the QoS control of the present invention, and if it determines that it is a target of the QoS control, it can change the address in the address response (e.g., DNS Response) (the actual address of a specific Cloud service (20) -> a specific virtual destination address) and send it back to the terminal device (10) (dictation operation).

In this case, the address of a specific Cloud service (20) identified from an address response (e.g., DNS Response) will be a virtual destination address in the form of a fixed address assigned to a specific Cloud service (20), and the data transmission/reception unit (12) can use the address of a specific Cloud service (20) identified from an address response (e.g., DNS Response), i.e., a specific virtual destination address, as a destination address to communicate with a specific Cloud service (20).

Accordingly, the terminal device (10) will transmit and receive data to a specific Cloud service (20) by using the address of the specific Cloud service (20) confirmed from the address response (e.g., DNS Response), that is, the specific virtual destination address changed by the present invention.

In this way, by the dictation operation of the present invention, the terminal device (10) performs communication with a specific Cloud service (20) based on a specific virtual destination address in the form of a fixed address, regardless of the actual address (e.g., dynamic IP) of the specific Cloud service (20).

For reference, from the perspective of the terminal device (100), an address response (e.g., DNS Response) returned in response to an address request (e.g., DNS Request) may be obtained from a specific node (30, e.g., DNS Server, NRF, EADSF, ...) and then the internal address may be changed, or may be extracted from the details managed within the data gateway device (100, e.g., UPF/SPGW-U) of the present invention.

In addition, in the present invention, the actual address of the cloud service and the virtual destination address specified/allocated thereto are not necessarily required to be different, and depending on the need/situation, the actual address = virtual destination address may be the same.

For example, it may be difficult to change the address of a service (e.g., cloud service) for a specific terminal device due to various necessary/situational 'restrictions' such as device characteristics of the terminal device or app characteristics.

Reflecting such cases, in the present invention, when responding to an address request/address response (e.g., DNS Request/DNS Response) of a specific terminal device, address information identical to the actual address (e.g., dynamic IP) of a service (e.g., cloud service) can be specified/allocated as a virtual destination address and sent in response.

Even in this case, the data gateway device (100, e.g., UPF/SPGW-U) of the present invention can support communication between a specific terminal device and a service (e.g., cloud service) through an address conversion function as described above, and can perform QoS control based on a virtual destination address.

As described above, according to the data gateway device and terminal device of the present invention, a specific technical configuration capable of performing fixed address-based QoS control for data traffic of a service (e.g., cloud service) using a dynamic address is realized.

Accordingly, according to the present invention, QoS control is enabled for data traffic of a service (e.g., a cloud service) using a dynamic address, thereby improving the service quality through flexible service quality provision for the service (e.g., a cloud service).

Figures 5 and 6 show Call-Flow examples that realize fixed address (virtual destination address) based QoS control of the present invention.

In Fig. 5, the data gateway device of the present invention is illustrated as UPF/SPGW-U (100), and the terminal device of the present invention is illustrated as terminal (10).

As illustrated in Figure 5, SMF/SPGW-C basically manages UPF/SPGW-U and can also manage resources for Cloud service ^{domain name} management by UPF/SPGW-U and fixed IP ^{virtual destination address} resources.

Based on this management, SMF/SPGW-C can set up and transmit a virtual destination table to be used as a criterion for allocating virtual destination addresses according to terminal sessions and cloud services for each UPF/SPGW-U.

Accordingly, when the UPF/SPGW-U (100) receives a DNS Request for a specific Cloud service from the terminal (10), it forwards it to the DNS (30) and obtains a DNS Response containing the actual address (e.g., dynamic IP) of the specific Cloud service from the DNS (30) and stores it internally (LDNS, Local DNS) (①).

And, UPF/SPGW-U (100) monitors the current address request/address response (e.g. DNS Request/DNS Response) based on the virtual destination table, to determine whether the terminal (10)/session is subject to QoS control of the present invention, including whether the terminal (10)/session is subject to QoS control (e.g. Zero Rating 1,...,N) and whether a specific Cloud service is a dynamic Domain subscriber, and if determined to be a QoS control target, changes the actual dynamic IP of the Cloud service in the DNS Response returned to the terminal (10) to a specific virtual destination address in the form of a fixed IP and then returns the response (②).

In this case, the terminal (10) will transmit uplink data to the cloud service using the address of the specific cloud service confirmed from the DNS response, i.e., the changed specific virtual destination address.

Accordingly, UPF/SPGW-U (100) identifies uplink data for a specific Cloud service of a terminal (10) received from N3, S1U, N9 Interface (terminal (10)/session, identification based on a specific virtual destination address), and connects/transmits the corresponding uplink data to the actual dynamic IP of the specific Cloud service through an address translation function (e.g., NAT/Proxy) within UPF/SPGW-U (100) to support communication between the terminal (10) and a specific Cloud service (20) (③).

In addition, UPF/SPGW-U (100) performs QoS control, such as processing CDR/charging based on a specific virtual destination address (SVC_ID) used as a fixed IP for uplink data for a specific Cloud service of the terminal (10), thereby performing virtual destination address-based QoS control for communication between the terminal (10) and a specific Cloud service based on a floating address (③).

FIG. 6 shows another Call-Flow example that realizes fixed address (virtual destination address) based QoS control of the present invention.

In Fig. 6, the data gateway device of the present invention is illustrated as UPF/SPGW-U (100), the terminal device of the present invention is illustrated as terminal A, the function of the conversion unit (110) described above is illustrated as Local DNS, and the function of the transceiver (Local NAT) is illustrated as being included in the control unit (120) described above.

When UPF/SPGW-U (100) receives a DNS request for a specific cloud service (e.g. TMAP.co.kr) from terminal A (1.), it caches it (2a.) and forwards it to DNS (30) (2b.) so that it can obtain a DNS response (domain response) containing the actual dynamic IP of the specific cloud service (e.g. TMAP.co.kr) from DNS (30) (3a).

UPF/SPGW-U (100) monitors the current address request/address response (e.g. DNS Request/DNS Response) and, if it is a target of QoS control of the present invention, changes the actual dynamic IP of the cloud service in the DNS Response returned to terminal A to a specific virtual destination address in the form of a fixed IP (e.g. 50.0.0.1 -> 10.0.0.1) and then returns the response (3b./4.).

As described above, the entire process from 1. to 4. of the above-described strategy, which monitors address requests/address responses (e.g., DNS Request/DNS Response) and changes the actual address (e.g., dynamic IP) of the Cloud service in the address response (e.g., DNS Response) to a specific virtual destination address and then replies, can be called a "dictation operation" that causes terminal A to forward the data traffic of the Cloud service to a specific virtual destination address in the form of a determined fixed address.

In this case, terminal A will transmit uplink data to the cloud service using the address of the specific cloud service confirmed from the DNS response, i.e. the changed specific virtual destination address (10.0.0.1) (1.).

Accordingly, UPF/SPGW-U (100) identifies uplink data for a specific Cloud service of Terminal A received from N3, S1U, and N9 Interfaces (terminal A/session, identification based on a specific virtual destination address), connects/forwards the corresponding uplink data to the actual dynamic IP of the specific Cloud service through an address translation function (e.g., Local NAT) (sIP: Terminal A IP_A -> GW~Service external IP_20.0.0.1, dIP: Specific virtual destination address_10.0.0.1 -> Actual dynamic IP_50.0.0.1) (a., b-1., b-2.), and conversely, forwards downlink data received from a specific Cloud service to Terminal A (sIP: Actual dynamic IP_50.0.0.1 -> Specific virtual destination address_10.0.0.1, dIP: GW~Service external IP_20.0.0.1 -> Terminal A IP_A), and connects/forwards the corresponding uplink data to the actual dynamic IP of the specific Cloud service through an address translation function (e.g., Local NAT). It can support communication (D-1., D-2., D.)

In addition, UPF/SPGW-U (100) can perform QoS control, such as performing CDR generation and charging processing based on a virtual destination address in the form of a fixed IP allocated/set for each uplink data of terminal A's cloud service through N3, S1U, and N9 Interface control coming from RAN.

FIGS. 8 to 10 are flowcharts showing examples of control scenarios in which the QoS control method of the present invention is performed.

In Fig. 8, the data gateway device of the present invention is illustrated as GW-U (UPF/SPGW-U) (100), and the terminal device of the present invention is illustrated as UE (10).

As illustrated in FIG. 8, in the present invention, during the PFCP Association process performed when initially connecting with the GW-U (100), the GW-C (SMF/SPGW-C) can check resources for managing the Cloud service ^{domain name} for each GW-U and the fixed IP ^{virtual destination address} resources and manage them together with other information of the GW-U.

Meanwhile, during the session setup/establishment process (Session Establishment) of the UE (10), the GW-C (SMF/SPGW-C) can include information in the PCO or EPCO to use the LDNS of the GW-U (100) involved in the session when requesting an address of a specific service (e.g., Cloud service (20)) and transmit it to the UE (10). In addition, the GW-C (SMF/SPGW-C) can set up and provide a virtual destination table related to the GW-U (100) involved in the session.

Accordingly, when a specific Cloud service (20) is to be used in the UE (10) of the present invention, an address request (e.g., DNS Query) for the specific Cloud service (20) is transmitted to the GW-U (100) based on the information obtained during the session setup/establishment process, and a query can be performed with the LDNS of the GW-U (100).

The LDNS in the GW-U (100) of the present invention can obtain an address response (e.g., DNS Response) containing the actual address of a specific cloud service (20) by transmitting the current address request (e.g., DNS Query) to the DNS (30) in the core or the upper DNS (30).

The GW-U (100) of the present invention monitors the address request/address response (e.g., DNS Request/DNS Response) to determine whether it is a QoS control target of the present invention, and if it is a QoS control target, changes the actual address (e.g., dynamic IP) of the cloud service (20) in the address response (e.g., DNS Response) returned to the terminal to a specific virtual destination address and then returns the response.

In this case, the UE (10) will transmit uplink data to the Cloud service (20) using the address of the specific Cloud service (20) confirmed from the address response (e.g., DNS Response), i.e., the changed specific virtual destination address (data w/ virtual destination address).

The GW-U (100) of the present invention identifies uplink data for a specific Cloud service (20) of a UE (10) received from an N3, S1U, and N9 Interface, and transfers the uplink data to an actual floating IP of a specific Cloud service (20) through an address translation function (e.g., NAT/Proxy) within the GW-U (100) to support communication between the UE (10) and the specific Cloud service (20), while performing QoS control based on a virtual destination address for the communication.

In this way, clear QoS control of data traffic between the UE (10) and the GW-U (100) during communication between the UE (10) and a specific cloud service (20) based on a dynamic address is possible by the GW-U (100) of the present invention.

In conclusion, according to the present invention, a terminal performs communication based on a fixed IP (virtual destination address) regardless of whether an actual service providing server has a dynamic IP, by means of GW-U (UPF/SPGW-U), and based on the fixed IP, it is possible to derive the effect of performing QoS control operations of GW-U (UPF/SPGW-U), such as QoS quality control based on transmission speed, usage measurement, and billing processing, more efficiently using fewer physical resources.

Hereinafter, with reference to FIGS. 9 and 10, the flow of performing the QoS control method of the present invention from the perspective of the GW-U (UPF/SPGW-U) of the present invention will be specifically described.

First, referring to FIG. 9, according to the QoS control method of the present invention, when an address request (e.g., DNS Request) requesting an address of a specific Cloud service (20) is received from a terminal (10) (S10), the GW-U (UPF/SPGW-U) determines whether there is an address request identical to the current address request (e.g., DNS Request) in the previously stored service address request/address response history (S20).

To this end, according to the QoS control method of the present invention, the GW-U (UPF/SPGW-U) can store/cache address requests/address responses (e.g., DNS Request/DNS Response) and manage them as history (hereinafter, service address request/address response history).

In other words, according to the QoS control method of the present invention, if the GW-U (UPF/SPGW-U) determines that there is no address request identical to the current address request (e.g., DNS Request) in the service address request/address response history (S20 No), the GW-U can forward the current address request (e.g., DNS Request) to a specific node (e.g., DNS Server, NRF, EASDF, ...) to obtain an address response (e.g., DNS Response) including the actual address (e.g., dynamic IP) of a specific Cloud service (20) (S30).

And, according to the QoS control method of the present invention, the GW-U (UPF/SPGW-U) can monitor the current address request/address response (e.g., DNS Request/DNS Response) to determine whether it is a target of the QoS control of the present invention (S40).

Specifically, the GW-U (UPF/SPGW-U) can maintain a virtual destination table for terminals/sessions that it participates in data transmission and reception, and can monitor the current address request/address response (e.g., DNS Request/DNS Response) of the terminal (10) based on this virtual destination table to determine whether it is a target of the QoS control of the present invention.

According to the QoS control method of the present invention, if the GW-U (UPF/SPGW-U) determines that the current address request/address response (e.g., DNS Request/DNS Response) is a target of QoS control by monitoring it (S40 Yes), prior to allocating a virtual destination address, it may further determine whether there is a Capability that can allocate a virtual destination address (e.g., idle virtual destination address resources, idle Mapping Table resources, etc.) (S50).

Accordingly, according to the QoS control method of the present invention, if virtual destination address allocation is possible (S50 Yes), a virtual destination address according to at least one of the session of the terminal (10) and the identifier (e.g., domain name) of a specific cloud service (20) can be specified and allocated to be used for address change in the current address response (e.g., DNS Response) (S60).

And, according to the QoS control method of the present invention, the GW-U (UPF/SPGW-U) can change the actual address (e.g., dynamic IP) of the cloud service in the current address response (e.g., DNS Response) to a specific virtual destination address allocated in step S60 and then send it back to the terminal (10) (S70, S80).

Meanwhile, according to the QoS control method of the present invention, if the GW-U (UPF/SPGW-U) determines that there is an address request identical to the current address request (e.g., DNS Request) in the service address request/address response history (S20 Yes), it can extract an address response (e.g., DNS Response) that was replied to the current address request (e.g., DNS Request) in the past from the service address request/address response history, that is, an address response (e.g., DNS Response) that was replied to by changing the internal address (real address -> specific virtual destination address) for the same address request in the past, and immediately reply to the terminal (10) (S25, S80).

As in the S70, S80 or S25, S80 described above, changing the address in the address response (e.g. DNS Response) and then replying can be called a "dictation operation" that causes the terminal to forward data traffic of the Cloud service to a specific virtual destination address in the form of a fixed address.

In this case, the terminal (10) will transmit uplink data to a specific Cloud service (20) using the address of a specific Cloud service confirmed from an address response (e.g., DNS Response), i.e., a changed specific virtual destination address.

Meanwhile, according to the QoS control method of the present invention, if the GW-U (UPF/SPGW-U) determines that it is not a QoS control target (S40 No), it can return the current address response (e.g. DNS Response) to the terminal (10) without changing the address (S65).

In addition, according to the QoS control method of the present invention, if the GW-U (UPF/SPGW-U) is determined to be a QoS control target (S40 Yes) but virtual destination address allocation is impossible (S50 No), the GW-U (UPF/SPGW-U) re-selection is requested from a corresponding GW-C such as an SMF or SPGW-C, if necessary (S55), and the current address response (e.g., DNS Response) can be returned to the terminal (10) as is without address change (S65).

Referring to FIG. 10 for further explanation, according to the QoS control method of the present invention, when data, i.e., uplink data, is received from the N3, S1U, and N9 interfaces (S100), the GW-U (UPF/SPGW-U) can determine whether the uplink data is a target of the QoS control of the present invention (S110).

Specifically, when the GW-U (UPF/SPGW-U) identifies, based on the virtual destination mapping table, the source address and/or session information of uplink data, the address and/or session of a terminal (e.g., 10) that applied the “dictation operation” to the destination address, and a specific virtual destination address, the GW-U can determine the corresponding uplink data as a QoS control target of the present invention, more specifically, “uplink data of a terminal (10) received to a specific virtual destination address” (S110 Yes).

Accordingly, according to the QoS control method of the present invention, the GW-U (UPF/SPGW-U) can support communication between the terminal (10) and the specific Cloud service (20) by transferring the uplink data determined to be a QoS control target, for example, the uplink data of the terminal (10) received to a specific virtual destination address assigned to a specific Cloud service (20), to the actual address (e.g., dynamic IP) of the specific Cloud service (20) through an address translation function (e.g., Local NAT) (S120).

In addition, according to the QoS control method of the present invention, the GW-U (UPF/SPGW-U) can perform QoS control based on a specific virtual destination address in relation to communication between a terminal (10) and a specific Cloud service (20) that supports uplink data of the terminal (10) received to a specific virtual destination address (S120).

That is, GW-U (UPF/SPGW-U) can perform QoS control based on a specific virtual destination address for communication between a terminal (10) and a specific Cloud service (20) based on the "dictation operation" of the present invention and its role in connecting communication between a terminal and an actual Cloud service.

Here, QoS control includes at least one of transmission speed-based quality control, usage measurement, and billing processing for communication between a terminal and a specific service (e.g., cloud service).

That is, according to the QoS control method of the present invention, the GW-U (UPF/SPGW-U) performs QoS control based on a virtual destination address for service-related communication based on a dynamic address used by the terminal, thereby performing QoS control such as QoS quality control/usage/charging processing based on transmission speed for the uplink of the terminal in virtual EndPoint units (utilizing the virtual destination address).

According to the QoS control method of the present invention, the GW-U (UPF/SPGW-U) can continuously perform QoS control based on a specific virtual destination address for communication between the terminal (10) and a specific Cloud service (20) by performing step S110 and subsequent steps until communication between the terminal (10) and a specific Cloud service (20) is terminated (S130 No).

Meanwhile, according to the QoS control method of the present invention, if the GW-U (UPF/SPGW-U) determines in step S110 that the current uplink data is not subject to QoS control (S110 No), it will transfer the corresponding uplink data to a service of the destination address (e.g., general data service, Cloud service, etc.) to support communication between the terminal (10) and the corresponding service (e.g., general data service, Cloud service, etc.) (S140).

As described above, according to the QoS control method of the present invention, a specific technical configuration is realized that can perform fixed address-based QoS control for data traffic of a service (e.g., cloud service) using a dynamic address.

Accordingly, according to the present invention, QoS control is enabled for data traffic of a service (e.g., a cloud service) using a dynamic address, thereby improving the service quality through flexible service quality provision for the service (e.g., a cloud service).

The QoS control method according to an embodiment of the present invention may be implemented in the form of a program command that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may include program commands, data files, data structures, etc., singly or in combination. The program commands recorded on the medium may be those specially designed and configured for the present invention or may be those known to and usable by those skilled in the art of computer software. Examples of the computer-readable recording medium include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and hardware devices specially configured to store and execute program commands such as ROMs, RAMs, and flash memories. Examples of the program commands include not only machine language codes generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc. The above hardware devices may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

Although the present invention has been described in detail with reference to preferred embodiments thereof, the present invention is not limited to the above-described embodiments, and it will be understood by those skilled in the art that various modifications or variations can be made therein without departing from the gist of the present invention as claimed in the following claims.

According to the data gateway device of the present invention and the QoS control method and terminal device performed in the device, the present invention is a new technology capable of performing fixed address-based QoS control even for data traffic of a service using a dynamic address (e.g., cloud service), and thus, by overcoming the limitations of existing technologies, it is an invention with industrial applicability because it is not only possible to utilize related technologies but also to market or sell applicable devices, and is clearly implementable in reality.

100 : Data Gateway Device
110: Conversion section 120: Control section
10: Terminal device
11: Address request section 12: Data transmission/reception section

Claims (14)

A conversion unit that changes the actual address of a specific service to a specific virtual destination address in an address response returned to the terminal in response to a request for an address of a specific service from the terminal; and
A control unit is included that supports communication between the terminal and the specific service by transmitting the uplink data of the terminal received to the specific virtual destination address to the actual address of the specific service through an address conversion function, and performs QoS (Quality of Service) control based on the specific virtual destination address for the communication;
A data gateway device, characterized in that the specific virtual destination address is a fixed address assigned to the specific service, regardless of the actual address of the specific service. In paragraph 1,
The above QoS control is,
A data gateway device characterized by including at least one of quality control based on transmission speed, usage measurement, and billing processing for communication between the terminal and the specific service. In paragraph 1,
A data gateway device, characterized in that the actual address of the specific service includes at least one dynamic address dynamically allocated for the specific service. In paragraph 1,
The above conversion part,
Based on the preset virtual destination table, a virtual destination address is specified according to at least one of the session identifiers of the terminal and the identifier of the specific service, and is allocated to be used for changing the address response.
The above virtual destination table is,
A data gateway device characterized in that it is set and transmitted by a control device that manages/controls sessions for each terminal. In paragraph 1,
The above virtual destination address is,
A data gateway device characterized by comprising at least one of v(virtual)IP, vTag, vInterface, vTEID(Tunnel Endpoint Identifier), vDSCP(Differentiated Service Code Point), vLocation, and vContext. In paragraph 1,
The above conversion part,
The address request is forwarded to a specific node that holds real-time floating addresses for a number of services, and the address response obtained from the specific node is changed to the specific virtual destination address and then returned to the terminal.
A data gateway device characterized in that, when an address request identical to the address request of the specific service is determined to be present in the history of previously stored service address requests/address responses, an address response changed to the specific virtual destination address is extracted from the history of the service address requests/address responses and is returned to the terminal. In paragraph 1,
The uplink data of the terminal received to the above specific virtual destination address is:
A data gateway device characterized by being detected at the N3, S1U, N9 Interface between the RAN (Radio Access Network) and the data gateway device. In paragraph 1,
The above control unit manages a virtual destination mapping table in conjunction with the above conversion unit,
The above virtual destination mapping table is:
A data gateway device characterized in that it is configured to include at least one of session and address information of a terminal, an identifier of a service, a real address of the service, a virtual destination address assigned to the service, and an external address assigned to be used as an address of the terminal by mapping to the real address of the service in the address conversion function. An address request section requesting an address for a specific service; and
A data transmission/reception unit is included for performing data transmission/reception with the specific service by using the address of the specific service confirmed from the address response in response to the address request;
The address of the specific service identified from the above address response is,
The actual address of the above specific service or a specific virtual destination address changed by the data gateway device involved in transmitting and receiving the above data,
A terminal device, characterized in that the specific virtual destination address is a fixed address assigned to the specific service, regardless of the actual address of the specific service. In a QoS control method performed in a data gateway device,
A conversion step for changing the actual address of a specific service to a specific virtual destination address in an address response returned to the terminal in response to a request for an address of a specific service from the terminal; and
A method of supporting communication between the terminal and the specific service by transmitting uplink data of the terminal received to the specific virtual destination address to the actual address of the specific service through an address conversion function, the method including a control step of performing QoS (Quality of Service) control based on the specific virtual destination address for the communication;
A QoS control method, characterized in that the specific virtual destination address is a fixed address assigned to the specific service, regardless of the actual address of the specific service. In Article 10,
The above QoS control is,
A QoS control method characterized by including at least one of quality control based on transmission speed, usage measurement, and billing processing for communication between the terminal and the specific service. In Article 10,
A QoS control method, characterized in that the actual address of the specific service includes at least one dynamic address dynamically allocated for the specific service. In Article 10,
The above virtual destination address is,
A QoS control method characterized by comprising at least one of v(virtual)IP, vTag, vInterface, vTEID(Tunnel Endpoint Identifier), vDSCP(Differentiated Service Code Point), vLocation, and vContext. In Article 10,
The uplink data of the terminal received to the above specific virtual destination address is:
A QoS control method characterized in that it is detected at the N3, S1U, N9 Interface between the RAN (Radio Access Network) and the data gateway device.

Images