CN112261676B - Centralized OAM resource allocation method in 5GS - Google Patents
Centralized OAM resource allocation method in 5GS Download PDFInfo
- Publication number
- CN112261676B CN112261676B CN202011082898.3A CN202011082898A CN112261676B CN 112261676 B CN112261676 B CN 112261676B CN 202011082898 A CN202011082898 A CN 202011082898A CN 112261676 B CN112261676 B CN 112261676B
- Authority
- CN
- China
- Prior art keywords
- oam
- resource
- network
- entity
- functional entity
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method, a device and a system for centralized OAM resource allocation in 5GS, which are suitable for an OAM resource allocation end and comprise the steps of receiving a request message sent by a sending end, wherein the request message at least comprises an OAM function supported by a network function entity NF; allocating an independent isolated virtual OAM resource for a network functional entity NF according to an OAM function supported by the network functional entity NF; and if the distribution is successful, sending a corresponding request success message to the sending end. The technical scheme of the invention ensures that the OAM resource allocation end allocates the OAM resources which are isolated by the virtualization container for each network functional entity NF.
Description
Technical Field
The invention relates to the technical field of mobile communication, in particular to a centralized OAM resource allocation method in 5 GS.
Background
5G mobile networks are expected to better provide more optimal support for diverse communication services, service models and end user groups. In order to provide independent network services for various services without independently laying a special network, the 5G network introduces a network slice technology and schedules the resources of the whole network layer by taking the network slice as a unit. The technology virtualizes physical infrastructure resources into a plurality of mutually independent parallel network slices, each network slice subnet realizes logic isolation in equipment, an access network, a transmission network and a core network, and each network slice serves a specific service scene so as to meet the requirements of different service scenes on the difference of bandwidth, time delay, service quality and the like, thereby meeting the diversified requirements of various vertical industries and enhancing network elasticity and self-adaptation. For example, patent No. CN10831038A discloses a method and an apparatus for scheduling network slice resources, which combines an NWDAF network data analysis function to analyze user data in slices, and solves the technical problem in the prior art that the network slice resource utilization rate is low due to poor flexibility of the network slice resource scheduling process.
OAM (Operation Administration and Maintenance) generally divides network management work into 3 types, Operation (Operation), Administration (Administration), and Maintenance (Maintenance), called OAM for short, according to the actual needs of operator network Operation. The operation mainly completes the analysis, prediction, planning and configuration work of the daily network and the business; maintenance is mainly daily operation activities performed on the network and its service test, fault management, and the like. In a 5GS (5G System), OAM may be regarded as a single network element entity, and network function entities nfs (network functions) in the 5GS may be managed in a centralized manner, including CM (configuration management), PM (performance management), FM (error management), CallTrace (user tracking management), OM (operation management), and the like. In the prior art, a centralized OAM entity is also used to manage OAM resources in the entire 5GS network, where a 5GS is a 3GPP system including a 5G-AN (5G access network), a 5GC (5G core network), and a UE (User Equipment). The OAM resources include network bandwidth, memory, hard disk capacity, CPU core number, etc. And OAM is link state management for solving a data link layer. However, each NF uses the general common resources on the centralized OAM entity, and does not allocate an independent OAM resource to a certain NF separately, in this case, once a problem occurs in OAM of one of the NFs, the OAM operation in the entire 5GS may be affected.
If the existing method of allocating an OAM virtual resource to one NF by using the virtualization container (NFV) technology is adopted, although the OAM of each NF can be isolated and the influence of the fault between the OAM of each NF can be reduced, the current flow and specification of dynamically allocating a dynamic OAM resource to each NF according to the TS 3GPP protocol standard does not exist yet, if the NF resource is statically allocated, the allocation and release of each virtual OAM resource needs manual operation, the network flexibility is not high and the network management efficiency is not high.
Disclosure of Invention
The invention mainly aims to provide a centralized OAM resource allocation method in a 5GS (gateway control system), aiming at realizing the dynamic allocation of OAM resources to a network function entity NF (network function entity) sending a request message in the 5 GS.
In order to achieve the above object, the method for centralized OAM resource allocation in 5GS provided by the present invention is applicable to an OAM resource allocation end, and includes the following steps:
s10, receiving a request message sent by a sending end, wherein the request message at least comprises an OAM function supported by a network function entity NF;
s20, allocating virtual OAM resources isolated individually for the network functional entity NF according to the OAM function supported by the network functional entity NF;
and S30, if the distribution is successful, sending a corresponding request success message to the sending end.
Preferably, the OAM resource allocation end is an OAM resource management module set in an OAM host, the sending end is a network function entity NF, and the request message further includes: the current network function entity NF type, where S20 is specifically:
s201, acquiring the quantity of basic resources required by the NF type of the network functional entity and the quantity of resources required by each OAM function supported by the NF type of the network functional entity according to the NF type of the network functional entity;
s202, calculating the total amount S of OAM resources distributed to the network functional entity NF;
s203, comparing the calculated total amount S of the OAM resources with the allocable OAM resource amount, and if the allocable OAM resource amount is less than the calculated total amount S of the OAM resources, sending a resource allocation failure message; and if the allocable OAM resource amount is larger than or equal to the calculated total OAM resource amount S, the OAM resource management module allocates OAM virtual resources for the network functional entity NF.
Preferably, the request message further includes a network function entity NF type, and the method for calculating the total amount S of OAM resources allocated to the network function entity NF in S202 is as follows:
the OAM resource management module calculates according to the type of the network function entity NF in the registration request message and the OAM function supported by the network function entity NF, and acquires the OAM resource required to be allocated by the network function entity NF, wherein the calculation formula is as follows:
n (NF type basis resource) + N (OAM function resource)
N (OAM functional resource) ═ N (cm) + N (pm) + N (fm) +. + N (tracks)
N (cm) or N (NF-type base resource) [ N (bandwidth), N (memory), N (storage space) ],
wherein S is the total amount of virtual OAM resources allocated to the network function entity NF, N (NF type basic resources) is the minimum OAM environment resource required by the network function entity NF, N (OAM function resource) is the total amount of resources required by all OAM functions supported by the NF, N (CM) is the resource quantity required by OAM support configuration management CM, N (PM) is the resource quantity required by OAM support performance management PM, N (FM) is the resource quantity required by OAM support error management FM, N (Trace) is the resource quantity required by OAM support user and equipment tracking management Trace, the resource of each function of N (NF type basic resources) is respectively the basic resource supporting computer operation and network communication, at least comprises memory and storage space, the number of CPU cores and the bandwidth are respectively denoted as N (memory), N (storage space), N (number of CPU cores), and N (bandwidth).
Preferably, when the request message is a registration request message, the registration request message at least further includes a heartbeat time interval of a heartbeat message sent by a network function entity NF, the heartbeat message sent by the network function entity NF at least includes an ID of the network function entity NF and an operation state of the network function entity NF, and after S30, the method further includes:
s40, if the OAM resource management module receives the heartbeat message sent by the network function entity NF in the heartbeat time interval, analyzing the heartbeat message to obtain the ID of the network function entity NF, and inquiring whether the network function entity NF is registered according to the ID of the network function entity NF;
s50, if the OAM resource management module inquires that the network function entity is a non-registered NF, discarding the heartbeat message; if the OAM resource management module inquires that the network function entity is a registered NF, checking the OAM resource operation state distributed by the NF; if the virtual OAM resource operation state of the NF is a normal state, returning a heartbeat response message to the network functional entity NF; if the virtual OAM resource operation state of the NF is a fault state, releasing the virtual OAM resource distributed by the NF and returning to release a complete message;
s60, if the OAM resource management module does not receive the heartbeat message sent by the network functional entity NF within the heartbeat time interval, will release the OAM resource allocated to the network functional entity NF and send an OAM resource release message to the network functional entity NF.
Preferably, when the request message is a deregistration message, the step S30 further includes:
s70, if the OAM resource management module receives the deregistration message of the network functional entity NF, determining whether the network functional entity NF is a registered network functional entity NF;
s80, if the network functional entity NF is not the registered network functional entity NF, abandoning the de-registration message; and if the network functional entity NF is the registered network functional entity NF, releasing the OAM resources distributed by the registered network functional entity NF.
The invention also provides a centralized OAM resource allocation device in 5GS, which is suitable for an OAM resource allocation end and comprises the following components:
a receiving module, configured to receive a request message sent by a sending end, where the request message at least includes an OAM function supported by a network function entity NF;
the distribution module is used for distributing independent isolated virtual OAM resources for the network functional entity NF according to the OAM function supported by the network functional entity NF;
and the response module is used for sending a corresponding request success message to the sending end if the distribution is successful.
Preferably, the OAM resource allocation end is an OAM resource management module set in an OAM host, the sending end is a network function entity NF, and the request message further includes: the current network function entity NF type, the distribution module comprises:
the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring the quantity of basic resources required by the NF type of the network functional entity and the quantity of resources required by each OAM function supported by the network functional entity according to the NF type of the network functional entity;
the calculation unit is used for calculating the total amount S of OAM resources distributed to the network functional entity NF;
the distribution unit is used for comparing the calculated OAM resource total amount S with the distributable OAM resource amount, and if the distributable OAM resource amount is less than the calculated OAM resource total amount S, sending a resource distribution failure message; and if the allocable OAM resource amount is larger than or equal to the calculated total OAM resource amount S, the OAM resource management module allocates OAM virtual resources for the network functional entity NF.
Preferably, when the request message is a registration request message, the registration request message at least further includes a heartbeat time interval at which a network function entity NF sends a heartbeat message, and the heartbeat message sent by the network function entity NF at least includes an ID of the network function entity NF and an operation state of the network function entity NF, and further includes:
the query unit is used for analyzing the heartbeat message to acquire the ID of the network functional entity NF and querying whether the network functional entity NF is registered according to the ID of the network functional entity NF if the OAM resource management module receives the heartbeat message sent by the network functional entity NF in the heartbeat time interval;
the heartbeat response module is used for discarding the heartbeat message if the OAM resource management module inquires that the network function entity is a non-registered NF; if the OAM resource management module inquires that the network function entity is a registered NF, checking the OAM resource operation state distributed by the NF; if the virtual OAM resource operation state of the NF is a normal state, returning a heartbeat response message to the network functional entity NF; if the virtual OAM resource operation state of the NF is a fault state, releasing the virtual OAM resource distributed by the NF and returning to release a complete message;
the first releasing module is configured to release the OAM resource allocated to the network functional entity NF and send an OAM resource release message to the network functional entity NF if the OAM resource management module does not receive the heartbeat message sent by the network functional entity NF within a heartbeat time interval.
Preferably, when the request message is a deregistration message, the method further comprises:
the judging module is used for judging whether the network functional entity NF is a registered network functional entity NF or not if the OAM resource management module receives a deregistration message of the network functional entity NF;
a second release module, configured to discard the de-registration message if the network function entity NF is not a registered network function entity NF; and if the network functional entity NF is the registered network functional entity NF, releasing the OAM resources distributed by the registered network functional entity NF.
The invention also provides a centralized OAM resource distribution system in 5GS, which comprises an OAM host machine for centrally managing OAM resources and a plurality of network function entities NF, wherein the OAM host machine is provided with an OAM resource management module, and the OAM resource management module dynamically distributes the OAM resources to the network function entities NF sending the request message according to the OAM functions supported by the network function entities NF.
The technical scheme of the invention adopts NFV technology, so that an OAM resource allocation end allocates independent OAM resources isolated by a virtualization container for each network function entity NF, further, network function entity NF registration request messages, heartbeat messages and de-registration messages are provided to communicate with a resource management module of OAM, the OAM resource management module allocates resources required by OAM operation for newly added network function entities in the network in time, the resources are released for the faulted NF and the de-registered NF, and the dynamic scheduling of the OAM virtual resources is realized.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the structures shown in the drawings without creative efforts.
FIG. 1 is a flow chart of a method according to an embodiment of the method of the present invention;
FIG. 2 is a flowchart illustrating a method refinement of the method of S20;
FIG. 3 is a flow chart of a method according to another embodiment of the method of the present invention;
FIG. 4 is a schematic flow chart of a method according to yet another embodiment of the method of the present invention;
FIG. 5 is a functional block diagram of an embodiment of an apparatus module according to the present invention;
FIG. 6 is a detailed diagram of functional modules of an embodiment of the assignment module of the present invention;
FIG. 7 is a functional block diagram of another embodiment of the apparatus of the present invention;
FIG. 8 is a functional block diagram of another embodiment of the apparatus of the present invention;
FIG. 9 is a system block diagram of an embodiment of the system of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that, if directional indications (such as up, down, left, right, front, and back … …) are involved in the embodiment of the present invention, the directional indications are only used to explain the relative positional relationship between the components, the movement situation, and the like in a specific posture (as shown in the drawing), and if the specific posture is changed, the directional indications are changed accordingly.
In addition, if there is a description of "first", "second", etc. in an embodiment of the present invention, the description of "first", "second", etc. is for descriptive purposes only and is not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In addition, technical solutions between various embodiments may be combined with each other, but must be realized by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope of the present invention.
The centralized OAM resource allocation method in 5GS provided by the invention is suitable for an OAM resource allocation end, and comprises the following steps:
s10, receiving a request message sent by a sending end, wherein the request message at least comprises an OAM function supported by a network function entity NF;
s20, allocating virtual OAM resources isolated individually for the network functional entity NF according to the OAM function supported by the network functional entity NF;
and S30, if the distribution is successful, sending a request success message to the sending end, wherein the request success message at least comprises the heartbeat time after the sending end negotiates with the OAM resource distribution end, and the IP address and the port number of the distributed virtual OAM resource.
In the embodiment of the present invention, as shown in fig. 1, by using the NFV technology, the OAM resource allocation end allocates an individual OAM resource isolated by a virtualization container to each network functional entity NF in the technical solution of the present invention. When a sending end in the 5GS sends a request message with an OAM function supported by the network function entity NF to the centralized OAM resource allocation end, the OAM resource allocation end allocates an OAM virtual resource according to the OAM function supported by the network function entity NF, and if the resource allocation is successful, returns a request success message. OAM functions supported by the network function entity NF comprise configuration management CM, performance management PM, error management FM, operation management OM, user tracking management (CallTrace) and the like, an OAM resource distribution end manages OAM resources in a centralized mode, each requested network function entity NF is distributed with virtualized and independently isolated OAM resources so as to manage the operation process of each network function entity NF respectively, and the condition that the operation of the whole OAM system of the 5GS is influenced by the fact that the OAM of a certain network function entity NF in the 5GS is in a problem is prevented. The invention realizes the dynamic allocation of OAM resources to each NF by matching a series of communication processes with resource allocation.
Preferably, the OAM resource allocation end is an OAM resource management module set in an OAM host, the sending end is a network functional entity NF, and the request message further includes: the current network function entity NF type, where S20 is specifically:
s201, acquiring the quantity of basic resources required by the NF type of the network functional entity and the quantity of resources required by each OAM function supported by the NF type of the network functional entity according to the NF type of the network functional entity;
s202, calculating the total amount S of OAM resources distributed to the network functional entity NF;
s203, comparing the calculated total amount S of the OAM resources with the allocable OAM resource amount, and if the allocable OAM resource amount is less than the calculated total amount S of the OAM resources, sending a resource allocation failure message; and if the allocable OAM resource amount is larger than or equal to the calculated total OAM resource amount S, the OAM resource management module allocates OAM virtual resources for the network functional entity NF.
In the embodiment of the present invention, as shown in fig. 2, in a 5GS system, an OAM resource management module is provided in a host of an OAM resource in the present invention, and is configured to allocate a corresponding OAM virtual resource to a network function entity NF that is qualified in a request. An OAM resource management module acquires a network function entity NF type of a request message sent by a network function entity NF, acquires the quantity of basic resources required by the network function entity NF type and the quantity of resources required by each OAM function supported by the network function entity NF according to the network function entity NF, calculates the total OAM resource quantity S allocated to the network function entity NF, compares the acquired total OAM resource quantity S with the existing distributable OAM resource quantity S of centralized OAM, and if the distributable OAM resource quantity is smaller than the total OAM resource quantity value, the resource distribution fails due to insufficient resources, returns a resource distribution failure message, and puts the reason value on the message (the reason value is a character string which indicates the failure reason, such as insufficient distributable virtual resources, wrong NF registration request message, wrong other reasons and the like). And if the resources are sufficiently allocated, the OAM resource management module allocates OAM virtual resources for the network functional entity NF.
Preferably, the request message further includes a network function entity NF type, and the method for calculating the total amount S of OAM resources allocated to the network function entity NF in S202 is as follows:
the OAM resource management module calculates according to the type of the network function entity NF in the registration request message and the OAM function supported by the network function entity NF, and acquires the OAM resource required to be allocated by the network function entity NF, wherein the calculation formula is as follows:
n (NF type basis resource) + N (OAM function resource)
N (OAM functional resource) ═ N (cm) + N (pm) + N (fm) +. + N (tracks)
N (cm) or N (NF-type base resource) [ N (bandwidth), N (memory), N (storage space) ],
wherein S is the total amount of virtual OAM resources allocated to the network function entity NF, N (NF type basic resources) is the minimum OAM environment resource required by the network function entity NF, N (OAM function resource) is the total amount of resources required by all OAM functions supported by the NF, N (CM) is the resource quantity required by OAM support configuration management CM, N (PM) is the resource quantity required by OAM support performance management PM, N (FM) is the resource quantity required by OAM support error management FM, N (Trace) is the resource quantity required by OAM support user and equipment tracking management Trace, the resource of each function of N (NF type basic resources) is respectively the basic resource supporting computer operation and network communication, at least comprises memory and storage space, the number of CPU cores and the bandwidth are respectively denoted as N (memory), N (storage space), N (number of CPU cores), and N (bandwidth).
Preferably, when the request message is a registration request message, the registration request message at least further includes a heartbeat time interval of a heartbeat message sent by a network function entity NF, the heartbeat message sent by the network function entity NF at least includes an ID of the network function entity NF and an operation state of the network function entity NF, and after S30, the method further includes:
s40, if the OAM resource management module receives the heartbeat message sent by the network function entity NF in the heartbeat time interval, analyzing the heartbeat message to obtain the ID of the network function entity NF, and inquiring whether the network function entity NF is registered according to the ID of the network function entity NF;
s50, if the OAM resource management module inquires that the network function entity is a non-registered NF, discarding the heartbeat message; if the OAM resource management module inquires that the network function entity is a registered NF, checking the OAM resource operation state distributed by the NF; if the virtual OAM resource operation state of the NF is a normal state, returning a heartbeat response message to the network functional entity NF; if the virtual OAM resource operation state of the NF is a fault state, releasing the virtual OAM resource distributed by the NF and returning to release a complete message;
s60, if the OAM resource management module does not receive the heartbeat message sent by the network functional entity NF within the heartbeat time interval, will release the OAM resource allocated to the network functional entity NF and send an OAM resource release message to the network functional entity NF.
In the embodiment of the present invention, as shown in fig. 3, a registration message sent by a network function entity NF carries an NF ID, an NF type, a supported OAM function, a heartbeat time interval, a public land mobile network identification number PLMN ID, and the like, when the NF sends a heartbeat message to an OAM resource management module, the OAM resource management module may determine an identity of the NF according to the NF ID (the NF ID is a unique standard of the NF, the NF ID is a UUID, and a UUID generated by a certain NF at a certain time is a unique value) according to a 3GPP protocol, if the NF cannot be found out by the query, discard the message, if the NF is found, check whether a virtual OAM running state of the NF is normal, and return an OAM running state and a load condition of the NF to the NF and in the message, if the virtual OAM resource running state of the NF is a fault state, release the virtual OAM resource and return a release complete message.
Preferably, when the request message is a deregistration message, the step S30 further includes:
s70, if the OAM resource management module receives the deregistration message of the network functional entity NF, determining whether the network functional entity NF is a registered network functional entity NF;
s80, if the network functional entity NF is not the registered network functional entity NF, abandoning the de-registration message; and if the network functional entity NF is the registered network functional entity NF, releasing the OAM resources distributed by the registered network functional entity NF.
In the embodiment of the present invention, the network function entity NF includes the NF ID of the NF in the deregistration message sent to the OAM resource management module, and after receiving the message, the OAM resource management module releases the OAM virtual resource of the NF and returns a resource release complete message.
The present invention further provides a device for centralized OAM resource allocation in 5GS, which at least has all the benefits brought by the technical solutions of the above embodiments because the device employs all the technical solutions of all the above embodiments, and details are not repeated here. It includes:
a receiving module 10, configured to receive a request message sent by a sending end, where the request message at least includes an OAM function supported by a network function entity NF;
an allocating module 20, configured to allocate an individually isolated virtual OAM resource to a network functional entity NF according to an OAM function supported by the network functional entity NF;
and the response module 30 is configured to send a corresponding request success message to the sending end if the allocation is successful.
Preferably, the OAM resource allocation end is an OAM resource management module set in an OAM host, the sending end is a network functional entity NF, and the allocation module 20 includes:
an obtaining unit 201, configured to obtain, according to a network function entity NF type, a quantity of basic resources required by the network function entity NF type and a quantity of resources required by each OAM function supported by the network function entity NF type;
a calculating unit 202, configured to calculate a total amount S of OAM resources allocated to the network functional entity NF;
an allocating unit 203, configured to compare the calculated OAM resource total amount S with an allocable OAM resource amount, and send a resource allocation failure message if the allocable OAM resource amount is less than the calculated OAM resource total amount S; and if the allocable OAM resource amount is larger than or equal to the calculated total OAM resource amount S, the OAM resource management module allocates OAM virtual resources for the network functional entity NF.
Preferably, when the request message is a registration request message, the registration request message at least further includes a heartbeat time interval at which a network function entity NF sends a heartbeat message, and the heartbeat message sent by the network function entity NF at least includes an ID of the network function entity NF and an operation state of the network function entity NF, and further includes:
the query module 40 is configured to, if the OAM resource management module receives a heartbeat message sent by the network function entity NF within a heartbeat time interval, parse the heartbeat message to obtain an ID of the network function entity NF, and query whether the network function entity NF is registered according to the ID of the network function entity NF;
a heartbeat response module 50, configured to discard the heartbeat message if the OAM resource management module queries that the network function entity NF is unregistered; if the OAM resource management module inquires that the network functional entity NF is registered, checking the OAM resource operation state and the load data distributed by the NF, and sending a heartbeat response message to the network functional entity NF, wherein the heartbeat response message at least comprises the OAM resource operation state and the load data distributed by the network functional entity NF;
the first releasing module 60 is configured to release the OAM resource allocated to the network functional entity NF and send an OAM resource release message to the network functional entity NF if the OAM resource management module does not receive the heartbeat message sent by the network functional entity NF within the heartbeat time interval.
Preferably, when the request message is a deregistration message, the method further comprises:
a determining module 70, configured to determine whether the network function entity NF is a registered network function entity NF if the OAM resource management module receives a deregistration message of the network function entity NF;
a second releasing module 80, configured to discard the de-registration message if the network function entity NF is not a registered network function entity NF; and if the network functional entity NF is the registered network functional entity NF, releasing the OAM resources distributed by the registered network functional entity NF.
The invention also provides a centralized OAM resource distribution system in 5GS, which comprises an OAM host machine for centrally managing OAM resources and a plurality of network function entities NF, wherein the OAM host machine is provided with an OAM resource management module, and the OAM resource management module dynamically distributes the OAM resources to the network function entities NF sending the request message according to the OAM functions supported by the network function entities NF.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention, and all modifications and equivalents of the present invention, which are made by the contents of the present specification and the accompanying drawings, or directly/indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A method for centralized operation, management and maintenance (OAM) resource allocation in 5GS is suitable for an OAM resource allocation end, and is characterized by comprising the following steps:
s10, receiving a request message sent by a sending end, wherein the request message at least comprises an OAM function supported by a network function entity NF;
s20, allocating virtual OAM resources isolated individually for the network functional entity NF according to the OAM function supported by the network functional entity NF;
and S30, if the distribution is successful, sending a corresponding request success message to the sending end.
2. The method for centralized OAM resource allocation in 5GS according to claim 1, adapted to an OAM resource allocation end, where the OAM resource allocation end is an OAM resource management module set in an OAM host, the sending end is a network function entity NF, and the request message further includes: the current network function entity NF type, where S20 is specifically:
s201, acquiring the quantity of basic resources required by the NF type of the network functional entity and the quantity of resources required by each OAM function supported by the NF type of the network functional entity according to the NF type of the network functional entity;
s202, calculating the total amount S of OAM resources distributed to the network functional entity NF;
s203, comparing the calculated total amount S of the OAM resources with the allocable OAM resource amount, and if the allocable OAM resource amount is less than the calculated total amount S of the OAM resources, sending a resource allocation failure message; and if the allocable OAM resource amount is larger than or equal to the calculated total OAM resource amount S, the OAM resource management module allocates OAM virtual resources for the network functional entity NF.
3. The method for centralized OAM resource allocation in 5GS according to claim 2, adapted to an OAM resource allocation end, wherein the request message further includes a network function entity NF type, and the method for calculating the total amount S of OAM resources allocated to the network function entity NF in S202 is:
the OAM resource management module calculates according to the type of the network function entity NF in the registration request message and the OAM function supported by the network function entity NF, and acquires the OAM resource required to be allocated by the network function entity NF, wherein the calculation formula is as follows:
n (NF type basis resource) + N (OAM function resource)
N (OAM function resource) ═ N (cm) + N (pm) + N (fm) +. + N (trace)
N (cm) or N (NF-type base resource) [ N (bandwidth), N (memory), N (storage space) ],
wherein S is the total amount of virtual OAM resources allocated to the network function entity NF, N (NF type basic resources) is the minimum OAM environment resource required by the network function entity NF, N (OAM function resource) is the total amount of resources required by all OAM functions supported by the NF, N (CM) is the resource quantity required by OAM support configuration management CM, N (PM) is the resource quantity required by OAM support performance management PM, N (FM) is the resource quantity required by OAM support error management FM, N (Trace) is the resource quantity required by OAM support user and equipment tracking management Trace, the resource of each function of N (NF type basic resources) is respectively the basic resource supporting computer operation and network communication, at least comprises memory and storage space, the number of CPU cores and the bandwidth are respectively denoted as N (memory), N (storage space), N (number of CPU cores), and N (bandwidth).
4. The method for centralized OAM resource allocation in 5GS according to claim 2, wherein when the request message is a registration request message, the registration request message further includes at least a heartbeat interval during which a network function entity NF sends a heartbeat message, the heartbeat message sent by the network function entity NF includes at least an ID of the network function entity NF and an operating status of the network function entity NF, and after S30, the method further includes:
s40, if the OAM resource management module receives the heartbeat message sent by the network function entity NF in the heartbeat time interval, analyzing the heartbeat message to obtain the ID of the network function entity NF, and inquiring whether the network function entity NF is registered according to the ID of the network function entity NF;
s50, if the OAM resource management module inquires that the network function entity is a non-registered NF, discarding the heartbeat message; if the OAM resource management module inquires that the network function entity is a registered NF, checking the OAM resource operation state distributed by the NF; if the virtual OAM resource operation state of the NF is a normal state, returning a heartbeat response message to the network functional entity NF; if the virtual OAM resource operation state of the NF is a fault state, releasing the virtual OAM resource distributed by the NF and returning to release a complete message;
s60, if the OAM resource management module does not receive the heartbeat message sent by the network functional entity NF within the heartbeat time interval, will release the OAM resource allocated to the network functional entity NF and send an OAM resource release message to the network functional entity NF.
5. The method for centralized OAM resource allocation in a 5GS according to claim 2, wherein when said request message is a deregistration message, further comprising after said S30:
s70, if the OAM resource management module receives the deregistration message of the network functional entity NF, determining whether the network functional entity NF is a registered network functional entity NF;
s80, if the network functional entity NF is not the registered network functional entity NF, abandoning the de-registration message; and if the network functional entity NF is the registered network functional entity NF, releasing the OAM resources distributed by the registered network functional entity NF.
6. A device for centralized operation, administration and maintenance (OAM) resource allocation in 5GS is applicable to an OAM resource allocation end, and is characterized by comprising:
a receiving module, configured to receive a request message sent by a sending end, where the request message at least includes an OAM function supported by a network function entity NF;
the distribution module is used for distributing independent isolated virtual OAM resources for the network functional entity NF according to the OAM function supported by the network functional entity NF;
and the response module is used for sending a corresponding request success message to the sending end if the distribution is successful.
7. The device for centralized OAM resource allocation in 5GS according to claim 6, wherein the OAM resource allocating end is an OAM resource management module disposed in an OAM host, the sending end is a network function entity NF, and the request message further includes: the current network function entity NF type, the distribution module comprises:
the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring the quantity of basic resources required by the NF type of the network functional entity and the quantity of resources required by each OAM function supported by the network functional entity according to the NF type of the network functional entity;
the calculation unit is used for calculating the total amount S of OAM resources distributed to the network functional entity NF;
the distribution unit is used for comparing the calculated OAM resource total amount S with the distributable OAM resource amount, and if the distributable OAM resource amount is less than the calculated OAM resource total amount S, sending a resource distribution failure message; and if the allocable OAM resource amount is larger than or equal to the calculated total OAM resource amount S, the OAM resource management module allocates OAM virtual resources for the network functional entity NF.
8. The apparatus for centralized OAM resource allocation in 5GS according to claim 6, wherein when the request message is a registration request message, the registration request message further includes at least a heartbeat interval during which a network function entity NF sends a heartbeat message, and the heartbeat message sent by the network function entity NF includes at least an ID of the network function entity NF and an operating status of the network function entity NF, further comprising:
the query unit is used for analyzing the heartbeat message to acquire the ID of the network functional entity NF and querying whether the network functional entity NF is registered according to the ID of the network functional entity NF if the OAM resource management module receives the heartbeat message sent by the network functional entity NF in the heartbeat time interval;
the heartbeat response module is used for discarding the heartbeat message if the OAM resource management module inquires that the network function entity is a non-registered NF; if the OAM resource management module inquires that the network function entity is a registered NF, checking the OAM resource operation state distributed by the NF; if the virtual OAM resource operation state of the NF is a normal state, returning a heartbeat response message to the network functional entity NF; if the virtual OAM resource operation state of the NF is a fault state, releasing the virtual OAM resource distributed by the NF and returning to release a complete message;
the first releasing module is configured to release the OAM resource allocated to the network functional entity NF and send an OAM resource release message to the network functional entity NF if the OAM resource management module does not receive the heartbeat message sent by the network functional entity NF within a heartbeat time interval.
9. The apparatus for centralized OAM resource allocation in a 5GS of claim 6, wherein when said request message is a deregistration message, further comprising:
the judging module is used for judging whether the network functional entity NF is a registered network functional entity NF or not if the OAM resource management module receives a deregistration message of the network functional entity NF;
a second release module, configured to discard the de-registration message if the network function entity NF is not a registered network function entity NF; and if the network functional entity NF is the registered network functional entity NF, releasing the OAM resources distributed by the registered network functional entity NF.
10. A centralized operation, management and maintenance OAM resource distribution system in 5GS is characterized by comprising an OAM host machine for managing OAM resources in a centralized mode and a plurality of network function entities NF, wherein an OAM resource management module is arranged in the OAM host machine, and the OAM resource management module dynamically distributes the OAM resources to the network function entities NF sending request messages according to OAM functions supported by the network function entities NF.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011082898.3A CN112261676B (en) | 2020-10-10 | 2020-10-10 | Centralized OAM resource allocation method in 5GS |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011082898.3A CN112261676B (en) | 2020-10-10 | 2020-10-10 | Centralized OAM resource allocation method in 5GS |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112261676A CN112261676A (en) | 2021-01-22 |
| CN112261676B true CN112261676B (en) | 2021-07-09 |
Family
ID=74241825
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011082898.3A Active CN112261676B (en) | 2020-10-10 | 2020-10-10 | Centralized OAM resource allocation method in 5GS |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112261676B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105284094A (en) * | 2014-05-15 | 2016-01-27 | 华为技术有限公司 | Network function virtualization network system, data processing method and device |
| CN106954267A (en) * | 2017-04-14 | 2017-07-14 | 北京邮电大学 | A kind of method for managing resource cut into slices based on wireless network |
| CN107786360A (en) * | 2016-08-30 | 2018-03-09 | 中兴通讯股份有限公司 | Network function virtualized management method and device |
| CN108011732A (en) * | 2016-11-02 | 2018-05-08 | 中国电信股份有限公司 | Method, controller and the system of configuration service resource |
| CN108243205A (en) * | 2016-12-23 | 2018-07-03 | 上海诺基亚贝尔股份有限公司 | A kind of method, equipment and system for being used to control cloud platform resource allocation |
| CN108900357A (en) * | 2018-08-01 | 2018-11-27 | 重庆邮电大学 | A kind of network slice virtual resource allocation method virtualized under C-RAN network |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10880176B2 (en) * | 2016-09-09 | 2020-12-29 | Huawei Technologies Co., Ltd. | Method and apparatus for network slicing |
-
2020
- 2020-10-10 CN CN202011082898.3A patent/CN112261676B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105284094A (en) * | 2014-05-15 | 2016-01-27 | 华为技术有限公司 | Network function virtualization network system, data processing method and device |
| CN107786360A (en) * | 2016-08-30 | 2018-03-09 | 中兴通讯股份有限公司 | Network function virtualized management method and device |
| CN108011732A (en) * | 2016-11-02 | 2018-05-08 | 中国电信股份有限公司 | Method, controller and the system of configuration service resource |
| CN108243205A (en) * | 2016-12-23 | 2018-07-03 | 上海诺基亚贝尔股份有限公司 | A kind of method, equipment and system for being used to control cloud platform resource allocation |
| CN106954267A (en) * | 2017-04-14 | 2017-07-14 | 北京邮电大学 | A kind of method for managing resource cut into slices based on wireless network |
| CN108900357A (en) * | 2018-08-01 | 2018-11-27 | 重庆邮电大学 | A kind of network slice virtual resource allocation method virtualized under C-RAN network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112261676A (en) | 2021-01-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110120988B (en) | Address management method, equipment and system | |
| US6898635B2 (en) | Mobile communication system and method of selecting server in mobile communication system | |
| US9465641B2 (en) | Selecting cloud computing resource based on fault tolerance and network efficiency | |
| CN114205844B (en) | Network service management method, device and system | |
| US20100077250A1 (en) | Virtualization based high availability cluster system and method for managing failure in virtualization based high availability cluster system | |
| US20210320845A1 (en) | Network function nf management method and nf management device | |
| CN111083181B (en) | Equipment scheduling method, gateway and system for large-scale access to Internet of things | |
| CN106301822B (en) | Method, device and system for configuring AP | |
| CN102137014A (en) | Resource management method, system and resource manager | |
| WO2016095524A1 (en) | Resource allocation method and apparatus | |
| CN107005452B (en) | Network function virtualization resource processing method and virtual network function manager | |
| CN109561450B (en) | Interaction method and device for load information | |
| CN108009018B (en) | Load adjusting method, device and system | |
| CN109981795B (en) | Resource request scheduling method and device | |
| US20240118935A1 (en) | Pod deployment method and apparatus | |
| WO2021032100A1 (en) | Network element allocation method and apparatus | |
| JP2020028060A (en) | Communication system and communication method | |
| CN101308467A (en) | Task processing method and device | |
| CN112261676B (en) | Centralized OAM resource allocation method in 5GS | |
| US20230074779A1 (en) | Service relations in provisioning of communication service instance | |
| CN106060182B (en) | A kind of address distribution method and device | |
| KR20130063867A (en) | Method for utilizing network resource in machine-to-machine cloud environment communication and the system thereof | |
| US20220141913A1 (en) | Core network for mobile communication system | |
| US20240334423A1 (en) | Adaptive distributed unit (du) scheduler | |
| CN113254207B (en) | Identification code generation method, device, server 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |