WO2007048185A1 - Systeme et procede facilitant la constitution d'un environnement de collaboration en reseau - Google Patents

Systeme et procede facilitant la constitution d'un environnement de collaboration en reseau Download PDF

Info

Publication number
WO2007048185A1
WO2007048185A1 PCT/AU2006/001585 AU2006001585W WO2007048185A1 WO 2007048185 A1 WO2007048185 A1 WO 2007048185A1 AU 2006001585 W AU2006001585 W AU 2006001585W WO 2007048185 A1 WO2007048185 A1 WO 2007048185A1
Authority
WO
WIPO (PCT)
Prior art keywords
accordance
participants
collaborative environment
collaboration data
networked collaborative
Prior art date
Application number
PCT/AU2006/001585
Other languages
English (en)
Inventor
Jonathan Chan-Lon Chan
Peter Glynn Rogers
Darwin Agahari
Original Assignee
Commonwealth Scientific And Industrial Research Organisation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from AU2005905923A external-priority patent/AU2005905923A0/en
Application filed by Commonwealth Scientific And Industrial Research Organisation filed Critical Commonwealth Scientific And Industrial Research Organisation
Publication of WO2007048185A1 publication Critical patent/WO2007048185A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0272—Virtual private networks

Definitions

  • the present invention relates to a system and method for facilitating the formation of a Networked Collaborative Environment between a plurality of participants, and, more particularly, but not exclusively, to a system and method for implementing network functionality supporting Collaborative Contexts between participants in a virtual enterprise.
  • the present invention provides a device for facilitating the formation of a networked collaborative environment between a plurality of participants, via a network infrastructure, the device including a collaboration data receiving means arranged to be accessible by each of the participants to enable each participant to provide collaboration data to the collaboration data receiving means, the collaboration data representing a contribution to the networked collaborative environment by the respective participant, the collaboration data receiving means being arranged to provide the collaboration data to a networking configuration means which is arranged to utilise the collaboration data to configure the network infrastructure to support the networked collaborative environment, including the contributions by the participants.
  • a "networked collaborative environment” is defined to be an environment which supports collaboration between a plurality of participants, such as, for example, collaboration in a virtual enterprise.
  • the networked collaborative environment is supported by networking functionality (in one embodiment extranet functionality) .
  • the device of the present invention advantageously facilitates the formation of the networked collaborative environment by enabling participants to "negotiate" resources to provide to the networked collaborative environment, and when the negotiation is complete, a network connecting those resources is implemented from the collaboration data which has been provided by the participants.
  • the device of the present invention supports the concept of (and enables implementation of) a "Collaborative Context" as a framework for defining service constructs, based on virtualisation techniques, within a virtual networking environment, to enable collaborating participants belonging to different competitive companies, to have collective provisioning capabilities for the purpose of contributing and negotiating selective resources (e.g. CPU, storage, data, computing machinery, end user) to create a virtual private enterprise for some mutual benefit.
  • a Collaborative Context remains quite distinct from other Collaborative Contexts that a company may be involved in.
  • the collaboration data includes user resource data representing the resources that the participants intend to contribute to the networked collaborative environment. These may include computing devices, applications, and in one embodiment may also include users who may be associated with a participant organisation.
  • resources may be designated at application granularity.
  • the collaboration data receiving means is available on-line to computing systems of the participants.
  • the collaboration data receiving means may be implemented by appropriate software and/or hardware which is arranged to interact with the participants and with the network.
  • the collaboration data receiving means includes an electronic document which is presented to the participants.
  • the document may be Web-based.
  • the formation of the networked collaborative environment involves the participants providing collaboration data to the collaboration data receiving means and each of the participants negotiating the collaboration data receiving means until agreement is reached.
  • the agreed collaboration data receiving means is then utilised to implement networking functionality (e.g. an extranet) in the network infrastructure, supporting the networked collaborative environment.
  • networking functionality e.g. an extranet
  • This embodiment therefore has the advantage that participants are provided with a process by way of which they may make contributions to a collaboration and which does not require substantial (or, indeed, any) intervention by the network provider.
  • the collaboration data receiving means is completed by the participants and then utilised by the networking configuration means to implement the supporting network.
  • the participants do not need to have any knowledge of the underlying network infrastructure.
  • the collaboration data is in terminology which is "high level" and does not require any skill or knowledge in network infrastructure .
  • the high level terminology includes terminology enabling participants to designate resources to be allocated to the networked collaborative environment.
  • the terminology includes Universal Resource Identifiers (URIs) designating user resources such as computing systems, applications, processors and users.
  • URIs Universal Resource Identifiers
  • URIs Universal Resource Identifiers
  • each of the participants may add and negotiate the various resources they are willing to contribute, utilising the collaboration data receiving means (which, as discussed above, in one embodiment is an electronic document) . Once all participants are satisfied with the resources being contributed, then they can w sign off" . Implementation of the network supporting the collaboration is then carried out without requiring any participant input.
  • An advantage of at least one embodiment is that a single collaboration data receiving means implements the corresponding networked collaborative environment. If the participants wish to enter other networked collaborative environments with other participants, then they will utilise other collaboration data receiving means, and therefore the networked collaborative environments will be isolated from each other. Even where a participant is involved in a number of networked collaborative environments, therefore, other participants will not know which particular environments they are involved in and which resources are allocated to those environments.
  • a further advantage of each participant having access to the collaboration data receiving means is that the networked collaborative environment is managed by the participants in a decentralised collective manner rather than being centrally managed (e.g. by network service providers) .
  • amendments can be made to the collaboration data receiving means by one or more of the participants, and the amendments then implemented in the network infrastructure. Again, in this embodiment, this does not require the intervention of a network provider.
  • the collaboration data is such as to be understandable by users who do not have any particular skills in configuring a network infrastructure. That is, the collaboration data provides a level of "abstraction" of network concepts. This enables end users without skill or knowledge of network infrastructure (e.g. they may not be network administrators) to be able to implement the networked collaborative environment.
  • the networking configuration means includes conversion means arranged to utilise the abstract collaboration data to provide network parameter values for implementation of the supporting network functionality.
  • the network parameter values may include binding of each resource to a customer resource specification (e.g. host address information, etc) and network requirements (e.g. QoS descriptors, security parameters, routing attributes, start time, etc) .
  • customer resource specification e.g. host address information, etc
  • network requirements e.g. QoS descriptors, security parameters, routing attributes, start time, etc
  • the system is arranged such that only participants of the networked collaborative environment are able to contribute collaboration data to the collaboration data receiving means. That is, no contributions are able to be made by other parties, such as the network provider. In this sense, the collaboration data receiving means is "controlled" by the participants of the networked collaborative environment.
  • the device of the present invention may be hosted by a network provider.
  • the supporting network functionality is implemented via a network infrastructure, having an architecture comprising Provider Edge (PE) devices connected by Customer Edge (CE) devices.
  • PE Provider Edge
  • CE Customer Edge
  • Such a network infrastructure may be implemented via a carrier grade network.
  • the networking configuration means is implemented by appropriate software/hardware in the PE device.
  • the collaboration data receiving means may be implemented by the PE device. Processes in the PE device are configured to implement the supporting network functionality.
  • an end user may be specified as a resource contributed to the networked collaborative environment.
  • the supporting network may be implemented to enable the end user to enter a collaboration via a computing device which is not necessarily specified as a resource to the collaboration.
  • the computing device is "dynamically bound" to the collaboration, by virtue of the user being specified as a resource. The user may move from one machine to another without needing to renegotiate inclusion of any new machine in the networked collaborative environment.
  • participant can "on demand” negotiate resources to be contributed to a collaboration through "virtualisation functions" .
  • Virtualisation functions introduce a level of abstraction among participants involved in a collaboration and between the participants and the underlying network infrastructure over which a collaboration operates. End resources therefore only need to relate to a virtual networking environment . A clean separation is therefore maintained between service provisioning and the network operations.
  • the device can be used to implement any networked collaborative environment, and in particular can be used to support Collaborative Contexts for Virtual Enterprises .
  • the present invention provides a system for facilitating the formation of a networked collaborative environment between a plurality of participants, the system including a device in accordance with the first aspect, and a networking configuration means which is arranged to utilise the collaboration data to configure a network infrastructure to implement the supporting network functionality for the networked collaborative environment, including the contributions by the participants.
  • the present invention provides a method of forming a networked collaborative environment between a plurality of participants, via a network infrastructure, the method comprising the steps of each of the participants negotiating contributions of resources they each wish to make to the networked collaborative environment, by providing collaboration data representing their proposed contributions, to a device including a collaboration data receiving means which is accessible by each of the participants, and implementing the supporting network functionality for the networked collaborative environment, by configuring the network infrastructure, including the contributions by the participants.
  • the present invention provides a method of facilitating formation of a networked collaborative environment between a plurality of participants, via a network infrastructure, including the steps of utilising a virtual networking environment including virtualisation functions that the participants can use to negotiate contributions that they will each make to the networked collaborative environment, the virtualisation functions being usable to configure a network infrastructure to implement the supporting network functionality for the networked collaborative environment, including the contributions by the participants.
  • the collaboration includes resources the participants wish to contribute to the networked collaborative environment, and the virtualisation functions include means arranged to designate the resources.
  • the virtualisation functions may include a device in accordance with the first aspect of the present invention.
  • the present invention provides an arrangement for facilitating formation of a networked collaborative environment between a plurality of participants, via a network infrastructure, the arrangement including virtualisation functions that the participants can utilise to negotiate contributions they will each make to the networked collaborative environment, the virtualisation functions being usable to configure a network infrastructure to implement supporting network functionality for the networked collaborative environment, including the contributions by the participants.
  • the present invention provides a computer programme including instructions for controlling a computing system to implement a device in accordance with the first aspect of the present invention.
  • the present invention provides a computer readable medium providing a computer programme in accordance with the sixth aspect of the present invention.
  • the present invention provides a computer programme including instructions for controlling a computing system to implement a system in accordance with the second aspect of the present invention.
  • the present invention provides a computer readable medium providing a computer programme in accordance with the eighth aspect .
  • the present invention provides a computer programme including instructions for controlling a computer system to implement an arrangement in accordance with the fifth aspect of the present invention.
  • the present invention provides a computer readable medium providing a computer programme in accordance with the tenth aspect of the present invention.
  • Figure 1 is a schematic diagram of a network arranged to implement a system in accordance with an embodiment of the present invention
  • Figure 2 is a schematic diagram illustrating an architecture of a system in accordance with an embodiment of the present invention
  • Figures 3 to 8 are schematic diagrams showing various stages in negotiation of an implementation of a networked collaborative environment in accordance with an embodiment of the present invention
  • Figure 9 shows a schematic diagram of a implementation of the present invention where participants to the networked collaborative environment also have prior connectivity via an alternative network;
  • Figure 10 is a diagram illustrating a packet walk-through for an implementation of supporting network functionality for a networked collaborative environment, in accordance with an embodiment of the present invention.
  • Figure 11 illustrates a process of "dynamic binding" of a further participant resource into the networked collaborative environment.
  • the following description describes an embodiment of the present invention which is a system and process for implementing a networked collaborative environment between a plurality of participants who may be involved in a virtual enterprise, for example, and wish to operate in a Collaborative Context and contribute resources, e.g. computing resources, to the collaboration. It will be appreciated, however, that the invention is not limited to implementing a Collaborative Context, but is able to facilitate implementation of any networked collaborative environment which may require supporting communication network functionality.
  • VPN Virtual Private extranet Service
  • a system for facilitating formation of a networked collaborative environment between a number of participants includes a collaboration data receiving means, which in this embodiment includes an electronic document, termed an "e-contract".
  • the e-contract is hosted by a network provider, who, in this embodiment, is responsible for a carrier grade network.
  • the e-contract is utilised by each of the participants to the networked collaborative environment to "negotiate" a Collaborative Context, by contributing resources which are entered into the e-contract.
  • a networking configuration means which in this embodiment is implemented by appropriate software and/or hardware in Provider Edge. (PE) devices, implements a supporting VPN and policy engine by configuring the carrier network appropriately.
  • PE Provider Edge.
  • VPXS is embodied as a virtual network provisioning framework that in this embodiment operates over carrier grade networks.
  • the VPXS architecture has adopted a notion from the IETF Layer 3 VPN reference model, namely, Provider Edge (PE) devices. It is assumed that a PE can serve multiple participants. Each participant may be a company and each company intranet connects to an identifiable interface of a PE via a customer edge (CE) device (see Figure 1) .
  • the CE may be a layer 2 or 3 networking device, and company resources may connect directly to the CE or via some other layer 2 or 3 networking devices .
  • the peering PEs instruct the underlying carrier network to establish traffic aggregates, known as PE tunnels.
  • PE tunnels may be realised as an MPLS label switched path (LSP) , a GMPLS tunnel, an IP-in-IP tunnel, a Virtual LAN (VLAN), etc.
  • LSP MPLS label switched path
  • GMPLS tunnel GMPLS tunnel
  • IP-in-IP tunnel IP-in-IP tunnel
  • VLAN Virtual LAN
  • Collaborative Contexts in this embodiment shall be user-provisioned.
  • the ability of this embodiment to enable end users to provision a Collaborative Context is a significant advantage.
  • a web application is utilised to provide the electronic document which forms the e-contract, to enable participants to specify, negotiate and provision the Collaborative Context.
  • the virtualisation functions which include the electronic document which forms the e-contract and which also include the networking configuration means which is arranged to implement the e-contract have a distributed design (implemented by software/hardware in each PE device) and therefore certain information needs to be exchanged between PE devices before a Collaborative Context is established.
  • company public-information e.g. company name, specialty, and contact details
  • service discovery process e.g. peer-to-peer, yellow pages, etc
  • an initiator (a) selects the companies to be involved and (b) nominates the identity of the end-user and application-resource (i.e. a type of Universal Resource Identifier - URI) within his own company to be used in the collaboration.
  • the URI defines a finer granularity of forwarding operations for the Collaborative Context where the URIs form the basis of an e-contract.
  • the e-contract is distributed to all peering PEs in the collaboration for the consideration of the other nominated participants (see #2 in Figure 2) .
  • each collaborating company will also add collaboration data by nominating, exchanging and committing their URIs to be used in the collaboration. Since a URI is a representation of a company' s internal resource, it was not revealed during the prior exchange of company public-information (see #1 in Figure 2) , but it is nominated at this point by each collaborating participant from their own private-information repository. During the lifetime of a Collaborative Context, a URI may be dynamically added to or removed from the collaboration. This constitutes a change in the e-contract which is subsequently disseminated among all peering PEs for the approval of the other participants.
  • each peering PE translates its own URIs into (a) customer resource specification (e.g. host address, web services addressing information, etc.) and (b) generates required network parameters for the underlying extranet service (e.g. QoS descriptors, security parameters, routing attributes, start time, etc.) .
  • customer resource specification e.g. host address, web services addressing information, etc.
  • required network parameters for the underlying extranet service e.g. QoS descriptors, security parameters, routing attributes, start time, etc.
  • the virtualisation functions facilitate the exchange and negotiation of collaboration data using a standardised protocol, for instance web services (#2 in Figure 2) .
  • the virtualisation functions are a distributed set of software/hardware components that reside in each PE.
  • the framework shown in Figure 2 has a number of key advantages for the deployment of new services that use the concept of Collaborative Contexts:
  • Web services standards may be used to provide the flexibility and extensibility required to support the introduction of new services. Without the benefits of the framework articulated above, the provisioning of extranet services would, based on current technologies, need to be embedded within some network level routing protocol such as BGP.
  • PE tunnels are constructed using a path setup protocol (e.g. RSVP-TE to establish an MPLS label switched path) . Since the establishment of a PE tunnel is instigated on-demand, by the virtualisation functions, a pre-configured full mesh topology between all PEs can be avoided.
  • RSVP-TE path setup protocol
  • the exchanged collaboration data is used by the PE for: • Invocation of exclusive forwarding operations on a per customer resource basis. Examples are, populating entries in (1) a policy routing mechanism with source/destination addresses or (2) a web switch with web services addressing information.
  • Collaborative Context operates.
  • the VPN technology is based on the IETF RFC2547 recommendation (BGP/MPLS VPNs) .
  • BGP/MPLS VPNs BGP/MPLS VPNs
  • company public-information e.g. company name, specialty and contact details
  • a distributed service discovery process e.g. peer-to-peer, yellow pages, etc
  • An initiator say company x b' , needs to select other companies, in this case only ⁇ c', to join a collaboration. Based on company b's private-information, the initiator nominates the URIs within its own company to be used in the collaboration (e.g. the identity of the end-user, Bob@companyB.com, and the application resource, pcl.companyB.com). This constitutes the basis of a ⁇ draft' status e-contract. It is assumed that each company's private-information is maintained by a PE prior to a Collaborative Context being set up. A person skilled in the art will appreciate how to populate the PE with this information. #2.
  • PEl forwards the e-contract to all peering PEs of the collaboration (only PE2 in this case) . It is assumed that all invitees (only company ⁇ c' in this case) will know about the existence of the e-contract by means
  • All invitees who accept the invitation shall also nominate the URIs to be used in the collaboration (for company ⁇ c', the identity of the end-user, Cath@companyC.com and the application resources, pc2.companyC.com and pc3. companyC . com) .
  • the e-contract On reaching the 'approved' status, the e-contract is committed for deployment by a nominated party (e.g. the initiator company) . At this point the status of the e-contract changes to 'pre-active' . This means that the
  • Collaborative Context is now ready to be deployed but the configuration of the underlying network is not yet invoked. #6.
  • the ⁇ pre-active' status e-contract is sent to all the other participating PEs. #7.
  • each participating PE (a) translates the URIs of their customers within the e-contract into customer resource specifications (for company B: pcl.companyB.com becomes IP address bl, etc.) and (b) generates required network parameters for the underlying VPN service (the route target attribute of RFC 2547 for this
  • Collaborative Context is x red' , etc.) . This information is added to the e-contract which is automatically updated and exchanged among all participating PEs. All company participants within a Collaborative Context have visibility of the ⁇ pre-active' status e-contract. A Collaborative Context is scheduled to commence either immediately or at a specified time in the future. Just prior to activation of the e-contract, the underlying network will be configured in accordance with the specifications of the Collaborative Context. Upon configuration of the network, the e-contract status is promoted from ⁇ pre-active' to ⁇ active' . The following description explains how the underlying network is configured.
  • PE tunnels are constructed as required using a standardised protocol (e.g. RSVP-TE) to establish MPLS label switched paths.
  • Figure 5 shows new entries being populated in the MPLS forwarding table, held in the PEs, after two uni-directional MPLS label switched paths have been set up between PEl and PE2.
  • PE tunnels are intended to be shared among many Collaborative Contexts if they happen to go to the same peering PE.
  • establishment of PE tunnels is a prerequisite for setting up a Layer 3 VPN over which a Collaborative Context operates.
  • a BGP/MPLS VPN is configured for the Collaborative Context.
  • the VPN is configured in accordance with the network requirements of the ⁇ pre-active' status e-contract.
  • VRF ⁇ red' table subsequently learns local customer routing information (for company B: subnet ⁇ bx' is cached and an inner label of 1001 is assigned to this interface) via an inter-gateway protocol such as OSPF.
  • the MPLS forwarding table is also updated with label entry 1001.
  • the Multi-Protocol Inter-Border Gateway Protocol MP-IBGP
  • MP-IBGP Multi-Protocol Inter-Border Gateway Protocol
  • the policy engine in PEl ensures that only packets from company ⁇ b' (via if_3 say) with source address bl and destination addresses cl2 or c21 go to the VRF red table. Note that inspection of both source and destination addresses is necessary because a customer resource may be involved in several collaborations at the same time. Namely, if a customer is involved in two concurrent collaborations the source address is the same but the destination addresses will be different, therefore the traffic of each collaboration will be steered to their own VRF.
  • a Collaborative Context's traffic is only routed among intranets via the PE tunnels. Consequently, this traffic must be directed by participating intranets to the associated PEs, which they achieve by learning remote intranet routing information. This requirement however, may impose some additional look-ups on the routers in the participating intranets. And as such consequential routing issues may arise, within these intranets, the complexity of which depends on the topology, connectivity and local administrative policies of the intranets. It is understood that various PE-intranet scenarios may exist in real life situations, but in general, matters peculiar to an intranet are outside the control of the VPXS service provider therefore routing issues which may arise in different PE-intranet scenarios will be implemented in accordance with the skilled addressee's skill and knowledge. We show below a few of the more likely PE-intranet scenarios.
  • Case 1 Perhaps the simplest case is that no remote routing information for a VPN needs to be learned by an intranet. This means that all outbound intranet traffic goes via its associated PE. A policy engine in the PE classifies which traffic forwards into the PE tunnels and which traffic forwards into other connections (e.g. the Internet) .
  • Case 2 For this case it is assumed that prior to the introduction of VPXS, different company intranets have no connectivity (i.e. their subnet addresses are unreachable by each other) . Now VPXS is introduced into the network. In this case the remote subnet address of a destination intranet is learned by a local intranet through a standard routing protocol (e.g. OSPF) .
  • OSPF standard routing protocol
  • Case 3 For this case it is assumed that, before the introduction of VPXS, a remote intranet's subnet address is already reachable by a local intranet (e.g. company ⁇ Jb' and ⁇ c' have prior connectivity via another network such as the Internet, see Figure 9) . Now with the introduction of VPXS, Collaborative Context traffic, between these already reachable intranets, needs to be directed from the intranets , into the PEs instead of some pre-existing connection. To achieve this, remote per host routing information needs to be learned by the local intranet's CE device and default gateway through a standard routing protocol (e.g. OSPF) . Preferably the CE device is the intranet's default gateway to avoid propagation of per host routing information throughout the intranet (see Figure 11) .
  • a standard routing protocol e.g. OSPF
  • Figure 10 shows a packet walk-through from a customer resource in company ⁇ c' to a customer resource in company x b' (i.e. from c21 to bl) , which invokes the functionality of, the policy engine in PE2 , the VRF table in PE2 and the MPLS forwarding in PEl.
  • Figure 11 shows the dynamic binding of a customer resource into a Collaborative Context. This occurs when a previously nominated user registers from an end host to the associated PE (i.e. Cath in company ⁇ c' logs in from c22) .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un système et un procédé de formation d'un environnement de collaboration en réseau entre un certain nombre de participants. Les membres du personnel de sociétés souhaitent souvent établir des relations afin de participer, par exemple, à une entreprise virtuelle pouvant exiger de chaque participant qu'il ait accès à une partie limitée des ressources mutuelles. Le système mis en place dans le cadre de cette invention offre aux participants la possibilité de créer un environnement de collaboration en réseau via une infrastructure en réseau, au sein duquel chaque participant dévolue des ressources (telles que des ressources informatiques) à l'environnement de collaboration. Le système comprend un dispositif de réception de données de collaboration émanant de chacun des participants, données incluant des informations sur les ressources que les participants fournissent (telles que des adresses URL). Un moteur utilise ces données pour configurer un réseau destiné à exploiter la fonctionnalité du réseau pour l'environnement de collaboration, dont les ressources apportées par les participants.
PCT/AU2006/001585 2005-10-26 2006-10-26 Systeme et procede facilitant la constitution d'un environnement de collaboration en reseau WO2007048185A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
AU2005905923A AU2005905923A0 (en) 2005-10-26 A method and system for facilitating the formation of a networked collaborative environment
AU2005905923 2005-10-26

Publications (1)

Publication Number Publication Date
WO2007048185A1 true WO2007048185A1 (fr) 2007-05-03

Family

ID=37967338

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/AU2006/001585 WO2007048185A1 (fr) 2005-10-26 2006-10-26 Systeme et procede facilitant la constitution d'un environnement de collaboration en reseau

Country Status (1)

Country Link
WO (1) WO2007048185A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115934112A (zh) * 2023-03-10 2023-04-07 德萱(天津)科技发展有限公司 一种基于驱动属性的多种类软件协作处理方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002041624A2 (fr) * 2000-11-06 2002-05-23 Terry Bernard Young Procede et systeme d'echange commerciaux par le biais de marches electroniques
US20030163547A1 (en) * 2001-09-28 2003-08-28 Accenture Global Services Gmbh Collaborative portal system for business launch centers and other environments
US20040078430A1 (en) * 2002-10-22 2004-04-22 Kraft Foods Holdings, Inc. Method to facilitate a collaborative supply of materials
US20060015562A1 (en) * 2004-07-19 2006-01-19 Roger Kilian-Kehr Mobile collaborative peer-to-peer business applications

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002041624A2 (fr) * 2000-11-06 2002-05-23 Terry Bernard Young Procede et systeme d'echange commerciaux par le biais de marches electroniques
US20030163547A1 (en) * 2001-09-28 2003-08-28 Accenture Global Services Gmbh Collaborative portal system for business launch centers and other environments
US20040078430A1 (en) * 2002-10-22 2004-04-22 Kraft Foods Holdings, Inc. Method to facilitate a collaborative supply of materials
US20060015562A1 (en) * 2004-07-19 2006-01-19 Roger Kilian-Kehr Mobile collaborative peer-to-peer business applications

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115934112A (zh) * 2023-03-10 2023-04-07 德萱(天津)科技发展有限公司 一种基于驱动属性的多种类软件协作处理方法
CN115934112B (zh) * 2023-03-10 2023-05-12 德萱(天津)科技发展有限公司 一种基于驱动属性的多种类软件协作处理方法

Similar Documents

Publication Publication Date Title
JP7290732B2 (ja) データ転送方法及び関連する装置
CN1957568B (zh) 用于配置跨域电信服务的开放式服务发现和路由选择机制
CN110809875B (zh) 服务对等交换
KR101352693B1 (ko) 통신 장치 및 방법
US10454821B2 (en) Creating and maintaining segment routed traffic engineering policies via border gateway protocol
US8954591B2 (en) Resource negotiation for cloud services using a messaging and presence protocol
US7272643B1 (en) System and method for managing and provisioning virtual routers
US8179905B1 (en) Method and apparatus for providing communication for virtual private networks
US20100027549A1 (en) Method and apparatus for providing virtual private network identifier
EP3151477B1 (fr) Fourniture rapide de contenu sur des réseaux d'accès metro
US20130035079A1 (en) Method and system for establishing data commuication channels
EP3151478B1 (fr) Contenu d'antémémoire de réseaux d'accès métropolitains
WO2014074962A1 (fr) Détection de qualité de service de communication et de collaboration unifiées (uc&c) sur des interréseaux
WO2018077304A1 (fr) Procédé, appareil et système de traitement d'informations de service
CN104506459B (zh) 智慧协同网络中的数据包传输方法、装置和系统
US7730294B2 (en) System for geographically distributed virtual routing
Semeria et al. Rfc 2547bis: bgp/mpls vpn fundamentals
Gleeson et al. RFC2764: A framework for IP based virtual private networks
EP1751935B1 (fr) Mecanisme de recherche et d'acheminement de services ouverts servant a effectuer la configuration de services de telecommunication interdomaines
WO2007048185A1 (fr) Systeme et procede facilitant la constitution d'un environnement de collaboration en reseau
Chan et al. Enterprise collaborative contexts and their provisioning for secure managed extranets
JP2002290441A (ja) Ｉｐ−ｖｐｎルータおよびｉｐ−ｖｐｎ用パケット転送路自動設定方法
Hilliard et al. Internet exchange bgp route server operations
Carthern et al. Intermediate LAN Switching
Yegenoglu et al. TSAT advanced network services and routing architecture

Legal Events

Date Code Title Description
DPE2 Request for preliminary examination filed before expiration of 19th month from priority date (pct application filed from 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06790420

Country of ref document: EP

Kind code of ref document: A1