CN116916345A - Network configuration method, NSRMF entity, NSMF entity and storage medium - Google Patents

Network configuration method, NSRMF entity, NSMF entity and storage medium Download PDF

Info

Publication number
CN116916345A
CN116916345A CN202310597813.2A CN202310597813A CN116916345A CN 116916345 A CN116916345 A CN 116916345A CN 202310597813 A CN202310597813 A CN 202310597813A CN 116916345 A CN116916345 A CN 116916345A
Authority
CN
China
Prior art keywords
entity
requirement
network
nsrmf
description field
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
Application number
CN202310597813.2A
Other languages
Chinese (zh)
Inventor
郭楚怡
张敏
孟琳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
Xian Jiaotong University
China Mobile Communications Ltd Research Institute
Original Assignee
China Mobile Communications Group Co Ltd
Xian Jiaotong University
China Mobile Communications Ltd Research Institute
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by China Mobile Communications Group Co Ltd, Xian Jiaotong University, China Mobile Communications Ltd Research Institute filed Critical China Mobile Communications Group Co Ltd
Priority to CN202310597813.2A priority Critical patent/CN116916345A/en
Publication of CN116916345A publication Critical patent/CN116916345A/en
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/02Arrangements for optimising operational condition

Abstract

The embodiment of the application provides a network configuration method, which comprises the following steps: after receiving the network slice requirement information, the NSMF entity decomposes the network slice requirement information into subnet slice requirement information; the NSMF entity transmits a requirement description field and NSST ID corresponding to the subnet slice requirement information to an NSRMF entity of the transmission network, and if the NSRMF entity judges that the pre-stored logic channel instance does not meet the configuration condition according to the requirement description field and NSST ID, a first operation instruction is generated based on the requirement description field and NSST ID; the NSRMF entity calls the transport network slice management function interface to issue a first operation instruction so as to complete network configuration of the transport network through the transport network slice management function, thereby realizing automatic unified docking and further reducing the complexity of management and interface flow.

Description

Network configuration method, NSRMF entity, NSMF entity and storage medium
Technical Field
The present application relates to the field of communications technologies, and in particular, to a network configuration method, an NSRMF entity, an NSMF entity, and a storage medium.
Background
In the current slicing subnet management, the end-to-end service requirement needs to be decomposed into requirements for a wireless network, a core network and a transmission network, the decomposed requirements can be issued to the subnet in a mode of description of a requirement description field (Slice Profile) and a network slicing service identifier (S-NSSAI), and the requirements are met through operation of network slicing subnet instances (Network Slice Subnet Instance, NSSI), but the requirements are not maintained according to the dimension of the S-NSSAI on the transmission side; when the interface is called, the operation objects of the wireless and core network slice sub-network management functions (Network Slice Subnet Management Function, NSSMF) are NSSI or match the requirement of S-NSSAI, and the operations such as creation, modification, deletion and the like of the transmission network slice management functions are aimed at maintaining a logic channel instead of S-NSSAI, so that the level difference exists in the requirement decomposition and the call of the sub-network NSSMF, the complexity of management and interface flow is further increased, and the problem that automatic unified interface docking cannot be realized exists.
Disclosure of Invention
The embodiment of the application provides a network configuration method, an NSRMF entity, an NSMF entity and a storage medium, which can call a sub-network NSSMF through a unified interface, thereby reducing the complexity of management and interface flow.
The technical scheme of the embodiment of the application is realized as follows:
in a first aspect, an embodiment of the present application provides a network configuration method, where the method is applied to an NSRMF entity, and the method includes:
the NSRMF entity receives a requirement description field and NSST ID issued by an NSMF entity;
if the NSRMF entity judges that the pre-stored logic channel instance does not meet the configuration condition according to the requirement description field and the NSST ID, generating a first operation instruction based on the requirement description field and the NSST ID;
the NSRMF entity invokes a transport network slice management function interface to issue the first operation instruction so as to complete network configuration of a transport network through the transport network slice management function.
In a second aspect, an embodiment of the present application provides a network configuration method, where the method is applied to an NSMF entity, and the method includes:
after receiving the network slice requirement information, the NSMF entity decomposes the network slice requirement information into subnet slice requirement information;
And the NSMF entity transmits a requirement description field and NSST ID corresponding to the subnet slice requirement information to an NSRMF entity of a transmission network, so that the NSRMF entity generates and transmits a first operation instruction based on the requirement description field and NSST ID.
In a third aspect, an embodiment of the present application provides an NSRMF entity, where the NSRMF entity includes: a receiving unit, a generating unit, a first issuing unit,
the receiving unit is configured to receive, by the NSRMF entity, a requirement description field and an NSST ID issued by the NSMF entity;
the generating unit is configured to generate a first operation instruction based on the requirement description field and the NSST ID if the NSRMF entity determines that the pre-stored logical channel instance does not meet the configuration condition according to the requirement description field and the NSST ID;
the first issuing unit is configured to invoke a transport network slice management function interface by the NSRMF entity to issue the first operation instruction, so as to complete network configuration of a transport network through the transport network slice management function.
In a fourth aspect, an embodiment of the present application provides an NSRMF entity, where the NSRMF entity includes: a first processor and a first memory; wherein, the liquid crystal display device comprises a liquid crystal display device,
The first memory is used for storing a computer program capable of running on the processor;
the first processor is configured to execute the network configuration method as described above when the computer program is run.
In a fifth aspect, an embodiment of the present application provides an NSMF entity, including: a decomposing unit, a second issuing unit,
the decomposing unit is configured to decompose the network slice requirement information into subnet slice requirement information after the NSMF entity receives the network slice requirement information;
the second issuing unit is configured to issue, by the NSMF entity, a requirement description field and an NSST ID corresponding to the subnet slice requirement information to an NSRMF entity of the transport network, so that the NSRMF entity generates and issues a first operation instruction based on the requirement description field and the NSST ID.
In a sixth aspect, an embodiment of the present application provides an NSMF entity, including: a second processor and a second memory; wherein, the liquid crystal display device comprises a liquid crystal display device,
the second memory is used for storing a computer program capable of running on the processor;
the second processor is configured to execute the network configuration method as described above when the computer program is run.
In a seventh aspect, an embodiment of the present application provides a computer readable storage medium, wherein the storage medium has stored thereon computer program code which, when executed by a computer, implements a network configuration method as described above.
The embodiment of the application provides a network configuration method, an NSRMF entity, an NSMF entity and a storage medium, wherein the method comprises the following steps: the NSRMF entity receives a requirement description field and NSST ID issued by the NSMF entity; if the NSRMF entity judges that the pre-stored logic channel instance does not meet the configuration conditions according to the requirement description field and NSST ID, generating a first operation instruction based on the requirement description field and NSST ID; the NSRMF entity invokes a transport network slice management function interface to issue a first operation instruction to complete network configuration of the transport network through the transport network slice management function. Therefore, the NSRMF entity may first receive the requirement description field and the nst ID issued by the NSMF entity, and if the NSRMF entity determines that the pre-stored logical channel instance does not meet the configuration condition according to the requirement description field and the nst ID, then may generate the first operation instruction based on the requirement description field and the nst ID; the NSRMF entity may call the transport network slice management function interface to issue the first operation instruction, so that the transport network slice management function completes the network configuration of the transport network, that is, the NSRMF entity provided by the present application may receive the information issued by the NSMF entity interface, so as to complete the subsequent network configuration of the transport network, and the NSMF entity interface may also call the NSSMF entity of the wireless network and the NSSMF entity of the core network indiscriminately, that is, call the NSSMF of the core network, the NSSMF of the wireless network and the NSRMF of the transport network through the unified NSMF entity interface, so as to implement automatic unified interfacing, and further reduce complexity of management and interface flow.
Drawings
Fig. 1 is a schematic diagram of a network slice, a network slice instance and a subnet instance according to an embodiment of the present application;
fig. 2 is a schematic diagram of a network configuration method according to an embodiment of the present application;
fig. 3 is a schematic diagram of a network configuration system according to an embodiment of the present application;
fig. 4 is a schematic diagram of NSST content on the transmission side according to an embodiment of the present application;
fig. 5 is a schematic diagram of a second network configuration method according to an embodiment of the present application;
fig. 6 is a schematic diagram of a network configuration system according to a second embodiment of the present application;
fig. 7 is a schematic diagram III of a network configuration method according to an embodiment of the present application;
fig. 8 is a schematic diagram illustrating interaction of management functions of network slices according to an embodiment of the present application;
fig. 9 is a schematic diagram of a network configuration method according to an embodiment of the present application;
fig. 10 is a schematic diagram of a composition structure of an NSRMF entity according to an embodiment of the present application;
fig. 11 is a schematic diagram of a second component structure of an NSRMF entity according to an embodiment of the present application;
fig. 12 is a schematic diagram of a composition structure of an NSMF entity according to an embodiment of the present application;
fig. 13 is a schematic diagram of a second structure of an NSMF entity according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. It is to be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to be limiting. It should be noted that, for convenience of description, only a portion related to the related application is shown in the drawings.
In the current fifth generation mobile communication technology (5th Generation Mobile Communication,5G) end-to-end network slice management scheme, a communication service management function (Communication Service Management Function, CSMF) performs slice demand management on a user side, a network slice management function (Network Slice Management Function, NSMF) provides management on a network slice instance (Network Slice Instance, NSI), and a network slice subnet management function (Network Slice Subnet Management Function, NSSMF) manages network slice subnet instances (Network Slice Subnet Instance, NSSI) of each domain (wireless, core, transport).
Network slice example: may be a truly functioning logical network that meets certain network characteristics or service requirements, and a network slice instance may provide one or more network services, and the network slice instance may be created from a network slice template.
In the whole network slice life cycle management, in order to realize different functions, the slice requirements of users and the guarantee of service level agreements (Service Level Agreement, SLA) are met, a network slice creation flow, an activation flow, an update flow and the like exist, and an application program interface (Application Program Interface, API) between different management functions is called to finish the flows.
Network slice: a network deployed on a physical or virtual infrastructure to support logical separation of a particular network capability from network characteristics may include an entire network including an access network, a transport network, a core network, and an application server, an end-to-end (E2E) entire network, and a network slice may be any combination of terminal devices, access networks, transport networks, core networks, and application servers.
Each time a user issues a new requirement or updates a requirement, an end-to-end operation is triggered, after the NSMF receives the requirement of the user, the NSMF can send the requirement of the subnet in a mode of creating, distributing, modifying or deleting NSI and the like, invokes NSSMF of each subdomain, triggers NSSI operation and the like, and meets the requirement of the user.
In the current network management function, according to network domain division, there are wireless network NSSMF, core network NSSMF and transport network slice management function, accept the decomposition of end-to-end demand corresponding to each domain demand, and divide NSSI of the corresponding network domain; fig. 1 is a schematic diagram of Network slicing, network slicing instance and subnet instance relationships, as shown in fig. 1, for a wireless Network (Access Network) and a Core Network (Core Network), a management hierarchy of slicing is NSSI to an underlying Network, each slice requirement is carried by one to a plurality of end-to-end slicing NSIs, one NSI includes NSSI of the wireless Network and the Core Network, each domain NSSI is mapped to a respective Network, wherein communication service instance represents a communication service instance, TN supporting connectivity may refer to support connectivity of a transmission Network.
The transmission network bears the pull-through of the wireless network and the core network, and distinguishes logical channels on the basis of the underlying physical network, and different logical channels have different SLAs to meet different slicing service requirements. The transmission side internet protocol (Internet Protocol, IP)/Multi-protocol label switching (Multi-Protocol Label Switch, MPLS) network, optical network, etc. can optimize resources through technical means (such as traffic engineering), underlying protocols, controller devices, etc., so as to satisfy SLA of logical channels and support to satisfy end-to-end slicing service requirements.
In the current slicing subnet management, the end-to-end service requirement needs to be decomposed into requirements for a wireless network, a core network and a transmission network, the decomposed requirements can be issued to the subnet in a mode of description of a requirement description field (Slice Profile) and a network slicing service identifier (S-NSSAI), and the requirements are met through operation of network slicing subnet instances (Network Slice Subnet Instance, NSSI), but the requirements are not maintained according to the dimension of the S-NSSAI on the transmission side; when the interface is called, the NSSMF operation objects of the wireless network and the core network are NSSI or match the requirement of S-NSSAI, and the operations of creating, modifying, deleting and the like of the transport network slice management function are aimed at the maintenance of a logic channel instead of S-NSSAI, so that the level difference exists in the requirement decomposition and the call of the sub-network NSSMF, the current three-domain (wireless network, core network and transport network) butt joint is realized according to the characteristics of the three domains, namely the point-to-point butt joint is usually carried out, namely NSMF butt joint is carried out according to the specific condition of NSSMF, the complexity of management and interface flow is increased, and the problem that the automatic unified interface butt joint cannot be realized exists.
In order to solve the problem that the complexity of the current management and interface flow is higher and the automatic unified interface docking cannot be realized, the embodiment of the application provides a network configuration method, an NSRMF entity, an NSMF entity and a storage medium, wherein the method comprises the following steps: the NSRMF entity receives a requirement description field and NSST ID issued by the NSMF entity; if the NSRMF entity judges that the pre-stored logic channel instance does not meet the configuration conditions according to the requirement description field and NSST ID, generating a first operation instruction based on the requirement description field and NSST ID; the NSRMF entity invokes a transport network slice management function interface to issue a first operation instruction to complete network configuration of the transport network through the transport network slice management function. Therefore, the NSRMF entity may first receive the requirement description field and the nst ID issued by the NSMF entity, and if the NSRMF entity determines that the pre-stored logical channel instance does not meet the configuration condition according to the requirement description field and the nst ID, then may generate the first operation instruction based on the requirement description field and the nst ID; the NSRMF entity may call the transport network slice management function interface to issue the first operation instruction, so that the transport network slice management function completes the network configuration of the transport network, that is, the NSRMF entity provided by the present application may receive the information issued by the NSMF entity interface, so as to complete the subsequent network configuration of the transport network, and the NSMF entity interface may also call the NSSMF entity of the wireless network and the NSSMF entity of the core network indiscriminately, that is, call the NSSMF of the core network, the NSSMF of the wireless network and the NSRMF of the transport network through the unified NSMF entity interface, so as to implement automatic unified interfacing, and further reduce complexity of management and interface flow.
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application.
Example 1
The embodiment of the application provides a network configuration method which is applied to an NSRMF entity. Fig. 2 is a schematic diagram of a network configuration method according to an embodiment of the present application, as shown in fig. 2, a method for performing network configuration by an NSRMF entity may include the following steps:
step 101, the NSRMF entity receives the NSST ID and the requirement description field issued by the NSMF entity.
In an embodiment of the present application, the NSRMF entity may first receive the NSST ID and the requirement description field issued by the NSMF entity.
It should be noted that, in an embodiment of the present application, the network configuration method may be implemented by a network configuration system, where the network configuration system may include an NSMF entity and a network slice requirement management function (Network Slicing Requirements Management Function, NSRMF) entity.
It should be noted that, in the embodiment of the present application, fig. 3 is a schematic diagram of a network configuration system provided in the embodiment of the present application, as shown in fig. 3, the network configuration system may include an NSMF entity and an NSRMF entity, where the NSRMF entity may be the same entity as the NSMF entity or different entities, if the NSRMF entity is the same entity as the NSMF entity, it indicates that a network slice requirement management function is deployed in the NSMF entity, and if the NSRMF entity is different from the NSMF entity, it indicates that a network slice requirement management function is deployed in the NSSMF entity on the transmission side, and the location where the network slice requirement management function is deployed is not limited in particular.
It should be noted that, in an embodiment of the present application, the NSMF may be responsible for receiving the network slice requirement information sent by the communication service management function (Communication Service Management Function, CSMF); managing life cycle, performance, faults and the like of the network slice instance; arranging the composition of network slice examples; the network slice requirement information is decomposed into requirement information for each network slice subnet instance and/or network function.
It should be noted that, in the embodiment of the present application, the network slice subnet template (Network Slice Subnet Template, NSST) ID may be used for NSSMF to obtain the corresponding NSST.
It should be noted that, in the embodiment of the present application, NSSMF may be responsible for receiving the network slicing subnet requirement sent by NSMF; managing a network slicing subnet instance; the composition of network slice subnet instances is orchestrated.
It should be noted that, in an embodiment of the present application, NSST may be used to create network slice subnet instances (Network Slice Subnet Instance, NSSI).
It should be noted that, in the embodiment of the present application, the NSRMF entity receives a requirement description field issued by the NSMF entity, where parameters of the requirement description field may include at least time delay, maximum bandwidth, transmission link type, and the like; the transmission link type may indicate forward/mid/return, and the application is not limited to the parameters included in the requirement description field.
Step 102, if the NSRMF entity determines that the pre-stored logical channel instance does not meet the configuration condition according to the requirement description field and the NSST ID, generating a first operation instruction based on the requirement description field and the NSST ID.
In the embodiment of the application, after receiving the requirement description field and NSST ID issued by the NSMF entity, the NSRMF entity generates a first operation instruction based on the requirement description field and NSST ID if the NSRMF entity determines that the pre-stored logic channel instance does not meet the configuration condition according to the requirement description field and NSST ID.
It should be noted that, in an embodiment of the present application, the first operation instruction includes a create instruction, and/or a modify instruction, and/or a delete instruction.
It should be noted that, in the embodiment of the present application, the pre-stored logical channel instances may include pre-stored logical channel instances, and the number of pre-stored logical channel instances is not specifically limited in the present application.
It should be noted that, in the embodiment of the present application, after receiving the requirement description field and the NSST ID issued by the NSMF entity, the NSRMF entity may first parse the requirement description field and the NSST ID, and then determine the content of the requirement description field and the capability requirement of NSST, respectively.
Illustratively, in the embodiment of the present application, the NSRMF entity parses the requirement description field and the NSST ID, may determine the content of the requirement description field, for example, the latency, the specific numerical requirement of the maximum bandwidth, and may find and parse the corresponding NSST according to the NSST ID, and determine the capability requirement of the NSST, that is, the specific description specification content.
It should be noted that, in the embodiment of the present application, the transmission side NSST includes at least one or more of the following parameters: NSST identification, NSST network domain identification, logical channel attribute specification parameters.
It should be noted that, in the embodiment of the present application, NSST of the radio network and the core network is used to describe the specification for creating NSSI, and NSST of the transmission side in the present application may be used to describe the requirement of the attribute specification for the underlying supported logical channel.
It should be noted that, in the embodiment of the present application, fig. 4 is a schematic diagram of NSST content on the transmission side according to the embodiment of the present application, as shown in fig. 4, where NSST content includes service description and logical channel specification requirements; the logic channel specification requirements include delay, jitter, maximum bandwidth and the like, and the content included in the logic channel specification requirements is not particularly limited.
It should be noted that, in the embodiment of the present application, the service description parameters included in the NSST content may be shown in the following table 1, for the NSST on the transmission side, M represents an optional parameter of the service description parameters, and O represents an optional parameter of the service description parameters.
TABLE 1
It should be noted that, in the embodiment of the present application, the NSST content may include the logical channel specification requirement parameters as shown in the following table 2, for the NSST on the transmission side, M represents an optional parameter of the logical channel specification requirement parameters, and O represents an optional parameter of the logical channel specification requirement parameters.
TABLE 2
That is, in the embodiment of the present application, the NSRMF entity may analyze the requirement description field and the NSST ID to determine the content of the requirement description field, for example, delay, specific numerical requirements of the maximum bandwidth, and may find the corresponding NSST according to the NSST ID and analyze the NSST ID, so as to find a plurality of logical channels matching the NSST description specification.
It should be noted that, in the embodiment of the present application, the NSRMF entity may view and acquire the existing (pre-stored) multiple logical channel instance resources and status information of the transmission side, so that the NSRMF entity may determine whether the pre-stored logical channel instance meets the configuration condition.
Further, in the embodiment of the present application, based on the content of the requirement description field and the capability requirement of NSST, the NSRMF entity may determine whether the pre-stored logical channel instance satisfies the configuration condition according to a preset screening rule; or based on the content of the requirement description field and the capability requirement of NSST, judging whether the pre-stored logic channel instance meets the configuration condition according to a preset analysis rule.
It should be noted that, in the embodiment of the present application, based on the content of the requirement description field and the capability requirement of NSST, the NSRMF entity may determine, according to a preset screening rule, whether the pre-stored logical channel instance may meet the requirement, that is, the specific content requirement of the requirement description field, for example, the delay requirement is 10ms, and may determine, according to the preset screening rule, whether the requirement is met, that is, whether the configuration condition is met; or, based on the content of the requirement description field and the capability requirement of NSST, whether the pre-stored logic channel instance meets the configuration condition can be judged according to a preset analysis rule.
Further, in the embodiment of the present application, the NSRMF entity determines that the pre-stored logical channel instance cannot meet the requirement, i.e., the specific content requirement of the requirement description field, according to the preset screening rule, based on the content of the requirement description field and the capability requirement of the NSST; or, if the pre-stored logic channel instance is judged to not meet the configuration condition according to the preset analysis rule, a first operation instruction can be generated based on the requirement description field and NSST ID; wherein the first operation instruction comprises a creation instruction, and/or a modification instruction, and/or a deletion instruction.
The pre-stored logical channels include logical channel 1, logical channel 2 and logical channel 3, and the nsrmf entity determines that none of the logical channel 1, logical channel 2 and logical channel 3 can meet the specific content requirement of the requirement, i.e. the requirement description field, according to a preset screening rule based on the content of the requirement description field and the capability requirement of the NSST, and then generates the first operation instruction based on the requirement description field and the NSST ID; wherein the first operation instruction comprises a creation instruction, and/or a modification instruction, and/or a deletion instruction.
It should be noted that, in the embodiment of the present application, the NSRMF entity may determine the requirements of the slice subnet according to the requirement description field and the NSST ID; if it is determined that the logical channel corresponding to the requirement of the slicing subnet does not exist based on the preset association relation, the first operation instruction can be generated based on the requirement description field and NSST ID; the preset association relation is used for determining the mapping relation between the slicing subnet requirements and the logic channels.
Further, in the embodiment of the present application, if the NSRMF entity determines that the pre-stored logical channel instance meets the configuration condition according to the preset screening rule based on the content of the requirement description field and the capability requirement of the NSST, the target logical channel may be determined in the pre-stored logical channel, and the configuration information may be generated based on the target logical channel; or judging that the pre-stored logic channel instance meets the configuration condition according to a preset analysis rule, or determining a target logic channel in the pre-stored logic channel and generating configuration information based on the target logic channel; the NSRMF entity invokes the transport network slice management function interface to issue configuration information to complete network configuration of the transport network through the transport network slice management function.
For example, in the embodiment of the present application, if the NSRMF entity determines that the pre-stored logical channel instance meets the configuration condition according to the requirement description field and the NSST ID, then the target logical channel may be determined in the pre-stored logical channels, and if the pre-stored logical channel includes logical channel 1, logical channel 2, and logical channel 3, the target logical channel 2 determined in the pre-stored logical channel may be used to carry the requirement, that is, the logical channel 2; and generating configuration information based on the target logical channel 2, where the configuration information may refer to establishing a relationship between a requirement and a logical channel, that is, if a pre-stored logical channel includes logical channel 1, logical channel 2, and logical channel 3, then the target logical channel may be determined in the pre-stored logical channel, for example, the target logical channel is logical channel 2, that is, the requirement may be carried through the target logical channel 2, and then an association relationship between the target logical channel 2 and the requirement may be established, and then the NSRMF entity may invoke a transport network slice management function interface to issue configuration information, so as to complete network configuration of the transport network through the transport network slice management function, that is, invoke the transport network slice management function to update the transport network configuration.
That is, in embodiments of the present application, the NSRMF entity may establish a relationship between the slicing subnet requirements and the logical channels based on the target logical channels.
Step 103, the NSRMF entity invokes the transport network slice management function interface to issue a first operation instruction, so as to complete network configuration of the transport network through the transport network slice management function.
In the embodiment of the present application, if the NSRMF entity determines that the pre-stored logical channel instance does not meet the configuration condition according to the requirement description field and the NSST ID, after generating the first operation instruction based on the requirement description field and the NSST ID, the NSRMF entity may invoke the transport network slice management function interface to issue the first operation instruction, so as to complete the network configuration of the transport network through the transport network slice management function.
In an exemplary embodiment of the present application, the NSRMF entity may invoke the transport network slice management function interface to issue a first operation instruction, and if the first operation instruction is a create instruction, that is, a new logical channel is needed, may invoke an interface according to a north definition of the transport network slice management function according to the parsed description specification content of the NSST, for example, may invoke a north new interface defined by IETF; if the first operation instruction is a modification instruction, the north modification interface defined by the IETF can be called to modify the existing logic channel, meanwhile, the id of the logic channel is required to be issued, the logic channel corresponding to the id can be determined through the id of the logic channel, so that the modification operation is performed on the logic channel, if the first operation instruction is a deletion instruction, the north deletion interface defined by the IETF can be called to delete the existing logic channel, meanwhile, the id of the logic channel is required to be issued, and the logic channel corresponding to the id can be determined through the id of the logic channel, so that the deletion operation is performed on the logic channel.
It should be noted that, in the embodiment of the present application, after the NSRMF entity invokes the transport network slice management function interface to issue the first operation instruction, the NSRMF entity may establish a relationship between the slice subnet requirement and the logical channel based on the first operation instruction.
In an exemplary embodiment of the present application, the NSRMF entity may invoke the transport network slice management function interface to issue the first operation instruction, for example, the NSRMF entity may invoke the transport network slice management function interface to issue the first operation instruction as a create instruction, so that the interface may be invoked according to a northbound definition of the transport network slice management function, for example, a northbound newly created interface defined by IETF may be invoked, and assuming that the newly created logical channel is a logical channel 1, the logical channel 1 is created for matching the slicing subnet requirement 1, then the transport network slice management function may return correspondence information between the slicing subnet requirement 1 and the logical channel 1 to the NSRMF entity, and the NSRMF entity may create a relationship between the slicing subnet requirement and the logical channel based on the information; the NSRMF entity can also call the transmission network slice management function interface to issue a first operation instruction as a modification instruction, can call the northbound modification interface defined by IETF to carry out modification operation, and supposedly, the NSRMF entity calls the transmission network slice management function interface to issue the modification instruction and the logic channel ID before the slicing subnet requirement 1 is carried by the logic channel 1, so that the slicing subnet requirement 1 is switched to the logic channel 2 to be carried, the logic channel 2 can be determined according to the issued logic channel ID, the transmission network slice management function can also return the corresponding relation information between the slicing subnet requirement 1 and the logic channel 2 to the NSRMF entity, and the NSRMF entity can establish the relation between the slicing subnet requirement and the logic channel based on the information; the NSRMF entity may also call the transport network slice management function interface to issue the first operation instruction as a deletion instruction, may call the northbound deletion interface defined by the IETF to perform a deletion operation, and call the transport network slice management function interface to issue the deletion instruction and the logical channel ID, where the transport network slice management function may perform deletion of a corresponding logical channel according to the logical channel ID.
It should be noted that, in the embodiment of the present application, NSMF does not need to discretely process different transport network slice management specifications, and unified conversion processing can be performed by the NSRMF entity, so that the problem can be automatically and uniformly solved, and further, the processing efficiency can be improved.
The embodiment of the application provides a network configuration method, which is applied to an NSRMF entity, and comprises the following steps: the NSRMF entity receives a requirement description field and NSST ID issued by the NSMF entity; if the NSRMF entity judges that the pre-stored logic channel instance does not meet the configuration conditions according to the requirement description field and NSST ID, generating a first operation instruction based on the requirement description field and NSST ID; the NSRMF entity invokes a transport network slice management function interface to issue a first operation instruction to complete network configuration of the transport network through the transport network slice management function. Therefore, the NSRMF entity may first receive the requirement description field and the nst ID issued by the NSMF entity, and if the NSRMF entity determines that the pre-stored logical channel instance does not meet the configuration condition according to the requirement description field and the nst ID, then may generate the first operation instruction based on the requirement description field and the nst ID; the NSRMF entity may call the transport network slice management function interface to issue the first operation instruction, so that the transport network slice management function completes the network configuration of the transport network, that is, the NSRMF entity provided by the present application may receive the information issued by the NSMF entity interface, so as to complete the subsequent network configuration of the transport network, and the NSMF entity interface may also call the NSSMF entity of the wireless network and the NSSMF entity of the core network indiscriminately, that is, call the NSSMF of the core network, the NSSMF of the wireless network and the NSRMF of the transport network through the unified NSMF entity interface, so as to implement automatic unified interfacing, and further reduce complexity of management and interface flow.
Example two
The embodiment of the application provides a network configuration method which is applied to an NSMF entity. Fig. 5 is a second schematic diagram of a network configuration method according to an embodiment of the present application, as shown in fig. 5, a method for performing network configuration by an NSMF entity may include the following steps:
step 201, after receiving the network slice requirement information, the NSMF entity decomposes the network slice requirement information into subnet slice requirement information.
In an embodiment of the present application, after receiving the network slice requirement information, the NSMF entity may first decompose the network slice requirement information into subnet slice requirement information.
Step 202, the NSMF entity issues a requirement description field and an NSST ID corresponding to the subnet slice requirement information to the NSRMF entity of the transport network, so that the NSRMF entity generates and issues a first operation instruction based on the requirement description field and the NSST ID.
In the embodiment of the present application, after receiving the network slice requirement information and decomposing the network slice requirement information into the subnet slice requirement information, the NSMF entity may issue a requirement description field and an NSST ID corresponding to the subnet slice requirement information to the NSRMF entity of the transport network, so that the NSRMF entity generates and issues the first operation instruction based on the requirement description field and the NSST ID.
It should be noted that, in an embodiment of the present application, the first operation instruction includes a create instruction, and/or a modify instruction, and/or a delete instruction.
It should be noted that, in the embodiment of the present application, the parameters of the requirement description field may include at least a delay, a maximum bandwidth, a transmission link type, and the like; the transmission link type may indicate forward/mid/return, and the application is not limited to the parameters included in the requirement description field.
It should be noted that, in the embodiment of the present application, fig. 6 is a schematic diagram of a network configuration system provided in the embodiment of the present application, as shown in fig. 6, the network configuration system may further include NSSMF entities in addition to NSMF entities and NSRMF entities, where the interface and operation between the NSSMF entities of the wireless network and the core network are consistent with each other, so that the interface format between the NSMF entities and the NSRMF entities is also the same as that between the wireless network and the core network, and each time the NSMF entities operate, the NSSMF entities of the wireless network, the NSSMF entities of the core network, and the NSRMF entities of the transport network may be called indiscriminately, and the interface parameters need to include identifiers (AN/CN/TN) of network domains; for a transmission side with a value TN, a core network with a value CN, a wireless network with a value AN, and a transmission side directly connected with NSRMF, in addition, interface parameters need to be identified by a subnet demand capability template NSST, and AN NSRMF entity can call a network slice management function of the transmission side to finish operation.
Further, in the embodiment of the present application, after receiving the network slice requirement information sent by the CSMF, the NSMF entity decomposes the network slice requirement information into subnet slice requirement information; the NSMF entity calls a subnet unifying interface, and issues a requirement description field, NSST ID and NSSI identification corresponding to the subnet slice requirement information to an NSSMF entity of the core network, an NSSMF entity of the wireless network and an NSRMF entity of the transmission network.
That is, in an embodiment of the present application, the NSMF entity may decompose the network slice requirement information into subnet slice requirement information after receiving the network slice requirement information; the NSMF entity calls a subnet unified interface, and transmits a requirement description field, NSST ID and NSSI identification corresponding to subnet slice requirement information to a NSSMF entity of a core network, a NSSMF entity of a wireless network and a NSRMF entity of a transmission network, namely, the application can call the core network NSSMF, the wireless network NSSMF and the transmission network NSRMF through the unified NSMF entity interface, thereby realizing automatic unified butt joint and further reducing the complexity of management and interface flow.
It should be noted that, in the embodiment of the present application, the NSMF entity receives the end-to-end slicing requirement, decomposes the network slicing requirement information into the subnet slicing requirement information, and may be expressed by a requirement description field in the interface parameter, where the transmission network requirement description field format is the same as the wireless network and the core network, the parameter of the requirement description field is a transmission network specific parameter, and if the NSMF entity only needs to issue a change requirement for the logical channel, the transmission network requirement description field may be set to be null.
It should be noted that, in the embodiment of the present application, it is assumed that the functions of the NSMF entity and the wireless network, and the NSSMF entity of the core network follow the 3GPP specifications, the interface definition between them refers to TS 28.531 (G50 version), the requirement description field refers to TS 28.541 (h 10 version), the transport network slice management function, and the northbound interface refer to IETF specifications (draft-rokui-5G-network-slice).
It should be noted that, in the embodiment of the present application, in order to adapt to the requirements of the transmission side, the definition of the unified interface between the NSMF and the wireless network NSSMF, the core network NSSMF, and the NSRMF needs to be adjusted correspondingly compared with the definition of the 3GPP, so as to adapt to the three domains (the core network, the wireless network, and the transmission network), and the definition of the parameters of the interface may be as shown in the following table 3:
TABLE 3 Table 3
The parameter nsstId corresponds to an ID of the NSST, the parameter nsiId is used when the NSSI is designated for deployment, the parameter domainType is used for identifying whether a wireless, core or transmission requirement is issued, the parameter perfReq wireless side and the core side are not needed, the transmission side is not needed, the parameters latency, jitter, maxBandwidth and the linkType are parameters needed by the transmission side and are needed for transmission, the parameter linkType indicates whether the requirement belongs to a forward link, a middle link or a return link of transmission, the parameters nsiInfo and the parameter nsiId are used for maintaining the NSI and the subnet slice resource relation for each subzone, and other parameters are defined in 3 GPP.
It should be noted that, in the embodiment of the present application, the interface and operation type and format from NSMF entity to NSRMF entity are defined as same as from NSMF entity to AN/CN NSSMF entity, and for NSRMF, at least the following parameter contents are included: parameters for identifying the network (AN/CN/TN, for transmission, value is TN), AN end-to-end resolved requirement description field (for transmission, parameters of the requirement description field should contain at least delay, maximum bandwidth, transmission link type, etc., where the transmission link type may indicate forward/in/return), and nst ID.
It should be noted that, in the embodiment of the present application, the NSMF entity invokes the subnet unification interface, and issues the second operation instruction corresponding to the subnet slice requirement information to the NSSMF entity of the core network, the NSSMF entity of the wireless network, and the NSRMF entity of the transmission network; wherein the second operation instruction includes a create instruction, and/or a modify instruction, and/or a delete instruction.
It should be noted that, in the embodiment of the present application, after the NSMF entity invokes the subnet unifying interface and issues the second operation instruction corresponding to the subnet slice requirement information to the NSSMF entity of the core network, the NSSMF entity of the wireless network, and the NSRMF entity of the transmission network, the NSSMF entity of the wireless network, the NSSMF entity of the core network, and the transport network slice management function of the core network may configure the wireless network, the core network, and the transport network, respectively.
For example, if the NSSMF entity of the wireless network receives the second operation instruction corresponding to the subnet slicing requirement information, and if the second operation instruction is the deletion instruction, the NSSMF entity of the wireless network may determine the corresponding NSSI according to the NSSI identifier, and perform the deletion operation on the NSSI, and similarly, if the NSRMF entity of the transmission network receives the second operation instruction corresponding to the subnet slicing requirement information, the configuration of the transmission network may be completed through steps 101 to 103 in the above embodiment.
That is, in the embodiment of the present application, after the NSMF entity invokes the subnet unifying interface and issues the second operation instruction corresponding to the subnet slice requirement information to the NSSMF entity of the core network, the NSSMF entity of the wireless network, and the NSRMF entity of the transmission network, the NSSMF entity of the wireless network, the NSSMF entity of the core network, and the transport network slice management function of the transport network may configure the wireless network, the core network, and the transport network, respectively, so as to complete all configuration flows of three domains.
It should be noted that, in the embodiment of the present application, the NSMF entity multiplexes the NSSMF entity of the core network and the NSSMF entity interface of the wireless network as much as possible, and the flexibility of the NSRMF entity of the transmission network provided by the present application is higher, the influence on the wireless network and the core network is small, and the implementation of the landing is facilitated.
In summary, the network configuration system includes an NSSMF entity in addition to the NSMF entity and the NSRMF entity, where the NSMF entity may decompose the network slice requirement information into subnet slice requirement information after receiving the network slice requirement information; the NSMF entity calls a sub-network unified interface, and issues a requirement description field, NSSTID and NSSI identification corresponding to the sub-network slice requirement information to a NSSMF entity of a core network, a NSSMF entity of a wireless network and a NSRMF entity of a transmission network, namely, the application can call the core network NSSMF, the wireless network NSSMF and the transmission network NSRMF through the unified NSMF entity interface, thereby realizing automatic unified docking, further reducing the complexity of management and interface flows, and the NSSMF entity of the wireless network, the NSSMF entity of the core network and the transmission network slice management function of the wireless network can respectively configure the wireless network, the core network and the transmission network based on a second operation instruction, so that all configuration flows of three domains can be efficiently completed.
The embodiment of the application provides a network configuration method, which is applied to an NSMF entity, and comprises the following steps: after receiving the network slice requirement information, the NSMF entity decomposes the network slice requirement information into subnet slice requirement information; the NSMF entity transmits a requirement description field and NSST ID corresponding to the subnet slice requirement information to an NSRMF entity of the transmission network, so that the NSRMF entity generates and transmits a first operation instruction based on the requirement description field and NSST ID. It can be seen that after receiving the network slice requirement information, the NSMF entity may first decompose the network slice requirement information into subnet slice requirement information; then, a requirement description field and NSST ID corresponding to the subnet slice requirement information are issued to an NSRMF entity of the transmission network; the NSRMF entity can generate and issue a first operation instruction based on the requirement description field and the NSST ID, and can call a subnet unified interface to issue the requirement description field, the NSST ID and the NSSI mark corresponding to the subnet slice requirement information to the NSSMF entity of the core network, the NSSMF entity of the wireless network and the NSRMF entity of the transmission network, namely, the NSSMF of the core network, the NSSMF of the wireless network and the NSRMF of the transmission network can be called through the unified NSMF entity interface, so that automatic unified butt joint can be realized, and the complexity of management and interface flows is reduced.
Example III
The embodiment of the application provides a network configuration method which is applied to a network configuration system, wherein the network configuration system comprises an NSMF entity and an NSRMF entity. Fig. 7 is a schematic diagram of a network configuration method according to an embodiment of the present application, and as shown in fig. 7, a method for performing network configuration by a network configuration system may include the following steps:
step 301, after receiving the network slice requirement information, the NSMF entity decomposes the network slice requirement information into subnet slice requirement information.
Step 302, the NSMF entity issues a requirement description field and an NSST ID corresponding to the subnet slice requirement information to the NSRMF entity of the transport network, so that the NSRMF entity generates and issues a first operation instruction based on the requirement description field and the NSST ID.
It should be noted that, in the embodiment of the present application, the parameters of the requirement description field may include at least a delay, a maximum bandwidth, a transmission link type, and the like; the transmission link type may indicate forward/mid/return, and the application is not limited to the parameters included in the requirement description field.
It should be noted that, in the embodiment of the present application, as shown in fig. 3, the network configuration system may include an NSMF entity and an NSRMF entity, where the NSRMF entity may be the same entity as the NSMF entity or may be a different entity, if the NSRMF entity is the same entity as the NSMF entity, it indicates that the network slice requirement management function is deployed in the NSMF entity, and if the NSRMF entity is a different entity from the NSMF entity, it indicates that the network slice requirement management function is deployed in the NSSMF entity on the transmission side, and the location where the network slice requirement management function is deployed is not limited specifically in the present application.
Step 303, if the NSRMF entity determines that the pre-stored logical channel instance does not meet the configuration condition according to the requirement description field and the NSST ID, generating a first operation instruction based on the requirement description field and the NSST ID.
It should be noted that, in an embodiment of the present application, the first operation instruction includes a create instruction, and/or a modify instruction, and/or a delete instruction.
It should be noted that, in the embodiment of the present application, the pre-stored logical channel instances may include pre-stored logical channel instances, and the number of pre-stored logical channel instances is not specifically limited in the present application.
It should be noted that, in the embodiment of the present application, after receiving the requirement description field and the NSST ID issued by the NSMF entity, the NSRMF entity may first parse the requirement description field and the NSST ID, and then determine the content of the requirement description field and the capability requirement of NSST, respectively.
Illustratively, in the embodiment of the present application, the NSRMF entity parses the requirement description field and the NSST ID, may determine the content of the requirement description field, for example, the latency, the specific numerical requirement of the maximum bandwidth, and may find and parse the corresponding NSST according to the NSST ID, and determine the capability requirement of the NSST, that is, the specific description specification content.
It should be noted that, in the embodiment of the present application, the transmission side NSST includes at least one or more of the following parameters: NSST identification, NSST network domain identification, logical channel attribute specification parameters.
It should be noted that, in the embodiment of the present application, NSST of the radio network and the core network is used to describe the specification for creating NSSI, and NSST of the transmission side in the present application may be used to describe the requirement of the attribute specification for the underlying supported logical channel.
In the embodiment of the application, the NSRMF entity may analyze the requirement description field and the NSST ID to determine the content of the requirement description field, for example, delay, specific numerical requirements of maximum bandwidth, and may find a corresponding NSST according to the NSST ID and analyze the NSST so as to find a plurality of logical channels matching the NSST description specification.
It should be noted that, in the embodiment of the present application, the NSRMF entity may view and acquire the existing (pre-stored) multiple logical channel instance resources and status information of the transmission side, so that the NSRMF entity may determine whether the pre-stored logical channel instance meets the configuration condition.
Further, in the embodiment of the present application, based on the content of the requirement description field and the capability requirement of NSST, the NSRMF entity may determine whether the pre-stored logical channel instance satisfies the configuration condition according to a preset screening rule; or based on the content of the requirement description field and the capability requirement of NSST, judging whether the pre-stored logic channel instance meets the configuration condition according to a preset analysis rule.
It should be noted that, in the embodiment of the present application, based on the content of the requirement description field and the capability requirement of NSST, the NSRMF entity may determine, according to a preset screening rule, whether the pre-stored logical channel instance may meet the requirement, that is, the specific content requirement of the requirement description field, for example, the delay requirement is 10ms, and may determine, according to the preset screening rule, whether the requirement is met, that is, whether the configuration condition is met; or, based on the content of the requirement description field and the capability requirement of NSST, whether the pre-stored logic channel instance meets the configuration condition can be judged according to a preset analysis rule.
Further, in the embodiment of the present application, the NSRMF entity determines that the pre-stored logical channel instance cannot meet the requirement, i.e., the specific content requirement of the requirement description field, according to the preset screening rule, based on the content of the requirement description field and the capability requirement of the NSST; or, if the pre-stored logic channel instance is judged to not meet the configuration condition according to the preset analysis rule, a first operation instruction can be generated based on the requirement description field and NSST ID; wherein the first operation instruction comprises a creation instruction, and/or a modification instruction, and/or a deletion instruction.
Further, in the embodiment of the present application, if the NSRMF entity determines that the pre-stored logical channel instance meets the configuration condition according to the preset screening rule based on the content of the requirement description field and the capability requirement of the NSST, the target logical channel may be determined in the pre-stored logical channel, and the configuration information may be generated based on the target logical channel; or judging that the pre-stored logic channel instance meets the configuration condition according to a preset analysis rule, or determining a target logic channel in the pre-stored logic channel and generating configuration information based on the target logic channel; the NSRMF entity invokes the transport network slice management function interface to issue configuration information to complete network configuration of the transport network through the transport network slice management function.
Step 304, the NSRMF entity invokes the transport network slice management function interface to issue a first operation instruction, so as to complete network configuration of the transport network through the transport network slice management function.
It should be noted that, in the implementation of the present application, the NSRMF entity may invoke the transport network slice management function interface to issue the first operation instruction, so that the transport network slice management function may complete the network configuration of the transport network.
In an exemplary embodiment of the present application, the NSRMF entity may invoke the transport network slice management function interface to issue a first operation instruction, and if the first operation instruction is a create instruction, that is, a new logical channel is needed, may invoke an interface according to a north definition of the transport network slice management function according to the parsed description specification content of the NSST, for example, may invoke a north new interface defined by IETF; if the first operation instruction is a modification instruction, the north modification interface defined by the IETF can be called to modify the existing logic channel, meanwhile, the id of the logic channel is required to be issued, the logic channel corresponding to the id can be determined through the id of the logic channel, so that the modification operation is performed on the logic channel, if the first operation instruction is a deletion instruction, the north deletion interface defined by the IETF can be called to delete the existing logic channel, meanwhile, the id of the logic channel is required to be issued, and the logic channel corresponding to the id can be determined through the id of the logic channel, so that the deletion operation is performed on the logic channel.
It should be noted that, in the embodiment of the present application, after the NSRMF entity invokes the transport network slice management function interface to issue the first operation instruction, the NSRMF entity may establish a relationship between the slice subnet requirement and the logical channel based on the first operation instruction.
In an exemplary embodiment of the present application, the NSRMF entity may invoke the transport network slice management function interface to issue the first operation instruction, for example, the NSRMF entity may invoke the transport network slice management function interface to issue the first operation instruction as a create instruction, so that the interface may be invoked according to a northbound definition of the transport network slice management function, for example, a northbound newly created interface defined by IETF may be invoked, and assuming that the newly created logical channel is a logical channel 1, the logical channel 1 is created for matching the slicing subnet requirement 1, then the transport network slice management function may return correspondence information between the slicing subnet requirement 1 and the logical channel 1 to the NSRMF entity, and the NSRMF entity may create a relationship between the slicing subnet requirement and the logical channel based on the information; the NSRMF entity can also call the transmission network slice management function interface to issue a first operation instruction as a modification instruction, can call the northbound modification interface defined by IETF to carry out modification operation, and supposes that the slice subnet requirement 1 is borne by the logic channel 1 before, and the NSRMF entity calls the transmission network slice management function interface to issue the modification instruction and the logic channel ID to switch the slice subnet requirement 1 to the logic channel 2 for bearing, wherein the logic channel 2 can be determined according to the issued logic channel ID; the NSRMF entity may also call the transport network slice management function interface to issue the first operation instruction as a deletion instruction, may call the northbound deletion interface defined by the IETF to perform a deletion operation, and call the transport network slice management function interface to issue the deletion instruction and the logical channel ID, where the transport network slice management function may perform deletion of a corresponding logical channel according to the logical channel ID.
It should be noted that, in the embodiment of the present application, NSMF does not need to discretely process different transport network slice management specifications, and unified conversion processing can be performed by the NSRMF entity, so that the problem can be automatically and uniformly solved, and further, the processing efficiency can be improved.
The embodiment of the application provides a network configuration method, which comprises the following steps: after receiving the network slice requirement information, the NSMF entity can decompose the network slice requirement information into subnet slice requirement information; the NSMF entity transmits a requirement description field and NSST ID corresponding to the subnet slice requirement information to an NSRMF entity of the transmission network, and if the NSRMF entity judges that the pre-stored logic channel instance does not meet the configuration condition according to the requirement description field and NSST ID, a first operation instruction is generated based on the requirement description field and NSST ID; the NSRMF entity invokes a transport network slice management function interface to issue a first operation instruction to complete network configuration of the transport network through the transport network slice management function. Therefore, the NSRMF entity may first receive the requirement description field and the nst ID issued by the NSMF entity, and if the NSRMF entity determines that the pre-stored logical channel instance does not meet the configuration condition according to the requirement description field and the nst ID, then may generate the first operation instruction based on the requirement description field and the nst ID; the NSRMF entity may call the transport network slice management function interface to issue the first operation instruction, so that the transport network slice management function completes the network configuration of the transport network, that is, the NSRMF entity provided by the present application may receive the information issued by the NSMF entity interface, so as to complete the subsequent network configuration of the transport network, and the NSMF entity interface may also call the NSSMF entity of the wireless network and the NSSMF entity of the core network indiscriminately, that is, call the NSSMF of the core network, the NSSMF of the wireless network and the NSRMF of the transport network through the unified NSMF entity interface, so as to implement automatic unified interfacing, and further reduce complexity of management and interface flow.
Example IV
Based on the above embodiments, a further embodiment of the present application provides a network configuration method, firstly, in order to automatically complete the docking of the NSMF with three sub-domains (wireless network, transmission network, core network), and avoid confusion on the transmission side and influence on the wireless network and the core network to the greatest extent, the present application proposes a network slice requirement management function (Network Slicing Requirements Management Function, NSRMF), and related interfaces and operation definitions, so as to implement unification of the NSMF on the lower interface call, where the functions may exist independently, and may be deployed in the NSMF entity, the transmission network, or the NSSMF entity on the transmission side.
At present, the interfacing interfaces and operations of the wireless network and the core network and the NSMF are consistent, so that the interface formats of the NSMF and the NSRMF are also the same as those of the wireless network and the core network, fig. 8 is AN interaction schematic diagram of each management function of the network slice provided by the embodiment of the present application, as shown in fig. 8, each operation of the NSMF may call the wireless network NSSMF indifferently, the core network NSSMF and the NSRMF entity of the transmission network, the interface parameters need to include identifiers (AN/CN/TN) of network domains, the transmission side directly interfaces with the NSRMF, in addition, the interface parameters need to have identifiers of a subnet requirement capability template NSST, the NSRMF calls the network slice management function of the transmission side to complete the operation, and the CSMF may be used for performing slice requirement management towards the user side.
It should be noted that, in the embodiment of the present application, the expressions of both NSMF and NSMF entities may be interchanged, the expressions of both NSSMF and NSSMF entities may be interchanged, and the expressions of both NSRMF and NSRMF entities may be interchanged.
It should be noted that, in the embodiment of the present application, NSST of the radio network and the core network is used to describe the specification for creating NSSI, and the transmission network is not required, and the present application multiplexes this concept, but NSST of the transmission side is used to describe the attribute specification requirements for the logical channel of the underlying support.
Further, in an embodiment of the present application, the functions of NSRMF include: (1) Receiving, identifying and backing up the requirement of an end-to-end slice issued by an NSMF interface on a transmission side slice; (2) capable of resolving NSST templates; (3) Determining network slice management operation meeting requirements through strategy or intelligent analysis, and calling a corresponding interface; (4) Maintaining the relation between the end-to-end decomposition requirement and the matched transmission slice; (5) And performing operations such as creation, modification, update and the like of the logic channel according to the northbound interface definition of the transport network slice management function.
It should be noted that, in the embodiment of the present application, fig. 9 is a schematic diagram of a network configuration method according to the embodiment of the present application, as shown in fig. 9, step S01: NSMF receives end-to-end slicing requirements, and decomposes the requirements into requirements of a wireless network, a transmission network and a core network, and can be expressed through interface requirement description fields, wherein the transmission network requirement description fields have the same format as the wireless network and the core network, and parameters are specific parameters of the transmission network; in particular, if the NSMF only wants to issue a change demand for a logical channel, the transport network demand description field may be empty.
It should be noted that, in the embodiment of the present application, after receiving the network slice requirement information sent by the CSMF, the NSMF entity decomposes the network slice requirement information into subnet slice requirement information; the NSMF entity calls a subnet unifying interface, and issues a requirement description field, NSST ID and NSSI identification corresponding to the subnet slice requirement information to an NSSMF entity of the core network, an NSSMF entity of the wireless network and an NSRMF entity of the transmission network.
That is, in an embodiment of the present application, the NSMF entity may decompose the network slice requirement information into subnet slice requirement information after receiving the network slice requirement information; the NSMF entity calls a subnet unified interface, and transmits a requirement description field, NSST ID and NSSI identification corresponding to subnet slice requirement information to a NSSMF entity of a core network, a NSSMF entity of a wireless network and a NSRMF entity of a transmission network, namely, the application can call the core network NSSMF, the wireless network NSSMF and the transmission network NSRMF through the unified NSMF entity interface, thereby realizing automatic unified butt joint and further reducing the complexity of management and interface flow.
It should be noted that, in the embodiment of the present application, the NSMF entity receives the end-to-end slicing requirement, decomposes the network slicing requirement information into the subnet slicing requirement information, and may be expressed by a requirement description field in the interface parameter, where the transmission network requirement description field format is the same as the wireless network and the core network, the parameter of the requirement description field is a transmission network specific parameter, and if the NSMF entity only needs to issue a change requirement for the logical channel, the transmission network requirement description field may be set to be null.
It should be noted that, in the embodiment of the present application, the NSRMF entity receives a requirement description field issued by the NSMF entity, where parameters of the requirement description field may include at least time delay, maximum bandwidth, transmission link type, and the like; the transmission link type indicates forward/mid/return, and the application does not specifically limit the parameters included in the requirement description field.
In the embodiment of the present application, as shown in fig. 9, step S02: the NSMF may invoke three sub-domain unified interfaces, issue operation instructions (second operation instructions) for creation, deletion, modification, etc.
It should be noted that, in the embodiment of the present application, the NSMF entity invokes the sub-domain unified interface, and issues the second operation instruction corresponding to the subnet slice requirement information to the NSSMF entity of the core network, the NSSMF entity of the wireless network, and the NSRMF entity of the transmission network; wherein the second operation instruction includes a create instruction, and/or a modify instruction, and/or a delete instruction.
It should be noted that, in the embodiment of the present application, after the NSMF entity invokes the subnet unifying interface and issues the second operation instruction corresponding to the subnet slice requirement information to the NSSMF entity of the core network, the NSSMF entity of the wireless network, and the NSRMF entity of the transmission network, the NSSMF entity of the wireless network, the NSSMF entity of the core network, and the transport network slice management function of the core network may configure the wireless network, the core network, and the transport network, respectively.
In an exemplary embodiment, the NSSMF entity of the wireless network receives a second operation instruction corresponding to the subnet slice requirement information, and if the second operation instruction is a deletion instruction, the NSSMF entity of the wireless network may determine a corresponding NSSI according to the NSSI identifier, and perform a deletion operation on the NSSI.
Further, in the embodiment of the present application, as shown in fig. 9, if the NSRMF entity of the transport network receives the second operation instruction corresponding to the subnet slice requirement information, step S03: the requirement description field and NSST ID may first be parsed to determine the contents of the requirement description field and the capability requirements of NSST, respectively.
Illustratively, in the embodiment of the present application, the NSRMF entity parses the requirement description field and the NSST ID, may determine the content of the requirement description field, for example, the latency, the specific numerical requirement of the maximum bandwidth, and may find and parse the corresponding NSST according to the NSST ID, and determine the capability requirement of the NSST, that is, the specific description specification content.
It should be noted that, in the embodiment of the present application, the transmission side NSST includes at least one or more of the following parameters: NSST identification, NSST network domain identification, logical channel attribute specification parameters.
It should be noted that, in the embodiment of the present application, NSST of the radio network and the core network is used to describe the specification for creating NSSI, and NSST of the transmission side in the present application may be used to describe the requirement of the attribute specification for the underlying supported logical channel.
That is, in the embodiment of the present application, the NSRMF entity may analyze the requirement description field and the NSST ID to determine the content of the requirement description field, for example, delay, specific numerical requirements of the maximum bandwidth, and may find the corresponding NSST according to the NSST ID and analyze the NSST ID, so as to find a plurality of logical channels matching the NSST description specification.
In the embodiment of the present application, step S04: the NSRMF entity may view and acquire the existing (pre-stored) multiple logical channel instance resources and status information of the transmitting side, so that the NSRMF entity may determine whether the pre-stored logical channel instance meets the configuration condition.
Further, in the embodiment of the present application, step S05: based on the step S04, the content of the requirement description field and the capability requirement of NSST are combined, whether the existing logic channel instance can meet the requirement is judged through screening by a preset rule strategy or according to an intelligent analysis algorithm, if yes, the logic channel is selected according to the analysis result, the relation between the requirement and the selected current logic channel is updated, and the transmission network management function is invoked to update the transmission network configuration; if not, the analysis results should give the next step of creating, deleting, modifying, etc. the logical channels.
It should be noted that, in the embodiment of the present application, based on the content of the requirement description field and the capability requirement of NSST, the NSRMF entity may determine whether the pre-stored logical channel instance can meet the requirement, i.e. the specific content requirement of the requirement description field, according to a preset screening rule (preset rule policy screening), for example, the delay requirement is 10ms, and may determine whether the requirement is met, i.e. whether the configuration condition is met according to the preset screening rule; or, based on the content of the requirement description field and the capability requirement of NSST, whether the pre-stored logic channel instance meets the configuration condition can be judged according to a preset analysis rule (intelligent analysis algorithm).
That is, in the embodiment of the present application, if the NSRMF entity determines that the pre-stored logical channel instance satisfies the configuration condition (slicing requirement) according to the preset screening rule (preset rule policy screening) based on the content of the requirement description field and the capability requirement of the NSST, then the target logical channel is determined in the pre-stored logical channel, and configuration information is generated based on the target logical channel; or judging that the pre-stored logic channel instance meets the configuration condition (slicing requirement) according to a preset analysis rule (intelligent analysis algorithm), or determining a target logic channel in the pre-stored logic channel and generating configuration information based on the target logic channel; the NSRMF entity invokes the transport network slice management function interface to issue configuration information to complete network configuration of the transport network through the transport network slice management function.
For example, in the embodiment of the present application, if the NSRMF entity determines that the pre-stored logical channel instance meets the configuration condition according to the requirement description field and the NSST ID, then the target logical channel may be determined in the pre-stored logical channels, for example, the pre-stored logical channels include logical channel 1, logical channel 2, and logical channel 3, and the target logical channel 2 determined in the pre-stored logical channels may be carried by the target logical channel, that is, logical channel 2; generating configuration information based on the target logical channel, wherein the configuration information can be used for establishing the relation between the requirement and the logical channel; that is, if the pre-stored logical channels include logical channel 1, logical channel 2, and logical channel 3, then it may be determined that the target logical channel is, for example, logical channel 2, that the target logical channel may be the logical channel 2, that is, the requirement may be borne by the target logical channel 2, so as to establish an association relationship between the target logical channel 2 and the requirement, and then the NSRMF entity invokes the transport network slice management function interface to issue configuration information, so as to complete network configuration of the transport network through the transport network slice management function, that is, invoke the transport network slice management function to update the transport network configuration.
That is, in embodiments of the present application, the NSRMF entity may establish a relationship between the slicing subnet requirements and the logical channels based on the target logical channels.
Further, in the embodiment of the present application, the NSRMF entity may determine, based on the content of the requirement description field and the capability requirement of the NSST, that the pre-stored logical channel instance cannot meet the requirement, that is, the specific content requirement of the requirement description field, according to a preset screening rule; or, if the pre-stored logic channel instance is judged to not meet the configuration condition according to the preset analysis rule, a first operation instruction can be generated based on the requirement description field and NSST ID; wherein the first operation instruction comprises a creation instruction, and/or a modification instruction, and/or a deletion instruction.
The pre-stored logical channels include logical channel 1, logical channel 2 and logical channel 3, and the nsrmf entity determines that none of the logical channel 1, logical channel 2 and logical channel 3 can meet the specific content requirement of the requirement, i.e. the requirement description field, according to a preset screening rule based on the content of the requirement description field and the capability requirement of the NSST, and then generates the first operation instruction based on the requirement description field and the NSST ID; wherein the first operation instruction comprises a creation instruction, and/or a modification instruction, and/or a deletion instruction.
Further, in the embodiment of the present application, step S06: the NSRMF entity may invoke the transport network slice management function interface to issue a first operation instruction to complete network configuration of the transport network through the transport network slice management function.
It should be noted that, in the embodiment of the present application, according to a preset rule policy (such as a channel occupancy rate threshold, a bandwidth usage condition threshold, etc.), an intelligent analysis (an intelligent algorithm or a policy is used to select an optimal channel from a plurality of channels meeting a specification to bear the requirement, or determine that a new channel is needed to be established), a logical channel meeting the requirement is determined, and according to the result, a transport network slice management northbound interface is called to complete corresponding operations and configurations (if an existing logical channel is selected to meet the requirement, the transport network slice management is not called to operate, and a matching relationship is updated and recorded, if a new logical channel is needed, then an interface can be called according to a northbound definition of a transport network slice management function, for example, a new interface defined by IETF can be called, if a certain modification is needed to be made to an existing channel to meet the requirement, and if the issued requirement relates to a deletion operation to an existing channel, a deletion interface defined by IETF can be called), and the definition specification referred to by the northbound interface of the transport network slice management function is not specifically limited.
It should be noted that, in the embodiment of the present application, the NSRMF entity may call the transport network slice management function interface to issue the first operation instruction, and if the first operation instruction is a creation instruction, that is, a new logical channel is needed, the NSRMF entity may call the interface according to the north definition of the transport network slice management function according to the parsed description specification content of the NSST, for example, may call the north newly-built interface defined by IETF; if the first operation instruction is a modification instruction, the north modification interface defined by the IETF can be called to modify the existing logic channel, meanwhile, the id of the logic channel is required to be issued, the logic channel corresponding to the id can be determined through the id of the logic channel, so that the modification operation is performed on the logic channel, if the first operation instruction is a deletion instruction, the north deletion interface defined by the IETF can be called to delete the existing logic channel, meanwhile, the id of the logic channel is required to be issued, and the logic channel corresponding to the id can be determined through the id of the logic channel, so that the deletion operation is performed on the logic channel.
Further, in the embodiment of the present application, step S07: NSRMF establishes the association between the end-to-end decomposition requirement and the matched transmission slice/logic channel
It should be noted that, in an embodiment of the present application, after generating the first operation instruction based on the requirement description field and the NSST ID, the NSRMF entity may establish a relationship between the slicing subnet requirement and the logical channel based on the first operation instruction.
Further, in the embodiment of the present application, the NSRMF entity may call the transport network slice management function interface to issue the first operation instruction, for example, the first operation instruction is a create instruction, then call the interface according to the northbound definition of the transport network slice management function, for example, the new operation of the northbound new interface defined by IETF may be called, assuming that the new logical channel is a logical channel 1, which is established by matching the slicing subnet requirement 1, then the transport network slice management function may return the correspondence information between the slicing subnet requirement 1 and the logical channel 1 to the NSRMF entity, and the NSRMF entity may establish the relationship between the slicing subnet requirement and the logical channel based on the information, and the definition specification referred to by the northbound interface of the transport network slice management function is not specifically limited.
It should be noted that, in the embodiment of the present application, NSMF does not need to discretely process different transport network slice management specifications, and unified conversion processing can be performed by the NSRMF entity, so that the problem can be automatically and uniformly solved, and further, the processing efficiency can be improved.
Further, in the embodiment of the present application, step S08: the wireless NSSMF, the core NSSMF and the transport network slice management function respectively configure the wireless network, the core network and the transport network to complete the whole flow.
In the embodiment of the present application, the NSST on the transmission side includes at least the following parameter contents: template ID (NSST ID), version number, NSST network domain identification value (allowed value has radio, core or transport), logical channel attribute specification (value of latency, maximum bandwidth, etc.).
It should be noted that, in the embodiment of the present application, the interface and operation type and format of NSMF to NSRMF are defined as NSMF to AN/CN NSSMF, and for NSRMF, at least the following parameter contents are included: parameters for identifying the network (AN/CN/TN, for transmission, value is TN), AN end-to-end resolved requirement description field (for transmission, parameters of the requirement description field should at least contain delay, maximum bandwidth, transmission link type, etc., where the transmission link type indicates forward/mid/return), NSST ID.
It should be noted that, in the embodiment of the present application, when the requirements match, the NSRMF may trigger a query for NSMF, a transport slice management function, an integrated resource management module, etc. to complete the functions; when the requirement is converted, the configured strategy or intelligent analysis can comprise a plurality of sets to adapt to different transmission slice management functions; and after the requirement conversion, interface calling and operation are carried out according to the northbound definition of the slice management function of the transmission network, and the requirement for the transmission logic channel is issued.
It should be noted that, in the embodiment of the present application, the NSRMF may also interface with a transmission side network without a slice management function to implement the slice management function, where the configured policy or intelligent analysis needs to include consideration of parameters of the underlying network supporting the slice, such as tunnel identifier, traffic rate, and so on.
It should be noted that, in the embodiment of the present application, it is assumed that functions of NSMF and wireless network, core network NSSMF conform to 3GPP specifications, an interface definition between them refers to TS 28.531 (G50 version), a requirement description field refers to TS 28.541 (h 10 version), a transport network slice management function, and a northbound interface refer to IETF specifications (draft-rokui-5G-network-slice).
Further, in the embodiment of the present application, in order to adapt to the requirements of the transmission side, the unified interfaces of the NSMF and the wireless network NSSMF, the core network NSSMF, and the NSRMF need to be fine-tuned correspondingly compared with the definition of the 3GPP, so as to adapt to the three domains. Taking allocatensi as an example, the parameter definition of the interface is shown in table 3.
Further, in the embodiment of the present application, after receiving the requirement of end-to-end slicing service decomposition, NSRMF may find a corresponding template according to the ID of NSST and parse the template, and find a logical channel matching the NSST description specification. The content of the transmission NSST template is shown in figure 4; the service description parameters are defined as shown in table 1, and the logical channel specification requirement parameters are defined as shown in table 2.
It should be noted that, in the embodiment of the present application, the present application supports modification of a logical channel separately, and may call NSRMF separately, and set all parameter values of a slice profile in an interface to 0, and at the same time, NSRMF itself establishes an association relationship between a sub-field requirement (slice profile) issued and an end-to-end requirement, and an association relationship between NSI carried by the requirement and a selected logical channel.
In summary, the network configuration system includes an NSSMF entity in addition to the NSMF entity and the NSRMF entity, where the NSMF entity may decompose the network slice requirement information into subnet slice requirement information after receiving the network slice requirement information; the NSMF entity calls a sub-network unified interface, and issues a requirement description field, NSSTID and NSSI identification corresponding to the sub-network slice requirement information to a NSSMF entity of a core network, a NSSMF entity of a wireless network and a NSRMF entity of a transmission network, namely, the application can call the core network NSSMF, the wireless network NSSMF and the transmission network NSRMF through the unified NSMF entity interface, thereby realizing automatic unified docking, further reducing the complexity of management and interface flows, and the NSSMF entity of the wireless network, the NSSMF entity of the core network and the transmission network slice management function of the wireless network can respectively configure the wireless network, the core network and the transmission network based on a second operation instruction, so that all configuration flows of three domains can be efficiently completed.
The embodiment of the application provides a network configuration method, which comprises the following steps: the NSRMF entity receives a requirement description field and NSST ID issued by the NSMF entity; if the NSRMF entity judges that the pre-stored logic channel instance does not meet the configuration conditions according to the requirement description field and NSST ID, generating a first operation instruction based on the requirement description field and NSST ID; the NSRMF entity invokes a transport network slice management function interface to issue a first operation instruction to complete network configuration of the transport network through the transport network slice management function. Therefore, the NSRMF entity may first receive the requirement description field and the nst ID issued by the NSMF entity, and if the NSRMF entity determines that the pre-stored logical channel instance does not meet the configuration condition according to the requirement description field and the nst ID, then may generate the first operation instruction based on the requirement description field and the nst ID; the NSRMF entity may call the transport network slice management function interface to issue the first operation instruction, so that the transport network slice management function completes the network configuration of the transport network, that is, the NSRMF entity provided by the present application may receive the information issued by the NSMF entity interface, so as to complete the subsequent network configuration of the transport network, and the NSMF entity interface may also call the NSSMF entity of the wireless network and the NSSMF entity of the core network indiscriminately, that is, call the NSSMF of the core network, the NSSMF of the wireless network and the NSRMF of the transport network through the unified NSMF entity interface, so as to implement automatic unified interfacing, and further reduce complexity of management and interface flow.
Example five
Based on the foregoing embodiments, the embodiment of the present application provides an NSRMF entity, fig. 10 is a schematic diagram of a composition structure of the NSRMF entity, and as shown in fig. 10, the NSRMF entity 10 includes: the acquisition unit 11, the generation unit 12, the first issuing unit 13,
the receiving unit 11 is configured to receive, by the NSRMF entity, a requirement description field and an NSST ID issued by the NSMF entity;
the generating unit 12 is configured to generate a first operation instruction based on the requirement description field and the nst ID if the NSRMF entity determines that the pre-stored logical channel instance does not meet the configuration condition according to the requirement description field and the nst ID;
the first issuing unit 13 is configured to invoke, by the NSRMF entity, a transport network slice management function interface to issue the first operation instruction, so as to complete network configuration of a transport network through the transport network slice management function.
In an embodiment of the present application, further, fig. 11 is a schematic diagram of a second component structure of the NSRMF entity, as shown in fig. 11, the NSRMF entity 10 provided in the embodiment of the present application may further include a first processor 14, a first memory 15 storing executable instructions of the first processor 14, further, the NSRMF entity 10 may further include a communication interface 16, and a bus 17 for connecting the first processor 14, the first memory 15, and the communication interface 16.
In an embodiment of the present application, the first processor 14 may be at least one of an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a digital signal processor (Digital Signal Processor, DSP), a digital signal processing device (Digital Signal Processing Device, DSPD), a programmable logic device (ProgRAMmable Logic Device, PLD), a field programmable gate array (Field ProgRAMmable Gate Array, FPGA), a central processing unit (Central Processing Unit, CPU), a controller, a microcontroller, and a microprocessor. It will be appreciated that the electronics for implementing the above-described processor functions may be other for different devices, and embodiments of the present application are not particularly limited. The NSRMF entity 10 may further comprise a first memory 15, which first memory 15 may be connected to the first processor 14, wherein the first memory 15 is adapted to store executable program code comprising computer operating instructions, the first memory 15 may comprise a high-speed RAM memory, and may further comprise a non-volatile memory, e.g. at least two disk memories.
In an embodiment of the application, a bus 17 is used to connect the communication interface 16, the first processor 14 and the first memory 15 and the mutual communication between these devices.
In an embodiment of the application, the first memory 15 is used for storing instructions and data.
Further, in the embodiment of the present application, the first processor 14 is configured to receive, by the NSRMF entity, a requirement description field and an NSST ID issued by the NSMF entity;
if the NSRMF entity judges that the pre-stored logic channel instance does not meet the configuration condition according to the requirement description field and the NSST ID, generating a first operation instruction based on the requirement description field and the NSST ID;
the NSRMF entity invokes a transport network slice management function interface to issue the first operation instruction so as to complete network configuration of a transport network through the transport network slice management function.
In practical applications, the first Memory 15 may be a volatile Memory (RAM), such as a Random-Access Memory (RAM); or a nonvolatile Memory (non-volatile Memory), such as a Read-Only Memory (ROM), a flash Memory (flash Memory), a Hard Disk (HDD) or a Solid State Drive (SSD); or a combination of the above types of memories and provides instructions and data to the first processor 14.
The embodiment of the application provides an NSRMF entity, which receives a requirement description field and NSST ID issued by the NSMF entity; if the NSRMF entity judges that the pre-stored logic channel instance does not meet the configuration conditions according to the requirement description field and NSST ID, generating a first operation instruction based on the requirement description field and NSST ID; the NSRMF entity invokes a transport network slice management function interface to issue a first operation instruction to complete network configuration of the transport network through the transport network slice management function. Therefore, the NSRMF entity may first receive the requirement description field and the nst ID issued by the NSMF entity, and if the NSRMF entity determines that the pre-stored logical channel instance does not meet the configuration condition according to the requirement description field and the nst ID, then may generate the first operation instruction based on the requirement description field and the nst ID; the NSRMF entity may call the transport network slice management function interface to issue the first operation instruction, so that the transport network slice management function completes the network configuration of the transport network, that is, the NSRMF entity provided by the present application may receive the information issued by the NSMF entity interface, so as to complete the subsequent network configuration of the transport network, and the NSMF entity interface may also call the NSSMF entity of the wireless network and the NSSMF entity of the core network indiscriminately, that is, call the NSSMF of the core network, the NSSMF of the wireless network and the NSRMF of the transport network through the unified NSMF entity interface, so as to implement automatic unified interfacing, and further reduce complexity of management and interface flow.
An embodiment of the present application provides a computer-readable storage medium having stored thereon a program which, when executed by a processor, implements a network configuration method as described above.
Specifically, the program instructions corresponding to one network configuration method in the present embodiment may be stored on a storage medium such as an optical disc, a hard disk, or a usb disk, and when the program instructions corresponding to one network configuration method in the storage medium are read or executed by an electronic device, the method includes the following steps:
the NSRMF entity receives a requirement description field and NSST ID issued by an NSMF entity;
if the NSRMF entity judges that the pre-stored logic channel instance does not meet the configuration condition according to the requirement description field and the NSST ID, generating a first operation instruction based on the requirement description field and the NSST ID;
the NSRMF entity invokes a transport network slice management function interface to issue the first operation instruction so as to complete network configuration of a transport network through the transport network slice management function.
Based on the above embodiments, the embodiment of the present application provides an NSMF entity, fig. 12 is a schematic diagram of the composition structure of the NSMF entity, and as shown in fig. 12, the NSMF entity 20 includes: a decomposition unit 21, a second issuing unit 22,
The decomposing unit 21 is configured to decompose the network slice requirement information into subnet slice requirement information after the NSMF entity receives the network slice requirement information;
the second issuing unit 22 is configured to issue, by the NSMF entity, a requirement description field and an NSST ID corresponding to the subnet slice requirement information to an NSRMF entity of the transport network, so that the NSRMF entity generates and issues a first operation instruction based on the requirement description field and the NSST ID.
In an embodiment of the present application, further, fig. 13 is a schematic diagram of a second component structure of an NSMF entity, as shown in fig. 13, where the NSMF entity 20 according to the embodiment of the present application may further include a second processor 23, a second memory 24 storing executable instructions of the second processor 23, and further, the NSMF entity 20 may further include a communication interface 25, and a bus 26 for connecting the second processor 23, the second memory 24, and the communication interface 25.
In an embodiment of the present application, the second processor 23 may be at least one of an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a digital signal processor (Digital Signal Processor, DSP), a digital signal processing device (Digital Signal Processing Device, DSPD), a programmable logic device (ProgRAMmable Logic Device, PLD), a field programmable gate array (Field ProgRAMmable Gate Array, FPGA), a central processing unit (Central Processing Unit, CPU), a controller, a microcontroller, and a microprocessor. It will be appreciated that the electronics for implementing the above-described processor functions may be other for different devices, and embodiments of the present application are not particularly limited. The NSMF entity 20 may further comprise a second memory 24, which second memory 24 may be connected to the second processor 23, wherein the second memory 24 is adapted to store executable program code comprising computer operating instructions, and the second memory 24 may comprise a high speed RAM memory, and may further comprise a non-volatile memory, e.g. at least two disk memories.
In an embodiment of the application, a bus 26 is used to connect the communication interface 25, the second processor 23 and the second memory 24 and the mutual communication between these devices.
In an embodiment of the application, the second memory 24 is used for storing instructions and data.
Further, in an embodiment of the present application, the second processor 23 is configured to decompose the network slice requirement information into subnet slice requirement information after the NSMF entity receives the network slice requirement information;
and the NSMF entity transmits a requirement description field and NSST ID corresponding to the subnet slice requirement information to an NSRMF entity of a transmission network, so that the NSRMF entity generates and transmits a first operation instruction based on the requirement description field and NSST ID.
In practical applications, the second Memory 24 may be a volatile Memory (RAM), such as a Random-Access Memory (RAM); or a nonvolatile Memory (non-volatile Memory), such as a Read-Only Memory (ROM), a flash Memory (flash Memory), a Hard Disk (HDD) or a Solid State Drive (SSD); or a combination of memories of the above kind and providing instructions and data to the second processor 23.
The embodiment of the application provides an NSMF entity, which decomposes network slice demand information into subnet slice demand information after receiving the network slice demand information; the NSMF entity transmits a requirement description field and NSST ID corresponding to the subnet slice requirement information to an NSRMF entity of the transmission network, so that the NSRMF entity generates and transmits a first operation instruction based on the requirement description field and NSST ID. It can be seen that after receiving the network slice requirement information, the NSMF entity may first decompose the network slice requirement information into subnet slice requirement information; then, a requirement description field and NSST ID corresponding to the subnet slice requirement information are issued to an NSRMF entity of the transmission network; the NSRMF entity can generate and issue a first operation instruction based on the requirement description field and the NSST ID, and can call a subnet unified interface to issue the requirement description field, the NSST ID and the NSSI mark corresponding to the subnet slice requirement information to the NSSMF entity of the core network, the NSSMF entity of the wireless network and the NSRMF entity of the transmission network, namely, the NSSMF of the core network, the NSSMF of the wireless network and the NSRMF of the transmission network can be called through the unified NSMF entity interface, so that automatic unified butt joint can be realized, and the complexity of management and interface flows is reduced.
An embodiment of the present application provides a computer-readable storage medium having stored thereon a program which, when executed by a processor, implements a network configuration method as described above.
Specifically, the program instructions corresponding to one network configuration method in the present embodiment may be stored on a storage medium such as an optical disc, a hard disk, or a usb disk, and when the program instructions corresponding to one network configuration method in the storage medium are read or executed by an electronic device, the method includes the following steps:
after receiving the network slice requirement information, the NSMF entity decomposes the network slice requirement information into subnet slice requirement information;
and the NSMF entity transmits a requirement description field and NSST ID corresponding to the subnet slice requirement information to an NSRMF entity of a transmission network, so that the NSRMF entity generates and transmits a first operation instruction based on the requirement description field and NSST ID.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of implementations of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block and/or flow of the flowchart illustrations and/or block diagrams, and combinations of blocks and/or flow diagrams in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart block or blocks and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks and/or block diagram block or blocks.
The foregoing description is only of the preferred embodiments of the present application, and is not intended to limit the scope of the present application.

Claims (16)

1. A network configuration method, wherein the method is applied to a network slice demand management function NSRMF entity, the method comprising:
receiving a requirement description field and a network slice subnet template identifier NSST ID issued by a network slice management function NSMF entity;
if the pre-stored logic channel instance is judged to not meet the configuration condition according to the requirement description field and the NSSTID, generating a first operation instruction based on the requirement description field and the NSSTID;
and calling a transport network slice management function interface to issue the first operation instruction so as to complete network configuration of the transport network through the transport network slice management function.
2. The method of claim 1, wherein the first operation instruction comprises a create instruction, and/or a modify instruction, and/or a delete instruction, and wherein after the NSRMF entity invokes a transport network slice management function interface to issue the first operation instruction, the method further comprises:
the NSRMF entity establishes a relationship between the slicing subnet requirements and the logical channels based on the first operation instruction.
3. The method according to claim 1, wherein the method further comprises:
analyzing the requirement description field and NSSTID, and respectively determining the content of the requirement description field and the capability requirement of NSST;
judging whether the pre-stored logic channel instance meets the configuration condition according to a preset screening rule based on the content of the requirement description field and the capability requirement of the NSST; or alternatively, the process may be performed,
and judging whether the pre-stored logic channel instance meets the configuration condition according to a preset analysis rule based on the content of the requirement description field and the capability requirement of the NSST.
4. The method according to claim 1, wherein the method further comprises:
if the NSRMF entity judges that the pre-stored logic channel instance meets the configuration conditions according to the requirement description field and the NSSTID, determining a target logic channel in the pre-stored logic channel, and generating configuration information based on the target logic channel;
And the NSRMF entity invokes the transport network slice management function interface to issue the configuration information so as to complete the network configuration of the transport network through the transport network slice management function.
5. The method of claim 4, wherein after the pre-stored logical channels determine the target logical channel, the method further comprises:
the NSRMF entity establishes a relationship between the slicing subnet requirements and logical channels based on the target logical channel.
6. A method according to claim 3, wherein the NSST comprises at least one or more of the following parameters: NSST identification, NSST network domain identification, logical channel attribute specification parameters.
7. The method according to claim 1, wherein the method further comprises:
determining a slice subnet requirement according to the requirement description field and the NSSTID;
if the fact that the logic channel corresponding to the slicing subnet requirement does not exist is determined based on a preset association relation, generating the first operation instruction based on the requirement description field and the NSSTID; the preset association relation is used for determining a mapping relation between the slicing subnet requirements and the logic channels.
8. A network configuration method, wherein the method is applied to an NSMF entity, the method comprising:
after receiving the network slice requirement information, the NSMF entity decomposes the network slice requirement information into subnet slice requirement information;
and the NSMF entity transmits a requirement description field and NSST ID corresponding to the subnet slice requirement information to an NSRMF entity of a transmission network, so that the NSRMF entity generates and transmits a first operation instruction based on the requirement description field and NSSTID.
9. The method of claim 8, wherein the method further comprises:
and the NSMF entity calls a subnet unifying interface, and transmits a requirement description field, NSSTID and NSSI identification corresponding to the subnet slice requirement information to a network slice subnet management function NSSMF entity of the core network, a NSSMF entity of the wireless network and a NSRMF entity of the transmission network.
10. The method according to claim 9, wherein the method further comprises:
the NSMF entity calls a subnet unification interface, and issues a second operation instruction corresponding to the subnet slice requirement information to the NSSMF entity of a core network, the NSSMF entity of a wireless network and the NSRMF entity of the transmission network; wherein the second operation instruction comprises a creation instruction, and/or a modification instruction, and/or a deletion instruction.
11. The method according to claim 9, wherein the method further comprises:
the interface parameters of the subnet unifying interface at least comprise one or more of the following parameters: network domain identifier, requirement description field, NSSTID.
12. An NSRMF entity, characterized in that the NSRMF entity comprises: a receiving unit, a generating unit, a first issuing unit,
the receiving unit is configured to receive, by the NSRMF entity, a requirement description field and an NSSTID issued by the NSMF entity;
the generating unit is configured to generate a first operation instruction based on the requirement description field and the NSSTID if the NSRMF entity determines that the pre-stored logical channel instance does not meet the configuration condition according to the requirement description field and the NSSTID;
the first issuing unit is configured to invoke a transport network slice management function interface by the NSRMF entity to issue the first operation instruction, so as to complete network configuration of a transport network through the transport network slice management function.
13. An NSRMF entity, characterized in that the NSRMF entity comprises: a first processor and a first memory; wherein, the liquid crystal display device comprises a liquid crystal display device,
the first memory is used for storing a computer program capable of running on the processor;
The first processor being adapted to perform the method of any of claims 1-7 when the computer program is run.
14. An NSMF entity, characterized in that it comprises: a decomposing unit, a second issuing unit,
the decomposing unit is configured to decompose the network slice requirement information into subnet slice requirement information after the NSMF entity receives the network slice requirement information;
the second issuing unit is configured to issue, by the NSMF entity, a requirement description field and an NSSTID corresponding to the subnet slice requirement information to an NSRMF entity of the transport network, so that the NSRMF entity generates and issues a first operation instruction based on the requirement description field and the NSSTID.
15. An NSMF entity, characterized in that it comprises: a second processor and a second memory; wherein, the liquid crystal display device comprises a liquid crystal display device,
the second memory is used for storing a computer program capable of running on the processor;
the second processor being adapted to perform the method of any of claims 8-11 when the computer program is run.
16. A computer readable storage medium, characterized in that the storage medium has stored thereon a computer program code which, when executed by a computer, performs the method of any of claims 1-7 or 8-11.
CN202310597813.2A 2023-05-25 2023-05-25 Network configuration method, NSRMF entity, NSMF entity and storage medium Pending CN116916345A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310597813.2A CN116916345A (en) 2023-05-25 2023-05-25 Network configuration method, NSRMF entity, NSMF entity and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310597813.2A CN116916345A (en) 2023-05-25 2023-05-25 Network configuration method, NSRMF entity, NSMF entity and storage medium

Publications (1)

Publication Number Publication Date
CN116916345A true CN116916345A (en) 2023-10-20

Family

ID=88361647

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310597813.2A Pending CN116916345A (en) 2023-05-25 2023-05-25 Network configuration method, NSRMF entity, NSMF entity and storage medium

Country Status (1)

Country Link
CN (1) CN116916345A (en)

Similar Documents

Publication Publication Date Title
US11146462B2 (en) Network slice management method, device, and system
EP3595244B1 (en) Network slice management method, unit and system
CN115296993B (en) System, function and interface for interconnected multi-domain network fragment control and management
US10999740B2 (en) Network slice management method, management unit, and system
US11271818B2 (en) Method, apparatus, and system for obtaining network slice
US11265210B2 (en) Network slice configuration method, apparatus, and system
CN108566289B (en) Slice architecture design management method based on 5G mobile communication network
US8310939B2 (en) Method, system, and device for configuring operation, administration and maintenance properties
US20230041039A1 (en) Method, device, and system for deploying network slice
CN114009096A (en) Interworking of application workload routing and network-defined edge routing
EP3142303A1 (en) Network control method and apparatus
US8824451B2 (en) Method and system for establishing an associated bidirectional label-switched path
EP3742786A1 (en) Network alarm method, device, system and terminal
CN111726293B (en) Message transmission method and device
EP3300400B1 (en) Capability opening method and system, and capability opening functional entity
EP3016327B1 (en) Method, device and system for establishing traffic engineering label switch path
CN114128227B (en) Transmitting MTNC-ID on SRv 6-enabled data plane to enable 5G transmission
CN116916345A (en) Network configuration method, NSRMF entity, NSMF entity and storage medium
CN112752326B (en) Network slice management method and device
CN116458204A (en) Transport network slice control device and control plane entity for a time-sensitive network based transport network
WO2024002101A1 (en) Packet transmission method and apparatus, related device, and storage medium
WO2023246118A1 (en) Message forwarding method and apparatus, and storage medium and electronic apparatus
CN113905401A (en) Sub-slice docking method, device and equipment
CN110581775A (en) Management method and device for management service instance of network slice

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