Method and apparatus for offloading data in a wireless communication system

Through coordination between user equipment and servers in the 6G communication system, selecting a suitable server to process smart device data, solving the problem of low data processing efficiency of smart device and achieving flexible data offloading and processing.

CN114762383BActive Publication Date: 2024-11-19SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080082805.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-11-29
Filing Date
2020-11-30
Publication Date
2024-11-19
Estimated Expiration
2040-11-30

AI Technical Summary

Technical Problem

In 6G communication systems, the amount of data processed by the smart device increases and types are diverse, and a technology that can unload data according to changing channel conditions and server environment is needed to improve data processing efficiency.

Method used

The user equipment (UE) determines the appropriate server, receives a list of split points, selects an unloading point and sends corresponding demand information, whether the server can process data in response, and decides whether to perform data unloading based on the response, and can be used during the data processing process. Change the uninstall point or requirement.

Benefits of technology

It realizes data offloading according to different needs and environmental conditions, improves the efficiency and flexibility of data processing, and is suitable for diversified intelligent device data processing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114762383B_ABST
    Figure CN114762383B_ABST
Patent Text Reader

Abstract

A method and apparatus for offloading data in a wireless communication system are provided. The method performed by a user equipment UE for offloading data includes: determining a server for processing at least some data; receiving a list of split points about splittable data from the server; determining at least one split point as an offloading point based on the list; sending information about the offloading point and information about the requirement of offloading data corresponding to the offloading point to the server; receiving a response from the server about whether the offloading data can be processed, and determining whether to process the offloading data based on the response.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for offloading data in a wireless communication system. More specifically, the present disclosure relates to a method and apparatus for offloading data to meet a preset demand. Background Art

[0002] Considering the development of wireless communication from generation to generation, technologies that serve humans, such as voice calls, multimedia services, and data services, have been mainly developed. After the commercialization of 5G (fifth generation) communication systems, the number of connected devices is expected to grow exponentially. Connected devices will be increasingly connected to communication networks. Examples of connected objects can include vehicles, robots, dashboards, home appliances, displays, smart sensors connected to various infrastructures, construction machinery, and factory equipment. Mobile devices are expected to develop in various forms, such as augmented reality glasses, virtual reality headsets, and holographic devices. In order to provide various services by connecting tens of billions of devices and things in the 6G (6th generation) era, efforts have been made to develop improved 6G communication systems. For these reasons, 6G communication systems are called super 5G systems.

[0003] The 6G communication system, which is expected to be commercialized around 2030, will have a peak data rate of terabit (1000 gigabits) bps and a radio latency of less than 100 μs, and will therefore be 50 times faster than the 5G communication system but have 1 / 10 of its radio latency.

[0004] In order to achieve such high data rates and ultra-low latency, 6G communication systems are considered to be implemented in the terahertz band (e.g., 95GH to 3THz band). It is expected that due to the more severe path loss and atmospheric absorption in the terahertz band relative to the millimeter band introduced in 5G, technologies that can ensure the signal transmission distance (i.e., coverage) will become more critical. As the main technology for ensuring coverage, it is necessary to develop radio frequency (RF) elements, antennas, novel waveforms with better coverage than orthogonal frequency division multiplexing (OFDM) beamforming, a large number of multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, and multi-antenna transmission technologies such as massive antennas. In addition, new technologies for improving terahertz band signal coverage, such as metamaterial-based lenses and antennas, orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS), are discussed.

[0005] In addition, in order to improve spectrum efficiency and overall network performance, the following technologies have been developed for 6G communication systems: full-duplex technology for enabling uplink transmission and downlink transmission to use the same frequency resources simultaneously; network technology utilizing satellites, high altitude platform stations (HAPS), etc. in an integrated manner; improved network structure for supporting mobile base stations, etc., and realizing network operation optimization and automation, etc.; dynamic spectrum sharing technology via collision avoidance based on spectrum usage prediction; use of artificial intelligence (AI) in wireless communication for improving the overall network operation by utilizing AI from the design stage of developing 6G and internalizing end-to-end AI support functions; and next-generation distributed computing technology for overcoming the limitations of UE computing power through ultra-high performance communication and computing resources accessible on the network (such as mobile edge computing (MEC), cloud, etc.). In addition, by designing new protocols used in 6G communication systems, mechanisms for realizing hardware-based security environments and secure use of data are being continuously developed, and technologies for maintaining privacy, attempting to strengthen connections between devices, optimizing networks, promoting softwareization of network entities, and increasing the openness of wireless communications are being continuously developed.

[0006] It is expected that research and development of hyperconnectivity (including human-to-machine (P2M) and machine-to-machine (M2M)) in 6G communication systems will allow the next generation of hyperconnectivity experience. In particular, it is expected that services such as truly immersive extended reality (XR), high-fidelity mobile holograms, and digital replicas can be provided through 6G communication systems. In addition, services such as remote surgery with enhanced safety and reliability, industrial automation, and emergency response will be provided through 6G communication systems, making the technology applicable to various fields such as industry, medical care, automobiles, and home appliances.

[0007] As smart devices advance, the amount of data processed by the smart devices increases, and the type of data processed by the smart devices becomes diversified. In other words, as the types of smart devices become diversified and their performance is improved, the amount of data to be processed increases and a higher level of data processing is required.

[0008] Therefore, there is a need for an offloading technology that allows a portion of data to be processed by a smart device to be processed by a server instead of by the smart device. When sending data to a server for processing is more efficient than processing the data in the smart device, the offloading technology refers to a technology that allows the smart device to send some of its data to a server for processing and receive the processing results from the server.

[0009] In addition, when multiple smart devices offload data, each smart device may offload different types of data, and therefore, different requirements need to be met. In addition, when offloading data from multiple smart devices, an offloading technology that takes into account real-time changing channel conditions and server environments is required.

[0010] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with respect to the present disclosure. Summary of the invention

[0011] An aspect of the present disclosure is to solve at least the above problems and / or disadvantages and provide at least the advantages described below. Therefore, an aspect of the present disclosure is to provide a method and apparatus for offloading data in a wireless communication system.

[0012] Another aspect of the present disclosure is to provide a method and apparatus for offloading data to meet preset requirements.

[0013] Another aspect of the present disclosure is to provide a method and apparatus for offloading data according to varying channel conditions and server environments.

[0014] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the presented embodiments.

[0015] According to one aspect of the present disclosure, a method for offloading data performed by a user equipment (UE) is provided. The method includes: determining a server for processing at least some data; receiving a list of split points about splittable data from the server; determining at least one split point as an offloading point based on the list; sending information about the offloading point and information about the demand for offloading data corresponding to the offloading point to the server; receiving a response from the server whether the offloading data can be processed, and determining whether to process the offloading data based on the response.

[0016] The information about the requirement may include at least one of quality of service (QoS) information, delay information, processing time information, or capacity information that needs to be satisfied when the offload data is processed by the server.

[0017] The response as to whether the offload data can be processed may include an acknowledgment (ACK) when the offload data can be processed to meet the requirement, and a negative ACK (NACK) when the requirement is a mandatory requirement, and a change request information when the requirement is not a mandatory requirement.

[0018] The method may further include estimating a time required for the server to process the offload data, and the requirement includes a condition that a time calculated by the server as the time required to process the offload data is less than the estimated time.

[0019] Determining whether to process the offload data may include, when a response as to whether the offload data can be processed includes ACK, sending information required to process the offload data to the server, and receiving a result of processing the offload data from the server.

[0020] The determining whether to process the offload data may include requesting the server to terminate the processing of the offload data when the response as to whether the offload data can be processed includes NACK.

[0021] The change request information may include information related to a request for changing an unloading point and a request for changing requirements.

[0022] Determining whether to process the uninstall data may include: when a response regarding whether the uninstall data can be processed includes change request information, changing the uninstall point or requirement based on the change request information, sending to the server information necessary for processing the uninstall data that has changed based on a result of the change, and receiving a result of processing the uninstall data from the server.

[0023] The data may include training data for machine learning, and the offloaded data may be data trained by the server in the training data.

[0024] The determination of the server may include receiving server information from at least one server, and determining a server for processing at least some of the data from the at least one server based on the received server information.

[0025] Determining whether to process the uninstall data may include determining that the uninstall data is to be processed by a server, changing an uninstall point and requirements while the server is processing the uninstall data, sending information about the changed uninstall point and requirements to the server, and receiving from the server a result of processing the uninstall data based on the information about the changed uninstall point and requirements.

[0026] According to another aspect of the present disclosure, a method for processing offload data performed by a server is provided. The method includes: determining split points at which data received from a UE can be split, and sending a list of the determined split points to the UE; receiving information about the offload points determined based on the list and information about the requirements of the offload data corresponding to the offload points from the UE; sending a response to the UE as to whether the server can process the offload data; and receiving a result of determining whether to process the offload data based on the response from the UE.

[0027] According to another embodiment of the present disclosure, a UE for offloading data is provided. The UE includes a memory, a transceiver, and at least one processor, wherein the at least one processor is configured to determine a server for processing at least some of the data, receive a list of split points from the server about splitting points at which the data can be split, determine at least one of the split points as an offloading point based on the list, send information about the offloading point and information about a demand for offloading data corresponding to the offloading point to the server, receive a response from the server about whether the offloading data can be processed, and determine whether to process the offloading data based on the response.

[0028] According to another embodiment of the present disclosure, a server for processing offload data is provided. The server includes a memory, a transceiver, and at least one processor, wherein the at least one processor is configured to determine split points at which data received from a UE can be split, and to send a list of the determined split points to the UE, receive information about the offload points determined based on the list and information about the demand for offload data corresponding to the offload points from the UE, send a response to the UE regarding whether the server can process the offload data, and receive a result of determining whether to process the offload data based on the response from the UE.

[0029] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description in conjunction with the accompanying drawings, in which:

[0031] Figure 1 is a schematic diagram of a system for offloading data according to an embodiment of the present disclosure;

[0032] Figure 2 is a diagram showing a server for processing offload data according to an embodiment of the present disclosure;

[0033] Figure 3 is a flowchart of a method for offloading data executed by a system according to an embodiment of the present disclosure;

[0034] Figure 4 is a flowchart of a method for offloading data performed by a user equipment (UE) according to an embodiment of the present disclosure;

[0035] Figure 5 is a diagram illustrating distributed machine learning according to an embodiment of the present disclosure;

[0036] Figure 6a is a diagram illustrating a method of determining a server for performing data offloading, performed by a UE according to an embodiment of the present disclosure;

[0037] Figure 6b is a diagram illustrating a method of changing or adding a server for performing data offloading while performing an offloading process according to an embodiment of the present disclosure;

[0038] Figure 7 is a diagram showing a system in which a coordinator matches a server for offloading data according to an embodiment of the present disclosure;

[0039] Figure 8 is a diagram illustrating an operation of allocating server resources to a UE group according to an embodiment of the present disclosure;

[0040] Fig. 9 is a flowchart of a method for determining uninstallation data or requirements according to an embodiment of the present disclosure;

[0041] Fig.10 A table showing requirements according to an embodiment of the present disclosure;

[0042] Fig.11 A table showing processing time information according to an embodiment of the present disclosure;

[0043] Fig.12 is a flowchart illustrating the operation of a server according to an embodiment of the present disclosure;

[0044] Fig.13 is a flowchart illustrating the operation of a server according to an embodiment of the present disclosure;

[0045] Fig.14 is a flowchart illustrating the operation of a UE according to an entity that determines an offloading point according to an embodiment of the present disclosure;

[0046] Fig.15 is a diagram illustrating a method of determining uninstallation data performed by a server according to an embodiment of the present disclosure;

[0047] Fig.16 is a flowchart of a method for changing offloading data or requirements when performing an offloading procedure, performed by a UE according to an embodiment of the present disclosure;

[0048] Fig.17 is a diagram illustrating a distributed computing control protocol (DCCP) according to an embodiment of the present disclosure;

[0049] Fig.18 shows the internal structure of a UE according to an embodiment of the present disclosure; and

[0050] Fig.19The internal structure of a server according to an embodiment of the present disclosure is shown.

[0051] Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures. DETAILED DESCRIPTION

[0052] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. Although various specific details are included to assist in understanding, these are considered to be exemplary only. Therefore, it will be appreciated by those of ordinary skill in the art that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and structures may be omitted for clarity and brevity.

[0053] The terms and words used in the specification and claims are not limited to the bibliographic meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it should be clear to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and not for limiting the disclosure defined by the attached claims and their equivalents.

[0054] It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0055] Throughout the specification, it should be understood that when an element is referred to as being "connected" or "coupled" to another element, it may be directly connected to the other element or electrically coupled to the other element (with one or more intervening elements interposed therebetween). In addition, when a component "includes" or "comprises" an element, unless there is a specific description to the contrary, the component may further include other elements without excluding other elements.

[0056] Throughout the disclosure, the expression "at least one of a, b, or c" means only a, only b, only c, both a and b, both a and c, both b and c, all of a, b, and c, or variations thereof.

[0057] Examples of the terminal may include a User Equipment (UE), a Mobile Station (MS), a cellular phone, a smart phone, a computer, a multimedia system, and the like capable of performing a communication function.

[0058] In this disclosure, a controller may also be referred to as a processor.

[0059] Throughout the specification, a layer (or a layer arrangement) may also be referred to as an entity.

[0060] Expressions described in various parts of the present specification, such as "in some embodiments of the present disclosure" or "in an embodiment of the present disclosure" do not necessarily refer to the same embodiment of the present disclosure.

[0061] Some embodiments of the present disclosure can be described according to functional block components and various processing operations. Some or all of these functional blocks can be implemented by any number of hardware and / or software components that perform specific functions. For example, the functional blocks of the present disclosure can be implemented by one or more microprocessors or by circuit components for performing certain functions. For example, the functional blocks according to the present disclosure can be implemented in any programming or scripting language. The functional blocks can be implemented using various algorithms executed by one or more processors. In addition, the present disclosure can use the technology of related art for electronic configuration, signal processing and / or data processing. Terms such as "module" and "configuration" can be used in a broad sense and are not limited to mechanical or physical implementations.

[0062] In addition, the connecting lines or connectors shown in the various figures are intended to represent the functional relationship and / or physical or logical connection between the components in the figures. In actual equipment, the connection between the components can be represented by various functional connections, physical connections or logical connections that are replaced or added.

[0063] Furthermore, the expression "at least one of a or b" means "a or b" or "both a and b".

[0064] Hereinafter, the present disclosure will be described with reference to the accompanying drawings.

[0065] Figure 1 is a schematic diagram of a system for offloading data according to an embodiment of the present disclosure.

[0066] Reference Figure 1 , a system for offloading data may include a UE 100 and a server 110 .

[0067] According to an embodiment of the present disclosure, a data processing method and apparatus for performing, at the server 110 , a part of data processing performed at the UE 100 may be provided.

[0068] Reference Figure 1Examples of UE 100 may include, but are not limited to, smart phones, tablet PCs, PCs, smart TVs, mobile phones, personal digital assistants (PDAs), laptop computers, media players, micro servers, global positioning systems (GPS), e-book terminals, digital broadcast terminals, navigation devices, public telephone booths, MP3 players, digital cameras, home appliances, and other mobile or non-mobile computing devices. In addition, UE 100 may be a wearable device with a communication function and a data processing function, such as a watch, glasses, a hairband, or a ring. However, the embodiments of the present disclosure are not limited thereto, and UE 100 may include any device capable of sending data to or receiving data from server 110 via a network.

[0069] According to an embodiment of the present disclosure, the network may include a local area network (LAN), a wide area network (WAN), a value-added network (VAN), a mobile wireless communication network, a satellite communication network, and a combination thereof. In addition, the network may be configured to be able to Figure 1 The network entities shown are integrated data communication networks that perform smooth communication and include wired Internet, wireless Internet, and mobile wireless communication networks.

[0070] Examples of wireless communication technology may include, but are not limited to, wireless LAN (Wi-Fi), Bluetooth, Bluetooth Low Energy (BLE), ZigBee, Wi-Fi Direct (WFD), Ultra-Wideband (UWB), Infrared Data Association (IrDA), and Near Field Communication (NFC).

[0071] In addition, according to an embodiment of the present disclosure, the server 110 may communicate with the UE 100 via a network, process data received from the UE 100, and send the processed result to the UE 100. When at least some of the data for the UE 100 is processed by the server 110, at least some of the data processed by the server 110 is hereinafter referred to as offload data.

[0072] Figure 2 is a diagram illustrating a server for processing offload data according to an embodiment of the present disclosure.

[0073] Reference Figure 2, UE 100 may include an operating system (OS) and hardware (HW). The processor of UE 100 may process data. In addition, UE 100 may allow some of its data to be processed on server 110-1 and server 110-2, and receive processing results from server 110-1 and server 110-2. According to an embodiment of the present disclosure, the efficiency of data processing may be improved by processing at least some data on server 110-1 and server 110-2 instead of processing all data on UE 100 alone. In this case, server 110-1 and server 110-2 according to an embodiment of the present disclosure are servers configured to use physical servers more efficiently, and may be servers to which virtualization technology is applied.

[0074] According to an embodiment of the present disclosure, server 110-1 is a server that performs virtual machine (VM)-based computing. More specifically, server 110-1 may be a server that virtualizes hardware resources using a hypervisor. A hypervisor is software that enables multiple OSes to run, and may be, for example, a virtual machine monitor (VMM). In other words, server 110-1 is a server that can virtualize hardware and monitor virtualized hardware.

[0075] In addition, according to an embodiment of the present disclosure, server 110-2 is a server that performs container-based distributed computing. The container of server 110-2 can run applications in its own isolated space. Therefore, server 110-2 can run multiple applications on one physical server.

[0076] The server 110 - 1 that performs VM-based computing and the server 110 - 2 that performs container-based computing are merely examples of servers, and embodiments of the present disclosure are not limited thereto. The server may be any server that can receive and process data of the UE 100 .

[0077] Figure 3 is a flowchart of a method of offloading data executed by a system according to an embodiment of the present disclosure.

[0078] Reference Figure 3 In operation S310, the UE 100 may receive server information from the server 110. The server information received from the server 110 may include computing capability information of the server 110, capability information of the server 110, or information on a condition of a communication channel of the server 110.

[0079] In operation S320, the UE 100 may determine a server for processing the offloaded data based on the received server information. The UE 100 may determine whether the data is suitable for processing in the server 110 based on the server information. The UE 100 may also determine whether to offload the data to the server 110 based on the result of the determination.

[0080] In operation S330, the UE 100 may transmit data to the server 110. For example, the data may be an executable file of software constituting an application program. In other words, the UE 100 may copy the code of the executable file constituting the software and transmit the copied code to the server 110.

[0081] In operation S340, the server 110 can determine the splitting point of the splittable received data. More specifically, when receiving the code of the executable file constituting the software, the server 110 can analyze the received code and split the code to determine the executable point in the code. In this case, the splitting point can mean the point for splitting the code into code parts, because each code part has no dependency on other code parts, and the code parts will be executed even when the code is uninstalled. In other words, the splitting point can be used as a reference for splitting the code into code parts that can be executed independently in each part. On the other hand, when the UE 100 has sufficient capabilities, the UE 100 can directly analyze the data to determine the splitting point of the splittable data.

[0082] At operation S350, the UE 100 may receive a list about split points at which the data may be split. For example, when the split point corresponds to a specific portion of the code, the UE 100 may receive a list including information about the corresponding portion of the code.

[0083] In operation S360, the UE 100 may determine an unloading point of the data based on the received list. More specifically, the UE 100 may select a point for splitting the data from the split points included in the list as the unloading point. In this case, the data corresponding to the unloading point may be determined as the unloading data to be processed by the server 110.

[0084] The uninstallation point may include a start point and an end point of the uninstallation data. When the data is code constituting an executable file of the software, the start and end points of the code may be the uninstallation points. For example, when the uninstallation points are line 1 and line 500 of the code, line 1 to line 500 of the code may be the uninstallation data to be processed by the server 110.

[0085] In operation S370, the UE 100 may transmit information about the offloading point and information about the demand corresponding thereto. When the UE 100 transmits the information about the offloading point to the server 110, the server 110 may identify information about the offloading data. For example, the server 110 may identify the start point and the end point of the offloading data based on the offloading point.

[0086] In addition, the UE 100 may transmit information on the requirement of the offload data corresponding to the offload point. The information on the requirement of the offload data may include reference information for processing the offload data.

[0087] In operation S380, the UE 100 may receive a response regarding whether the offload data can be processed by the server 110. More specifically, the server 110 may determine whether it can process the offload data to meet the demand based on the received information regarding the offload point and the information regarding the demand. As a result of the determination, the server 110 may send a response including information regarding whether the server 110 can process the offload data to the UE 100.

[0088] In operation S390, the UE 100 may determine whether the offload data is to be processed by the server 110 based on the received response. More specifically, when the UE 100 determines that the offload data is to be processed by the server 110, the UE 100 may send information required for processing the offload data to the server 110, and receive a processing result of the offload data from the server 110. In this case, as described below, the information required for processing the offload data may be changed according to the response received from the server 110. On the other hand, when the UE 100 determines that the offload data is not to be processed by the server 110, the UE 100 may terminate the data offload process.

[0089] Figure 4 is a flowchart of a method for offloading data performed by a UE according to an embodiment of the present disclosure.

[0090] Reference Figure 4 In operation S410, the UE 100 may determine a server 110 for processing at least a portion of the data. More specifically, the UE 100 may receive server information from the server 110 and determine the server 110 for processing at least a portion of the data of the UE 100 based on the received server information.

[0091] In operation S420, UE 100 may receive a list of split points about splittable data from server 110. More specifically, UE 100 may copy the data and provide the copied data to server 110. The data may be a software executable file constituting an application. For example, the data may be a Java bytecode constituting an Android application. UE 100 may provide the copied code to server 110, and may receive a list of split points about splittable code from server 110. For example, when the code is splittable at line 1, line 500, line 700, and line 1000, UE 100 may receive a list of corresponding split points from server 110.

[0092] In the present disclosure, although for convenience, codes constituting an application are described as an example of data, the type of data is not limited thereto, and the data may be any type of data that can be processed by the UE 100 or the server 110. For ease of description, split points of splittable data are hereinafter represented as A, B, C, and D.

[0093] In operation S430, the UE 100 may determine at least one split point as an uninstallation point based on the list. When the UE 100 determines point A and point B as uninstallation points, data corresponding to point A to point B may be determined as uninstallation data. On the other hand, when the UE 100 selects only point A as the uninstallation point, the uninstallation data may be data before or after point A. In other words, the uninstallation point may be used as a reference for determining the uninstallation data.

[0094] In operation S440, the UE 100 may transmit information about the unloading point and information about the requirement of the unloading data corresponding to the unloading point to the server 110. For example, the UE 100 may transmit the point A and the point B determined as the unloading point to the server 110. In addition, the UE 100 may transmit information about the requirement of the unloading data corresponding to the point A to the point B to the server 110. The information about the requirement may include reference information for processing the unloading data corresponding to the point A to the point B. For example, the requirement may include information indicating that a delay of less than 3 ms or an image quality of 4K or higher should be satisfied. The reference information may be sent to the server 110. Fig.10 The information that may be included in the requirements is described later.

[0095] In operation S450, the UE 100 may receive a response from the server 110 regarding whether the server 110 is capable of processing the offload data. Determining whether the offload data is to be processed by the server 110 may mean determining whether the server 110 is capable of processing the offload data to meet its needs. The response received from the server 110 may include an indicator indicating whether the server 110 is capable of processing the offload data. Although for convenience, as an example of an indicator indicating whether the server 110 is capable of processing the offload data, an ACK (ACK) or a NACK (NACK) will be described hereinafter, the type of the indicator is not limited thereto, and the indicator may be any type of indicator capable of indicating whether the server 110 is capable of processing the offload data.

[0096] More specifically, when the server 110 is able to process the offload data to meet the received demand, the response may include ACK. On the other hand, when the server 110 is unable to process the offload data to meet the demand, the response may include NACK when the demand is a mandatory demand, and the response may include change request information when the demand is not a mandatory demand.

[0097] In operation S460, the UE 100 may determine whether the offload data is to be processed by the server 110 based on the received response. The received response may include at least one of ACK, NACK, or change request information.

[0098] More specifically, when the received response includes only ACK, the UE 100 may transmit information necessary for processing the offload data to the server 110, and receive a processing result of the offload data from the server 110. In this case, the information necessary for processing the offload data may be data context information stored in a memory of the UE 100. More specifically, a result value of the data processed by the UE 100 may be an input value for the offload data to be processed by the server 110, and thus, the UE 100 may transmit the data context information previously stored in the memory to the server 110. For example, when a code corresponding to point B to point C is determined as offload data, the UE 100 may transmit data necessary for executing the code corresponding to point B to point C to the server 110. In this case, the information necessary for processing the offload data may be a result value or data context obtained by executing the code corresponding to point A to point B.

[0099] On the other hand, when the received response includes NACK, UE 100 may determine to terminate the offloading process. UE 100 may request server 110 to terminate the offloading process. In addition, when the offloading process is terminated, UE 100 may process data independently or request to offload its data from a new server 110.

[0100] In addition, when the received response includes change request information and ACK or NACK, UE 100 can determine whether to change the unloading point or requirement based on the change request information. In other words, when the response regarding whether server 110 is capable of processing the unloading data includes change request information, UE 100 can change the unloading point or requirement based on the change request information, and send the server 110 the information necessary for processing the unloading data that is changed based on the changed unloading point or requirement. When the unloading point is changed, the information necessary for processing the changed unloading data may include data context information of UE 100 corresponding to the changed unloading point. For example, when the unloading data corresponding to point B to point C is changed to the unloading data corresponding to point C to point D, the information necessary for processing the changed unloading data can be obtained by changing the information for executing the code corresponding to point B to point C to the information necessary for executing the code corresponding to point C to point D.

[0101] In addition, when the requirements change, the information necessary for processing the changed uninstall data may include information about the changed requirements. Fig.10 The demand information is described later.

[0102] Figure 5 is a diagram illustrating distributed machine learning according to an embodiment of the present disclosure.

[0103] Reference Figure 5 , the UE 100 may perform distributed machine learning, which allows the server 110 to process at least some of the training data 500 for machine learning. More specifically, the server 110 may perform training on the training data 510 of the server 110, and the training data 510 of the server 110 includes at least some of the training data 500. In addition, the server 110 may send the training result of the training data 510 to the UE 100. In addition, the UE 100 may perform training on the training data 520 of the UE 100 based on the training result of the training data 510 received from the server 110. In addition, the UE 100 may perform inference on certain data based on the training data 510 and the training result of the training data 520. More specifically, the UE 100 may infer the output value of the input data based on the result of the distributed training on the training data 500. In addition, the inference on the data may also be performed by the UE 100 and the server 110 in a distributed manner.

[0104] although Figure 5An example is shown in which the UE 100 additionally performs training based on the training result from the server 110, but the training may be performed in another manner, that is, the UE 100 may first train at least some of the training data 500, and then the server 110 may additionally perform training based on the training result from the UE 100. In addition, the UE 100 may receive the training result from the server 110, and infer the output value of the input data based on the received distributed training result. In addition, the server 110 may perform distributed inference by inferring the output value of the input data based on the result of the distributed training.

[0105] Figure 6a is a diagram illustrating a method of determining a server for performing data offloading, performed by a UE according to an embodiment of the present disclosure.

[0106] Reference Figure 6a Before offloading data, UE 100 may determine a server for performing offloading. Figure 6a An example is shown in which the server information is first broadcast to the UE 100, and the UE 100 may first broadcast the UE information to the server. More specifically, when the UE information is first broadcast to the server, the server may broadcast the server information to the UE 100 based on the broadcasted UE information.

[0107] In operation S610, the UE 100 may receive first server information from the first server 110. Also, in operation S620, the UE 100 may receive second server information from the second server 120.

[0108] At operation S630, the UE 100 may determine to offload its data to the first server 110. More specifically, the UE 100 may determine to offload the data to the first server 110, which is one of the first server 110 and the second server 120, based on the received first server information and the second server information. For example, the UE 100 may determine to offload the data to the first server 110 by considering the channel conditions, supportable quality of service (QoS), capacity information, etc. of the first server 110 and the second server 120, respectively included in the first server information and the second server information.

[0109] At operation S640, the UE 100 may send a server access request and UE information to the first server 110. Then, at operation S650, the first server 110 may send an access grant to the UE 100 based on the received server access request and UE information. Thus, the UE 100 may be connected to the first server 110 via the network.

[0110] In operation S660, the UE 100 may transmit data to the first server 110. More specifically, the UE 100 may pre-copy a code and transmit the copied code to the first server 110. Figures 1 to 5 A description of the uninstallation process is provided. Therefore, it will be omitted here Figures 1 to 5 .

[0111] Figure 6b is a diagram illustrating a method of changing or adding a server for performing data offloading while performing an offloading process according to an embodiment of the present disclosure;

[0112] When describing Figure 6b The above mentioned methods will be omitted. Figure 6a Description.

[0113] Reference Figure 6b , at operation S630, the UE 100 may determine to offload the data to the first server 110. In this case, when the data is related to a delay-sensitive service, the UE 100 may determine to offload the data to the first server 110, and pre-send the data to the second server 120 as a candidate server as well as the first server 110. On the other hand, when the data is related to a delay-insensitive service, the UE 100 may send the data only to the first server 110, and may not pre-send the data to the second server 120 as a candidate server.

[0114] In operation S631 , the UE 100 may perform an offloading procedure to the first server 110 .

[0115] In operation S632, the UE 100 may determine to offload data to the second server 120 while performing the offloading process. In this case, the second server 120 may be added so that the UE offloads data to the second server 120 as well as the first server 110. In addition, the UE 100 may change the server to which the data is to be offloaded from the first server 110 to the second server 120. In other words, the UE 100 may add or change the second server 120 based on the result of the offloading process performed by the first server 110.

[0116] In operation S633, the UE 100 may perform an offloading process to the second server 120. In this case, when the data is transmitted to the second server 120 in advance because the data is related to a delay-sensitive service, the second server 120 may perform the offloading process based on the previously transmitted data, which facilitates delay-sensitive processing. On the other hand, when the data is not transmitted to the second server 120 in advance because the data is related to a delay-insensitive service, the second server 120 may receive the offloading data from the UE 100 and perform processing only on the received offloading data, which allows efficient use of the capacity of the second server 120.

[0117] Figure 7 is a diagram illustrating a system according to an embodiment of the present disclosure, in which a coordinator matches servers for performing data offloading.

[0118] According to an embodiment of the present disclosure, a separate coordinator 700 may determine a server to which data of the UE 100 will be offloaded. The coordinator 700 is a device for determining a server to which data of the UE 100 will be offloaded, and may be configured as a server or a network entity.

[0119] Reference Figure 7 , the coordinator 700 may receive UE information from the UE 100. In addition, the coordinator 700 may receive first server information and second server information from the first server 110 and the second server 120, respectively. The coordinator 700 may determine which of the first server and the second server is to match the UE 100 based on the first server information and the second server information.

[0120] The coordinator 700 may send the matching result to the UE 100, the first server 110, and the second server 120. For example, when the coordinator 700 determines that the UE 100 matches the first server 110, the UE 100 may perform an offloading process for offloading to the first server 110 according to the matching result.

[0121] In addition, according to an embodiment of the present disclosure, the coordinator 700 may not only determine which server is to be matched with the UE 100, but also determine which portion of the offload data 750 is to be processed at each of the first server 110 and the second server 120. Figure 7, the coordinator 700 may analyze the split points at which the offload data 750 may be split into point A to point C. The coordinator 700 may determine the offload data 751 to be processed at the first server 110 as data corresponding to point A to point B of the offload data 750. In addition, the coordinator 700 may determine the offload data 752 to be processed at the second server 120 as data corresponding to point B to point C of the offload data 750. In other words, the UE 100 allows the first server 110 to process the offload data 751 of the first server 110 as a part of the offload data 750, while allowing the second server 120 to process the offload data 752 of the second server 120 as the remaining part of the offload data 750.

[0122] Figure 8 is a diagram illustrating an operation of allocating server resources to a UE group according to an embodiment of the present disclosure.

[0123] Reference Figure 8 In 810, at least some available resources of the server 110 may be allocated to a specific UE group. More specifically, when a specific UE group subscribes to a specific service, the server 110 may allocate some available resources of the server 110 to the specific UE group so as to support the service of the UE group. In this case, when the specific UE group pays a fee for the subscription service, the server 110 may allocate different resources to the specific UE group according to the paid fee or the characteristics of the service.

[0124] In addition, reference Figure 8 820, when the resources previously reserved for a specific UE group are insufficient, additional resources of the server 110 may be allocated to the UE group. More specifically, when the server 110 has available resources other than the previously reserved resources for the specific UE group, the server 110 may allocate additional resources to the specific UE group, and the UE group may use the additional resources.

[0125] In addition, reference Figure 8 830 , when the resources previously reserved for the specific UE group are sufficient, the server 110 may use fewer resources than the previously reserved resources for the specific UE group.

[0126] Fig. 9 The present invention is a flowchart of a method for determining uninstallation data or a demand corresponding thereto according to an embodiment of the present disclosure.

[0127] More specifically, Fig. 9 is a flowchart showing a response of the server when the information on the offloading point and the information on the requirement received from the UE 100 are recommended requirements.

[0128] Reference Fig. 9, in operation S910, the server 110 may receive information about an uninstallation point and information about a demand.

[0129] Then, in operation S920, the server 110 may determine whether the offloading point and the requirement are acceptable based on the received information. When the server 110 determines in operation S920 that the offloading point and the requirement are acceptable, the server 110 may send a response including an ACK in operation S930.

[0130] When the offload points and requirements are mandatory requirements, the server 110 is required to send a response including a NACK as long as at least some of the offload points and requirements are unacceptable. In other words, when the offload points and requirements are mandatory requirements, the server 110 cannot change any of the offload points and requirements, and therefore does not need to determine whether all of the offload points and requirements are unacceptable.

[0131] On the other hand, when the server 110 determines in operation S920 that the offloading point and the requirement are not acceptable, the server 110 may determine in operation S940 whether all the offloading points and the requirements are not acceptable. In other words, in this case, the offloading point and the requirement are recommended requirements.

[0132] When all offloading points and requirements are unacceptable, the server 110 may send a response including NACK at operation S950. On the other hand, according to an embodiment of the present disclosure, even when all offloading points and requirements are unacceptable, the server 110 may send a response including information indicating a suggested new offloading point or new requirement.

[0133] As long as some of the offloading points and requirements are acceptable, the server 110 may send a response including NACK and change request information in operation S960. More specifically, the server 110 may request to change the unacceptable parts of the offloading points and requirements.

[0134] Fig.10 A table illustrating requirements according to an embodiment of the present disclosure is shown.

[0135] Reference Fig.10 , the type of requirement 1010 may include a case where the requirement to offload data is a mandatory requirement ( 1011 ) and a case where the requirement to offload data is a recommended requirement ( 1015 ).

[0136] In the case where the demand for offloading data is a mandatory demand that must be satisfied (1011), when the server 110 cannot accept the mandatory demand, the server 110 may return NACK, or when there is no response within a predetermined time period, the response is considered to be NACK (1012). In other words, although the server 110 should return NACK when the server 110 cannot accept at least some mandatory demands, the response may be considered to be NACK even if there is no response. In addition, when the server 110 cannot accept the mandatory demand, the server 110 may delete or discard the received data and may not perform the offloading process.

[0137] In addition, when the server 110 cannot accept the mandatory requirement, it may further return NACK and details of the change request (1013). More specifically, when the server 110 cannot meet the mandatory requirement, it may propose details of the change request for changing the mandatory requirement while returning NACK. For example, the server 110 may return the minimum and / or maximum requirement information that the server 110 itself can provide together with the NACK. In addition, the server 110 may include a QoS requirement corresponding to a request to reduce the amount of offloaded data or to downgrade the service in the details of the change request.

[0138] On the other hand, when the server 110 can accept the mandatory demand, the server 110 may return ACK, or when no response is received within a predetermined time period, the response is considered to be ACK (1014). In addition, information on whether the response is considered to be ACK or NACK when no response is received within a preset time period may be included in the details of the mandatory demand, or may be preset between the UE 100 and the server 110. For example, in the case where the details of the mandatory demand include information indicating that "when no response is received from the server 110 within 5 ms, the response is considered to be ACK", when no response is actually received from the server 110 within 5 ms, the UE 100 may regard the response as ACK, and may continue to perform the offloading process.

[0139] In the case where the requirement of the offload data is the recommended requirement (1015), the server 110 cannot return NACK even when the server 110 cannot accept the recommended requirement (1016). In other words, even when the server 110 cannot accept the recommended requirement, the server 110 can process the offload data based on the changed requirement. Therefore, when the recommended requirement is unacceptable, the server 110 can send information about the difference between the recommended requirement and the changed requirement together with NACK or ACK.

[0140] On the other hand, when the server 110 can accept the recommended requirements, it can return ACK, or when there is no response, the response is considered to be ACK (1017). As described above, when no response is received from the server 110, whether the response is ACK or NACK may be included in the details of the recommended requirements, or may be preset between the UE 100 and the server 110.

[0141] According to an embodiment of the present disclosure, the details 1020 of the requirements may include QoS information, capacity information, and processing time information. More specifically, the QoS information may mean information about the minimum QoS requirements that must be met when processing the offloaded data. For example, the QoS information may include image quality information, data transmission rate information, delay information, etc., but is not limited thereto, and may include any information related to QoS.

[0142] In addition, the capacity information may be information about the memory capacity required for processing the offload data. For example, the server 110 may determine whether the memory capacity available for processing the offload data meets the requirements of the UE 100.

[0143] Reference now Fig.11 The processing time information included in the details 1020 of the requirement is more fully described.

[0144] Fig.11 A table showing processing time information according to an embodiment of the present disclosure.

[0145] refer to Fig.11 The details 1020 of the demand received from the UE 100 may include processing time information 1021. The processing time information 1021 is information related to the UE estimated time and the server estimated time. The server 110 may determine a response to the demand for offloading data based on the processing time information 1021.

[0146] More specifically, UE 100 can estimate the time taken by server 110 to process the offload data. The value obtained when UE 100 estimates the time taken by server 110 to process the offload data is referred to as UE estimated time hereinafter. In addition, server 110 can estimate the time taken by server 110 itself to process the offload data, and the estimated time is referred to as server estimated time hereinafter. In this case, the server estimated time can be more accurate than the UE estimated time. More specifically, because server 110 can predict the amount of calculation in real time based on information received from UE 100, the server estimated time can be more accurate than the UE estimated time. In other words, the server estimated time is more accurate than the UE estimated time because the UE estimated time does not take into account real-time channel or server conditions, while the server estimated time can reflect real-time information.

[0147] When the sum of the UE estimated time and the network delay is shorter than the time required for the UE 100 to directly process the offload data, the UE 100 may determine that it is more efficient to process the offload data at the server 110 than to directly process the offload data. In this case, the network delay may refer to the sum of the time required for the server 110 to send the offload data and the time required to receive the processing result of the offload data from the server 110. In other words, when the sum of the UE estimated time and the network delay is less than a preset threshold, the UE 100 may request the server 110 to process the offload data. More specifically, when the sum of the UE estimated time, the time required to send the offload data, and the time required to receive the processing result is less than a preset threshold, the UE 100 may request the server 110 to process the offload data.

[0148] In addition, because the server estimated time is more accurate than the UE estimated time, when the server estimated time is longer than the UE estimated time, it can be understood that the actual time taken by the server 110 to process the offload data is longer than the time expected by the UE 100. In other words, when the server estimated time is longer than the UE estimated time, the server 110 can determine that the time taken to process the offload data is longer than the time expected by the UE 100, and send a response including a NACK. In addition, the server 110 can send change request information related to the demand change together with the NACK.

[0149] On the other hand, when the UE estimated time is longer than the server estimated time, the server 110 can determine that the time spent processing the offload data is shorter than the time expected by the UE 100, and send a response including ACK. In addition, even in this case, the server 110 can send ACK and a change request information for suggesting a change requirement.

[0150] When the server 110 notifies the UE 100 of the capability information of the server 110, the UE estimated time may be obtained by using the following formula (1):

[0151]

[0152] Referring to formula (1), UE estimates time t s It can be obtained by dividing the calculation amount w of UE 100 by the unit calculation amount w of server 110. unit The result and the unit time t required for the unit calculation amount of the computing server 110 unit The product obtained by multiplying.

[0153] In addition, the UE 100 can directly estimate the UE estimated time by using the following formula (2):

[0154]

[0155] In formula (2), the parameter values ​​are as follows:

[0156] t s is the UE estimated time, f l is the UE computing capability, w is the computing amount of UE 100, t l is the time required for UE 100 to actually measure the computation amount w, μ is the ratio of the allocatable resources of server 110, and f s is the computing capacity of the server 110. The information about these parameter values ​​may be received via server information when the server 110 is determined, or may be received from the server 110 periodically.

[0157] In addition, the service estimated time can be obtained by using the following formula (3):

[0158]

[0159] The server estimated time may be obtained by considering the unit calculation amount of the server 110 in real time.

[0160] Fig.12 is a flowchart illustrating the operation of a server according to an embodiment of the present disclosure.

[0161] Reference Fig.12 In operation S1210, the server 110 may receive information about the offloading point and information about the requirement. In addition, in operation S1220, the server 110 may determine whether the offloading point and the requirement are acceptable based on the received information.

[0162] When the server 110 determines that the offloading point and the requirement are acceptable, in operation S1230, the server 110 may perform offloading and send a processing result to the UE 100. More specifically, when the server 110 determines that the offloading point and the requirement are acceptable, the server 110 may receive information required to process the offloading data from the UE 100, and process the offloading data based on the received information. In addition, the server 110 may send a processing result to the UE 100.

[0163] On the other hand, when the server 110 determines that the offloading point and the requirements are not acceptable, in operation S1240, the server 110 may send a response including a NACK. In this case, the offloading process may be terminated. For example, the server 110 may receive a request from the UE 100 to terminate the processing of the offloading data. On the other hand, even when the server 110 sends a response including a NACK to the UE 100, the UE 100 may not terminate the offloading process, but may request the server 110 to perform the offloading again by downgrading the requirements, or request the server 110 to resume the offloading process after a predetermined period of time has passed.

[0164] In addition, when the server 110 determines that the offloading point and requirements are unacceptable, the server 110 may include its minimum guarantee together with the NACK in the transmitted response. The minimum guarantee may mean the minimum guarantee supported by the server 110. For example, the minimum guarantee may include information indicating "maximum delay less than 5ms" and "processing offload data with minimum 4K image quality". According to one embodiment of the present disclosure, the server 110 may broadcast the minimum guarantee at each preset period or broadcast the minimum guarantee non-periodically. In this case, the UE 100 may determine whether to change the offloading point and requirements based on the minimum guarantee broadcast by the server 110.

[0165] Fig.13 is a flowchart illustrating the operation of a server according to an embodiment of the present disclosure.

[0166] Reference Fig.13 The server 110 can determine whether to process the uninstalled data according to whether the data retention request is received. When describing operations S1310 and S1320, the above-mentioned description of Figures 1 to 5 , Figure 6a and Figure 6b as well as Figures 7 to 12 Description.

[0167] In operation S1310, the server 110 may receive information about the offloading point and information about the requirements. In addition, in operation S1320, the server 110 may determine whether the offloading point and the requirements are acceptable based on the received information.

[0168] When the server 110 determines that the offloading point and the requirements are acceptable, the server 110 may or may not send a response including an ACK at operation S1330. When no response is received within a predetermined time period, the UE 100 may determine that an ACK has been received. In this case, the server 110 may perform an offloading process based on the offloading data.

[0169] In operation S1340, the server 110 may determine whether there is a received data retention request indicator. The data retention request indicator refers to an indicator requesting the server 110 to retain previously received data instead of deleting or discarding it. The data retention request indicator may be included in the information on the transmission requirement.

[0170] When the server 110 determines that there is a received data retention request indicator, in operation S1341, the server 110 may send a response and information related to the pause. Because the server 110 cannot accept the uninstall point or demand, it may send a response including a NACK. In addition, because there is a received data retention request indicator, the server 110 may stop or pause the uninstall process for a predetermined period of time without terminating the uninstall process. In addition, the server 110 may send information related to the pause of the uninstall process. In addition, the server 110 may send a response and difference information related to the demand. After sending the response and the information related to the pause, the server 110 may not perform the uninstall process but retain the data to restart the uninstall process later.

[0171] When the server 110 determines that the data retention request indicator is not received, in operation S1342, the server 110 may send a response and change request information. More specifically, the server 110 may send a response including an ACK or a NACK, depending on whether the requirement is a mandatory or recommended requirement. In addition, the server 110 may also send change request information about the requirement and an ACK or a NACK.

[0172] Fig.14 is a flowchart illustrating an operation of the UE 100 according to an entity that determines an offloading point according to an embodiment of the present disclosure.

[0173] According to the above uninstallation process, UE 100 can determine an uninstallation point, receive a response to the determined uninstallation point from server 110, and determine a final uninstallation point based on the received response. In other words, an example has been described in which UE 100 is an entity that determines an uninstallation point.

[0174] When the server 110 is not an entity that determines the offloading point in operation S1430, that is, when the UE 100 is an entity that determines the offloading point, the UE 100 may determine the offloading point in operation S1440.

[0175] Reference Fig.14 , the server 110 may determine the uninstallation point. More specifically, when the server 110 is the entity that determines the uninstallation point in operation S1430, the server 110 may determine the uninstallation point. According to an embodiment of the present disclosure, when the server 110 is the entity that determines the uninstallation point, the uninstallation point included in the response received from the server 110 in operation S1420 may be determined as the final uninstallation point.

[0176] In operation S1450, the UE 100 may determine whether to process the offload data. More specifically, the UE 100 may determine whether to process the offload data based on the offload point determined by the server 110. When the UE 100 determines the offload point, the UE 100 may determine whether to process the offload data based on the determined offload point.

[0177] In operation S1460, the UE 100 may determine to terminate the processing of the offload data corresponding to the offload point determined by the server 110. In this case, the UE 100 may transmit a request to the server 110 to terminate the processing of the offload data.

[0178] On the other hand, when the UE 100 determines to process the offload data, at operation S1470, the UE 100 may transmit information required to process the offload data to the server 110. In addition, at operation S1480, the UE 100 may receive a processing result of the offload data from the server 110.

[0179] Fig.15 is a diagram illustrating a method of determining uninstall data performed by the server 110 according to an embodiment of the present disclosure.

[0180] Reference Fig.15 , the UE 100 may determine that at least a portion of the data 1500 is to be processed by the server 110. In other words, the UE 100 may determine at least some of the data 1500 as offload data 1510.

[0181] Reference Fig.15 , the server 110 may analyze the data 1500 and determine split points such as points A, B, C, and D at which the data 1500 is splittable. The UE 100 may determine the offloading points to be points A and C based on the list including points A, B, C, and D received from the server 110. Therefore, the offloading data 1510 may be determined as data corresponding to points A to C of the data 1500.

[0182] According to an embodiment of the present disclosure, the server 110 may receive information about the offloading points A and C, and information about the need to offload data 1510 from the UE 100. The server 110 may determine whether it can process the offloading data 1510 based on the received information.

[0183] When the server 110 cannot process the offload data 1510 determined by the UE 100 due to insufficient capacity of the server 110, the server 110 may include a change request in the response to change the offload data 1510. Fig.15An example is shown in which the server 110 cannot process the offload data 1510 due to its lack of capacity, but when the server 110 cannot meet the offload point or demand for any other reason, the server 110 may also include a change request in the response to change the offload data 1510. For example, the server 110 may include a request to change the offload point to point A and point B in the response, and send the response to the UE 100. When the server 110 is responsible for determining the offload data, the UE 100 may change the offload data 1510 to data 1520 corresponding to point A to point B according to the change request from the server 110. Therefore, the UE 100 may process the data 1521 corresponding to point B to point C in addition to the offload data 1520 in the data 1500.

[0184] On the other hand, due to its remaining capacity for transmission to UE 100, server 110 may include in the response a request for extending the amount of offload data 1510. When server 110 is an entity that determines the offload data, offload data 1522 to be processed by server 110 may be determined according to a change request for changing offload data 1510 included in the response. In other words, according to the request from server 110 for extending the amount of offload data 1510, offload data 1522 may be determined as data corresponding to point A to point D.

[0185] Thus, when server 110 is responsible for determining offload data, UE 100 needs to accept a change request from server 110. On the other hand, when UE 100 is an entity that determines offload data, UE 100 may change requirements or offload data based on a change request from server 110.

[0186] Fig.16 is a flowchart of a method for changing offloading data or requirements when performing an offloading procedure, which is performed by the UE 100 according to an embodiment of the present disclosure.

[0187] When describing Fig.16 The above mentioned methods will be omitted. Figures 1 to 5 , Figure 6a and Figure 6b ,as well as Figures 7 to 15 For example, according to the above reference Figures 1 to 5 , Figure 6a and Figure 6b ,as well as Figures 7 to 15 Describes the actions to determine the unload data.

[0188] Reference Fig.16 In operation S1610, the UE 100 may determine to process the offload data. In other words, the UE 100 may transmit information required to process the offload data to the server 110 based on the response from the server 110.

[0189] In operation S1620, the UE 100 may periodically receive the server information. In addition, the UE 100 may aperiodically receive the server information. In other words, the UE 100 may obtain information about a real-time change state or channel condition of the server 110 based on the received server information.

[0190] At operation S1630, the UE 100 may determine whether to change the offloading point or requirement based on the received server information. When the UE 100 determines not to change the offloading point or requirement, it may maintain the existing offloading process at operation S1640.

[0191] On the other hand, when the UE 100 determines to change the offloading point or requirement, it may send additional information to the server 110 at operation S1650. The additional information may include information related to the change of the offloading point or requirement. More specifically, the UE 100 may send a request to reduce or expand the amount of offloading data, or information for downgrading or upgrading requirements to the server 110.

[0192] In operation S1660, UE 100 may receive the result of the processing of the offload data performed based on the additional information. More specifically, server 110 may send a response to UE 100 regarding whether to accept the changed demand based on the additional information. In the case where server 110 sends an indicator indicating the acceptance of the changed demand to UE 100 (when the offload point has not changed), server 110 may perform the processing of the offload data based on the previously received information necessary for processing the offload data. On the other hand, when the amount of offload data is extended, server 110 may additionally receive only the information necessary for processing the extended amount of offload data. In other words, even when the amount of offload data is reduced or the demand is downgraded, server 110 may process the offload data based on the previously received information.

[0193] Fig.17 is a diagram showing a distributed computing control protocol (DCCP) 1700 according to an embodiment of the present disclosure.

[0194] Reference Fig.17 , DCCP 1700 refers to a protocol for supporting a dynamic offloading process between the UE 100 and the server 110 by exchanging control information using a Stream Control Transmission Protocol (SCTP) port.

[0195] DCCP 1700 may be a distributed computing protocol similar to S1 Application Protocol (S1-AP). Fig.17, DCCP 1700 may be located at a distributed computing control layer. In addition, to support the offloading process, DCCP 1700 may control the establishment, modification, or release of a connection between UE 100 and server 110. In addition, DCCP 1700 may control operations for determining offloading data, performing offloading, and indicating capability information for offloading between UE 100 and server 110. In other words, DCCP 1700 may control information necessary for offloading data to be included in a message.

[0196] Fig.18 FIG. 1 shows an internal structure of UE 100 according to an embodiment of the present disclosure.

[0197] refer to Fig.18 According to an embodiment of the present disclosure, UE 100 may include a processor 1801, a transceiver 1802, and a memory 1803. The processor 1801, the transceiver 1802, and the memory 1803 of UE 100 may be operated according to the above method for UE 100 to perform communication. The components of UE 100 are not limited to the above examples. For example, UE 100 may include more or less components than the above. In addition, the processor 1801, the transceiver 1802, and the memory 1803 may be implemented as a single chip.

[0198] The transceiver 1802 collectively represents the receiver and transmitter of the UE 100, and can send or receive signals to or from the server 110 via the network. The signals sent or received via the network may include control information and data. To this end, the transceiver 1802 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of the signal to be transmitted, and an RF receiver for low-noise amplification of the received signal and down-converting its frequency. However, this is merely an example of the transceiver 1802, and the components of the transceiver 1802 are not limited to the RF receiver and the RF transmitter.

[0199] In addition, the transceiver 1802 may receive a signal via a radio channel and output the signal to the processor 1801 , and transmit a signal output from the processor 1801 via a radio channel.

[0200] The memory 1803 may store data and programs required for the operation of the UE 100. In addition, the memory 1803 may store control information or data in a signal transmitted or received by the UE 100. The memory 1803 may include a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a compact disk (CD)-ROM, and a digital video disk (DVD), or a combination thereof.

[0201] The processor 1801 may include at least one processor. For example, the processor 1801 may include a communication processor (CP) for performing communication control and an application processor (AP) for controlling an upper layer (e.g., an application). The processor 1801 may control a series of processes so that the UE 100 may operate according to the above-mentioned embodiments of the present disclosure.

[0202] More specifically, the processor 1801 may determine the server 110 for processing at least a portion of the data. The processor 1801 may receive a list of split points of splittable data from the server 110 via the transceiver 1802. The processor 1801 may determine at least one of the split points as an unloading point based on the received list. In addition, the processor 1801 may send information about the unloading point and information about the demand for unloading data corresponding to the unloading point to the server 110 via the transceiver 1802. In addition, the processor 1801 may receive a response from the server 110 regarding whether the unloading data can be processed via the transceiver 1802, and determine whether to process the unloading data based on the received response.

[0203] Fig.19 The internal structure of the server 110 according to an embodiment of the present disclosure is shown.

[0204] Reference Fig.19 According to an embodiment of the present disclosure, the server 110 may include a processor 1901, a transceiver 1902, and a memory 1903. The processor 1901, the transceiver 1902, and the memory 1903 of the server 110 may be operated according to the above-mentioned method for performing communication by the server 110. The components of the server 110 are not limited to the above-mentioned examples. For example, the server 110 may include more or less components than the above-mentioned. In addition, the processor 1901, the transceiver 1902, and the memory 1903 may be implemented as a single chip.

[0205] The transceiver 1902 collectively represents the receiver and transmitter of the server 110, and can send or receive signals to or from the UE 100 via the network. The signals sent or received via the network may include control information and data. To this end, the transceiver 1902 may include an RF transmitter for up-converting and amplifying the frequency of the signal to be transmitted, and an RF receiver for low-noise amplification of the received signal and down-converting its frequency. However, this is merely an example of the transceiver 1902, and the components of the transceiver 1902 are not limited to the RF receiver and the RF transmitter.

[0206] In addition, the transceiver 1902 may receive a signal via a radio channel and output the signal to the processor 1901 , and transmit a signal output from the processor 1901 via a radio channel.

[0207] The memory 1903 may store data and programs required for the operation of the server 110. In addition, the memory 1903 may store control information or data in a signal obtained by the server 110. The memory 1903 may include a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination thereof.

[0208] The memory 1903 may store data and information received from the UE 100. In addition, when receiving a data retention request indicator from the UE 100, the server 110 may store previously transmitted data in order to resume the offloading process according to the control of the processor 1901.

[0209] The processor 1901 may include at least one processor. For example, the processor 1901 may include a CP for performing communication control and an AP for controlling an upper layer (eg, an application). The processor 1901 may control a series of processes so that the server 110 may operate according to the above-described embodiments of the present disclosure.

[0210] More specifically, the processor 1901 may determine split points of the splittable data received from the UE 100, and transmit a list of the determined split points to the UE 100 via the transceiver 1902. The processor 1901 may control the transceiver 1902 to receive information about the determined offloading points and information about the demand for offloading data corresponding to the offloading points, transmit a response about whether the server 110 can process the offloading data, and receive a result of determining whether the offloading data will be processed based on the response.

[0211] Some embodiments of the present disclosure may be implemented by a computer-readable recording medium having computer-executable instructions such as program modules executed by a computer recorded thereon. A computer-readable recording medium may be any available medium that a computer can access, and includes volatile and non-volatile media and removable and non-removable media. In addition, a computer-readable recording medium may include a computer storage medium. Computer storage media include volatile and non-volatile and removable and non-removable media, which are implemented by any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data.

[0212] Although certain embodiments of the present disclosure have been described with reference to the accompanying drawings, it will be understood by those skilled in the art that various changes and modifications in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the following claims.

[0213] The method of unloading data in a wireless communication system according to some embodiments of the present disclosure may be implemented in the form of program instructions, which may be executed by various types of computers and may be recorded on a computer-readable recording medium. The computer-readable recording medium may include separate program instructions, data files, data structures, etc. or a combination thereof. The program instructions recorded on the computer-readable recording medium may be designed and configured specifically for the present disclosure, or may be known to and may be used by technicians in the field of computer software. The computer-readable recording medium may be included in a computer program product.

[0214] Examples of computer-readable recording media 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 optical floppy disks, and hardware devices specially configured to store and execute program instructions such as ROM, RAM, flash memory, etc. Examples of program instructions include not only machine codes (such as those created by a compiler), but also high-level language codes that can be executed by a computer using an interpreter, etc.

[0215] The computer-readable storage medium may be provided in the form of a non-transitory storage medium. In this regard, the term "non-transitory" simply means that the storage medium does not refer to a temporary electrical signal and is tangible, and the term does not distinguish between data stored semi-permanently and data stored temporarily in the storage medium. For example, a "non-transitory storage medium" may include a buffer that temporarily stores data.

[0216] According to an embodiment of the present disclosure, the method according to various embodiments of the present disclosure may be included in a computer program product when provided. The computer program product may be traded between a seller and a buyer as a product. For example, the computer program product may be distributed in the form of a device-readable storage medium (e.g., CD-ROM), or distributed online (e.g., downloaded or uploaded) via an application store (e.g., Google, Play Store), or distributed directly between two user devices (e.g., smartphones). For online distribution, at least a portion of a computer program product (e.g., a downloadable application) may be stored or temporarily created on a device-readable storage medium, such as a manufacturer's server, a server of an application storage device, or a memory of a relay server.

[0217] Furthermore, in this specification, the term "unit" may be a hardware component (eg, a processor or a circuit) and / or a software component executed by a hardware component (eg, a processor).

[0218] The method and apparatus for offloading data in a wireless communication system according to the embodiments of the present disclosure can provide services that meet the needs.

[0219] In addition, the method and apparatus for offloading data in a wireless communication system according to an embodiment of the present disclosure can improve data processing efficiency by changing the offloaded data according to a server status or a channel condition.

[0220] The above description of the present disclosure is provided for illustration, and those skilled in the art will appreciate that various changes in form and detail may be readily made therein without departing from the basic features and spirit and scope of the present disclosure as defined by the appended claims. Therefore, the above-described embodiments of the present disclosure and all aspects thereof are merely illustrative and not restrictive. For example, each component defined as an integrated component may be implemented in a distributed manner. Similarly, components defined as separate components may be implemented in an integrated manner.

[0221] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.

Claims

1. A method for offloading data performed by a user equipment UE, the method include: determining a server for processing at least some of said data, said data comprising code; sending the data to the server; receiving, from the server, a list comprising at least one split point at which the data is splittable; determining, based on the list, an offloading point for the data from the at least one split point; sending information about the uninstallation point and information about a demand for uninstallation data corresponding to the uninstallation point to the server; receiving a response from the server as to whether the offload data can be processed; as well as determining whether to process the offload data based on the response, wherein the at least one split point comprises a point for splitting the code into code portions, the code portions being executable even when uninstalled, each code portion being independent of other portions of the code, Wherein, when the uninstall data cannot be processed to meet the requirement, the response on whether the uninstall data can be processed includes: When the request is a mandatory request, including a negative acknowledgement (NACK), and When the requirement is not mandatory, include change request information, The change request information includes a request to change the location of the unloading point from one point to another point.

2. The method according to claim 1, in, The information about the requirement includes at least one of quality of service (QoS) information, delay information, processing time information, or capacity information that needs to be satisfied when the offload data is processed by the server.

3. The method according to claim 1, in, The response regarding whether the uninstall data can be processed includes: When the offload data can be processed to meet the demand, an ACK is included.

4. The method according to claim 3, further comprising: include: The time required for the server to process the uninstalled data is estimated, wherein the requirement includes a condition that the time calculated by the server as the time required to process the uninstalled data is less than the estimated time.

5. The method according to claim 3, in, Determining whether to process the uninstall data includes: When the response regarding whether the offload data can be processed includes the ACK, sending information required for processing the offload data to the server; and A result of processing the offload data is received from the server.

6. The method according to claim 1, in, The determining whether to process the offload data includes requesting the server to terminate processing of the offload data when the response as to whether the offload data can be processed includes the NACK.

7. The method according to claim 1, in, The change request information includes information related to a request for changing the requirement.

8. The method according to claim 1, in, Determining whether to process the uninstall data includes: When the response regarding whether the offload data can be processed includes the change request information, changing the offload point or the requirement based on the change request information; sending information necessary for processing the changed uninstall data to the server based on the result of the change; and A result of processing the changed uninstall data is received from the server.

9. The method according to claim 1, in, The data includes training data for machine learning, and The uninstallation data is data in the training data that is trained by the server.

10. The method according to claim 1, in, Servers identified for processing at least some of the data include: receiving server information from at least one server; and Based on the received server information, a server for processing at least some of the data is determined from the at least one server.

11. The method according to claim 1, in, Determining whether to process the uninstall data includes: determining that the uninstall data is to be processed by the server; During the period when the server processes the offload data, changing the offload point and the demand; sending information about the changed offload points and requirements to the server; and A result of processing the offloading data based on the information about the changed offloading point and requirement is received from the server.

12. A method for processing uninstallation data executed by a server, the method include: receiving data including a code from a user equipment UE; determining a split point at which data received from the UE is splittable; Sending a list including at least one split point to the UE; receiving, from the UE, information about an offloading point for the data among the at least one split point, and information about a demand for offloading data corresponding to the offloading point; sending a response to the UE regarding whether the server is capable of processing the offload data; as well as receiving, from the UE, a result of determining whether to process the offload data based on the response, wherein the at least one split point comprises a point for splitting the code into code portions, the code portions being executable even when uninstalled, each code portion being independent of other portions of the code, Wherein, when the uninstall data cannot be processed to meet the requirement, the response on whether the uninstall data can be processed includes: When the request is a mandatory request, including a negative acknowledgement (NACK), and When the requirement is not mandatory, include change request information, The change request information includes a request to change the location of the unloading point from one point to another point.

13. The method according to claim 12, in, The response regarding whether the server is capable of processing the offload data includes: When the server is able to process the offloaded data to meet the demand, an ACK is included.

14. A user equipment UE for offloading data, the UE include: Memory; Transceiver; as well as At least one processor configured to: determining a server for processing at least some of the data, the data including the code, sending the data to the server, receiving from the server a list comprising at least one split point at which the data is splittable, determining, based on the list, an unloading point for the data from the at least one split point, sending information about the uninstallation point and information about a demand for uninstallation data corresponding to the uninstallation point to the server, receiving a response from the server as to whether the offload data can be processed, and determining whether to process the offload data based on the response, wherein the at least one split point comprises a point for splitting the code into code portions, the code portions being executable even when uninstalled, each code portion being independent of other portions of the code, Wherein, when the uninstall data cannot be processed to meet the requirement, the response on whether the uninstall data can be processed includes: When the request is a mandatory request, including a negative acknowledgement (NACK), and When the requirement is not mandatory, include change request information, The change request information includes a request to change the location of the unloading point from one point to another point.

15. A server for processing offload data, the server include: Memory; Transceiver; as well as At least one processor configured to: receiving data including a code from a user equipment UE, determining a split point at which data received from the UE is splittable, sending a list including at least one split point to the UE, receiving, from the UE, information about an offloading point for the data among the at least one split point and information about a demand for offloading data corresponding to the offloading point, sending a response to the UE regarding whether the server is able to process the offloaded data, and receiving, from the UE, a result of determining whether to process the offload data based on the response, wherein the at least one split point comprises a point for splitting the code into code portions, the code portions being executable even when uninstalled, each code portion being independent of other portions of the code, Wherein, when the uninstall data cannot be processed to meet the requirement, the response on whether the uninstall data can be processed includes: When the request is a mandatory request, including a negative acknowledgement (NACK), and When the requirement is not mandatory, include change request information, The change request information includes a request to change the location of the unloading point from one point to another point.