Method and device for supporting edge computing service federation

Abstract

A method performed by an edge configuration server (ECS) associated with a first edge computing service provider in an edge computing system includes sending a request message to a partner ECS associated with a second edge computing service provider for requesting information associated with an edge data network (EDN), and receiving a response message including information associated with the EDN from the partner ECS, where the EDN is identified based on the request message.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication systems, and more particularly, to a method for supporting edge computing services in cooperation between operators or edge computing service providers in a wireless communication system. Background Art

[0002] The fifth generation (5G) mobile communication technology defines a wide frequency band that enables high transmission rates and new services, and can be implemented not only in frequency bands below 6 gigahertz (GHz), such as 3.5 GHz, but also in frequency bands above 6 GHz, called millimeter waves (mmWave), including 28 GHz and 39 GHz. People have also considered implementing the sixth generation (6G) mobile communication technology, called a super 5G system, in terahertz (THz) bands, such as the 95 GHz to 3THz band, to achieve a transmission rate 50 times faster than 5G mobile communication technology and ultra-low latency that is one-tenth of that of 5G mobile communication technology.

[0003] At the beginning of the development of 5G technology, in order to support services and meet the performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC) and massive machine-type communication (mMTC), standardization has been ongoing on beamforming and massive multiple-input multiple-output (MIMO) for alleviating radio wave path loss in millimeter waves and increasing radio wave transmission distance, supporting parameter sets such as multiple subcarrier spacing for dynamic operation of millimeter wave resources and time slot formats for efficient utilization, initial access technology for supporting multi-beam transmission and broadband, definition and operation of bandwidth parts (BWP), new channel coding methods such as low-density parity check (LDPC) codes for large-scale data transmission and polar codes for high-reliability transmission of control information, L2 preprocessing and network slicing for providing dedicated networks dedicated to specific services.

[0004] Discussions have been ongoing on improvements and performance enhancements to initial 5G mobile communication technologies in view of the services to be supported by 5G mobile communication technologies, and physical layer standardization has been carried out on technologies such as vehicle-to-everything (V2X) for assisted driving decisions by autonomous vehicles based on information about the vehicle's position and status transmitted by the vehicle and for improving user convenience, unlicensed radio new air interface (NR-U) for system operation in compliance with various regulatory requirements in unlicensed frequency bands, NR user equipment (UE) power saving, non-terrestrial network (NTN) for UE satellite direct communication to provide coverage in areas where communication with terrestrial networks is not possible, and positioning.

[0005] In addition, standardization is ongoing regarding technologies such as the Industrial Internet of Things (IIoT) for supporting new services through interoperability and convergence with other industries, Integrated Access and Backhaul (IAB) for providing nodes for network service area extension by supporting wireless backhaul links and access links in an integrated manner, mobility enhancement including conditional handover and dual-active protocol stack (DAPS) handover, and two-step random access for simplifying the random access channel (RACH) procedure (two-step RACH for NR). Standardization is also ongoing regarding the 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and the system architecture / service of mobile edge computing (MEC) for receiving services based on UE location.

[0006] As 5G mobile communication systems are commercialized, an exponentially increasing number of connected devices will be connected to the communication network, and it is therefore expected that enhanced functions and performance of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research related to extended reality (XR) is planned for effective support of augmented reality (AR), virtual reality (VR), mixed reality (MR), 5G performance improvement, and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.

[0007] This development of 5G mobile communication systems will lay the foundation not only for the development of new waveforms for providing terahertz band coverage of 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas and large antennas, metamaterial lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technology using orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS), but also for the development of full-duplex technology for increasing the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for achieving system optimization from the design stage by utilizing satellites and AI and internalizing end-to-end AI-supported performance, and next-generation distributed computing technology for realizing services with a complexity that exceeds the operational capability limits of UEs by utilizing ultra-high performance communication and computing resources.

[0008] An edge computing system for supporting edge node sharing (i.e., edge federation) may support access to an edge application server (EAS) hosted in another operator's edge hosting environment (EHE). The other operator's EHE may be located in an edge data network (EDN) that is different from the EDN to which the protocol data unit (PDU) session is traditionally connected. That is, there is a need in the art for access to EDNs with different data network names (DNNs) / single network slice selection assistance information (S-NSSAI), and for improved UE routing selection policies (URSPs) or UE-locally configured DNN / S-NSSAI values ​​that are traditionally configured in the UE (configured according to the home PLMN). Summary of the invention

[0009] Technical issues The present disclosure is to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below.

[0010] Therefore, one aspect of the present disclosure is to provide a method for supporting edge computing services by accessing an edge hosting environment of another operator other than the network operator in which the UE is registered, so as to support edge computing service collaboration (edge ​​federation or edge node sharing).

[0011] Another aspect of the present disclosure is to provide a method for determining whether edge computing service collaboration is required in an edge computing system.

[0012] Another aspect of the present disclosure is to provide a method for obtaining configuration information in a partner edge computing system.

[0013] Another aspect of the present disclosure is to provide a method for modifying a configuration in a UE so that a PDU session of the UE can be generated according to partner edge computing configuration information.

[0014] Technical Solution According to one aspect of the present disclosure, a method performed by an edge configuration server (ECS) associated with a first edge computing service provider in an edge computing system includes: sending a request message for requesting information associated with an edge data network (EDN) to a partner ECS associated with a second edge computing service provider, and receiving a response message including information associated with the EDN from the partner ECS, wherein the EDN is identified based on the request message.

[0015] According to one aspect of the present disclosure, a method performed by a partner ECS associated with a first edge computing service provider in an edge computing system includes: receiving a request message for requesting information associated with an EDN from an ECS associated with a second edge computing service provider, identifying the EDN based on the request message to provide edge computing services, and sending a response message including the information associated with the EDN to the ECS.

[0016] According to one aspect of the present disclosure, an ECS associated with a first edge computing service provider in an edge computing system includes: a transceiver; and a controller, the controller being coupled to the transceiver and configured to send a request message for requesting information associated with an EDN to a partner ECS associated with a second edge computing service provider, and to receive a response message including the information associated with the EDN from the partner ECS, wherein the EDN is identified based on the request message.

[0017] According to one aspect of the present disclosure, a partner ECS associated with a first edge computing service provider in an edge computing system includes: a transceiver; and a controller, the controller being coupled to the transceiver and configured to receive a request message for requesting information associated with an EDN from an ECS associated with a second edge computing service provider, identify the EDN based on the request message to provide edge computing services, and send a response message including the information associated with the EDN to the ECS.

[0018] Advantageous Effects of the Invention According to an embodiment of the present disclosure, an edge computing service available area for a specific UE may be expanded.

[0019] Furthermore, according to embodiments of the present disclosure, operators may reduce the cost of investing in a hosting environment and infrastructure for providing edge computing services.

[0020] In addition, according to an embodiment of the present disclosure, configuration information and policies related to PDU session generation in a UE may be updated to access an edge computing hosting environment of a partner operator.

[0021] Effects that can be obtained in the present disclosure are not limited to the above-mentioned effects, and other unmentioned effects will be clearly understood by those of ordinary skill in the art to which the present disclosure belongs. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0023] Figure 1 An example of an edge computing system architecture for supporting federation or edge node sharing according to an embodiment is shown.

[0024] Figure 2 An example of a signaling flow for providing edge data network configuration information through federation according to an embodiment is shown.

[0025] Figure 3 An example of a signaling flow for providing edge data network configuration information through federation according to an embodiment is shown.

[0026] Figure 4 An example of a signaling flow of a method for determining whether to configure and apply a URSP generated for federation and a method for managing a user plane path according to an embodiment is shown.

[0027] Figure 5 is a block diagram showing an internal structure of a UE according to an embodiment.

[0028] Figure 6 The structure of a network entity for performing a network function according to an embodiment is shown. DETAILED DESCRIPTION

[0029] The embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The terms described below are defined in consideration of the functions in the present disclosure and may differ according to the intentions or customs of the user, operator, etc. Therefore, the definition of the terms should be based on the entire disclosed content. For clarity and brevity, the description of well-known functions and structures is omitted.

[0030] As used herein, for ease of description, terms referring to network entities and objects, messages, and identification information of edge computing systems are used exemplarily. Therefore, the present disclosure is not limited by the terms used below, and other terms referring to subjects with equivalent technical meanings may be used.

[0031] In the drawings described herein, the order of description does not always correspond to the order in which the steps of each method are performed, and the order relationship between the steps may be changed, or the steps may be performed in parallel. Alternatively, some elements may be omitted, and only some elements may be included therein, without departing from the essence and scope of the present disclosure.

[0032] Here, for convenience, terms and names defined in the 5G system standard will be used, but the present disclosure is not limited by these terms and names and can be applied to systems conforming to other standards in the same manner.

[0033] Figure 1 An example of an edge computing system architecture 100 for supporting federation or sharing of edge nodes is shown according to an embodiment.

[0034] Figure 1 A description of the network and edge computing entities shown in is as follows.

[0035] The edge computing system may include an edge enabler server (EES) 110, an edge configuration server (ECS) 120, and an edge enabler client (EEC) 130. The EES is building an edge hosting environment (or edge computing platform) and knows information about an edge application server (EAS) 140 running in the edge hosting environment (i.e., edge data network 150).

[0036] The EES 110 may perform a function of negotiating with the UE 160 to connect the application client (AC) 170 of the UE 160 and the EAS 140 in an edge hosting environment. The EEC 130 may be embedded in the UE 160 supporting the edge computing system. The layer in which the interoperation between the edge enabler and the EEC 130 is performed may be referred to as an edge enabling layer. In the present disclosure, the UE 160 in which the EEC 130 is embedded to configure the edge enabling layer may include not only smartphones but also IoT devices and vehicles.

[0037] The ECS 120 knows the deployment information about the EES 110, and can perform a function of transmitting configuration information (edge ​​data network configuration information) for using edge computing services to the UE 160. The configuration information may include edge data network connection information (e.g., data network name, S-NSSAI, etc.), edge data network service area (e.g., cell list, tracking area list, PLMN ID), and EES 110 connection information such as a uniform resource identifier (URI). The edge data network service area may be an available area of ​​the EES 110 configured by the EES 110. Based on this, the UE 160 can receive EES 110 information accessible from a specific location. In the case where the ECS 120 is able to know information about the EAS 140 running in the edge hosting environment of a specific EES 110, the UE 160 can also obtain the corresponding information through the EEC 130. In addition, the ECS 120 can exchange configuration information for using edge computing services with other ECSs 120.

[0038] EAS 140 may refer to a third-party application server running in an edge computing system. EAS 140 runs on the infrastructure provided by the edge hosting environment, and thus EAS 140 may provide ultra-low latency services at a location close to UE 160.

[0039] UE 160 may include AC 170, EEC 130 that performs interoperation between AC and edge computing services, and a mobile terminal (MT) that accesses a mobile communication system. The application of UE 160 is an application provided by a third party and may mean a client application for a specific application service running in UE 160. Multiple applications may run in UE 160. At least one of these applications may use MEC services. EEC 130 in UE 160 may perform operations required to use edge computing services in UE 160. EEC 130 may determine an application that is capable of using edge computing services, and may perform operations to connect a network interface so that data of AC 170 of UE 160 may be transmitted to EAS 140 that provides edge computing services. The operation of establishing a data connection to use edge computing services may be performed in a third generation partnership project (3GPP) communication layer by a mobile terminal. The 3GPP communication layer performs a modem operation to use a mobile communication system, and may establish a wireless connection for data communication, register the UE 160 in the mobile communication system, establish a connection to send data to the mobile communication system, and perform a role of sending or receiving data.

[0040] In the federation (or edge node sharing) scenario described herein, UE 160 is registered in the core network 180 of network operator A 102 and is able to access an edge computing service provision server supported by partner network operator B 104 (in the edge hosting environment of operator B 104) via a PDU session generated with the help of operator A's core network 180.

[0041] Figure 2 An example of a signaling flow 200 for providing edge data network configuration information through federation is shown according to an embodiment.

[0042] In step 1, UE / EEC 210 may send a service provisioning request message to ECS A 220. For example, ECS A 220 may be an anchor ECS of network operator A. The corresponding message may include at least one of a UE identifier, an EEC identifier, UE location information, a home public land mobile network (HPLMN) ID, a serving PLMN ID, and AC information (e.g., an AC identifier, an EAS identifier, an EAS fully qualified domain name (FQDN), etc.).

[0043] The ECS A 220 may then determine whether to perform federation by considering the UE identifier, AC information, etc. included in the received service provisioning request message.

[0044] ECS A 220 may determine that federation is performed in the absence of such an EAS that is running or capable of instantiating an EAS in an edge hosting environment of a PLMN network operator accessed by UE 210 or an edge computing service provider that contracts directly with the PLMN network operator. Specifically, ECS A 220 may identify information about currently running EASs by comparing an EAS ID list in an EES profile provided by an EES accessible from the current location of UE 210 with AC information provided by UE 210. If information about the EAS running at this stage cannot be identified in the ECS, ECSA 220 may identify whether the subscriber of UE 210 hosting the EEC 210 supports federation (edge ​​node sharing) services.

[0045] In step 2-1, as a result of authentication (identification), in the case where federation for the corresponding UE is allowed, ECSA 220 may send a request message to an EES (e.g., EES A 230) that UE 210 can access, to identify whether an EAS (an EAS that can provide services to the corresponding AC) that complies with the AC information provided by UE 210 is running or whether its instantiation is possible. The instantiable EAS list request message sent by the ECS to the EES may include a UE identifier and AC information, and may be sent in the form of an existing EAS discovery request message. In step 2-2, ECS A 220 may receive an instantiable EAS list response message in response to the instantiable EAS list request message from the EES (e.g., EES A 230) that UE 210 can access.

[0046] In step 3, if it is identified in the previous stage that the EAS that can be provided to the EEC 210 is not running and its instantiation is impossible, the ECS A 220 may send an EDN configuration information request message to the federation partner ECS B 240 in order to perform federation. The EDN configuration information request message may include at least one of a UE identifier, an EEC ID, UE location information, a provider identifier of the ECS A 220, or AC information. For reference, the provider of the ECS or EES may be a mobile communication network operator or an operator that only provides edge computing service solutions (e.g., a cloud service provider). This information may be identified by the provider identifier of the ECS.

[0047] In step 4, ECS B 240 may find an EDN in which an EAS that complies with the UE information and AC information that have been received from ECS A 220 is running or whose instantiation is possible. For example, ECS B 240 may obtain EAS list information from EES B 250 hosted in an EDN accessible from the location of the UE and identify the EAS list information. When requesting the EAS list information, ECS B 240 may provide EES B 250 with a UE identifier, a UE HPLMN ID, a provider identifier of ECS A 220, etc., and may be provided with information that is allowed for the corresponding UE and ECS A 200 provider. This operation may be performed for a plurality of EESs registered in ECS B 240.

[0048] In step 5, ECS B 240 may provide ECS A 220 with EDN configuration information capable of providing services to the corresponding UE based on the information collected in the previous operation (for example, the information may include an EES identifier, an EES address, a DNN, an S-NSSAI, and / or a data network access identifier (DNAI)). In the case that the EDN configuration information cannot be shared with ECS A 220, ECS B 240 may send an indicator indicating that the EDN configuration signal cannot be shared or a redirection request indicator to ECS A 200 instead of providing EDN configuration data to ECS A 220.

[0049] In step 6, ECS A 220 may compare the DNN and S-NSSAI information in the EDN configuration information provided by ECS B 240 with the DNN or S-NSSAI conventionally used by UE 210. In the case of receiving information different from the information conventionally configured in the UE or different from the DNN and S-NSSAI in the EDN configuration information stored in ECS A 220 from ECS B 240, ECS A 220 may determine that a new PDU session for federation needs to be newly generated. ECS A 220 may determine that the UE needs to be configured with the DNN and S-NSSAI configuration information necessary to generate a new PDU session.

[0050] In step 7, in the case where it is determined that new DNN and S-NSSAI information should be configured for the UE, the ECS A 220 may send an application function steering for UE routing policy determination request (AF steering for URSP determination request) message to the network exposure function of the core network 260 of the PLMN (e.g., the home PLMN of the UE subscriber) that the UE 210 is currently accessing. The information in the corresponding message may be configured by: UE identifier, AC identifier (e.g., AC ID of EEC, AC ID of AC in UE), The space availability of the EDN service area configured to be provided by the partner ECS (for example, ECS B), The EDN DNN / S-NSSAI received from ECS B, used as a routing descriptor (RSD) constituting the URSP (for selecting a PDU Session that complies with the corresponding DNN / S-NSSAI when generating or mapping PDU Sessions through the URSP), and / or In case AF guidance to URSP has been issued conventionally from ECS A, the configured priority is higher than the priority of URSP.

[0051] In step 8, ECS A 220 may receive an AF directive to URSP determination response message from the network function of the core network 260. The corresponding message may include successful reception of the request and whether URSP generation is possible.

[0052] In step 9 , the network function of the core network 260 may send the generated URSP to the UE at the request of the ECS A 220 .

[0053] In step 10, the network function of the core network 260 may provide ECS A 220 with a result message regarding successful reception of the UE's URSP and completion of URSP configuration application.

[0054] In step 11, when recognizing that the URSP has been successfully configured and applied to the UE, the ECS A 220 may perform AF traffic impacting.

[0055] In step 12, ECS A 220 may transmit the EDN configuration message received from ECS B 240 in the previous operation to UE / EEC 210 by including the EDN configuration information in a service provisioning response message.

[0056] Figure 3 An example of a signaling flow 300 for providing edge data network configuration information through federation is shown according to an embodiment.

[0057] In the following, reference will be made to Figure 3 Describe the signaling flow in detail.

[0058] In step 0a or 0b, the ECS may receive information about the instantiable EAS list and federation (or edge node sharing) information from an EES server or an edge management system (EMS) (Note: these EES servers and EMS are directly operated by the network operator, or may be provided and operated by an edge computing service provider contracted with the network operator). For example, ECS B340 may receive instantiable EAS information and federation (or edge node sharing) information from EES B 350 or EMS B 370 (i.e., management system B) according to edge application requirements. The information that may be received by the ECS from the EES or EMS may include the following information.

[0059] Instantiable EAS information: EAS identifier and address information that can be instantiated in an edge hosting environment or infrastructure of a network operator or an edge computing service provider contracted with a network operator (in the case of an EAS before instantiation, an FQDN or URI value instead of IP address information can be configured as the address information), edge computing service provider (ECSP) identifier information (the identifier value for a provider that provides an edge hosting environment in which the EAS can be instantiated can have an identifier value indicating a network operator or a third-party edge computing service provider), information about an EDN or network slice information that may be instantiated therein (a combined value of a DNN and an S-NSSAI), information about a location that may be instantiated therein (a latitude and longitude value as geographic location information, or a tracking area ID, cell ID, PLMN ID, or data network access identifier value as a 3GPP network-related location information value) Federation (or edge node sharing) information: information about whether federation (or border node sharing) is allowed, the federation allowed area, the federation allowed duration, an indicator indicating whether subscribers of other service providers are allowed to access and use the edge computing services of a specific EAS, EES or EDN, the allowed area (e.g., latitude and longitude, or tracking area ID, cell ID, PLMNID, DNAI, etc.), and the allowed duration (timestamp value or scheduling value).

[0060] Information about whether inter-PLMN (or inter-ECSP) EDGE-9 (EES to EES interface) is supported: Information about whether the EDGE-9 interface for a specific EES is supported even for other PLMNs or edge computing service provider domains. For example, information about whether access and provision of services to the EES are allowed outside the edge hosting environment of the edge computing service provider or the PLMN where the EES is currently installed. Whether EDGE-9 is supported may be supported only for specific network operators or edge computing service providers, and the EDGE-9 interface allowed targets including specific network operator or edge computing service provider information (e.g., ECSP identifier information or PLMN ID information) may be restricted. For example, ECS B 340 can obtain the identifier of edge computing service provider A from EES B 350 or EMS B 370.

[0061] Information on whether inter-PLMN (or inter-ECSP) EDGE-10 is supported: Information on whether the EDGE-10 interface for a specific ECS is supported even for other PLMNs or edge computing service provider domains. For example, information on whether access and provision of services to the ECS is allowed outside the edge computing service provider or edge hosting environment of the PLMN where the ECS is currently installed. Edge computing service provider information or specific network operator information may be provided together, in which case federation (or edge node sharing) is only allowed for the corresponding provider / operator.

[0062] In step 1, UE / EEC 310 may send a service provisioning request message to ECS A 320. For example, ECS A 320 may be an anchor ECS of network operator A. For example, the corresponding message may include at least one of a UE identifier, an EEC identifier, UE location information, an HPLMN ID, a serving PLMN ID, and AC information (e.g., an AC identifier, an EAS identifier, an EAS (FQDN), etc.).

[0063] In step 2, the ECS A 320 may determine whether to perform federation by considering a UE identifier, AC information, etc. included in the received service provisioning request message.

[0064] ECS A 320 may determine to perform federation in the absence of such an EAS that is running or capable of instantiating an EAS in an edge hosting environment of a PLMN network operator accessed by UE 310 or an edge computing service provider directly contracted with the PLMN network operator. Specifically, ECS A 320 may identify information about the currently running EAS by comparing an EAS ID list in an EES profile provided by an EES accessible from the current location of UE 310 with the AC information provided by UE 310. If information about the EAS running at this stage cannot be identified in the ECS, ECS A 320 may identify whether the subscriber of UE 310 hosting the EEC supports federation (edge ​​node sharing) services. As a result of the authentication, when federation for the corresponding UE is allowed, ECS A 320 can identify whether an EAS capable of providing services to the corresponding AC that complies with the AC information is running or its instantiation is possible based on the instantiable EAS list information provided by EES A or EMS A330 in step 0b, wherein the AC information is information provided by UE 310 to the EES accessible by UE 310, and can identify whether the EAS accessible by UE 310 can be instantiated.

[0065] In step 3, if it is identified in the previous operation that the EAS that can be provided to the EEC is not running and its instantiation is impossible, ECS A 320 may send an EDN configuration information request message to the federation partner ECS B 340 in order to perform federation. For example, the corresponding message may include a UE identifier, an EEC ID, UE location information, and / or AC information.

[0066] In step 4, ECS B 340 may find an EDN in which an EAS that complies with the UE 310 information and AC information that have been received from ECS A 320 is running or whose instantiation is possible. For example, ECSB 340 may obtain EAS list information from an EES hosted in an EDN accessible from the location of UE 310 and identify the EAS list information. When requesting the EAS list information, ECS B 340 may provide the EES with a UE identifier, a UE HPLMN ID, a provider identifier of ECS A 320, etc., and may be provided with information that is allowed by the corresponding UE 310 and ECS A 320 provider. This operation may be performed for a plurality of EESs registered in ECS B 340.

[0067] In step 5, ECS B 340 may send a response message to the request to ECS A 320. ECS B 340 may provide EDN configuration information (e.g., the information may include an EES identifier, an EES address, a DNN, an S-NSSAI, and / or a DNAI) that can provide services to the corresponding UE to ECS A 320 based on the information collected in the previous operation. In the case where the EDN configuration information cannot be shared with ECS A 320, ECS B 340 may send an indicator indicating that the EDN configuration signal cannot be shared or a redirection request indicator to ECS A 320 instead of providing EDN configuration data to ECS A 320.

[0068] In step 6, ECS A 320 may compare the DNN and S-NSSAI information in the EDN configuration information provided by ECS B 340 with the DNN or S-NSSAI traditionally used by UE 310. In the case of receiving information different from the DNN and S-NSSAI in the EDN configuration information traditionally configured in UE 310 or stored in ECS A 320 from ECS B 340, ECSA 320 may determine that a new PDU session for federation needs to be newly generated. ECS A 320 may determine that UE 310 needs to be configured with the DNN and S-NSSAI configuration information necessary to generate a new PDU session.

[0069] In step 7, in the case where it is determined that new DNN and S-NSSAI information should be configured for UE 310, ECS A 320 may send an application function guidance for UE routing policy determination request (AF guidance for URSP determination request) message to the network exposure function of the core network 360 of the PLMN (e.g., the home PLMN of the UE subscriber) that UE 310 is currently accessing. The information in the corresponding message may be configured by the following items: UE identifier, AC identifier (e.g., AC ID of the EEC, or AC ID of the AC in the UE), The space availability of the EDN service area configured to be provided by the partner ECS (for example, ECS B), EDN DNN / S-NSSAI received from ECS B used as RSD, and / or If the existing ECS ​​A issues AF guidance to the URSP, the priority of the configuration is higher than the priority of the URSP.

[0070] In step 8, ECS A 320 may receive an AF directive to URSP determination response message from the network function of the core network 360. The corresponding message may include successful reception of the request and whether URSP generation is possible.

[0071] In step 9 , the network function of the core network 360 may send the generated URSP to the UE 310 at the request of the ECS A 320 .

[0072] In step 10, the network function of the core network 360 may provide ECS A 320 with a result message regarding successful reception of the URSP of the UE 310 and completion of the URSP configuration application.

[0073] In step 11 , when recognizing that the URSP has been successfully configured and applied to the UE 310 , the ECS A 320 may perform AF traffic impact with the core network 360 .

[0074] In step 12, ECS A 320 may send the EDN configuration message received from ECS B 340 in the previous stage to EEC 310 by including the EDN configuration information in the service provisioning response message.

[0075] In the above Figure 2 and Figure 3 In the example, the steps performed after ECS A 320 obtains the EDN configuration information capable of federation from partner ECS B 340 may be as follows: Figure 4 Modify and execute as shown.

[0076] Figure 4 An example of a signaling flow 400 of a method for determining whether to configure and apply a URSP generated for federation and a method for managing a user plane path according to an embodiment is shown.

[0077] In step 1, assume that Figure 2 or Figure 3 Steps 1-6 have been completed.

[0078] In step 2, if it is determined that new DNN and S-NSSAI information should be configured for UE 410, ECS A 420 may send an application function steering for UE routing policy determination request (AF steering for URSP determination request) message to the network exposure function of the core network 460 of the PLMN (e.g., the home PLMN of the UE subscriber) that UE 410 is currently accessing. The information in the corresponding message may be configured by: UE identifier, AC identifier (e.g., AC ID of the EEC or AC ID of the AC in the UE), The space availability of the EDN service area configured to be provided by the partner ECS (for example, ECS B), EDN DNN / S-NSSAI received from ECS B used as RSD, and / or If ECS A has traditionally published AF guidelines for URSP, the configuration takes precedence over the URSP.

[0079] In step 3, ECS A 420 may receive an AF directive to URSP determination response message from the network function of the core network 460. The corresponding message may include successful reception of the request and whether URSP generation is possible.

[0080] In step 4, the network function of the core network 460 may send the generated URSP to the UE / EEC at the request of the ECS A 420. The UE / EEC 410 may identify whether successful configuration and application of the URSP, which has been obtained from the core network 460, is possible. For example, based on the reception of the URSP of the method for updating the mapping between the traffic generated by the application client or EEC used traditionally and the PDU session, the UE / EEC 410 may identify that the application of the URSP is successful. The subject that performs this identification operation may correspond to a modem, EEC or AC in the UE, or a function in the OS, and when the successful application of the URSP is identified in any device in the UE, the EEC 410 should be notified of the identification.

[0081] In step 5, the network function of the core network 460 may provide a result message regarding the successful reception of the URSP by the UE 410 and the completion of the application of the URSP configuration to the ECS A 420.

[0082] In step 6, the UE / EEC 410 may send the message indicating whether the configuration / application of the URSP is successful, which has been received in step 4, to the ECS. The corresponding message may include: information included in the applied URSP and an indicator indicating whether the application is successful. The information in the URSP may include: information about an application program to be applied (e.g., AC identifier, FQDN) or a DNN used as a traffic descriptor (DNN preconfigured and used in the AC), and at least one of the S-NSSAI or the DNN used as the RSD. In addition, in the case where multiple URSP configurations / applications are performed for multiple ACs, the indicator indicating whether the application of the URSP is successful may indicate whether the URSP configuration / application is successful for each AC in the UE 410.

[0083] In step 7a, ECS A 420 may perform AF traffic impacting with the core network 460 after receiving messages indicating whether the configuration / application of the URSP is successful from both the core network 460 and the EEC 410. In step 7b, ECS A 420 may notify ECS B 440 that the URSP has been successfully configured / applied, and may send an indicator requesting the execution of AF traffic impacting, a target UE identifier, and a serving PLMN ID of the UE 410 to ECS B 400. ECS B 440 may transmit the information received from ECS A 420 in step 7b to EES B 450.

[0084] In step 8 , ECS A 420 may include the EDN configuration information received from ECS B 440 in the previous step in a service provisioning response message and transmit the EDN configuration information to UE / EEC 410 .

[0085] Figures 2 to 4 The signals / information sent and received between ECS A and ECS B can be transmitted through the EDGE-10 interface between ECS A and ECS B.

[0086] The methods and / or embodiments of the present disclosure may be Figure 5 UE and Figure 6 network entity execution.

[0087] Figure 5 is a block diagram showing an internal structure of a UE 500 according to an embodiment.

[0088] Reference Figure 5 , UE 500 may include a radio frequency (RF) processor 5-10, a baseband processor 5-20, a memory 5-30, and a controller 5-40. The present disclosure is not limited to the above example, and UE 500 may include more Figure 5 UE 500 may include an AC and an EEC as described herein.

[0089] The RF processor 5-10 may be configured to perform functions of sending and receiving signals through a wireless channel, such as frequency band conversion and amplification of signals. That is, the RF processor 5-10 may be configured to up-convert the baseband signal provided by the baseband processor 5-20 to an RF band signal, thereby transmitting the signal through an antenna, and down-convert the RF band signal received by the antenna to a baseband signal. For example, the RF processor 5-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. The UE 500 may have multiple antennas, and the RF processor 5-10 may include multiple RF chains. The RF processor 5-10 may perform beamforming. That is, the RF processor 5-10 may be configured to adjust the phase and amplitude of the signal sent and received through multiple antennas or antenna elements. In addition, the RF processor 5-10 may perform MIMO, and may receive multiple layers when performing MIMO operations.

[0090] The baseband processor 5-20 can perform the conversion function between the baseband signal and the bit string according to the physical layer specification of the system. For data transmission, the baseband processor 5-20 encodes and modulates the transmission bit string to generate complex symbols. For data reception, the baseband processor 5-20 can demodulate and decode the baseband signal provided from the RF processor 5-10 to recover the received bit string. That is, when the orthogonal frequency division multiplexing (OFDM) scheme is applied, in the case of data transmission, the baseband processor 5-20 generates complex symbols by encoding and modulating the transmission bit string, maps the complex symbols to subcarriers, and then configures OFDM symbols through inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. In the case of data reception, the baseband processor 5-20 can divide the baseband signal provided by the RF processor 5-10 into OFDM symbol units, recover the signal mapped to the subcarrier through a fast Fourier transform (FFT) operation, and then recover the received bit string through demodulation and decoding.

[0091] The baseband processor 5-20 and the RF processor 5-10 may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. At least one of the baseband processor 5-20 and the RF processor 5-10 may include multiple communication modules to support a variety of different wireless access technologies and different communication modules for processing different frequency band signals. For example, different wireless access technologies may include a wireless local area network (LAN) and a cellular network. Different frequency bands may include super high frequency (SHF) (e.g., 2.NRHz or NRHz) bands and millimeter wave (e.g., 50GHz) bands. The UE 500 may send and receive signals to and from a base station by using the baseband processor 5-20 and the RF processor 5-10, and the signal may include control information and data.

[0092] The memory 5-30 stores data such as basic programs, application programs, and configuration information for the operation of the UE 500. Specifically, the memory 5-30 may store information related to a second access node that performs wireless communication using a second radio access technology, and may provide the stored data in response to a request from the controller 5-40. The memory 5-30 may include a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, and a digital versatile disk (DVD), or a combination of storage media. In addition, the memory 5-30 may include a plurality of memories.

[0093] The controller 5-40 controls the overall operation of the UE 500. For example, the controller 5-40 may control the signal flow between blocks to perform operations according to the above flowchart, and may be configured to send a service provisioning request message to the ECS through the baseband processor 5-20 and the RF processor 5-10, and receive a service provisioning response message from the ECS. In addition, the controller 5-40 records data in the memory 5-30 and reads data from it. To this end, the controller 5-40 may include at least one processor. For example, the controller 5-40 may include a communication processor (CP) for performing communication control and an application processor (AP) for controlling a higher layer (such as an application). At least one element in the UE 500 may be implemented as a single chip.

[0094] Figure 6 1 shows the structure of a network entity 600 for performing network functions according to an embodiment. For example, Figure 6 A network entity can be a node of the network. For example, Figure 6 The network entity may correspond to one of the EEC, ECS, EES, EAS, EMS or EDN described above through the embodiments of the present disclosure.

[0095] Reference Figure 6 , a network entity for performing a network function may include a transceiver 610, a controller 620, and a memory 630. The controller 620 may be defined as a circuit, an application specific integrated circuit, or at least one processor.

[0096] The transceiver 610 may send / receive signals to / from other network entities. The transceiver 610 may send / receive signals or messages to / from, for example, an access and mobility management function (AMF), which is a network entity that manages access and mobility of UEs to an access network.

[0097] The controller 620 may control the overall operation of a network entity that performs network functions according to the embodiments proposed in the present disclosure. For example, the controller 620 may control the signal flow between blocks to perform the operations described herein, and may be configured to send a request message to a partner ECS for requesting information associated with an EDN, and receive a response message including information associated with the EDN. The controller 620 may be configured to receive an EES profile from an EES.

[0098] The memory 630 may store at least one of information transmitted / received by the transceiver 610 and information generated by the controller 620 .

[0099] The above embodiments and the accompanying drawings are only specific examples presented to easily explain the technical content of the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is clear to those skilled in the art that other variations based on the technical scope of the present disclosure can be implemented. In addition, the above embodiments can be used in combination as needed. For example, all embodiments of the present disclosure can be partially combined to operate a base station and a UE.

[0100] While the present disclosure has been described with reference to various embodiments, various changes may be made without departing from the spirit and scope of the present disclosure, which is defined not by the detailed description and embodiments but by the appended claims and their equivalents.

Claims

1. A method performed by an edge configuration server ECS associated with a first edge computing service provider in an edge computing system, the method comprising: Sending a request message for requesting information associated with an edge data network EDN to a partner ECS associated with a second edge computing service provider; as well as receiving a response message from the partner ECS including information associated with the EDN, Wherein, the EDN is identified based on the request message.

2. The method according to claim 1, in, The request message includes at least one of information about a location of a terminal, an identifier of the terminal, information about an application client, or an identifier of an edge enabler client.

3. The method according to claim 1, in, The information associated with the EDN includes at least one of an identifier of an edge enabler server EES associated with the partner ECS, an address of the EES, a data network name DNN, single network slice selection auxiliary information S-NSSAI, or a data network access identifier DNAI.

4. The method according to claim 1, further comprising: receiving, from an edge enabler server EES associated with the ECS, an EES profile including information of an instantiable edge application server EAS; as well as In a case where an EAS is not identified based on the EES profile, a determination is made to use edge computing services from the second edge computing service provider.

5. The method according to claim 1, in, The request message and the response message are transmitted via an edge-10 interface.

6. A method performed by a partner edge configuration server ECS associated with a first edge computing service provider in an edge computing system, the method comprising: receiving, from an ECS associated with a second edge computing service provider, a request message for information associated with an edge data network (EDN); identifying the EDN based on the request message to provide edge computing services; as well as A response message including information associated with the EDN is sent to the ECS.

7. The method according to claim 6, in, The request message includes at least one of information about a location of a terminal, an identifier of the terminal, information about an application client, or an identifier of an edge enabler client, and The request message and the response message are transmitted via the edge-10 interface.

8. The method according to claim 6, in, The information associated with the EDN includes at least one of an identifier of an edge enabler server EES associated with the partner ECS, an address of the EES, a data network name DNN, single network slice selection auxiliary information S-NSSAI, or a data network access identifier DNAI.

9. The method according to claim 6, further comprising: The instantiable edge application server EAS information is received from the edge enabler server EES associated with the partner ECS.

10. An edge configuration server ECS associated with a first edge computing service provider in an edge computing system, the ECS comprising: Transceiver; as well as a controller coupled to the transceiver and configured to: sending a request message for information associated with an edge data network EDN to a partner ECS associated with a second edge computing service provider, and receiving a response message from a partner ECS including information associated with the EDN, Wherein, the EDN is identified based on the request message.

11. The ECS according to claim 10, in, The request message includes at least one of information about a location of a terminal, an identifier of the terminal, information about an application client, or an identifier of an edge enabler client, and The request message and the response message are transmitted via the edge-10 interface.

12. The ECS according to claim 10, in, The information associated with the EDN includes at least one of an identifier of an edge enabler server EES associated with the partner ECS, an address of the EES, a data network name DNN, single network slice selection auxiliary information S-NSSAI, or a data network access identifier DNAI.

13. The ECS of claim 10, wherein: The controller is also configured to: receiving an EES profile including information of an instantiable edge application server EAS from an edge enabler server EES associated with the ECS, and In a case where an EAS is not identified based on the EES profile, a determination is made to use edge computing services from the second edge computing service provider.

14. A partner edge configuration server ECS associated with a first edge computing service provider in an edge computing system, the ECS comprising: Transceiver; as well as a controller coupled to the transceiver and configured to: receiving, from an ECS associated with a second edge computing service provider, a request message for information associated with an edge data network (EDN), identifying the EDN to provide edge computing services based on the request message, and A response message including information associated with the EDN is sent to the ECS.

15. The partner ECS according to claim 14, in, The request message includes at least one of information about a location of a terminal, an identifier of the terminal, information about an application client, or an identifier of an edge enabler client, The information associated with the EDN includes at least one of an identifier of an edge enabler server EES associated with the partner ECS, an address of the EES, a data network name DNN, single network slice selection auxiliary information S-NSSAI, or a data network access identifier DNAI, and The request message and the response message are transmitted via the edge-10 interface.

Images