WO2024036921A1

WO2024036921A1 - Object processing method and apparatus, and device

Info

Publication number: WO2024036921A1
Application number: PCT/CN2023/079639
Authority: WO
Inventors: 翁新瑜
Original assignee: 华为云计算技术有限公司
Priority date: 2022-08-19
Filing date: 2023-03-03
Publication date: 2024-02-22
Also published as: CN117640120A

Abstract

An object processing method and apparatus, and a device. In the present application, a joint apparatus receives a registration operation executed by a user on a joint network platform, grants the user permission to process an object, detects an object publishing operation executed by the user on the joint network platform, and acquires information of an object. The joint apparatus publishes the information of the object on the joint network platform, and selects a target network platform from a plurality of network platforms signing a contract with the joint network platform. After selecting the target network platform, the joint apparatus publishes the information of the object on the target network platform; and the user is notified that the object is successfully published on the joint network platform and the target network platform. The joint apparatus is deployed in a computing device. The user executes the registration operation and the object publishing operation on the joint network platform, so that the joint apparatus can publish the object on the joint network platform and the target network platform, thereby preventing the user from repeatedly performing the registration operation and the object publishing operation, and simplifying the registration and object publishing processes.

Description

An object processing method, device and equipment

Cross-references to related applications

This application claims the priority of the Chinese patent application submitted to the China Patent Office on August 19, 2022, with the application number 202210999881.7 and the application title "An object processing method, device and equipment", the entire content of which is incorporated herein by reference. Applying.

Technical field

The present application relates to the field of cloud technology, and in particular, to an object processing method, device and equipment.

Background technique

With the popularity of cloud data centers, various types of cloud market businesses that can be deployed in the cloud have emerged. For example, financial cloud market, government cloud market. Various financial products released by banks and other financial institutions in the financial cloud market, and some government service products released by official organizations in the government cloud market.

These different types of cloud markets are relatively independent, and product publishers need to register, release products, update and revoke products in each cloud market respectively.

As the number of cloud markets that product publishers need to register increases and the number of products they maintain increases, product publishers need to perform a large number of registration operations and product processing operations.

Contents of the invention

This application provides an object processing method, device and equipment to achieve unified registration and unified object processing for different network platforms.

In the first aspect, embodiments of the present application provide an object processing method, which can be executed by a joint device. The joint device can be deployed in one computing device or in a cluster composed of multiple computing devices. The joint device receives The registration operation performed by the user on the joint network platform grants the user the permission to process objects on the joint network platform, and can also grant the user the permission to process objects on the network platform contracted with the joint network platform. The joint device detects the user's access to the joint network platform. The object publishing operation performed on the joint network platform obtains the information of the object that needs to be published provided by the user; the joint device publishes the object information on the joint network platform and selects the target network on multiple network platforms that have signed contracts with the joint network platform platform; after selecting the target network platform, publish the object's information in the target network platform; notify the user that the object has been successfully published on the joint network platform and the target network platform.

Through the above method, the user only needs to perform the registration operation and object publishing operation on the joint network platform, and the joint device can publish the object on the joint network platform and the target network platform, avoiding the user from performing repeated registration operations and object publishing operations, simplifying Registration and object publishing process.

In a possible implementation, the joint device can also establish a contract connection between the joint network platform and multiple network platforms, and obtain the object provision policies and object processing rules of multiple network platforms. The object provision policy is used to describe the requirements for providing objects. Constraint policies to be followed, object processing rules are used to describe the constraint rules that need to be followed for object processing operations.

Through the above method, the joint device can establish the contracting relationship between the joint network platform and multiple network platforms in advance, so as to Subsequently, the user's registration operations and object processing operations (such as object release operations, update operations, cancellation operations, and transaction operations) on the joint network platform will be synchronized to the network platform with which the user has contracted.

In a possible implementation, the object processing rules include object publishing rules, and the object publishing rules describe the constraint rules that need to be followed for object publishing operations; when the joint device selects a target network platform from multiple network platforms that have contracted with the joint network platform , the user's information can be obtained; the target network platform is selected from multiple network platforms based on the user's information, the object provision strategies of multiple network platforms, and the object processing rules. Among them, the user complies with the object provision strategy of the target network platform, and the object publishing operation Comply with the object handling rules of the target network platform.

Through the above method, the joint device can select the target network platform for the user by itself, without the user having to select, and automatically synchronizes the object processing operations of the joint network platform and other network platforms.

In a possible implementation, the target network platform can also be specified by the user. That is to say, the association device can obtain the specified information sent by the user, and the specified information indicates the target network platform.

Through the above method, users can specify the target network platform according to their own needs, and the joint device can publish objects on the target network platform according to the user's needs.

In a possible implementation, the association device can also synchronize transaction operations performed on the object. The joint device obtains the transaction information of the object from the target network platform, and the transaction information of the object describes the transaction operation performed on the object on the target network platform; it feeds back the transaction information of the object to the user.

Through the above method, the association device can obtain relevant information (that is, transaction information) on the transaction operation on the target network platform and notify the user in a timely manner.

In a possible implementation, the object processing rules include object update rules. The object update rules describe constraint rules that need to be followed for update operations on the object. The association device can synchronize the update operations performed on the object. For example, the joint device can detect the update operation performed by the user on the object on the joint network platform, obtain the information that the object provided by the user needs to be updated in the target network platform according to the update operation; send an update request to the target network platform, and the update request is used to request The object is updated in the target network platform, and the update request includes the information that needs to be updated.

Through the above method, the joint device can synchronize the update operation on the joint network platform to the target network platform, thereby preventing the user from performing repeated update operations.

In a possible implementation, the object processing rules include object cancellation rules. The object cancellation rules describe constraint rules that need to be followed for the cancellation operation on the object. The association device can synchronize the cancellation operations performed on the object. The joint device can detect the revocation operation performed by the user on the object on the joint network platform, determine the object that the user needs to cancel on the target network platform based on the detection operation; send a revocation request to the target network platform, and the revocation request is used to request revocation on the target network platform. Undo the object.

Through the above method, the joint device can synchronize the undo operation on the joint network platform to the target network platform to prevent the user from performing repeated undo operations.

In the second aspect, embodiments of the present application also provide a joint device that has the behavioral function of realizing the joint device in the method example of the first aspect. The beneficial effects can be found in the description of the first aspect and will not be described again here. Functions can be implemented by hardware, or by hardware executing corresponding software. Hardware or software includes one or more modules corresponding to the above functions. In a possible design, the structure of the joint device includes a joint management module and a unilateral management module. These modules can perform the corresponding functions in the above method examples of the first aspect. For details, please refer to the detailed description in the method examples, which will not be described again here.

In a third aspect, embodiments of the present application also provide a computing device that has the function of realizing the behavior of the combined device in the method example of the first aspect. For beneficial effects, please refer to the description of the first aspect and will not be repeated here. . The structure of the computing device includes a processor and a memory, and the processor is configured to support the associated device to perform corresponding functions in the method of the first aspect. A memory is coupled to the processor and stores computer program instructions and data necessary for the associated device. The structure of the communication device also includes a communication interface for communicating with other devices.

In the fourth aspect, embodiments of the present application also provide a computing device cluster, which has the function of realizing the behavior of the joint device in the method example of the first aspect. For beneficial effects, please refer to the description of the first aspect. Again. The computing device cluster includes at least one computing device. The structure of any computing device includes a processor and a memory. The processor in any computing device is configured to support the joint device to execute the above-mentioned first aspect and each possible implementation of the first aspect. Some or all of the features in the method. A memory is coupled to the processor and stores computer program instructions and data necessary for the associated device. The structure of the communication device also includes a communication interface for communicating with other devices.

In a fifth aspect, this application also provides a computer-readable storage medium. The computer-readable storage medium stores instructions, which when run on a computer, cause the computer to execute the above-mentioned first aspect and each possible implementation of the first aspect. method within the method.

In a sixth aspect, the present application also provides a computer program product containing instructions that, when run on a computer, cause the computer to execute the method in the above-mentioned first aspect and each possible implementation of the first aspect.

In a seventh aspect, this application also provides a computer chip, which is connected to a memory. The chip is used to read and execute the software program stored in the memory, and execute the method in the above-mentioned first aspect and each possible implementation of the first aspect. .

Description of drawings

Figure 1 is a schematic diagram of the architecture of a system provided by this application;

Figure 2 is a schematic structural diagram of a combined device provided by this application;

Figure 3 is a schematic structural diagram of a unilateral device provided by this application;

Figure 4 is a schematic diagram of an object processing method provided by this application;

Figure 5A is a schematic diagram of a registration interface provided by this application;

Figure 5B is a schematic diagram of a registration interface provided by this application;

Figure 5C is a schematic diagram of a registration interface provided by this application;

Figure 6 is an interface diagram of a publishing object provided by this application;

Figure 7 is a schematic structural diagram of a computing device provided by this application;

Figure 8 is a schematic structural diagram of a computing device cluster provided by this application.

Detailed ways

Before introducing the object processing methods, devices and equipment provided by the embodiments of the present application, several concepts involved in the embodiments of the present application will be described.

1. Network platform.

The network platform is an information collection system in the network. The network platform can be presented in the form of a website or an application. The network platform is oriented to various users so that users can obtain or display items or services on the network platform.

In the embodiment of the present application, the joint device 100 and the single device 200 can maintain their respective network platforms and manage information within their respective network platforms. In the example of this application, the joint device 100 and the single device 200 can manage objects on the network platform. For convenience of distinction, the network platform maintained by the joint device 100 is called a joint network platform. General The network platform maintained by the party device 200 is called a single-party network platform.

The object provider can apply to the federation device 100 to register with the federation network platform. Registration of an object provider to the joint network platform means that the object provider has the authority to process objects on the joint network platform. In this embodiment of the present application, the object provider can also obtain permission to process objects on the single-party network platform by requesting the joint device 100 . That is to say, in this embodiment of the present application, the object provider may not directly apply to the single-party device 200 to register with the network platform, but obtain the permission to process objects on the single-party network platform through interaction with the joint device 100 .

2. Object.

In the embodiment of this application, the object is the form of real items, services, etc. presented in the network environment. In the embodiment of the present application, the joint device 100 or the single device 200 is allowed to process objects in the managed network platform. For example, the joint device 100 or the single-party device 200 can process the object under the instruction of the user (the user can be the object provider or the object acquirer), or can process the object on its own. In the embodiment of the present application, the object The processing includes but is not limited to: object release, object transaction, object withdrawal, and object update.

1), object release.

Object publishing refers to publishing an object to a network platform and presenting the object's information on the network platform. The object's information includes the number of the object, the object's appearance, the object's function introduction and other attribute information related to the object itself. The object's information also includes the object's transaction conditions, and the object's transaction conditions agree on the way to obtain the object. For example, the transaction conditions of the object stipulate the fee to be paid to obtain the object, or the maximum value allowed to obtain the object. For another example, the transaction conditions of the object stipulate the validity period for acquiring the object. The object information is required by the object provider when publishing the information.

In the embodiment of this application, two object publishing methods are allowed. One publishing method is that the object provider directly publishes the object to the network platform managed by the unilateral device 200 through the unilateral device 200, and the other publishing method is that the object provider The other party publishes the object to the network platform managed by the single party's device 200 through the joint device 100 .

In the embodiment of the present application, the joint device 100 or the single-party device 200 can publish the object on the managed network platform when detecting the object publishing operation of the object provider on the managed network platform. Taking the federation device 100 as an example, when the federation device 100 detects the object publishing operation performed by the object provider and determines that the object provider needs to publish the object, the federation device 100 can determine whether the object provider complies with the object provision policy and determine the required Whether the published object complies with the object publishing rules. When the object provider complies with the object provision policy and the object to be published complies with the object publishing rules, the federation device 100 can publish the object to the network platform managed by the federation device 100 .

2), object transaction.

Object transaction refers to the transfer of objects from one party (that is, the object provider) to another party (that is, the object acquirer). Object transaction is to transfer the ownership or usage rights of the object to the object acquirer. The object acquirer can obtain the object from the object provider in accordance with the transaction conditions of the object in the network platform. For example. The object is an item, and the object provider can offer ownership of the object for sale. For another example, if the object is an object, the object provider can provide the right to use the object by leasing the object. For another example, if the object is a virtual product such as a service, the object provider can provide the right to use the object.

In the embodiment of the present application, the joint device 100 or the single-party device 200 can complete the object transaction when detecting the transaction operation of the object by the object acquirer and the object provider on the managed network platform. Taking the joint device 100 as an example, the joint device 100 can initiate a transaction according to the transaction operation of the object acquirer. The joint device 100 can agree or reject the transaction under the instruction of the object provider or in accordance with the object transaction conditions provided by the counterparty provider. It can also Whether the transaction can be established can be determined according to the preset transaction conditions of the object. Upon consent to the transaction or the establishment of the transaction, the joint The device 100 can transfer the ownership of the object from the object provider to the object acquirer on the managed network platform. The association device 100 can also feed back transaction information to the object provider.

3), object cancellation.

Object revocation refers to removing the published object from the network platform, hiding or deleting the object's information in the network platform.

In the embodiment of the present application, the joint device 100 or the single-party device 200 can revoke the object from the managed network platform when detecting the object provider's operation on the object on the managed network platform. Taking the joint device 100 as an example, the joint device 100 can detect the object provider's operation on the joint network platform, hide or delete the object's information from the joint network platform, and can also sign a contract with the joint network platform. Hide or delete the subject’s information on the unilateral network platform.

4), object update.

Object update refers to updating the information of a published object, such as changing the attribute information of the published object or the transaction conditions of the object.

In the embodiment of the present application, the joint device 100 can update the object in the joint network platform when detecting the update operation of the object performed by the object provider on the joint management platform, and can also update the object in the joint network platform through the single-party device 200. 200 to carry out object updates on the network platform managed. Taking the federation device 100 as an example, the federation device 100 can detect an update operation on an object performed by the object provider. For example, the update operation indicates that the object provider needs to change the attribute information of the published object or the transaction conditions of the object. The joint device 100 can change the attribute information of the published object or the transaction conditions of the object on the joint network platform. If the object is also published on a single network platform, the joint device 100 can notify the single device 200 to change the published object. attribute information, or the transaction conditions of the object.

The joint device 100 and the single-party device 200 can also update the object in the managed network platform when detecting a transaction operation on the object performed by the object transaction party. After the object transaction is completed, the joint device 100 and the single-party device 200 will update the object according to the object acquisition party. The executed transaction operation updates the information of the object (such as updating the number of objects, adding the transaction record of the object, etc.). For example, the association device 100 can automatically update the number of objects according to the transaction operation performed by the object acquirer after the object transaction is completed.

3. Object provision strategy and object processing rules.

When the object provider registers to the network platform through the joint device 100 or the single-party device 200, the object provider needs to satisfy the object provision policy set by the joint device 100 or the single-party device 200.

When the object provider processes objects on the network platform through the joint device 100 or the unilateral device 200, the object provider needs to meet the object provision policy set by the joint device 100 or the unilateral device 200, and the processing operation of the object needs to meet Object handling rules. That is to say, the object provision policy is a constraint policy for the object provider and is a constraint policy that the object provider needs to follow. The object processing rules are constraint rules for object processing operations that need to be followed for the object processing operations. Constraint rules.

For example, the object provision policy can restrict the location of the object provider, require the object provider to provide real-name information, and also require the object provider to provide supporting documents. It can also set the amount of the deposit that the object provider needs to pay, and can also set the The object provider needs to provide descriptive materials for the objects to be published.

Regarding object processing rules, for different types of processing operations, the object processing rules include the content of different processing rules. From the perspective of the type of processing operations, the object processing rules include some or all of the following: object publishing rules, object transaction rules , object cancellation rules, object update rules.

Among them, the object publishing rules describe the rules that need to be followed for object publishing. For example, the object publishing rules can stipulate The type of object to be published can also constrain the validity period of the published object, or the time period allowed for publishing the object, and can also constrain the information that needs to be included in the object's information.

Object transaction rules describe the rules that the transaction object needs to follow. For example, object transaction rules can stipulate that the transaction needs to comply with the object transaction conditions, and can also indicate the effective time for payment of fees when trading on the object, and can also indicate that the object acquirer needs to meet Conditions (such as whether real-name authentication, whether the delivery address is valid, etc.) can also indicate whether the object provider is allowed to modify the cost of the transaction object.

Object revocation rules describe the rules that need to be followed to revoke an object. For example, object revocation rules can indicate which objects can be revoked, the effective time period for revoking the object after the object is released, and the automatic revocation of the object. Cancellation condition, for example, the automatic cancellation condition can indicate that the object is automatically canceled when the quantity in the object information changes to zero or when the number of transactions of the object reaches the maximum number of transactions of the object.

Object update rules describe the rules that need to be followed when updating objects. Object update rules can indicate which objects can be updated, and can also indicate the effective time period for updating the object after the object is released. It can also indicate which information of the information is allowed to be updated, which information is prohibited from being updated, and can also indicate that the object can be updated by itself. Automatic update conditions. For example, the automatic update condition can instruct the object to update the quantity in the object information according to the number of transactions every time it trades. It can also instruct the object to record the transaction information (such as the number of transactions, object acquisition, etc.) every time it trades. Party information, transaction time, etc.).

The object processing rules set by the joint device 100 or the unilateral device 200 may include one or more of the above-listed rules. If one or more of the rules are defaulted in the object processing rules, it can be considered as a default. No rules are set for rule-related processing operations. For example, the object processing rules do not include object cancellation rules, and it can be considered that any object can be canceled without any restrictions.

In addition, the division of the object processing rules is only an example. In addition to the several rules listed above, other contents are also allowed to be included in the object processing rules.

The following takes the operation of objects as publishing objects as an example to explain the role of object provision policies and object processing rules.

In the embodiment of this application, when the object provider directly publishes the object to the network platform managed by the unilateral device 200 through the unilateral device 200, the unilateral device 200 only needs to confirm that the object provider complies with the object provision policy set by the unilateral device 200. If the object that needs to be published complies with the object publishing rules set by the unilateral device 200, the object is published to the managed network platform.

When the object provider publishes the object to the network platform managed by the single device 200 through the joint device 100, if the joint device 100 sets the object provision policy and object publishing rules, the joint device 100 needs to first determine whether the object provider complies with the joint device. Whether the object provision strategy and the operation of publishing objects set by the federation device 100 comply with the object publishing rules set by the federation device 100, the federation device 100 determines that the object provider complies with the object provision strategy and the operation of publishing objects set by the federation device 100. In the case of the object publishing rules set by the joint device 100, the joint device 100 can publish the information of the object on the joint network platform, and determine whether the object provider complies with the object provision policy set by the unilateral device 200, the publishing object Whether the operation complies with the object publishing rules set by the unilateral device 200. When the object provider complies with the object provision policy set by the unilateral device 200 and the operation of publishing the object complies with the object publishing rules set by the unilateral device 200, the joint device 100 may initiate a request message to the unilateral device 200. The request Message is used to request publication of the object.

If the joint device 100 does not set the object provision policy and object processing rules, the joint device 100 can directly publish the object information on the joint network platform and determine whether the object provider complies with the rules set by the single device 200 Whether the object provision policy and object publishing operation comply with the object processing rules set by the unilateral device 200, and subsequent steps are performed.

As shown in FIG. 1 , a schematic system architecture diagram is provided according to an embodiment of the present application. The system includes a joint device 100 and multiple single-party devices 200 . The joint device 100 is connected to multiple single-party devices 200 .

Any single party device 200 can manage a single party network platform. The unilateral device 200 can process objects on the unilateral network platform, such as publishing objects, completing object transactions, revoking objects, or updating objects on the unilateral network platform. The single-party device 200 can initiate a signing request to the joint device 100 at the invitation of the joint device 100 or actively establish a contract connection between the joint network platform and the joint network platform. By signing with the joint network platform, the single-party device 200 allows the joint network The object processing operation on the platform is synchronized to the single-party network platform, or the object provider is allowed to process the object on the single-party network platform through the joint device 100 . The processing of the object on the single-party network platform by the single-party device 200 may be based on the object processing operation performed by the object provider or the object acquirer, or may be based on the request message sent by the joint device 100 , or may be It is executed based on the rules preset by the object provider (such as automatic update conditions and automatic withdrawal conditions included in the object processing rules).

The single-party device 200 can also manage object providers registered to the single-party network platform. For example, the single-party device 200 can allow or deny the object provider to register to the single-party network platform through the joint device 100, and can also send information to the object provider through the joint device 100, such as sending information to notify the success or failure of the transaction, and sending notification that the object is released successfully. Or failed response (such as the first successful response, the first rejection response mentioned below) and other messages. Different single-party devices 200 manage different single-party network platforms. One single-party device 200 can only manage the corresponding single-party network platform, but cannot manage the single-party network platforms managed by other single-party devices 200 .

The unilateral device 200 may be provided with corresponding object provision policies and object processing rules. The object provision policies and object processing rules may also be understood as the object provision policies and object processing rules of the unilateral network platform. Among them, the object provision policy is a constraint policy that needs to be satisfied and set for the object provider that needs to register to the unilateral network platform or needs to publish objects on the unilateral network platform. Any object provider that needs to register to the unilateral network platform or that needs to process objects on the unilateral network platform must comply with the object provision policy of the unilateral device 200 . Object processing rules are constraint rules that need to be satisfied for processing operations performed on objects processed on the unilateral network platform. Any processing operation on an object in the unilateral network platform must comply with the object processing rules of the unilateral device 200 .

Some functions of the joint device 100 are similar to those of the single-party device 200. The joint device 100 can also manage a network platform. In order to distinguish it from a single-party network platform, the network platform managed by the joint device 100 is called a joint network platform. The federation device 100 can process the object on the federated network platform when detecting the processing operation performed by the object provider or object acquirer on the object on the federated network platform, such as publishing the object and completing the object on the federated network platform. Transaction, revoke object, or update object. The federation device 100 can also manage object providers registered to the federation network platform. For example, the federation device 100 can agree or deny the registration of the object provider to the joint network platform, and can also send information to the object provider, such as information on successful or failed transactions, information on successful or failed object publishing, etc.

The federation device 100 may be provided with corresponding object provision strategies and object processing rules. The object provision strategies and object processing rules can also be understood as the object provision strategies and object processing rules of the joint network platform. Among them, the object provision policy is a constraint that needs to be met for the object provider that needs to register to the joint network platform or needs to process objects on the joint network platform. Any object provider that needs to register to the federated network platform or that needs to process objects on the federated network platform must comply with the object providing policy of the federated device 100 . Object processing rules are constraints that need to be met for object processing operations on the joint network platform. condition. Any processing operation for objects on the joint network platform must comply with the object processing rules of the joint device 100 .

The federated device 100 is connected to multiple single-party devices 200 . The federated device 100 can also provide the object provider with a direct channel to the single-party network platform managed by any single-party device 200 . The object provider can register to a single-party network platform through the association device 100, that is, obtain the authority to process objects on the single-party network platform. The object provider can also implement object processing on a unilateral network platform through the joint device 100, such as object publishing, object trading, object withdrawal, and object updating. That is to say, the object provider can publish objects to a single-party network platform through the association device 100, trade the objects on the single-party network platform, revoke objects published to the single-party network platform, and update objects published to the single-party network platform.

In the embodiment of this application, the operations on the object provider side and the single-party network platform transaction object refer to the operations that the object provider needs to perform during the object transaction process, such as the object provider obtaining transaction information, the object provider canceling the transaction, etc.

In other words, the joint device 100 can detect the processing operation of the object provider on the object, and initiate a request message (such as the first request message, the second request message, and the third request in subsequent embodiments) to the single device 200 according to the processing operation. message), this request message is used to request the processing of objects on a unilateral network platform. The single-party device 200 can process the object on the single-party network platform according to the request message. The single-party device 200 can also feed back the processing results to the object provider through joint transactions. For the object acquirer, after the object acquirer trades the object on a single-party network platform, the joint device 100 can obtain transaction information from the single-party device 200 that manages the single-party network platform, and feed back the transaction information to the object provider.

In addition to saving its own object provision policy and object processing rules, the joint device 100 can also obtain the object provision policies and object processing rules of each unilateral device 200 .

When an object provider needs to register with a single-party network platform through the joint device 100 or needs to process an object on a single-party network platform, the joint device 100 can determine whether the provider complies with the object provision policy of the single-party device 200 and determine whether the object that needs to be processed complies with the single-party network platform. Object processing rules for device 200.

Both the joint device 100 and the single device 200 can be implemented by software, or can be implemented by hardware. As an example, the implementation of the joint device 100 is introduced next. Similarly, the implementation of the single device 200 may refer to the implementation of the joint device 100 .

As an example of a software functional unit, the federation device 100 may include code running on a computing instance. The computing instance may be at least one of a physical host (computing device), a virtual machine, a container, and other computing devices. Further, the above computing device may be one or more. For example, federated appliance 100 may include code running on multiple hosts/virtual machines/containers. It should be noted that multiple hosts/virtual machines/containers used to run the application can be distributed in the same region (region) or in different regions. Multiple hosts/VMs/containers used to run the code can be distributed in the same availability zone (AZ) or in different AZs, each AZ including a data center or multiple geographical locations Close data center. Among them, usually a region can include multiple AZs.

Likewise, the multiple hosts/VMs/containers used to run the code can be distributed in the same virtual private cloud (VPC), or across multiple VPCs. Among them, usually a VPC is set up in a region. Cross-region communication between two VPCs in the same region or between VPCs in different regions requires a communication gateway in each VPC, and the interconnection between VPCs is realized through the communication gateway.

As an example of a hardware functional unit, the federation device 100 may include at least one computing device, such as a server. Alternatively, the association device 100 may also utilize an application-specific integrated circuit (application-specific integrated circuit). integrated circuit, ASIC), or programmable logic device (PLD), etc. The above-mentioned PLD can be implemented by a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.

Multiple computing devices included in the federation device 100 may be distributed in the same region or in different regions. Multiple computing devices included in the federation device 100 may be distributed in the same AZ or in different AZs. Similarly, multiple computing devices included in the federation device 100 may be distributed in the same VPC or in multiple VPCs. The plurality of computing devices may be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

It should be noted that in the above system, the joint device 100 and the unilateral device 200 are different devices as an example. In a possible scenario, the system does not need to have a separate joint device 100. The function of the joint device 100 is implemented by one unilateral device 200 among the plurality of unilateral devices 200. The unilateral network platform managed by the unilateral device 200 for realizing the function of the joint device 100 can be understood as a joint network platform. In the subsequent embodiments, this application only takes the joint device 100 as a device that is different from the single device 200 as an example for description. However, it should be understood that when one single device 200 among multiple single devices 200 implements this, In the case of combining the functions of the combined device 100 , the operations performed by the single device 200 for realizing the functions of the combined device 100 are the same as the operations performed by the combined device 100 .

The structure of the joint device 100 will be described below. As shown in Figure 2 , this application also provides a joint device 100. The joint device 100 includes a joint processing module 110 and a plurality of unilateral processing modules 120.

The joint processing module 110 implements management functions for the joint network platform. For example, the joint processing module 110 can process objects on the joint network platform according to the object processing operations performed by the object provider on the joint network platform, such as publishing objects on the joint network platform, completing object transactions, and revoking objects. object, or update object. For another example, the joint processing module 110 can also manage object providers registered to the joint network platform. For example, the joint processing module 110 can register to the joint network platform at the request of the object provider.

The plurality of unilateral processing modules 120 are respectively connected to the unilateral device 200 , and one unilateral processing module 120 is connected to one unilateral device 200 . For any single-party processing module 120, the single-party processing module 120 can communicate with the connected single-party device 200. The single-party processing module 120 cooperates with the connected single-party device 200 and can be based on the object provider or object acquirer on the joint network platform. The object processing operation is completed on the unilateral network platform managed by the unilateral device 200, such as object publishing, object transaction, object cancellation, and object update. For example, the unilateral processing module 120 may initiate a request message to the unilateral device 200 according to the instruction of the object provider to request the unilateral device 200 to publish the object, revoke the object or update the object on the unilateral network platform. For another example, when the unilateral device 200 detects the transaction operation of the object acquirer on the unilateral network platform, the unilateral processing module 120 can obtain the transaction information from the unilateral device 200 and feed the transaction information back to the object provider.

Among them, the joint processing module 110 and the unilateral processing module 120 can be implemented by software, or can be implemented by hardware. For details about the implementation manner of the joint processing module 110 and the unilateral processing module 120 and the implementation type of the joint device 100, please refer to the foregoing description, and will not be described again here.

It should be noted that in other embodiments, the joint processing module 110 can be used to perform any steps in the object processing method, and the unilateral processing module 120 can be used to perform any steps performed by the joint device 100 in the object processing method. Joint processing The steps that the module 110 and the unilateral processing module 120 are responsible for implementing can be specified as needed. The joint processing module 110 and the unilateral processing module 120 respectively implement any steps executed by the joint device 100 in the object processing method. All functions of the joint device 100 are realized.

The structure of the single-party device 200 is described below. As shown in FIG. 3 , the present application also provides a single-party device 200 . The single-party device 200 includes a platform management module 220 and a joint communication module 210 .

The platform management module 220 is responsible for the management of unilateral network platforms. For example, the platform management module 220 can process the object on the single-party network platform according to the processing operation of the object on the single-party network platform of the object provider or according to the request message received from the joint communication module 210, such as publishing on the single-party network platform. Object, complete object transaction, revoke object, or update object.

Due to the intervention of the joint device 100, the objects in the unilateral network platform managed by the platform management module 220 can be divided into two categories. One category is the objects published by the object provider on the unilateral network platform directly through the platform management module 220, and the other category is It is an object published by the object provider on a single network platform indirectly through the association device 100.

For the former type of object, the platform management module 220 can directly detect the processing operations performed by the object provider on the object. After the object is published to the single-party network platform, the platform management module 220 can also perform other processing operations on the object on the single-party network platform according to the processing operations performed by the object provider, such as revoking the object or updating the object. The platform management module 220 can also conduct object transactions on the single-party network platform according to the transaction operations of the object acquirer, and directly feed back transaction information (such as the number of objects traded, payment methods, fees paid, etc.) to the object provider.

For the latter type of object, the platform management module 220 needs to communicate through the joint device 100 to obtain information related to the object processing operations performed by the object provider (such as information about objects that need to be published, information about objects that need to be updated, information about objects that need to be revoked) object information, etc.). The platform management module 220 receives the request message sent by the unilateral processing module 120. The request message is used to request that the object be processed on the unilateral network platform. The platform management module 220 implements the object processing on the unilateral network platform according to the request message. The platform management module 220 can also publish objects, revoke objects, or update objects on the single-party network platform according to the request message. The platform management module 220 can also conduct object transactions on the single-party network platform according to the transaction operations of the object acquirer. The platform management module 220 can feed back transaction information (such as the number of objects traded, payment) to the single-party processing module 120 through the joint communication module 210. method, payment fees, etc.).

In the embodiments of this application, the processing of objects of the latter type is mainly described, and this application is not limited to the processing method of objects of the former type.

The joint communication module 210 is connected to the joint device 100 (such as the unilateral processing module 120) and communicates with the joint device 100. The joint communication module 210 can receive a request message from the single-party processing module 120, and the request message is used to request processing of the object on the single-party network platform. For example, the request message is used to request to publish an object, revoke an object, or update an object on a unilateral network platform. The joint communication module 210 can receive a request message from the single-party processing module 120, the request message being used to request processing of the object on the single-party network platform. For example, the request message is used to request to publish an object, revoke an object, or update an object on a unilateral network platform. When the platform management module 220 performs an object transaction on the single-party network platform as instructed by the object acquirer, the joint communication module 210 obtains the transaction information from the platform management module 220 and feeds back the transaction information to the current processing module.

Among them, the platform management module 220 and the joint communication module 210 can be implemented by software, or can be implemented by hardware. The implementation of the platform management module 220 and the joint communication module 210 is similar to the implementation of the joint processing module 110. For details, please refer to the foregoing content and will not be described again here.

The object processing method provided by the embodiment of the present application will be described below with reference to Figure 4. In the embodiment shown in Figure 4, the system includes three unilateral devices 200 as an example. For convenience of explanation, the three unilateral devices 200 respectively represents a single device 200A, a single device 200B, and a single device 200C. Among them, the single-party network platform managed by the single-party device 200A is network platform A. The unilateral network platform managed by the unilateral device 200B is network platform B. Unilateral installation 200C The unilateral network platform managed is network platform C. The method includes two parts. One part is a contracting process between the three unilateral devices 200 and the joint device 100 respectively. During the contracting process, the unilateral device 200 can provide policies and object processing rules to the object providing the unilateral device 200 . For details, refer to steps 401 to 407. The other part is for the object provider and the object acquirer to implement object processing on a single network platform through the joint device 100 . For details, refer to steps 408 to 421.

Step 401: The single-party device 200A (such as the joint communication module 210A) initiates a first contract request to the joint device 100 (such as the single-party processing module 120A connected to the single-party device 200A). The first contract request is used to request the network platform A to communicate with the joint network. Platform signing, the first signing request carries the object provision policy and object processing rules of the unilateral device 200A. Optionally, the first signing request may also carry some necessary certification information or identification information. For example, the qualification certification information of the unilateral device 200A or network platform A, the information of relevant contacts, and the identification of the unilateral device 200A or network platform A.

Step 402: After receiving the first contract request, the unilateral processing module 120A connected to the unilateral device 200A determines that it agrees with network platform A to establish a contracting relationship with the joint network platform, and then sends the third joint communication module 210A in the unilateral device 200A. A signing response, the first signing response is used to indicate agreement to join the joint network platform. The first signing response may also carry the identification code allocated by the unilateral processing module 120A to the unilateral device 200A, so that in the subsequent interaction process, the unilateral device 200A can carry the identification code in the interactive information to indicate to the unilateral processing module 120A This information comes from the single device 200A.

After receiving the first contracting request, the unilateral processing module 120A determines whether to agree to establish a contracting relationship between network platform A and the joint network platform based on the first contracting request. For example, the unilateral processing module 120 may agree to establish a contract relationship between network platform A and the joint network platform after confirming that the object provision policy and object processing rules of the unilateral device 200A meet the preset requirements. This application does not limit the specific content of the preset requirements. For example, the preset requirements can indicate that the object types involved in the object provision policy and object processing rules are consistent with the types of objects required by the joint network platform. For example, the object processing The payment method required when specifying transaction objects is consistent with the payment method required by the United Network Platform. For another example, the unilateral processing module 120 may agree that the network platform A establishes a contract relationship with the joint network platform after confirming that the qualification certification information of the unilateral device 200A or the network platform A is true and valid. For another example, the unilateral processing module 120 may agree that the network platform A establishes a contract relationship with the joint network platform after confirming that the identity of the unilateral device 200A or the network platform A is valid.

In steps 401 to 402, for example, the single device 200A actively requests the joint device 100 to join the joint network platform. In practical applications, the joint device 100 is allowed to request to initiate a contract invitation to the single device 200A. For specific implementation, please refer to steps 403 to 402. 405.

Step 403: The joint device 100 (such as the single-party processing module 120B connected to the single-party device 200B) initiates a contract invitation to the single-party device 200B (such as the joint communication module 210B). The contract invitation is used to invite network platform B to establish a contract connection with the joint network platform. . The contract invitation may carry some necessary certification information related to the joint device 100. For example, the qualification certification information of the joint device 100 or the joint network platform. Optionally, the contract invitation can also carry requirements that need to be met to join the joint network platform.

Step 404: The unilateral device 200B (such as the joint communication module 210B) initiates a second signing request to the joint device 100. The second signing request is used to request the network platform B to establish a contracting relationship with the joint network platform. The second signing request carries the unilateral The object provision policy of device 200B, and object processing rules. Optionally, the second signing request may also carry some necessary certification information or identification information. For example, the qualification certification information of the unilateral device 200B or network platform B, and the identification of the unilateral device 200B or network platform B.

Step 405: After receiving the second signing request, the unilateral processing module 120B connected to the unilateral device 200B determines that network platform B is allowed to join the joint network platform, and sends a second signing response to the joint communication module 210B in the unilateral device 200B. , the second signing response is used to indicate that the joint network platform agrees to establish a signing relationship with network platform B.

Similarly, the single-party device 200C and the joint device 100 can sign a contract using either of the above two methods. For details, refer to steps 406 to 407.

Step 406: The single-party device 200C (such as the joint communication module 210C) initiates a third contract request to the joint device 100 (such as the single-party processing module 120 connected to the single-party device 200C). The third contract request is used to request the network platform C to communicate with the joint network. The platform establishes a contract connection, and the third contract request carries the object provision policy and object processing rules of the unilateral device 200C. Optionally, the third contract signing request can also carry some necessary certification information or identification information. For example, the qualification certification information of the single-party device 200C or network platform A, and the identification of the single-party device 200C or network platform A.

Step 407: After receiving the third contract request, the unilateral processing module 120C connected to the unilateral device 200C determines that it agrees with network platform C to establish a contract connection with the joint network platform, and then sends the third contract to the joint communication module 210C in the unilateral device 200C. The third signing response is used to indicate that network platform C agrees to establish a signing relationship with the joint network platform.

At this point, the contracting process between the three unilateral devices 200 and the joint device 100 is completed. Through this contracting process, the single-party device 200 and the joint device 100 establish mutual trust. The single-party device 200 adds the managed single-party network platform to the joint network platform, allowing objects in the joint network platform to be published to the single-party network platform. The federated device 100 can, on behalf of the unilateral device 200, audit object providers that need to register or process objects based on the object provision policy of the unilateral device 200, and audit processing operations for processing based on the object processing rules of the unilateral device 200.

After the single-party device 200 completes the contract with the joint device 100, the object provider and the object acquisition facilitator can process the objects on the single-party network platform through the joint device 100.

For the object provider, the object provider can apply to register in the joint network platform to request permission to process objects on the joint network platform. The object provider can also obtain permission from the joint device 100 to process objects on a single network platform. When the federation device 100 detects a registration operation for the federation network platform, it may agree or reject the registration. When the association device 100 detects a registration operation for a unilateral network platform, it may also agree or deny the permission acquisition request.

After the joint device 100 agrees to register for the single-party network platform, the object provider can process the object on the joint network platform, and can also process the object on the single-party network platform through the joint device 100 . The joint device 100 sends the request message to the single-party device 200. After receiving the request message, the single-party device 200 can process the object on the single-party network platform according to the request message.

The following describes the processing process of this object with specific steps:

Step 408: The federation device 100 (such as the federation processing module 110) detects the object provider's registration operation for the federation network platform.

The joint device 100 can provide a client of the joint trading platform to the object provider. The client can be understood as client software or client equipment. The object provider registers on the United Network Trading Platform through the client.

As shown in FIG. 5A , it is a registration interface provided to users by the joint processing module 110 in the embodiment of the present application. In this registration interface, some information that needs to be provided by the object provider is displayed. In Figure 5A, the object provider's information includes the object provider's name, object provider's identification, etc.

Step 409: If the joint processing module 110 determines that the object provider complies with the object providing policy of the joint device 100, grant permission to process the object on the joint network platform. For example, the joint processing module 110 sends a success message to the object provider to notify the joint network platform that the registration is successful.

The joint processing module 110 may obtain the object provider's information according to the registration request, and determine whether the object providing policy of the joint device 100 is complied with. If the object provider's information complies with the object provision policy of the association device 100, the association processing module 110 may send a success message to the object provider. If the object provider's information does not comply with the object provision policy of the joint device 100, such as the object provider's information is missing or invalid, the joint processing module 110 sends a failure message to the object provider to notify the joint network platform that the registration failed. The message may also carry the reason for the failure to register for the federated network platform.

Step 410: The joint device 100 (such as the joint processing module 110) receives a registration operation for a single network platform executed on the joint network platform. The registration operation is used to request permission to process objects on a single network platform. The joint device 100 can Obtain the object provider information through this registration operation.

The registration operation for a single network platform performed by the object provider on the joint network platform is similar to the registration operation for the joint network platform initiated by the object provider on the joint network platform. For details, please refer to the above description, which will not be discussed here. Again.

As shown in Figure 5B, it is another registration interface provided to users by the joint processing module 110 in the embodiment of the present application. In this registration interface, options for multiple unilateral network platforms are displayed (such as displaying network platform A, network platform B , network platform C) and some information that the object provider needs to provide. In FIG. 5B , the information of the object provider is similar to the information of the object provider mentioned in the foregoing description. It should be noted that due to the differences in network platforms, there may be certain differences in the information required by object providers to settle in or join different network platforms. In Figure 5B, the information that the object provider needs to provide can be supplementary information. The supplementary information is different information between the information that needs to be provided by the object provider that joins the joint network platform and the information that needs to be provided by the object provider that joins the unilateral network platform. . If the information required by the object provider to join the joint network platform is the same as the information required by the object provider to join the single-party network platform, then there is no need for the user to enter information in Figure 5B, and only the user needs to check the single-party network that he wants to join. platform.

The object provider can fill in the relevant information in this interface and check the unilateral network platform that needs to obtain permission to process the object.

Step 411: When the joint processing module 110 determines that the object provider complies with the object provision policy of the unilateral device 200, it notifies the object provider that the registration for the unilateral network platform is successful, and grants the object provider permission to process objects on the unilateral network platform.

The joint processing module 110 can determine whether the object provision policy of the unilateral device 200 is consistent with the registration operation for the unilateral network platform. If it is consistent, notify the object provider that the registration for the unilateral network platform is successful. If not, notify the object provider that the registration for the unilateral network platform has failed. , and can also notify the reason for the failure of registration on the unilateral network platform.

In steps 408 to 411, the object provider successively performs the registration operation on the joint network platform for the joint network platform and the unilateral network platform for illustration. In practical applications, it is not limited to the joint network platform for the joint network platform. The platform and the order in which each party's network platform performs registration operations. For example, the joint processing module 110 allows registration operations for the joint network platform and the unilateral network platform to be simultaneously performed on the joint network platform.

Referring to Figure 5C, another registration interface provided for users according to the embodiment of the present application is provided. In the registration interface, the user is prompted whether he or she needs to join the unilateral network platform immediately after settling in the joint network platform, and the options of each unilateral network platform are displayed. The registration interface can also display some information that the object provider needs to provide.

The object provider can choose to join the unilateral network platform immediately in the request configuration interface and check the box to obtain the processing The unilateral network platform to which the management object permissions belong, fill in the relevant information in the interface, click OK, and initiate a settlement request and a permission acquisition request at the same time.

After settling in the joint network platform and joining the unilateral network platform, the object provider can process objects on the joint network platform and the unilateral network platform.

(1) Object release.

Step 412: The joint processing module 110 obtains the object to be published provided by the object provider, and determines the unilateral network platform on which the object needs to be published.

The object provider can be deployed on the client of the object provider through the joint network platform, and perform an object publishing operation on the joint network platform. The joint processing module 110 detects the object publishing operation, and through the object publishing operation, it can be determined that the object provider needs to publish Object information. The object publishing operation may also indicate whether the joint processing module 110 needs to publish the object to a single network platform. If the object provider has previously obtained permission to process objects on multiple single-party network platforms, the object publishing operation may also indicate the single-party network platform to which the joint processing module 110 needs to release the object. That is, the object provider may provide designated information that indicates the unilateral network platform executed by the object provider.

In the embodiment of this application, the specific content included in the object's information is not limited. The object's information may include the following information:

Object attribute information includes some or all of the following:

The identifier of the object (the identifier is used to uniquely identify the object), the name of the object, the identifier of the object provider that provides the object (the identifier is used to uniquely identify the object provider), the name of the object provider, the object's Description information (used to describe the object, which can be presented in the form of text, images, or uniform resource locator (URL) links), object usage environment (used to describe the environment in which the object is used , for example, the object is a software product, and the usage environment of the object is used to indicate the operating system for which the software product is applicable), the type of object, the number of objects, and the label of the object.

Object transaction conditions include some or all of the following:

The payment method of the object, the payment fee, and the method of performance of the transaction after the object is traded (the method of performance describes the method of providing the object to the object acquirer, such as the method of fulfillment indicating that the object is provided to the object acquirer by sending express mail ).

As shown in Figure 6, it is the object publishing configuration interface provided to users by the joint processing module 110 in the embodiment of the present application. The object publishing configuration interface displays object information that the object provider needs to provide when publishing objects. The object release configuration interface also displays options for multiple unilateral network platforms (such as displaying network platform A, network platform B, and network platform C).

In Figure 6, the object information includes the object's identifier, the object's name, the name of the object provider, the object's image, the object's category, the object's description information, the object's label, and other attribute information related to the object. The object's information also includes the object's transaction conditions, which include the object's payment method and the fees that the transaction object needs to pay.

The object provider can enter the object information and check the unilateral network platform in the object publishing configuration interface.

After acquiring the object to be published, the joint processing module 110 first determines whether the publishing operation for the object complies with the object processing rules of the joint device 100 (such as the object publishing rules in the object processing rules). When the publishing operation complies with the object processing rules of the federation device 100, the object is published to the federation network. platform, that is, adding the object's information to the joint network platform.

If the object provider does not indicate whether the joint processing module 110 needs to publish the object to a unilateral network platform, or the object provider instructs the joint processing module 110 to publish the object to a unilateral network platform, but does not specify a specific unilateral network platform.

The joint processing module 110 can determine the unilateral network platform on which the object can be published based on the object processing rules of each unilateral device 200 (such as the object publishing rules in the object processing rules). For example, the joint processing module 110 can determine by itself whether the publishing operation for the object complies with the object processing rules of the unilateral device 200A, the object processing rules of the unilateral device 200B, and the object processing rules of the unilateral device 200C. If the publishing operation for the object complies with the object processing rules of the unilateral device 200A, the object can be published to the network platform A. If the publishing operation for the object conforms to the object processing rules of the unilateral device 200B, the object can be published to the network. In platform B, if the publishing operation for the object complies with the object processing rules of the unilateral device 200C, the object can be published to network platform C. If the publishing operations for the object do not comply with the object processing rules of each unilateral device 200, the joint processing module 110 does not need to publish the object to any unilateral network platform.

The joint processing module 110 can inform the object provider of the network platforms on which the object can be published. If the object cannot be published on any network platform, the joint processing module 110 can also inform the object provider of the reason why the object cannot be published on the network platform.

If the object provider instructs the joint processing module 110 to publish the object to a single-party network platform, and the single-party network platform is designated.

The joint processing module 110 can determine whether the object can be published to the designated unilateral network platform according to the object processing rules of the designated unilateral device 200 (such as the object publishing rules in the object processing rules). That is, the joint processing module 110 determines Whether the publishing operation for the object complies with the object processing rules of the specified unilateral device 200 . For example, if the specified unilateral network platform is network platform A, the joint processing module 110 may determine whether the publishing operation for the object complies with the object processing rules of the unilateral device 200A. If the publishing operation for the object complies with the object processing rules of the unilateral device 200A, the joint processing module 110 determines that the object can be published to network platform A. If the publishing operation for the object does not comply with the object processing rules of the unilateral device 200A, the joint processing module 110 Module 110 determines that the object cannot be published to network platform A. The joint processing module 110 can inform the object provider that the object cannot be published to the designated unilateral network platform, and can also inform the object provider of the reason why the object cannot be published to the designated unilateral network platform.

Assume that the unilateral network platforms to be published by the object determined by the joint processing module 110 are network platform A, network platform B, and network platform C. Here, the joint device 100 interacts with the unilateral device 200A by publishing the object to network platform A as an example. Note that the method of publishing the object to network platform B and network platform C is similar to the method of publishing the object to network platform A, and will not be described again here.

Step 413: The unilateral processing module 120A connected to the unilateral device 200A initiates a first request message to the joint communication module 210 in the unilateral device 200A. The first request message is used to request the network platform A to publish the object. The first request message carries information about the object. Optionally, the first request message may also include the information of the object provider (these information may be the messages provided by the object provider when applying to join the network platform), the object display page, and the object provider display page, and release time information.

The object display page is generated by the joint processing module 110. The object display page is used to display the page of the object, and the page can display the information of the object. The object display page may be a page on which the joint processing module 110 displays the object in the joint network platform.

The object provider introduction page is generated by the joint processing module 110. The object provider introduction page is used to introduce the object provider's page, and the page can display the object provider's information. The object provider introduction page may be a page where the joint processing module 110 introduces the object provider in the joint network platform.

The release time information is used to indicate the time when the object provider requests to release the object, that is, the time when the object provider performs the object release operation.

The first request message may carry the object display page and the object provider display page in the form of network links.

Step 414: The platform management module 220A in the unilateral device 200A obtains the information of the object in the first request message, and publishes the object to the managed network platform A, that is, displays the object in the network platform A. information.

In step 414, after obtaining the information of the object, the platform management module 220 may directly publish the object to the managed network platform A, or may perform a secondary confirmation based on the information of the object, that is, once again determine the target for the object. Whether the publishing operation of the object complies with the object processing rules of the unilateral device 200A. When the platform management module 220 determines that the publishing operation of the object complies with the object processing rules of the unilateral device 200A, the platform management module 220 publishes the object to the managed network platform A. , that is, the information of the object is displayed in the network platform A. When the platform management module 220 determines that the publishing operation for the object does not comply with the object processing rules of the unilateral device 200A, the platform management module 220 can communicate with the unilateral device 200A. The connected unilateral processing module 120 sends a first rejection response to refuse to publish the object to network platform A.

When the platform management module 220A displays the information of the object in the network platform A, the platform management module 220A can use the information of the object to generate a display page to present on the network platform A, or it can also use the information carried in the first request message to generate a display page. As the display page, the object display page is directly presented in the network platform A. The object display page carried in the first request message can also be processed, and the processed object display page is presented in the network platform A.

The platform management module 220A can also display the object provider of the object in the network platform A. The platform management module 220A can use the object provider's information to generate a display page to present in the network platform A. It can also display the first The object provider introduction page carried in the request message is used as the display page and is directly presented on the network platform A. The object provider introduction page carried in the first request message can also be processed, and the processed object provider The introduction page is presented in this network platform A.

Step 415: The platform management module 220A sends a first success response to the unilateral processing module 120A connected to the unilateral device 200A. The first success response is used to indicate that the object is successfully published in network platform A.

After receiving the first successful response, the unilateral processing module 120A may notify the object provider that the object is successfully published in network platform A. The embodiment of the present application does not limit the way in which the unilateral processing module 120 notifies the object provider that the object is successfully published in network platform A. For example, the unilateral processing module 120 can notify the object provider that the object is successfully published on network platform A by sending an email, a text message, or an application message.

(2) Object transactions.

Assume that the object has been published to network platform A, network platform B, and network platform C. The object acquirer can obtain the object in network platform A, network platform B, and network platform C to implement object transactions. The object acquirer can The network platform A obtains the object to implement the object transaction as an example. The object acquirer obtains the object on the network platform B or network platform C to implement the object transaction. The object acquirer obtains the object on the network platform A to implement the object transaction. The method is similar and will not be described again here.

Step 416: The platform management module 220A in the unilateral device 200A detects the object acquisition party's transaction operation on the object, and determines whether the transaction operation on the object complies with the object processing rules of the unilateral device 200A (such as the object processing Object Transaction Rules in Rules).

The object acquirer can view the information of the object in the network platform A through the client of the single-party network platform deployed on the object acquirer side, and can also trade the object on the network platform. For example, the object acquirer can add the object to Shopping cart, pay the appropriate fee to request the object. The platform management module 220 can detect the transaction operation for the object and determine whether the transaction operation for the object complies with the object processing rules of the unilateral device 200A. For example, the platform management module 220 can determine whether the transaction operation for the object complies with the requirements of the object transaction rules. Trading conditions are the same.

Step 417: When the platform management module 220A determines that the transaction operation for the object complies with the object processing rules of the unilateral device 200A, the joint communication module 210A sends the transaction information to the unilateral processing module 120A connected to the unilateral device 200A. It is information related to the transaction operation for the object, such as transaction time, objects traded, number of objects traded, fees paid and other information.

Step 418: After obtaining the transaction information, the unilateral processing module 120A connected to the unilateral device 200A can feed back the transaction information to the object provider.

The embodiment of the present application does not limit the way in which the unilateral processing module 120A feeds back the transaction information to the object provider. For example, the unilateral processing module 120A sends transaction information to the object provider through the client on the object provider side. For another example, the unilateral processing module 120A can feedback the transaction information to the object provider side by sending emails, text messages, etc.

After the object provider obtains the transaction information, the object provider can also perform the transaction and provide the object to the object acquirer. For example, the object provider can provide the object by sending express mail or by providing services. Give the object getter. The object provider can feed back transaction fulfillment information to the unilateral processing module 120A. Transaction fulfillment information is used to prove that the object provider has fulfilled the transaction or is fulfilling the transaction. For example, the transaction fulfillment information can be logistics information for express shipments, or execution information for services (mainly for virtual products such as services and recharges).

After obtaining the transaction fulfillment information, the unilateral processing module 120A can provide the transaction fulfillment information to the object acquirer.

(3) Object update.

Step 419: The joint processing module 110 detects the object update operation performed by the object provider on the joint network platform, and obtains the object that needs to be updated and the information that needs to be updated provided by the object provider.

The object provider can perform an update operation on the object on the joint network platform through a client deployed on the joint network platform on the object provider side, so as to provide the joint processing module 110 with the object that needs to be updated, and the object that needs to be updated. information. Optionally, the object provider can also specify the network platform that needs to update the object. For example, the object provider can only instruct the object in the joint network platform to be updated or only instruct the object in one or more unilateral network platforms to be updated, and For example, the object provider may instruct objects in the joint network platform and the unilateral network platform to be updated simultaneously.

For example, when the object provider needs to update the quantity of the object, the object provider can also specify that it only needs to update the quantity of the object in the federated network platform.

When the object provider needs to update the name of the object, the object provider can instruct the object in the joint network platform and the unilateral network platform to be updated synchronously.

When the object provider needs to limit the number of transactions for objects in one or more single-party network platforms, the object provider can only instruct to update the number of objects in one or more single-party network platforms.

After the joint processing module 110 obtains the object that needs to be updated and the information about the object that needs to be updated, if the object provider does not instruct to specify the network platform that needs to be updated, or instructs to synchronously update the objects in the joint network platform and the unilateral network platform .

The joint processing module 110 can determine the needs based on the object processing rules of each unilateral device 200 (such as the object update rules in the object processing rules) and the object processing rules of the joint device 100 (such as the object update rules in the object processing rules). Updated web platform. For example, the joint processing module 110 can determine by itself whether the update operation for the object complies with the object processing rules of the unilateral device 200A, the object processing rules of the unilateral device 200B, the object processing rules of the unilateral device 200C, and the object processing rules of the joint device 100. If the update operation for the object complies with the object processing rules of the unilateral device 200A, then network platform A is the network platform that needs to update the object. If the update operation for the object complies with the object processing rules of the unilateral device 200B, then network platform B is The network platform that needs to update the object. If the update operation for the object complies with the object processing rules of the unilateral device 200C, the network platform C is the network platform that needs to update the object. If the update operation for the object complies with the object processing rules of the joint device 100, the joint network platform is the network platform that needs to update the object. If the update operations on the object do not comply with any object processing rules, the joint processing module 110 cannot update the object on any network platform. The joint processing module 110 can notify the object provider that the object cannot be updated. The joint processing module 110 can also Informs the object provider why the object cannot be updated.

If the object provider specifies the network platform that needs to update the object.

The joint processing module 110 determines whether the object can be updated on a unilateral network platform according to the object processing rules of the specified network platform (such as the object publishing rules in the object processing rules). That is, the joint processing module 110 determines whether the object can be updated on the unilateral network platform. Whether the update operation complies with the specified object processing rules of the unilateral device 200. For example, if the specified unilateral network platform is network platform B, the joint processing module 110 may determine whether the update operation for the object complies with the object processing rules of the unilateral device 200B. If the update operation for the object complies with the object processing rules of the unilateral device 200B, the joint processing module 110 determines that the object can be updated in network platform B. If the update operation for the object does not comply with the object processing rules of the unilateral device 200B, the joint processing module 110 Module 110 determines that the object cannot be published to network platform B. The joint processing module 110 can inform the object provider that the object cannot be published to the designated unilateral network platform, and can also inform the object provider of the reason why the object cannot be published to the designated unilateral network platform. The processing method of the joint processing module 110 when the object provider specifies a joint network platform is similar to the processing method of the joint processing module 110 when the object provider specifies a unilateral network platform, and will not be described again here.

The following takes the interaction between the joint device 100 and the single device 200B to update objects in network platform B as an example. The methods of updating objects in network platform A and network platform C are similar to the methods of updating objects in network platform B. Herein, No further details will be given.

Step 420: The unilateral processing module 120B connected to the unilateral device 200B initiates a second request message to the joint communication module 210B in the unilateral device 200B. The second request message is used to request an update object in the network platform B. The second request message carries the object that needs to be updated and the information of the object that needs to be updated. For example, the second request message may request to update the name of the object Q, and the second request message carries the updated name of the object Q.

Step 421: The platform management module 220B in the unilateral device 200B updates the information of the object in the network platform B according to the second request message. For example, the platform management module 220B may carry the name of the object Q in the network platform as the name carried in the second request message.

In step 421, after determining the object that needs to be updated and the information that needs to be updated, the platform management module 220B can directly update the information of the object in network platform B according to the second request message, or it can also update the information of the object according to the object that needs to be updated and the information that needs to be updated. The updated information is confirmed twice, that is, it is determined again whether the update operation for the object complies with the object processing rules of the unilateral device 200B. The platform management module 220B determines that the update operation for the object complies with the object processing rules of the unilateral device 200B. Next, in network platform B, the object is updated according to the second request message. Information, when the platform management module 220B determines that the update operation for the object does not comply with the object processing rules of the unilateral device 200B, the platform management module 220B may send a second rejection response to the unilateral processing module 120B connected to the unilateral device 200B to Deny network platform B to update the object.

Step 422: The platform management module 220B sends a second success response to the unilateral processing module 120B connected to the unilateral device 200B. The second success response is used to indicate that the object is successfully updated in network platform B.

After receiving the second successful response, the unilateral processing module 120B may notify the object provider that the object is published and updated successfully in network platform B. The embodiment of the present application does not limit the way in which the unilateral processing module 120 notifies the object provider that the object is published and updated successfully in network platform B. For example, the unilateral processing module 120 can notify the object provider that the object is published and updated successfully in network platform B by sending an email, a text message, or a prompt message from the client.

(4) Object cancellation.

Step 423: The joint processing module 110 detects the object provider's revocation operation on the object on the joint network platform, and obtains the objects provided by the object provider that need to be revoked.

The object provider can perform a revocation operation on the object on the joint network platform through the client of the joint network platform, and provide the object that needs to be revoked to the joint processing module 110 . Optionally, the object provider can also specify the network platform that needs to revoke the object. For example, the object provider can only instruct the revoking of objects in the joint network platform or only instruct the revoking of objects in one or more unilateral network platforms, and For example, the object provider may instruct the simultaneous withdrawal of objects in the joint network platform and the unilateral network platform.

After acquiring the object that needs to be revoked, the joint processing module 110 may instruct the object provider to simultaneously revoke the object in the joint network platform and the unilateral network platform if the object provider has not instructed to specify the network platform that needs to be revoked.

The joint processing module 110 may determine that revocation is required based on the object processing rules of each unilateral device 200 (such as the object cancellation rules in the object processing rules) and the object processing rules of the joint device 100 (such as the object cancellation rules in the object processing rules). The object's network platform. For example, the joint processing module 110 may determine whether the undo operation for the object complies with the object processing rules of the unilateral device 200A, the object processing rules of the unilateral device 200B, the object processing rules of the unilateral device 200C, and the object processing rules of the joint device 100 . If the revocation operation for the object complies with the object processing rules of the unilateral device 200A, then network platform A is the network platform that needs to revoke the object. If the revocation operation for the object complies with the object processing rules of the unilateral device 200B, then network platform B is The network platform that needs to revoke the object, if the revoke operation for the object complies with the object processing rules of the unilateral device 200C, then the network platform C is the network platform that needs to revoke the object. If the cancellation operation for the object complies with the object processing rules of the joint device 100, the joint network platform is the network platform that needs to cancel the object. If the revocation operations for the object do not comply with any object processing rules, the joint processing module 110 cannot revoke the object on any network platform. The joint processing module 110 can notify the object provider that the object cannot be revoked. The joint processing module 110 can also Informs the object provider why the object cannot be revoked.

If the object provider specifies the network platform that needs to revoke the object.

If the object provider specifies a unilateral network platform, the joint processing module 110 determines whether the object can be revoked on the unilateral network platform according to the object processing rules of the designated unilateral device 200 (such as the object publishing rules in the object processing rules), That is, the joint processing module 110 determines whether the undo operation for the object complies with the specified object processing rules of the unilateral device 200 . For example, if the designated unilateral network platform is network platform C, the joint processing module 110 may determine whether the undo operation for the object complies with the object processing rules of the unilateral device 200C. If the revocation operation for the object complies with the object processing rules of the unilateral device 200C, the joint processing module 110 determines that the object can be revoked in the network platform C. If the revocation operation for the object does not comply with the object processing rules of the unilateral device 200C, The joint processing module 110 determines that the object cannot be published to the network platform C. The joint processing module 110 can inform the object provider that the object cannot be published to the designated unilateral network platform, and can also inform the object provider of the reason why the object cannot be published to the designated unilateral network platform. The processing method of the joint processing module 110 when the object provider specifies a joint network platform is similar to the processing method of the joint processing module 110 when the object provider specifies a unilateral network platform, and will not be described again here.

The following takes the interaction between the joint device 100 and the single device 200C to revoke an object in network platform C as an example. The method of revoking an object in network platform A and network platform B is similar to the method of revoking an object in network platform C. Herein, No further details will be given.

Step 424: The unilateral processing module 120C connected to the unilateral device 200C initiates a third request message to the joint communication module 210C in the unilateral device 200C. The third request message is used to request the network platform C to revoke the object. The third request message carries the object that needs to be revoked.

Step 425: The platform management module 220C in the unilateral device 200C revokes the object in the network platform C according to the third request message. That is to say, the platform management module 220C can delete or hide the information of the object on the network platform C.

In step 425, after determining the object that needs to be revoked, the platform management module 220C can directly revoke the object in network platform C according to the third request message, or can also perform a secondary confirmation based on the object that needs to be revoked. , that is, it is determined again whether the undo operation for the object complies with the object processing rules of the unilateral device 200C. When the platform management module 220C determines that the undo operation for the object complies with the object processing rules of the unilateral device 200C, in the network platform C The object is revoked in the network platform C according to the third request message. When the platform management module 220C determines that the object does not comply with the object processing rules of the unilateral device 200C, the platform management module 220C can process it to the unilateral device connected to the unilateral device 200C. Module 120C sends a third rejection response to refuse to revoke the object on network platform C.

Step 426: The joint communication module 210C sends a third success response to the unilateral processing module 120C connected to the unilateral device 200C. The third success response is used to indicate that the object is successfully revoked in the network platform C.

After receiving the third successful response, the unilateral processing module 120C may notify the object provider that the object is successfully revoked in the network platform C. The embodiment of the present application does not limit the way in which the unilateral processing module 120C notifies the object provider that the object is successfully revoked in the network platform C. For example, the unilateral processing module 120C can notify the object provider that the object has been successfully revoked in network platform C by sending emails, text messages, and prompt messages from the client.

The present application also provides a computing device 700. As shown in Figure 7, computing device 700 includes: bus 701, processor 702, memory 703, and communication interface 704. The processor 702, the memory 703 and the communication interface 704 communicate through the bus 701. Computing device 700 may be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in the computing device 700.

The bus 701 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one line is used in Figure 7, but it does not mean that there is only one bus or one type of bus. Bus 701 may include a path that carries information between various components of computing device 700 (eg, memory 703, processor 702, communication interface 704).

The processor 702 may include a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP) or a digital signal processor (DSP). any one or more of them.

Memory 703 may include volatile memory, such as random access memory (RAM). The processor 702 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD) or solid state drive (SSD). drive, SSD).

The memory 703 stores executable program code, and the processor 702 executes the executable program code to respectively realize the functions of the aforementioned joint management module 110 and the unilateral management module 120, thereby realizing the object processing method. That is, the memory 703 stores computer program instructions for executing the object processing method.

Alternatively, executable code is stored in the memory 703, and the processor 702 executes the executable code to implement the functions of the aforementioned association device 100, thereby implementing the object processing method. That is, the memory 703 stores computer program instructions for executing the object blowing method.

The communication interface 704 uses transceiver modules such as, but not limited to, network interface cards and transceivers to implement communication between the computing device 700 and other devices or communication networks.

It should be understood that, although not shown, the computing device shown in FIG. 7 can also be used to implement the functions of a single-party management device. The memory 703 in the computing device stores executable program code, and the processor 702 executes the executable program code to realize the functions of the aforementioned joint communication module 210 and the platform management module 220 respectively, thereby realizing the unilateral method in the aforementioned object processing method. Operations performed by device 200. That is, the memory 703 stores computer program instructions for executing the unilateral device 200 in the object processing method.

Alternatively, executable code is stored in the memory 703, and the processor 702 executes the executable code to respectively realize the functions of the aforementioned unilateral device 200, thereby realizing the operations performed by the unilateral device 200 in the object processing method. That is, the memory 703 stores instructions for executing the single device 200 in the target method.

An embodiment of the present application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device may be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device may also be a terminal device such as a desktop computer, a laptop computer, or a smartphone.

As shown in FIG. 8 , the computing device cluster includes at least one computing device 700 . The same instructions for executing the application deployment method may be stored in the memory 703 of one or more computing devices 700 in the computing device cluster.

In some possible implementations, the memory 703 of one or more computing devices 700 in the computing device cluster may also store part of the instructions for executing the application deployment method. In other words, a combination of one or more computing devices 700 may collectively execute instructions for performing an application deployment method.

It should be noted that the memories 703 in different computing devices 700 in the computing device cluster can store different instructions, respectively used to execute part of the functions of the joint device 100 or the single device 200 . That is, the instructions stored in the memory 703 in different computing devices 700 can implement the functions of one or more modules in the joint management module 110 and the unilateral management module 120, or the instructions stored in the memories 703 in different computing devices 700 can Realize the functions of one or more modules among the joint management module 110, the unilateral management module 120, the joint communication module 210, and the platform management module 220.

In some possible implementations, one or more computing devices in a cluster of computing devices may be connected through a network. Wherein, the network may be a wide area network or a local area network, etc.

An embodiment of the present application also provides a computer program product containing instructions. The computer program product may be A software or program product that contains instructions that can be run on a computing device or stored on any available medium. The computer program product, when executed on at least one computing device, causes at least one computing device to execute an application deployment method, or an application deployment method.

An embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium may be any available medium that a computing device can store or a data storage device such as a data center that contains one or more available media. The available media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media (eg, solid state drive), etc. The computer-readable storage medium includes instructions that instruct the computing device to perform an application deployment method, or instruct the computing device to perform an application deployment method.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that it can still be used Modifications are made to the technical solutions described in the foregoing embodiments, or equivalent substitutions are made to some of the technical features; however, these modifications or substitutions do not cause the essence of the corresponding technical solutions to depart from the protection scope of the technical solutions of the various embodiments of the present invention.

Claims

An object processing method, characterized in that the method is executed by a computing device, and the method includes:

Receive the registration operation performed by the user on the joint network platform, and grant the user permission to process objects on the joint network platform;

Detect the object publishing operation performed by the user on the joint network platform, and obtain the information provided by the user on the object that needs to be published;

Publish the object's information on the joint network platform, and select a target network platform from multiple network platforms contracted with the joint network platform;

Publish the object's information in the target network platform;

The user is notified that the object is successfully published on the joint network platform and the target network platform.
The method of claim 1, further comprising:

Establish a contract relationship between the joint network platform and the multiple network platforms, and obtain the object provision policies and object processing rules of the multiple network platforms. The object provision policy is used to describe the constraints that need to be followed to provide the object. Policy, the object processing rules are used to describe the constraint rules that need to be followed for the processing operations of the object.
The method of claim 2, wherein the object processing rules include object publishing rules, and the object publishing rules describe constraint rules that need to be followed for the publishing operation of the object;

The selection of a target network platform from multiple network platforms contracted with the joint network platform includes:

Obtain information about the user;

The target network platform is selected from the plurality of network platforms based on the user's information, the object provision policies of the plurality of network platforms, and the object processing rules, wherein the user meets the object provision of the target network platform Policy, the object publishing operation complies with the object processing rules of the target network platform.
The method of claim 1, wherein selecting a target network platform from multiple network platforms contracted with the joint network platform includes:

Obtain designated information sent by the user, where the designated information indicates the target network platform.
The method according to any one of claims 1 to 4, characterized in that the method further includes:

Obtain the transaction information of the object from the target network platform, and the transaction information of the object describes the transaction operation performed on the object on the target network platform;

Feedback the transaction information of the object to the user.
The method according to any one of claims 1 to 5, characterized in that the object processing rules include object update rules, the object update rules describe constraint rules that need to be followed for the update operation of the object, and the method Also includes:

Detect the update operation performed by the user on the object on the joint network platform, and obtain the information provided by the user that the object needs to be updated in the target network platform according to the update operation;

Send an update request to the target network platform, where the update request is used to request to update the object in the target network platform, where the update request includes the information that needs to be updated.
The method according to any one of claims 1 to 6, characterized in that the object processing rules include object cancellation rules, and the object cancellation rules describe constraint rules that need to be followed for the cancellation operation of the object. The method Also includes:

Detect the undo operation performed by the user on the object on the joint network platform, and determine according to the detection operation The object that the user needs to revoke on the target network platform;

A revocation request is sent to the target network platform, where the revocation request is used to request that the object be revoked in the target network platform.
A combination device, characterized in that the combination device includes:

A joint processing module, configured to receive registration operations performed by users on the joint network platform, grant permissions to the users to process objects on the joint network platform, and detect object release operations performed by users on the joint network platform, Obtain the information of the object that needs to be published provided by the user, and publish the information of the object on the joint network platform;

A unilateral processing module, configured to select a target network platform from multiple network platforms contracted with the joint network platform; publish the object's information in the target network platform; and notify the user that the object is in the joint network platform. Successfully published on the network platform and the target network platform.
The device according to claim 8, characterized in that the unilateral processing module is also used to:

Establish a contract relationship between the joint network platform and the multiple network platforms, and obtain the object provision policies and object processing rules of the multiple network platforms. The object provision policy is used to describe the constraints that need to be followed to provide the objects. Policy, the object processing rules are used to describe the constraint rules that need to be followed for the processing operations of the object.
The device of claim 8, wherein the object processing rules include object publishing rules, and the object publishing rules describe constraint rules that need to be followed for the publishing operation of the object;

The unilateral processing module selects a target network platform from multiple network platforms contracted with the joint network platform for:

Obtain information about the user;

The target network platform is selected from the plurality of network platforms based on the user's information, the object provision policies of the plurality of network platforms, and the object processing rules, wherein the user meets the object provision of the target network platform Policy, the object publishing operation complies with the object processing rules of the target network platform.
The device of claim 8, wherein the unilateral processing module is configured to: when multiple network platforms contracted with the joint network platform select a target network platform:

Obtain designated information sent by the user, where the designated information indicates the target network platform.
The device according to any one of claims 8-11, characterized in that the unilateral processing module is also used for:

Obtain the transaction information of the object from the target network platform, and the transaction information of the object describes the transaction operation performed on the object on the target network platform;

Feedback the transaction information of the object to the user.
The device according to any one of claims 8 to 12, characterized in that the object processing rules include object update rules, and the object update rules describe constraint rules that need to be followed for the update operation of the object,

The joint processing module is also used to:

Detect the update operation performed by the user on the object on the joint network platform, and obtain the information provided by the user that the object needs to be updated in the target network platform according to the update operation;

The unilateral processing module is also configured to send an update request to the target network platform. The update request is used to request to update the object in the target network platform. The update request includes the information that needs to be updated.
The device according to any one of claims 8 to 13, characterized in that the object processing rules include object cancellation rules, and the object cancellation rules describe constraint rules that need to be followed for the cancellation operation of the object,

The joint processing module is also used to detect the undo operation performed by the user on the object on the joint network platform. Determine, according to the detection operation, the object that the user needs to revoke on the target network platform;

The unilateral processing module is also configured to send a cancellation request to the target network platform, where the cancellation request is used to request to cancel the object in the target network platform.
A computing device cluster, characterized by including at least one computing device, each computing device including a processor and a memory;

The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any one of claims 1 to 7.
A computer program product containing instructions, characterized in that, when the instructions are executed by a computing device cluster, the computing device cluster causes the computing device cluster to execute the method according to any one of claims 1 to 7.
A computer-readable storage medium, characterized in that it includes computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the method according to any one of claims 1 to 7.