CN116418703A - Feasibility inspection processing method, device and equipment - Google Patents
Feasibility inspection processing method, device and equipment Download PDFInfo
- Publication number
- CN116418703A CN116418703A CN202111669660.5A CN202111669660A CN116418703A CN 116418703 A CN116418703 A CN 116418703A CN 202111669660 A CN202111669660 A CN 202111669660A CN 116418703 A CN116418703 A CN 116418703A
- Authority
- CN
- China
- Prior art keywords
- feasibility
- network slice
- feasibility check
- request message
- check
- 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.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 24
- 238000007689 inspection Methods 0.000 title abstract description 9
- 238000000034 method Methods 0.000 claims abstract description 69
- 238000012545 processing Methods 0.000 claims abstract description 26
- 230000004044 response Effects 0.000 claims description 75
- 238000004891 communication Methods 0.000 abstract description 7
- 230000000694 effects Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
-
- 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/0803—Configuration setting
Abstract
The invention provides a processing method, a processing device and processing equipment for feasibility inspection, and relates to the technical field of communication. The method comprises the following steps: receiving a first request message sent by second communication equipment; a feasibility check work instance of a first network slice related requirement is created and a feasibility check procedure of the first network slice related requirement is performed. The technical scheme of the invention solves the problem that a specific scheme of feasibility checking is not given in the current management flow of feasibility checking.
Description
Technical Field
The present invention relates to the technical field of the present invention, and in particular, to a method, an apparatus, and a device for processing feasibility inspection.
Background
A network feasibility check may be performed before network allocation and network deployment is performed to ensure feasibility of network configuration and network deployment. The current network feasibility check needs to check the condition, resources and the like of the whole network, and the related follow-up operations such as network allocation, network deployment and the like can be performed after no problem is determined. However, in the current management flow of the feasibility check, only the network element performing the feasibility check is defined, and no specific scheme for the feasibility check is given yet.
Disclosure of Invention
The invention aims to provide a processing method, a processing device and processing equipment for feasibility inspection, which are used for solving the problem that a specific scheme for feasibility inspection is not given in the current management flow of feasibility inspection.
To achieve the above object, an embodiment of the present invention provides a processing method for feasibility check, which is applied to a first device, and includes:
receiving a first request message sent by second equipment;
creating and/or configuring a feasibility check working instance of a first network slice related requirement, and executing a feasibility check flow of the first network slice related requirement.
Optionally, the first request message carries the first network slice related requirement and/or creation request information for indicating to create and/or configure the feasibility check working instance.
Optionally, after creating and/or configuring the feasibility check working instance of the first network slice related requirement, further comprises:
and sending a first response message to the second device.
Optionally, the first response message carries first indication information for indicating the feasibility checking working instance, and/or attribute information of the feasibility checking working instance.
Optionally, the method further comprises:
receiving a second request message sent by the second device;
and acquiring attribute information of the feasibility checking working example.
Optionally, after the obtaining the attribute information of the feasibility checking working instance, the method further includes:
and sending a second response message to the second device.
Optionally, the second response message carries attribute information of the feasibility check working instance.
Optionally, the attribute information includes at least one of:
the feasibility checking working example is operated;
a working schedule for performing a feasibility check on the first network slice related requirements;
a feasibility check result of performing feasibility check on the first network slice related requirement;
and comment text of the feasibility checking result.
Optionally, the method further comprises:
receiving a third request message sent by the second equipment;
deleting the feasibility checking working example.
Optionally, after deleting the feasibility checking work instance, the method further comprises:
and sending a third response message to the second device.
Optionally, the third response message carries second indication information for indicating that the feasibility check working instance has been deleted.
To achieve the above object, an embodiment of the present invention provides a processing method for feasibility check, applied to a second device, the method including:
transmitting a first request message to a first device; wherein the first request message is used to indicate a feasibility check for a first network slice related requirement.
Optionally, the first request message carries the first network slice related requirement and/or creation request information for indicating to create the feasibility check working instance.
Optionally, after the first request message is sent to the first device, the method further includes:
and receiving a first response message sent by the first equipment.
Optionally, the first response message carries first indication information for indicating the feasibility checking working instance, and/or attribute information of the feasibility checking working instance.
Optionally, after the first request message is sent to the first device, the method further includes:
sending a second request message to the first device; the second request message is used for indicating to acquire attribute information of the feasibility check working instance.
Optionally, after the sending the second request message to the first device, the method further includes:
And receiving a second response message sent by the first device.
Optionally, the second response message carries the attribute information.
Optionally, the attribute information includes at least one of:
the feasibility checking working example is operated;
a working schedule for performing a feasibility check on the first network slice related requirements;
a feasibility check result of performing feasibility check on the first network slice related requirement;
and comment text of the feasibility checking result.
Optionally, the method further comprises:
if the feasibility checking result in the attribute information is feasible, requesting to configure a network slice and/or a network slice subnet meeting the related requirements of the first network slice from the first equipment;
and if the feasibility checking result in the attribute information is infeasible, updating the first network slice related requirement.
Optionally, the method further comprises:
sending a third request message to the second device; wherein the third request message is used for indicating to delete the feasibility check working instance.
Optionally, after the sending the third request message to the second device, the method further includes:
And receiving a third response message sent by the first device.
Optionally, the third response message carries second indication information for indicating that the feasibility check working instance has been deleted.
To achieve the above object, an embodiment of the present invention provides a processing apparatus for feasibility check, which is applied to a first device, and includes:
the first receiving module is used for receiving a first request message sent by the second equipment;
and the first processing module is used for creating a feasibility checking working example of the first network slice related requirement and executing a feasibility checking flow of the first network slice related requirement.
To achieve the above object, an embodiment of the present invention provides a processing apparatus for feasibility check, applied to a second device, including:
the first sending module is used for sending a first request message to the first equipment; wherein the first request message is used to indicate a feasibility check for a first network slice related requirement.
To achieve the above object, an embodiment of the present invention provides an apparatus comprising: a transceiver, a processor, a memory, and a program or instructions stored on the memory and executable on the processor; in the case where the device is a first device, the processor, when executing the program or instructions, implements the steps in the processing method of the feasibility check on the first device side as above; in the case where the device is a second device, the processor, when executing the program or instructions, implements the steps in the processing method of the feasibility check on the second device side as above.
To achieve the above object, an embodiment of the present invention provides a readable storage medium having stored thereon a program or instructions which, when executed by a processor, implement the steps in the processing method of the feasibility check of the first device side or the second device side as above.
The technical scheme of the invention has the following beneficial effects:
in the embodiment of the invention, the first equipment receives the first request message sent by the second equipment, creates the feasibility checking working example of the related requirement of the first network slice, and executes the feasibility checking flow of the related requirement of the first network slice, namely, a specific scheme of feasibility checking in the management flow of the feasibility checking is provided, the corresponding refinement of the feasibility checking operation is realized, and a solution is provided for the realization of a network management system.
Drawings
Fig. 1 is a flowchart of a processing method of a first device side feasibility check according to an embodiment of the invention;
FIG. 2 is a flow chart of a method for processing a feasibility check according to an embodiment of the invention;
FIG. 3 is a block diagram of a processing apparatus for a first device-side feasibility check according to an embodiment of the invention;
FIG. 4 is a block diagram of an apparatus of an embodiment of the present invention;
FIG. 5 is a flowchart of a processing method of the second device side feasibility check according to the embodiment of the invention;
Fig. 6 is a block diagram of a processing apparatus for a second device-side feasibility check according to an embodiment of the invention.
Detailed Description
In order to make the technical problems, technical solutions and advantages to be solved more apparent, the following detailed description will be given with reference to the accompanying drawings and specific embodiments.
It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
In various embodiments of the present invention, it should be understood that the sequence numbers of the following processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.
In addition, the terms "system" and "network" are often used interchangeably herein.
In the examples provided herein, it should be understood that "B corresponding to a" means that B is associated with a from which B may be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may also determine B from a and/or other information.
As shown in fig. 1, a processing method for feasibility checking according to an embodiment of the present invention is applied to a first device, and the method includes:
step 11: and receiving a first request message sent by the second equipment.
Alternatively, the first device may be referred to as a network sliced subnet management service Provider (NSSMS_Provider) and the second device may be referred to as a network sliced subnet management service Consumer (NSSMS_Consumer)
Optionally, the first request message may be used to instruct the first device to perform a feasibility check on the first network slice related requirement, for example, the first request message may be used to instruct the first device to create a feasibility check work instance on the first network slice related requirement, and perform a feasibility check procedure on the first network slice related requirement, where the first request message may be referred to as a feasibility check work creation request message.
Optionally, the first request message may carry the first network slice related requirement and/or creation request information for indicating to create the feasibility check working instance.
Step 12: a feasibility check work instance of a first network slice related requirement is created and a feasibility check procedure of the first network slice related requirement is performed.
For example: the feasibility check job (Feasibility Check Job, IOC) represents a feasibility check job of the network slice related requirements (e.g. a service file (servivprofile) may represent the network slice related requirements, a slice file (slicerprofile) represents the network slice subnet related requirements) to determine if the network slice related requirements can be met, which may be contained by a subnet (subnet).
When nssms_consumer derives a network slice related requirement (i.e., serviveProfile, sliceProfile), nssms_consumer may send a request message to nssms_provider for a feasibility check specifying the network slice related requirement before requesting nssms_provider to allocate or modify NSI or NSSI. To express the feasibility check job of a particular network slice related requirement (i.e., serviceProfile, sliceProfile), nssms_consumer needs to request nssms_provider to create a feasibility check job instance at the nssms_provider that specifies the network slice related requirement and perform a feasibility check process.
In the above scheme (such as the progress of the feasibility checking work, the feasibility checking result, the comment file of the feasibility checking result, the running state of the feasibility checking work example, etc.), the first communication device receives the first request message sent by the second communication device, creates the feasibility checking work example required by the first network slice, and executes the feasibility checking flow required by the first network slice, namely, gives a specific scheme of feasibility checking in the management flow of feasibility checking, realizes the corresponding refinement of the feasibility checking operation, and provides a solution for realizing the network management system.
Optionally, after the creating and/or configuring the feasibility check working instance of the first network slice related requirement, the method further comprises:
and sending a first response message to the second device.
In this embodiment, the sending of the response message to the second device is not limited to the sending of the first response message to the second device after the completion of the creating and/or configuring the feasibility check working instance of the first network slice related requirement, that is, after the completion of the creating and/or configuring the feasibility check working instance of the first network slice related requirement, or the sending of the first response message to the second device before the completion of the creating and/or configuring the feasibility check working instance of the first network slice related requirement, for example, the sending of the first response message to the second device when the creating and/or configuring the feasibility check working instance of the first network slice related requirement is triggered, which is not limited to the embodiment of the invention.
Optionally, the first response message may be used to indicate that the feasibility checking working instance is created and/or configured, and/or the first response message may be used to indicate attribute information of the feasibility checking working instance (such as a progress of the feasibility checking working, a feasibility checking result, a comment file of the feasibility checking result, an operation state of the feasibility checking working instance, etc., which is not limited by the embodiment of the present invention), for example, when the protocol agreeing that the feasibility checking working instance is created and/or configured, and/or a result of the feasibility checking is determined when the second device receives the first response message.
Optionally, the first response message carries first indication information for indicating the feasibility checking working instance, and/or attribute information of the feasibility checking working instance.
For example: when the first response message carries first indication information for indicating the feasibility check working example, that is, when the first device creates the feasibility check working example, the first response message may be sent to the second device, so that the second device knows the feasibility check working example created for the first network slice related requirement, and the second device may request the attribute information of the feasibility check working example from the first device based on the feasibility check working example. The first response message may also be referred to herein as a feasibility check creation response message.
Also for example: when the first response message carries attribute information for indicating the feasibility check working example, that is, in the process that the first device creates the feasibility check working example and executes the feasibility check on the first network slice related requirement, the first response message can be actively sent to the second device by the first device, so that the second device knows the attribute information and the like of the feasibility check working example required by the first network slice related requirement, the second device can conveniently execute corresponding operation on the attribute information of the feasibility check working example, if the feasibility check result indicates that the feasibility check is feasible, the second device side can request the first device side to allocate a network slice or a network slice subnet with the checked network slice related requirement (that is, serviceProfile or slicerph profile); if the feasibility check result is not feasible, the second device may update the first network slice related requirement and may trigger the feasibility check job again, etc.
Optionally, the method further comprises:
receiving a second request message sent by the second device;
and acquiring attribute information of the feasibility checking working example.
Optionally, the second request message may be used to indicate that the attribute information of the feasibility checking working instance is obtained, that is, the attribute information of the feasibility checking working instance is queried, where the attribute information of the feasibility checking working instance may be obtained from the content stored in the second request message or may be obtained from other network elements, which is not limited by the embodiment of the present invention. The second request message may also be referred to herein as a feasibility check job schedule and results query request message.
Wherein the attribute information includes, but is not limited to, at least one of: the feasibility checking working example is operated; a working schedule for performing a feasibility check on the first network slice related requirements; a feasibility check result of performing feasibility check on the first network slice related requirement; and comment text of the feasibility checking result. Alternatively, the attribute information may be configured at the time of creating the feasibility check working instance, or the like, although the embodiment of the invention is not limited thereto.
For example: configuration information for the feasibility check job instance may include, but is not limited to, at least one of: sliceProfile, serviceProfile, operational state (Progress), feasibility check result (feasiltyresult), comment file (comment text), and the like, as shown in table 1.
TABLE 1
| Attribute name | Support definition | Readable and readable | Writable | Whether or not to be unchanged | Can be notified of |
| sliceProfile | CM | T | T | F | T |
| serviceProfile | CM | T | T | F | T |
| operationalState | M | T | F | F | T |
| Progress | M | T | F | F | T |
| feasibilityResult | M | T | F | F | T |
| commentText | O | T | F | F | T |
Wherein, the operationalState is an attribute for describing the running state of the feasibility check working instance. This attribute may be configured by NSSMS_provider, readable by NSSMS_Consumer. The allowable values may be: is executing and is completed.
The Progress is an attribute describing a work Progress of the feasibility check on the first network slice related requirement, which may specify the Progress of the feasibility check job in the form of a percentage. This attribute is configured by nssms_provider and can be read by nssms_consumer. The allowable values may be: 0 to 100.
feasilitityresult is a feasibility check result describing a feasibility check on the first network slice related requirement. This attribute is configured by nssms_provider and can be read by nssms_consumer. The allowable values may be: is feasible and not feasible;
Where feasible means NSSMS _ Provider can meet the first network slice related requirements (i.e., serviceProfile, sliceProfile). Infeasible means that the first network slice related requirement (i.e., serviceProfile, sliceProfile) cannot be met by NSSMS _ Provider.
The commentary text is an attribute describing comments for the feasibility check result, for example: in the case where the value of feasility result indicates infeasibility, the commentat may indicate a reason of infeasibility, etc., the embodiment of the present invention is not limited thereto.
Specifically, to obtain the working progress of the feasibility check, the nssms_consumer may request the nssms_provider to query the values of the attributes "operation alstate" and "progress", e.g., in executing the feasibility check flow required for the first network slice, the nssms_consumer may request the nssms_provider to query the values of the attributes "operation alstate" and "progress". To obtain the feasibility check result, nssms_consumer may request nssms_provider to query the value of attribute "feasiltyresult" and/or optionally query "complettext" when the feasibility check flow is completed, which is not limited by the embodiment of the present invention.
Optionally, after the obtaining the attribute information of the feasibility checking working instance, the method further includes:
And sending a second response message to the second communication device.
Optionally, the second response message may be used to indicate attribute information of the feasibility checking working instance, for example, the second response message directly indicates the working progress and/or the result of the feasibility checking, which is not limited to this embodiment of the method.
Optionally, the second response message may carry the attribute information.
For example: and inquiring corresponding attribute information (such as values of operation state and progress) at the first equipment, and sending a second response message to the second equipment so that the second equipment side can know the working progress and/or result of the current feasibility check. The second response message may also be referred to herein as a feasibility check job schedule and results query response message.
Optionally, the method further comprises:
receiving a third request message sent by the second equipment;
deleting the feasibility checking working example.
Wherein the third request message may be used to indicate a deletion of the first network slice-related required feasibility check working instance. For example: after the feasibility check result is obtained, the nssms_consumer may request the nssms_provider to delete the feasibility check working instance of the nssms_provider end. The third request information may also be referred to herein as a feasibility check job delete request message.
Optionally, after deleting the feasibility checking work instance, the method further comprises:
and sending a third response message to the second device.
Optionally, the third response message may be used to indicate that the feasibility check working instance has been deleted. For example: the protocol defines that the feasibility check working instance is determined to have been deleted when the second device receives the third response message.
Optionally, the third response message may further carry second indication information for indicating that the feasibility check working instance has been deleted.
In this embodiment, after the first device deletes the feasibility checking working instance required by the first network slice, the third response message may also be fed back to the second device, so that the second device may learn that the first device has deleted the feasibility checking working instance. The third response message may also be referred to herein as a feasibility check job delete response message.
As shown in fig. 2, the embodiment of the present invention further provides a flowchart of a processing method of feasibility checking, which specifically includes:
step 1: the nssms_provider receives the feasibility check job creation request (create MOI operation) and the network slice related requirements sent by the nssms_consumer to request a check whether the network slice related requirements can be met.
Step 2: NSSMS_Provider creates a feasibility check work instance and configures attribute information, such as SliceProfile, serviceProfile, operationalState, progress, feasibilityResult and completText, etc. Nssms_provider begins the feasibility check process, at which point nssms_provider may also request other MnS producers to check the feasibility of network-sliced subnet components using the same network-sliced subnet feasibility check program.
Step 3: NSSMS_provider sends a feasibility check job creation response to NSSMS_Consumer.
Step 4: during execution of the feasibility check flow, the nssms_provider receives a feasibility check job schedule and results query request (getmoiattritor) sent by the nssms_consumer specifying a feasibility check job instance to query the values of the attributes "progress" and "feasiltyresult" of the item.
Step 5: NSSMS_Provider reads the values of the attributes "progress" and "feasility result" for the specified feasibility check working instance.
Step 6: NSSMS_provider sends a feasibility check job schedule and results query response (getMOIAttributes) to NSSMS_Consumer, which contains values specifying the attributes "progress" and "feasility result" of the feasibility check work instance.
Step 7: when NSSMS_Consumer decides to delete a feasibility check work instance (e.g., a feasibility check result is obtained), NSSMS_Provider receives a feasibility check work delete request (delete MOI operation) for the specified feasibility check work instance.
Step 8: nssms_provider deletes the specified feasibility check working instance.
Step 9: NSSMS_Provider sends a feasibility check job delete response for the deleted feasibility check work instance.
The specific scheme of feasibility checking in the management flow of feasibility checking is provided in the scheme, the corresponding refinement of the feasibility checking operation is realized, the feasibility checking response solution is defined, and the solution is provided for the network management system.
The processing method of the feasibility check according to the embodiment of the present invention is described above, and the apparatus and the device corresponding to the method are described below.
As shown in fig. 3, a processing apparatus 300 for feasibility checking according to an embodiment of the invention is applied to a first device, and includes:
a first receiving module 310, configured to receive a first request message sent by a second device;
the first processing module 320 is configured to create a feasibility check working instance of the first network slice related requirement, and execute a feasibility check procedure of the first network slice related requirement.
Optionally, the first request message carries the first network slice related requirement and/or creation request information for indicating to create the feasibility check working instance.
Optionally, the apparatus 300 further includes:
and the first sending module is used for sending a first response message to the second equipment.
Optionally, the first response message carries first indication information for indicating the feasibility checking working instance, and/or attribute information of the feasibility checking working instance.
Optionally, the apparatus 300 further includes:
the second receiving module is used for receiving a second request message sent by the second equipment;
and the second processing module is used for acquiring the attribute information of the feasibility checking working example.
Optionally, the apparatus 300 further includes:
and the second sending module is used for sending a second response message to the second equipment.
Optionally, the second response message carries the attribute information.
Optionally, the attribute information includes at least one of:
the feasibility checking working example is operated;
a working schedule for performing a feasibility check on the first network slice related requirements;
A feasibility check result of performing feasibility check on the first network slice related requirement;
and comment text of the feasibility checking result.
Optionally, the apparatus 300 further includes:
the third receiving module is used for receiving a third request message sent by the second equipment;
and the third processing module is used for deleting the feasibility checking working example.
Optionally, the apparatus 300 further includes:
and the third sending module is used for sending a third response message to the second equipment.
Optionally, the third response message carries second indication information for indicating that the feasibility check working instance has been deleted.
The device in the embodiment of the present invention can implement each embodiment of the processing method for feasibility inspection on the first device side, and can achieve the same technical effects, and for avoiding repetition, the description is omitted here.
An apparatus according to another embodiment of the present invention, as shown in fig. 4, includes a transceiver 410, a processor 400, a memory 420, and a program or instructions stored on the memory 420 and executable on the processor 400; the steps in the above processing method applied to the feasibility check on the first device side are implemented when the processor 400 executes the program or the instruction, and the same technical effects can be achieved, so that repetition is avoided and no further description is given here.
The transceiver 410 is configured to receive and transmit data under the control of the processor 400.
Wherein in fig. 4, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 400 and various circuits of memory represented by memory 420, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. Transceiver 410 may be a number of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 400 is responsible for managing the bus architecture and general processing, and the memory 420 may store data used by the processor 400 in performing operations.
The readable storage medium of the embodiment of the present invention stores a program or an instruction, where the program or the instruction, when executed by a processor, implements the steps in the processing method applied to the feasibility check on the first device side as described above, and can achieve the same technical effects, so that repetition is avoided and no further description is given here.
Wherein the processor is a processor in the communication device described in the above embodiment. The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory RAM), a magnetic disk or an optical disk.
The embodiments of the first device are described above, and the embodiments of the second device side corresponding thereto are described below with reference to the drawings.
As shown in fig. 5, an embodiment of the present invention provides a processing method for feasibility checking, which is applied to a second device, and the method includes:
step 51: transmitting a first request message to a first device; wherein the first request message is used to indicate a feasibility check for a first network slice related requirement.
Optionally, the first request message carries the first network slice related requirement and/or creation request information for indicating to create the feasibility check working instance.
Optionally, after the first request message is sent to the first device, the method further includes:
and receiving a first response message sent by the first equipment.
Optionally, the first response message carries first indication information for indicating the feasibility checking working instance, and/or attribute information of the feasibility checking working instance.
Optionally, after the first request message is sent to the first device, the method further includes:
sending a second request message to the first device; the second request message is used for indicating to acquire attribute information of the feasibility check working instance.
Optionally, after the sending the second request message to the first device, the method further includes:
and receiving a second response message sent by the first device.
Optionally, the second response message carries the attribute information.
Optionally, the attribute information includes at least one of:
the feasibility checking working example is operated;
a working schedule for performing a feasibility check on the first network slice related requirements;
a feasibility check result of performing feasibility check on the first network slice related requirement;
and comment text of the feasibility checking result.
Optionally, the method further comprises:
if the feasibility checking result in the attribute information is feasible, requesting to configure a network slice and/or a network slice subnet meeting the related requirements of the first network slice from the first equipment;
and if the feasibility checking result in the attribute information is infeasible, updating the first network slice related requirement.
Optionally, the method further comprises:
sending a third request message to the second device; wherein the third request message is used for indicating to delete the feasibility check working instance.
Optionally, after the sending the third request message to the second device, the method further includes:
and receiving a third response message sent by the first device.
Optionally, the third response message carries second indication information for indicating that the feasibility check working instance has been deleted.
It should be noted that, the method of the second device in the embodiment of the present invention corresponds to the method of the first device side, and embodiments thereof may be referred to each other, and the same technical effects can be achieved, and the repetition is omitted.
The processing method of the feasibility check according to the embodiment of the present invention is described above, and the apparatus and the device corresponding to the method are described below.
As shown in fig. 6, an embodiment of the present invention provides a processing apparatus 600 for feasibility checking, applied to a second device, including:
a first sending module 610, configured to send a first request message to a first device; wherein the first request message is used to indicate a feasibility check for a first network slice related requirement.
Optionally, the first request message carries the first network slice related requirement and/or creation request information for indicating to create the feasibility check working instance.
Optionally, the apparatus further comprises:
and the first receiving module is used for receiving the first response message sent by the first equipment.
Optionally, the first response message carries first indication information for indicating the feasibility checking working instance, and/or attribute information of the feasibility checking working instance.
Optionally, the apparatus 600 further includes:
a second sending module, configured to send a second request message to the first device; the second request message is used for indicating to acquire attribute information of the feasibility check working instance.
Optionally, the apparatus 600 further includes:
and the second receiving module is used for receiving a second response message sent by the first device.
Optionally, the second response message carries the attribute information.
Optionally, the attribute information includes at least one of:
the feasibility checking work instance status;
a working schedule for performing a feasibility check on the first network slice related requirements;
A feasibility check result of performing feasibility check on the first network slice related requirement;
and comment text of the feasibility checking result.
Optionally, the apparatus 300 further includes:
the first processing module is used for requesting to configure the network slice and/or the network slice subnet meeting the related requirements of the first network slice from the first equipment if the feasibility check result in the attribute information is feasible;
and the second processing module is used for updating the related requirements of the first network slice if the feasibility check result in the attribute information is infeasible.
Optionally, the apparatus 300 further includes:
a third sending module, configured to send a third request message to the second device; wherein the third request message is used for indicating to delete the feasibility check working instance.
Optionally, the apparatus 300 further includes:
and the third receiving module is used for receiving a third response message sent by the first equipment.
Optionally, the third response message carries second indication information for indicating that the feasibility check working instance has been deleted.
The device in the embodiment of the present invention can implement each embodiment of the processing method for feasibility inspection on the second device side, and can achieve the same technical effects, and for avoiding repetition, the description is omitted here.
With continued reference to fig. 4, an apparatus according to an embodiment of the present invention is a second apparatus, and includes a transceiver 410, a processor 400, a memory 420, and a program or instructions stored in the memory 420 and executable on the processor 400; the steps in the above processing method applied to the feasibility check on the second device side are implemented when the processor 400 executes the program or the instruction, and the same technical effects can be achieved, so that repetition is avoided and no further description is given here.
The transceiver 410 is configured to receive and transmit data under the control of the processor 400.
Wherein in fig. 4, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 400 and various circuits of memory represented by memory 420, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. Transceiver 410 may be a number of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 400 is responsible for managing the bus architecture and general processing, and the memory 420 may store data used by the processor 400 in performing operations.
The readable storage medium of the embodiment of the present invention stores a program or an instruction, where the program or the instruction, when executed by a processor, implements the steps in the processing method applied to the feasibility check on the first device side as described above, and can achieve the same technical effects, so that repetition is avoided and no further description is given here.
Wherein the processor is a processor in the communication device described in the above embodiment. The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory RAM), a magnetic disk or an optical disk.
In an embodiment of the invention, the modules may be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different bits which, when joined logically together, comprise the module and achieve the stated purpose for the module.
Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Likewise, operational data may be identified within modules and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices.
Where a module may be implemented in software, taking into account the level of existing hardware technology, a module may be implemented in software, and one skilled in the art may, without regard to cost, build corresponding hardware circuitry, including conventional Very Large Scale Integration (VLSI) circuits or gate arrays, and existing semiconductors such as logic chips, transistors, or other discrete components, to achieve the corresponding functions. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
The exemplary embodiments described above are described with reference to the drawings, many different forms and embodiments are possible without departing from the spirit and teachings of the present invention, and therefore, the present invention should not be construed as limited to the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure will be thorough and complete, and will convey the scope of the invention to those skilled in the art. In the drawings, the size of the elements and relative sizes may be exaggerated for clarity. The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. Unless otherwise indicated, a range of values includes the upper and lower limits of the range and any subranges therebetween.
While the foregoing is directed to the preferred embodiments of the present invention, it will be appreciated by those skilled in the art that various modifications and adaptations can be made without departing from the principles of the present invention, and such modifications and adaptations are intended to be comprehended within the scope of the present invention.
Claims (27)
1. A method for processing feasibility check, applied to a first device, the method comprising:
receiving a first request message sent by second equipment;
creating and/or configuring a feasibility check working instance of a first network slice related requirement, and executing a feasibility check flow of the first network slice related requirement.
2. The method according to claim 1, wherein the first request message carries the first network slice related requirements and/or creation request information for indicating creation and/or configuration of the feasibility check working instance.
3. The method of claim 1, further comprising, after creating and/or configuring the feasibility check job instance of the first network slice related requirement:
and sending a first response message to the second device.
4. A method according to claim 3, characterized in that the first response message carries first indication information for indicating the feasibility check working instance and/or attribute information of the feasibility check working instance.
5. The method as recited in claim 1, further comprising:
receiving a second request message sent by the second device;
and acquiring attribute information of the feasibility checking working example.
6. The method according to claim 5, further comprising, after the obtaining the attribute information of the feasibility check working instance:
and sending a second response message to the second device.
7. The method of claim 6, wherein the second response message carries attribute information of the feasibility check working instance.
8. The method according to any one of claims 4 to 7, wherein the attribute information includes at least one of:
the feasibility checking working example is operated;
a working schedule for performing a feasibility check on the first network slice related requirements;
a feasibility check result of performing feasibility check on the first network slice related requirement;
and comment text of the feasibility checking result.
9. The method as recited in claim 1, further comprising:
receiving a third request message sent by the second equipment;
deleting the feasibility checking working example.
10. The method of claim 9, wherein after deleting the feasibility check work instance, further comprising:
and sending a third response message to the second device.
11. The method of claim 10, wherein the third response message carries second indication information indicating that the feasibility check work instance has been deleted.
12. A processing method of feasibility checking, applied to a second device, characterized in that the method comprises:
transmitting a first request message to a first device; wherein the first request message is used to indicate a feasibility check for a first network slice related requirement.
13. The method according to claim 12, wherein the first request message carries the first network slice related requirements and/or creation request information for indicating creation of the feasibility check work instance.
14. The method of claim 12, wherein after the sending the first request message to the first device, further comprises:
and receiving a first response message sent by the first equipment.
15. The method according to claim 14, wherein the first response message carries first indication information for indicating the feasibility check working instance and/or attribute information of the feasibility check working instance.
16. The method of claim 12, wherein after the sending the first request message to the first device, further comprises:
sending a second request message to the first device; the second request message is used for indicating to acquire attribute information of the feasibility check working instance.
17. The method of claim 16, wherein after the sending the second request message to the first device, further comprises:
and receiving a second response message sent by the first device.
18. The method of claim 17, wherein the second response message carries the attribute information.
19. The method according to any one of claims 15 to 18, wherein the attribute information comprises at least one of:
the feasibility checking working example is operated;
a working schedule for performing a feasibility check on the first network slice related requirements;
a feasibility check result of performing feasibility check on the first network slice related requirement;
and comment text of the feasibility checking result.
20. The method as recited in claim 19, further comprising:
If the feasibility checking result in the attribute information is feasible, requesting to configure a network slice and/or a network slice subnet meeting the related requirements of the first network slice from the first equipment;
and if the feasibility checking result in the attribute information is infeasible, updating the first network slice related requirement.
21. The method as recited in claim 12, further comprising:
sending a third request message to the second device; wherein the third request message is used for indicating to delete the feasibility check working instance.
22. The method of claim 21, wherein after the sending the third request message to the second device, further comprises:
and receiving a third response message sent by the first device.
23. The method of claim 22, wherein the third response message carries second indication information indicating that the feasibility check work instance has been deleted.
24. A processing apparatus for feasibility check, applied to a first device, comprising:
the first receiving module is used for receiving a first request message sent by the second equipment;
And the first processing module is used for creating a feasibility checking working example of the first network slice related requirement and executing a feasibility checking flow of the first network slice related requirement.
25. A processing apparatus for feasibility check applied to a second device, comprising:
the first sending module is used for sending a first request message to the first equipment; wherein the first request message is used to indicate a feasibility check for a first network slice related requirement.
26. An apparatus, comprising: a transceiver, a processor, a memory, and a program or instructions stored on the memory and executable on the processor; -wherein, in the case of the device being a first device, the processor, when executing the program or instructions, implements the steps of the method of processing a feasibility check according to any one of claims 1 to 11; the steps in the processing method of the feasibility check of any one of claims 12 to 23 are implemented when the processor executes the program or instructions in case the device is a second device.
27. A readable storage medium having stored thereon a program or instructions, which when executed by a processor, implement the steps in the method of processing a feasibility check according to any one of claims 1 to 23.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111669660.5A CN116418703A (en) | 2021-12-31 | 2021-12-31 | Feasibility inspection processing method, device and equipment |
| PCT/CN2022/143955 WO2023125937A1 (en) | 2021-12-31 | 2022-12-30 | Feasibility check processing method and apparatus, and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111669660.5A CN116418703A (en) | 2021-12-31 | 2021-12-31 | Feasibility inspection processing method, device and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116418703A true CN116418703A (en) | 2023-07-11 |
Family
ID=86998133
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111669660.5A Pending CN116418703A (en) | 2021-12-31 | 2021-12-31 | Feasibility inspection processing method, device and equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN116418703A (en) |
| WO (1) | WO2023125937A1 (en) |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10986540B2 (en) * | 2018-01-12 | 2021-04-20 | Huawei Technologies Co., Ltd. | Network slice provisioning and operation |
| WO2020200479A1 (en) * | 2019-04-05 | 2020-10-08 | Nokia Technologies Oy | Feasibility check for network slice instantiation |
-
2021
- 2021-12-31 CN CN202111669660.5A patent/CN116418703A/en active Pending
-
2022
- 2022-12-30 WO PCT/CN2022/143955 patent/WO2023125937A1/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023125937A1 (en) | 2023-07-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103516690B (en) | A kind of business processing status information query method and device | |
| KR101757417B1 (en) | Method for updating communication node firmware in wireless communication | |
| CN107479984B (en) | Distributed spatial data processing system based on message | |
| CN109600769B (en) | Communication method and device | |
| CN110365508B (en) | Method for instantiating virtual network function and network function virtualization orchestrator | |
| CN113254075B (en) | Instruction execution method, instruction execution device, electronic device, and storage medium | |
| CN114710549A (en) | Dynamic management method, system and service node of network card in container platform | |
| CN109189403B (en) | Operating system OS batch installation method and device and network equipment | |
| CN112583630A (en) | Device management method, device, system, device and storage medium | |
| CN112202879B (en) | Middleware management method and device, electronic equipment and storage medium | |
| CN116418703A (en) | Feasibility inspection processing method, device and equipment | |
| CN110597600A (en) | Method for modifying application configuration parameters of distributed system and distributed system | |
| CN101426220A (en) | Method, apparatus and system for base station cutover | |
| CN114500510A (en) | Request information response method, device, communication equipment and storage medium | |
| JP5502051B2 (en) | Method for processing step execution results in software application control managed objects | |
| CN113518974A (en) | System and method for finding and identifying computing nodes in a network | |
| US11523281B1 (en) | Validating customized user equipment (UE) | |
| US20240073294A1 (en) | Information providing apparatus, computer-readable recording medium, equipment registration system, and equipment registration method | |
| CN110221869B (en) | Method and device for configuring data center operating environment | |
| CN114189384B (en) | Service processing method, device, equipment and storage medium | |
| WO2021226975A1 (en) | Configuration method and apparatus | |
| WO2023050815A1 (en) | Slice service configuration method, network device, network system, and storage medium | |
| CN110896407B (en) | NFVO component configuration management, request forwarding method and request processing device | |
| CN112506580A (en) | Data fusion method and device, storage medium and electronic device | |
| CN114124760A (en) | Network test stream number distribution method and device, network tester and storage medium |
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 |