TWI646809B - Sharing method of network resource and network coordination apparatus - Google Patents

Abstract

A method for sharing a network resource includes the following steps: receiving a resource sharing request from a tenant; and requesting, by the resource sharing request, the controller to determine whether the resource of the shared transmission network satisfies a resource sharing request, where the controller is configured to manage the shared transmission a plurality of forwarding devices in the transport network; in response to the controller determining that the resources of the shared transport network satisfy the resource sharing request, generating a tenant identification code for the tenant; and transmitting the tenant identification code to the tenant for the tenant to identify according to the tenant The code returns one or more group identification codes, and a corresponding transmission service type of each group identification code; the controller is required to generate one or more packet headers for the transmission service type corresponding to each group identification code ( Packet header), and requires the controller to update the forwarding table of the forwarding device.

Description

Network resource sharing method and network coordination device

The disclosure relates to a method for sharing network resources and a network coordination device.

To provide convenient cellular network services, network operators often need to use rigid and expensive devices, complex control-plane protocols, and traditional vendor-specific configuration interfaces. )Wait.

Different network operators can build their own core networks for user devices to access the Internet through the core network built by their network operators. However, based on the consideration of independent operation and management of different network operators, the core networks built by different network operators cannot be fully shared by different network operators.

The disclosure relates to a method for sharing network resources and a network coordinating device, which can dynamically allocate resources on a shared transmission network to different tenants according to the needs of different tenants and the state of the shared transmission network. Independently and flexibly share the resources of the transport network and simplify The complexity of tenant settings for network sharing.

According to a first aspect of the present invention, a method for sharing a network resource includes: receiving a resource sharing request from a tenant; and requesting, by the resource sharing request, the controller to determine whether the resource of the shared transmission network satisfies a resource sharing request, where the controller uses To manage a plurality of forwarding devices in the shared transmission network; in response to the controller determining that the resources of the shared transmission network satisfy the resource sharing request, generating a tenant identification code for the tenant; and transmitting the tenant identification code to the tenant for the tenant to identify according to the tenant The code returns one or more group identification codes, and a corresponding transmission service type of each group identification code; the controller is required to generate one or more packet headers for the transmission service type corresponding to each group identification code ( Packet header), and requires the controller to update the forwarding table of the forwarding device.

According to a first aspect of the present invention, a network coordination apparatus is provided. The network coordination device includes an interface circuit and a processing circuit. The processing circuit is coupled to the interface circuit and configured to: receive a resource sharing request from the tenant; and, according to the resource sharing request, request the controller to determine whether the resource of the shared transmission network satisfies the resource sharing request, where the controller is configured to manage the shared transmission network. a plurality of forwarding devices in the path; in response to the controller determining that the resources of the shared transmission network satisfy the resource sharing request, generating a tenant identification code for the tenant; and transmitting the tenant identification code to the tenant, for the tenant to return the tenant according to the tenant identification code a plurality of group identification codes, and a transmission service type corresponding to each group identification code; the controller is required to generate one or more packet headers for the transmission service type corresponding to each group identification code, and request the controller according to To update the forwarding flow table of the forwarding device.

In order to better understand the above and other aspects of the present invention, the preferred embodiments are described below, and in conjunction with the drawings, the detailed description is as follows:

10‧‧‧Network System

102a, 102b‧‧‧ User devices

104‧‧‧Wireless access network

106, 306‧‧‧ shared transmission network

108a, 108b, 304a, 304b‧‧‧ tenants

110a, 110b‧‧‧ core network

112‧‧‧Internet

114, 308‧‧‧ controller

116‧‧‧Network sharing module

1042‧‧‧ Base station facilities

1062, 3062‧‧‧Transfer device

S202, S204, S206, S208, S208a, S210, S212, S214, S216, S218‧‧ steps

302‧‧‧Network sharing module

M1, M2‧‧‧ mapping table

X1, X2‧‧‧ Tenant ID

G1~GN, G1’~GN’‧‧‧ Group ID

P1~PN, P1’~PN’‧‧‧ Service Type

FT‧‧‧Transfer flow table

FIG. 1 is a schematic diagram of a network system according to an embodiment of the present disclosure.

FIG. 2 is a system flowchart of a method for sharing network resources according to an embodiment of the present disclosure.

FIG. 3 is a schematic diagram of the network sharing module coordinating the controller to control the transfer device according to the request made by the tenant in the network system according to an embodiment of the disclosure.

FIG. 1 is a schematic diagram of a network system 10 in accordance with an embodiment of the present disclosure. In the network system 10 shown in FIG. 1, the user devices 102a and 102b are connected to a shared transport network 106 via a radio access network 104 in the area, and then transmitted through the shared transmission. The network 106 is connected to the core networks 110a and 110b of the corresponding tenants 108a, 108b for accessing the Internet 112.

For convenience of description, only two user devices 102a, 102b, two tenants 108a, 108b, and two core networks 110a, 110b are illustrated in FIG. However, this disclosure is not limited to this. In other embodiments, the network system can include one or more user devices, one or more tenants, and one or more core networks.

Tenants 108a, 108b are, for example, physical network operators, virtual networks Operator, or service provider. In this example, core networks 110a and 110b are built or leased by tenants 108a and 108b, respectively. User devices 102a and 102b are users of tenants 108a and 108b, respectively.

The wireless access network 104, for example, includes one or more base station facilities 1042 to provide radio access services for the user devices 102a and 102b. In this embodiment, it is assumed that the base station facility 1042 can share user devices (e.g., user devices 102a and 102b) of different tenants.

The shared transport network 106 includes one or more forwarding devices 1062 that are signaled to each other. The forwarding device 1062 can be a switch, a router, or any network node that can receive packets and transmit packets according to specific rules.

Each forwarding device 1062 has, for example, a flow table, which may include one or more flow entries to describe a packet delivery rule, an action, and a statistics (statistics). ) and other information. The packet delivery rule exists, for example, in the form of a packet header in the flow entry.

The forwarding device 1062 can refer to the forwarding flow table to determine how to process the received packet. For example, when a forwarding device 1062 receives a packet, the forwarding device 1062 will parse the packet information and compare the rules described by the parsed information with the flow entry to forward the packet to a particular network node.

In this embodiment, the different tenants 108a, 108b can share the transmission resources of the shared transmission network 106 through the coordinated operation of the controller 114 and the network sharing module 116. Therefore, the data packet of the user device 102a can be shared. The transport network 106 is delivered to the core network 110a of the corresponding tenant 108a, and the data packet of the user device 102b can be sent to the core network 110b of the corresponding tenant 108b via the shared transport network 106.

The controller 114 can centrally manage the forwarding device 1062 in the shared transport network 106. For example, the controller 114 can add, modify, delete packet delivery rules and update its forwarding flow table for each forwarding device 1062.

The network sharing module 116 signal is connected between the tenants 108a, 108b and the controller 114. In an embodiment, the tenants 108a, 108b can communicate with the network sharing module 116 through a Representational State Transfer (REST) application interface, and the network sharing module 116 and the controller 114 can also use the REST application. Interface to communicate.

The network sharing module 116 can receive requests from the tenants 108a, 108b regarding the use of the shared transport network 106. In response to the requests of the tenants 108a, 108b, the network sharing module 116 can coordinate the controller 114 to load, update or delete specific packet delivery rules for the forwarding device 1062 to enable the tenants 108a, 108b to load on the shared transport network 106. Within the scope, the network resources of the shared transport network 106 are planned and used according to their respective needs.

Controller 114 and network sharing module 116 can be implemented, for example, in software, hardware, or a combination thereof. In an embodiment, the controller 114 is, for example, a Software-Defined Network (SDN) controller. The network sharing module 116 is, for example, a network sharing application module on the upper layer of the controller 114.

The controller 114 and the network sharing module 116 can be implemented together in the same On an arithmetic device (such as a computer), or on a different computing device. The computing device for implementing the function of the network sharing module 116 is defined as a network coordination device. The network coordination device can include an interface circuit and an arithmetic processing circuit coupled to the interface circuit. The interface circuit is, for example, an input/output (I/O) circuit for transmitting and receiving signals. The processing circuit is, for example, a microprocessor circuit, a microcontroller, a digital signal processing circuit (DSP) circuit, a programmable logic device (PLD), a state machine, an independent hardware circuit, or any other suitable control. Logic to implement the functionality of the network sharing module 116 described herein. More generally, the procedures and logic flows described herein can be performed by a programmable processor executing one or more computer programs to implement the functions described herein.

FIG. 2 is a system flowchart of a method for sharing network resources according to an embodiment of the present disclosure.

In step S202, the tenant (e.g., tenant 108a or 108b) transmits a resource sharing request to the network sharing module (e.g., network sharing module 116). The tenant is, for example, a physical network operator, a virtual network operator, or a service provider that wants to use resources of a shared transmission network.

In an embodiment, the network sharing module can provide a template for the tenant to input the resource sharing request. The resource sharing request includes, for example, a transmission bandwidth requirement value required by the tenant, or other quality of service (QoS) parameters. The described requirements template can be implemented, for example, through a REST application interface.

In step S204, the network sharing module is based on the received resource sharing. The request requires the controller (such as the controller 114) to determine whether the resources of the shared transport network (e.g., the shared transport network 106) satisfy the resource sharing request.

In step S206, the controller determines whether the resource of the shared transmission network satisfies the resource sharing request.

For example, the controller determines whether the remaining available transmission bandwidth in the shared transmission network can support the transmission bandwidth requirement value proposed by the tenant to determine whether the resources of the shared transmission network satisfy the resource sharing request.

In step S208, the controller returns the determination result to the network sharing module.

If the judgment result shows that the resources of the shared transmission network cannot satisfy the resource sharing request, for example, the remaining available bandwidth in the shared transmission network is not enough to support the bandwidth requirement described in the resource sharing request, the network sharing module will respond As a result of the judgment, the tenant is notified that the shared transmission network is currently unable to provide resource sharing, and the entire sharing process is terminated, as shown in step S208a.

On the other hand, when the judgment result indicates that the resource of the shared transmission network satisfies the resource sharing request, in step S210, the network sharing module will respond to the determination result, generate a tenant ID (tenant ID) to the tenant, and store the tenant. Related information. Information about the tenant is, for example, information such as the available bandwidth of the tenant and the available virtual network topology.

In step S212, the network sharing module returns the tenant identification code to the tenant.

In step S214, the tenant shares the network with the tenant identification code. The module returns one or more group identification codes, and a type of transmission service corresponding to each group identification code, for example, the type of service to be used.

For example, the tenant may propose a request for multiple transport service types to the network sharing module based on the obtained tenant identification code, and respectively define a corresponding group ID for each transport service type. These group identifiers and their corresponding transport service types will be transmitted back to the network sharing module.

In an embodiment, the tenant can fill in a required service type and a corresponding group identification code in a demand template provided by the network sharing module through the REST application interface.

In step S216, the network sharing module requests the controller to generate one or more packet headers for the transmission service type corresponding to each group identification code, so as to update the forwarding flow table of the forwarding device accordingly.

The packet header is, for example, the part of the first-class entry that describes the packet delivery rule. In other words, the network sharing module will require the controller to load a specific one or more packet delivery rules for the forwarding device in the shared transport network to transmit packets corresponding to a particular service type.

In step S218, the controller responds to the request of the network sharing module, and adds, modifies or deletes the flow entry of the forwarding flow table in the forwarding device according to the generated packet header to implement the tenant requirement in the shared transmission network. Packet delivery rules for transport service types.

In an embodiment, it is assumed that the group identifier returned by the tenant includes a first group identifier and a second group identifier, and the first group identifier pair The first transmission service type required by the tenant, the second group identification code corresponding to the second transmission service type required by the tenant (the first transmission service type and the second transmission service type are, for example, different service types), the network The road sharing module may require the controller to generate one or more first packet headers for the first transmission service type, so that the controller updates the forwarding flow table of the forwarding device according to the one or more first packet headers; The module may also require the controller to generate one or more second packet headers for the second transmission service type, such that the controller updates the forwarding flow table in the forwarding device based on the one or more second packet headers.

In addition, the network sharing module can establish a corresponding mapping table for each tenant. The network sharing module can map the first group identifier to one or more first packet headers provided by the controller, and map the second group identifier to the mapping table through the mapping table. One or more second packet headers provided by the controller. Details of the mapping table will be further explained in FIG. 3 and Tables 1 to 4.

According to the embodiment of the disclosure, the network sharing module can sense and manage the resource sharing status of each tenant to the shared transmission network. For tenants who are allowed to use the transmission resources of the shared transmission network, the network sharing module can respectively assign the tenants a specific tenant identification code. Thereafter, the tenants can propose the type of transmission service to be used to the network sharing module based on the tenant identification code held by each of them. Each type of transmission service to be used corresponds to a group identification code. The network sharing module can record the mapping relationship between each group identification code and the corresponding transmission service type, and provide the corresponding available packet header to the controller for each transmission service type, and correct the conversion according to the A transfer flow table in the delivery device.

In the above manner, the tenant's request can be automatically mapped to the flow entry of the transfer device via the cooperative operation of the network sharing module and the controller. For tenants who want to use the shared transmission network resources, they only need to fill in the requirements provided by the network sharing module to implement the required transmission services in the shared transmission network, without having to By setting each forwarding device in the shared transmission network, the complexity of the tenant's network sharing setting can be greatly simplified. In addition, after obtaining the tenant identification code, the tenant can use it to dynamically update and revise the previously requested transmission service type. Different tenants maintain the independence and flexibility of resource management for the shared transmission network.

For convenience of explanation, in the network system according to an embodiment of the present disclosure, if there are two tenants requesting to use the shared transmission network resource, how does the network sharing module coordinate the controller pair sharing? The transfer device in the transport network is managed.

Referring to FIG. 3, a schematic diagram of a network sharing module coordinating a controller to control a forwarding device according to a request from a tenant in a network system according to an embodiment of the disclosure is shown.

In this example, it is assumed that the network sharing module 302 provides the tenant 304a and the tenant 304b to use the network resources in the shared transport network 306. A plurality of forwarding devices 3062 are included in the shared transmission network 306. Such transfer devices 3062 are centrally managed by controller 308. The transfer device 3062 is, for example, an SDN switch. Controller 308 is, for example, an SDN controller.

The network sharing module 302 can establish a corresponding mapping table for each tenant (such as the tenants 304a and 304b), the mapping table includes the tenant's tenant identification code, one or more group identification codes, and each group identification code. The corresponding transport service type. The mapping table may further include a corresponding one or more packet headers generated by the network sharing module 302 to the controller 308.

As shown in FIG. 3, the network sharing module 302 stores mapping tables M1 and M2 corresponding to the respective tenants 304a and 304b. The mapping tables M1 and M2 mainly include three fields: a tenant identification code, a group identification code, and a service type.

In the mapping table M1, the tenant identification code X1 is a specific name or number assigned by the network sharing module 302 to the tenant 304a. The tenant 304a can propose a transmission service type requirement to the network sharing module 302 based on the tenant identification code X1, and define a corresponding group identification code for each transmission service type. In another embodiment, the mapping table M1 may further include requesting the controller 308 to generate corresponding packet header information.

For example, after obtaining the tenant identification code X1 provided by the network sharing module 302, the tenant 304a fills in the service type to be used by using the requirement template provided by the network sharing module 302, and each service type corresponds to one. Group ID. As shown in the figure, the group identification codes G1 to GN correspond to service types P1 to PN, respectively, where N is a positive integer.

Similarly, in the mapping table M2, the tenant identification code X2 is a specific name or number assigned by the network sharing module 302 to the tenant 304b. The tenant 304b can submit a transmission service request to the network sharing module 302 based on the tenant identification code X2. begging.

For example, after obtaining the tenant identification code X2 provided by the network sharing module 302, the tenant 304b can use the input template provided by the network sharing module 302 to fill in the service type to be used, and each service type will correspond to A group identification code. As shown, the group identification codes G1'~GN' correspond to service types P1'~PN', respectively, where N' is a positive integer.

Since the mapping tables M1 and M2 are stored in the network sharing module 302, only the network sharing module 302 knows between the group identification codes and the corresponding service types compared to the controller 308 and the forwarding device 3062. Mapping relationship. Thereafter, the tenant (eg, tenant 304a) may modify or prune the particular transmission by describing its own tenant identification code (eg, tenant identification code X1) and a specific group identification code (eg, group identification code G1) in the instruction. Service type (such as service type P1).

The network sharing module 302 can request the controller 308 to provide a corresponding packet header for different service types P1~PN, P1'~PN' according to the mapping tables M1 and M2. The packet header describes the packet delivery rules for the flow entries in the forwarding device 3062.

In response to the request of the network sharing module 302, the controller 308 will add, delete or modify the flow entries in the forwarding device 3062 to the forwarding flow table FT, so that the forwarding device 3062 can process according to the packet forwarding rules that meet the requirements of the tenants 304a, 304b. And forward the packet.

Incidentally, since the network sharing module 302 gives the corresponding tenant identification code according to different tenants, the tenant 304a and the tenant 304b The mapping relationship between the corresponding group identifier and the service type may be independent of each other.

The following uses Tables 1 to 4 to more specifically describe the information that may be stored in the mapping table. For convenience of explanation, the mapping table M1 corresponding to the tenant 302a will be described here. It should be noted that, in actual application, the content and format of the mapping table need not be limited.

In the example of Table 1, after acquiring the tenant identification code "X1", the tenant 302a requests the network sharing module 302 for the type of transmission service, including two service types: the service type of the control plane. And the type of service of the user plane. These two service types correspond to the group identification codes "G1" and "G2" respectively.

The network sharing module 302 can record the mapping relationship between the tenant identification code "X1" and the group identification codes "G1" and "G2" for the tenant 302a, and record the group identification codes "G1", "G2" and corresponding The mapping between service types. The recorded mapping relationship can be presented, for example, in a mapping table or other suitable data structure.

The controller 308 can respond to the request of the network sharing module 302, and provides one or more first packet headers for the service type corresponding to the group identification code "G1", and corresponds to the group identification code "G2". The service type provides one or more second packet headers. In an embodiment, the network sharing module 302 can further record the mapping relationship between the group identification code "G1" and the first packet header in the mapping table M1, and record the group identification code "G2" and the first The mapping relationship between the two packet headers is to map the group identification code "G1" to the first packet header provided by the controller 308 through the mapping table M1, and map the group identification code "G2" to the control. Provided by device 308 The second packet header.

In the network system of Long Term Evolution (LTE), different priorities can be further given to packets that are also in the control plane. For example, for the service type of the control plane, the priority of a service type that is attached to the attachment may be higher than the priority of the service type of the tracking area update. Alternatively, for the service type of the user plane, the priority of the service type of the Internet Protocol Call Technology (VoIP) may be higher than the priority of the web-browsing service type. To this end, the tenant 302a can also determine different group identification codes for each service plane of the control plane and the user plane. After establishing the mapping relationship between the tenant identification code---group identification code--packet type, the network sharing module 302 will request the controller 308 to update one or more forwarding devices 3062 in the shared transmission network 306. The transfer flow table FT causes the transfer device 3062 to transfer the packets of the control plane and the data plane based on the prioritization when packet transfer is performed according to the transfer flow table FT. Tables 2 to 4 are examples of service types for each control plane and user plane, and different group identification codes are determined.

Please refer to Table 2, which is an illustration of another example of a mapping table. in In the example of Table 2, after obtaining the tenant identification code "X1", the tenant 302a requests the network sharing module 302 to transmit a service type, including four service types: the service type of the control plane, and the control plane. Service Type 2, Service Type 1 of the user plane, and Service Type 2 of the user plane. These four service types are mapped to the group identification codes "G1", "G2", "G3", and "G4", respectively.

In actual application, the tenant 302a may also define more levels of priority for the service planes of the control plane and the user plane, and map them to different group identifiers.

See Table 3 for an example of Table 2 to further define an application for the type of service. It is assumed here that the service type 1 of the control plane is the login service type; the service type 2 of the control plane is the handover service type; and the service type 1 of the user plane is the Internet Protocol Call Technology (VoIP) service type. The service type 2 of the user plane is a video service type.

table 3

See Table 4, which further defines another application of the service type for the example of Table 2. It is assumed here that the service type 1 of the control plane is a Mobility Management Entity (MME) service type; the service type 2 of the control plane is a Serving Gateway (S-GW) service type; and the service type of the user plane 1 is a type of Internet Protocol Call (VoIP) service; a service type 2 of the user plane is a video service type.

According to the descriptions in Tables 1 to 4, each tenant can propose different transmission service type requirements to the network sharing module according to their own needs or plans. Each transmission service type corresponds to a group identification code. Network sharing module for each rent The user establishes a corresponding mapping table to record the mapping relationship between the group identifier and the corresponding service type for the individual tenant.

After the mapping table is established, the network sharing module may further provide one or more applicable packet headers for each service type, so that the controller updates the forwarding flow table in the forwarding device accordingly, thereby sharing A packet delivery rule that implements the tenant transmission requirements in the transport network. In some embodiments, the network sharing module can further record the mapping relationship between each packet header and the group identifier in the mapping table.

In summary, the method for sharing network resources and the network coordination device for implementing the method can dynamically allocate resources on a shared transmission network according to the needs of each tenant and the state of the shared transmission network. In this way, different tenants can independently and flexibly share the resources of the transmission network and simplify the complexity of the tenant's setting for network sharing.

The description includes many specifics, and should not be construed as limiting the scope of the claimed embodiments. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can be implemented in the various embodiments or in any suitable subcombination. Moreover, while the above features are described as working in some combination even initially stated as such, one or more of the required combinations may be removed from the combination in some cases, and the required combination may involve A variation of a combination or sub-combination. Similarly, although operations are depicted in a particular order in the figures, this should not be understood as in order to obtain the desired results. Instead, such operations are required to be performed in the particular order or sequence of the order shown, or all illustrated operations are performed.

Only some illustrations and implementations have been disclosed. Variations, modifications, and enhancements of the described examples and implementations, as well as other implementations, can be made based on the disclosure.

Claims (18)

A method for sharing a network resource includes: receiving a resource sharing request from a tenant; and requesting, by the resource sharing request, a controller to determine whether a resource of a shared transport network satisfies the resource sharing request The controller is configured to manage a plurality of forwarding devices in the shared transmission network; and in response to the controller determining that the resource of the shared transmission network satisfies the resource sharing request, generating a tenant identification code for the tenant; The identifier is sent back to the tenant, and the tenant returns one or more group identification codes according to the tenant identification code, and a transmission service type corresponding to each of the group identification codes; the controller is required to The transport service type corresponding to the group identifier generates one or more packet headers, and the controller is required to update the transfer table of the transfer devices to receive from another tenant. Another resource sharing request; providing the another resource sharing request to the controller for the controller to confirm whether the resource of the shared transmission network is full The another resource sharing request; in response to the controller confirming that the resource of the shared transmission network satisfies the another resource sharing request, generating another tenant identification code for the another tenant; and transmitting the another tenant identification code To the other tenant, the another tenant returns another one or more group identification codes according to the another tenant identification code, each of the other group identification codes respectively corresponding to another transmission required by another tenant Service type; The controller is required to generate another one or more packet headers for the another transmission service type corresponding to each of the other group identifiers, and request the controller to update the forwarding flow table of the forwarding devices accordingly. The sharing method of claim 1, wherein the one or more group identification codes comprise a first group identification code and a second group identification code, the first group identification code corresponding to the tenant The first transmission service type required, the second group identification code corresponds to a second transmission service type required by the tenant, and the sharing method further includes: requesting the controller to generate one or one for the first transmission service type a plurality of first packet headers, causing the controller to update the forwarding flow tables of the forwarding devices according to the one or more first packet headers; and requesting the controller to generate one or one for the second transmission service type And a plurality of second packet headers, so that the controller updates the forwarding flow tables of the forwarding devices according to the one or more second packet headers. The sharing method of claim 2, further comprising: mapping the first group identification code to the one or more first packet headers through a mapping table; and transmitting the mapping table by using the mapping table The second group identification code is mapped to the one or more second packet headers. The sharing method of claim 2, wherein the first transmission service type and the second transmission service type are different packet types. The sharing method of claim 1, further comprising: establishing a mapping table for the tenant, the mapping table including the tenant identification code of the tenant, the one or more group identification codes, and each group The type of transmission service corresponding to each of the group identification codes. For example, the sharing method described in claim 1 further includes: providing a template for the tenant to input the resource sharing request; wherein the resource sharing request includes a transmission bandwidth requirement value. The sharing method described in claim 5, wherein the requirement template is implemented by a Representational State Transfer (REST) application interface. The sharing method of claim 1, further comprising: establishing a mapping table for the tenant, the mapping table including the tenant identification code of the tenant, the one or more group identification codes, and each group a transmission service type corresponding to each of the group identification codes; and another mapping table for the another tenant, the another mapping table including the another tenant identification code of the another tenant, the another one or more group identifications a code, and the another type of transmission service corresponding to each of the other group identification codes. The sharing method of claim 1, wherein the tenant is a physical network operator, a virtual network operator, or a service provider. A network coordination device includes: An interface circuit, and a processing circuit coupled to the interface circuit and configured to: receive a resource sharing request from a tenant; and request a controller to determine a shared transmission network according to the resource sharing request Whether the resource satisfies the resource sharing request, wherein the controller is configured to manage a plurality of forwarding devices in the shared transmission network; and in response to the controller determining that the resource of the shared transmission network satisfies the resource sharing request, generating, for the tenant a tenant identification code; the tenant identification code is transmitted back to the tenant, and the tenant returns one or more group identification codes according to the tenant identification code, and a transmission service type corresponding to each of the group identification codes Requiring the controller to generate one or more packet headers for the transmission service type corresponding to each group identifier, and requesting the controller to update the forwarding flow table of the forwarding devices accordingly (flow Receiving another resource sharing request from another tenant; providing another resource sharing request to the controller for the controller to confirm the sharing Whether the resource of the network satisfies the another resource sharing request; in response to the controller confirming that the resource of the shared transmission network satisfies the another resource sharing request, generating another tenant identification code for the another tenant; Returning a tenant identification code to the other tenant for the other tenant to return another one or more group identification codes according to the another tenant identification code, each of the other group identification codes respectively corresponding to another tenant Another type of transport service required; The controller is required to generate another one or more packet headers for the another transmission service type corresponding to each of the other group identifiers, and request the controller to update the forwarding flow table of the forwarding devices accordingly. The network coordinating device of claim 10, wherein the one or more group identification codes comprise a first group identification code and a second group identification code, the first group identification code pair The first transmission service type required by the tenant, the second group identification code corresponding to a second transmission service type required by the tenant, the processing circuit is further configured to: request the controller to target the first transmission service type Generating one or more first packet headers, causing the controller to update the forwarding flow tables of the forwarding devices according to the one or more first packet headers; and requesting the controller to target the second transmission service type Generating one or more second packet headers, causing the controller to update the forwarding flow tables of the forwarding devices according to the one or more second packet headers. The network coordination device of claim 11, wherein the processing circuit is further configured to: map the first group identification code to the one or more first packet headers through a mapping table; The second group identification code is mapped to the one or more second packet headers through the mapping table. The network coordination device of claim 11, wherein the first transmission service type and the second transmission service type are different services. Packet type. The network coordination device of claim 10, wherein the processing circuit is further configured to: establish a mapping table for the tenant, the mapping table includes the tenant identification code of the tenant, the one or more groups The identification code, and the type of the transmission service corresponding to each of the group identification codes. The network coordination device of claim 10, wherein the processing circuit is further configured to: provide a template for the tenant to input the resource sharing request; wherein the resource sharing request includes a transmission frequency Wide request value. The network coordination device according to claim 14, wherein the requirement template is implemented by a Representational State Transfer (REST) application interface. The network coordination device of claim 10, wherein the processing circuit is further configured to: establish a mapping table for the tenant, the mapping table includes the tenant identification code of the tenant, the one or more groups An identification code, and a type of the transmission service corresponding to each of the group identification codes; and establishing another mapping table for the another tenant, the another mapping table including the another tenant identification code of the another tenant, the other One or more group identification codes, and the other transmission service type corresponding to each of the other group identification codes. The network coordinating device of claim 10, wherein the tenant is a physical network operator, a virtual network operator, or a service provider.