Connection establishment method, communication device and storage medium

Abstract

An embodiment of the present application provides a connection establishment method, a communication device, and a storage medium. The connection establishment method includes: receiving a connection establishment request sent by a request initiator through a network call controller component of a client context, wherein the connection establishment request carries at least a first resource identifier and a tail resource identifier; then sending a connection request to a management context according to the connection establishment request through the network call controller component; then performing connection configuration according to the connection request through the management context to obtain connection resource information corresponding to the first resource identifier and the tail resource identifier; then receiving the connection resource information from the management context through the network call controller component; and sending the connection resource information to the request initiator through the network call controller component to complete the connection establishment. In an embodiment of the present application, the cross-layer connection interaction process between the controller and the request initiator is fully and clearly implemented, which can enhance the connection establishment capability in a multi-controller interaction scenario.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a connection establishment method, a communication device, and a storage medium. Background Art

[0002] In a single-domain scenario, only one controller can be used to schedule connections. In upper- and lower-layer interaction scenarios involving multiple controllers, context is used to divide and share resources. However, in this cross-layer management and control system, the cross-layer connection interaction process initiated by the client-layer controller is not clear enough, and the connection establishment capability in the interaction scenario is weak. Summary of the Invention

[0003] The embodiments of the present application provide a connection establishment method, a communication device, and a storage medium, which are intended to enhance the connection establishment capability in a multi-controller interaction scenario.

[0004] In a first aspect, an embodiment of the present application provides a connection establishment method, which is applied to a controller, wherein the controller is configured to have a customer context and a management context, and the customer context is configured to have a network call controller component;

[0005] The connection establishment method includes:

[0006] Receiving, through the network call controller component, a connection establishment request sent by a request initiator, wherein the connection establishment request carries at least a first resource identifier and a last resource identifier;

[0007] sending, by the network call controller component, a connection request to the management context according to the connection establishment request;

[0008] Performing connection configuration according to the connection request through the management context to obtain connection resource information corresponding to the first resource identifier and the last resource identifier;

[0009] receiving, by the network call controller component, the connection resource information from the management context;

[0010] The network call controller component sends the connection resource information to the request initiator to complete the connection establishment.

[0011] In a second aspect, an embodiment of the present application further provides a communication device comprising: at least one processor; at least one memory for storing at least one program; and implementing the connection establishment method as described above when at least one of the programs is executed by at least one of the processors.

[0012] In a third aspect, an embodiment of the present application further provides a computer-readable storage medium storing a program executable by a processor, wherein the program executable by the processor is used to implement the connection establishment method as described above when executed by the processor.

[0013] In a fourth aspect, an embodiment of the present application also provides a computer program product, comprising a computer program or computer instructions, wherein the computer program or the computer instructions are stored in a computer-readable storage medium, and the processor of the communication device reads the computer program or the computer instructions from the computer-readable storage medium, and the processor executes the computer program or the computer instructions, so that the communication device performs the connection establishment method as described above.

[0014] According to the connection establishment method, communication device and storage medium provided in the embodiments of the present application, when the controller receives a connection establishment request sent by the request initiator and carrying at least a first resource identifier and a tail resource identifier through the network call controller component in the client context within it, the controller first sends a connection request to the management context within it according to the connection establishment request, and then performs connection configuration according to the connection request through the management context to obtain the connection resource information corresponding to the first resource identifier and the tail resource identifier required by the request initiator, and then receives the connection resource information from the management context through the network call controller component, and then sends the connection resource information to the request initiator to complete the connection establishment. Therefore, the cross-layer connection interaction process between the controller and the request initiator is completely and clearly realized, and the connection establishment capability in the multi-controller interaction scenario can be enhanced. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a schematic diagram of the component interaction process during the connection establishment process in a single controller;

[0016] Figure 2 This is a flow chart of a connection establishment method provided by an embodiment of the present application;

[0017] Figure 3 This is an embodiment of the present application. Figure 2 Flowchart of step S2000 in FIG.

[0018] Figure 4 This is a schematic diagram of the connection request interaction process between the service layer controller and the client layer controller in the cross-layer SDN controller architecture provided by one embodiment of the present application;

[0019] Figure 5 This is a schematic diagram of the connection request interaction process between the service layer controller and the client layer controller in the cross-layer SDN controller architecture provided by another embodiment of the present application;

[0020] Figure 6Another embodiment of the present application provides Figure 2 Flowchart of step S2000 in FIG.

[0021] Figure 7 This is a schematic diagram of the connection request interaction process between the service layer controller and the client layer controller in the cross-layer SDN controller architecture provided by another embodiment of the present application;

[0022] Figure 8 This is a schematic diagram of the connection request interaction process between the service layer controller and the client layer controller in the cross-layer SDN controller architecture provided by another embodiment of the present application;

[0023] Figure 9 This is an embodiment of the present application. Figure 2 Flowchart of step S4000 in FIG.

[0024] Figure 10 This is an embodiment of the present application. Figure 2 Flowchart of step S5000 in FIG.

[0025] Figure 11 Another embodiment of the present application provides Figure 2 Flowchart of step S5000 in FIG.

[0026] Figure 12 is a flowchart of a connection establishment method provided by another embodiment of the present application;

[0027] Figure 13 This is a schematic diagram of the connection request interaction process in a peer-to-peer SDN controller architecture provided by an embodiment of the present application;

[0028] Figure 14 This is a schematic diagram of the connection request interaction process in a peer SDN controller architecture provided by another embodiment of the present application;

[0029] Figure 15 This is a schematic diagram of the connection request interaction process in a peer SDN controller architecture provided by another embodiment of the present application;

[0030] Figure 16 This is a schematic diagram of the connection request interaction process in a peer SDN controller architecture provided by another embodiment of the present application;

[0031] Figure 17 This is a schematic diagram of a communication device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0032] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0033] It should be noted that although the device schematics illustrate functional module divisions and the flowcharts illustrate logical sequences, in certain circumstances, the steps shown or described may be performed in a sequence that differs from the module divisions in the device or the sequence in the flowcharts. The terms "first," "second," and so on, used in the specification, claims, and accompanying drawings are used to distinguish similar items and are not necessarily intended to describe a specific sequence or precedence.

[0034] In the embodiments of the present application, words such as "further," "exemplarily," or "optionally" are used to indicate examples, illustrations, or descriptions and should not be interpreted as being more preferred or advantageous over other embodiments or designs. The use of words such as "further," "exemplarily," or "optionally" is intended to present related concepts in a concrete manner.

[0035] In order to more conveniently describe the working principle of the embodiments of the present application later, an introduction to the relevant technical scenarios is given below.

[0036] Management Control Continuum (MCC) integrates essentially identical management and control functions to achieve unified management and control of transport resources, providing integrated management and control services to upper-layer users. Software-defined network (SDN) controllers, element management systems (EMS), network management systems (NMS), and control planes are all examples of a management and control system. Functional modules within a management and control system provide functional services through interfaces.

[0037] Connection scheduling is a basic function of the management and control system. Figure 1 , Figure 1The interactive sequence of connection establishment in the management and control system is shown, where the components of the management and control system include: Network Call Controller (NCC), Connection Controller (CC), Routing Controller (RC), Link Resources Manager (LRM), Termination and Adaptation Performer (TAP), etc., as well as forwarding plane network elements.

[0038] The link topology and resource usage information in the controller is stored in the resource database (RDB).

[0039] The resources of the forwarding plane (such as time slots, bandwidth, etc.) need to be converted into resources that can be controlled in the management and control system. The resources of the forwarding plane are represented by forwarding points (FP) or forwarding end points (FwEP), and the resources used by the management and control system are represented by subnetwork points (SNP). The relationship between FP / FwEP and SNP is managed by the TAP module. One SNP can be bound to one FP / FwEP, or multiple SNPs can be bound to one FP / FwEP to indicate that multiple SNPs share the use of the FP / FwEP resources. In other words, the connection maintained by the management and control system uses a series of SNPs (including the first SNP and the last SNP) from the perspective of management; from the perspective of the forwarding plane, the FP / FwEP resources in the forwarding plane network element are used.

[0040] A group of SNPs is represented as a Subnetwork Point Pool (SNPP). The association between different SNPPs is represented as an SNPP Link. An SNP resource identifier represents an SNP instance, and an SNPP identifier represents an SNPP instance. A Boundary Resource Identifier (BRI) is used at domain boundaries to identify transmission resources at that boundary and to control interfaces between components.

[0041] A component interaction process for the controller to directly control the transmission resources is as follows:

[0042] Reference Figure 1 In the controller, when NCC receives the connection establishment request (i.e. Figure 1After step 1 shown in the figure (the same below, no further details are given), the boundary resource identifier BRI in the request (step 2) is converted by the Directory Services (DS) into two SNP resource identifiers within this controller. The connection establishment request may also carry some or all of the routing information of the connection. The NCC sends the first SNP resource identifier and the last SNP resource identifier to the CC (step 3). The CC requests the RC to query the connection route between the first and last SNP resource identifiers (step 4). The RC calculates the path that meets the CC's request based on the topology information and local connection status information provided by the LRM (step 5). For example, if the CC's request carries the routing information of the connection, the routing information of the connection can also participate in the RC's routing query. The RC returns the routing information to the CC, and the CC requests the LRM (step 6) to select an appropriate link connection from the links passed by the route; the LRM configures the forwarding resource usage status to the forwarding plane through the TAP component (steps 7 and 8). After the forwarding plane updates the link resource usage status and establishes the subnet cross-connection, the connection established by the controller is successfully established. After the establishment is successful, the NCC responds to the client that the connection is successfully established.

[0043] In the SDN Controller hierarchy, the upper and lower controllers form a client-server relationship. The client-server controllers interact with the service-server controllers through the ServerContext and ClientContext. Each controller can create multiple ClientContexts, at least one ServerContext, and one AdministrativeContext. Resources within each context include SNPPs and SNPP links.

[0044] For resource management and control within the SDN Controller, ServerContext resources can be forwarding-plane resources directly controlled by the local controller or resources provided by the service-layer Controller. These resources are mapped to the Local Resource Pool within the AdministrativeContext. The AdministrativeContext then allocates subsets of the Local Resource Pool to different ClientContexts. For each ClientContext, resources are provided to the client-layer Controller via the virtual network.

[0045] ServerContext to AdministrativeContext, and AdministrativeContext to ClientContext, can all undergo resource reconstruction, abstraction and mapping, as well as namespace conversion.

[0046] Client-layer controllers do not directly control the resources provided by service-layer controllers. When these resources are needed, they must be accessed through cross-layer interactions. In single-domain scenarios, connection scheduling can be accomplished with a single controller. In upper- and lower-layer interaction scenarios involving multiple controllers, resource division and sharing can be accomplished using contexts. However, in current cross-layer management and control systems, the cross-layer connection interaction processes and interface relationships initiated by client-layer controllers are not yet clearly defined, resulting in weak connection establishment capabilities in these interaction scenarios. Furthermore, the connection scheduling process between multiple peer controllers presents similar issues to cross-layer connection interactions.

[0047] Based on this, the present application provides a connection establishment method, a communication device, and a storage medium. The connection establishment method of one embodiment is applied to a controller, the controller is configured to have a client context and a management context, and the client context is configured to have a network call controller component; the method includes: receiving a connection establishment request sent by a request initiator through the network call controller component, wherein the connection establishment request carries at least a first resource identifier and a tail resource identifier; sending a connection request to the management context through the network call controller component according to the connection establishment request; performing connection configuration through the management context according to the connection request to obtain connection resource information corresponding to the first resource identifier and the tail resource identifier; receiving the connection resource information from the management context through the network call controller component; sending the connection resource information to the request initiator through the network call controller component to complete the connection establishment. In this embodiment, when the controller receives a connection establishment request carrying at least a first resource identifier and a tail resource identifier sent by the request initiator through the network call controller component in the client context within it, the controller first sends a connection request to the management context within it according to the connection establishment request, and then performs connection configuration according to the connection request through the management context to obtain the connection resource information corresponding to the first resource identifier and the tail resource identifier required by the request initiator, and then receives the connection resource information from the management context through the network call controller component, and then sends the connection resource information to the request initiator to complete the connection establishment. Therefore, the cross-layer connection interaction process between the controller and the request initiator is completely and clearly implemented, and the connection establishment capability in the multi-controller interaction scenario can be enhanced.

[0048] The embodiments of the present application are further described below with reference to the accompanying drawings.

[0049] like Figure 2 As shown, Figure 2 This is a flowchart of a connection establishment method provided by an embodiment of the present application. The connection establishment method can be, but is not limited to, applied to a controller, the controller being configured to have a customer context and a management context, the customer context being configured to have a network call controller component; the method can include, but is not limited to, steps S1000 to S5000.

[0050] Step S1000: receiving a connection establishment request sent by a requesting party through a network call controller component, wherein the connection establishment request carries at least a first resource identifier and a last resource identifier;

[0051] Step S2000: Sending a connection request to the management context according to the connection establishment request through the network call controller component;

[0052] Step S3000: performing connection configuration according to the connection request through the management context, and obtaining connection resource information corresponding to the first resource identifier and the last resource identifier;

[0053] Step S4000: receiving connection resource information from the management context via the network call controller component;

[0054] Step S5000: Send the connection resource information to the requesting party through the network call controller component to complete the connection establishment.

[0055] In this step, when the controller receives a connection establishment request carrying at least a first resource identifier and a last resource identifier sent by the request initiator through the network call controller component in its internal client context, the controller first sends a connection request to its internal management context according to the connection establishment request, and then performs connection configuration according to the connection request through the management context to obtain the connection resource information corresponding to the first resource identifier and the last resource identifier required by the request initiator, and then receives the connection resource information from the management context through the network call controller component, and then sends the connection resource information to the request initiator to complete the connection establishment. Therefore, the cross-layer connection interaction process between the controller and the request initiator is completely and clearly realized, which can enhance the connection establishment capability in the multi-controller interaction scenario.

[0056] In one embodiment, the requesting party may be a variety of device types, which are not limited here. For example, it may be, but is not limited to, another controller that is a superior or inferior controller of the controller, or it may be, but is not limited to, another controller that is equivalent to the controller, etc. These two different application scenarios will be explained separately later and will not be elaborated here.

[0057] In one embodiment, the network call controller component is also configured in the management context, and the management context and the customer context share the network call controller component. That is, within a controller, the components included in the Context represent the relationship between the Context and the logical functions of the components, and do not represent the actual deployment situation. During implementation, each component may have only one instance, and the component has the ability to interact across contexts.

[0058] In one embodiment, the management context is configured to have a network call controller component that is different from the network call controller component of the customer context, and the controller implements information interaction between the customer context and the management context through the network call controller component of the customer context and the network call controller component of the management context.

[0059] In one embodiment, the first resource identifier includes the first boundary resource identifier; the tail resource identifier includes the tail boundary resource identifier; that is, the boundary resource identifier can be converted into the first and last two SNP resource identifiers within this controller. In addition, part or all of the routing information of the connection may also be carried in the connection establishment request. The specific configuration needs to be made according to the actual application scenario and is not limited here.

[0060] In one embodiment, the client context is also configured to have a directory service component, which is used to convert resource identifiers. That is, the client context not only has the logical functions of the network call controller component, but also has the logical functions of the directory service component, and can convert boundary resource identifiers into the first and last SNP resource identifiers within this controller.

[0061] In one embodiment, similar to the configuration of the network call controller component, the directory service component is also configured in the management context, and the management context and the customer context share the directory service component; or, the management context is configured to have a directory service component that is different from the directory service component of the customer context.

[0062] like Figure 3 As shown, an embodiment of the present application further illustrates step S2000, which includes but is not limited to steps S2100 to S2300.

[0063] Step S2100: The network call controller component sends the first resource identifier and the last resource identifier to the directory service component according to the connection establishment request for resource identifier conversion, and obtains the first sub-network resource identifier and the last sub-network resource identifier returned by the directory service component;

[0064] Step S2200: Generate a connection request according to the first sub-network resource identifier and the last sub-network resource identifier through the network call controller component;

[0065] Step S2300: Send a connection request to the management context through the network call controller component.

[0066] In this step, the network call controller component sends the first resource identifier and the last resource identifier to the directory service component for resource identifier conversion according to the connection establishment request, so that the directory service component converts the first sub-network resource identifier and the last sub-network resource identifier and returns it to the network call controller component. On this basis, the network call controller component accurately and reliably generates a connection request according to the first sub-network resource identifier and the last sub-network resource identifier, thereby achieving the purpose of sending a connection request to the management context through the network call controller component.

[0067] The following specific examples are given to clearly illustrate the working principles of the above-mentioned relevant embodiments.

[0068] Example 1:

[0069] See also Figure 4 and Figure 5 , Figure 4 This is a schematic diagram of the connection request interaction process between the service layer controller and the client layer controller in the cross-layer SDN Controller architecture provided by one embodiment of the present application. Figure 5 This is a schematic diagram of the connection request interaction process between the service layer controller and the client layer controller in the cross-layer SDN Controller architecture provided by another embodiment of the present application, wherein Figure 4 and Figure 5 In the ClientContext, the NCC component and the DS component are included, and the client layer Controller triggers the interaction of multi-domain service layer connection requests.

[0070] like Figure 4As shown, n+1Controller and n Controller are upper and lower layer controllers, belonging to the Client / Server relationship, and communicate with each other through ClientContext-ServerContext. The necessary parameters, protocols, resources, etc. required for communication with the client layer Controller (i.e., n+1Controller) are configured in ClientContext, including ClientContext identification, communication encryption protocol, virtual network resources allocated to the client, and corresponding namespaces; the necessary parameters, protocols, resources, etc. required for communication with the service layer Controller (i.e., n Controller) are configured in ServerContext, including ServerContext identification, communication encryption protocol, virtual network resources provided by the service layer, and corresponding namespaces.

[0071] Multiple sets of ClientContext-ServerContext can be configured between the client-layer Controller and the service-layer Controller to meet different communication needs. They negotiate with each other to determine a mutually agreed-upon namespace and the resource identification format within that namespace. n Transmission resources within the Controller's scope are converted from ServerContext and local resources. n The Controller assigns a subset of transmission resources to different ClientContexts after conversion. This conversion is optional based on the trust relationship, and its functions include resource reconstruction, abstraction and mapping, and namespace conversion. For this controller, AdministrativeContext can also be called LocalContext, and Context refers to any of ClientContext, ServerContext, and AdministrativeContext. The resources of the above controller and Context refer to SNP, SNPP, or SNPP Link, and the resources within the forwarding plane refer to FP or FwEP.

[0072] It should be noted that Figure 4 and Figure 5 The components in the Context represent logical functions and do not represent the actual deployment situation. In a Controller, the components contained in the Context represent the relationship between the Context and the logical functions of the components. This is to facilitate the expression of the interaction logic in the process. For example, Figure 4In the example, ClientContext is configured with NCC, AdministrativeContext is also configured with NCC, and the two NCCs are interconnected. Alternatively, each component may have only one instance when implemented. If the NCCs are combined into one instance, the component has the ability to interact across contexts, and the interaction process between NCCs is completed within the NCC. Figure 5 As shown, ClientContext and AdministrativeContext share NCC in this case.

[0073] Figure 4 and Figure 5 The specific steps of the connection request interaction process shown are as follows:

[0074] When the NCC of n Controller receives the connection establishment request initiated by n+1 Controller (i.e. Figure 4 The request carries the ServerContext resource identifier of n+1Controller. The ServerContext resource identifier contains at least the first and last resource identifiers (BRIs).

[0075] Then, the NCC of the ClientContext in the n Controller passes the connection establishment request to the DS component, which converts the resource identifier in the connection request into the SNP resource identifier of the AdministrativeContext (step 2);

[0076] Then, the NCC of ClientContext carries the SNP resource identifier of AdministrativeContext and makes a connection request to AdministrativeContext (step 3);

[0077] After the AdministrativeContext completes the connection configuration (AdministrativeContext may recursively perform connection calculations and then request configuration), the configuration result of the connection request is returned to the NCC of the ClientContext. The result contains the connection resource information of the SNP resource identifier of the AdministrativeContext path (step 4);

[0078] Preferably, Figure 5As shown, the NCC of ClientContext and the NCC of AdministrativeContext are combined into one instance. Then the NCC component has the ability to interact across contexts and the interaction process between NCCs. That is to say, the above steps 3 and 4 are completed within the NCC. Figure 5 The other implementation steps for the scenario shown are the same as Figure 4 The same is true for the .

[0079] Then, the NCC converts the resource identifier in the returned connection resource information into a ClientContext resource identifier through the DS component (step 5), and then returns it to the n+1Controller (step 6), thereby completing the entire connection request process.

[0080] In particular, the n Controller may omit steps 2 and 5 according to the connection request information or local control policy.

[0081] In one embodiment, the client context is further configured to have a connection controller component, a routing controller component, and a link resource manager component. The connection controller component is used to request the routing controller component to query the connection route and request the link resource manager component to select a connection link. The routing controller component is used to calculate the connection route, and the link resource manager component is used to select a connection link from the links that the route passes through.

[0082] like Figure 6 As shown, an embodiment of the present application further illustrates step S2000, which includes but is not limited to steps S2400 to S2900.

[0083] Step S2400: Acquire the first sub-network resource identifier and the last sub-network resource identifier of the customer context according to the first resource identifier and the last resource identifier in the connection establishment request, wherein the first sub-network resource identifier of the customer context corresponds to the first resource identifier, and the last sub-network resource identifier of the customer context corresponds to the last resource identifier;

[0084] Step S2500: using the network call controller component to send the first sub-network resource identifier and the last sub-network resource identifier of the customer context to the routing controller component through the connection controller component;

[0085] Step S2600: Requesting the link resource manager component to obtain, through the routing controller component, the first routing topology and first local connection state information corresponding to the first sub-network resource identifier and the last sub-network resource identifier of the customer context;

[0086] Step S2700: Calculating a routing path based on the first routing topology and the first local connection state information by the routing controller component to obtain first target routing information, wherein the first target routing information includes a first sub-network resource identifier and a last sub-network resource identifier of the customer context;

[0087] Step S2800: using the network call controller component to receive first target routing information from the routing controller component via the connection controller component;

[0088] Step S2900: Generate a connection request according to the first target routing information through the network call controller component, and send the connection request to the management context through the network call controller component.

[0089] In this step, since the first and last sub-network resource identifiers of the customer context are obtained based on the first and last resource identifiers in the connection establishment request, the network call controller component can further transmit the first and last sub-network resource identifiers of the customer context to the routing controller component via the connection controller component. The routing controller component then requests the link resource manager component to obtain the first routing topology and first local connection state information corresponding to the first and last sub-network resource identifiers of the customer context, and calculates the first routing topology and first local connection state information to obtain first target routing information. This facilitates the network call controller component to receive the first target routing information, generate a connection request based on the first target routing information, and send the connection request to the management context. It can be seen that, compared to the previous embodiment, the network call controller component can generate a connection request based not only on the first and last sub-network resource identifiers, but also on the first target routing information in this implementation scenario. In either case, the purpose of reliably sending the connection request to the management context can be achieved.

[0090] In one embodiment of the present application, step S2000 is further explained. When the client context is further configured to have a directory service component, step S2000 includes but is not limited to steps S21000 to S28000.

[0091] Step S21000: Acquire the first sub-network resource identifier and the last sub-network resource identifier of the customer context according to the first resource identifier and the last resource identifier in the connection establishment request, wherein the first sub-network resource identifier of the customer context corresponds to the first resource identifier, and the last sub-network resource identifier of the customer context corresponds to the last resource identifier;

[0092] Step S22000: using the network call controller component to send the first sub-network resource identifier and the last sub-network resource identifier of the customer context to the routing controller component through the connection controller component;

[0093] Step S23000: Requesting the link resource manager component via the routing controller component to obtain the second routing topology and second local connection state information corresponding to the first sub-network resource identifier and the last sub-network resource identifier of the customer context;

[0094] Step S24000: Calculating a routing path based on the second routing topology and the second local connection state information by the routing controller component to obtain second target routing information, wherein the second target routing information includes a first sub-network resource identifier and a last sub-network resource identifier of the customer context;

[0095] Step S25000: using the network call controller component to receive second target routing information from the routing controller component via the connection controller component;

[0096] Step S26000: The network call controller component sends the second target routing information to the directory service component for resource identifier conversion of the first sub-network resource identifier and the last sub-network resource identifier of the customer context, and obtains third target routing information returned by the directory service component, which includes the first sub-network resource identifier and the last sub-network resource identifier of the management context.

[0097] Step S27000: Generate a connection request according to the third target routing information through the network call controller component;

[0098] Step S28000: Send a connection request to the management context through the network call controller component.

[0099] In this step, since the first sub-network resource identifier and the last sub-network resource identifier of the customer context are obtained according to the first resource identifier and the last resource identifier in the connection establishment request, based on this, the network call controller component can be further used to send the first sub-network resource identifier and the last sub-network resource identifier of the customer context to the routing controller component through the connection controller component, so that the routing controller component requests the link resource manager component to obtain the second routing topology and the second local connection state information corresponding to the first sub-network resource identifier and the last sub-network resource identifier of the customer context, and calculates the second routing topology and the second local connection state information to obtain the second target routing information, thereby facilitating the network call controller component to receive the second target routing information, and then the network call controller component sends the second target routing information to the link resource manager component. The target routing information is sent to the directory service component for resource identifier conversion of the first sub-network resource identifier and the last sub-network resource identifier of the customer context, so as to obtain the third target routing information returned by the directory service component, which includes the first sub-network resource identifier and the last sub-network resource identifier of the management context. Finally, the network call controller component generates a connection request according to the third target routing information and sends the connection request to the management context. It can be seen that compared with the aforementioned embodiment, not only can the network call controller component generate a connection request according to the first sub-network resource identifier and the last sub-network resource identifier, but also the connection request can be generated according to the first target routing information, and the connection request can also be generated according to the third target routing information. However, no matter which one, the purpose of reliably sending a connection request to the management context can be achieved.

[0100] The following specific examples are given to clearly illustrate the working principles of the above-mentioned relevant embodiments.

[0101] Example 2:

[0102] See also Figure 7 and Figure 8 , Figure 7 This is a schematic diagram of the connection request interaction process between the service layer controller and the client layer controller in the cross-layer SDN Controller architecture provided by another embodiment of the present application. Figure 8 This is a schematic diagram of the connection request interaction process between the service layer controller and the client layer controller in the cross-layer SDN Controller architecture provided by another embodiment of the present application, wherein Figure 7 and Figure 8 In the example, ClientContext includes NCC components, DS components, CC components, RC components, and LRM components, and the client layer Controller triggers the interaction of multi-domain service layer connection requests.

[0103] It should be noted that Figure 7and Figure 8 The components in the Context represent logical functions and do not represent the actual deployment situation. In a Controller, the components contained in the Context represent the relationship between the Context and the logical functions of the components. This is to facilitate the expression of the interaction logic in the process. For example, Figure 7 In the example, ClientContext is configured with NCC, AdministrativeContext is also configured with NCC, and the two NCCs are interconnected. Alternatively, each component may have only one instance when implemented. If the NCCs are combined into one instance, the component has the ability to interact across contexts, and the interaction process between NCCs is completed within the NCC. Figure 8 As shown, ClientContext and AdministrativeContext share NCC in this case.

[0104] Figure 7 and Figure 8 The specific steps of the connection request interaction process shown are as follows:

[0105] When the NCC of Controller n receives the connection establishment request initiated by Controller n+1 (step 1), the request carries the ServerContext resource identifier of Controller n+1. The ServerContext resource identifier contains at least the first and last resource identifiers (BRIs).

[0106] Then, the NCC of the ClientContext in the n Controller sends a connection request carrying the SNP resource identifier of the ClientContext to the CC (step 2). The CC requests the RC to query the connection route between the first and last SNP resource identifiers (step 3). The RC calculates the path calculation result that meets the CC's request based on the topology information and local connection status information provided by the LRM (step 4). The CC then continues to make a connection request to the NCC with its path calculation result.

[0107] Then, the NCC passes the connection establishment request to the DS component, converts the resource identifier in the connection establishment request into the SNP resource identifier of the AdministrativeContext (step 5), and then the NCC makes a connection request to the AdministrativeContext (step 6);

[0108] After the AdministrativeContext completes the connection configuration (AdministrativeContext may recursively perform connection calculations and then request configuration), the configuration result of the connection request is returned to the NCC of the ClientContext. The result contains the connection resource information of the SNP resource identifier of the AdministrativeContext path (step 7);

[0109] Preferably, Figure 8 As shown, the NCC of ClientContext and the NCC of AdministrativeContext are combined into one instance. Then the NCC component has the cross-Context interaction capability and the interaction process between NCCs. That is to say, the above step 7 is completed within the NCC. Figure 8 The other implementation steps for the scenario shown are the same as Figure 7 is similar, so I will not go into details here.

[0110] Then, the NCC converts the resource identifier in the returned connection resource information into a ClientContext resource identifier through the DS component (step 8), and then sends it to the CC (step 9). After the CC confirms the connection information is successful, it returns it to the n+1Controller (step 10), thus completing the entire connection request process.

[0111] In particular, the n Controller may omit steps 5 and 8 according to the connection request information or local control policy.

[0112] like Figure 9 As shown, in one embodiment of the present application, when the customer context is also configured to have a directory service component, the connection resource information includes the first sub-network resource identifier and the last sub-network resource identifier of the management context, and step S4000 is further explained. Step S4000 includes but is not limited to steps S4100 to S4300.

[0113] Step S4100: receiving connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the management context from the management context through the network call controller component;

[0114] Step S4200: The network call controller component sends the connection resource information to the directory service component for resource identifier conversion of the first sub-network resource identifier and the last sub-network resource identifier of the management context, thereby obtaining connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the customer context.

[0115] Step S4300: Receive connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the client context from the directory service component through the network call controller component.

[0116] In this step, when the customer context is also configured to have a directory service component and the connection resource information includes the first sub-network resource identifier and the last sub-network resource identifier of the management context, the network call controller component receives the connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the management context from the management context, and then sends the connection resource information to the directory service component for resource identifier conversion to obtain the connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the customer context, and finally receives the connection resource information after resource identifier conversion from the directory service component. It can be seen that the resource identifier conversion through the directory service component is conducive to finally receiving the required connection resource information from the management context.

[0117] like Figure 10 As shown, in one embodiment of the present application, when the client context is further configured to have a connection controller component, step S5000 is further explained, and step S5000 includes but is not limited to steps S5100 to S5200.

[0118] Step S5100: The network call controller component sends the connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the customer context to the connection controller component for information confirmation;

[0119] Step S5200: When the connection controller component confirms the connection resource information successfully, the connection controller component sends the connection resource information to the requesting party through the network call controller component.

[0120] In this step, the connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the customer context is sent to the connection controller component for information confirmation through the network call controller component. The purpose is to confirm whether the connection resource information is successful through the connection controller component. When the connection controller component confirms the connection resource information successfully, the connection controller component is used to send the connection resource information to the request initiator through the network call controller component. It can be seen that the information confirmation process performed by the connection controller component can effectively ensure that the connection resource information in the confirmed successful state can be returned and sent.

[0121] like Figure 11 As shown, in one embodiment of the present application, when the client context is further configured to have a connection controller component, step S5000 is further explained, and step S5000 includes but is not limited to steps S5300 to S5500.

[0122] Step S5300: The network call controller component sends the connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the management context to the connection controller component for information confirmation;

[0123] Step S5400: When the connection controller component successfully confirms the connection resource information, the network call controller component obtains the first sub-network resource identifier and the last sub-network resource identifier of the customer context based on the first sub-network resource identifier and the last sub-network resource identifier of the management context;

[0124] Step S5500: The network call controller component sends the connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the client context to the request initiator.

[0125] In this step, the connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the customer context is sent to the connection controller component for information confirmation through the network call controller component. The purpose is to confirm whether the connection resource information is successful through the connection controller component. When the connection controller component confirms the connection resource information successfully, the network call controller component obtains the first sub-network resource identifier and the last sub-network resource identifier of the customer context based on the first sub-network resource identifier and the last sub-network resource identifier of the management context, and then sends the connection resource information to the request initiator through the network call controller. It can be seen that the information confirmation process performed by the connection controller component can effectively ensure that the connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the customer context is generated through the network call controller.

[0126] In one embodiment, the controller and the request initiator are peer controllers to each other. That is to say, in this case, the relationship between the controller and the request initiator is not a fixed upper and lower layer relationship, that is, it is not a fixed subordinate relationship between the client layer and the service layer, but a mutual peer relationship. Subsequent examples will explain the connection interaction process in this scenario in detail, which will not be repeated here.

[0127] like Figure 12 As shown, in one embodiment of the present application, when the controller is further configured to have a service context, the connection establishment method further includes but is not limited to step S6000.

[0128] Step S6000: When connection resource information that meets the connection requirements of the requesting party is not obtained locally, a request for obtaining connection resource information is sent to the network call controller component in the client context of the next peer controller through the service context.

[0129] In this step, when connection resource information that meets the connection requirements of the initiator of the request is not obtained locally, it means that there is no network call controller component in the client context of the controller locally that can meet the request of the initiator of the request to obtain connection resource information. At this time, a request for obtaining connection resource information is sent to the network call controller component in the client context of the next peer controller through the service context, in the hope that the next peer controller can meet the request of the initiator of the request to obtain connection resource information, thereby obtaining connection resource information that meets the connection requirements of the initiator of the request.

[0130] The following specific examples are given to more clearly illustrate the working principles of the above-mentioned related embodiments.

[0131] Example 3:

[0132] See also Figure 13 and Figure 14 , Figure 13 This is a schematic diagram of the connection request interaction process in a peer-to-peer (P2P) SDNController architecture provided by an embodiment of the present application. Figure 14 This is a schematic diagram of the connection request interaction process in the Peer-Peer SDN Controller architecture provided by another embodiment of the present application, wherein Figure 13 and Figure 14 In the ClientContext, both NCC and DS components are included.

[0133] exist Figure 13 and Figure 14 In the example, there is a peer-peer relationship between n+1Controller and nController. nController communicates with n+1Controller's ServerContext through ClientContext, that is, n+1Controller can initiate connection establishment to nController through ServerContext; n+1Controller communicates with nController's ServerContext through ClientContext, that is, nController can initiate connection establishment to n+1Controller through ServerContext.

[0134] Figure 13 and Figure 14 The specific steps of the connection request interaction process shown are as follows:

[0135] When the n Controller initiates a connection establishment with the n+1 Controller, the n Controller acts as the client-layer Controller, and the n+1 Controller acts as the server-layer Controller. The connection establishment process is the same as that in Example 1. Therefore, the n Controller in this example plays the same role as the n+1 Controller in Example 1. The connection establishment process in Example 1 has been described in detail and will not be repeated here to avoid redundancy.

[0136] When the n+1Controller initiates a connection establishment with the nController, the n+1Controller acts as the client-layer Controller, and the nController acts as the service-layer Controller. The connection establishment process is the same as that in Example 1 above. In this case, the nController in this example plays the same role as that in Example 1, and the n+1Controller in this example plays the same role as that in Example 1. Since the connection establishment process in Example 1 has been described in detail, it will not be repeated here to avoid redundancy.

[0137] It should be noted that when n Controller initiates a connection establishment to n+1Controller, n+1Controller should discard the ServerContext resource corresponding to the ClientContext of n Controller during connection calculation to avoid resource nesting loops, and vice versa.

[0138] Example 4:

[0139] See also Figure 15 and Figure 16 , Figure 15 This is a schematic diagram of the connection request interaction process in the Peer-Peer SDNController architecture provided by another embodiment of the present application. Figure 16 This is a schematic diagram of the connection request interaction process in the Peer-Peer SDN Controller architecture provided by another embodiment of the present application, wherein Figure 15 and Figure 16 In the ClientContext, NCC components, DS components, CC components, RC components and LRM components are included.

[0140] exist Figure 15 and Figure 16In the example, there is a peer-peer relationship between n+1Controller and nController. nController communicates with n+1Controller's ServerContext through ClientContext, that is, n+1Controller can initiate connection establishment to nController through ServerContext; n+1Controller communicates with nController's ServerContext through ClientContext, that is, nController can initiate connection establishment to n+1Controller through ServerContext.

[0141] Figure 15 and Figure 16 The specific steps of the connection request interaction process shown are as follows:

[0142] When the n Controller initiates a connection establishment with the n+1 Controller, the n Controller acts as the client-layer Controller, and the n+1 Controller acts as the server-layer Controller. The connection establishment process is the same as that in Example 2. In this case, the n Controller in this example plays the same role as the n+1 Controller in Example 2. The n+1 Controller in this example plays the same role as the n Controller in Example 2. Since the connection establishment process in Example 2 has been described in detail, it will not be repeated here to avoid redundancy.

[0143] When the n+1Controller initiates a connection establishment with the nController, the n+1Controller acts as the client-layer Controller, and the nController acts as the service-layer Controller. The connection establishment process is the same as that in Example 2. In this case, the nController in this example plays the same role as that in Example 2, and the n+1Controller in this example plays the same role as that in Example 2. Since the connection establishment process in Example 2 has been described in detail, it will not be repeated here to avoid redundancy.

[0144] It should be noted that when n Controller initiates a connection establishment to n+1Controller, n+1Controller should discard the ServerContext resource corresponding to the ClientContext of n Controller during connection calculation to avoid resource nesting loops, and vice versa.

[0145] In addition, if Figure 17 As shown, an embodiment of the present application also discloses a communication device, including: at least one processor 210; at least one memory 220, for storing at least one program; when the at least one program is executed by the at least one processor 210, a connection establishment method as in any of the previous embodiments is implemented.

[0146] In addition, an embodiment of the present application further discloses a computer-readable storage medium, in which computer-executable instructions are stored. The computer-executable instructions are used to execute the connection establishment method in any of the above embodiments.

[0147] In addition, an embodiment of the present application also discloses a computer program product, including a computer program or computer instructions, which are stored in a computer-readable storage medium. The processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium, and the processor executes the computer program or computer instructions, so that the computer device executes the connection establishment method as in any of the previous embodiments.

[0148] The system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of the system architecture and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

[0149] Those skilled in the art will appreciate that all or some of the steps in the methods, systems, and functional modules / units in the devices disclosed above may be implemented as software, firmware, hardware, or appropriate combinations thereof.

[0150] In a hardware implementation, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0151] As used in this specification, the terms "component," "module," "system," and the like are used to refer to computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, or a computer. By way of illustration, both applications running on a computing device and a computing device can be components. One or more components can reside in a process or execution thread, and a component can be located on one computer or distributed between two or more computers. In addition, these components can be executed from various computer-readable media having various data structures stored thereon. Components can communicate, for example, through local or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component on a local system, a distributed system, or a network, such as the Internet interacting with other systems via signals).

Claims

1. A connection establishment method, applied to a controller, wherein the controller is configured to have a client context and a management context, wherein the client context and the management context are configured to share a network call controller component; The connection establishment method includes: Receiving, through the network call controller component, a connection establishment request sent by a request initiator, wherein the connection establishment request carries at least a first resource identifier and a last resource identifier; sending, by the network call controller component, a connection request to the management context according to the connection establishment request; Performing connection configuration according to the connection request through the management context to obtain connection resource information corresponding to the first resource identifier and the last resource identifier; receiving, by the network call controller component, the connection resource information from the management context; The connection resource information is sent to the request initiator through the network call controller component to complete the connection establishment.

2. The method according to claim 1, wherein: The receiving, by the network call controller component, a connection establishment request sent by a request initiator, includes: receiving, by the network call controller component shared by the client context, a connection establishment request sent by a requesting party; The sending, by the network call controller component, a connection request to the management context according to the connection establishment request, comprises: sending, by the network call controller component shared by the client context, a connection request to the network call controller component shared by the management context according to the connection establishment request; The step of performing connection configuration according to the connection request through the management context to obtain connection resource information corresponding to the first resource identifier and the last resource identifier includes: performing connection configuration according to the connection request by the network call controller component shared by the management context, and obtaining connection resource information corresponding to the first resource identifier and the last resource identifier; The receiving, by the network call controller component, the connection resource information from the management context comprises: receiving, by the network call controller component common to the client context, the connection resource information from the network call controller component common to the management context; The step of sending the connection resource information to the requesting party through the network call controller component to complete the connection establishment includes: The connection resource information is sent to the requesting party through the network call controller component shared by the client context to complete the connection establishment.

3. The method according to claim 1 or 2, characterized in that: The first resource identifier includes a first boundary resource identifier; the last resource identifier includes a last boundary resource identifier.

4. The method according to claim 2, characterized in that The client context is further configured to have a directory service component, and the directory service component is used to convert resource identification.

5. The method according to claim 4, characterized in that: The directory service component is further configured in the management context, and the management context and the customer context share the directory service component; Alternatively, the management context is configured to have a directory service component that is different from the directory service component of the client context.

6. The method according to claim 4, characterized in that The sending of a connection request to the network call controller component shared by the management context according to the connection establishment request by the network call controller component shared by the client context comprises: Sending the first resource identifier and the last resource identifier to the directory service component for resource identifier conversion according to the connection establishment request through the network call controller component shared by the client context, and obtaining the first sub-network resource identifier and the last sub-network resource identifier returned by the directory service component; Generate a connection request according to the first sub-network resource identifier and the last sub-network resource identifier by the network call controller component shared by the customer context; The connection request is sent to the network call controller component shared by the management context through the network call controller component shared by the client context.

7. The method according to claim 2, characterized in that The client context is further configured to have a connection controller component, a routing controller component, and a link resource manager component. The connection controller component is used to request the routing controller component to query a connection route and request the link resource manager component to select a connection link. The routing controller component is used to calculate a connection route, and the link resource manager component is used to select a connection link from the links that the route passes through.

8. The method according to claim 7, characterized in that The sending of a connection request to the network call controller component shared by the management context according to the connection establishment request by the network call controller component shared by the client context comprises: Obtaining, by the network call controller component shared by the customer contexts, a first sub-network point resource identifier and a last sub-network point resource identifier of the customer context according to the first resource identifier and the last resource identifier in the connection establishment request, wherein the first sub-network point resource identifier of the customer context corresponds to the first resource identifier, and the last sub-network point resource identifier of the customer context corresponds to the last resource identifier; Using the network call controller component shared by the customer context, the first sub-network resource identifier and the last sub-network resource identifier of the customer context are sent to the routing controller component through the connection controller component; Requesting, through the routing controller component, the link resource manager component to obtain the first routing topology and first local connection state information corresponding to the first sub-network resource identifier and the last sub-network resource identifier of the customer context; Calculating a routing path based on the first routing topology and the first local connection state information by the routing controller component to obtain first target routing information, wherein the first target routing information includes a first sub-network resource identifier and a last sub-network resource identifier of the customer context; utilizing the network call controller component common to the client context to receive the first target routing information from the routing controller component via the connection controller component; generating, by the network call controller component common to the client context, a connection request according to the first target routing information; The connection request is sent to the network call controller component shared by the management context through the network call controller component shared by the client context.

9. The method according to claim 7, characterized in that The client context is further configured with a directory services component; The sending of a connection request to the network call controller component shared by the management context according to the connection establishment request by the network call controller component shared by the client context comprises: Obtaining, by the network call controller component shared by the customer contexts, a first sub-network point resource identifier and a last sub-network point resource identifier of the customer context according to the first resource identifier and the last resource identifier in the connection establishment request, wherein the first sub-network point resource identifier of the customer context corresponds to the first resource identifier, and the last sub-network point resource identifier of the customer context corresponds to the last resource identifier; Using the network call controller component shared by the customer context, the first sub-network resource identifier and the last sub-network resource identifier of the customer context are sent to the routing controller component through the connection controller component; Requesting, through the routing controller component, the link resource manager component to obtain the second routing topology and the second local connection state information corresponding to the first sub-network resource identifier and the last sub-network resource identifier of the customer context; Calculating a routing path based on the second routing topology and the second local connection state information by the routing controller component to obtain second target routing information, wherein the second target routing information includes a first sub-network resource identifier and a last sub-network resource identifier of the customer context; receiving, by the network call controller component common to the client context, the second target routing information from the routing controller component via the connection controller component; sending the second target routing information to the directory service component through the network call controller component shared by the customer contexts to perform resource identifier conversion on the first sub-network resource identifier and the last sub-network resource identifier of the customer context, and obtaining third target routing information returned by the directory service component that includes the first sub-network resource identifier and the last sub-network resource identifier of the management context; generating, by the network call controller component common to the client context, a connection request based on the third target routing information; The connection request is sent to the network call controller component shared by the management context through the network call controller component shared by the client context.

10. The method according to claim 2, characterized in that The client context is further configured to have a directory service component; the connection resource information includes a first sub-network resource identifier and a last sub-network resource identifier of the management context; The receiving, by the network call controller component shared by the client context, the connection resource information from the network call controller component shared by the management context, comprises: Receiving, by the network call controller component shared by the client context, the connection resource information including the first sub-network point resource identifier and the last sub-network point resource identifier of the management context from the network call controller component shared by the management context; Sending the connection resource information to the directory service component through the network call controller component shared by the customer context to perform resource identifier conversion on the first sub-network resource identifier and the last sub-network resource identifier of the management context, thereby obtaining connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the customer context; The connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the client context is received from the directory service component through the network call controller component shared by the client context.

11. The method according to claim 10, characterized in that The client context is further configured to have a connection controller component; the network call controller component shared by the client context sends the connection resource information to the requesting party, including: Sending the connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the customer context to the connection controller component for information confirmation via the network call controller component shared by the customer context; When the connection controller component successfully confirms the connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the customer context, the connection controller component is used to send the connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the customer context to the request initiator through the network call controller component shared by the customer context.

12. The method according to claim 2, characterized in that The client context is further configured to have a connection controller component; the connection resource information includes a first sub-network resource identifier and a last sub-network resource identifier of the management context; The network call controller component shared by the client context sends the connection resource information to the requesting party, comprising: Sending the connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the management context to the connection controller component for information confirmation via the network call controller component shared by the customer context; When the connection controller component successfully confirms the connection resource information, the network call controller component shared by the customer context obtains the first sub-network resource identifier and the last sub-network resource identifier of the customer context based on the first sub-network resource identifier and the last sub-network resource identifier of the management context; The connection resource information including the first sub-network resource identifier and the last sub-network resource identifier of the customer context is sent to the request initiator through the network call controller component shared by the customer context.

13. The method according to claim 1 or 2, characterized in that The controller and the request initiator are peer controllers.

14. The method according to claim 13, characterized in that The controller is further configured to have a service context, and the connection establishment method further includes: When connection resource information meeting the connection requirement of the requesting party is not obtained locally, a request for obtaining connection resource information is sent to a network call controller component shared by a client context of a next peer controller via the service context.

15. A connection establishment method, applied to a controller, the controller being configured to have a customer context and a management context, the customer context and the management context both being configured to have a network call controller component, the network call controller component corresponding to the management context being different from the network call controller component corresponding to the customer context; The connection establishment method includes: Receiving, through the network call controller component corresponding to the client context, a connection establishment request sent by a request initiator, wherein the connection establishment request carries at least a first resource identifier and a last resource identifier; sending, by the network call controller component corresponding to the client context, a connection request to the network call controller component corresponding to the management context according to the connection establishment request; Performing connection configuration according to the connection request through the network call controller component corresponding to the management context to obtain connection resource information corresponding to the first resource identifier and the last resource identifier; receiving, by the network call controller component corresponding to the client context, the connection resource information from the network call controller component corresponding to the management context; The connection resource information is sent to the request initiator through the network call controller component corresponding to the client context to complete the connection establishment.

16. The method according to claim 15, characterized in that The client context is further configured to have a directory service component, and the directory service component is used to convert resource identification.

17. The method according to claim 15, characterized in that The client context is further configured to have a connection controller component, a routing controller component, and a link resource manager component. The connection controller component is used to request the routing controller component to query a connection route and request the link resource manager component to select a connection link. The routing controller component is used to calculate a connection route, and the link resource manager component is used to select a connection link from the links that the route passes through.

18. A communication device, characterized in that: include: at least one processor; at least one memory for storing at least one program; When at least one of the programs is executed by at least one of the processors, the connection establishment method according to any one of claims 1 to 17 is executed.

19. A computer-readable storage medium, characterized in that A processor-executable program is stored therein, and when the processor-executable program is run by the processor, the connection establishment method according to any one of claims 1 to 17 is executed.

20. A computer program product comprising a computer program or computer instructions, characterized in that The computer program or the computer instruction is stored in a computer-readable storage medium, the processor of the communication device reads the computer program or the computer instruction from the computer-readable storage medium, and the processor executes the computer program or the computer instruction, so that the communication device performs the connection establishment method according to any one of claims 1 to 17.

Images