CN113824589B - RESTful-based slicing capability open interface mapping method - Google Patents
RESTful-based slicing capability open interface mapping method Download PDFInfo
- Publication number
- CN113824589B CN113824589B CN202111102805.3A CN202111102805A CN113824589B CN 113824589 B CN113824589 B CN 113824589B CN 202111102805 A CN202111102805 A CN 202111102805A CN 113824589 B CN113824589 B CN 113824589B
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 238000013507 mapping Methods 0.000 title claims abstract description 30
- 230000004044 response Effects 0.000 claims abstract description 33
- 230000006870 function Effects 0.000 claims description 177
- 230000004048 modification Effects 0.000 claims description 29
- 238000012986 modification Methods 0.000 claims description 29
- 238000013461 design Methods 0.000 claims description 11
- 238000012546 transfer Methods 0.000 claims description 11
- 238000012217 deletion Methods 0.000 claims description 10
- 230000037430 deletion Effects 0.000 claims description 10
- 238000007792 addition Methods 0.000 claims description 8
- 238000012544 monitoring process Methods 0.000 claims description 8
- 238000007667 floating Methods 0.000 claims description 3
- 230000001939 inductive effect Effects 0.000 claims description 3
- 230000008569 process Effects 0.000 abstract description 5
- 238000007726 management method Methods 0.000 description 25
- 238000004891 communication Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000007257 malfunction Effects 0.000 description 2
- 230000007704 transition Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000036632 reaction speed Effects 0.000 description 1
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 slicing capability, and dividing the slicing capability into 4 slice open function categories and 4 basic function categories; s2: analyzing slicing capability, and extracting keywords from the slicing capability as message bodies of request information and response information; s3: generating a slicing capability interface in a REST style; the invention provides a RESTful slice capability open interface mapping method, which can convert the existing and newly designed slice management and configuration capability into a REST style-based capability open interface, provides a RESTful normalized slice capability open interface mapping strategy, can be applied to capability open of 5G slices, and effectively solves the problems that the API 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.
Description
Technical Field
The invention relates to the field of 5G network slicing for power service, in particular to a RESTful-based slicing capability open interface mapping method.
Background
Network slicing is defined as a plurality of virtual networks operating as independent services on a general physical infrastructure, and the 5G network slicing technology can manage and arrange network resources according to factors such as applications, scenes, demands and the like, and tailor and customize network functions, and the 5G network capability opening refers to the capability of mutually opening between the 5G network and a third party application, and the capability of opening the 5G network to the third party application generally includes: the network/terminal monitoring capability, basic service capability, and control capability, whereas the third party application may also open the capability of the terminal, mobility information, service related information, etc. to the 5G network, so that the operator optimizes and manages the network according to the service requirement.
Under the 5G network architecture, the capability opening and terminal management, flow management, network slicing and MEC (Mobile Edge Computing ) technologies are combined, so that an operator can consider third-party service and security requirements during network planning and management, an open 5G slicing function is possible, the operator packages and integrates various capabilities in the own network management system to form a plurality of independent slicing inquiry management functions, and the operator opens the functions to an electric power user, so that the electric power user can directly manage the network slicing used by the operator to a certain extent, and the operation efficiency and the reaction speed of the service are improved.
The design of the capability open interface is the key of the open platform of the 5G network slice control capability in the power industry, but the open platform of the 5G network slice control capability can be also regarded as a network application program, the network application program is divided into a front end part and a back end part, the front end equipment is endlessly layered (such as a mobile phone, a tablet, a desktop computer and the like), therefore, a unified mechanism is needed to facilitate the communication between different front end equipment and the back end, which leads to the popularity of an API framework and even the design idea of 'API First', and RESTful API is the API design theory of a set of internet application programs which is mature at present.
REST (Representational State Transfer, 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, uniform resource identifier), XML (Extensible Markup Language ), JSON (JavaScript Object Notation, JS object profile), and the like, a lightweight, cross-platform, cross-language architecture design is supported, REST is a new architecture style of Web services, and main principles of RESTful architecture include: 1. there is a resource identifier for all resources on the network, 2. Operations on the resource do not change the identifier, 3. The same resource has multiple manifestations (xml, json), 4. All operations are Stateless.
However, the API interface mapping strategy of the slice open management and control capability is still not mature enough, and the slice open interface mapping process is not standard enough.
The present invention thus provides a new solution to this problem.
Disclosure of Invention
Aiming at the defects existing in the prior art, the invention aims to provide a slice capability open interface mapping method based on RESTful, which effectively solves the problems that the prior API interface mapping strategy of the slice capability open management and control capability is not mature enough and the slice capability open interface mapping process is not standard enough.
The technical scheme is that the method for mapping the slicing capability open interface based on RESTful comprises the following three steps:
s1, summarizing and sorting slicing capability, and dividing the slicing capability into 4 slice open function categories and 4 basic function categories;
s2: analyzing slicing capability, and extracting keywords from the slicing capability as message bodies of request information and response information;
s3: generating a slicing capability interface in a REST style;
the REST is an abbreviation of Representational State Transfer, which represents group design principles and constraints, and RESTful refers to the implementation of meeting these principles and constraints;
the step S1: the slice capability is summarized and organized into 4 slice open function categories and 4 basic function categories, including the following:
the slice open function class is specific classification guided by functions, and the basic function classification is 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 respectively comprise the following functions:
the slice operation monitoring comprises real-time slice operation state inquiry and historical slice operation state inquiry; the slice fault management comprises real-time fault information alarming and historical fault information inquiring; the slice function configuration comprises the logic functions of customizing slice types as required, setting the number of terminals accessing to the network slice and adding the network slice newly; the slice instance configuration comprises the 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 function classifications are specifically: addition, deletion, modification, and query; the functions in the slice open function class are divided into 4 basic function classifications, and the increase in the basic function classifications includes: the logical functions of the newly added network slice and the creation of the slice instance, and the deletion in the classification in the basic functions comprise: revocation of slice instances, modification in the basic functional classification includes: the method comprises the steps of customizing slice types according to requirements, setting the number of terminals accessing to a network slice, and carrying out configuration management on slice examples, wherein the inquiry in basic function classification comprises the following steps: real-time running state query of the slice, historical running state query of the slice, real-time warning of fault information, historical query of the fault information and information query of a slice instance;
the step S2: analyzing slicing capability, and extracting keywords from the slicing capability as message bodies of request information and response information, wherein the specific contents are as follows:
extracting keywords in function names according to the basic function classification, obtaining message bodies of interface request information and response information, and selecting corresponding data types and data formats, wherein the keywords in the function names can be divided into two types, one is a requirement of a power user, the keywords are used as the message bodies of the request information, the other is a result hoped to be obtained by the power user, and the keywords are used as the message bodies of the response information;
enumerating the message body and its format for its presence from the 4 basic functional classifications of addition, deletion, modification, and query, respectively:
the message body of the added function comprises a message body of request information of the added function and a message body of response information of the added function, and specifically comprises the following steps: the method comprises the steps that a power user makes a request for adding a certain resource to an operator, an object of 'adding' can be a slicing example and access equipment, or can be a certain function of slicing, the operator establishes a slicing example or adds a function for a certain slicing through a network management system of the operator according to the requirement of the power user, the related identification of the slicing is returned to the power user, double, string and Boolean types can be selected according to specific conditions, and JSON is uniformly selected as a data format;
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 form of 8 bits and 1 byte;
the deleting function specifically comprises the following steps: the deleting function is a function capable of removing the back-end resource, and the object of the deleting function can be a slice instance, an access device or a certain function of a slice, so that the response information of the deleting function only comprises a prompt of successful deleting and does not need to give out a selection of a message body;
the modification function is specifically as follows: the modification function not only can modify the slice and the access equipment, but also can modify the open functions of all slices, and after the power user makes a modification request, the operator carries out modification operation according to the request and returns the modified result to the power user;
the query function specifically comprises the following steps: the query function refers to the capability of a power user to acquire data from an operator, and the object of the query function can be slicing or accessing the data of equipment;
the step S3: the slicing capability interface for generating the REST style is specifically:
the slicing capability opening interface adopts a RESTful mode, wherein the core idea of the RESTful is that a data operation instruction sent by a client is a verb+object structure, the verb refers to five HTTP methods, and corresponds to CRUD operation, and in the selection of the HTTP methods, a GET method Read is selected, and the operation of taking out resources from a server is indicated;
the HTTP is an abbreviation of HyperText Transfer Protocol, which indicates the hypertext transfer protocol;
the HTTP has 5 methods corresponding to CRUD operations:
(1) GET method: reading the operation read;
(2) POST method: newly creating an operation Create;
(3) PUT method: updating operation Update;
(4) PATCH method: an Update operation Update, which refers to partial Update;
(5) DELETE method: delete operation Delete;
the definition of the open interface URL of the slicing capability is divided according to the open function category of the slicing, a URL domain is divided for each open function category of the slicing under the root directory of the resource, in the URL domain, division of URL subdomains is carried out according to specific slicing functions, when the newly created slicing functions are encountered, different capability domains are divided after classification, and a URL subdomain is newly built to correspond to the URL subdomains;
the URL is an abbreviation of Universal Resource Locator, representing a uniform resource locator.
The invention has the beneficial effects that:
the RESTful-based slice capability open interface mapping method provided by the invention can design an API interface of a REST style which is high-efficient and available for the existing slice open capability, can automatically provide an interface based on the REST style for the newly designed slice open capability, can convert the existing and newly designed slice management and configuration capability into the REST style-based capability open interface, provides a RESTful-based normalized slice open capability interface mapping strategy, can be applied to capability open of 5G slices, and effectively solves the problems that the API interface mapping strategy of the existing 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.
Drawings
Fig. 1 is an overall flow diagram of the present invention.
Detailed Description
The foregoing and other features, aspects and advantages of the present invention will become more apparent from the following detailed description of the embodiments, which proceeds with reference to the accompanying fig. 1 of the drawings. The following embodiments are described in detail with reference to the drawings.
The RESTful-based slice capability open interface mapping method provided by the present invention will be described in detail by way of embodiments with reference to the accompanying drawings.
A RESTful-based slicing capability open interface mapping method, the method comprising three steps:
s1, summarizing and sorting slicing capability, and dividing the slicing capability into 4 slice open function categories and 4 basic function categories;
s2: analyzing slicing capability, and extracting keywords from the slicing capability as message bodies of request information and response information;
s3: generating a slicing capability interface in a REST style;
the REST is an abbreviation of Representational State Transfer, which indicates the group design rules and constraints, and RESTful refers to the implementation of meeting these rules and constraints.
The step S1 is to summarize and sort the slicing capability into 4 kinds of slicing open function categories and 4 kinds of basic function categories, and specifically comprises the following contents:
the slice open function class is specific class guided by functions, the basic function class is basic function obtained by inducing and sorting slice capacity, the former focuses on classifying the 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 following steps: the operator gathers the 5G slice operation state information collected by the operator and timely sends the information to the power user, the power user 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 the following steps: the operators collect the information of slice operation monitoring collected by the operators, analyze abnormal data, acquire fault information, timely push the fault information to the power users, and store the collected fault information in a list form so as to meet the future query requirements of the power users;
the slicing function configuration specifically comprises the following steps: the power enterprise can participate in top-level design and life cycle management of power service network slicing, on the basis of three major categories of eMBB (enhanced mobile broadband), uRLLC (high reliability low latency communication) and mMTC (large-scale machine communication), the power enterprise can expand custom slicing types as required to distinguish different regional services or services with special management requirements, so that the mapping relation between the power service and the network slicing types is optimized, the power enterprise can set different terminal access quantity according to different types of network slicing, the power enterprise can define logic functions of each network slicing, and the slicing logic functions are optimized according to the functional requirements of different types of power service;
the slice example configuration is specifically: the power enterprise can independently arrange new network slice examples according to service requirements, and perform certain configuration management and information query operations on the new network slice examples, and can cancel corresponding slice examples when network slices are not needed for reasons;
the slice function configuration and the slice instance configuration are different in that the former focuses on the overall setting and changing of the slice function, and the latter focuses on the addition, deletion and change of a specific slice instance;
the 4 slice open function categories and function examples are shown in table 1:
table 1 slice open function class and function example
The invention divides the functions in the slice open function category into 4 basic functions: the functions were abstractly divided into these 4 categories by analyzing the slice function examples set forth in table 1, with the additions in the basic function classification including: the logical functions of the newly added network slice and the creation of the slice instance, and the deletion in the classification in the basic functions comprise: revocation of slice instances, modification in the basic functional classification includes: the method comprises the steps of customizing slice types according to requirements, setting the number of terminals accessing to a network slice, and carrying out configuration management on slice examples, wherein the inquiry in basic function classification comprises the following steps: the method comprises the steps of inquiring the real-time running state of the slice, inquiring the historical running state of the slice, alarming fault information in real time, inquiring the historical fault information and inquiring the information of the slice instance.
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:
on the basis of step S1, extracting keywords in function names according to basic function classification, obtaining message bodies of interface request information and response information, and selecting corresponding data types and data formats, wherein the keywords in the function names can be divided into two types, one is a requirement of a power user, the other is a message body of the request information, and the other is a result hoped to be obtained by the power user, and the keywords are used as the message bodies of the response information;
enumerating the message bodies and their formats that may exist from the 4 basic functional categories of addition, deletion, modification and query, respectively;
the message body of the added function comprises a message body of request information of the added function and a message body of response information of the added function, and specifically comprises the following contents:
the electric power user gives a request for adding a certain resource to an operator, wherein the object of the 'adding' can be a slicing example and access equipment, or can be a certain function of slicing, the operator establishes a slicing 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 identification of the related slice is returned to the electric power user, the message body of request information of the added function is shown in a table 2, the message body of response information of the added function is shown in a table 3, the data type can be Double (Double-precision floating point number), string (character String type, reference type) and Boolean type according to specific conditions, the variable is stored in 8 bits, the numerical form of 1 byte and the like, and the data format uniformly selects JSON;
table 2 message body of request information for adding function
Table 3 message body of response information of add function
The deleting function specifically comprises the following contents:
the deleting function is a function capable of removing the back-end resource, the object of the deleting function can be a slice instance, an access device or a certain function of a slice, the response information of the deleting function only needs to include a prompt of successful deleting, the selection of a message body is not needed, and the message body selection of the request information of the deleting function is shown in a table 4;
table 4 message body of request information of delete function
The modification function specifically comprises the following contents:
the modification function not only can modify the slice and the access equipment, but also can modify the open functions of all slices, after the power user makes a modification request, the operator carries out modification operation according to the request and returns the modified result to the power user, 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 of modification function
| Message body | Must select/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, a | double | JSON | Bandwidth modification requirements |
| ModDelay | Optionally, a | double | JSON | Time delay modification requirements |
| Devices | Optionally, a | double | JSON | Access device support number modification requirements |
| Function | Optionally, a | string | JSON | Slice open function requiring modification |
| ModDevice-id | Optionally, a | double | JSON | Access device sequence number to be modified |
Table 6 message body of response information of modification function
The query function specifically comprises the following contents:
the query function refers to the capability of a power user to acquire data from an operator, the object of the query function may be data of a slice, an access device or the like, 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 | Must select/optional | Data type | Data format | Description of the invention |
| KEY | Must choose | string | JSON | Capability opening key |
| Slice-id | Must choose | string | JSON | Slice number |
| QuiriedSlice-id | Must choose | string | JSON | Serial number of slice to be queried |
| QuiriedDevice-id | Optionally, a | double | JSON | Device serial number to be queried |
| Time | Optionally, a | string | JSON | Data acquisition time |
Table 8 message body of response information of query function
The step S3: the slicing capability interface for generating the REST style specifically comprises the following contents:
the slicing capability opening interface should be implemented in a RESTful manner, wherein REST (Representational State Transfer)) refers to a group design principle and constraint conditions, RESTful refers to implementation meeting the principle and constraint conditions, the core idea of RESTful is that data operation instructions sent by a client are all structures of 'verb+object', verbs are usually five HTTP (HyperText Transfer Protocol ) methods, and correspond to CRUD operations, in slicing capability opening, all opening functions of a power user are to take one or more pieces of slicing information (which can be operation data of slices or serial numbers of new slices) from an operator, and the power user cannot directly perform operations such as adding, modifying or deleting on a slicing network, so that in the selection of the HTTP methods, the power user selects a GET method (Read) entirely, and refers to operations of taking out resources (one or more items) from a server;
HTTP has 5 methods corresponding to CRUD operations:
(1) GET method: a read operation;
(2) POST method: a new creation operation (Create);
(3) PUT method: an Update operation (Update);
(4) PATCH method: an Update operation (Update), commonly referred to as a partial Update;
(5) DELETE method: delete operation (Delete);
the GET method corresponds to a Read operation, which is an operation of fetching resource(s) from a server; the definition of a slicing capability open interface URL (Universal Resource Locator, uniform resource locator) is divided according to slicing open function categories, a URL domain is divided for each slicing open function category under the root directory of resources, in the URL domain, division of URL subdomains can be further carried out according to specific slicing functions, and when a newly created slicing function is encountered, different capability domains can be divided after classification, and a URL subdomain is newly created to correspond to the URL subdomain; the capability open interface URL definition rules are shown in table 9; the capability open interface HTTP response information body definition is shown in table 10.
Table 9 capability open interface URL definition rules
Table 10 capability open interface HTTP response information body definition
| Fields | Description of the invention |
| responseCode | A return code indicating the request status |
| responseMsg | Return message detailing request status |
| res | Message body content, data format is JSON |
TABLE 11 responseCode optional value
The following describes the mapping procedure of the slicing capability open interface through a specific embodiment:
taking the fault information history query as an example to illustrate the mapping flow of the slicing capability open interface:
first, the fault information History query can be divided into "slice fault management" in the slice open function category and "query" in the basic function category, so that the URL domain where it is located can be determined as/Malfunction/, and in addition, since it focuses on "History information", the URL subdomain is set as/Malfunction/History/;
next, the power user applies words to describe the meaning of the function of 'fault Information history inquiry', acquires fault Information of a specific history Time point, extracts keywords, respectively obtains keywords such as 'history', 'fault Information', and the like, selects 'KEY', 'Time' and 'quick slice-id' from message bodies corresponding to the function of 'inquiry' of basic function classification as message bodies of request Information through analysis, wherein the KEY represents a capability open KEY, the quick slice-id represents a serial number of a slice to be inquired, the Time represents data acquisition Time, namely the fault Information inquiry Time point, and selects 'Type' and 'Information' as message bodies of response Information, namely fault types and fault Information respectively;
finally, according to the style of RESTful, the capability opening interface of the fault information history inquiry function is completed, the fault information history inquiry request information is shown in a table 12, and the fault information history inquiry response information is shown in a table 13;
table 12 fault information history query request information
TABLE 13 historical query response to failure information
Taking the creation of a slice instance as an example, the mapping flow of the slice capability open interface is described:
firstly, the Creation of the slice instance can be divided into a slice instance configuration in the slice open function category and an addition in the basic function category, the URL domain where the slice instance is located is determined to be/NS-Case/, and in addition, the URL subdomain is set to be/NS-Case/Creation/, because the Creation is focused on the Creation;
then, extracting keywords to obtain keywords such as a slice instance, creating and the like respectively, analyzing, selecting a message body with a KEY, a Bandwidth-max, a Delay-min and a device-max as request information in a message body corresponding to an increasing basic function, wherein the KEY represents a capability open KEY, the Bandwidth-max represents a maximum Bandwidth requirement, the Delay-min represents a minimum Delay requirement, the device-max represents a maximum terminal number requirement, and the device-max represents an ID number of a newly-built slice instance;
finally, according to the style of RESTful, the capability opening interface for completing the creation function of the slice instance is provided, 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 instance
Table 15 creation response information for slice instance
It should be noted that, the slice capability open interface mapping method based on RESTful provided by the 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.
The invention described with reference to the above figures, in particular use, comprises three steps:
s1, summarizing and sorting slicing capability, and dividing the slicing capability into 4 slice open function categories and 4 basic function categories;
s2: analyzing slicing capability, and extracting keywords from the slicing capability as message bodies of request information and response information;
s3: generating a slicing capability interface in a REST style;
the RESTful-based slice capability open interface mapping method provided by the invention can design an API interface of a REST style which is high-efficient and available for the existing slice open capability, can automatically provide an interface based on the REST style for the newly designed slice open capability, can convert the existing and newly designed slice management and configuration capability into the REST style-based capability open interface, provides a RESTful-based normalized slice open capability interface mapping strategy, can be applied to capability open of 5G slices, and effectively solves the problems that the API interface mapping strategy of the existing 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.
Claims (1)
1. The RESTful-based slicing capability open interface mapping method is characterized by comprising the following three steps:
s1, summarizing and sorting slicing capability, and dividing the slicing capability into 4 slice open function categories and 4 basic function categories;
s2: analyzing slicing capability, and extracting keywords from the slicing capability as message bodies of request information and response information;
s3: generating a slicing capability interface in a REST style;
the REST is an abbreviation of Representational State Transfer, which represents group design principles and constraints, and RESTful refers to the implementation of meeting these principles and constraints;
the step S1: the slice capability is summarized and organized into 4 slice open function categories and 4 basic function categories, including the following:
the slice open function class is specific classification guided by functions, and the basic function classification is 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 respectively comprise the following functions:
the slice operation monitoring comprises real-time slice operation state inquiry and historical slice operation state inquiry; the slice fault management comprises real-time fault information alarming and historical fault information inquiring; the slice function configuration comprises the logic functions of customizing slice types as required, setting the number of terminals accessing to the network slice and adding the network slice newly; the slice instance configuration comprises the 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 function classifications are specifically: addition, deletion, modification, and query; the functions in the slice open function class are divided into 4 basic function classifications, and the increase in the basic function classifications includes: the logical functions of the newly added network slice and the creation of the slice instance, and the deletion in the classification in the basic functions comprise: revocation of slice instances, modification in the basic functional classification includes: the method comprises the steps of customizing slice types according to requirements, setting the number of terminals accessing to a network slice, and carrying out configuration management on slice examples, wherein the inquiry in basic function classification comprises the following steps: real-time running state query of the slice, historical running state query of the slice, real-time warning of fault information, historical query of the fault information and information query of a slice instance;
the step S2: analyzing slicing capability, and extracting keywords from the slicing capability as message bodies of request information and response information, wherein the specific contents are as follows:
extracting keywords in function names according to the basic function classification, obtaining message bodies of interface request information and response information, selecting corresponding data types and data formats, wherein the keywords in the function names are classified into two types, one is a requirement of a power user, the other is a result which the power user hopes to obtain, and the other is a message body of the response information;
enumerating the message body and its format for its presence from the 4 basic functional classifications of addition, deletion, modification, and query, respectively:
the message body of the added function comprises a message body of request information of the added function and a message body of response information of the added function, and specifically comprises the following steps: the method comprises the steps that a power user makes a request for adding a certain resource to an operator, the object of the 'adding' is a slicing example, access equipment or a certain function of slicing, the operator newly builds the slicing example or adds a function for a certain slicing through a network management system of the operator according to the requirement of the power user, the related identification of the slicing is returned to the power user, double, string and Boolean types are selected according to specific conditions, and JSONs are uniformly selected according to data types;
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 form of 8 bits and 1 byte;
the deleting function specifically comprises the following steps: the deleting function is a function of removing the back-end resource, and the object of the deleting function is a slice instance, an access device or a certain function of a slice, so that the response information of the deleting function only comprises a prompt of successful deleting and does not need to give a message body selection;
the modification function is specifically as follows: the modification function not only modifies the slice and the access equipment, but also modifies the open functions of each slice, after the power user makes a modification request, the operator carries out modification operation according to the request, and returns the modified result to the power user;
the query function specifically comprises the following steps: the query function refers to the capability of a power user to acquire data from an operator, and the object of the query function is slicing or accessing the data of equipment;
the step S3: the slicing capability interface for generating the REST style is specifically:
the slicing capability opening interface adopts a RESTful mode, wherein the core idea of the RESTful is that a data operation instruction sent by a client is a verb+object structure, the verb refers to five HTTP methods, and corresponds to CRUD operation, and in the selection of the HTTP methods, a GET method Read is selected, and the operation of taking out resources from a server is indicated;
the HTTP is an abbreviation of HyperText Transfer Protocol, which indicates the hypertext transfer protocol;
the HTTP has 5 methods corresponding to CRUD operations:
(1) GET method: reading the operation read;
(2) POST method: newly creating an operation Create;
(3) PUT method: updating operation Update;
(4) PATCH method: an Update operation Update, which refers to partial Update;
(5) DELETE method: delete operation Delete;
the definition of the open interface URL of the slicing capability is divided according to the open function category of the slicing, a URL domain is divided for each open function category of the slicing under the root directory of the resource, in the URL domain, division of URL subdomains is carried out according to specific slicing functions, when the newly created slicing functions are encountered, different capability domains are divided after classification, and a URL subdomain is newly built to correspond to the URL subdomains;
the URL is an abbreviation of Universal Resource Locator, representing 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 CN113824589A (en) | 2021-12-21 |
| CN113824589B true 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 (4)
| 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 |
| CN110447247A (en) * | 2017-03-20 | 2019-11-12 | 康维达无线有限责任公司 | Service ability at user equipment is open |
| 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 |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3417647B1 (en) * | 2016-02-17 | 2019-11-20 | NEC Corporation | A method for operating a wireless network, a wireless network and a management entity |
| EP3552419B1 (en) * | 2016-12-23 | 2021-07-14 | Huawei Technologies Co., Ltd. | System and method for programming and/or management of core network slices |
| WO2019111267A1 (en) * | 2017-12-06 | 2019-06-13 | Telefonaktiebolaget Lm Ericsson (Publ) | First node, second node, and methods performed thereby for managing a network slice instance |
| US10986540B2 (en) * | 2018-01-12 | 2021-04-20 | Huawei Technologies Co., Ltd. | Network slice provisioning and operation |
| US10671462B2 (en) * | 2018-07-24 | 2020-06-02 | Cisco Technology, Inc. | System and method for message management across a network |
-
2021
- 2021-09-18 CN CN202111102805.3A patent/CN113824589B/en active Active
Patent Citations (4)
| 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 |
| CN110447247A (en) * | 2017-03-20 | 2019-11-12 | 康维达无线有限责任公司 | Service ability at user equipment is open |
| 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 |
|---|
| NEWT: A RESTful service for building High Performance Computing web applications;Shreyas Cholia等;《2010 Gateway Computing Environments Workshop (GCE)》;全文 * |
| 基于能力开放的5G网络切片管理研究;李红祎等;《万方数据库》;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113824589A (en) | 2021-12-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11768811B1 (en) | Managing user data in a multitenant deployment | |
| US11238069B2 (en) | Transforming a data stream into structured data | |
| CN111930547A (en) | Fault positioning method and device and storage medium | |
| US11829381B2 (en) | Data source metric visualizations | |
| US20130218919A1 (en) | Method and apparatus for managing content | |
| US12019634B1 (en) | Reassigning a processing node from downloading to searching a data group | |
| CN110362544A (en) | Log processing system, log processing method, terminal and storage medium | |
| US11269808B1 (en) | Event collector with stateless data ingestion | |
| CN103927314B (en) | A kind of method and apparatus of batch data processing | |
| CN109359094A (en) | A kind of full link tracing method and device of distributed system journal | |
| CN111737630B (en) | Method for recording user access path | |
| CN101098248A (en) | Method and system for implementing universal network management based on configuration describing document | |
| US20230018723A1 (en) | Cascading payload replication | |
| CN113824589B (en) | RESTful-based slicing capability open interface mapping method | |
| Jin | Research on data retrieval and analysis system based on Baidu reptile technology in big data era | |
| CN112131239B (en) | Data processing method, computer equipment and readable storage medium | |
| CN116974948B (en) | Service system testing method, system, equipment and medium | |
| CN113157904A (en) | Sensitive word filtering method and system based on DFA algorithm | |
| CN111711695A (en) | Distributed equipment management system based on cloud platform | |
| CN111611222A (en) | Data dynamic processing method based on distributed storage | |
| CN115168474B (en) | Internet of things central station system building method based on big data model | |
| CN108959041B (en) | Method for transmitting information, server and computer readable storage medium | |
| KR20010060617A (en) | Report generation and access device and method in network management system | |
| CN115599657B (en) | Software facility abnormity judgment method | |
| CN110740046B (en) | Method and device for analyzing service contract |
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 |