CN117376143A

CN117376143A - Service execution method and device based on full-dimension definable network function instance

Info

Publication number: CN117376143A
Application number: CN202311303489.5A
Authority: CN
Inventors: 刘萌萌; 郝楠
Original assignee: Zhejiang Lab
Current assignee: Zhejiang Lab
Priority date: 2023-10-08
Filing date: 2023-10-08
Publication date: 2024-01-09

Abstract

The specification discloses a service execution method and device based on a full-dimension definable network function instance. The method comprises the following steps: the service consumer side sends a service request aiming at a target NF instance of a designated mode corresponding to a network function NF provided by the service producer side, so that a network warehouse function NRF corresponding to the service producer side inquires the target NF instance according to the service request, and configuration files of NF instances of a plurality of modes corresponding to NF are stored in the NRF; judging whether the NRF inquires a target NF instance of a designated mode; if yes, acquiring a configuration file corresponding to a target NF instance of a designated mode sent by the NRF, otherwise, acquiring configuration files of NF instances of other modes except the designated mode sent by the NRF; and accessing the service producer side according to the received configuration file to execute the target service corresponding to the service request through the NF instance provided by the service producer side.

Description

Service execution method and device based on full-dimension definable network function instance

Technical Field

The present disclosure relates to the field of communications networks, and in particular, to a method and apparatus for executing a service based on a full-dimension definable network function instance.

Background

With the development of technology, network architecture starts to adopt key technologies such as Software defined network (Software-Defined Networking, SDN), network function virtualization (Network Function Virtualization, NFV), intelligent computing (Intelligent Computing), and the like, and evolves towards Software, virtualization, distributed, intelligent, heterogeneous directions, and has the characteristics of separation of control plane and user plane, decoupling of Software and hardware, elastic reconfiguration of network functions, and the like.

However, the protocol stack of the Network Function (NF) under the existing Service-Based Architecture (SBA) Network architecture is fixed, and the NF instance mode is single, which is difficult to satisfy the actual Service requirement of the user.

Therefore, how to ensure the diversification of network function examples, and fully meet the requirements of backward compatible network evolution technology and actual service scene requirements, is a problem to be solved.

Disclosure of Invention

The present disclosure provides a method and apparatus for executing services based on a full-dimension definable network function instance, so as to partially solve the foregoing problems in the prior art.

The technical scheme adopted in the specification is as follows:

the present specification provides a service execution method based on a full-dimension definable network function instance, including:

a service consumer side sends a service request aiming at a target NF instance of a designated mode corresponding to a network function NF provided by a service producer side, so that a network warehouse function NRF corresponding to the service producer side inquires the target NF instance according to the service request, and configuration files of NF instances of a plurality of modes corresponding to the NF are stored in the NRF;

judging whether the NRF inquires a target NF instance of the appointed mode;

if yes, acquiring a configuration file corresponding to the target NF instance of the appointed mode sent by the NRF, otherwise, acquiring configuration files of NF instances of other modes except the appointed mode sent by the NRF;

and accessing the service producer side according to the received configuration file to execute the target service corresponding to the service request through the NF instance provided by the service producer side.

Optionally, the service consumer side sends a service request for a target NF instance of a specified modality corresponding to the network function NF provided by the service producer side, which specifically includes:

invoking a service operation of the NRF and providing input parameters including: the NF type of the service consumer side, the NF type of the target NF and the appointed mode;

and sending the service request carrying the input parameters to the NRF so as to enable the NRF to inquire a target NF instance matched with the input parameters, and returning an inquiry result to the service consumer side.

Optionally, the configuration file stored in the NRF is registered and stored in the NRF when the service producer side runs for the first time, and the configuration file includes information of NF instances corresponding to NF provided by the service producer side.

Optionally, the protocol stacks of NF instances of different modalities are configured differently, and the service producer side dynamically reconstructs the protocol stacks to generate new NF instances in response to a specified operation of the user.

Optionally, before accessing the service producer side according to the received configuration file, the method further comprises: if the NRF does not inquire the target NF instance of the appointed mode, an instance switching option is obtained, wherein the switching option comprises an NF instance of a traditional mode and an NF instance of a candidate mode; and selecting NF examples of other modes except the appointed mode from the example switching options, and acquiring NF example configuration files of the other modes from the NRF.

Optionally, according to the received configuration file, accessing the service producer side to execute the target service corresponding to the service request through the NF instance provided by the service producer side, which specifically includes:

if the NRF does not query the target NF instance of the appointed mode, a first configuration file of the NF instance of the traditional mode corresponding to the NF is obtained from the NRF;

and accessing the service producer side based on the first configuration file to execute the target service through the NF instance of the traditional mode provided by the service producer side.

if the NRF does not query the target NF instance of the appointed mode, acquiring a second configuration file of the NF instance of the candidate mode corresponding to the NF from the NRF;

and accessing the service producer side based on the second configuration file to execute the target service through the NF instance of the candidate modality provided by the service producer side.

Optionally, the input parameters carried by the service request further include: and the history request information corresponding to the service consumer terminal, wherein the NF examples of the candidate modes are determined from the NF examples of the modes according to the history request information when the NRF does not inquire the target NF examples of the designated modes.

The present specification provides a service execution device based on a full-dimensional definable network function instance, including:

the service consumer side sends a service request aiming at a target NF instance of a designated mode corresponding to a network function NF provided by a service producer side, so that a network warehouse function NRF corresponding to the service producer side inquires the target NF instance according to the service request, and configuration files of NF instances of a plurality of modes corresponding to the NF are stored in the NRF;

the judging module is used for judging whether the NRF inquires a target NF instance of the appointed mode;

the acquisition module is used for acquiring configuration files corresponding to the target NF instance of the appointed mode sent by the NRF if yes, or acquiring configuration files of NF instances of other modes except the appointed mode sent by the NRF if not;

and the execution module accesses the service producer side according to the received configuration file so as to execute the target service corresponding to the service request through the NF instance provided by the service producer side.

The present specification provides a computer readable storage medium storing a computer program which when executed by a processor implements the above-described business execution method based on a full-dimensional definable network function instance.

The present specification provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the service execution method based on the full-dimension definable network function instance.

The above-mentioned at least one technical scheme that this specification adopted can reach following beneficial effect:

the network function provided by the service producer side can comprise NF examples of a plurality of modes, thereby ensuring the diversification of the NF examples, fully meeting the service demands of different scenes, and the service consumer side can designate the mode of a target NF example.

Drawings

The accompanying drawings, which are included to provide a further understanding of the specification, illustrate and explain the exemplary embodiments of the present specification and their description, are not intended to limit the specification unduly. In the drawings:

fig. 1 is a flow chart of a service execution method based on a full-dimension definable network function example provided in the present specification;

FIG. 2 is a schematic diagram of a registration and discovery process for NF services provided in the present specification;

FIG. 3 is a schematic diagram of an example selection process for NF provided in this specification;

fig. 4 is a schematic diagram of a service execution device based on a full-dimensional definable network function example provided in the present specification;

fig. 5 is a schematic diagram of an electronic device corresponding to fig. 1 provided in the present specification.

Detailed Description

For the purposes of making the objects, technical solutions and advantages of the present specification more apparent, the technical solutions of the present specification will be clearly and completely described below with reference to specific embodiments of the present specification and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present specification. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present disclosure.

The following describes in detail the technical solutions provided by the embodiments of the present specification with reference to the accompanying drawings.

Fig. 1 is a flow chart of a service execution method based on a full-dimension definable network function example provided in the present specification, which includes the following steps:

s101: the service consumer side sends a service request aiming at a target NF instance of a designated mode corresponding to a network function NF provided by a service producer side, so that a network warehouse function NRF corresponding to the service producer side inquires the target NF instance according to the service request, and configuration files of NF instances of a plurality of modes corresponding to the NF are stored in the NRF.

Network Function virtualization (NFV, network Function Virtualization) decouples the relationship of software and hardware strong binding in traditional physical devices by applying standardized Network Functions (NF) to unified hardware. Through a plurality of network function instances (Network Function Instance) virtually implemented on the unified hardware device, a plurality of heterogeneous network function instance groups (Network Function Set) with different network functions, which are formed according to the network functions and logic/codes corresponding to the operating system kernel, are loaded on each of the plurality of network function instances, and then corresponding service requests are executed through the function instances in the instance groups. In practical applications, heterogeneous architectures may be built at the NF Instance (NF Instance) level, NF Service Instance (NF Service Instance) level, NF group (NF Set) level, and NF Service group (NF Service Set) level.

In a communication system, a Service Provider (SP) represents an operator of a network Service, and a Service Provider corresponding to the Service Provider provides network functions corresponding to different network services to a user, and executes corresponding services through corresponding network functions after receiving a Service request.

The service consumer (Service Consumers, SC) represents a program for accessing a service according to a service interface description, and a user sends a service request to a service provider through its corresponding service consumer to execute a corresponding service through a network function corresponding to the service provider.

An instance may be an actual program set corresponding to a network function, and the network function provided by the service provider corresponding to the service provider may include: authentication server functions, access and mobility management functions, data networks, such as operator services, internet access or third party services, unstructured data storage functions, network opening functions, network repository functions, network slice selection functions, control policy functions, session management functions, unified data management, (wireless) access networks, service communication agents, wired access gateway functions, etc., which are not exemplified one by one in this specification.

The full-dimensional definable intelligent Network facing the distributed computing environment regards the dynamic configuration of the protocol stack as a definable dimension, which is also called a modality, however, under the existing Service-Based Architecture (SBA) Network architecture, there is a problem that heterogeneous Network Functions (NF) coexist, that is, NF supporting the dynamic protocol stack and NF not supporting the dynamic protocol stack exist at the same time.

Based on the above, the present specification provides a service execution method based on a full-dimension definable network function instance, which solves the problem of coexistence of heterogeneous dynamic NFs in a full-dimension definable intelligent communication network, and meets the requirement of backward compatible network evolution technology.

Among them, NF can disclose its capability as a Service (Service) through a Service-Based Interface (SBI). NF service is a capability that NF service producers (NF Service Producer) disclose to other authorized NF service consumers (NF Service Consumer) via SBI. NF may disclose one or more NF services (NF services). Interaction between the two NFs (NF Service Consumer and NF Service Producer) may be via a Request-Response, subscribe-Notify mechanism. For ease of understanding, the present description provides a schematic diagram of a registration and discovery process for NF services, as shown in fig. 2.

Fig. 2 is a schematic diagram of a registration and discovery process of NF services provided in the present specification.

When the service producer starts to operate for the first time, an NF profile (NF profile) needs to be registered in a network repository function (NRF, network Repository Function). NF profile contains information about NF instances (NF instance), such as NF instance ID, NF service instance supported, etc.

In addition to the case of local configuration, NF Service Consumer (also called Requester NF, source NF) initiates a NF/NF service discovery (service discovery) process to NRF to obtain NF/NF service instance of NF Service Producer (also called target NF).

In the process of actually executing the service, a service consumer side sends a service request aiming at a target NF instance of a designated mode corresponding to a network function provided by a service producer side, so that a network warehouse function NRF corresponding to the service producer side inquires the target NF instance of the designated mode according to the service request.

Specifically, the service consumer side invokes an nrrf_nfdiscovery_request service operation (service operation) of the NRF corresponding to the service producer side, and provides input parameters, where the necessary parameters include: one or more target network function services (target NF service) names, NF type of target NF, NF type of service consumer, modality specified by the service consumer, and the like.

The service consumer side sends the service request carrying the input parameters to the NRF, the NRF determines the function instance matched with the input parameters, and sends (outputs) the determined configuration file (NF profile) of the work NF instance to the service consumer side.

Each configuration file at least contains the required parameters output to NF Service Consumer through the nnrf_nfdiscovery_request Response message. According to the results of NF/NF service discovery, NF Service Consumer may cache NF profiles and select NF/NF service instance during the expiration date.

It should be noted that, the NRF corresponding to the service producer side stores NF instances of several modes corresponding to the network function NF provided by the service producer side, where the network function discloses at least one network function service NF service, the NF/NF service may correspond to a plurality of network functions or network function service (NF/NF service) instances of different modes, and protocol stacks corresponding to the NF/NF service instances of different modes may have different configurations, but the implemented network function service is the same. The service producer side can respond to the appointed operation of the user to dynamically reconstruct the protocol stack of the NF/NF service to generate a new NF/NF service instance.

The protocol stack is a core component of a network communication system and is composed of a plurality of network protocol layers, each layer being responsible for a different function. Common network protocol stacks include the TCP/IP protocol stack, OSI model, and the like.

Taking as an example NF instances corresponding to access and mobility management functions (Access and Mobility management Function, AMF), one possible protocol stack configuration corresponding thereto includes: NG interface protocol (Protocol for NG Interface, NGAP), stream control transmission protocol (Stream Control Transmission Protocol, SCTP), IP, L2, L1; another possible protocol stack configuration includes NGAP, SCTP, non-IP, L2, L1.

S102: judging whether the NRF inquires the target NF instance of the appointed mode.

S103: if yes, acquiring a configuration file corresponding to the target NF instance of the appointed mode sent by the NRF, otherwise, acquiring configuration files of NF instances of other modes except the appointed mode sent by the NRF.

S104: and accessing the service producer side according to the received configuration file to execute the target service corresponding to the service request through the NF instance provided by the service producer side.

The NRF corresponding to the service producer side may query, according to the input parameter, the target NF instance of the service Request corresponding to the specified mode, where the specified mode may be one of query attributes of the nrrf_nfdiscovery_request service operation (service operation) provided by the NRF, and is used to instruct the service consumer to prefer a mode of the target NF/NF service, that is, to prefer the target NF mode. The attribute is an optional attribute, and the default value represents legacy mode (legacy mode).

If the NF/NF service instance corresponding to the service producer side provided by the NRF does not include the target NF instance whose mode is the designated mode (i.e., the preferred target NF mode), the NRF may return the query result to the service consumer side, so that the service consumer side switches the NF/NF service mode of the service consumer side, or switches the requested mode (i.e., the NF/NF service mode of the target service producer side). The mode switching can be switched to a traditional mode (mode 0) or to other modes on the premise of mode matching between the service consumer side and the service producer side.

If the NRF does not query the target NF instance of the specified modality, the service consumer side may acquire an instance switching option, where the switching option may include the NF instance of the conventional modality (modality 0) and the NF instance of the candidate modality.

The instance switching option may be generated by the NRF and then sent to the service consumer side, and of course, may also be generated locally by the service consumer side.

The service consumer side can select NF examples of other modes except the designated mode in the example switching options based on the designated protocol and acquire the corresponding configuration files from the NRF.

In this specification, an NF instance of a mode other than the specified mode may be selected from instance switching options by the NRF, and the configuration file thereof may be returned directly to the service consumer side.

If the service consumer side selects the NF instance of the conventional mode, the NRF may return a first configuration file corresponding to the NF instance of the conventional mode to the service consumer side, and after receiving the first configuration file, the service consumer side may access the service producer side based on the first configuration file, so as to execute the target service corresponding to the service request through the NF instance of the conventional mode provided by the service producer side.

If the service consumer side selects the NF instance of the candidate mode, the NRF may return a second configuration file corresponding to the NF instance of the candidate mode to the service consumer side, and after receiving the second configuration file, the service consumer side may access the service producer side based on the second configuration file, so as to execute the target service corresponding to the service request through the NF instance of the candidate mode provided by the service producer side.

In this specification, the input parameters carried by the service request may further include history request information corresponding to the service consumer side, where the history request information is used to characterize a history mode preference of the service consumer side for the NF instance mode. When the NRF does not query the target NF instance of the specified mode, it is indicated that the service producer side cannot provide the target NF instance of the specified mode, in this case, the NRF may determine the matching degree between the NF instance of each mode and the history request information, and use the NF instance with the highest matching degree as the NF instance of the candidate mode. The NF instance with the highest matching degree may be a function instance of the modality with the highest access frequency before the service consumer side.

If the NRF queries the target NF instance of the specified mode, a third configuration file corresponding to the target NF instance may be returned to the service consumer side, so that the service consumer side accesses the target NF instance corresponding to the service producer side based on the third configuration file, and thus the target service is executed through the target NF instance. For ease of understanding, the present description provides an example selection process schematic for NF, as shown in fig. 3.

Fig. 3 is a schematic diagram of an example selection process for NF provided in summary in the present specification.

Wherein NF Service Consumer (NF-Sub>A) currently runs instance 2, NF-Sub>A instance 2 has Sub>A modality of x, an input parameter is provided in the NF discovery request, sub>A preferred target NF/NF service modality is designated as x, but NRF cannot find NF/NF service instances having Sub>A modality of x, NRF provides 3 NF/NF service instances whose modality is not the preferred target NF/NF service modality, wherein NF-B instance 1 has Sub>A modality of 0, NF-B instance 2 has Sub>A modality of y, and NF-B instance 3 has Sub>A modality of z. One implementation (Option 1) is NF Service Consumer (NF-Sub>A) to fall back to the legacy modality (modality 0) and select NF-B instance 1 (modality 0) to initiate the subsequent business process. Another implementation (Option 2) is to switch NF Service Consumer (NF-Sub>A) to modality y and select NF-B instance 2 (modality y) to initiate the subsequent business process.

It should be noted that fig. 3 only shows NF instance selection and mode switching flow, and the flow is similar to NF service instance selection and mode switching, and will not be repeated.

In practical applications, "preferred target NF modality" may be added to the input parameter of nnrf_nfdiscovery_ Request service operation, and "Information about the modality of the target NF (e.g., protocol stack composition)" may be added to the output parameter.

It should be noted that the Network Function (NF) described herein may be a Network Element (Network Element), a Network Unit (Network Unit), or a Network device (Network Appliance, network Equipment).

According to the method, the network function provided by the service producer side can comprise NF examples of a plurality of modes, so that the diversification of the NF examples is ensured, the service demands of different scenes are fully met, the service consumer side can designate the mode of a target NF example, and when the NRF can not inquire the target NF example of the mode designated by the service consumer side, the service can be executed through the NF examples of other modes, so that the problem of coexistence of heterogeneous dynamic NF in the full-dimension definable intelligent network is solved, and the technical requirement of backward compatible network evolution is met.

The above is one or more methods for implementing service execution based on the full-dimension definable network function example in the present specification, and based on the same concept, the present specification further provides a corresponding service execution device based on the full-dimension definable network function example, as shown in fig. 4.

Fig. 4 is a schematic diagram of a service execution device provided in the present specification and based on a full-dimensional definable network function instance, where the service execution device includes:

a sending module 401, configured to send, by a service consumer side, a service request for a target NF instance of a designated mode corresponding to a network function NF provided by a service producer side, so that a network warehouse function NRF corresponding to the service producer side queries the target NF instance according to the service request, where a configuration file of NF instances of several modes corresponding to the NF is stored in the NRF;

a judging module 402, configured to judge whether the NRF queries a target NF instance of the specified mode;

an obtaining module 403, configured to obtain a configuration file corresponding to the target NF instance of the specified mode sent by the NRF if yes, or obtain configuration files of NF instances of other modes than the specified mode sent by the NRF;

and the execution module 404 accesses the service producer side according to the received configuration file to execute the target service corresponding to the service request through the NF instance provided by the service producer side.

Optionally, the sending module 401 is specifically configured to invoke a service operation of the NRF, and provide input parameters, where the input parameters include: the NF type of the service consumer side, the NF type of the target NF and the appointed mode; and sending the service request carrying the input parameters to the NRF so as to enable the NRF to inquire a target NF instance matched with the input parameters, and returning an inquiry result to the service consumer side.

Optionally, before accessing the service producer according to the received configuration file, the obtaining module 403 is further configured to obtain an instance switching option if the NRF does not query the target NF instance of the specified mode, where the switching option includes an NF instance of a conventional mode and an NF instance of a candidate mode; and selecting NF examples of other modes except the appointed mode from the example switching options, and acquiring NF example configuration files of the other modes from the NRF.

Optionally, the executing module 404 is specifically configured to obtain, if the NRF does not query the target NF instance of the specified modality, a first configuration file of an NF instance of a traditional modality corresponding to the NF from the NRF; and accessing the service producer side based on the first configuration file to execute the target service through the NF instance of the traditional mode provided by the service producer side.

Optionally, the executing module 404 is specifically configured to obtain, if the NRF does not query the target NF instance of the specified modality, a second configuration file of the NF instance of the candidate modality corresponding to the NF from the NRF; and accessing the service producer side based on the second configuration file to execute the target service through the NF instance of the candidate modality provided by the service producer side.

The present specification also provides a computer readable storage medium storing a computer program, where the computer program is configured to perform a service execution method based on the full-dimensional definable network function instance provided in fig. 1.

The present specification also provides a schematic structural diagram of an electronic device corresponding to fig. 1 shown in fig. 5. At the hardware level, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile storage, as illustrated in fig. 5, although other hardware required by other services may be included. The processor reads the corresponding computer program from the nonvolatile memory into the memory and then runs the computer program to realize the service execution method based on the full-dimension definable network function example as described in fig. 1. Of course, other implementations, such as logic devices or combinations of hardware and software, are not excluded from the present description, that is, the execution subject of the following processing flows is not limited to each logic unit, but may be hardware or logic devices.

Improvements to one technology can clearly distinguish between improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) and software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable Gate Array, FPGA)) is an integrated circuit whose logic function is determined by the programming of the device by a user. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented by using "logic compiler" software, which is similar to the software compiler used in program development and writing, and the original code before the compiling is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but not just one of the hdds, but a plurality of kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), lava, lola, myHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog are currently most commonly used. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers, and embedded microcontrollers, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, atmel AT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller may thus be regarded as a kind of hardware component, and means for performing various functions included therein may also be regarded as structures within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in one or more software and/or hardware elements when implemented in the present specification.

It will be appreciated by those skilled in the art that embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the present specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present description can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present description is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the specification. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks 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 flow or flows 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 flow or flows 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 flow or flows and/or block diagram block or blocks.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

It will be appreciated by those skilled in the art that embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the present specification may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present description can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.

The foregoing is merely exemplary of the present disclosure and is not intended to limit the disclosure. Various modifications and alterations to this specification will become apparent to those skilled in the art. Any modifications, equivalent substitutions, improvements, or the like, which are within the spirit and principles of the present description, are intended to be included within the scope of the claims of the present description.

Claims

1. A business execution method based on a full-dimension definable network function instance, comprising:

judging whether the NRF inquires a target NF instance of the appointed mode;

2. The method of claim 1, wherein the service consumer side sends a service request for a target NF instance of a specified modality corresponding to the network function NF provided by the service producer side, specifically comprising:

3. The method of claim 1, wherein a configuration file stored in the NRF is registered and stored in the NRF when the service producer side runs for the first time, and the configuration file includes information of NF instances corresponding to NF provided by the service producer side.

4. The method of claim 1, wherein protocol stacks of NF instances of different modalities are different in composition, and the service producer side dynamically reconstructs the protocol stacks to generate new NF instances in response to a specified operation by a user.

5. The method of claim 1, wherein prior to accessing the service producer side based on the received profile, the method further comprises:

if the NRF does not inquire the target NF instance of the appointed mode, an instance switching option is obtained, wherein the switching option comprises an NF instance of a traditional mode and an NF instance of a candidate mode;

and selecting NF examples of other modes except the appointed mode from the example switching options, and acquiring NF example configuration files of the other modes from the NRF.

6. The method of claim 1, wherein accessing the service producer side according to the received configuration file to execute the target service corresponding to the service request through the NF instance provided by the service producer side specifically comprises:

7. The method of claim 1, wherein accessing the service producer side according to the received configuration file to execute the target service corresponding to the service request through the NF instance provided by the service producer side specifically comprises:

8. The method of claim 7, wherein the input parameters carried by the service request further comprise: and the history request information corresponding to the service consumer terminal, wherein the NF examples of the candidate modes are determined from the NF examples of the modes according to the history request information when the NRF does not inquire the target NF examples of the designated modes.

9. A service execution device based on a full-dimensional definable network function instance, comprising:

10. A computer-readable storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, implements the method of any of the preceding claims 1-8.

11. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of the preceding claims 1-8 when executing the program.