CN113824589A - RESTful-based slice capability open interface mapping method - Google Patents
RESTful-based slice capability open interface mapping method Download PDFInfo
- Publication number
- CN113824589A CN113824589A CN202111102805.3A CN202111102805A CN113824589A CN 113824589 A CN113824589 A CN 113824589A CN 202111102805 A CN202111102805 A CN 202111102805A CN 113824589 A CN113824589 A CN 113824589A
- Authority
- CN
- China
- Prior art keywords
- slice
- function
- capability
- slicing
- open
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a RESTful-based slicing capability open interface mapping method, which comprises the following three steps: s1, summarizing and sorting the slicing capability, and classifying the slicing capability into 4 slicing open function categories and 4 basic function categories; s2: analyzing slicing capability, and extracting keywords from the slicing capability to serve as message bodies of request information and response information; s3: generating a REST style slicing capability interface; the RESTful-based slice capability open interface mapping method can convert the existing and newly designed slice management and configuration capabilities into the REST style-based capability open interface, provides a RESTful standardized slice open capability interface mapping strategy, can be applied to 5G slice capability opening, and effectively solves the problems that the API (application programming interface) mapping strategy of the current slice open management and control capability is not mature enough and the slice capability open interface mapping process is not standardized enough in the prior art.
Description
Technical Field
The invention relates to the field of 5G network slicing oriented to power services, in particular to a slicing capability open interface mapping method based on RESTful.
Background
Network slicing is defined as multiple virtual networks operating as independent services on a general physical infrastructure, a 5G network slicing technology can manage and arrange network resources according to elements such as applications, scenes, and requirements, and tailor and customize network functions, the 5G network capability openness refers to the capability of mutual openness between a 5G network and a third party application, and the capability of the 5G network openness for the third party application generally includes: the network/terminal monitoring capability, the basic service capability and the control capability, otherwise, the third-party application can also open the terminal capability, the mobility information, the service related information and the like to the 5G network, so that an operator can optimize and manage the network according to the service requirement.
Under the 5G network architecture, capability opening is combined with terminal management, flow management, network slicing and MEC (Mobile Edge Computing) technology, so that it is possible for an operator to consider both third-party services and security requirements during network planning and management, an open 5G slicing function is realized, the operator packs and integrates various capabilities in the own network management system to form independent slicing query management functions, the operator opens the functions to power users, the power users can directly manage the network slicing used by the power users to a certain extent, and the operation efficiency and the reaction speed of services are improved.
The design of the capability open interface is a key of a 5G network slice control capability open platform in the power industry, and the 5G network slice control capability open platform can also be regarded as a network application program, the network application program is divided into a front end and a rear end, and the front end equipment is currently layered endlessly (such as a mobile phone, a tablet, a desktop computer and the like), so that a unified mechanism is required to be provided to facilitate communication between different front end equipment and the rear end, which leads to the popularity of an API framework and even the design idea of API First, and the RESTful API is the API design theory of a relatively mature set of Internet application programs at present.
REST (Representational State transition or Representational State transition) was proposed in 2000, and based on standards and protocols such as HTTP (Hyper Text Transfer Protocol), URI (Uniform Resource Identifier), XML (Extensible Markup Language), JSON (JavaScript Object Notation), JSON Object profile), and the like, lightweight, cross-platform, and cross-Language architectural design is supported, REST is a new architectural style of Web services, and the main principles of RESTful architecture include: 1. there is one resource identifier for all resources on the network, 2. the operation on the resource does not change the identifier, 3. the same resource has multiple manifestations (xml, json), 4. all operations are Stateless (Stateless).
However, the API interface mapping policy of the current slicing open control capability is not mature enough, and the slicing open interface mapping process is not standardized enough.
The present invention therefore provides a new solution to this problem.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide a RESTful-based slice capability open interface mapping method, and effectively solves the problems that the API (application programming interface) mapping strategy of the current slice open management and control capability is not mature enough and the slice capability open interface mapping process is not standard enough in the prior art.
The technical scheme for solving the problem is that the RESTful-based slicing capability open interface mapping method comprises three steps:
s1, summarizing and sorting the slicing capability, and classifying the slicing capability into 4 slicing open function categories and 4 basic function categories;
s2: analyzing slicing capability, and extracting keywords from the slicing capability to serve as message bodies of request information and response information;
s3: generating a REST style slicing capability interface;
the REST is an abbreviation of Representational State Transfer and represents group design principles and constraint conditions, and RESTful refers to realization of meeting the principles and constraint conditions;
the step S1: the slicing capability is summarized and sorted, and classified into 4 slice open function categories and 4 basic function categories, which comprise the following contents:
the slice open function category is a specific category which takes functions as guidance, and the basic function category is a basic function obtained by inducing and sorting slice capacity;
the 4 slice open function categories are slice operation monitoring, slice fault management, slice function configuration and slice instance configuration respectively;
the 4 slice open function categories specifically include the following functions:
the slice operation monitoring comprises slice real-time operation state query and slice historical operation state query; the slice fault management comprises real-time fault information alarm and historical fault information query; the slice function configuration comprises the logic functions of self-defining slice types according to requirements, setting the number of terminals accessed into network slices and adding new network slices; the slice instance configuration comprises creation of a slice instance, configuration management of the slice instance, information inquiry of the slice instance and revocation of the slice instance;
the 4 basic functional categories are specifically: add, delete, modify, and query; classifying the functions in the slice open function category into 4 basic function categories, wherein the basic function categories are increased by: the logic function of newly-added network slices and the creation of slice instances, and the deletion in classification in the basic function comprises the following steps: revocation of slice instances, modification in the underlying functional classification includes: customizing the slice type according to the requirement, setting the number of terminals accessed to the network slice, and managing the configuration of the slice example, wherein the query in the basic function classification comprises the following steps: the method comprises the following steps of slice real-time operation state query, slice historical operation state query, fault information real-time alarm, fault information historical query and slice example information query;
the step S2: analyzing slicing capability, and extracting keywords from the slicing capability to be used as message bodies of request information and response information, wherein the specific contents are as follows:
extracting keywords in the function name according to the basic function classification, obtaining a message body of interface request information and response information, and selecting a corresponding data type and a corresponding data format, wherein the keywords in the function name can be divided into two categories, one category is a requirement provided by a power user, the keywords are used as the message body of the request information, the other category is a result which the power user wants to obtain, and the keywords are used as the message body of the response information;
the 4 basic functional categories, which are added, deleted, modified and queried respectively, list the message bodies and the formats thereof present:
the message body for adding the function includes a message body for adding request information of the function and a message body for adding response information of the function, and specifically includes: the power consumer puts forward a request for adding a certain resource to an operator, wherein an object of 'adding' can be a slice example, access equipment or a certain function of the slice, the operator establishes a slice example or adds a function for a certain slice through a network management system of the operator according to the requirement of the power consumer, and returns the identifier of the related slice to the power consumer, the data type can be selected from Double, String and Boolean types according to specific conditions, and the data format uniformly selects JSON;
the Double represents a Double-precision floating point number, the String represents a character String type and is also a reference type, the Boolean represents a Boolean type, and the variable is stored in a numerical value form of 8 bits and 1 byte;
the deleting function is specifically as follows: the deleting function refers to a function capable of removing back-end resources, the object of the deleting function can also be a slice instance, an access device or a certain function of the slice, and the response information of the deleting function only needs to include a prompt of successful deleting without giving a message body selection;
the modification function is specifically: the modification function can modify the slice and the access equipment and can also modify the open functions of each slice, and after the power consumer provides a modification request, an operator performs modification operation according to the request and returns the modified result to the power consumer;
the query function is specifically: the query function refers to the capability of the power consumer to acquire data from an operator, and the object of the query function can be data of a slice or an access device;
the step S3: the generating the REST style slicing capability interface specifically comprises the following steps:
the slicing capability open interface adopts a RESTful mode, and the core idea of RESTful is that a data operation instruction sent by a client is a verb and object structure, wherein the verb refers to five HTTP methods and corresponds to CRUD operation, and a GET method Read is selected on selection of the HTTP methods and refers to operation of taking out resources from a server;
the HTTP is an abbreviation of HyperText Transfer Protocol and represents a HyperText Transfer Protocol;
the HTTP has 5 methods corresponding to CRUD operation:
(1) the GET method comprises the following steps: reading operation read;
(2) the POST method comprises the following steps: creating operation Create;
(3) the PUT method comprises the following steps: updating operation Update;
(4) the PATCH method comprises the following steps: update operation Update, which means partial Update;
(5) the DELETE method: delete operation Delete;
the definition of the slice capability open interface URL is divided according to the slice open function categories, a URL domain is divided for each slice open function category under the root directory of the resource, URL subdomains are divided according to specific slice functions in the URL domain, when a newly created slice function is met, different capability domains are divided after classification, and a URL subdomain is newly created to correspond to the capability domains;
the URL is an abbreviation for Universal Resource Locator and represents a uniform Resource Locator.
The invention has the following beneficial effects:
the RESTful-based slice capability open interface mapping method provided by the invention can design an efficient and available REST-style API (application programming interface) for the existing slice open capability, can automatically provide an REST-style-based interface for the newly designed slice open capability, can convert the existing and newly designed slice management and configuration capabilities into a REST-style-based capability open interface, provides a RESTful standardized slice open capability interface mapping strategy, can be applied to 5G slice capability opening, and effectively solves the problems that the API mapping strategy of the current slice open management and control capability is not mature and the slice capability open interface mapping process is not standard in the prior art.
Drawings
FIG. 1 is an overall flow diagram of the present invention.
Detailed Description
The foregoing and other technical and other features and advantages of the invention will be apparent from the following more particular description of the embodiments, as illustrated in the accompanying drawings in which reference is made to FIG. 1. The structural contents mentioned in the following embodiments are all referred to the attached drawings of the specification.
The RESTful-based slice capability open interface mapping method provided by the present invention will be described in detail below by embodiments with reference to the accompanying drawings.
The RESTful-based slice capability open interface mapping method comprises the following three steps:
s1, summarizing and sorting the slicing capability, and classifying the slicing capability into 4 slicing open function categories and 4 basic function categories;
s2: analyzing slicing capability, and extracting keywords from the slicing capability to serve as message bodies of request information and response information;
s3: generating a REST style slicing capability interface;
the REST is an abbreviation of Representational State Transfer, and represents group design principles and constraints, and RESTful refers to implementation that satisfies the principles and constraints.
And step S1, summarizing and sorting the slicing capability, and classifying the slicing capability into 4 slice open function categories and 4 basic function categories, wherein the slicing capability specifically comprises the following contents:
the slice open function category is a concrete category taking functions as guidance, and the basic function category is a basic function obtained by inducing and sorting slice capacity, wherein the former is more important in classifying slice capacity in practical application, and the latter is simpler and more abstract than the former;
the 4 slice open function categories are slice operation monitoring, slice fault management, slice function configuration and slice instance configuration respectively;
the slice operation monitoring specifically comprises: the operator collects the 5G slice operation state information and sends the information to the power consumer in time, the power consumer can read and analyze the data information, and the strategy is changed when the slice fails so as to ensure the normal operation of the service;
the slice fault management specifically comprises: an operator collects the collected slice operation monitoring information, analyzes abnormal data, obtains fault information, timely pushes the fault information to a power consumer, and stores the collected fault information in a list form to meet the future query requirements of the power consumer;
the slicing function configuration specifically comprises the following steps: the method comprises the following steps that an electric power enterprise can participate in top-level design and life cycle management of electric power service network slices, on the basis of three types of eMBBs (enhanced mobile broadband), uRLLCs (high reliability low delay communication) and mMTC (large-scale machine communication), the electric power enterprise can expand self-defined slice types as required to distinguish different partition services or services with special management requirements, so that the mapping relation between the electric power service and the network slice types is optimized, the electric power enterprise can set different terminal access numbers according to different types of network slices, the electric power enterprise can define the logic function of each network slice, and the slice logic function is optimized according to the function requirements of the different types of electric power services;
the slice example configuration specifically comprises: the power enterprise can independently arrange a new network slice example according to the business requirement, perform certain configuration management and information query operation on the network slice example, and can cancel the corresponding slice example when the network slice is not needed due to the reason;
the slicing function configuration and the slicing example configuration are different in that the slicing function configuration focuses on overall setting and changing of the slicing function, and the slicing example configuration focuses on increasing, deleting, changing and checking of specific slicing examples;
the 4 slice open function categories and functional representations are shown in table 1:
table 1 slice open function categories and function examples
The invention divides the functions in the slice open function category into 4 basic functions: add, delete, modify, and query, abstractly classified into these 4 categories by analyzing the example of the slicing function presented in table 1, where an addition in the base function category includes: the logic function of newly-added network slices and the creation of slice instances, and the deletion in classification in the basic function comprises the following steps: revocation of slice instances, modification in the underlying functional classification includes: customizing the slice type according to the requirement, setting the number of terminals accessed to the network slice, and managing the configuration of the slice example, wherein the query in the basic function classification comprises the following steps: the method comprises the steps of slice real-time operation state query, slice historical operation state query, fault information real-time alarm, fault information historical query and slice instance information query.
The step S2: analyzing slicing capability, and extracting keywords from the slicing capability as message bodies of request information and response information, wherein the message bodies specifically comprise the following contents:
based on step S1, extracting keywords in the function name according to the basic function classification, obtaining message bodies of the interface request information and the response information, and selecting corresponding data types and data formats, where the keywords in the function name can be classified into two categories, one is a request from the power consumer, and the other is a result that the power consumer wants to obtain, and the keywords are used as message bodies of the response information;
respectively classifying and listing possible message bodies and formats thereof from the adding, deleting, modifying and inquiring 4 basic functions;
the message body for adding the function comprises a message body for adding request information of the function and a message body for adding response information of the function, and specifically comprises the following contents:
an electric power user puts forward a request for adding a certain resource to an operator, an object of 'adding' can be a slice example, access equipment or a certain function of the slice, the operator establishes a slice example or adds a function for a certain slice through a network management system of the operator according to the requirement of the electric power user, the identifier of the related slice is returned to the electric power user, a message body of request information of the function is shown in a table 2, a message body of response information of the function is shown in a table 3, the data type can select types such as Double-precision floating point, String (character String type, also a reference type) and Boolean (JSa type, variable is stored in 8 bits and numerical value form of 1 byte) according to specific conditions, and the data format uniformly selects ON;
table 2 message body of request information for adding function
Table 3 message body of response information of add function
The deletion function specifically includes the following:
the deleting function refers to a function capable of removing a back-end resource, an object of the deleting function can also be a slice instance, an access device or a certain function of a slice, response information of the deleting function only needs to include a prompt of successful deleting, a message body does not need to be selected, and the message body selection of request information of the deleting function is shown in table 4;
table 4 message body of request information of delete function
The modification function specifically includes the following:
the modification function can modify not only the slice and the access device, but also the open functions of each slice, after the power consumer makes a modification request, the operator performs modification operation according to the request and returns the modified result to the power consumer, the message body selection of the request information of the modification function is shown in table 5, and the message body selection of the response information of the modification function is shown in table 6;
table 5 message body of request information for modify function
| Message body | Optional/optional | Data type | Data format | Description of the invention |
| KEY | Must choose | string | JSON | Capability opening key |
| ModSlice-id | Must choose | double | JSON | Serial number of slice to be modified |
| ModBandwidth | Optionally | double | JSON | Bandwidth modification requirements |
| ModDelay | Optionally | double | JSON | Delay modification requirement |
| Devices | Optionally | double | JSON | Access device support number modification requirements |
| Function | Optionally | string | JSON | Slice open function requiring modification |
| ModDevice-id | Optionally | double | JSON | Access equipment serial number to be modified |
Table 6 message body of response information of the modify function
The query function specifically includes the following:
the query function refers to the capability of the power consumer to obtain data from the operator, the object of the query function may be data of slices or access devices, etc., the message body of the request information of the query function is shown in table 7, and the message body of the response information of the query function is shown in table 8.
Table 7 message body of request information of query function
| Message body | Optional/optional | Data type | Data format | Description of the invention |
| KEY | Must choose | string | JSON | Capability opening key |
| Slice-id | Must choose | string | JSON | Serial number of slice |
| QuiriedSlice-id | Must choose | string | JSON | Serial number of slice to be inquired |
| QuiriedDevice-id | Optionally | double | JSON | Serial number of equipment to be inquired |
| Time | Optionally | string | JSON | Time of data acquisition |
Table 8 message body of response information of the query function
The step S3: the specific content of the slicing capability interface for generating the REST style includes the following contents:
the slice capability open interface is realized by adopting a RESTful mode, wherein REST (representational State Transfer)) refers to group design principles and constraint conditions, RESTful refers to realization of meeting the principles and the constraint conditions, and the core idea of RESTful is that data operation instructions sent by a client are all in a structure of 'verb + object', and verbs are generally five HTTP (HyperText Transfer Protocol) methods, corresponding to CRUD operation, in the slicing capability opening, all the opening functions of the power consumer are to take out one or more pieces of slicing information (the information can be the operation data of the slicing and also the serial number of the newly-built slicing) from the operator, the power consumer cannot directly perform operations such as adding, modifying or deleting on the slicing network itself, therefore, in the selection of the HTTP method, the present application selects the GET method (Read) in its entirety, which refers to an operation of fetching a resource (one or more items) from a server;
HTTP has 5 methods corresponding to CRUD operation:
(1) the GET method comprises the following steps: a read operation (read);
(2) the POST method comprises the following steps: new operation (Create);
(3) the PUT method comprises the following steps: update operation (Update);
(4) the PATCH method comprises the following steps: update operation (Update), typically referred to as partial Update;
(5) the DELETE method: delete operation (Delete);
the GET method corresponds to a Read operation, which refers to an operation of fetching a resource (one or more items) from a server; the method comprises the following steps that the definition of a slice capability open interface URL (uniform Resource Locator) is divided according to slice open function categories, a URL domain is divided for each slice open function category under a root directory of resources, URL subdomains can be divided in the URL domain according to specific slice functions to serve as a way for acquiring capability resources, when a newly created slice function is met, different capability domains can be classified and a URL subdomain is newly created to correspond to each other; the capability open interface URL definition rule is shown in table 9; the capability open interface HTTP response body definition is shown in table 10.
Table 9 capability open interface URL definition rules
Table 10 capability open interface HTTP response body definition
| Field(s) | Description of the invention |
| responseCode | Return code indicating request status |
| responseMsg | Return message detailing request status |
| res | The message body content and the data format are JSON |
TABLE 11 responseCode optional values
The following describes the mapping process of the slicing capability open interface by specific embodiments:
the mapping process of the slice capability open interface is described by taking historical fault information query as an example:
firstly, fault information historical queries can be divided into 'slice fault management' in a slice open function category and 'queries' in a basic function category, so that a URL domain where the fault information historical queries are located can be determined to be/Malfunction/, and in addition, as the focuses of the fault information historical queries are on 'historical information', the URL sub-domain of the fault information historical queries is set to be/Malfunction/History/;
next, the power consumer applies the connotation of the text description "history query of fault Information" function to obtain fault Information of a specific history Time point, extracts keywords to respectively obtain keywords such as "history" and "fault Information", and after analysis, selects "KEY", "Time" and "quick slice-id" as message bodies of request Information from message bodies corresponding to the "query" function classified by basic functions, the KEY represents a capability opening KEY, the quick slice-id represents a slice number to be queried, the Time represents data acquisition Time, namely a fault Information query Time point, and selects "Type" and "Information" as message bodies of response Information, namely fault Type and fault Information, respectively;
finally, according to the RESTful style, a capacity open interface of the fault information history query function is completed, the fault information history query request information is shown in a table 12, and the fault information history query response information is shown in a table 13;
table 12 historical query request information for fault information
Table 13 fault information historical query response information
The mapping process of the slicing capability open interface is described by taking the creation of a slicing instance as an example:
firstly, the Creation of a slice instance can be divided into 'slice instance configuration' in a slice open function category and 'increase' in a basic function category, the URL domain where the slice instance is located is determined to be/NS-Case/, and in addition, the URL sub-domain is set to be/NS-Case/Creation/, because the focus of the Creation is on the 'Creation';
then, extracting keywords, respectively obtaining keywords such as 'slice example', 'creation', and the like, analyzing, selecting 'KEY', 'Bandwidth-max', 'Delay-min' and 'Devices-max' as message bodies of request information from message bodies corresponding to 'add' basic functions, the KEY representing a capability open KEY, the Bandwidth-max representing a maximum Bandwidth requirement, the Delay-min representing a minimum time Delay requirement, the Devices-max representing a maximum terminal number requirement, and selecting 'AddedSlice-ID' as the message body of response information, representing the ID serial number of a newly-built slice example;
finally, according to the style of RESTful, a capability open interface for completing the creation function of the slice instance, the creation request information of the slice instance is shown in table 14, and the creation response information of the slice instance is shown in table 15;
table 14 creation request information for slice instances
Table 15 creation response information for slice instance
It should be noted that the RESTful-based slice capability open interface mapping method provided by the present invention is independent of the management capability of the operator, and does not directly control the creation, modification, and deletion of the slice, and the direct operation of the slice belongs to the capability category of the operator, and the power enterprise only obtains the result after the operation of the operator.
In particular use, the method comprises three steps, as described with reference to the above figures:
s1, summarizing and sorting the slicing capability, and classifying the slicing capability into 4 slicing open function categories and 4 basic function categories;
s2: analyzing slicing capability, and extracting keywords from the slicing capability to serve as message bodies of request information and response information;
s3: generating a REST style slicing capability interface;
the RESTful-based slice capability open interface mapping method provided by the invention can design an efficient and available REST-style API (application programming interface) for the existing slice open capability, can automatically provide an REST-style-based interface for the newly designed slice open capability, can convert the existing and newly designed slice management and configuration capabilities into a REST-style-based capability open interface, provides a RESTful standardized slice open capability interface mapping strategy, can be applied to 5G slice capability opening, and effectively solves the problems that the API mapping strategy of the current slice open management and control capability is not mature and the slice capability open interface mapping process is not standard in the prior art.
Claims (4)
1. RESTful-based slice capability open interface mapping method, which is characterized by comprising three steps:
s1, summarizing and sorting the slicing capability, and classifying the slicing capability into 4 slicing open function categories and 4 basic function categories;
s2: analyzing slicing capability, and extracting keywords from the slicing capability to serve as message bodies of request information and response information;
s3: generating a REST style slicing capability interface;
the REST is an abbreviation of Representational State Transfer, and represents group design principles and constraints, and RESTful refers to implementation that satisfies the principles and constraints.
2. The RESTful-based slice capability open interface mapping method of claim 1, wherein the step S1: the slicing capability is summarized and sorted, and classified into 4 slice open function categories and 4 basic function categories, which comprise the following contents:
the slice open function category is a specific category which takes functions as guidance, and the basic function category is a basic function obtained by inducing and sorting slice capacity;
the 4 slice open function categories are slice operation monitoring, slice fault management, slice function configuration and slice instance configuration respectively;
the 4 slice open function categories specifically include the following functions:
the slice operation monitoring comprises slice real-time operation state query and slice historical operation state query; the slice fault management comprises real-time fault information alarm and historical fault information query; the slice function configuration comprises the logic functions of self-defining slice types according to requirements, setting the number of terminals accessed into network slices and adding new network slices; the slice instance configuration comprises creation of a slice instance, configuration management of the slice instance, information inquiry of the slice instance and revocation of the slice instance;
the 4 basic functional categories are specifically: add, delete, modify, and query; classifying the functions in the slice open function category into 4 basic function categories, wherein the basic function categories are increased by: the logic function of newly-added network slices and the creation of slice instances, and the deletion in classification in the basic function comprises the following steps: revocation of slice instances, modification in the underlying functional classification includes: customizing the slice type according to the requirement, setting the number of terminals accessed to the network slice, and managing the configuration of the slice example, wherein the query in the basic function classification comprises the following steps: the method comprises the steps of slice real-time operation state query, slice historical operation state query, fault information real-time alarm, fault information historical query and slice instance information query.
3. The RESTful-based slice capability open interface mapping method of claim 1, wherein the step S2: analyzing slicing capability, and extracting keywords from the slicing capability to be used as message bodies of request information and response information, wherein the specific contents are as follows:
extracting keywords in the function name according to the basic function classification, obtaining a message body of interface request information and response information, and selecting a corresponding data type and a corresponding data format, wherein the keywords in the function name can be divided into two categories, one category is a requirement provided by a power user, the keywords are used as the message body of the request information, the other category is a result which the power user wants to obtain, and the keywords are used as the message body of the response information;
the 4 basic functional categories, which are added, deleted, modified and queried respectively, list the message bodies and the formats thereof present:
the message body for adding the function includes a message body for adding request information of the function and a message body for adding response information of the function, and specifically includes: the power consumer puts forward a request for adding a certain resource to an operator, wherein an object of 'adding' can be a slice example, access equipment or a certain function of the slice, the operator establishes a slice example or adds a function for a certain slice through a network management system of the operator according to the requirement of the power consumer, and returns the identifier of the related slice to the power consumer, the data type can be selected from Double, String and Boolean types according to specific conditions, and the data format uniformly selects JSON;
the Double represents a Double-precision floating point number, the String represents a character String type and is also a reference type, the Boolean represents a Boolean type, and the variable is stored in a numerical value form of 8 bits and 1 byte;
the deleting function is specifically as follows: the deleting function refers to a function capable of removing back-end resources, the object of the deleting function can also be a slice instance, an access device or a certain function of the slice, and the response information of the deleting function only needs to include a prompt of successful deleting without giving a message body selection;
the modification function is specifically: the modification function can modify the slice and the access equipment and can also modify the open functions of each slice, and after the power consumer provides a modification request, an operator performs modification operation according to the request and returns the modified result to the power consumer;
the query function is specifically: the query function refers to the ability of the power consumer to obtain data from the operator, and the object of the query function may be data of slices or access devices.
4. The RESTful-based slice capability open interface mapping method of claim 1, wherein the step S3: the generating the REST style slicing capability interface specifically comprises the following steps:
the slicing capability open interface adopts a RESTful mode, and the core idea of RESTful is that a data operation instruction sent by a client is a verb and object structure, wherein the verb refers to five HTTP methods and corresponds to CRUD operation, and a GET method Read is selected on selection of the HTTP methods and refers to operation of taking out resources from a server;
the HTTP is an abbreviation of HyperText Transfer Protocol and represents a HyperText Transfer Protocol;
the HTTP has 5 methods corresponding to CRUD operation:
(1) the GET method comprises the following steps: reading operation read;
(2) the POST method comprises the following steps: creating operation Create;
(3) the PUT method comprises the following steps: updating operation Update;
(4) the PATCH method comprises the following steps: update operation Update, which means partial Update;
(5) the DELETE method: delete operation Delete;
the definition of the slice capability open interface URL is divided according to the slice open function categories, a URL domain is divided for each slice open function category under the root directory of the resource, URL subdomains are divided according to specific slice functions in the URL domain, when a newly created slice function is met, different capability domains are divided after classification, and a URL subdomain is newly created to correspond to the capability domains;
the URL is an abbreviation for Universal Resource Locator and represents a uniform Resource Locator.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111102805.3A CN113824589B (en) | 2021-09-18 | 2021-09-18 | RESTful-based slicing capability open interface mapping method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111102805.3A CN113824589B (en) | 2021-09-18 | 2021-09-18 | RESTful-based slicing capability open interface mapping method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113824589A true CN113824589A (en) | 2021-12-21 |
| CN113824589B CN113824589B (en) | 2023-05-16 |
Family
ID=78922696
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111102805.3A Active CN113824589B (en) | 2021-09-18 | 2021-09-18 | RESTful-based slicing capability open interface mapping method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113824589B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108141727A (en) * | 2015-08-03 | 2018-06-08 | 康维达无线有限责任公司 | The mobile core network service exposure of user equipment |
| US20190223055A1 (en) * | 2018-01-12 | 2019-07-18 | Huawei Technologies Co., Ltd. | Network slice provisioning and operation |
| US20190312782A1 (en) * | 2016-12-23 | 2019-10-10 | Huawei Technologies Co., Ltd. | System and method for programming and/or management of core network slices |
| CN110447247A (en) * | 2017-03-20 | 2019-11-12 | 康维达无线有限责任公司 | Service ability at user equipment is open |
| US20200034219A1 (en) * | 2018-07-24 | 2020-01-30 | Cisco Technology, Inc. | System and method for message management across a network |
| US20200382386A1 (en) * | 2017-12-06 | 2020-12-03 | Telefonaktiebolaget Lm Ericsson (Publ) | First node, second node, and methods performed thereby for managing a network slice instance |
| CN112449315A (en) * | 2019-08-27 | 2021-03-05 | 华为技术有限公司 | Network slice management method and related device |
| CN112737813A (en) * | 2020-12-11 | 2021-04-30 | 广东电力通信科技有限公司 | Power business management method and system based on 5G network slice |
| US20210153077A1 (en) * | 2016-02-17 | 2021-05-20 | NEC Laboratories Europe GmbH | System and method for operating a wireless network |
-
2021
- 2021-09-18 CN CN202111102805.3A patent/CN113824589B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108141727A (en) * | 2015-08-03 | 2018-06-08 | 康维达无线有限责任公司 | The mobile core network service exposure of user equipment |
| US20210153077A1 (en) * | 2016-02-17 | 2021-05-20 | NEC Laboratories Europe GmbH | System and method for operating a wireless network |
| US20190312782A1 (en) * | 2016-12-23 | 2019-10-10 | Huawei Technologies Co., Ltd. | System and method for programming and/or management of core network slices |
| CN110447247A (en) * | 2017-03-20 | 2019-11-12 | 康维达无线有限责任公司 | Service ability at user equipment is open |
| US20200382386A1 (en) * | 2017-12-06 | 2020-12-03 | Telefonaktiebolaget Lm Ericsson (Publ) | First node, second node, and methods performed thereby for managing a network slice instance |
| US20190223055A1 (en) * | 2018-01-12 | 2019-07-18 | Huawei Technologies Co., Ltd. | Network slice provisioning and operation |
| US20200034219A1 (en) * | 2018-07-24 | 2020-01-30 | Cisco Technology, Inc. | System and method for message management across a network |
| CN112449315A (en) * | 2019-08-27 | 2021-03-05 | 华为技术有限公司 | Network slice management method and related device |
| CN112737813A (en) * | 2020-12-11 | 2021-04-30 | 广东电力通信科技有限公司 | Power business management method and system based on 5G network slice |
Non-Patent Citations (2)
| Title |
|---|
| SHREYAS CHOLIA等: "NEWT: A RESTful service for building High Performance Computing web applications", 《2010 GATEWAY COMPUTING ENVIRONMENTS WORKSHOP (GCE)》 * |
| 李红祎等: "基于能力开放的5G网络切片管理研究", 《万方数据库》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113824589B (en) | 2023-05-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11768811B1 (en) | Managing user data in a multitenant deployment | |
| US11822512B1 (en) | Graphical user interface for previewing events using a selected field delimiter option | |
| CN105138592B (en) | A kind of daily record data storage and search method based on distributed structure/architecture | |
| US11651012B1 (en) | Coding commands using syntax templates | |
| US10331504B2 (en) | Method and system for extending application programming interfaces | |
| CN110427368A (en) | Data processing method, device, electronic equipment and storage medium | |
| US11615082B1 (en) | Using a data store and message queue to ingest data for a data intake and query system | |
| US11966797B2 (en) | Indexing data at a data intake and query system based on a node capacity threshold | |
| CN103593434A (en) | Application recommendation method and device and server equipment | |
| CN101098248A (en) | Method and system for implementing universal network management based on configuration describing document | |
| CN109359094A (en) | A kind of full link tracing method and device of distributed system journal | |
| US20220245155A1 (en) | Distributed multi-source data processing and publishing platform | |
| US20190363986A1 (en) | Reconstructing message flows based on hash values | |
| CN113157904B (en) | Sensitive word filtering method and system based on DFA algorithm | |
| CN102831179B (en) | web page processing method and device | |
| CN109559121A (en) | Transaction path calls exception analysis method, device, equipment and readable storage medium storing program for executing | |
| CN116974948A (en) | Service system testing method, system, equipment and medium | |
| CN113824589B (en) | RESTful-based slicing capability open interface mapping method | |
| CN110855562A (en) | Internet of things data distribution management method and system, storage medium and management terminal | |
| CN113515715B (en) | Buried point event code generation method, buried point event code processing method and related equipment | |
| CN114756301A (en) | Log processing method, device and system | |
| CN112783842B (en) | Log collection method and device | |
| CN108470047B (en) | Remote platform monitoring system based on Internet of Things | |
| US7155503B2 (en) | Data server | |
| CN115599657B (en) | Software facility abnormity judgment method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |