WO2022126389A1 - 建立网络连接的方法及装置 - Google Patents
建立网络连接的方法及装置 Download PDFInfo
- Publication number
- WO2022126389A1 WO2022126389A1 PCT/CN2020/136584 CN2020136584W WO2022126389A1 WO 2022126389 A1 WO2022126389 A1 WO 2022126389A1 CN 2020136584 W CN2020136584 W CN 2020136584W WO 2022126389 A1 WO2022126389 A1 WO 2022126389A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network
- identifier
- information
- access point
- template
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 148
- 230000005540 biological transmission Effects 0.000 claims description 110
- 238000004891 communication Methods 0.000 claims description 75
- 230000006870 function Effects 0.000 claims description 43
- 238000012545 processing Methods 0.000 claims description 42
- 238000004590 computer program Methods 0.000 claims description 15
- 238000013507 mapping Methods 0.000 claims description 11
- OOXMVRVXLWBJKF-DUXPYHPUSA-N n-[3-[(e)-2-(5-nitrofuran-2-yl)ethenyl]-1,2,4-oxadiazol-5-yl]acetamide Chemical compound O1C(NC(=O)C)=NC(\C=C\C=2OC(=CC=2)[N+]([O-])=O)=N1 OOXMVRVXLWBJKF-DUXPYHPUSA-N 0.000 claims 4
- 230000008569 process Effects 0.000 description 21
- 238000007726 management method Methods 0.000 description 15
- 238000010586 diagram Methods 0.000 description 11
- 230000008878 coupling Effects 0.000 description 5
- 238000010168 coupling process Methods 0.000 description 5
- 238000005859 coupling reaction Methods 0.000 description 5
- 238000013461 design Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000013468 resource allocation Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 1
- 238000010348 incorporation Methods 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
Definitions
- the present application relates to the field of network function virtualization (NFV), and in particular, to a method and apparatus for establishing a network connection.
- NFV network function virtualization
- networks deployed by network operators include a wide variety of hardware devices. These hardware devices can be dedicated devices or general-purpose devices.
- network operators need to develop new network services (NS). Each time network operators develop a new network service, they need to deploy new types of hardware devices in the network accordingly.
- NS network services
- NFV is proposed.
- general-purpose equipment and virtualization technology NFV enables general-purpose equipment to implement the functions of special-purpose equipment in traditional networks, thereby reducing the expensive cost of deploying special-purpose equipment.
- NFV can realize the decoupling of software and hardware. Through the decoupling of software and hardware, the function of network equipment no longer depends on special equipment.
- NFV can take advantage of the characteristics of cloud computing, so that resources (such as various hardware devices) can be fully and flexibly shared, enabling rapid development and deployment of new network services, and automatic deployment, elastic scaling, fault isolation and self-healing etc. Therefore, the application of NFV is becoming more and more extensive.
- NFV can be applied to the data center.
- a data center can include multiple virtual network functions (VNFs).
- VNFs virtual network functions
- One or more network services can be deployed on the VNF in the data center. If a certain network service deployed on the VNF of a data center needs to establish a connection across the data center, that is, if the VNF needs to communicate with the VNF of another data center, an end-to-end network connection needs to be established, that is, the need to establish an end-to-end network connection. Establish a network connection between this VNF and the VNF in another data center.
- the VNF 1011 of the data center 101 needs to communicate with the VNF 1021 of the data center 102, it is necessary to establish the VNF 1011 and the external gateway (data center gateway, DC) of the data center.
- connection between the transmission access GW 103 and the transmission access GW 104 may be established by a wide area network (wide area network, WAN) infrastructure manager (WAN infrastructure manager, WIM).
- a virtualized infrastructure manager (VIM) managing the data center 101 can configure the DC GW 1012 so that the DC GW 1012 establishes a connection with the transmission access GW 103.
- the VIM managing the data center 102 may configure the DC GW 1022 so that the DC GW 1022 establishes a connection with the transport access GW 104.
- VNF 1011 establishes connection with DC GW 1012
- VNF 1021 establishes connection with DC GW 1022
- the present application provides a method and apparatus for establishing a network connection, which can establish a connection between a VNF and a DC GW to realize a network connection across data centers.
- an embodiment of the present application provides a method for establishing a network connection, the method comprising: receiving NS instantiation request information from an operations support system and a business support system (operations support system and business support system, OSS/BSS); Obtain the identifier of the first service access point template, the identifier of at least one virtual link template, the information of the virtual link template corresponding to the identifier of each virtual link template and the information of the external network according to the NS instantiation request information, wherein , the information of the virtual link template is used to indicate the requirements for creating a virtual link connected to the first service access point, the information of the external network includes the identification of the first network and the identification of the connection service endpoint, the first network uses For connecting the first service access point and the connection service endpoint, the connection service endpoint is used to connect the data center managed by the virtual infrastructure manager VIM and the general transmission network; send first request information to the VIM, the first request The information is used to request the establishment of the first service access point, the first service
- a first service access point can be established, so that the first service access point is connected to the connection service endpoint through the first network, and the first service access point is connected to the VNF through the corresponding virtual link , which implements the connection between the VNF and the connection service endpoint, such as the DC GW.
- the NS instantiation request information includes the identity of the NS instance and the information of the external network, and the identity of the first service access point template is obtained according to the NS instantiation request information, and the identity of at least one virtual link template is obtained.
- Identification the information of the virtual link template corresponding to the identification of each virtual link template and the information of the external network, including: obtaining the information of the external network and the network service template corresponding to the identification of the NS instance according to the NS instantiation request information (network service descriptor, NSD) file, wherein, the NSD file includes the information of the first service access point template and the information of the virtual link template, and the information of the first service access point template includes the first service access point The identity of the template and the identity of the at least one virtual link template.
- NSD network service descriptor
- the information of the external network can be obtained from the NS instantiation request information, the identifier of the first service access point template, the identifier of at least one virtual link template, the identifier of each virtual link template can be obtained from the NSD file information of the corresponding virtual link template, so as to send the first request information to the VIM, so that the VIM establishes the first service access point according to the first request information.
- the NS instantiation request information also includes information of the transmission network, and the information of the transmission network includes the identification of the first service access point template, the identification of the connection service endpoint, and the identification of the second network , the identifier of the second network is used for the connection service endpoint to access the universal transmission network.
- the information of the transport network can be obtained from the NS instantiation request information, and thus, the second request information can be sent to the VIM, so that the VIM can forward the second request information to the connection service endpoint.
- the method further includes: receiving information from the transmission network of the OSS/BSS, where the information of the transmission network includes the identity of the first service access point template, the identity of the connection service endpoint, and the first The identifier of the second network, the identifier of the second network is used for the connection service endpoint to access the universal transmission network.
- the information of the transmission network can be obtained, and thus, the second request information can be sent to the VIM, so that the VIM can forward the second request information to the connection service endpoint.
- the information of the transport network is included in the NS instantiation update request. Based on the above method, the information of the transport network can be carried in the NS instantiation update request.
- the NS instantiation request information includes the identity of the NS instance; according to the NS instantiation request information, obtain the identity of the first service access point template, the identity of at least one virtual link template, each virtual link
- the information of the virtual link template corresponding to the identifier of the road template and the information of the external network including: obtaining the NSD file corresponding to the identifier of the NS instance, the NSD file including the information of the first service access point template and the virtual link template
- the information of the first service access point template includes the identifier of the first service access point template, the identifier of the at least one virtual link template, and the information of the external network.
- the identifier of the first service access point template, the identifier of the at least one virtual link template, the information of the external network and the The information of the virtual link template is used to send the first request information to the VIM, so that the VIM establishes the first service access point according to the first request information.
- the NS instantiation request information also includes information of the transmission network, and the information of the transmission network includes the identity of the first service access point template, the identity of the connection service endpoint and the identity of the second network, The identifier of the second network is used for the connection service endpoint to access the universal transport network.
- the information of the transport network can be obtained from the NS instantiation request information, and thus, the second request information can be sent to the VIM, so that the VIM can forward the second request information to the connection service endpoint.
- the method further includes: sending second request information to the VIM, where the second request information is used to request that the interface connecting the connection service endpoint and the universal transmission network be set to the second network , and map the identifier of the second network with the identifier of the first network on the connection service endpoint.
- the connection service endpoint can be set so that the interface connecting the connection service endpoint and the general transmission network is the second network, and the identifier of the second network has a mapping relationship with the identifier of the first network. In this way, the data center is connected to the general transmission network by connecting the service endpoints.
- the above method is used to set the network, it is not necessary to pay attention to whether the network of the general transmission network or other data centers is successfully established. That is to say, even if the general transmission network or the network of other data centers has not been established, the first service access point can be established by the above method, and the connection service endpoint can be set. Subsequently, after the general transmission network or the network of other data centers is established, it is only necessary to connect with the connection service endpoint, which simplifies the process of cross-domain network connection.
- the first network is an already deployed network or an undeployed network. Based on the above method, regardless of whether the external network is deployed or not, the above method can be used to establish the network.
- an embodiment of the present application provides a method for establishing a network connection.
- the method includes: receiving first request information from an NFV orchestrator (NFV orchestrator, NFVO), where the first request information is used to request the establishment of a first service an access point, where the first service access point is used to connect to the connection service endpoint through the first network, and is used to connect to a virtual link corresponding to the identifier of at least one virtual link template, wherein the identifier of the virtual link template Used to identify the virtual link template, the virtual link template is used to indicate the requirement for creating a virtual link connected with the first service access point, and the connection service endpoint is used to connect the data center managed by the VIM and the general transmission network ; Establish the first service access point according to the first request information.
- NFV orchestrator NFV orchestrator
- the first service access point can be established, so that the first service access point is connected to the connection service endpoint through the first network, and the first service access point is connected to the VNF through the corresponding virtual link , which implements the connection between the VNF and the connection service endpoint, such as the DC GW.
- the method further includes: receiving second request information from the NFVO, where the second request information is used to request that the interface connecting the connection service endpoint and the universal transmission network be set as the second network , and map the identification of the second network with the identification of the first network on the connection service endpoint, and the identification of the second network is used for the connection service endpoint to access the universal transport network; send to the connection service endpoint the second request information.
- the connection service endpoint can be set so that the interface connecting the connection service endpoint and the general transmission network is the second network, and the identifier of the second network has a mapping relationship with the identifier of the first network. In this way, the data center is connected to the general transmission network by connecting the service endpoints.
- the above method is used to set the network, it is not necessary to pay attention to whether the network of the general transmission network or other data centers is successfully established. That is to say, even if the general transmission network or the network of other data centers has not been established, the first service access point can be established by the above method, and the connection service endpoint can be set. Subsequently, after the general transmission network or the network of other data centers is established, it is only necessary to connect with the connection service endpoint, which simplifies the process of cross-domain network connection.
- the first network is an already deployed network or an undeployed network. Based on the above method, regardless of whether the external network is deployed or not, the above method can be used to establish the network.
- an embodiment of the present application provides a communication apparatus, which can implement the method in the first aspect or any possible implementation manner of the first aspect.
- the apparatus comprises corresponding units or components for carrying out the above-described method.
- the units included in the apparatus may be implemented by software and/or hardware.
- the apparatus may be, for example, a terminal, or a chip, a chip system, or a processor that can support the terminal to implement the above method.
- an embodiment of the present application provides a communication apparatus, which can implement the method in the second aspect or any possible implementation manner of the second aspect.
- the apparatus comprises corresponding units or components for carrying out the above-described method.
- the units included in the apparatus may be implemented by software and/or hardware.
- the apparatus may be, for example, a network device, or a chip, a chip system, or a processor that can support the network device to implement the above method.
- an embodiment of the present application provides a communication device, including: a processor, where the processor is coupled to a memory, and the memory is used to store a program or an instruction, when the program or the instruction is executed by the processor , so that the device implements the method described in the first aspect or any possible implementation manner of the first aspect.
- an embodiment of the present application provides a communication device, including: a processor, the processor is coupled to a memory, and the memory is used to store a program or an instruction, when the program or instruction is executed by the processor , so that the device implements the method described in the second aspect or any possible implementation manner of the second aspect.
- an embodiment of the present application provides a communication device, where the device is configured to implement the method described in the first aspect or any possible implementation manner of the first aspect.
- an embodiment of the present application provides a communication device, where the device is configured to implement the method described in the second aspect or any possible implementation manner of the second aspect.
- an embodiment of the present application provides a computer-readable medium on which a computer program or instruction is stored, and when the computer program or instruction is executed, enables a computer to perform the above-mentioned first aspect, or any possibility of the first aspect method described in the implementation of .
- an embodiment of the present application provides a computer-readable medium on which a computer program or instruction is stored, and when the computer program or instruction is executed, enables a computer to execute the second aspect or any possibility of the second aspect. method described in the implementation of .
- an embodiment of the present application provides a computer program product, which includes computer program code, and when the computer program code is run on a computer, enables the computer to execute the first aspect or any of the possible aspects of the first aspect. Implement the method described in the method.
- an embodiment of the present application provides a computer program product, which includes computer program code, and when the computer program code runs on a computer, the computer program code enables the computer to execute the second aspect or any of the possible second aspects. Implement the method described in the method.
- an embodiment of the present application provides a chip, including: a processor, where the processor is coupled to a memory, and the memory is used to store a program or an instruction, and when the program or instruction is executed by the processor , so that the chip implements the method described in the first aspect or any possible implementation manner of the first aspect.
- an embodiment of the present application provides a chip, including: a processor, where the processor is coupled to a memory, and the memory is used to store a program or an instruction, and when the program or instruction is executed by the processor , so that the chip implements the method described in the second aspect or any possible implementation manner of the second aspect.
- an embodiment of the present application provides a communication system.
- the system includes the device described in the third aspect and/or the device described in the fourth aspect, or the system includes the device described in the fifth aspect and/or the device described in the sixth aspect, or the system It includes the device of the seventh aspect and/or the device of the eighth aspect, or the system includes the chip of the thirteenth aspect and/or the chip of the fourteenth aspect.
- any of the communication devices, chips, computer-readable media, computer program products or communication systems provided above are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be achieved. Referring to the beneficial effects in the corresponding method, details are not repeated here.
- FIG. 1 is a schematic diagram of a network system provided by the prior art
- FIG. 2 is a schematic structural diagram of a network system provided by an embodiment of the present application.
- FIG. 3 is a schematic structural diagram of an NFV system provided by an embodiment of the present application.
- FIG. 4 is a schematic diagram of a hardware structure of a communication device provided by an embodiment of the present application.
- FIG. 5 is a schematic flowchart 1 of a method for establishing a network connection provided by an embodiment of the present application
- FIG. 6 is a second schematic flowchart of a method for establishing a network connection provided by an embodiment of the present application.
- FIG. 7 is a third schematic flowchart of a method for establishing a network connection provided by an embodiment of the present application.
- FIG. 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
- FIG. 9 is a schematic diagram of the composition of a communication system provided by an embodiment of the present application.
- the methods provided in the embodiments of the present application can be used in various network systems that require cross-network communication.
- the method provided by the embodiment of the present application is described below by taking the network system 20 shown in FIG. 2 as an example.
- the network system 20 may include a data center 201 , a data center 206 and a general transmission network 205 .
- Data center 201 and data center 206 may communicate through common transport network 205 .
- the data center 201 is communicatively connected to the general transmission network 205 through the connection service endpoint 204
- the data center 206 is communicatively connected to the general transmission network 205 through the connection service endpoint 207 to realize communication between the data center 201 and the data center 206 .
- NS 202 and NS 203 are deployed on the data center 201 .
- NS 208 and NS 209 are deployed on data center 206 .
- the NS 202 includes a service access point 2021, a VNF 2022 and a VNF 2023 that are communicatively connected to the service access point 2021.
- the NS 203 includes a service access point 2031, a VNF 2032, a VNF 2033, and a VNF 2034 that are communicatively connected to the service access point 2031.
- the NS 209 includes a service access point 2091, a VNF 2092 and a VNF 2093 that are communicatively connected to the service access point 2091.
- the NS 208 includes a service access point 2081, a VNF 2082, a VNF 2083, and a VNF 2084 communicatively connected to the service access point 2081.
- the service access point 2021 may be communicatively connected with the service access point 2031 , and may be communicatively connected with the connection service endpoint 204 .
- the service access point 2031 may be in communication connection with the service access point 2021 and in communication connection with the connection service endpoint 204 .
- the service access point 2081 may be communicatively connected to the service access point 2091 and to the connection service endpoint 207 .
- the service access point 2091 may be in communication connection with the service access point 2081 and in communication connection with the connection service endpoint 207 .
- the general transmission network in this embodiment of the present application may be a WAN, which is used to connect multiple data centers.
- the general transport network may include multiple networks.
- the NS in this embodiment of the present application may be various types of NS, such as Internet Protocol (Internet Protocol, IP) multimedia subsystem (IP multimedia subsystem, IMS) network service, or next-generation mobile core Network (evolved packet core, EPC) services, etc.
- Internet Protocol Internet Protocol
- IP multimedia subsystem IP multimedia subsystem
- EPC next-generation mobile core Network
- the data center in the embodiment of the present application can be used to transmit, accelerate, display, calculate or store information on the network infrastructure (for example, the VNF 2022 or the VNF 2082, etc.).
- the network infrastructure for example, the VNF 2022 or the VNF 2082, etc.
- the VNF in this embodiment of the present application may be a virtualized entity with network functions.
- a VNF has a mobile management entity (mobile management entity, MME) function
- the VNF is a virtual MME.
- the network function may be deployed on one or more virtual machines (virtual machines, VMs), so that the one or more VMs have the network function.
- the service access point in this embodiment of the present application may be used to connect to the connection service endpoint through an external network, and to connect to at least one virtual link.
- the external network can be used to connect service access points and service endpoints.
- the external network 210 in FIG. 2 is used to connect the service access point 2021 and connect the service endpoint 204 .
- Virtual links can be used to connect service access points and VNFs.
- the virtual link 2024 in FIG. 2 is used to connect the service access point 2021 and the VNF 2023
- the virtual link 2025 in FIG. 2 is used to connect the service access point 2021 and the VNF 2022.
- connection service endpoint in the embodiment of the present application may be used to connect the data center and the general transmission network.
- connection service endpoint 207 in FIG. 2 may be used to connect the data center 206 and the general transport network 205.
- the network system 20 shown in FIG. 2 is only used for example, and is not used to limit the technical solution of the present application. Those skilled in the art should understand that in the specific implementation process, the network system 20 may also include other elements, and the number of NSs, VNFs, connection service endpoints, service access points, and data centers may also be determined according to specific needs. No restrictions.
- FIG. 3 is a schematic structural diagram of an NFV system 30 according to an embodiment of the present application.
- the NFV system 30 may be used in various networks, eg implemented in a data center (data center 201 or data center 206 shown in Figure 2), a carrier network or a local area network.
- the NFV system 30 includes an NFV management and orchestration system (NFV management and orchestration, NFV MANO) 301, an NFV infrastructure (NFV infrastructure, NFVI) 302, a plurality of VNFs 303, a plurality of element management (EM) 304, and Operations support system and business support system (OSS/BSS) 305.
- NFV management and orchestration NFV management and orchestration
- NFV MANO NFV management and orchestration
- NFV infrastructure NFV infrastructure
- EM element management
- OSS/BSS Operations support system and business support system
- NFV MANO 301 can be used to perform monitoring and management of NFVI 302 and VNF 303.
- NFV MANO 301 may include NFV orchestrator (NFVO) 3011, one or more VNF managers (VNF manager, VNFM) 3012 and VIM 3013.
- NFVO 3011 can be used to manage the life cycle of virtualized services, and to allocate and schedule virtual resources in NFVI 302, etc.
- NFVO 3011 can communicate with one or more VNFMs 3012 to perform resource-related requests; NFVO 3011 can also send configuration information to VNFM 3012 to collect VNF 303 status information.
- NFVO 3011 may also communicate with VIM 3013 to perform resource allocation, and/or reservation, and to exchange virtualized hardware resource configuration and status information.
- VNFM 3012 may be used to manage the life cycle of one or more VNFs, eg, instantiating VNF 303, updating VNF 303, querying VNF 303, scaling VNF 303, terminating VNF 303 Wait. Further, VNFM 3012 can communicate with VNF 303 to complete VNF lifecycle management and exchange configuration and status information. In an NFV system, there can be multiple VNFMs. Different VNFMs can manage the lifecycle of different types of VNFs.
- the VIM 3013 can control and manage the interaction of the VNF 303 with computing hardware 3024, storage hardware 3025, network hardware 3026, virtual computing (virtual computing) 3021, virtual storage 3022, and virtual network 3023.
- the VIM 3013 can perform resource management functions, including managing infrastructure resources, allocation (eg, adding resources to virtual containers), and operational functions (eg, collecting NFVI fault information).
- VNFM 3012 and VIM 3013 can communicate with each other to request resource allocation, exchange virtualized hardware resource configuration and status information, etc.
- NFVI 302 in FIG. 3 includes a hardware resource layer, a virtualization layer, and a virtual resource layer.
- NFVI 302 includes hardware resources, software resources, or a combination of the two to complete the deployment of the virtualized environment.
- hardware resources and virtualization layers are used to provide virtualized resources, such as virtual machines and other forms of virtual containers, for VNF 303.
- the hardware resource layer includes computing hardware 3024 , storage hardware 3025 and network hardware 3026 .
- Computing hardware 3024 may be off-the-shelf hardware and/or custom-made hardware to provide processing and computing resources.
- the storage hardware 3025 may be storage capacity provided within the network or storage capacity resident in the storage hardware 3025 itself (local storage within the server).
- the resources of computing hardware 3024 and storage hardware 3025 may be pooled.
- Network hardware 3026 may be a switch, router, and/or any other network device configured to have switching capabilities.
- Network hardware 3026 may span multiple domains and may include multiple networks interconnected by one or more transport networks.
- the virtualization layer in NFVI 302 can abstract hardware resources and decouple VNF 303 from the physical layer in order to provide VNF 303 with virtualized resources.
- the virtual resource layer includes virtual computing 3021 , virtual storage 3022 and virtual network 3023 .
- Virtual computing 3021 and virtual storage 3022 may be provided to VNF 303 in the form of virtual machines, and/or other virtual containers.
- one or more VNFs 303 may be deployed on a virtual machine (VM).
- the virtualization layer abstracts the network hardware 3026, thereby forming a virtual network 3023, which may include a virtual switch used to provide connections between virtual machines and other virtual machines.
- computing hardware 3024, storage hardware 3025 and network hardware 3026 may include multiple racks, or multiple racks, or even multiple computer rooms.
- the EM 304 is a system used to configure and manage network elements in traditional telecommunication systems.
- the EM 304 can also be used to configure and manage the VNF, and initiate lifecycle management operations such as instantiation of a new VNF to the VNFM.
- OSS/BSS 305 supports various end-to-end telecom services.
- the management functions supported by OSS include: network configuration, service provision, and fault management.
- BSS can be used to process orders, payment, revenue, etc., and support product management, order management, revenue management and customer management.
- the NFV system 30 shown in FIG. 3 is only used for example, and is not used to limit the technical solution of the present application. Those skilled in the art should understand that in the specific implementation process, the NFV system 30 may also include other network elements, and the number of each network element may also be determined according to specific needs, which is not limited.
- each network element in FIG. 3 in this embodiment of the present application may be a functional module in a device.
- the function module may be an element in a hardware device, a software function module running on the hardware, or a virtualized function instantiated on a platform (eg, a cloud platform).
- FIG. 4 is a schematic diagram of a hardware structure of a communication device applicable to an embodiment of the present application.
- the communication apparatus 40 includes at least one processor 401 and at least one communication interface 404, which are used to implement the methods provided by the embodiments of the present application.
- the communication device 40 may also include a communication line 402 and a memory 403 .
- the processor 401 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors for controlling the execution of the programs of the present application. integrated circuit.
- CPU central processing unit
- ASIC application-specific integrated circuit
- Communication line 402 may include a path, such as a bus, to transfer information between the components described above.
- the communication interface 404 can be any device such as a transceiver, such as an Ethernet interface, a radio access network (RAN) interface, a wireless local area network (WLAN) interface, a transceiver, a pin , bus, or transceiver circuit, etc.
- RAN radio access network
- WLAN wireless local area network
- Memory 403 may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types of storage devices that can store information and instructions It can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, CD-ROM storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of being executed by a computer Access any other medium without limitation.
- the memory may exist independently and be coupled to processor 401 through communication line 402 .
- the memory 403 may also be integrated with the processor 401 .
- the memory provided by the embodiments of the present application may generally be non-volatile.
- the memory 403 is used for storing computer-executed instructions involved in executing the solutions provided by the embodiments of the present application, and the execution is controlled by the processor 401 .
- the processor 401 is configured to execute the computer-executed instructions stored in the memory 403, so as to implement the methods provided by the embodiments of the present application.
- the computer-executed instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
- the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
- the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 4 .
- the communication apparatus 40 may include multiple processors, such as the processor 401 and the processor 405 in FIG. 4 .
- processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.
- a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
- the above-mentioned communication apparatus 40 may be a general-purpose device or a dedicated device.
- the communication device 40 may be a desktop computer, a network server or a device with a similar structure in FIG. 4 .
- This embodiment of the present application does not limit the type of the communication device 40 .
- A/B may indicate A or B
- a and/or may be used to describe There are three kinds of relationships between related objects, for example, A and/or B, which can be expressed as: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural.
- words such as “first” and “second” may be used to distinguish technical features with the same or similar functions.
- the words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like do not limit the difference.
- words such as “exemplary” or “for example” are used to represent examples, illustrations or illustrations, and any embodiment or design solution described as “exemplary” or “for example” should not be construed are preferred or advantageous over other embodiments or designs.
- the use of words such as “exemplary” or “such as” is intended to present the relevant concepts in a specific manner to facilitate understanding.
- the NFVO, and/or the VIM, and/or the OSS/BSS may perform some or all of the steps in the embodiments of the present application. These steps are only examples, and the embodiments of the present application may also perform other steps. steps or variations of steps. In addition, various steps may be performed in different orders presented in the embodiments of the present application, and it may not be necessary to perform all the steps in the embodiments of the present application.
- the specific structure of the execution body of the method for establishing a network connection is not particularly limited in the embodiments of the present application, as long as the methods provided in the embodiments of the present application can be implemented.
- the execution body of the method for establishing a network connection provided in this embodiment of the present application may be NFVO, or a component applied in NFVO, such as a chip, which is not limited in this application.
- the execution body of the method for establishing a network connection provided by this embodiment of the present application may be a VIM, or a component applied in the VIM, such as a chip, which is not limited in this application.
- the execution body of the method for establishing a network connection may be an OSS/BSS, or a component applied in the OSS/BSS, such as a chip, which is not limited in this application.
- the following embodiments are described by taking as an example that the execution bodies of the method for establishing a network connection are NFVO, VIM, and OSS/BSS respectively.
- a method for establishing a network connection includes S501-S504.
- S501 OSS/BSS sends NS instantiation request information to NFVO.
- the OSS/BSS may be the OSS/BSS 305 in FIG. 3 .
- NFVO may be NFVO 3011 in Figure 3.
- the NS instantiation request information may be used to request to instantiate the NS.
- the NS instantiation request information may also be referred to as an NS instantiation request, a request to instantiate an NS, and the like, which is not limited.
- the OSS/BSS corresponding to the data center 201 can send the NS instantiation request information 1 to the NFVO corresponding to the data center 201, and the OSS/BSS corresponding to the data center 206 can send the NS instantiation request information 1 to the NFVO corresponding to the data center 201.
- the NFVO corresponding to the data center 206 sends the NS instantiation request message 2 .
- the NS instantiation request information 1 is used for requesting to instantiate the NS 202.
- the NS instantiation request information 2 is used to request the instantiation of the NS 209 .
- the content included in the NS instantiation request information may include but not be limited to the following three situations:
- the NS instantiation request information includes the identity of the NS instance.
- the identifier of the NS instance may be used to identify the NS instance.
- the NS instantiation request information also includes the information of the transmission network.
- the information of the transmission network may include the identifier of the first service access point template, the identifier of the connection service endpoint, and the identifier of the second network.
- the information of the transmission network may also be referred to as WAN information, wide area network information, or wide area network connection data information (WanConnectionData), etc., which are not limited.
- the identifier of the first service access point template may be used to identify the first service access point template.
- the first service access point template may also be referred to as a first SAPD (service access point descriptor).
- the first service access point template may be used to indicate requirements for creating the first service access point.
- the first service access point may be the service access point 2021, the service access point 2031, the service access point 2081 or the service access point 2091 in FIG. 2 .
- the service access point is a router resource. That is to say, the service access point has the function of routing.
- the identifier of the connection service endpoint may be used to identify the connection service endpoint.
- the connection service endpoint can be used to connect the data center managed by VIM and the general transport network.
- the VIM may be the VIM 3013 in FIG. 3 .
- the connection service endpoint may be the connection service endpoint 207 in FIG. 2, and the connection service endpoint 207 may be used for The data center 206 and the general transmission network 205 are connected.
- the connection service endpoint may be the connection service endpoint 204 in FIG. 2
- the connection service endpoint 204 may be used to connect to the data center 201 and Universal Transport Network 205.
- connection service endpoint is the external gateway of the data center.
- the connection service endpoint 204 is the external gateway of the data center 201
- the connection service endpoint 207 is the external gateway of the data center 206 .
- the identifier of the second network may be used to connect the service endpoint to access the general transmission network. That is to say, the second network is a network adjacent to the connection service endpoint in the general transmission network.
- the content included in the information of the transmission network may be as shown in Table 1.
- the information of the transmission network includes the related information of the first access point, the identification of the template and the information of the protocol data (protocolData).
- the relevant information of the first service access point includes the identifier of the first service access point template.
- the type of the identifier of the first service access point template is a string (string).
- the type of protocol data information is WAN connection protocol data (WanConnectionProtocolData).
- WanConnectionProtocolData includes connection service endpoint information (ConnectivityServiceEndpointInfo), and the connection service endpoint information includes an identifier of the connection service endpoint (connectivityServiceEndpointId).
- the connection service endpoint information also includes WAN Layer 2 protocol configuration information (SiteToWanLayer2ProtocolData).
- SiteToWanLayer2ProtocolData The interface connecting the service endpoint and the general transport network in SiteToWanLayer2ProtocolData is the second network.
- parameter quantity type Information about the first service access point 1 >Identification of the first service access point template 1 string protocolData WanConnectionProtocolData ...
- Table 1 is only an example of the information of the transmission network, and in a specific application, the information of the transmission network may also include more or less information than Table 1, which is not limited.
- the NS instantiation request information includes the identity of the NS instance and the information of the external network.
- the information of the external network includes the identifier of the first network and the identifier of the connection service endpoint.
- the information of the external network may also be referred to as the information of the externally connected network of the first service access point, the information of the external Network, etc., which is not limited.
- the identifier of the first network may be used to identify the first network.
- the first network may be used to connect the first service access point and the service endpoint, and the first network may also be referred to as an external network (external network). Further, the first network is an already deployed network or an undeployed network.
- first service access point and the connection service endpoint reference may be made to the description in Case 1 above.
- the first service access point is the service access point 2021 in FIG. 2 and the connection service endpoint is the connection service endpoint 204 in FIG.
- the network may be the external network 210 in FIG. 2 .
- the information of the external network is included in the information of the first service access point.
- the information of the first service access point may also be referred to as the first SapData.
- the content included in the information of the external network may be as shown in Table 2.
- the information of the external network includes externalNetwork, and the type of externalNetwork is external network data (externalNetworkdata). If the number of externalNetwork is 0, it can indicate that the information of the external network is not included in the NS instantiation request information.
- Table 2 is only an example of the information of the external network, and in a specific application, the information of the external network may also include more information than Table 2, which is not limited.
- the parameters included in externalNetworkdata can be as shown in Table 3.
- the segment ID is the ID of the undeployed network, that is to say, the ID of the newly established network is required.
- the number of segment identifiers is 0 or 1, and the type is string.
- the number of identifiers of the connection service endpoint is 0 or 1, and the type is string.
- the network name is the identifier of the deployed network.
- the number of network names is 0 or 1, and the type is string.
- externalNetworkdata includes the segment identifier and the identifier of the connection service endpoint, or externalNetworkdata includes the network name and the identifier of the connection service endpoint.
- parameter quantity type segmentationID 0 or 1 string connectivityServiceEndpointId 0 or 1 string networkName 0 or 1 string
- Table 3 is only an example of parameters included in externalNetworkdata, and in specific applications, externalNetworkdata may also include more or less parameters than Table 3, which is not limited.
- the NS instantiation request information includes the identity of the NS instance, the information of the external network, and the information of the transmission network.
- the OSS/BSS sends the NS instantiation request information to the NFVO.
- the OSS/BSS corresponding to the data center 201 sends the NS instantiation request information 1 to the NFVO corresponding to the data center 201, and the data The OSS/BSS corresponding to the center 206 sends the NS instantiation request information 2 to the NFVO corresponding to the data center 206 .
- the NS instantiation request information 1 is used for requesting to instantiate the NS 202.
- the NS instantiation request information 2 is used to request the instantiation of the NS 209.
- the OSS/BSS corresponding to the data center 206 sends the NS instantiation request 3 to the NFVO corresponding to the data center 206, and the OSS/BSS corresponding to the data center 201 sends the NFVO corresponding to the data center 201.
- the NS instantiation request information 3 is used to request to instantiate the NS 208.
- the NS instantiation request information 4 is used to request the instantiation of the NS 203.
- NFVO receives NS instantiation request information from OSS/BSS.
- S502 NFVO obtains the identifier of the first service access point template, the identifier of at least one virtual link template, the information of the virtual link template corresponding to the identifier of each virtual link template, and the information of the external network according to the NS instantiation request information .
- the identifier of the virtual link template corresponds to the identifier of the first service access point template.
- the identifier of the virtual link template can be used to identify a virtual link template (virtual link descriptor, VLD).
- VLD virtual link descriptor
- a virtual link template may be used to indicate requirements for creating a virtual link connected to the first service access point.
- the virtual link template corresponding to the service access point 2021 may be used to instruct the creation of the virtual link 2024 and the virtual link 2025 connected to the service access point 2021. Require.
- the information of the virtual link template may be used to indicate the virtual link template, that is, may be used to indicate a requirement for creating a virtual link connected to the first service access point.
- NFVO receives the network service template (network service descriptor, NSD) file from OSS/BSS, so that after NFVO receives the NS instantiation request information, according to the NS instantiation request information and the NSD file, Acquire the identifier of the first service access point template, the identifier of at least one virtual link template, the information of the virtual link template corresponding to the identifier of each virtual link template, and the information of the external network.
- NSD network service descriptor
- the NSD file includes the information of the first service access point template and the information of the virtual link template.
- the information of the first service access point template may include an identifier of the first service access point template, an identifier of at least one virtual link template, and information of an external network.
- the information of the first service access point template may also be referred to as information of the first sapd.
- the information of the external network can be specified in the design state. For the introduction of the information of the external network, refer to the description in Case 2 above.
- the NFVO obtains, according to the NS instantiation request information, the identifier of the first service access point template, the identifier of at least one virtual link template, the information of the virtual link template corresponding to the identifier of each virtual link template, and Information about the external network, including: NFVO obtains the NSD file corresponding to the identifier of the NS instance. In this way, the NFVO can obtain the identifier of the first service access point template, the identifier of at least one virtual link template, the information of the virtual link template corresponding to the identifier of each virtual link template, and the information of the external network from the NSD file.
- the NSD file includes the information of the first service access point template and the information of the virtual link template.
- the information of the first service access point template may include an identifier of the first service access point template and an identifier of at least one virtual link template.
- the NFVO obtains, according to the NS instantiation request information, the identifier of the first service access point template, the identifier of at least one virtual link template, the information of the virtual link template corresponding to the identifier of each virtual link template, and
- the information of the external network includes: NFVO obtains the information of the external network and the NSD file corresponding to the identifier of the NS instance according to the NS instantiation request information. In this way, NFVO can obtain the information of the external network from the NS instantiation request information, and obtain the identity of the first service access point template, the identity of at least one virtual link template and the identity of each virtual link template from the NSD file corresponding to information about the virtual link template.
- the NSD file may further include the identifier of the NSD.
- NFVO receives the NSD file, it can also receive a request from OSS/BSS to create an identifier of an NS instance.
- the request to create the identity of the NS instance includes the identity of the NSD.
- NFVO receives the request to create the identity of the NS instance, it sends the identity of the NS instance to OSS/BSS.
- the NS instantiation request information sent by OSS/BSS to NFVO may include the identity of the NS instance, so that NFVO can identify the NS instance according to the NS instance. The id to get the NSD file.
- the NFVO sends a request for creating a virtual link instance to the VIM, so that the VIM establishes a virtual link according to the request for creating a virtual link instance.
- the request for creating a virtual link instance may be used to establish a virtual link.
- the request for creating a virtual link instance may be used to establish a virtual link 2024 and a virtual link 2025 .
- the request for creating a virtual link instance includes the information of the virtual link template.
- the first request information may be used to establish a first service access point.
- the first service access point may be used to connect to the connection service endpoint through the first network, and to connect to the virtual link corresponding to the identifier of the at least one virtual link template.
- the service access point 2021 can be used to connect with the connection service endpoint 204 through the external network 210, and the service access point 2021 can also be connected to the virtual link 2024 and the virtual link. Road 2025.
- the first request information includes information of an external network and information of a virtual link instance.
- the information of the virtual link instance may include the identifier of the virtual link corresponding to the identifier of at least one virtual link template.
- the VIM receives the first request information from the NFVO.
- S504 The VIM establishes a first service access point according to the first request information.
- a possible implementation manner, where the VIM establishes the first service access point according to the first request information includes: the VIM establishes a connection between the first service access point and the connection service endpoint through the first network according to the first request information, and A connection between the first service access point and the virtual link corresponding to the identifier of the at least one virtual link description template is established.
- the first request information includes the information of the external network and the information of the virtual link instance
- the information of the external network includes the identification of the external network 210 and the connection to the service endpoint 204.
- ID the information of the virtual link instance includes the ID of the virtual link 2024 and the ID of the virtual link 2025
- the VIM creates a service access point 2021 to connect the virtual link 2024 and the virtual link 2025, and then creates a service access point Point 2021 to external network 210 connecting service endpoint 204.
- the VIM after the VIM establishes the first service access point, it sends a first establishment complete message to the NFVO to notify the NFVO that the establishment of the first service access point is completed. Subsequently, after receiving the first establishment complete message, the NFVO may send a second establishment complete message to the OSS/BSS to notify the OSS/BSS that the establishment of the first service access point is complete.
- the NFVO interacts with the VNFM to create a VNF, which may specifically include the following steps A-step C:
- Step A The NFVO sends a VNF instance ID creation request to the VNFM.
- the VNFM may be the VNFM 3012 in FIG. 3 .
- the VNF instance identifier creation request may be used to request the creation of a VNF instance identifier.
- the NSD file may further include information of a VNF template (VNF descriptor, VNFD).
- VNF descriptor VNF descriptor
- the information of the VNFD can be used to indicate the VNFD, that is, it can be used to indicate the requirement to create the VNF.
- the information of the VNFD includes the identifier of the VNFD and the VNFD.
- the VNF instance identity creation request may include the identity of the VNFD.
- the VNFM receives the VNF instance identifier creation request from the NFVO.
- the VNFM After receiving the VNF instance ID creation request, the VNFM creates the VNF instance ID.
- the VNFM can also establish a binding relationship between the instance identifier of the VNF and the identifier of the VNFD.
- Step B NFVO receives the VNF instance ID creation response from the VNFM.
- the VNF instance identifier creation response includes the instance identifier of the VNF. Further, the VNF instance identifier creation response also includes creation success information.
- Step C NFVO sends VNF instantiation request to VNFM.
- the VNF instantiation request may be used to request the creation of a VNF.
- the VNF instantiation request includes the instance identifier of the VNF.
- the VNFM receives the VNF instantiation request from the NFVO.
- the VNFM after receiving the VNF instantiation request from NFVO, the VNFM obtains the VNFD identifier according to the VNF instance identifier, and obtains the VNFD. Subsequently, the VNFM can create a VNF based on the VNFD.
- the first service access point can forward the data from the VNF to the connection service endpoint, and transfer the data from the connection service endpoint. Forwarded to the corresponding VNF.
- the service access point 2021 can forward the data from the VNF 2022 to the connection service endpoint 204, and forward the data from the connection service endpoint 204 to the VNF 2022.
- the first service access point may also forward data from the VNF to other service access points in the data center, and forward data from other service access points to the corresponding VNF.
- the service access point 2021 can forward the data from the VNF 2023 to the service access point 2031, and forward the data from the service access point 2031 to the VNF 2023.
- the VNFM after the VNFM creates the VNF, it sends a third establishment complete message to the NFVO to notify the NFVO that the VNF is created. Subsequently, after receiving the third establishment complete message, the NFVO may send a fourth establishment complete message to the OSS/BSS to notify the OSS/BSS that the VNF creation is complete.
- the first service access point can be established, so that the first service access point is connected to the connection service endpoint through the first network, and the first service access point is connected to the VNF through the corresponding virtual link, Implements the connection between the VNF and the connection service endpoint, for example, the DC GW.
- the actions of the OSS/BSS or NFVO or VIM in the above S501-S504 may be executed by the processor 401 in the communication device 40 shown in FIG. 4 calling the application code stored in the memory 403, which is not performed in this embodiment. any restrictions.
- the NFVO can send the second request information to the VIM, So that the VIM sends the second request information to the connection service endpoint.
- the connection service endpoint can be set according to the second request, so that the interface connecting the connection service endpoint and the general transmission network is the second network, and the identifier of the second network is the same as that of the second network.
- the identifiers of the first network have a mapping relationship. Specifically, reference may be made to the method shown in FIG. 6 , and the method shown in FIG. 5 may further include S601-S603.
- the second request information may be used to request that the interface connecting the connection service endpoint and the universal transmission network be set to the second network, and to set the identifier of the second network with the identifier of the first network on the connection service endpoint. Identifies the mapping.
- the second request information includes an identifier of the second network and an identifier of the first network. Further, the second request information also includes the identifier of the connection service endpoint.
- the VIM receives the second request information from the NFVO.
- the VIM sends the second request information to the connection service endpoint.
- the VIM after receiving the second request information, directly sends the second request information to the connection service endpoint, that is, the NFVO transparently transmits the second request information to the connection service endpoint through the VIM.
- the VIM after receiving the second request information, includes the second request information in one piece of information, for example, the first configuration information and sends it to the connection service endpoint.
- connection service endpoint receives the second request information from the VIM.
- connection service endpoint sets the connection interface between the connection service endpoint and the universal transmission network as the second network according to the second request information, and maps the identifier of the second network with the identifier of the first network on the connection service endpoint .
- connection interface between the connection service endpoint 204 and the universal transmission network 205 can be set to the second network, and mapping the identifier of the second network with the identifier of the first network on the connection service endpoint 204 .
- connection service endpoint can forward data from the first network to the second network, and forward data from the second network to the first network.
- the data center is connected to the general transmission network by connecting the service endpoints.
- a first configuration complete message is sent to the VIM to notify the VIM that the setting of the connection service endpoint is completed.
- the VIM may send a second configuration complete message to the NFVO to notify the NFVO that the setting of the connection service endpoint is complete.
- the NFVO may send a third configuration complete message to the OSS/BSS to notify the OSS/BSS that the setting of the connection service endpoint is complete.
- the connection service endpoint can be set so that the interface connecting the connection service endpoint and the general transmission network is the second network, and the identifier of the second network has a mapping relationship with the identifier of the first network.
- the data center is connected to the general transmission network by connecting the service endpoints.
- the method shown in FIG. 6 is used to set the network, it is not necessary to pay attention to whether the network of the general transmission network or other data centers is successfully established. That is to say, even if the general transmission network or the network of other data centers has not been established, the first service access point can be established by the method shown in FIG. 6 , and the connection service endpoint can be set. Subsequently, after the establishment of the general transmission network or other data center network is completed, it is only necessary to connect with the connection service endpoint, which simplifies the process of cross-domain network connection.
- the actions of the NFVO or VIM in the above S601-S603 may be executed by the processor 401 in the communication device 40 shown in FIG. 4 calling the application code stored in the memory 403, which is not limited in this embodiment.
- the OSS/BSS sends the information of the transmission network to the NFVO, and after the NFVO receives the information of the transmission network, it can send the second information to the VIM.
- Request information so that the VIM sends the second request information to the connection service endpoint.
- the connection service endpoint can be set according to the second request, so that the interface connecting the connection service endpoint and the general transmission network is the second network, and the identifier of the second network is the same as that of the second network.
- the identifiers of the first network have a mapping relationship. Specifically, reference may be made to the method shown in FIG. 7 , and the method shown in FIG. 5 may further include S701-S704.
- the OSS/BSS sends the information of the transmission network to the NFVO.
- the OSS/BSS after acquiring the information of the transmission network, sends the information of the transmission network to the VFVO.
- the OSS/BSS can obtain the information of the transport network from the slice manager, and send the information of the transport network to the VFVO.
- the operator determines the information of the transmission network, and after inputting the information of the transmission network into the OSS/BSS, the OSS/BSS sends the information of the transmission network to the VFVO.
- the information of the transport network is included in the NS instantiation update request.
- the NS instantiation update request can be used to request to update the relevant information of the NS instantiation.
- the NS instantiation update request may also be referred to as a request to update the NS instantiation, a request to update information of the NS instantiation, and the like.
- the NFVO receives information from the transport network of the OSS/BSS.
- connection service endpoint sets the connection interface between the connection service endpoint and the universal transmission network as the second network according to the second request information, and maps the identifier of the second network with the identifier of the first network on the connection service endpoint .
- the OSS/BSS may send the information of the transmission network to the NFVO after sending the NS instantiation request information.
- the NFVO can send the second request information to the connection service endpoint through the VIM after receiving the information of the transmission network, so as to set the connection service endpoint, so that the interface connecting the connection service endpoint and the general transmission network is the second network, and the second network
- the identifier of the first network has a mapping relationship with the identifier of the first network. In this way, the data center is connected to the general transmission network by connecting the service endpoints.
- connection service endpoint can be set. Subsequently, after the general transmission network or the network of other data centers is established, it is only necessary to connect with the connection service endpoint, which simplifies the process of cross-domain network connection.
- the actions of the OSS/BSS or NFVO or VIM in the above S701-S704 may be executed by the processor 401 in the communication device 40 shown in FIG. 4 calling the application code stored in the memory 403, which is not performed in this embodiment. any restrictions.
- each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. in the module.
- the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation.
- FIG. 8 shows a schematic structural diagram of a communication device 80 .
- the communication device 80 includes a transceiver module 801 and a processing module 802 .
- the communication device 80 is used to implement the functions of NFVO.
- the communication device 80 is, for example, the embodiment shown in FIG. 5 , the embodiment shown in FIG. 6 or the NFVO described in the embodiment shown in FIG. 7 .
- the communication device 80 may be an NFVO, a chip applied in the NFVO, or other combined devices or components having the above-mentioned NFVO function.
- the transceiver module 801 may be a transceiver, the transceiver may include an antenna and a radio frequency circuit, etc.
- the processing module 802 may be a processor (or a processing circuit), such as a baseband processor, and the baseband processor may Include one or more CPUs.
- the transceiver module 801 may be a radio frequency unit, and the processing module 802 may be a processor (or a processing circuit), such as a baseband processor.
- the transceiver module 801 may be an input and output interface of a chip (eg, a baseband chip), and the processing module 802 may be a processor (or a processing circuit) of the chip system, which may include one or more central processing units unit.
- transceiver module 801 in this embodiment of the present application may be implemented by a transceiver or a transceiver-related circuit component
- processing module 802 may be implemented by a processor or a processor-related circuit component (or referred to as a processing circuit).
- transceiving module 801 may be used to perform all transceiving operations performed by NFVO in the embodiment shown in FIG. 5, such as S501 and S503, and/or other processes for supporting the techniques described herein.
- the processing module 802 may be used to perform all operations performed by the NFVO in the embodiment shown in FIG. 5 except for the transceiving operations, eg, S502, and/or other processes for supporting the techniques described herein.
- the transceiving module 801 may be configured to perform all transceiving operations performed by NFVO in the embodiment shown in FIG. 6, such as S501, S503, S601, and/or other processes for supporting the techniques described herein.
- the processing module 802 may be used to perform all operations performed by the NFVO in the embodiment shown in FIG. 6 except for the transceiving operations, eg, S502, and/or other processes for supporting the techniques described herein.
- the transceiving module 801 may be configured to perform all transceiving operations performed by NFVO in the embodiment shown in FIG. 7, such as S501, S503, S701 and S702, and/or other processes for supporting the techniques described herein .
- the processing module 802 may be used to perform all operations performed by the NFVO in the embodiment shown in FIG. 7 except for the transceiving operations, eg, S502, and/or other processes for supporting the techniques described herein.
- the transceiver module 801 is configured to receive NS instantiation request information from the OSS/BSS.
- a processing module 802 configured to obtain, according to the NS instantiation request information, the identifier of the first service access point template, the identifier of at least one virtual link template, the information of the virtual link template corresponding to the identifier of each virtual link template, and the external The information of the network, wherein the information of the virtual link template is used to indicate the requirement of creating a virtual link connected with the first service access point, the information of the external network includes the identification of the first network and the identification of the connection service endpoint, the first The network is used to connect the first service access point and the connection service endpoint, and the connection service endpoint is used to connect the data center managed by the VIM and the general transmission network.
- the transceiver module 801 is further configured to send first request information to the VIM, where the first request information is used to request the establishment of a first service access point, and the first service access point is used to connect with the connection service endpoint through the first network, and use the The virtual link corresponding to the identifier of the at least one virtual link template is connected.
- the NS instantiation request information includes the identity of the NS instance and the information of the external network
- the processing module 802 is specifically configured to obtain the information of the external network and the network service corresponding to the identity of the NS instance according to the NS instantiation request information.
- a template NSD file where the NSD file includes information of the first service access point template and information of the virtual link template, and the information of the first service access point template includes the identifier of the first service access point template and at least one virtual link road template logotype.
- the NS instantiation request information also includes the information of the transmission network, and the information of the transmission network includes the identifier of the first service access point template, the identifier of the connection service endpoint, and the identifier of the second network.
- the identifier is used to connect the service endpoint to the general transport network.
- the transceiver module 801 is further configured to receive information from the transmission network of the OSS/BSS, and the information of the transmission network includes the identity of the first service access point template, the identity of the connection service endpoint, and the second network.
- the identifier of the second network is used to connect the service endpoint to the universal transmission network.
- the information of the transport network is included in the NS instantiation update request.
- the NS instantiation request information includes the identifier of the NS instance; the processing module 802 is specifically used to obtain the NSD file corresponding to the identifier of the NS instance, and the NSD file includes the information of the first service access point template and the virtual link.
- the information of the road template, the information of the first service access point template includes the identifier of the first service access point template, the identifier of at least one virtual link template, and the information of the external network.
- the NS instantiation request information also includes information of the transmission network, and the information of the transmission network includes the identifier of the first service access point template, the identifier of the connection service endpoint, and the identifier of the second network.
- the identifier is used to connect the service endpoint to the general transport network.
- the transceiver module 801 is further configured to send second request information to the VIM, where the second request information is used to request that the interface connecting the service endpoint and the general transmission network be set to the second network, and
- the connection service endpoint maps the identifier of the second network with the identifier of the first network.
- the first network is an already deployed network or an undeployed network.
- the communication device 80 is used to implement the functions of the VIM.
- the communication device 80 is, for example, the embodiment shown in FIG. 5 , the embodiment shown in FIG. 6 or the VIM described in the embodiment shown in FIG. 7 .
- the communication device 80 may be a VIM, or may be a chip applied in the VIM, or other combined device or component having the above-mentioned VIM function.
- the transceiver module 801 may be a transceiver, and the transceiver may include an antenna and a radio frequency circuit, etc.
- the processing module 802 may be a processor (or a processing circuit), such as a baseband processor, and the baseband processor may Include one or more CPUs.
- the transceiver module 801 may be a radio frequency unit, and the processing module 802 may be a processor (or a processing circuit), such as a baseband processor.
- the transceiver module 801 may be an input and output interface of a chip (eg, a baseband chip), and the processing module 802 may be a processor (or a processing circuit) of the chip system, which may include one or more central processing units unit.
- transceiver module 801 in this embodiment of the present application may be implemented by a transceiver or a transceiver-related circuit component
- processing module 802 may be implemented by a processor or a processor-related circuit component (or referred to as a processing circuit).
- the transceiving module 801 may be used to perform all transceiving operations performed by the VIM in the embodiment shown in FIG. 5 , such as S503 , and/or other processes used to support the techniques described herein.
- the processing module 802 may be configured to perform all operations performed by the VIM in the embodiment shown in FIG. 5 except for the transceiving operations, eg, S504, and/or other processes for supporting the techniques described herein.
- the transceiving module 801 may be configured to perform all transceiving operations performed by the VIM in the embodiment shown in FIG. 6, such as S503, S601 and S602, and/or other processes for supporting the techniques described herein.
- the processing module 802 may be configured to perform all operations performed by the VIM in the embodiment shown in FIG. 6 except for the transceiving operations, eg, S504, and/or other processes for supporting the techniques described herein.
- the transceiving module 801 may be configured to perform all transceiving operations performed by the VIM in the embodiment shown in FIG. 7, such as S503, S702, and S703, and/or other processes for supporting the techniques described herein.
- the processing module 802 may be configured to perform all operations performed by the VIM in the embodiment shown in FIG. 7 except for the transceiving operations, eg, S504, and/or other processes for supporting the techniques described herein.
- the transceiver module 801 is configured to receive first request information from NFVO, where the first request information is used to request the establishment of a first service access point, and the first service access point is used to connect to a connection service endpoint through a first network, And the virtual link corresponding to the identifier for connecting at least one virtual link template, wherein the identifier of the virtual link template is used to identify the virtual link template, and the virtual link template is used to instruct to create a connection with the first service access point According to the requirements of the virtual link, the connection service endpoint is used to connect the data center and the general transmission network managed by the virtual infrastructure manager VIM.
- the processing module 802 is configured to establish a first service access point according to the first request information.
- the transceiver module 801 is further configured to receive second request information from NFVO, where the second request information is used to request that the interface connecting the service endpoint and the general transmission network be set to the second network, and Mapping the identifier of the second network with the identifier of the first network on the connection service endpoint, where the identifier of the second network is used to connect the service endpoint to access the universal transmission network; the transceiver module 802 is further configured to send the second network to the connection service endpoint Request information.
- the first network is an already deployed network or an undeployed network.
- FIG. 9 shows a schematic diagram of the composition of a communication system.
- the communication system 90 may include: NFVO 901, VIM 902 and OSS/BSS 903. It should be noted that FIG. 9 is only an exemplary drawing, and the embodiment of the present application does not limit the network elements and the number of network elements included in the communication system 90 shown in FIG. 9 .
- the NFVO 901 is used to implement the functions of the NFVO in the method embodiments shown in the above-mentioned FIG. 5-FIG. 7 .
- NFVO 901 can be used to receive NS instantiation request information from OSS/BSS 903, and obtain the identity of the first service access point template, the identity of at least one virtual link template, and each virtual link template according to the NS instantiation request information. information of the virtual link template corresponding to the identifier of the road template and information of the external network, and send the first request information to the VIM 902.
- the VIM 902 is configured to implement the functions of the VIM in the method embodiments shown in FIG. 5 to FIG. 7 .
- the VIM 902 may be configured to receive the first request information from the NFVO 901, and establish the first service access point according to the first request information.
- the OSS/BSS 903 is used to implement the functions of the OSS/BSS in the method embodiments shown in FIG. 5 to FIG. 7 above.
- OSS/BSS 903 may be used to send NS instantiation request information to NFVO 901.
- the communication system 90 further includes a connection service endpoint 904 .
- the connection service endpoint 904 is used to implement the function of connecting the service endpoint in the method embodiments shown in FIG. 6 to FIG. 7 above.
- the connection service endpoint 904 can be configured to receive the second request information from the VIM 902, according to the second request information, set the connection interface between the connection service endpoint 904 and the universal transport network as the second network, and connect the service endpoint The identifier of the second network is mapped with the identifier of the first network.
- the disclosed apparatus and method may be implemented in other manners.
- the device embodiments described above are only illustrative.
- the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods.
- multiple units or components may be Incorporation may either be integrated into another device, or some features may be omitted, or not implemented.
- the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
- the units described as separate components may or may not be physically separated, and components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place, or may be distributed to multiple different places . Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
- each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
- the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
- the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a readable storage medium.
- the technical solutions of the embodiments of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, which are stored in a storage medium , including several instructions to make a device (which may be a single-chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application.
- the aforementioned storage medium includes: a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk and other mediums that can store program codes.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
参数 | 数量 | 类型 |
第一业务接入点的相关信息 | 1 | |
>第一业务接入点模板的标识 | 1 | string |
protocolData | WanConnectionProtocolData | |
… |
参数 | 数量 | 类型 |
externalNetwork | 0或1 | externalNetworkdata |
… |
参数 | 数量 | 类型 |
segmentationID | 0或1 | string |
connectivityServiceEndpointId | 0或1 | string |
networkName | 0或1 | string |
Claims (26)
- 一种建立网络连接的方法,其特征在于,所述方法包括:接收来自运营支持***和业务支持***OSS/BSS的网络服务NS实例化请求信息;根据所述NS实例化请求信息获取第一业务接入点模板的标识,至少一个虚拟链路模板的标识,每个虚拟链路模板的标识对应的虚拟链路模板的信息和外部网络的信息,其中,所述虚拟链路模板的信息用于指示创建同第一业务接入点连接的虚拟链路的要求,所述外部网络的信息包括第一网络的标识和连接服务端点的标识,所述第一网络用于连接所述第一业务接入点和所述连接服务端点,所述连接服务端点用于连接虚拟基础设施管理器VIM所管理的数据中心和通用传输网;向所述VIM发送第一请求信息,所述第一请求信息用于请求建立所述第一业务接入点,所述第一业务接入点用于通过所述第一网络与所述连接服务端点连接,以及用于连接所述至少一个虚拟链路模板的标识对应的虚拟链路。
- 根据权利要求1所述的方法,其特征在于,所述NS实例化请求信息包括NS实例的标识和所述外部网络的信息,所述根据所述NS实例化请求信息获取第一业务接入点模板的标识,至少一个虚拟链路模板的标识,每个虚拟链路模板的标识对应的虚拟链路模板的信息和外部网络的信息,包括:根据所述NS实例化请求信息获取所述外部网络的信息和所述NS实例的标识对应的网络服务模板NSD文件,其中,所述NSD文件包括第一业务接入点模板的信息和所述虚拟链路模板的信息,所述第一业务接入点模板的信息包括第一业务接入点模板的标识和所述至少一个虚拟链路模板的标识。
- 根据权利要求2所述的方法,其特征在于,所述NS实例化请求信息还包括传输网络的信息,所述传输网络的信息包括所述第一业务接入点模板的标识,所述连接服务端点的标识,以及第二网络的标识,所述第二网络的标识用于所述连接服务端点接入所述通用传输网。
- 根据权利要求2所述的方法,其特征在于,所述方法还包括:接收来自所述OSS/BSS的传输网络的信息,所述传输网络的信息包括所述第一业务接入点模板的标识,所述连接服务端点的标识,以及第二网络的标识,所述第二网络的标识用于所述连接服务端点接入所述通用传输网。
- 根据权利要求4所述的方法,其特征在于,所述传输网络的信息包括在NS实例化更新请求中。
- 根据权利要求1所述的方法,其特征在于,所述NS实例化请求信息包括NS实例的标识;所述根据所述NS实例化请求信息获取第一业务接入点模板的标识,至少一个虚拟链路模板的标识,每个虚拟链路模板的标识对应的虚拟链路模板的信息和外部网络的信息,包括:获取所述NS实例的标识对应的NSD文件,所述NSD文件包括第一业务接入点模板的信息和所述虚拟链路模板的信息,所述第一业务接入点模板的信息包括所述第 一业务接入点模板的标识,所述至少一个虚拟链路模板的标识和所述外部网络的信息。
- 根据权利要求6所述的方法,其特征在于,所述NS实例化请求信息还包括传输网络的信息,所述传输网络的信息包括所述第一业务接入点模板的标识,所述连接服务端点的标识以及第二网络的标识,所述第二网络的标识用于所述连接服务端点接入所述通用传输网。
- 根据权利要求3、4、5或7所述的方法,其特征在于,所述方法还包括:向所述VIM发送第二请求信息,所述第二请求信息用于请求将所述连接服务端点与所述通用传输网之间连接的接口设置为所述第二网络,以及在所述连接服务端点上将所述第二网络的标识与所述第一网络的标识做映射。
- 根据权利要求1-8中任一项所述的方法,其特征在于,所述第一网络为已经部署好的网络或者未部署的网络。
- 一种建立网络连接的方法,其特征在于,所述方法包括:接收来自网络功能虚拟化编排器NFVO的第一请求信息,所述第一请求信息用于请求建立第一业务接入点,所述第一业务接入点用于通过第一网络与连接服务端点连接,以及用于连接至少一个虚拟链路模板的标识对应的虚拟链路,其中,所述虚拟链路模板的标识用于标识所述虚拟链路模板,所述虚拟链路模板用于指示创建同第一业务接入点连接的虚拟链路的要求,所述连接服务端点用于连接虚拟基础设施管理器VIM所管理的数据中心和通用传输网;根据所述第一请求信息,建立所述第一业务接入点。
- 根据权利要求10所述的方法,其特征在于,所述方法还包括:接收来自所述NFVO的第二请求信息,所述第二请求信息用于请求将所述连接服务端点与所述通用传输网之间连接的接口设置为第二网络,以及在所述连接服务端点上将所述第二网络的标识与所述第一网络的标识做映射,所述第二网络的标识用于所述连接服务端点接入所述通用传输网;向所述连接服务端点发送所述第二请求信息。
- 根据权利要求10或11所述的方法,其特征在于,所述第一网络为已经部署好的网络或者未部署的网络。
- 一种通信装置,其特征在于,所述通信装置包括:收发模块和处理模块;所述收发模块,用于接收来自运营支持***和业务支持***OSS/BSS的网络服务NS实例化请求信息;所述处理模块,用于根据所述NS实例化请求信息获取第一业务接入点模板的标识,至少一个虚拟链路模板的标识,每个虚拟链路模板的标识对应的虚拟链路模板的信息和外部网络的信息,其中,所述虚拟链路模板的信息用于指示创建同第一业务接入点连接的虚拟链路的要求,所述外部网络的信息包括第一网络的标识和连接服务端点的标识,所述第一网络用于连接所述第一业务接入点和所述连接服务端点,所述连接服务端点用于连接虚拟基础设施管理器VIM所管理的数据中心和通用传输网;所述收发模块,还用于向所述VIM发送第一请求信息,所述第一请求信息用于请求建立所述第一业务接入点,所述第一业务接入点用于通过所述第一网络与所述连 接服务端点连接,以及用于连接所述至少一个虚拟链路模板的标识对应的虚拟链路。
- 根据权利要求13所述的通信装置,其特征在于,所述NS实例化请求信息包括网络服务NS实例的标识和所述外部网络的信息,所述处理模块,具体用于根据所述NS实例化请求信息获取所述外部网络的信息和所述NS实例的标识对应的网络服务模板NSD文件,其中,所述NSD文件包括第一业务接入点模板的信息和所述虚拟链路模板的信息,所述第一业务接入点模板的信息包括第一业务接入点模板的标识和所述至少一个虚拟链路模板的标识。
- 根据权利要求14所述的通信装置,其特征在于,所述NS实例化请求信息还包括传输网络的信息,所述传输网络的信息包括所述第一业务接入点模板的标识,所述连接服务端点的标识,以及第二网络的标识,所述第二网络的标识用于所述连接服务端点接入所述通用传输网。
- 根据权利要求14所述的通信装置,其特征在于,所述收发模块,还用于接收来自所述OSS/BSS的传输网络的信息,所述传输网络的信息包括所述第一业务接入点模板的标识,所述连接服务端点的标识,以及第二网络的标识,所述第二网络的标识用于所述连接服务端点接入所述通用传输网。
- 根据权利要求16所述的通信装置,其特征在于,所述传输网络的信息包括在NS实例化更新请求中。
- 根据权利要求13所述的通信装置,其特征在于,所述NS实例化请求信息包括NS实例的标识;所述处理模块,具体用于获取所述NS实例的标识对应的NSD文件,所述NSD文件包括第一业务接入点模板的信息和所述虚拟链路模板的信息,所述第一业务接入点模板的信息包括所述第一业务接入点模板的标识,所述至少一个虚拟链路模板的标识和所述外部网络的信息。
- 根据权利要求18所述的通信装置,其特征在于,所述NS实例化请求信息还包括传输网络的信息,所述传输网络的信息包括所述第一业务接入点模板的标识,所述连接服务端点的标识以及第二网络的标识,所述第二网络的标识用于所述连接服务端点接入所述通用传输网。
- 根据权利要求15、16、17或19所述的通信装置,其特征在于,所述收发模块,还用于向所述VIM发送第二请求信息,所述第二请求信息用于请求将所述连接服务端点与所述通用传输网之间连接的接口设置为所述第二网络,以及在所述连接服务端点上将所述第二网络的标识与所述第一网络的标识做映射。
- 根据权利要求13-20中任一项所述的通信装置,其特征在于,所述第一网络为已经部署好的网络或者未部署的网络。
- 一种通信装置,其特征在于,所述通信装置包括:收发模块和处理模块;所述收发模块,用于接收来自网络功能虚拟化编排器NFVO的第一请求信息,所述第一请求信息用于请求建立第一业务接入点,所述第一业务接入点用于通过第一网络与连接服务端点连接,以及用于连接至少一个虚拟链路模板的标识对应的虚拟链路,其中,所述虚拟链路模板的标识用于标识所述虚拟链路模板,所述虚拟链路模板用于指示创建同第一业务接入点连接的虚拟链路的要求,所述连接服务端点用于连接虚拟 基础设施管理器VIM所管理的数据中心和通用传输网;所述处理模块,用于根据所述第一请求信息,建立所述第一业务接入点。
- 根据权利要求22所述的通信装置,其特征在于,所述收发模块,还用于接收来自所述NFVO的第二请求信息,所述第二请求信息用于请求将所述连接服务端点与所述通用传输网之间连接的接口设置为第二网络,以及在所述连接服务端点上将所述第二网络的标识与所述第一网络的标识做映射,所述第二网络的标识用于所述连接服务端点接入所述通用传输网;所述收发模块,还用于向所述连接服务端点发送所述第二请求信息。
- 根据权利要求22或23所述的通信装置,其特征在于,所述第一网络为已经部署好的网络或者未部署的网络。
- 一种通信装置,其特征在于,包括:处理器,所述处理器与存储器耦合,所述存储器用于存储程序或指令,当所述程序或指令被所述处理器执行时,使得所述装置执行如权利要求1至9中任一项所述的方法,或者执行如权利要求10至12中任一项所述的方法。
- 一种计算机可读介质,其上存储有计算机程序或指令,其特征在于,所述计算机程序或指令被执行时使得计算机执行如权利要求1至9中任一项所述的方法或者如权利要求10至12中任一项所述的方法。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2020/136584 WO2022126389A1 (zh) | 2020-12-15 | 2020-12-15 | 建立网络连接的方法及装置 |
JP2023536074A JP2023552488A (ja) | 2020-12-15 | 2020-12-15 | ネットワーク接続を確立するための方法及び装置 |
EP20965407.8A EP4250103A4 (en) | 2020-12-15 | 2020-12-15 | METHOD AND DEVICE FOR ESTABLISHING NETWORK CONNECTION |
CN202080107879.3A CN116803061A (zh) | 2020-12-15 | 2020-12-15 | 建立网络连接的方法及装置 |
US18/335,020 US20230327959A1 (en) | 2020-12-15 | 2023-06-14 | Method for establishing network connection and apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2020/136584 WO2022126389A1 (zh) | 2020-12-15 | 2020-12-15 | 建立网络连接的方法及装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/335,020 Continuation US20230327959A1 (en) | 2020-12-15 | 2023-06-14 | Method for establishing network connection and apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022126389A1 true WO2022126389A1 (zh) | 2022-06-23 |
Family
ID=82059865
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/136584 WO2022126389A1 (zh) | 2020-12-15 | 2020-12-15 | 建立网络连接的方法及装置 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20230327959A1 (zh) |
EP (1) | EP4250103A4 (zh) |
JP (1) | JP2023552488A (zh) |
CN (1) | CN116803061A (zh) |
WO (1) | WO2022126389A1 (zh) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017185922A1 (zh) * | 2016-04-29 | 2017-11-02 | 华为技术有限公司 | 一种业务部署方法、装置以及网元 |
US20180004576A1 (en) * | 2015-01-23 | 2018-01-04 | Nec Corporation | Network functions virtualization management and orchestration method, network functions virtualization management and orchestration system, and program |
WO2019127418A1 (zh) * | 2017-12-29 | 2019-07-04 | 华为技术有限公司 | 网络服务管理方法、相关装置及*** |
US20200067782A1 (en) * | 2017-05-03 | 2020-02-27 | NEC Laboratories Europe GmbH | Mla based distributed management and orchestration (mano) system and method |
CN111221619A (zh) * | 2018-11-27 | 2020-06-02 | ***通信集团江西有限公司 | 一种业务开通和编排的方法、装置及设备 |
-
2020
- 2020-12-15 JP JP2023536074A patent/JP2023552488A/ja active Pending
- 2020-12-15 WO PCT/CN2020/136584 patent/WO2022126389A1/zh active Application Filing
- 2020-12-15 CN CN202080107879.3A patent/CN116803061A/zh active Pending
- 2020-12-15 EP EP20965407.8A patent/EP4250103A4/en active Pending
-
2023
- 2023-06-14 US US18/335,020 patent/US20230327959A1/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180004576A1 (en) * | 2015-01-23 | 2018-01-04 | Nec Corporation | Network functions virtualization management and orchestration method, network functions virtualization management and orchestration system, and program |
WO2017185922A1 (zh) * | 2016-04-29 | 2017-11-02 | 华为技术有限公司 | 一种业务部署方法、装置以及网元 |
US20200067782A1 (en) * | 2017-05-03 | 2020-02-27 | NEC Laboratories Europe GmbH | Mla based distributed management and orchestration (mano) system and method |
WO2019127418A1 (zh) * | 2017-12-29 | 2019-07-04 | 华为技术有限公司 | 网络服务管理方法、相关装置及*** |
CN111221619A (zh) * | 2018-11-27 | 2020-06-02 | ***通信集团江西有限公司 | 一种业务开通和编排的方法、装置及设备 |
Non-Patent Citations (2)
Title |
---|
ETSI: "Network Functions Virtualisation (NFV) Release 2; Protocols and Data Models; YAML data model specification for descriptor-based virtualised resource management", ETSI DRAFT; ETSI GS NFV-SOL 014 V2.8.1, 28 August 2020 (2020-08-28), pages 1 - 72, XP014385200 * |
See also references of EP4250103A4 * |
Also Published As
Publication number | Publication date |
---|---|
US20230327959A1 (en) | 2023-10-12 |
EP4250103A1 (en) | 2023-09-27 |
EP4250103A4 (en) | 2024-01-10 |
JP2023552488A (ja) | 2023-12-15 |
CN116803061A (zh) | 2023-09-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110088732B (zh) | 一种数据包处理方法、主机和*** | |
WO2019184967A1 (zh) | 一种网络切片的部署方法及装置 | |
CN105323136B (zh) | 信息的处理方法及装置 | |
EP3022888B1 (en) | Network element and method of running applications in a cloud computing system | |
WO2019127418A1 (zh) | 网络服务管理方法、相关装置及*** | |
WO2019062830A1 (zh) | 实例业务拓扑的生成方法及装置 | |
WO2019137516A1 (zh) | 网络切片部署方法及其装置 | |
US11539582B1 (en) | Streamlined onboarding of offloading devices for provider network-managed servers | |
WO2017185251A1 (zh) | Vnfm的确定方法和网络功能虚拟化编排器 | |
WO2021185083A1 (zh) | Vnf实例化方法及装置 | |
US20220350637A1 (en) | Virtual machine deployment method and related apparatus | |
US11985065B2 (en) | Enabling isolated virtual network configuration options for network function accelerators | |
WO2022126389A1 (zh) | 建立网络连接的方法及装置 | |
CN112953739A (zh) | 基于k8s平台纳管sdn的方法、***以及存储介质 | |
WO2021022947A1 (zh) | 一种部署虚拟机的方法及相关装置 | |
WO2022141293A1 (zh) | 一种弹性伸缩的方法及装置 | |
WO2018120222A1 (zh) | 一种管理vnffg的方法、装置和*** | |
WO2019011180A1 (zh) | 一种License的发送方法和装置 | |
WO2023030218A1 (zh) | 网络业务部署方法、nfvo以及nfv*** | |
CN111581203B (zh) | 信息处理方法、装置及存储介质 | |
WO2022089291A1 (zh) | 一种数据流镜像方法及装置 | |
US20230409362A1 (en) | Managing network function accelerators for radio-based applications from virtualized computing service control plane | |
US20230409363A1 (en) | Radio-based application processing server with network function accelerator at virtualization management offloading card | |
EP4149062A1 (en) | Deployment method and apparatus for virtualized network service | |
CN118118348A (zh) | 一种虚拟化网络功能vnf的实例化方法及装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20965407 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202080107879.3 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023536074 Country of ref document: JP |
|
ENP | Entry into the national phase |
Ref document number: 2020965407 Country of ref document: EP Effective date: 20230623 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |