Method and system for intent-driven deployment and management of communication services in a wireless communication system

Abstract

Various embodiments of the present disclosure disclose methods and systems for intent-driven deployment and management of communication services at the edge of a 3GPP network. The main purpose of the embodiments herein is to disclose methods and systems for runtime deployment and management of (multiple) communication service instances at the edge of a 3GPP network. Another purpose of the embodiments herein is to provide a mechanism by which CSI can be targeted to specific locations for better market penetration. Another purpose of the embodiments herein is to provide a mechanism by which CSI can be deployed using availability criteria that manage when a service will be available (given a timestamp). Another purpose of the embodiments herein is to make deployment of CSI at the edge of the network easier, thereby creating new business opportunities for both service and edge providers.

Description

Technical Field

[0001] The present disclosure relates to the field of fifth generation (5G) wireless communication networks, and more specifically, to deploying communication services at the edge of a 3GPP network in a 5G communication network. Background Art

[0002] The fifth generation (5G) communication network includes a 5G access network (AN), a 5G core network and at least one user equipment (UE) (refer to TS23.501). It is expected that the 5G network will provide optimized support for a variety of different communication services, different traffic loads and different end-user groups.

[0003] 5G networks are designed to enhance their capabilities to meet the key performance indicators (KPIs) required by emerging vehicle-to-everything (V2X) applications. For these advanced applications, requirements such as data rate, reliability, latency, communication range and speed become more stringent. For example, network slicing can use vehicle-to-everything (V2X) services. One of the key technologies to achieve network slicing is fixed mobile convergence (FMC). FMC includes wireless to everything (WTTx) and fiber to everything (FTTx). Therefore, 5G seamless eMBB (enhanced mobile broadband) is expected to provide native support for network slicing. For optimization and resource efficiency, 5G networks will select the most appropriate 3GPP or non-3GPP access technology for communication services. This allows multiple access technologies to be used for one or more services active on the UE at the same time.

[0004] Operators can use one or more network slice instances to provide communication services that require similar network characteristics to different vertical industries. 3GPP TS28.530 and 28.531 define the management of network slices in 5G networks. It also defines the concept of communication services provided using one or more network slices. A network slice instance (NSI) can support multiple communication service instances (CSI).

[0005] Currently, research is being conducted in 3GPP SA5 (TR 28.805-Research on Communication Service Management), which discusses the provisions for the management of (multiple) CSIs running on (multiple) NSIs. 3GPP also defines management entities such as the Network Slice Management Function (NSMF) and the Communication Service Management Function (CSMF), which provide network slice instance (NSI) and communication service instance (CSI) management services respectively. In addition, research on the edge is being conducted in 3GPP SA6 (3GPP TR 23.758-Research on application architecture to enable edge applications), which is used to specify an application framework or enabling layer platform to support edge computing in 3GPP specified networks (e.g., edge service discovery, client authentication). The study includes the interaction between the UE and the enabling layer platform, as well as the interaction between the applications deployed on the edge and the enabling layer platform. In addition, the study also achieves integration with the underlying 3GPP core network.

[0006] Currently, there are no procedures defined in 3GPP or elsewhere regarding mechanisms for deploying and managing communication services at the edge of a 3GPP network. Summary of the invention

[0007] Technical issues

[0008] The main purpose of the embodiments of this document is to disclose a method and system for runtime deployment and management of (multiple) communication service instances (CSIs) at the edge of a 3GPP network for a 5G network.

[0009] Another object of embodiments herein is to provide a mechanism by which CSI can be targeted to specific locations for better market penetration.

[0010] It is another object of embodiments herein to provide a mechanism by which CSI can be deployed using availability criteria that govern when a service will be available.

[0011] Technical Solution

[0012] Therefore, an embodiment of the present invention provides a method for deploying at least one communication service at a network edge in a 5G network, the method comprising: sending, by an intent-driven management service (IDMS) consumer, a request for creating at least one communication service to an IDMS producer; identifying, by the IDMS producer, a network edge for creating at least one communication service based on a service availability parameter provided in the request received from the IDMS consumer, wherein the service availability parameter comprises a timestamp indicating the availability of the at least one requested communication service; and identifying, by a network service management function (NSMF), a network slice instance (NSI) to be assigned to the at least one communication service, wherein the NSI comprises an application that provides server functions for the at least one communication service.

[0013] Therefore, an embodiment of the present invention provides a method for managing at least one communication service at a network edge in a 5G network, the method comprising: a communication service consumer (CSC) sending a request for creating at least one communication service to a communication service producer (CSP); selecting a profile by the CSP, wherein the profile is available at a timestamp provided in the request received from the CSC; identifying, by the CSP, a network edge for creating at least one communication service based on an availability parameter provided in the request received from the CSC, and identifying, by the NSMF, a network slice instance (NSI) to be assigned to the at least one communication service, wherein the NSI includes an application that provides server functions for the at least one communication service.

[0014] Therefore, an embodiment of the present invention provides a system for deploying and managing at least one communication service at a network edge, the system comprising: a communication service consumer (CSC); a communication service producer (CSP) communicatively coupled to the CSC, wherein the CSP is configured to: receive a request from the CSC to create at least one communication service, wherein the request is in the form of one of an intent and a transport protocol request; select a profile, wherein the profile is available at a timestamp provided in the request from the CSC; identify a network edge for creating at least one communication service based on an availability parameter provided in the request received from the CSC, wherein the service availability parameter includes a timestamp indicating the availability of the requested service; and send a request to the NSMF to allocate resources to the CSC, wherein the NSMF identifies a network slice instance (NSI) to be assigned to the at least one communication service upon receiving the request from the CSP, wherein the NSI includes an application that provides server functionality for the at least one communication service.

[0015] These and other aspects of the example embodiments herein will be better understood and appreciated when considered in conjunction with the following description and accompanying drawings. However, it should be understood that the following description, while indicating the example embodiments and many of their specific details, is given by way of illustration and not limitation. Many changes and modifications may be made within the scope of the example embodiments herein without departing from the spirit thereof, and the example embodiments herein include all such modifications.

[0016] Advantageous Effects of the Invention

[0017] The present disclosure provides methods and systems for runtime deployment and management of (multiple) communication service instances (CSIs) at the 3GPP network edge for 5G networks.

[0018] The present disclosure provides a mechanism by which CSI can be targeted to specific locations for better market penetration.

[0019] The present disclosure provides a mechanism by which CSI can be deployed using availability criteria that govern when a service will be available. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The embodiments of the present invention are shown in the accompanying drawings, in which similar reference letters indicate corresponding parts in various drawings. The embodiments of the present invention will be better understood through the following description with reference to the accompanying drawings, in which:

[0021] Figure 1 A 5G network according to an embodiment disclosed herein is shown;

[0022] Figure 2 illustrates intent-driven deployment of communication services in the network edge of a 5G network according to embodiments disclosed herein; and

[0023] Figure 3 Deployment of communication services in the network edge of a 5G network according to an embodiment disclosed herein is shown. DETAILED DESCRIPTION

[0024] The example embodiments herein and their various features and advantageous details are explained more fully with reference to the non-limiting embodiments shown in the accompanying drawings and described in detail in the following description. Descriptions of known components and processing techniques are omitted to avoid unnecessarily obscuring the embodiments herein. The description herein is intended only to facilitate an understanding of the implementation of the example embodiments herein and to further enable those skilled in the art to practice the example embodiments herein. Therefore, the present disclosure should not be interpreted as limiting the scope of the example embodiments herein.

[0025] The embodiments herein enable runtime deployment and management of (multiple) communication service instances at the 3GPP network edge of a 5G network. Figures 1 to 3 , where like reference characters consistently denote corresponding features throughout the drawings) illustrates example embodiments.

[0026] Figure 1 A 5G network 100 is shown according to embodiments disclosed herein.

[0027] One of the key features of the 5G network 100 is network slicing. A network slice is a logical network that provides specific network capabilities and network characteristics. According to TS23.501, the 5G network 100 can provide optimized support for a variety of different communication services, different traffic loads, and different end-user groups. For example, communication services using network slicing include vehicle-to-everything (V2X) services, 5G seamless eMBB services with FMC, and massive IoT connections.

[0028] The 5G network 100 includes at least one user equipment (UE) 102. The at least one UE 102 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless communication device, a handheld device, a laptop, a cordless phone, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a sensor, an implanted device, a wearable device (such as a smart watch, smart clothing, smart glasses, smart wristbands, smart jewelry, etc.), an Internet of Things (IoT) device, an entertainment device, a vehicle component, a smart meter, a global positioning system device, or any other suitable device configured to communicate via at least one of a wireless or wired medium. The 5G network also includes an access network, an edge network 108, a service provider 106, and a core network 116. The access network includes at least one access point. The access point may be, but is not limited to, a base station, such as a gNodeB (gNB) 104. The edge network 108 includes at least one edge application 110, an edge management system 112, and a user plane function (UPF) 114.

[0029] The core network 116 includes a network management system 118 and a 5G core network function (NF) 120, each of which is coupled to each other. A network slice management function (NSMF) is part of the network management system (NMS) 118. The network slice management function (NSMF) is responsible for managing (multiple) network slices for communication service instances (CSIs). For example, a wireless node may provide connectivity for or to a network (e.g., a wide area network such as the Internet 122 or a cellular network) via a wired or wireless communication link.

[0030] The access network includes at least one functional element that enables communication between the operator 106 and the UE 102. The core network 116 includes at least one functional element that enables communication between operators 106 or between UEs 102. In addition, the access network may include one or more of a next generation radio access network (NG-RAN) and a non-3GPP access network (AN) connected to the core network 116.

[0031] The edge network 108 is located at the periphery of the complete centralized network including the access network and the core network 116. The edge network 108 includes at least one edge application 110, an edge management system 112, and a user plane function (UPF) 114. The at least one edge application 110 may include, for example, but not limited to, a video streaming application. The UPF 114 represents the data plane evolution of the control and user plane separation (CUPS) strategy. The edge management system 112 is responsible for the overall management of the edge network 108.

[0032] Edge computing enables operator and third-party services to be hosted close to the access point of the attached UE to enable efficient service delivery with reduced end-to-end latency and load on the transport network.

[0033] According to TS28.530, a communication service provider (CSP) 106 may provide communication services to a communication service consumer (CSC) 102. Communication services may include business-to-consumer (B2C) services, business-to-business (B2B) services, business-to-home (B2H) services, and business-to-business-to-everything (B2B2X) services. B2C services include mobile web browsing, 5G voice, rich communication services, and the like. B2B services include Internet access, LAN interconnection, and the like. B2H services include Internet access, MBMS, VOIP, VPN, and the like. B2B2X services include international roaming, RAN sharing, and the like. According to the embodiments described herein, various communication services, such as video streaming services, are pre-configured by the network management system 118 so that they are available in the edge network 108, rather than in the core network 116. To facilitate access to the Internet, the network management system 118 moves the UPF 114 to the edge network.

[0034] According to the embodiments described herein, UE 102 can utilize any communication service via edge network 108 located between access point 104 and core network 116, thereby facilitating user easy access to communication services. In other words, the request for communication service is processed by edge network 108 which is closer to UE 102 than core network 116.

[0035] According to TS28.530 and TS28.531, operators can use one or more network slices to provide communication services to users. A network slice is a logical network that provides specific network capabilities and network characteristics. A network slice instance (NSI) can support multiple communication service instances (CSIs). According to TS23.501, an NSI is a collection of network function instances and required resources that constitute a deployed network slice. The architecture of the 5G network 100 can separate the user plane (UP) function 114 from the control plane (CP) function, allowing independent scalability, evolution, and flexibility deployment, for example, in a centralized location or a distributed remote location.

[0036] At least one UE 102 may be interchangeably referred to throughout as a communication service consumer (CSC) 102. A service provider 106 may be interchangeably referred to throughout as a communication service producer and a network operator.

[0037] The 5G network 100 may be configured to deploy and manage (multiple) communication service instances at the edge of the network 100. A communication service consumer (CSC) 102 may send a request to create a communication service to a communication service producer (CSP) 106. CSC 102 includes a processor (not shown), a memory (not shown), a communication interface (not shown), and a display (not shown). The request includes multiple parameters, such as a service type parameter, a service requirement parameter, a service availability parameter, and edge identification information. The request may be in the form of a transport protocol request, such as, but not limited to, an HTTP request. The request may also be an intent-based service request. In the case of an intent-based service request, the UE may transmit an intent to the network operator. The intent describes the consumer's intent to deploy a communication service at the edge of the 5G network 100. TS23.501 defines three types of slices / service types - enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), and massive Internet of Things (MIoT). According to TS128.530, the eMBB service type is intended to support high data rates and high traffic density. The URLLC service type is intended to support requirements associated with high reliability and low latency scenarios. The mIoT service type is designed to efficiently and economically support a large number of high-density IoT devices.

[0038] In addition, an embodiment defines an additional value of service type as GEN, which will be the default service type if the CSC 102 does not provide the service type. The parameter "service requirement" provides service requirements, such as the number of concurrent users and the number of concurrent sessions. The number of concurrent users defines the service requirement based on the total number of users that the service should be able to support concurrently, which can be provided as an integer. The number of concurrent sessions defines the service requirement based on the total number of concurrent sessions that the service should be able to support, which can be provided as an integer. Service availability This parameter defines the availability of the service. For example, it can define time bound availability for the service. This helps to achieve the target availability of the service at a specific point in time or a specific day of the week, or a combination thereof.

[0039] Another important parameter is edge identification information. A service provider can have edge networks deployed in multiple locations. It is critical to identify the target edge network where the communication service needs to be deployed. The edge identification information can contain edge ID or geolocation. The parameter edgeID will be the unique ID of the edge network that will be provided in the request. The parameter geolocation will be in the form of a single latitude and longitude or TAI.

[0040] CSP 106 can identify and select a matching service profile available in the service catalog. CSP 106 can select a profile based on the requested service type and the requested service requirements. For example, CSC 102 can request video streaming. CSP 106 can select a profile available at the timestamp provided in the request from CSC 102. CSP 106 can identify the edge network 108 to be used based on the information provided in the request. CSP 106 can convert the service requirements into resource-oriented requirements and send the request to the Network Slice Management Function (NSMF) in NMS 118 to allocate the required resources (refer to Section 7.2 of TS 28.531).

[0041] The network slice management function (NSMF) may identify appropriate resources, such as a network slice instance (NSI), to be assigned to the communication service. The NSMF may allocate the resources to be assigned to the communication service. The NSMF may allocate a resource response, i.e., the NSI and its constituent network slice subnet instances (NSSIs), to the CSP 106. The NSMF may indicate that the NSI / NSSI is successfully allocated to the CSP 106.

[0042] Figure 2 Intent driven deployment of communication services in the network edge of a 5G network according to an embodiment disclosed herein is shown. In step 210, an intent driven management service (IDMS) service consumer 202 passes an intent to an IDMS producer 204. The intent describes the consumer's intent to deploy communication services at the edge of the 5G network 100. The format of the intent is depicted in Table 1.

[0043] Table 1

[0044]

[0045] Upon receiving the CSI intent at the edge, the IDMS producer 204 performs the following management tasks. In step 212, the IDMS producer 204 identifies and selects a matching service profile available in the service catalog 203. The network management system 118 configures the service catalog during service creation. The IDMS producer 204 can access the service catalog. The service catalog includes all available services, the duration of the availability of the service, etc. The IDMS producer 204 can be configured to find a matching service from the service catalog.

[0046] The IDMS producer 204 may select a profile that supports the URLLC service type. The IDMS producer 304 may select an available profile based on the service availability requirements provided in the request from the IDMS consumer 302. TS23.501 defines three types of slices / service types (eMBB, URLLC, MIoT), and the service type parameter may have any of three defined values, namely eMBB, URLLC, or MIoT. According to TS28.530, the eMBB service type is intended to support high data rates and high traffic density. The URLLC service type is intended to support requirements associated with high reliability and low latency scenarios. The mIoT service type is intended to efficiently and economically support a large number of high-density IoT devices.

[0047] The parameter "Service Requirements" provides service requirements, such as the number of concurrent users and the number of concurrent sessions. The number of concurrent users defines the service requirements in terms of the total number of users the service should be able to support concurrently, which may be provided as an integer. The number of concurrent sessions defines the service requirements in terms of the total number of concurrent sessions the service should be able to support, which may be provided as an integer.

[0048] Service Availability This parameter defines the availability of the service. For example, it can define a time-limited availability for a service. This helps to achieve the target availability of the service at a specific point in time or a specific day of the week or a combination thereof. The service availability parameter is provided in the request sent by the IDMS consumer 302 in the form of a timestamp. The timestamp indicates that the specific service requested by the IDMS consumer 302 can be made available by the IDMS producer 304 during the time period shown below. The timestamp can be in the form of, but not limited to, yyyy-MM-dd or HH:mm:ss. The timestamp can be defined as follows: Allowed values: <from>{<timestamp>}–<to>{<timestamp>}.

[0049] Another important parameter is edge identification information. A service provider may have edge networks deployed in multiple locations. It is critical to identify the target edge network where the communication service needs to be deployed. The edge identification information may contain an edge ID or a geographic location. The parameter edge ID will be a unique ID of the edge network that will be provided in the request. The IDMS service consumer 202 may obtain this ID and the geographic area mapping in advance when signing a contract with the service provider or through different offline / online methods. The parameter geographic location will be in the form of a single latitude and longitude or TAI.

[0050] In step 214, the IDMS producer 204 identifies the edge network to be used based on the information provided in the request. Thus, the IDMS producer 204 identifies the edge network 108 for the service requested by the IDMS service consumer 202. The locations of the various edge networks may be stored by a database (not shown) coupled to the IDMS producer 204. In step 216, the IDMS producer 204 converts the service requirements into resource-oriented requirements. In other words, the IDMS producer 204 forms requirements for the underlying network slice instance / network slice subnet instance (NSI / NSSI) to meet the service requirements. In step 218, the IDMS producer 204 sends a request to the NSMF, which is part of the network management system (NMS) 118, to allocate the required resources to be assigned to the communication service (Section 7.2 of TS28.531).

[0051] In step 220, the NSMF identifies appropriate resources to be assigned to the IDMS service, such as a network service instance (NSI). The NSI should be able to support the required service requirements, such as 1 million users. In addition to the required 5GS network functions, such as user plane functions (UPF), the NSI should also include applications that provide server functions for the required services, for example, providing video streaming server functions for ultra-low latency video streaming services. In step 222, the NSMF then allocates the NSI and its constituent NSSIs (according to TS28.531 Section 7.2). In this step, the required configuration and provisioning of the constituent NFs and application server functions will be performed. In step 224, the NSMF indicates the successful allocation of the NSI / NSSI to the IDMS producer 204. In step 226, the IDMS producer 204 indicates to the IDMS service consumer 202 that the CSI is successfully created at the edge.

[0052] The various actions in method 200 may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, the Figure 2 Some of the actions listed in .

[0053] Embodiments herein provide a mechanism to deploy and manage communication service instances at the 3GPP network edge.A communication service consumer will be able to request deployment of a communication service at the 3GPP network edge at a specific location.

[0054] Embodiments herein provide two mechanisms to initiate a request: a) using an intent-based service request and b) using a communication service request.

[0055] Figure 3The deployment of communication services in the network edge of the 5G network 100 according to the embodiments disclosed herein is shown. In step 302, the communication service consumer (CSC) 102 sends a request for communication service creation to the communication service producer (CSP) 106. The request includes a service type parameter, a service requirement parameter, a service availability parameter, and edge identification information. The request can be in the form of a transport protocol request, such as but not limited to an HTTP request. TS23.501 defines three types of slices / service types (eMBB, URLLC, MIoT), and the service type parameter can have any one of three defined values, namely eMBB, URLLC or MIoT. According to TS28.530, the eMBB service type is intended to support high data rates and high traffic density. The URLLC service type is intended to support requirements associated with high reliability and low latency scenarios. The mIoT service type is intended to efficiently and economically support a large number of high-density IoT devices.

[0056] In addition, the embodiment defines an additional value of the service type as GEN, and if the CSC 102 does not provide the service type, GEN will be the default service type. The parameter "service demand" provides service requirements, such as the number of concurrent users and the number of concurrent sessions. The number of concurrent users defines the service requirements according to the total number of users that the service should be able to support concurrently, and the number of concurrent users can be provided as an integer. The number of concurrent sessions defines the service requirements according to the total number of concurrent sessions that the service should be able to support, and the number of concurrent sessions can be provided as an integer. The parameter service availability defines the availability of the service. For example, it can define a time-limited availability for the service. This helps to achieve the target availability of the service at a specific point in time or a specific day of the week, or a combination thereof. Another important parameter is edge identification information. A service provider may have edge networks deployed in multiple locations. It is critical to identify the target edge network where the communication service needs to be deployed. The edge identification information may contain an edge ID or a geographic location. The parameter edge ID will be a unique ID of the edge network that will be provided in the request. CSC102 can obtain the ID and geographic area mapping in advance when signing a contract with the service provider or through different offline / online methods. The parameter geographic location will take the form of a single longitude and latitude or TAI.

[0057] In step 304, when CSC 102 sends a request for communication service creation to CSP 106, CSP 106 identifies and selects a matching service profile available in service catalog 303. Network management system 118 configures service catalog 303 during service creation. CSP 106 can be configured to access service catalog 303. Service catalog 303 includes all available services, duration of service availability, etc. Available services can be, for example, but not limited to, video streaming services. CSP 106 selects a profile based on the requested service type and the requested service requirements. In addition to considering the requested service type and the requested service requirements, CSP 106 selects a profile based on a service availability parameter. The service availability parameter is provided in the request sent by CSC 102 in the form of a timestamp. The timestamp can be defined as follows: Allowed values: <from> {<timestamp>}–<to> {<timestamp>}. The timestamp indicates that the specific service requested by CSC 102 can be made available by CSP 106 through the allowed values ​​during the time period as shown above. The timestamp format can be, but is not limited to, yyyy-MM-dd and HH:mm:ss.

[0058] In step 306, the CSP 106 identifies the edge network 108 to be used based on the information provided in the request. Thus, the CSP 106 identifies the edge network 108 for the service requested by the CSC 102. The locations of the various edge networks may be stored by a database (not shown) coupled to the CSP 106. In step 308, the CSP 106 converts the service requirements into resource-oriented requirements. In other words, the CSP 106 forms requirements for the underlying network slice instance / network slice subnet instance (NSI / NSSI) to meet the service requirements. In step 310, the CSP 106 sends a request to the Network Slice Management Function (NSMF), which is part of the Network Management System 118, to allocate the required resources to be assigned to the communication service (Section 7.2 of TS 28.531).

[0059] In step 312, the NSMF identifies appropriate resources to be assigned to the communication service, such as a network slice instance (NSI). The NSI can support the required service requirements, such as 1 million users. In addition to the required 5GS network functions, such as the user plane function (UPF) 114, the NSI should also contain applications that provide server functions for the required services, such as providing video streaming server functions for ultra-low latency video streaming services.

[0060] In steps 314 and 316, the NSMF allocates the NSI and its constituent NSSIs (according to TS28.531 Section 7.2). In this step, the required configuration and provisioning of the constituent NF and application server functions will be performed. The NSMF indicates the successful allocation of the NSI / NSSI to the CSP 106. In step 318, the CSP 106 indicates the successful creation of the CSI at the edge network 108.

[0061] The various actions in method 300 may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, the Figure 3 Some of the actions listed in .

[0062] Embodiments herein provide mechanisms for deploying and managing communication service instances at the edge of a 3GPP network. Communication service consumers will be able to request that communication services be deployed at the edge of a 3GPP network at a specific location. Embodiments herein provide two mechanisms to initiate requests: a) using a communication service request; b) using an intent-based service request.

[0063] The embodiments disclosed herein may be implemented by at least one software program running on at least one hardware device and performing network management functions to control the elements. Figure 1 The elements shown may be at least one of a hardware device, or a combination of a hardware device and a software module.

[0064] The above description of the specific embodiments will fully reveal the general nature of the embodiments herein so that others can easily modify and / or adapt these specific embodiments to various applications by applying current knowledge without departing from the general concept, and therefore, such adaptations and modifications should and are intended to be understood within the meaning and scope of the equivalents of the disclosed embodiments. It should be understood that the terms or terms used herein are only for description and not limitation. Therefore, although the embodiments of this article have been described according to the embodiments, those skilled in the art will recognize that the embodiments of this article can be implemented by modification within the spirit and scope of the embodiments described herein.

Claims

1. A method performed by an intent-driven management service (IDMS) producer in a wireless communication system, the method comprising: receiving, from an IDMS consumer, an intent for delivering a service from a network edge of a wireless communication system, wherein the intent includes a service type, service availability including a service start timestamp and a service end timestamp, service requirements, and identification information of the edge; as well as Based on intent recognition service, Among them, service types include ultra-reliable and low-latency communications URLLC or enhanced mobile broadband eMBB, The edge identification information includes at least one of an ID and a position, and Wherein, in the case where service deployment is required at a specific edge of the network, the identification information of the edge includes an ID.

2. The method according to claim 1, wherein: The service requirements include at least one number of concurrent users and at least one number of concurrent sessions, wherein the ID of a particular edge of the network is known to the IDMS consumer, and Wherein, when the service deployment is at a specific location, the identification information of the edge includes the location.

3. An intent-driven management service IDMS producer in a wireless communication system, the IDMS producer comprising: Transceiver; and A controller is coupled to the transceiver and is configured to: receiving from an IDMS consumer an intent to deliver a service from a network edge of a wireless communication system, wherein the intent includes a service type, service availability including a service start timestamp and a service end timestamp, service requirements, and identification information of the edge, and Based on intent recognition service, Among them, service types include ultra-reliable and low-latency communications URLLC or enhanced mobile broadband eMBB, The edge identification information includes at least one of an ID and a position, and Wherein, in the case where service deployment is required at a specific edge of the network, the identification information of the edge includes an ID.

4. The IDMS producer according to claim 3, wherein: The service requirements include at least one number of concurrent users and at least one number of concurrent sessions, wherein the ID of a particular edge of the network is known to the IDMS consumer, and Wherein, when the service deployment is at a specific location, the identification information of the edge includes the location.

Images