CN116962263A

CN116962263A - Message receiving and sending method and device

Info

Publication number: CN116962263A
Application number: CN202210382340.XA
Authority: CN
Inventors: 李世涛
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-04-12
Filing date: 2022-04-12
Publication date: 2023-10-27
Also published as: WO2023197815A1

Abstract

The application provides a method and a device for receiving and sending a message, and relates to the technical field of communication. The second device receives a network element creation request message from the first device, where the network element creation request message includes: managing the function parameters and virtualizing the network function parameters; under the condition that the management function parameter comprises the identification of the test task associated with the network element, determining the test task associated with the network element according to the identification of the test task; or under the condition that the management function parameter does not comprise the identification of the test task associated with the network element, creating the test task associated with the network element; if the test result of the test task passes, a network element is created according to the virtualized network function parameter; and if the test result of the test task does not pass, sending a response message of failure in network element creation to the first equipment. According to the application, the network element is created according to the passing condition of the test result of the test task, so that the network security can be ensured, and the occurrence of network faults can be avoided.

Description

Message receiving and sending method and device

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a method and a device for receiving and sending a message.

Background

Network function virtualization (network function virtualization, NFV) uses generic hardware devices and virtualization technology to carry the functions of dedicated devices in legacy networks, thereby reducing the expensive costs associated with deploying dedicated devices. By decoupling the software and hardware, the network device functions are no longer dependent on dedicated hardware. Meanwhile, by utilizing the characteristics of cloud computing, resources can be fully and flexibly shared, rapid development and deployment of new services are realized, and automatic deployment, elastic expansion, fault isolation, self-healing and the like are performed based on actual service requirements. The NFV can receive the virtualization request and perform virtualization processing on the corresponding service according to the request. Network Functions (NFs) deployed using virtualization technologies are referred to as virtualized network functions (virtualised network function, VNFs).

Virtualization, software, of NFV technology puts forward requirements for fast update, fast iteration, fast delivery for the above application scenarios, while the practice of continuous integration (continuous integration, CI)/continuous delivery (continuous delivery, CD) technology helps to achieve these requirements, through which fast development and release of VNFs can be facilitated. In the overall CI/CD flow, both VNF providers and operators need to participate in it, together completing the whole process from development to online operation.

The current network management system based on the object model only can support the creation of a new NF, when the new NF is directly delivered to the network management system of an operator, the operator cannot determine whether the NF can meet service requirements and whether the NF can meet online operation requirements, and the network can be directly operated after the NF is delivered, so that network faults can occur and even the system is paralyzed.

Disclosure of Invention

The application provides a method and a device for receiving and sending a message, which are used for improving the deployment efficiency of network elements and ensuring the safety of a network environment.

In a first aspect, the present application provides a method for receiving a message, which may be performed by a second device, where the second device may implement functions of a network element management service (network function management service, NFMS) or a slice subnet management service (network slice subnet management service, NSSMS) or a slice management service (network slice management service, NSMS), and may also implement functions of other services, and the application is not specifically limited herein.

The second device receives a network element creation request message from the first device, where the network element creation request message includes: managing the function parameters and virtualizing the network function parameters; under the condition that the management function parameter comprises the identification of the test task associated with the network element, determining the test task associated with the network element according to the identification of the test task; or under the condition that the management function parameter does not comprise the identification of the test task associated with the network element, creating the test task associated with the network element; if the test result of the test task passes, a network element is created according to the virtualized network function parameter; and if the test result of the test task does not pass, sending a response message of failure in network element creation to the first equipment.

In the application, after receiving a network element creation request message from a first device, a second device verifies whether the network element creation request message includes an identifier of a test task associated with the network element, determines the test task according to the task identifier when the network element creation request message includes the identifier of the test task, directly creates the test task if the network element creation request message does not include the identifier of the test task, and creates the network element based on a test result of the test task. Compared with the method without any verification of the network element, the method can obviously ensure the safety of network operation, and based on the second equipment construction and verification test task, the data processing efficiency can be improved, and the smooth operation of the network can be ensured.

In an alternative embodiment, the second device receives a network element update request message from the first device, where the network element update request message includes: updated virtualized network function parameters of the network element; the updated virtualized network function parameters of the network element include: an updated version of the network element; creating a test task associated with the network element; if the test result of the test task is passed, updating the version of the network element according to the updated virtualized network function parameters of the network element; and if the test result of the test task does not pass, sending a response message of failure of version update of the network element to the first equipment.

In the application, after receiving the network element test task update request message from the first device, the second device creates a test task associated with the network element, and updates the version of the network element based on the test result of the test task. Compared with the method that no verification is carried out on the network element, the method can obviously ensure the safety of network operation by directly updating the version of the network element, and can improve the data processing efficiency and ensure the smooth operation of the network based on the second equipment construction and verification test task.

In an alternative embodiment, the test tasks include at least one of the following tasks: function test tasks of the network element and running environment test tasks of the network element.

It should be noted that, the function test task of the network element is mainly used for testing the performance of the network element, verifying whether the network element has the capability of executing a certain task, etc.; the running environment testing task of the network element is mainly used for testing whether the network element can work normally in a certain environment, verifying the adapting capability of the network element to the running environment and the like. The testing tasks in the application can comprise the function testing tasks of the network element, the running environment testing tasks of the network element and both, and the application is not particularly limited herein and can be flexibly set according to actual requirements.

In an alternative embodiment, the test tasks include: the second device receives a creation request message from the first device function test task, and the creation request message of the function test task includes: the equipment parameters of the network element, the virtualized network function parameters of the network element and the function test task message; sending a parameter message of a function test task to first equipment; the parameter message of the function test task comprises at least one of the following parameters: identification of a functional test task, progress status of the functional test task, execution result of the functional test task, and report of the functional test task.

By the method, the function test task of the network element is created, so that the data processing efficiency can be improved, and the smooth operation of the network is ensured.

In an alternative embodiment, the second device receives the task state query request message from the first device before sending the parameter message of the functional test task to the first device.

It should be noted that, after receiving the query request message of the first device, the second device may send the parameter message of the function test task to the first device, instead of actively sending the parameter message, so that the method may better adapt to the requirement of the first device, and avoid the waste of signaling.

In an alternative embodiment, the test tasks include: the second device receives a creation request message of the operation environment test task from the first device, wherein the creation request message of the operation environment test task comprises: the method comprises the steps of equipment parameters of a network element, virtualized network function parameters of the network element and running environment test task information; sending a parameter message of the operation environment test task to the first device, wherein the parameter message of the operation environment test task comprises at least one of the following parameters: the method comprises the steps of identifying the running environment test task, the progress status of the running environment test task, the execution result of the running environment test task and the report of the running environment test task.

By the method, the data processing efficiency can be improved, and the smooth operation of the network is ensured.

In an alternative embodiment, the second device receives the task query request message from the first device's running environment test task before sending the parameter message of the running environment test task to the first device.

It should be noted that, after receiving the query request message of the first device, the second device may send the parameter message of the running environment test task to the first device, instead of actively sending the parameter message, so that the method may better adapt to the requirement of the first device, and avoid the waste of signaling.

In an alternative embodiment, the second device receives a first slice from the first device, the first slice for performing the runtime environment test task; the first slice is updated according to the updated virtualized network function parameter of the network element.

In the application, the new version network element is tested on the test slice, and even if the test has a problem, the actual network is not affected, and the mode can ensure the security of the network.

In an alternative embodiment, the second device determines that an operation environment test task associated with the network element exists according to the configuration information of the network element; determining the existence of a first slice according to an operation environment test task associated with a network element, wherein the first slice is used for executing the operation environment test task; if the first slice exists, updating the first slice according to the updated virtualized network function parameters of the network element; or if it is determined that the first slice does not exist, creating the first slice according to the updated virtualized network function parameters of the network element.

By the method, whether the slice for running the environment test of the network element is deleted or not in the initial deployment can be confirmed, and if the slice is not deleted, the test slice is continuously used for testing the network element with the new version, so that resources can be saved.

In an alternative embodiment, the second device updates the version of the network element in a second slice, the second slice being a slice of the running network element, according to the updated virtualized network function parameters of the network element.

In the application, after the test on the slice to be tested is completed and no problem exists, the actual network is updated, so that the operation of the actual network is ensured to be less influenced.

In a second aspect, the present application provides a method for sending a message, which may be performed by a first device, which may be an operation support system (operations support system, OSS), or a service support system (business support system, BSS) may also be another device, and the present application is not limited in this regard.

The first device sends a network element creation request to the second device, and the network element creation request message includes: managing the function parameters and virtualizing the network function parameters; under the condition that the management function parameter comprises the identifier of the test task associated with the network element, the second equipment is instructed to determine the test task associated with the network element according to the identifier of the test task; or, in case the identification of the test task associated with the network element is not included in the management function parameter, instructing the second device to create the test task associated with the network element.

In an alternative embodiment, the first device sends a network element update request message to the second device, where the network element update request message includes: the updated virtualized network function parameters of the network element include: an updated version of the network element; the second device is instructed to create a test task associated with the network element.

In an alternative embodiment, the test tasks include: the method comprises the steps that a first device sends a creation request message of a function test task to a second device, wherein the creation request message of the function test task comprises the following steps: the equipment parameters of the network element, the virtualized network function parameters of the network element and the function test task message; receiving a parameter message of a function test task from the second device; the parameter message of the function test task comprises at least one of the following parameters: identification of a functional test task, progress status of the functional test task, execution result of the functional test task, and report of the functional test task.

In an alternative embodiment, before the first device receives the parameter message of the function test task from the second device, the first device further sends a task state query request message of the function test task to the second device.

In an alternative embodiment, the test tasks include: the first device sends a creation request message of the operation environment test task to the second device, wherein the creation request message of the operation environment test task comprises: the method comprises the steps of equipment parameters of a network element, virtualized network function parameters of the network element and running environment test task information; receiving a parameter message of a running environment test task from the second device; the parameter message of the running environment test task comprises at least one of the following parameters: the method comprises the steps of identifying the running environment test task, the progress status of the running environment test task, the execution result of the running environment test task and the report of the running environment test task.

In an alternative embodiment, before the first device receives the parameter message of the running environment test task from the second device, the first device further sends a task query request message of the running environment test task to the second device.

In an alternative embodiment, the first device sends a first slice to the second device, the first slice being used to perform the runtime environment test task.

In a third aspect, an embodiment of the present application provides a method for receiving and sending a message, where a first device sends a network element creation request message to a second device, where the network element creation request message includes: managing the function parameters and virtualizing the network function parameters; the second device receives a network element creation request message from the first device; under the condition that the management function parameter comprises the identifier of the test task associated with the network element, the first equipment instructs the second equipment to determine the test task associated with the network element according to the identifier of the test task, and the second equipment determines the test task associated with the network element according to the identifier of the test task; or, under the condition that the management function parameter does not include the identifier of the test task associated with the network element, the first device instructs the second device to create the test task associated with the network element, and the second device creates the test task associated with the network element; if the test result of the test task passes, the second equipment creates a network element according to the virtualized network function parameter; if the test result of the test task does not pass, the second device sends a response message of network element creation failure to the first device.

In a fourth aspect, an embodiment of the present application provides a communication apparatus, where the communication apparatus may be a first device (such as a first device in the first aspect, a first device in the second aspect) or a chip disposed inside the first device, and may also be a second device (such as a second device in the first aspect, a second device in the second aspect) or a chip disposed inside the second device. The communication device has functions of implementing any one of the first aspect to the second aspect, for example, the communication device includes a module or a unit or means (means) corresponding to executing steps related to any one of the first aspect to the second aspect, where the functions or units or means may be implemented by software, or implemented by hardware, or implemented by executing corresponding software by hardware.

In one possible design, the communication device includes a processing unit and a transceiver unit, where the transceiver unit may be configured to transceiver signals to enable communication between the communication device and other devices, for example, the transceiver unit is configured to receive configuration information from a terminal device; the processing unit may be adapted to perform some internal operations of the communication device. The transceiver unit may be referred to as an input-output unit, a communication unit, etc., and may be a transceiver; the processing unit may be a processor. When the communication device is a module (e.g., a chip) in the communication apparatus, the transceiver unit may be an input/output interface, an input/output circuit, an input/output pin, or the like, and may also be referred to as an interface, a communication interface, or an interface circuit; the processing unit may be a processor, a processing circuit, a logic circuit, or the like.

In yet another possible design, the communication device includes a processor, and may further include a transceiver for receiving signals, the processor executing program instructions to perform the method in any of the possible designs or implementations of the first aspect to the second aspect. Wherein the communication device may further comprise one or more memories for coupling with the processor, which memories may hold the necessary computer programs or instructions to implement the functions referred to in any of the above first to second aspects. The processor may execute a computer program or instructions stored by the memory, which when executed, cause the communication device to implement the method in any of the possible designs or implementations of the first to fourth aspects described above.

In yet another possible design, the communication device includes a processor that may be used to couple with the memory. The memory may hold the necessary computer programs or instructions to implement the functions referred to in any of the above first to fourth aspects. The processor may execute a computer program or instructions stored by the memory, which when executed, cause the communication device to implement the method in any of the possible designs or implementations of the first to second aspects described above.

In yet another possible design, the communication device includes a processor and an interface circuit, wherein the processor is configured to communicate with other devices through the interface circuit and perform the method in any of the possible designs or implementations of the first to third aspects.

It will be appreciated that in the fourth aspect described above, the processor may be implemented by hardware or software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general purpose processor, implemented by reading software code stored in a memory. Further, the above processor may be one or more, and the memory may be one or more. The memory may be integral to the processor or separate from the processor. In a specific implementation process, the memory and the processor may be integrated on the same chip, or may be respectively disposed on different chips.

In a fifth aspect, an embodiment of the present application provides a communication system, including the first device and the second device in the first to third aspects.

In a sixth aspect, the present application provides a chip system comprising a processor and possibly a memory for implementing the method described in any one of the possible designs of the first to third aspects. The chip system may be formed of a chip or may include a chip and other discrete devices.

In a seventh aspect, the present application also provides a computer readable storage medium having stored therein computer readable instructions which when run on a computer cause the computer to perform the method as in any one of the possible designs of the first to third aspects.

In an eighth aspect, the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of embodiments of the first to third aspects described above.

The technical effects achieved by the second to eighth aspects are described with reference to the technical effects achieved by the corresponding possible design solutions in the first aspect, and the description of the technical effects is not repeated here.

Drawings

FIG. 1 is a schematic diagram of an NFV architecture according to an embodiment of the present application;

Fig. 2 shows a method flow diagram of a network element deployment;

fig. 3 is a schematic diagram of a creation flow of a functional test task of a network element according to an embodiment of the present application;

fig. 4 is a schematic diagram of a creation flow of an operation environment test task of a network element according to an embodiment of the present application;

fig. 5 is a schematic flow chart of a message transmission method according to an embodiment of the present application;

fig. 6 is a flow chart illustrating another method for transmitting a message according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 9 shows a schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings. The specific method of operation in the method embodiment may also be applied to the device embodiment or the system embodiment. In the description of the present application, unless otherwise indicated, the meaning of "a plurality" is two or more. Therefore, the implementation of the apparatus and the method can be referred to each other, and the repetition is not repeated.

Fig. 1 shows a schematic diagram of an NFV architecture. The NFV architecture may implement a variety of networks, such as a local area network (local area network, LAN), an internet protocol (internet protocol, IP) network, or an evolved packet core (evolved packet core, EPC) network, among others.

As shown in fig. 1, the NFV architecture may include an NFV management and orchestration system (NFV management and orchestration system, NFV-MANO) 110, one or more operation support systems/service support systems (operation support system/business support system, OSS/BSS) 120, a plurality of element management systems (EM) 130, a plurality of VNFs 140, and an NFV infrastructure (NFV infrastructure, NFVI) 150.

NFV-MANO 110 may include an NFV orchestrator (NFVO) 111, one or more VNF managers (VNFM) 112, and a virtual infrastructure Manager (virtualised infrastructure Manager, VIM) 113.

The NFVO is configured to implement management and processing of network service descriptors (network service descriptor, NSD), virtual network function forwarding graphs (VNF forwarding graph, VNFFG), management of a network service life cycle, and global view functions of life cycle management of the VNF and virtual resources in cooperation with the VNFM.

VNFM implements life cycle management of VNFs, including management of virtualized network function descriptors (VNFs), instantiations of VNFs, elastic scaling of VNF instances (including scaling out/up and scaling in/down), healing of VNF instances (scaling), and termination of VNF instances. The VNFM also supports receiving an elastic scaling (scaling) policy issued by the NFVO, and implements automatic VNF elastic scaling.

The VIM is mainly responsible for the management (including reservation and allocation) of infrastructure layer hardware resources and virtualized resources, the monitoring and fault reporting of the state of the virtual resources, and the virtualized resource pool is provided for the upper layer application.

OSS/BSS120 is primarily directed to telecommunications service operators and provides integrated network management and business operation functions including network management (e.g., fault monitoring, network information gathering, etc.), billing management, customer service management, etc.

EM130 is configured to perform conventional fault, configuration, user, performance and security management (FCAPS) functions for VNFs.

The VNF140 corresponds to a physical network function (physical network function, PNF) in a conventional non-virtualized network, such as a virtualized packet core network (evolved packet core, EPC) node (e.g., mobility management entity (mobility management entity, MME), serving Gateway (SGW), public data network gateway (public data network gateway, PGW), etc.). The functional behaviour and status of the network functions are independent of whether virtualized or not, NFV technology requirements hope that VNF and PNF possess the same functional behaviour and external interfaces.

The VNF140 may be composed of one or more VNF components (VNFC) of lower functionality level. Thus, one VNF may be deployed on multiple Virtual Machines (VMs), each carrying the functionality of one VNFC, and a VNF may also be deployed on one VM.

NFVI150 may include a virtual resource layer, a virtualization layer, and a Hardware (HW) resource layer. Among them, a plurality of VMs, such as VM1, VM2, and VM3 in fig. 1, may be included in the virtual resource layer, or virtual storage, virtual network, and the like (not shown in fig. 1) may be further included. The hardware resource layer may include a plurality of hardware such as HW1, HW2, and HW3 in fig. 1, which may be computing hardware, storage hardware, network hardware, etc. (not shown in fig. 1).

The hardware in the hardware resource layer may include a dedicated processor or a general purpose processor for providing processing and computing functions, such as a central processing unit (central process unit, CPU), a device for providing storage capabilities, e.g., disk or network attached storage (network attached storage, NAS); and switches, routers, and/or other network devices.

The virtual resource layer may be provided to the VNF140 in the form of virtual machines, e.g. one or more virtual machines make up one VNF140. The virtualization layer forms a virtual network through hardware in the hardware resource layer and is used for realizing communication among a plurality of virtual machines. For example, the virtual network may be implemented by techniques such as virtual local area network (vritual local area network, VLAN), virtual private local area network traffic (virtual private LAN service, VPLS), virtual extensible local area network (virtual extensible local area network, vxLAN), or universal routing encapsulation network virtualization (nerwork virtualization using generic routing encapsulation, NVGRE).

The virtualization layer in the NFVI150 is configured to abstract hardware resources of the hardware resource layer, decouple the VNF140 from a physical layer to which the hardware resources belong, and provide virtual resources to the VNF.

NFV-MANO110 may be used to enable monitoring and management of VNF140 and NFVI 150. NFVO111 may communicate with one or more VNFMs 112 to fulfill resource-related requests, send configuration information to VNFMs 112, and collect status information of VNFs 140. In addition, NFVO111 may also communicate with VIM113 to enable resource allocation and/or to enable reservation and exchange of configuration information and status information for virtualized hardware resources. The VNFM112 may be used to manage one or more VNFs 140, perform various management functions, such as initializing, updating, querying, and/or terminating the VNFs 140.VIM113 may be used to control and manage interactions of virtual resources and hardware resources in VNF140 and NFVI. For example, VIM113 may be used to perform an allocation operation of resources to VNF140. The VNFM112 and VIM113 may communicate with each other to exchange virtualized hardware resource configuration and status information.

Fig. 2 shows a flow of a network element deployment method that may be implemented through interaction of OSS, NFMS, and NFV-MANO. The following is performed:

In step 201, the oss sends a request to the NFMS.

Specifically, the request is for requesting creation of a new NF object instance. The request includes an NF object to be created, for example, the NF object is an access and mobility management function (access and mobility management function, AMF), and if the AMF instance is created in the VNF form, the NF object includes vnfparamterlist (VNF parameter list) (specifically associated VnfdID (VNF deployment template identifier)) information.

In step 202, the nfms determines that the NF object is created in VNF according to the vnfparamtersslist contained in the object parameter carried in the request.

In step 203, the nfms requests creation of VNF instance from NFV-MANO using vnfparamterlist (specific VnfdID information).

In step 204, the nfv-MANO sends a response message to the NFMS that the VNF instance creation was successful.

In step 205, the nfms creates a new NF object at the network management system.

In step 206, the nfms sends a response message to the OSS that the NF object creation was successful.

It should be further noted that, the above-mentioned parameters of NF generally inherit some of the parameters of ManagedFunction as shown in the following table 1, and further include parameters related to the functions of the network element itself as shown in the following table 2, where table 2 is described taking the network element as an AMF as an example. Wherein the parameters of ManagedFunction typically include VNF-related information, such as associated VNFD, VNF package information, etc., a VNF parameter list (energy/environment parameter list), a prioritlabel (priority identification), a supported perfmetric group (supported set of measurable performance parameters); the peeparameterlist indicates parameters of energy (power consumption), environment (running environment), etc. of the wireless network element; priority label indicates the priority status of the network element; supplantedPerfMetricgroups indicates the types of measurable data that the network element may support.

TABLE 1

Among them, parameters related to the functions of the AMF include plmnnfoslist (network operator information list), AMF identifier, taiList (tracking area identifier), cNSIIdList (core network slice identifier list), managednfpprofile (managed network element capability set), aMFSet (AMF cluster information). Wherein plmnifolist indicates the operator network information described by AMF; the aMFIdentifier indicates the identity of the AMF; taiList indicates tracking area identity (tracking area identity, TAI) (tracking area identity, base station cell management related) information to which the AMF belongs; cnsiildlist indicates slice information to which AMF belongs; the managedNTFPprofile indicates that network element equipment parameters, such as supported capacity, supported functions and the like, are different from network element equipment parameters corresponding to NF which are not generally provided; aMFSet indicates the AMF group to which the AMF belongs.

TABLE 2

However, in the network element deployment flow of fig. 2, when a new NF object is delivered to the OSS, the OSS cannot determine whether the NF is perfect in function, and if the NF can meet the online requirement, a problem may occur in the operation process if the NF is directly online, so that a network fault or even paralysis is caused.

Based on the above situation, the application considers that two parameters are added to the parameters of the ManagedFunction, namely, a functional test Job (functional test task) and an operational test Job (operation environment test task), wherein the functional test Job can indicate task identification information or specific task item information of the functional test task; the operationalttestjob may indicate task identification information or specific task item information of the execution environment test task, as described in table 3 below.

TABLE 3 Table 3

The functional testjob is mainly related to network element function and capability test, and may include parameters in table 4 below, such as managedNFProfile, vnfParametersList, jobProgress (task progress), result (Result), report (link) (Report or link of Report). Wherein managedNFProfile, vnfParametersList is not described herein in detail, and JobProgress indicates the execution of the functional test task, and may be indicated by a percentage, as can be understood by referring to tables 1 and 2 above; result indicates the execution Result of the functional test task, such as pass or fail; report (link) indicates a test Report of the functional test task, which may include recording and explanation of events such as faults, alarms and the like occurring in the testing process of the functional test task.

TABLE 4 Table 4

The operation test job is mainly used for online test, generally, a network element with test is deployed in a network environment specially used for test, and the running condition of the network element in a network is tested to determine whether the network element can meet the requirement of the network. Operational testjob may include parameters in table 5 below, managedNFProfile, vnfParametersList, sliceProfile (slice requirement), serviceProfile (business requirement), jobProgress (task progress), result, report (link) (Report or link to Report), networkslicekubinetref (reference to a slice subnet), networkSliceRef (reference to a slice). Herein, managedNFProfile, vnfParametersList may be understood by referring to the above tables 1 and 2, which are not described herein, and the slice subnet requirement is indicated by the slicerp profile, and is mainly used for describing requirements of a test environment, including a maximum number of users, time delay, throughput of an uplink/downlink network, a maximum session number, and the like. In addition, the slicing subnetwork is divided into a core network, a wireless access network, a transmission slicing subnetwork, and different subnetworks may contain different demand parameters, and specific parameters of the slicep profile may be determined according to which slicing subnetwork the network element to be tested belongs to. The ServiceProfile indicates a slice requirement, and is mainly used for describing a requirement on a test environment, one slice may include a plurality of different slice subnets, and is mainly used for describing a cross-domain test environment, for example, a network element (AMF) for a core network, the test environment may also be tested not only on the core network slice subnets, and the test environment may be a real situation such as a radio access network, a core network and a transmission network. ServiceProfile contains slice requirements such as maximum number of users, latency, uplink/downlink network throughput, maximum number of sessions, etc. JobProgress indicates the execution of the run-time environment test tasks, which may be indicated by a percentage; result indicates the execution Result of the running environment test task, such as pass or fail; report (link) indicates a test Report of the running environment test task, and may include recording and explanation of events such as faults, alarms and the like occurring in the running environment test task test process. The networkslicekubcnetref indicates a slice subnet test environment associated with the network element to be tested, and if the parameter is carried in the task creation request, the slice subnet environment is directly used for testing without carrying a SliceProfile parameter. If the task creation request does not contain the parameter, but contains the SliceProfile parameter, after the task creation is successful, the networkSliceSubmetRef is used for describing the slice subnet identifier created according to the SliceProfile parameter. The networkSliceRef indicates a slice test environment associated with the network element to be tested, and if the parameter is carried in the task creation request, the parameter does not need to carry a ServiceProfile parameter, and the slice environment is directly used for testing. If the task creation request does not contain the parameter, but contains the ServiceProfile parameter, after the task creation is successful, the networkSliceRef is used for describing the slice identifier created according to the ServiceProfile parameter.

TABLE 5

In the application, the function test task of the network element is mainly used for testing the performance of the network element, verifying whether the network element has the capability of executing a certain task or not, and the like; the running environment testing task of the network element is mainly used for testing whether the network element can work normally in a certain environment, verifying the adapting capability of the network element to the running environment and the like. The testing tasks in the application can comprise the function testing tasks of the network element, the running environment testing tasks of the network element and both, and the application is not particularly limited herein and can be flexibly set according to actual requirements.

Based on the above description, the present application describes, through fig. 3, a flow of creating a functional test task of a network element, where the creation of the functional test task of the network element generally needs interaction of multiple devices, and may be implemented by interaction of a first device, which may be an OSS or BSS, a second device, which may implement a function of NFMS, NSSMS, NSMS, and even other devices, which may be Test management system (task test system). However, the second device may typically implement the functionality of Test management system, so the functional testing tasks of the network element may be implemented by the interaction of the first device with the second device. Fig. 3 illustrates a first device as an OSS, a second device for implementing NFMS functions, and other devices as Test management system.

In step 301, the oss sends a create request message for a functional test task to the NFMS.

Specifically, the creation request message of the functional test task includes: the device parameters of the network element are as the managedNTFPprofile, the virtualized network function parameters of the network element are as the vnfParametersList, and the function test task message, which can be understood as specific task information of the function test task, such as identification of the function test task or task item information.

In step 302, the nfms creates a FunctionTestJob task object.

Specifically, the NFMS may create a FunctionTestJob task object according to the identity of the functional test task in the functional test task message.

In step 303, the nfms sends a functional test task to Test management system.

Specifically, the functional test task may include VNF package information contained in a managednfpprofile and a vnfparamterlist. In addition, the VNF package may further include a test case of the NF, and Test management system performs related tests according to the information. Of course, in the case that fig. 3 does not include Test management system, this step may not be performed, and the test of the functional test task may be directly performed by the NFMS.

In step 304, the nfms sends an identification of the successful creation function testjob task to the OSS.

Specifically, the OSS may use the identification to query information such as the status of the functional test tasks.

In step 305, the nfms sends a parameter message of the functional test task to the OSS.

Specifically, the parameter message of the functional test task includes at least one of the following parameters: identification of a functional test task, progress status of the functional test task such as JobProgress, execution Result of the functional test task such as Result, and Report of the functional test task such as Report (link). In addition, the parameter messages of the functional test tasks may be presented via uniform resource locator (uniform resource locator, URL) links.

Furthermore, before executing step 305, the NFMS may send the parameter message of the functional test task to the first device instead of actively sending the parameter message after receiving the query request message of the OSS, which may better adapt to the requirements of the first device, and avoid the waste of signaling. Therefore, steps A to C may also be performed.

And step A, the OSS sends a task state query request message of the function test task to the NFMS.

Specifically, the request message carries the identifier of the successful FunctionTestJob task created in step 304.

Step B, the NFMS sends a task status query request message of the functional test task to Test management system.

Step C, test management system sends a parameter message of the functional test task to the NFMS.

Based on the above description, the present application describes, through fig. 4, a process for creating a running environment test task of a network element, where the creation of a functional test task of the network element generally needs interaction of multiple devices, and may be implemented by interaction of a first device, a second device, and even other devices, where the first device may be an OSS or BSS, the second device may implement a function of NFMS, NSSMS, NSMS, and the other devices may be Test management system. However, the second device may typically implement the functionality of Test management system, so the running environment testing task of the network element may be implemented by the interaction of the first device with the second device. Fig. 4 illustrates a first device as OSS, a second device for implementing NSSMS functions, and other devices as Test management system, VNF-MANO.

In step 401, the oss sends a create request message to the NSSMS to run the environment test tasks.

Specifically, the creation request message of the running environment test task includes: the device parameters of the network element are as the managedNTFPprofile, the virtualized network function parameters of the network element are as the vnfParametersList, and the running environment test task message, which can be understood as specific task information of the running environment test task, such as identification or task item information of the running environment test task, etc., and the running environment test task message comprises the SliceProfile information for testing the network, etc.

In step 402, NSSMS creates a slicing subnet for NF testing according to the SliceProfile parameter carried in the request message.

In step 403, NSSMS initiates a VNF instantiation request to a VNF-MANO.

Specifically, VNF instantiation of NF for testing is included in the request.

In step 404, the VNF-MANO returns a response message to NSSMS that VNF instantiation is complete.

In step 405, NSSMS sends the run-time environment test task to Test management system.

Specifically, the running environment test task may include VNF package information contained in a managednfpprofile and a vnfparamterlist. In addition, the VNF package may further include a test case of the NF, and Test management system performs related tests according to the information. Of course, in the case that fig. 4 does not include Test management system, this step may not be performed, and the testing of the functional test task may be accomplished directly through NSSMS.

In step 406, NSSMS sends an identification of the successful creation of the operational TestJob task to the OSS.

Specifically, the OSS may use the identification to query information such as the status of the running environment test task.

In step 407, NSSMS sends a parameter message to the OSS for the run-time environment test task.

Specifically, the parameter message of the running environment test task includes at least one of the following parameters: the identification of the runtime test task, the progress status of the runtime test task such as JobProgress, the execution Result of the runtime test task such as Result, and the Report of the runtime test task such as Report (link). In addition, the parameter message of the running environment test task can be displayed through the URL connection.

Furthermore, before executing step 407, the NSSMS may send the parameter message of the functional test task to the OSS instead of actively sending the parameter message after receiving the query request message of the OSS, which may better adapt to the requirement of the OSS and avoid the waste of signaling. Therefore, steps A to C may also be performed.

And step A, the OSS sends a task state query request message of the running environment test task to the NSSMS.

Specifically, the request message carries an identification of the operational testjob task that was successfully created in step 406.

Step B, NSSMS sends a task state query request message to Test management system for the running environment test task.

Step C, test management system sends a parameter message of the run-time environment test task to NSSMS.

By the method, the running environment test task is created, so that the data processing efficiency can be improved, and the smooth running of the network is ensured.

Based on the description of creation of the functional testjob in fig. 3 and the description of the operationalttestjob in fig. 4, the following detailed description is based on the specific application of fig. 3 and fig. 4, and is mainly applied to deployment of network elements and upgrading of network elements, although other application scenarios may be also involved in actual application, and the application is not limited in detail herein. As shown in fig. 5, the present application mainly introduces a method for transmitting a message, where the transmission of the message is mainly used in a deployment scenario of a network element, and may be illustrated by interaction between a first device and a second device, where the first device uses OSS as an example, and the second device uses NFMS as an example to implement an NFMS function, and the following is implemented:

step 501, the oss sends a network element creation request message to the NFMS, where the network element creation request message includes: the management function parameter is a managedNTFPProfile parameter and the virtualized network function parameter is a vnfParametersList parameter.

Accordingly, the NFMS receives the network element creation request message.

In step 502, the nfms determines whether an identification of a test task associated with the network element is included in the management function parameter.

In step 503A, in the case that the management function parameter includes the identifier of the test task associated with the network element, the NFMS determines the test task associated with the network element according to the identifier of the test task.

Wherein the test tasks include at least one of the following tasks: function test tasks of the network element and running environment test tasks of the network element. The testing tasks in the application can comprise the function testing tasks of the network element, the running environment testing tasks of the network element and both, and the application is not particularly limited herein and can be flexibly set according to actual requirements.

In addition, in the step 503A, the OSS may instruct the NFMS to determine the test task associated with the network element according to the identifier of the test task according to the own service requirement, which is not particularly limited herein.

In step 503B, in the case that the management function parameter does not include the identifier of the test task associated with the network element, the NFMS creates the test task associated with the network element.

If the test task is a functional test task of a network element, the test task may be created with reference to the flow of fig. 3, if the test task is an operation environment test task of a network element, the test task may be created with reference to the flow of fig. 4, and if the first test task includes both the functional test task of the network element and the operation environment test task of the network element, the test task may be created with reference to the flows of fig. 3 and 4 directly, which is not repeated herein.

In addition, in the above step 503B, the OSS may instruct the NFMS to create a test task according to its own service requirement, and the present application is not limited herein.

The steps 503A and 503B may be optionally performed, and the present application is not particularly limited herein.

In step 504A, if the test result of the test task passes, the NFMS creates a network element according to the virtualized network function parameter.

In step 504B, if the test result of the test task fails, the NFMS sends a response message of failure in network element creation to the OSS.

The optional execution of steps 504A and 504B described above is not particularly limited herein.

As shown in fig. 6, the present application mainly introduces a message transmission method, where the message transmission is mainly used in an upgrade scenario of a network element, and may be illustrated by interaction between a first device and a second device, where the first device is illustrated by using OSS as an example, and the second device is illustrated by using NFMS function and NSSMS function as an example, and the following is implemented:

in step 601, the oss sends a network element update request message to the NSSMS, where the network element update request message includes: updated virtualized network function parameters of the network element; the updated virtualized network function parameters of the network element include: updated version of the network element.

It should be noted that, the OSS may send a network element update request message to the NSSMS, or other request messages, which do not limit the name of the request message, or update the request message for the network element test task, etc., so long as the request message carries the updated virtualized network function parameter of the network element, it may be executed with reference to the flow described in fig. 6.

Accordingly, the NSSMS receives the network element update request message.

It should be noted that, in practical application, before executing step 601, NSSMS further determines a slice running the current NF, for example, the current NF version is v1.0, and runs in the network slice-1 subnet. Furthermore, the OSS may receive an updated version of the NF that may be carried in the new VNF package.

In step 602, NSSMS creates a test task associated with a network element.

If the test task is a functional test task of a network element, the test task may be created with reference to the flow of fig. 3, if the test task is an operation environment test task of a network element, the test task may be created with reference to the flow of fig. 4, and if the test task includes both the functional test task of the network element and the operation environment test task of the network element, the test task may be created with reference to the flows of fig. 3 and 4 directly, which is not repeated herein.

In step 603A, if the test result of the test task is passed, the NSSMS updates the version of the network element according to the updated virtualized network function parameter of the network element.

In step 603B, if the test result of the test task fails, the NSSMS sends a response message of failure of version update of the network element to the first device.

In actual use, before step 602 is performed, steps 1 a-1 b or steps 2 a-2 d-2 may be further performed, which are mainly to determine whether there is a first slice for performing the running environment test task, and update the first slice is performed as follows:

In step 1a, the oss sends a first slice to the NSSMS.

It should be noted that, the first slice is a slice which is automatically created by the OSS according to the requirement of the second test task; after the OSS sends the configuration information query request of NF to the NFMS, if it is determined that the running environment test task of NF exists, if it is queried that the first slice is not released, the OSS directly sends the first slice save to the NSSMS; the present application is not particularly limited herein, and may also be a first slice that is automatically created when the OSS sends a configuration information query request of NF to the NFMS and determines that an operation environment test task of NF exists and the queried first slice is released.

In step 1b, NSSMS updates the first slice according to the updated virtualized network function parameters of the network element.

Step 1 a-step 1b, test the new version network element on the test slice, even if the test has a problem, the actual network will not be affected, and the mode can ensure the security of the network.

In step 2a, nssms sends a configuration information query request message of the network element to NFMS.

In step 2b, the nfms sends a query request response message to the NSSMS.

Specifically, the response message includes a running environment test task associated with the network element.

In step 2c, NSSMS determines the presence of the first slice according to the running environment test task associated with the network element.

If it is determined that the first slice exists, the NSSMS updates the first slice according to the updated virtualized network function parameters of the network element, step 2 d-1.

If it is determined that the first slice does not exist, step 2d-2, the NSSMS creates the first slice according to the updated virtualized network function parameters of the network element.

Through the steps 2 a-2 d-2, whether the slice used for running the environment test by the network element in the initial deployment is deleted or not can be confirmed, if not, the test slice is continuously used for testing the network element with the new version, and resources can be saved.

In step 603A, the version of the network element may be updated in a second slice according to the updated virtualized network function parameter of the network element, where the second slice is a slice running the network element. After the test on the slice to be tested is finished and no problem exists, the actual network is updated, so that the operation of the actual network is ensured to be less influenced.

The scheme provided by the embodiment of the application is mainly introduced from the perspective of equipment interaction. It will be appreciated that in order to achieve the above-described functionality, each device may comprise corresponding hardware structures and/or software modules that perform each function. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The embodiment of the application can divide the functional units of the device according to the method example, for example, each functional unit can be divided corresponding to each function, and two or more functions can be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

In case of an integrated unit, fig. 7 shows a possible exemplary block diagram of the communication device involved in an embodiment of the application. As shown in fig. 7, the communication apparatus 700 may include: a processing unit 701 and a transceiver unit 702. The processing unit 701 is used for controlling and managing the operation of the communication device 700. The transceiver unit 702 is used to support communication between the communication apparatus 700 and other devices. Alternatively, the transceiver unit 702 may include a receiving unit and/or a transmitting unit for performing receiving and transmitting operations, respectively. Optionally, the communication device 700 may further comprise a storage unit for storing program code and/or data of the communication device 700. The transceiver unit may be referred to as an input-output unit, a communication unit, etc., and may be a transceiver; the processing unit may be a processor. When the communication device is a module (e.g., a chip) in the communication apparatus, the transceiver unit may be an input/output interface, an input/output circuit, an input/output pin, or the like, and may also be referred to as an interface, a communication interface, or an interface circuit; the processing unit may be a processor, a processing circuit, a logic circuit, or the like. Specifically, the device may be a message receiving device, that is, the second device, or may be a message sending device, that is, the first device.

In one embodiment, when the communication device is a message receiving device, the message receiving device may include: a processing unit 701 and a transmitting and receiving unit 702.

The transceiver unit 702 is configured to receive a network element creation request message from a message sending apparatus, where the network element creation request message includes: managing the function parameters and virtualizing the network function parameters; a processing unit 701, configured to determine, if the management function parameter includes an identifier of a test task associated with the network element, a test task associated with the network element according to the identifier of the test task; or under the condition that the management function parameter does not comprise the identification of the test task associated with the network element, the test task associated with the network element is created; if the test result of the test task passes, a network element is created according to the virtualized network function parameter; and if the test result of the test task does not pass, sending a response message of network element creation failure to the message sending device.

In an alternative manner, the transceiver unit 702 is further configured to receive a network element update request message from the message sending device, where the network element update request message includes: updated virtualized network function parameters of the network element; the updated virtualized network function parameters of the network element include: an updated version of the network element; the processing unit 701 is further configured to create a test task associated with the network element; if the test result of the test task is passed, updating the version of the network element according to the updated virtualized network function parameters of the network element; and if the test result of the test task does not pass, sending a response message of failure of version update of the network element to the message sending device.

In an alternative form, the test task includes at least one of the following tasks: function test tasks of the network element and running environment test tasks of the network element.

In an alternative way, the test tasks include: the function test task of the network element, the transceiver unit 702 is specifically configured to:

receiving a creation request message from a function test task of a message sending device, wherein the creation request message of the function test task comprises the following components: the equipment parameters of the network element, the virtualized network function parameters of the network element and the function test task message; sending a parameter message of the function test task to a message sending device, wherein the parameter message of the function test task comprises at least one of the following parameters: identification of a functional test task, progress status of the functional test task, execution result of the functional test task, and report of the functional test task.

In an alternative manner, before the transceiver unit 702 sends the parameter message of the functional test task to the messaging device, it is further configured to: a task state query request message is received from a functional test task of a messaging device.

In an alternative way, the test tasks include: the network element's operation environment test task, the receiving and transmitting unit 702 is specifically configured to:

Receiving a creation request message of an operation environment test task from a message sending device, wherein the creation request message of the operation environment test task comprises the following components: the method comprises the steps of equipment parameters of a network element, virtualized network function parameters of the network element and running environment test task information; sending a parameter message of the operation environment test task to a message sending device, wherein the parameter message of the operation environment test task comprises at least one of the following parameters: the method comprises the steps of identifying the running environment test task, the progress status of the running environment test task, the execution result of the running environment test task and the report of the running environment test task.

In an alternative manner, before the transceiver unit 702 sends the parameter message of the running environment test task to the first device, the transceiver unit is further configured to: a task state query request message is received from a running environment test task of a first device.

In an alternative way, the transceiver unit 702 is further configured to: receiving a first slice from a first device, the first slice for performing a runtime environment test task; the processing unit 701 is further configured to update the first slice according to the updated virtualized network function parameter of the network element.

In an optional manner, the processing unit 701 is further configured to determine, according to configuration information of the network element, that there is an operation environment test task associated with the network element; determining the existence of a first slice according to the running environment test task associated with the network element, wherein the first slice is used for executing the running environment test task; if the first slice exists, updating the first slice according to the updated virtualized network function parameters of the network element; or if it is determined that the first slice does not exist, creating the first slice according to the updated virtualized network function parameters of the network element.

In an alternative manner, the processing unit 701 is specifically configured to:

and updating the version of the network element in a second slice according to the updated virtualized network function parameters of the network element, wherein the second slice is the slice for running the network element.

In one embodiment, when the communication device is a message sending device, the message receiving device may include: a processing unit 701 and a transmitting and receiving unit 702.

The transceiver unit 702 is configured to send a network element creation request to the message receiving apparatus, where the network element creation request message includes: managing the function parameters and virtualizing the network function parameters; a processing unit 701, configured to instruct the message receiving apparatus to determine, when the management function parameter includes an identifier of a test task associated with the network element, the test task associated with the network element according to the identifier of the test task; or, in case the management function parameter does not include an identification of the test task associated with the network element, instructing the message receiving device to create the test task associated with the network element.

In an alternative manner, the transceiver unit 702 is further configured to send a network element update request message to the message receiving device, where the network element update request message includes: the updated virtualized network function parameters of the network element include: an updated version of the network element; the processing unit 701 is further configured to instruct the message receiving apparatus to create a test task associated with the network element.

the method comprises the steps of sending a creation request message of a functional test task to a message receiving device, wherein the creation request message of the functional test task comprises the following components: the equipment parameters of the network element, the virtualized network function parameters of the network element and the function test task message; receiving a parameter message of a function test task from a message receiving device, wherein the parameter message of the function test task comprises at least one of the following parameters: identification of a functional test task, progress status of the functional test task, execution result of the functional test task, and report of the functional test task.

In an alternative manner, before the transceiver unit 702 receives the parameter message from the function test task of the message receiving device, it is further configured to: and sending a task state query request message of the functional test task to the message receiving device.

The method comprises the steps of sending a creation request message of an operation environment test task to a message receiving device, wherein the creation request message of the operation environment test task comprises the following steps: the method comprises the steps of equipment parameters of a network element, virtualized network function parameters of the network element and running environment test task information; receiving a parameter message of an operation environment test task from a message receiving device, wherein the parameter message of the operation environment test task comprises at least one of the following parameters: the method comprises the steps of identifying the running environment test task, the progress status of the running environment test task, the execution result of the running environment test task and the report of the running environment test task.

In an alternative manner, before the transceiver unit 702 receives the parameter message of the running environment test task from the message receiving device, it is further configured to:

and sending a task query request message of the running environment test task to the message receiving device.

In an alternative way, the transceiver unit 702 is further configured to:

and sending a first slice to the message receiving device, wherein the first slice is used for executing the running environment testing task.

As shown in fig. 8, a communication device 800 is further provided in the present application. The communication device 800 may be a chip or a system-on-chip. The communication device may be located in an apparatus, for example, a first apparatus, or a second apparatus, etc., according to any of the method embodiments described above, so as to perform an action corresponding to the apparatus.

Alternatively, the chip system may be constituted by a chip, and may also include a chip and other discrete devices.

The communication device 800 includes a processor 810.

A processor 810 for executing computer programs stored in a memory 820 to perform the actions of the various devices in any of the method embodiments described above.

The communication device 800 may also include a memory 820 for storing a computer program.

Optionally, a memory 820 is coupled to the processor 810. Coupling is an indirect coupling or communication connection between devices, units, or modules, which may be in electrical, mechanical, or other form for the exchange of information between the devices, units, or modules. Optionally, the memory 820 is integrated with the processor 810.

The processor 810 and the memory 820 may be one or more, without limitation.

Optionally, in practical applications, the communications apparatus 800 may or may not include the transceiver 830, and the communications apparatus 800 may interact with other devices through the transceiver 830 as indicated by a dashed box. Transceiver 830 may be a circuit, bus, transceiver, or any other device that may be used to interact with information.

In a possible implementation manner, the communication apparatus 800 may be an access network device, or a session management network element, or a multicast/broadcast session management network element in each implementation of the above methods.

The specific connection medium between the transceiver 830, the processor 810, and the memory 820 is not limited in the embodiment of the present application. The embodiment of the present application is shown in fig. 8 with the memory 820, the processor 810, and the transceiver 830 connected by a bus, which is shown in fig. 8 with a bold line, and the connection between other components is merely illustrative, and not limited thereto. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 8, but not only one bus or one type of bus. In an embodiment of the present application, the processor may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic blocks disclosed in the embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.

In the embodiment of the present application, the memory may be a nonvolatile memory, such as a hard disk (HDD) or a Solid State Drive (SSD), or may be a volatile memory (RAM). The memory may also be any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory in embodiments of the present application may also be circuitry or any other device capable of implementing a memory function for storing computer programs, program instructions and/or data.

Based on the above embodiments, referring to fig. 9, another communication apparatus 900 is provided according to an embodiment of the present application, including: interface circuitry 910 and logic circuitry 920; interface circuit 910, which may be understood as an input-output interface, may be configured to perform the steps of transceiving the respective devices in any of the method embodiments described above, e.g. step 501 described above, where oss sends a network element creation request message to NFMS; logic 920 may be configured to execute code or instructions to perform the methods performed by the devices in any of the above embodiments, which are not described herein.

Based on the above embodiments, the present embodiments also provide a computer readable storage medium storing instructions that, when executed, cause the methods performed by the respective devices in any of the method embodiments described above to be implemented, for example, causing the method performed by the OSS or NFMS or NSSMS in the embodiments shown in fig. 5 or 6 to be implemented. The computer readable storage medium may include: various media capable of storing program codes, such as a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk.

Based on the above embodiments, the present application provides a communication system including a first device (e.g., OSS), a second device (e.g., NFMS), and a third device (e.g., NSSMS) mentioned in any of the above method embodiments, which may be used to perform the methods performed by the respective devices in any of the above method embodiments.

The communication system may further comprise Test management system, which Test management system may be capable of performing the relevant method of any of the method embodiments described above by data interaction with a second device.

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 an entirely hardware embodiment, an entirely 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, disk storage, CD-ROM, 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 methods, apparatus (systems) and computer program products according to the application. 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.

Claims

1. A method of receiving a message, comprising:

receiving a network element creation request message from a first device, wherein the network element creation request message comprises: managing the function parameters and virtualizing the network function parameters;

under the condition that the management function parameter comprises the identification of the test task associated with the network element, determining the test task associated with the network element according to the identification of the test task; or under the condition that the management function parameter does not comprise the identification of the test task associated with the network element, creating the test task associated with the network element;

if the test result of the test task passes, creating the network element according to the virtualized network function parameter;

And if the test result of the test task does not pass, sending a response message of the network element creation failure to the first equipment.

2. The method as recited in claim 1, further comprising:

receiving a network element update request message from the first device, where the network element update request message includes: updated virtualized network function parameters of the network element; the updated virtualized network function parameters of the network element include: an updated version of the network element;

creating a test task associated with the network element;

if the test result of the test task is passed, updating the version of the network element according to the updated virtualized network function parameter of the network element;

and if the test result of the test task does not pass, sending a response message of failure of version update of the network element to the first equipment.

3. The method according to claim 1 or 2, wherein the test task comprises at least one of the following tasks: and the function test task of the network element and the running environment test task of the network element.

4. A method according to claim 3, wherein the test task comprises: the function test task of the network element, and the creating the test task associated with the network element comprises the following steps:

Receiving a creation request message of the functional test task from the first device, wherein the creation request message of the functional test task comprises the following components: the equipment parameters of the network element, the virtualized network function parameters of the network element and the function test task message;

sending a parameter message of the function test task to the first device, wherein the parameter message of the function test task comprises at least one of the following parameters: the identification of the functional test task, the progress status of the functional test task, the execution result of the functional test task and the report of the functional test task.

5. The method of claim 4, wherein prior to sending the parameter message of the functional test task to the first device, further comprising:

and receiving a task state query request message of the function test task from the first device.

6. A method according to claim 3, wherein the test task comprises: the running environment test task of the network element, and the creating the test task associated with the network element comprises the following steps:

receiving a creation request message of the running environment test task from the first device, wherein the creation request message of the running environment test task comprises the following components: the equipment parameters of the network element, the virtualized network function parameters of the network element and the running environment test task message;

Sending a parameter message of the running environment test task to the first device, wherein the parameter message of the running environment test task comprises at least one of the following parameters: the method comprises the steps of identifying the running environment test task, the progress status of the running environment test task, the execution result of the running environment test task and the report of the running environment test task.

7. The method of claim 6, wherein prior to sending the parameter message of the execution environment test task to the first device, further comprising:

a task state query request message of the execution environment test task from the first device is received.

8. The method according to claim 6 or 7, further comprising:

receiving a first slice from a first device, the first slice for performing the runtime environment testing task;

and updating the first slice according to the updated virtualized network function parameters of the network element.

9. The method according to claim 6 or 7, further comprising:

determining that an operation environment test task associated with the network element exists according to the configuration information of the network element;

Determining the existence condition of a first slice according to the operation environment test task associated with the network element, wherein the first slice is used for executing the operation environment test task;

if the first slice exists, updating the first slice according to the updated virtualized network function parameters of the network element; or alternatively, the first and second heat exchangers may be,

if it is determined that the first slice does not exist, the first slice is created according to the updated virtualized network function parameters of the network element.

10. The method according to claim 2, wherein said updating the version of the network element according to updated virtualized network function parameters of the network element comprises:

updating the version of the network element in a second slice according to the updated virtualized network function parameters of the network element, wherein the second slice is a slice for running the network element.

11. A method for transmitting a message, comprising:

sending a network element creation request to a second device, wherein the network element creation request message comprises: managing the function parameters and virtualizing the network function parameters;

under the condition that the management function parameter comprises the identifier of the test task associated with the network element, the second equipment is instructed to determine the test task associated with the network element according to the identifier of the test task; or, in case that the management function parameter does not include the identifier of the test task associated with the network element, instructing the second device to create the test task associated with the network element.

12. The method as recited in claim 11, further comprising:

sending a network element update request message to the second device, where the network element update request message includes: the updated virtualized network function parameters of the network element include: an updated version of the network element;

instructing the second device to create a test task associated with the network element.

13. The method according to claim 11 or 12, wherein the test task comprises at least one of the following tasks: and the function test task of the network element and the running environment test task of the network element.

14. The method of claim 13, wherein the test task comprises: the function test task of the network element, the instructing the second device to create the test task associated with the network element, includes:

sending a creation request message of the functional test task to the second device, wherein the creation request message of the functional test task comprises the following components: the equipment parameters of the network element, the virtualized network function parameters of the network element and the function test task message;

Receiving a parameter message of the function test task from the second device, wherein the parameter message of the function test task comprises at least one of the following parameters: the identification of the functional test task, the progress status of the functional test task, the execution result of the functional test task and the report of the functional test task.

15. The method of claim 14, wherein prior to receiving the parameter message from the functional test task of the second device, further comprising:

and sending a task state query request message of the functional test task to the second device.

16. The method of claim 13, wherein the test task comprises: the running environment test task of the network element, the instructing the second device to create the test task associated with the network element, includes:

sending a creation request message of the operation environment test task to the second device, wherein the creation request message of the operation environment test task comprises the following components: the equipment parameters of the network element, the virtualized network function parameters of the network element and the running environment test task message;

Receiving a parameter message of the running environment test task from the second device, wherein the parameter message of the running environment test task comprises at least one of the following parameters: the method comprises the steps of identifying the running environment test task, the progress status of the running environment test task, the execution result of the running environment test task and the report of the running environment test task.

17. The method of claim 16, wherein prior to receiving the parameter message of the execution environment test task from the second device, further comprising:

and sending a task query request message of the running environment test task to the second equipment.

18. The method according to claim 16 or 17, further comprising:

and sending a first slice to the second device, wherein the first slice is used for executing the running environment testing task.

19. A method for receiving and transmitting a message, comprising:

the first device sends a network element creation request message to the second device, wherein the network element creation request message comprises: managing the function parameters and virtualizing the network function parameters;

the second device receives a network element creation request message from the first device;

Under the condition that the management function parameter comprises the identifier of the test task associated with the network element, the first equipment indicates the second equipment to determine the test task associated with the network element according to the identifier of the test task, and the second equipment determines the test task associated with the network element according to the identifier of the test task; or, in the case that the management function parameter does not include the identifier of the test task associated with the network element, the first device instructs the second device to create the test task associated with the network element, and the second device creates the test task associated with the network element;

if the test result of the test task passes, the second device creates the network element according to the virtualized network function parameter;

and if the test result of the test task is not passed, the second device sends a response message of the network element creation failure to the first device.

20. A message receiving apparatus, comprising:

a transceiver unit, configured to receive a network element creation request message from a message sending device, where the network element creation request message includes: managing the function parameters and virtualizing the network function parameters;

The processing unit is used for determining the test task associated with the network element according to the identifier of the test task under the condition that the management function parameter comprises the identifier of the test task associated with the network element; or if the management function parameter does not include the identifier of the test task associated with the network element, creating the test task associated with the network element; if the test result of the test task passes, creating the network element according to the virtualized network function parameter; and if the test result of the test task does not pass, sending a response message of the network element creation failure to the message sending device.

21. The apparatus of claim 20, wherein the transceiver unit is further configured to receive a network element update request message from the message sending apparatus, where the network element update request message includes: updated virtualized network function parameters of the network element; the updated virtualized network function parameters of the network element include: an updated version of the network element;

the processing unit is further configured to create a test task associated with the network element; if the test result of the test task is passed, updating the version of the network element according to the updated virtualized network function parameter of the network element; and if the test result of the test task does not pass, sending a response message of failure of version update of the network element to the message sending device.

22. The apparatus of claim 20 or 21, wherein the test task comprises at least one of: and the function test task of the network element and the running environment test task of the network element.

23. The apparatus of claim 22, wherein the test task comprises: the network element function test task, the transceiver unit is specifically configured to:

receiving a creation request message of the functional test task from the message sending device, wherein the creation request message of the functional test task comprises the following components: the equipment parameters of the network element, the virtualized network function parameters of the network element and the function test task message;

sending a parameter message of the function test task to the message sending device, wherein the parameter message of the function test task comprises at least one of the following parameters: the identification of the functional test task, the progress status of the functional test task, the execution result of the functional test task and the report of the functional test task.

24. The apparatus according to claim 23, wherein before the transceiving unit transmits the parameter message of the functional test task to the messaging apparatus, the transceiving unit is further configured to:

And receiving a task state query request message of the function test task from the message sending device.

25. The apparatus of claim 22, wherein the test task comprises: the network element running environment test task, the transceiver unit is specifically configured to:

receiving a creation request message of the running environment test task from the message sending device, wherein the creation request message of the running environment test task comprises the following components: the equipment parameters of the network element, the virtualized network function parameters of the network element and the running environment test task message;

sending a parameter message of the operation environment test task to the message sending device, wherein the parameter message of the operation environment test task comprises at least one of the following parameters: the method comprises the steps of identifying the running environment test task, the progress status of the running environment test task, the execution result of the running environment test task and the report of the running environment test task.

26. The apparatus of claim 25, wherein before the transceiver unit sends the parameter message of the running environment test task to the first device, the transceiver unit is further configured to:

27. The apparatus according to claim 25 or 26, wherein the transceiver unit is further configured to: receiving a first slice from a first device, the first slice for performing the runtime environment testing task;

the processing unit is further configured to update the first slice according to the updated virtualized network function parameter of the network element.

28. The apparatus according to claim 25 or 26, wherein the processing unit is further configured to determine, according to the configuration information of the network element, that there is an operating environment test task associated with the network element; determining the existence condition of a first slice according to the operation environment test task associated with the network element, wherein the first slice is used for executing the operation environment test task; if the first slice exists, updating the first slice according to the updated virtualized network function parameters of the network element; or if it is determined that the first slice does not exist, creating the first slice according to the updated virtualized network function parameters of the network element.

29. The apparatus according to claim 21, wherein the processing unit is specifically configured to:

30. A message transmission apparatus, comprising:

a transceiver unit, configured to send a network element creation request to a message receiving device, where the network element creation request message includes: managing the function parameters and virtualizing the network function parameters;

a processing unit, configured to instruct the message receiving device to determine, when the management function parameter includes an identifier of a test task associated with the network element, the test task associated with the network element according to the identifier of the test task; or, if the management function parameter does not include the identifier of the test task associated with the network element, instructing the message receiving device to create the test task associated with the network element.

31. The apparatus of claim 30, wherein the transceiver unit is further configured to send a network element update request message to the message receiving apparatus, the network element update request message including: the updated virtualized network function parameters of the network element include: an updated version of the network element;

The processing unit is further configured to instruct the message receiving device to create a test task associated with the network element.

32. The apparatus of claim 30 or 31, wherein the test task comprises at least one of: and the function test task of the network element and the running environment test task of the network element.

33. The apparatus of claim 32, wherein the test task comprises: the network element function test task, the transceiver unit is specifically configured to:

sending a creation request message of the functional test task to the message receiving device, wherein the creation request message of the functional test task comprises the following components: the equipment parameters of the network element, the virtualized network function parameters of the network element and the function test task message;

receiving a parameter message of the function test task from the message receiving device, wherein the parameter message of the function test task comprises at least one of the following parameters: the identification of the functional test task, the progress status of the functional test task, the execution result of the functional test task and the report of the functional test task.

34. The apparatus according to claim 33, wherein before the transceiving unit receives the parameter message of the functional test task from the message receiving apparatus, the transceiving unit is further configured to:

and sending a task state query request message of the function test task to the message receiving device.

35. The apparatus of claim 32, wherein the test task comprises: the network element running environment test task, the transceiver unit is specifically configured to:

transmitting a creation request message of the operation environment test task to the message receiving device, wherein the creation request message of the operation environment test task comprises the following components: the equipment parameters of the network element, the virtualized network function parameters of the network element and the running environment test task message;

receiving a parameter message of the running environment test task from the message receiving device, wherein the parameter message of the running environment test task comprises at least one of the following parameters: the method comprises the steps of identifying the running environment test task, the progress status of the running environment test task, the execution result of the running environment test task and the report of the running environment test task.

36. The apparatus of claim 35, wherein prior to the transceiver unit receiving a parameter message of the execution environment test task from the message receiving apparatus, the transceiver unit is further configured to:

37. The apparatus according to claim 35 or 36, wherein the transceiver unit is further configured to:

38. A communication device, comprising: at least one processor and memory;

the memory is used for storing a computer program or instructions;

the at least one processor configured to execute the computer program or instructions to cause the method of any one of claims 1-10 or any one of claims 11-18 to be performed.

39. A communication system comprising the message receiving means of any one of claims 20 to 29 and the message transmitting means of any one of claims 30 to 37.

40. A computer readable storage medium storing instructions which, when executed by a computer, cause the method of any one of claims 1-10 or any one of claims 11-18 to be performed.

41. A computer program product comprising a computer program or instructions which, when run on a computer, causes the method of any one of claims 1 to 10 or any one of claims 11 to 18 to be performed.