WO2016000303A1 - 一种资源分配方法、系统及计算机存储介质 - Google Patents
一种资源分配方法、系统及计算机存储介质 Download PDFInfo
- Publication number
- WO2016000303A1 WO2016000303A1 PCT/CN2014/085146 CN2014085146W WO2016000303A1 WO 2016000303 A1 WO2016000303 A1 WO 2016000303A1 CN 2014085146 W CN2014085146 W CN 2014085146W WO 2016000303 A1 WO2016000303 A1 WO 2016000303A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- resource
- terminal user
- entity
- group
- allocated
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
Definitions
- the present invention relates to system integration technologies in the field of communications and computers, and more particularly to a resource allocation method, system and computer storage medium. Background technique
- a telecommunication service system is composed of several software/hardware modules, and different types of modules complete a certain function required by the system, for example, a database provides system configuration, user attributes, persistent storage and access of message data; and a file storage server provides The media file of the user to send and receive messages is stored and accessed persistently; the media server provides the functions of recording and playback, and key collection; the interactive voice response (IV) application server provides analysis of business logic and response processing to user input; The missed call notification server provides the logic and functionality for the integration of missed events into SMS messages.
- a database provides system configuration, user attributes, persistent storage and access of message data
- a file storage server provides The media file of the user to send and receive messages is stored and accessed persistently; the media server provides the functions of recording and playback, and key collection; the interactive voice response (IV) application server provides analysis of business logic and response processing to user input;
- the missed call notification server provides the logic and functionality for the integration of missed events into SMS messages.
- the inventors found that the existing telecommunication service system has at least the following defects:
- ATC A has become the advantage of the Advanced Telecom Computing Architecture (ATCA) hardware platform.
- ATCA Advanced Telecom Computing Architecture
- the preferred hardware platform for operators to deploy telecom service platforms is lower than that of minicomputers and high-end servers. Therefore, when using the ATCA hardware platform, the key software such as the original database is changed by the mode installed in one server.
- the existing telecommunication service system In order to deploy to a distributed deployment mode of multiple ATCA blades, the existing telecommunication service system has complicated configuration and management due to multi-node deployment; and, the existing telecommunication service system is based on virtualization-based cloud management technology. Management of virtual resources, for example, managing virtual resources such as general-purpose virtual machines/virtual disks. Therefore, the existing telecommunication service system cannot allocate corresponding resources to the end users according to the resource types allocated by the request. Summary of the invention
- embodiments of the present invention are directed to providing a resource allocation method, system, and computer storage medium, which can uniformly configure and manage resource entities based on a resource architecture, and can meet different resource granularity and different types of resource allocation requirements.
- An embodiment of the present invention provides a resource allocation method, where the method includes:
- the terminal user is allocated a corresponding resource entity.
- the pre-configuring a plurality of resource entities includes:
- Software application modules and/or hardware application modules that implement different functions are respectively configured as different types of resource entities.
- the determining the correspondence between the terminal user group and the resource entity includes: determining a correspondence between the terminal user group and a single resource entity;
- the resource type, the terminal user number, and the corresponding relationship between the terminal user group and the resource entity that are allocated according to the request, and the corresponding resource entity are allocated to the terminal user, including:
- the determining the correspondence between the terminal user group and the resource entity includes: classifying the resource entity, and configuring multiple resource entities of the same type into one resource group, and determining a correspondence between the terminal user group and the resource group;
- the resource type, the terminal user number, and the corresponding relationship between the terminal user group and the resource entity that are allocated according to the request, and the corresponding resource entity are allocated to the terminal user, including:
- the determining, according to the number of the terminal user, the terminal user group to which the terminal user belongs includes:
- the terminal user number is configured in the number segment corresponding to the terminal user group to which the terminal user belongs, by using a number header, a number tail, or a number header plus a number tail configuration manner;
- the allocating a corresponding resource entity to the terminal user includes:
- the terminal resource is allocated a corresponding resource entity by using the maximum available priority allocation mode, the random allocation mode, or the terminal user number modulo mode.
- the receiving the resource allocation request sent by the terminal user includes:
- the method further includes:
- the resource is requested by the resource address to provide the terminal user with a corresponding service.
- the method further includes:
- the embodiment of the present invention further provides a resource allocation system, where the system includes: a resource configuration module, a determining module, a receiving module, and a resource allocation module;
- the resource configuration module is configured to pre-configure multiple resource entities
- the determining module is configured to determine a correspondence between the terminal user group and the resource entity configured by the resource configuration module;
- the receiving module is configured to receive a resource allocation request, where the resource allocation request carries a resource type and a terminal user number that are requested to be allocated;
- the resource allocation module is configured to: according to the resource type, the terminal user number, and the corresponding relationship between the terminal user group and the resource entity determined by the determining module, according to the request received by the receiving module, The user assigns a corresponding resource entity.
- the resource configuration module is configured to respectively implement software application modules and/or hardware application modules that implement different functions as different types of resource entities.
- the determining module is configured to determine a correspondence relationship between the terminal user group and a single resource entity
- the resource allocation module is configured to determine, according to the terminal user number, a terminal user group to which the terminal user belongs; a resource type allocated according to the request, and a correspondence between the user terminal group and a single resource entity, Assigning the corresponding resource entity to the terminal user.
- the resource configuration module is configured to classify resource entities, configure multiple resource entities of the same type as one resource group, and determine corresponding correspondence between the terminal user group and the resource group.
- the resource allocation module is configured to determine, according to the terminal user number, a terminal user group to which the terminal user belongs, and determine, according to the resource type allocated by the request and the correspondence between the terminal user group and the resource group, A resource group corresponding to the terminal user, and the terminal user is allocated a resource entity in the corresponding resource group.
- the resource allocation module is configured to pre-configure the terminal user number in a number segment corresponding to the terminal user group to which the terminal user belongs by using a number header, a number tail, or a number header plus a number tail configuration manner; The terminal user number and the corresponding configuration manner are used to determine the terminal user group to which the terminal user belongs.
- the resource allocation module is configured to allocate the corresponding resource entity to the terminal user by using a maximum available priority allocation mode, a random allocation mode, or a terminal user number modulo mode.
- the receiving module is configured to receive a resource allocation request by using a URL interface.
- the system further comprises:
- the service providing module is configured to obtain the resource address of the allocated resource entity according to the resource entity allocation information returned by the URL interface, and request the resource to provide the corresponding service to the terminal user by using the resource address.
- the system further comprises:
- the resource daemon module is configured to automatically detect the state change of the resource entity; and add or delete the resource entity according to the state of the resource entity.
- the embodiment of the present invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the resource allocation method according to the embodiment of the present invention.
- the resource allocation method, system and computer storage medium provided by the embodiments of the present invention use a resource-oriented architecture to pre-configure a plurality of resource entities, and determine a correspondence relationship between the terminal user group and the resource entity; and receive a resource allocation request sent by the terminal user.
- Carrying in the resource allocation request The resource type and the terminal user number that are requested to be allocated; the resource type, the terminal user number, and the correspondence between the terminal user group and the resource entity according to the request, and the corresponding resource entity is allocated to the terminal user;
- the embodiment implements unified configuration and management of the resource entity based on the resource architecture; and can flexibly allocate resources according to the resource type, the terminal user number, and the correspondence between the terminal user group and the resource entity, so as to satisfy different resources. Granularity and requirements for different types of resource allocation.
- FIG. 1 is a schematic flowchart of implementing a resource allocation method according to an embodiment of the present invention
- FIG. 2 is a schematic structural diagram of a resource allocation system according to an embodiment of the present invention.
- FIG. 3 is a schematic structural diagram of a structure of a telecommunication service system according to an embodiment of the present invention. detailed description
- a plurality of resource entities are pre-configured, and a correspondence between the terminal user group and the resource entity is determined.
- the resource allocation request sent by the terminal user is received, where the resource allocation request carries the resource type and the terminal user that are requested to be allocated.
- the number is allocated to the terminal user according to the resource type, the terminal user number, and the correspondence between the terminal user group and the resource entity.
- Step S100 Pre-configure a plurality of resource entities, and determine a correspondence between a terminal user group and a resource entity.
- the pre-configuring a plurality of resource entities includes: configuring software application modules and/or hardware application modules that implement different functions as different types of resource entities.
- the resource allocation method according to the embodiment of the present invention is applied to a resource allocation system.
- the resource allocation system is composed of several types of software application/hardware application modules, and different types of software application/hardware application modules perform certain specific functions or services, if a software application/hardware application module can provide some application or service
- the function or service abstracts the software application/hardware application module into a resource entity. Therefore, the resource allocation system may be composed of multiple resource entities. In this way, resource entities can be uniformly configured and managed based on the resource architecture.
- the determined correspondence between the terminal user group and the resource entity is preset in the resource allocation system, that is, the terminal user in the terminal user group can only select the corresponding terminal user group when providing the service. Resource entity.
- Method 1 determining the correspondence between the terminal user group and the single resource entity
- Method 2 classifying the resource entity, and the same type
- the multiple resource entities are configured as a resource group, and the corresponding relationship between the terminal user group and the resource group is determined.
- the method for determining the correspondence between the terminal user group and the resource entity includes:
- the resources may be classified into two types: a storage resource and a computing resource. Therefore, when the resource entity is classified, the resource entity may be classified into two types according to the resource type: the first resource entity and the second resource class.
- the storage resource entity is a stateful resource entity, and the resource entity in the telecommunication service system that cannot provide persistent data or file storage belongs to a computing resource.
- the media server, the IVR application server, the missed call notification server, etc. although the computing class resource entity cannot store the user's data or files persistently, may record temporary session data or cache some locally through a certain copy synchronization technology. Non-real-time changes in configuration and data to improve Described performance of the telecommunications business.
- some software/hardware modules in the telecommunication service system do not directly provide services or functions for applications or services, and are not in the scope of resource entities, for example, a network management server and an overhead user interface.
- resource entities including: resource name, resource unique number, user identification (User Identification, UID), resource type, resource address, resource status, primary and backup flags, dedicated indication, etc.; where the resource address is provided by one resource entity to other service/application modules (for example, interface modules implementing some type of external protocol) or resource entities An internal addressing interface of its function or service.
- service/application modules for example, interface modules implementing some type of external protocol
- resource entities An internal addressing interface of its function or service.
- Different types of resource entities have different types of resource addresses according to their resource characteristics.
- the address of the database is the Internet Protocol Address (IP) address and port of its database service. No.
- IP Internet Protocol Address
- the IVR application server is the IP address of its internal message interface
- media server is the IP address of the Session Initiation Protocol (SIP) message.
- IP Internet Protocol Address
- the embodiment of the present invention can automatically detect the state change of the resource entity, and can dynamically add or delete the resource entity according to the state of the resource entity, and the specific implementation manner is as follows:
- the cloud platform uses the preset resource pool scheduling rule as an application instance.
- new virtual machine resources as new media servers;
- the corresponding resource entity record is automatically added to the new resource entity, and the corresponding relationship between the resource entity and the terminal user group is configured; when configured as a resource group, according to a preset rule Adding a new resource entity to a preset resource group; otherwise, when detecting the resource entity exiting, automatically deleting the deleted resource entity record, and deleting the corresponding relationship between the resource entity and the terminal user group; In the group, the resource entity is deleted from the resource group in which the resource entity is located. In this way, the overall performance of the system can be extended, It has smooth horizontal expansion capability and can correspondingly reduce the workload of configuration and management due to capacity expansion.
- Step S101 Receive a resource allocation request, where the resource allocation request carries a resource type and a terminal user number that are requested to be allocated.
- the resource allocation request is sent by a software application/hardware application module serving the end user in the resource allocation system.
- the resource allocation request includes information such as a resource type, an end user number, and the like that are requested to be allocated.
- Step S102 Allocate a corresponding resource entity to the terminal user according to the resource type, the terminal user number, and the predetermined correspondence between the terminal user group and the resource entity.
- the terminal user group when determining the correspondence between the terminal user group and the single resource entity in the first manner, first determining, according to the terminal user number, the terminal user group to which the terminal user belongs; and then selecting the resource type and the user terminal group according to the request.
- the terminal user is assigned a corresponding resource entity.
- multiple corresponding resource entities may be configured for each terminal user group.
- the terminal user group and the resource group in the second manner first determining, according to the terminal user number, the terminal user group to which the terminal user belongs; the resource type and the terminal user group and resources allocated according to the request Corresponding relationship of the group, determining a resource group corresponding to the terminal user; and allocating a resource entity in the corresponding resource group to the terminal user.
- multiple corresponding resource groups may be configured for each terminal user group.
- the terminal user may be allocated a corresponding resource entity by using a maximum available priority allocation mode, a random allocation mode, or a terminal user number modulo mode;
- the mode may be set according to the resource type and the resource usage that are requested to be allocated, and is not limited to the three allocation modes given above;
- the above allocation method is not specifically limited.
- the storage class resource entity since the storage class resource entity needs to persistently store user-related data or files, the storage class resource used by an end user must be fixed regardless of the manner in which the storage class resource entity is allocated. Therefore, when an end user is created, the storage class resource entity used by the terminal user is comprehensively selected according to the configured allocation mode and the current resource usage, and the system stores the address of the storage class resource entity in the terminal user. In the database, the subsequent application or service related to the end user does not re-allocate the storage class resource entity.
- the terminal user may be allocated a corresponding storage class resource entity by using the maximum available priority allocation mode, for example, the used resource entity is used according to the resource usage situation.
- the storage resource entity is allocated to the terminal user, the resource entity with the smallest amount of used data is preferentially selected; when the computing resource entity is allocated to the terminal user, the random allocation mode or the user may be used.
- the number modulo mode or the like allocates a corresponding resource entity to the terminal user, and allocates a corresponding resource entity to the terminal user according to the modulo mode of the user number.
- the determining, according to the number of the terminal user, the terminal user group to which the terminal user belongs includes:
- the terminal user number is configured in the number segment corresponding to the terminal user group to which the terminal user belongs, by using a number header, a number tail, or a number header plus a number tail configuration manner;
- the terminal user group to which the terminal user belongs is determined.
- the terminal user with the number header 185 is classified as the first terminal user group, and the terminal user with the number header 186 is classified as the second terminal user group, and the number is The terminal user whose header is 187 is classified as the third terminal user group, and the terminal user group to which the terminal user belongs can be determined according to the number of the terminal user number; when configuring in the end of the number, for example, the last two digits of the number end The end user from 00-30 is classified as the first end user group, and the last two digits from the end of the number are classified as the second end user group from the end users of 31-60, and the last two digits of the last digit are returned from the end users of 61-99.
- the terminal user group to which the terminal user belongs can be determined according to the last two digits of the terminal user number; when configuring by the number head plus the number tail, for example, the number head is 185 and the number tail The last one is classified as the first end user group from 1-5, and the first digit of the number is 185 and the last digit of the number is classified as the second terminal user group from 6-9, according to the number and tail of the terminal user number.
- One bit can determine the end user group to which the end user belongs.
- the allocating a corresponding resource entity to the terminal user includes:
- the terminal resource is allocated a corresponding resource entity by using the maximum available priority allocation mode, the random allocation mode, or the terminal user number modulo mode.
- the terminal user group to which the terminal user belongs is the terminal user group 1, according to the correspondence between the terminal user group 1 and the single resource entity in Table 1, it is determined that the resource entity 1 and the resource entity may be allocated to the terminal user. 3 or resource entity 4;
- the resource type that the terminal user requests to be allocated is a computing class resource
- the resource entities are classified, and multiple resource entities of the same type are configured as one resource group.
- the correspondence between the configured terminal user groups and resource groups is as shown in Table 2:
- the terminal user group to which the terminal user belongs is the terminal user group 1, determining, according to the correspondence between the terminal user group 1 and the resource group in Table 2, that the resource group 1 or the resource group 2 can be allocated to the terminal user.
- the resource type that the terminal user requests to be allocated is a storage class resource
- the resource entity in the resource group 1 can be allocated to the terminal user, and the maximum available priority allocation party is adopted.
- the resource user 1 or the resource entity 3 in the resource group 1 is allocated to the terminal user.
- the resource is selected for the terminal user.
- the resource allocation algorithm is encapsulated into a URL interface, and different forms of URL interfaces are provided for calling by the calling end.
- the calling end may be an external service/application module.
- the calling end IMAP4 protocol interface invokes the URL interface to obtain the database resource address allocated by the login user; or may be an internal resource entity or an internal service/application module.
- the calling IVR application server invokes the URL interface to obtain the media server resource address allocated by the calling user of the call.
- the URL interface includes a SQL stored procedure interface and a message interface.
- the SQL stored procedure interface is usually called by an internal resource entity or an internal service/application module, and the message interface is usually called by an external service/application module.
- the calling end can receive the resource allocation request through the URL interface.
- the input parameter of the URL interface is a resource type, a terminal user number and the like allocated by the request obtained from the resource allocation request.
- the calling end obtains the resource address of the allocated resource entity according to the output parameter of the URL interface, that is, according to the resource entity allocation information returned by the URL interface, and requests the resource to provide the corresponding service to the terminal user.
- the resource entity allocation information includes: whether there is an identifier of an available resource entity, a UID of the allocated resource entity, and the like, and the calling end determines, according to the identifier of the available resource entity returned by the URL interface, whether the available resource entity is available, When it is determined that the resource entity is available, the corresponding resource address is obtained according to the UID of the allocated resource entity; Ask resources to provide corresponding services for end users.
- the embodiment of the present invention performs resource virtualization processing on the functional software application and/or the hardware application module at the application level, and abstracts the functional software application and/or the hardware application module into different types of resource entities for unified configuration and management, and Translating calls between software applications and/or hardware application modules into services requesting resources, thereby reducing system configuration and management complexity; and, the present invention is capable of allocating resource types, end user numbers, and end user groups according to requests The corresponding relationship with the resource entity flexibly allocates resources, thereby meeting the requirements of different resource granularities and different types of resource allocation.
- the embodiment of the present invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the resource allocation method according to the embodiment of the present invention.
- an embodiment of the present invention provides a resource allocation system.
- the principle and method for solving the problem are similar. Therefore, the implementation process and implementation principles of the resource allocation system can refer to the implementation process and implementation of the foregoing method. The principle description, the repetition will not be repeated.
- the resource allocation system provided by the embodiment of the present invention includes: a resource configuration module 200, a determining module 201, a receiving module 202, and a resource allocating module 203. ; among them,
- the resource configuration module 200 is configured to pre-configure multiple resource entities
- the determining module 201 is configured to determine a correspondence between the terminal user group and the resource entity configured by the resource configuration module 200.
- the receiving module 202 is configured to receive a resource allocation request, where the resource allocation request carries a resource type and a terminal user number that are requested to be allocated;
- the resource allocation module 203 is configured to allocate a resource type, a terminal user number, and the terminal determined by the determining module 201 according to the request accepted by the receiving module 202.
- the corresponding relationship between the user group and the resource entity, and the corresponding resource entity is allocated to the terminal user.
- the resource configuration module 200 is configured to respectively implement a software application module and an I or a hardware application module that implement different functions as different types of resource entities.
- the determining module 201 is configured to determine a correspondence between the terminal user group and a single resource entity
- the resource allocation module 203 is configured to determine, according to the terminal user number, a terminal user group to which the terminal user belongs; a resource type allocated according to the request, and a group of the user terminal and a single resource entity Corresponding relationship, the terminal user is assigned a corresponding resource entity.
- the determining module 201 is configured to classify resource entities, configure multiple resource entities of the same type into one resource group, and determine a correspondence between the terminal user group and the resource group.
- the resource allocation module 203 is configured to determine, according to the terminal user number, a terminal user group to which the terminal user belongs; a resource type allocated according to the request, and a correspondence between the terminal user group and the resource group, Determining a resource group corresponding to the terminal user, and allocating a resource entity in the corresponding resource group to the terminal user.
- the resource allocation module 203 is configured to preconfigure the terminal user number in a number segment corresponding to the terminal user group to which the terminal user belongs by using a number header, a number tail, or a number header plus a number tail configuration manner; Determining, according to the terminal user number and the corresponding configuration manner, the terminal user group to which the terminal user belongs.
- the resource allocation module 203 is configured to allocate a corresponding resource entity to the terminal user by using a maximum available priority allocation mode, a random allocation mode, or a terminal user number modulo mode.
- the receiving module 202 is configured to receive a resource by using a URL interface. With the request.
- system further includes:
- the service providing module 204 is configured to obtain the resource address of the allocated resource entity according to the resource entity allocation information returned by the calling interface, and request the resource to provide the corresponding service to the terminal user by using the resource address.
- system further includes:
- the resource daemon module 205 is configured to automatically detect a state change of the resource entity; and add or delete the resource entity according to the state of the resource entity.
- the resource configuration module 200, the determining module 201, the resource allocating module 203, the service providing module 204, and the resource daemon module 205 in the resource allocation system may all be used by the central processing unit in the resource allocation system.
- CPU Central Processing Unit
- DSP digital signal processor
- FPGA Field-Programmable Gate Array
- the receiving module 202 can be used by the resource in practical applications. Implemented in the receiver or receiver antenna in the distribution system.
- the virtualization and cloudization gradually become the preferred solution for the high-end telecom operators to establish a new telecommunication service system.
- This trend requires the resource allocation system provider's products to be as purely software as possible to be deployed to virtual machines running on general-purpose hardware.
- the entire system's business scale can be expanded or contracted accordingly.
- the resource allocation system in the embodiment of the present invention has the capability of automatically detecting the state change of the internal resource entity, updating the resource entity, and configuring related information.
- the application layer since the URL interface has a shielding effect on the application layer module, the application layer does not perceive the state change of the underlying resource entity, and still invokes a certain type of resource address required by the URL interface request according to the existing method.
- the URL interface automatically selects the resource entity available to the terminal user according to the currently configured resource entity and related configuration information, so that the application layer can The newly added resource entity is invoked to extend the processing capability of the entire system, or the resource entity that has exited is not invoked to avoid service interruption, thereby causing the service size of the entire resource allocation system to expand or contract accordingly.
- the above functional modules may be software functional modules or hardware devices.
- the resource allocation system may be a distributed system or a centralized system. If the system is a distributed system, the above functional modules may be respectively implemented by hardware devices, and each hardware device interacts with the network; if it is a centralized system, the above functional modules It can be implemented in software and integrated into a hardware device.
- the embodiment of the present invention further provides a telecommunication service system. Since the principle and method for solving the problem are similar, the implementation process and implementation principles of the telecommunication service system can be referred to the implementation process and implementation of the foregoing method. The principle description, the repetition will not be repeated.
- FIG. 3 is a schematic structural diagram of a telecommunication service system according to an embodiment of the present invention. As shown in FIG. 3, a telecommunication service system according to an embodiment of the present invention includes two resource allocation systems as shown in FIG. 2, which may be referred to as a first resource allocation.
- the system 300 and the second resource allocation system 301, the first resource allocation system 300 and the second resource allocation system 301 have the same function and are mutually exclusive backup systems.
- the embodiment of the present invention implements a telecommunication service system by using a resource-based architecture, and may be in the first resource allocation system 300 and the second telecommunication service system 301, respectively.
- the first resource allocation system 300 and the second resource allocation system 301 can be deployed in different computer rooms or in different cities, so that services can be shared for telecom operators;
- the first resource allocation system 300 and the second resource allocation system 301 are mutually In the active/standby disaster recovery system, when one of the resource allocation systems switches to the standby resource allocation system due to a failure, the end user's data has been copied from the primary resource allocation system to the standby resource allocation system, and the standby resource allocation system is configured to switch.
- the alternate resource address is used to continue to provide services for the end user to switch to the standby resource allocation system to ensure the continuity of the service in the geographical disaster recovery scenario.
- the resource allocation request sent by the terminal user to a resource allocation system in the telecommunication service system further carries an identifier of the active/standby resource entity that is requested to be allocated, and receives the terminal user.
- the resource allocation request it is determined whether the primary resource resource or the standby resource entity is requested according to the identifier of the primary/secondary resource entity that is requested to be requested, and the subsequent corresponding operation is performed according to the determination result, and the corresponding terminal is allocated to the terminal user.
- the telecommunication service system can be extended to include N resource distribution systems, and N is a positive integer.
- the N resource distribution systems in the telecommunication service system can be deployed in different computer rooms or different cities, and corresponding primary and backup relationships are configured.
- the telecommunication service system is composed of a central site and a plurality of remote sites, the central site is configured with an active resource entity, and the plurality of remote sites are configured with an alternate resource entity; thus, the telecommunication service system can be a telecommunication carrier. Share business and have a higher level of geographic disaster tolerance.
- the Mobile Virtual Network Operator usually does not build its own telecom value-added service platform, and uses its leased mobile network operator (MNO) to telecommunication services.
- MNO mobile network operator
- the platform provides telecom value-added services for its users. This mode of operation is multi-tenancy; this requires the mobile network operator's telecom service platform to provide services to its own users in addition to providing services to one or more MVNO end users. business.
- the sharing platform can be isolated from each other to a certain extent, and the telecommunication service system provider can support providing multiple virtual telecommunication service systems in one telecommunication service system, thereby realizing the isolation of user data and service data management between different tenants, and The system still needs to provide a unified management view to the host MNO operator instead of several fully split subsystems.
- the present invention can assign a resource entity to a service provider (SP), and establish an association between the terminal user group and the SP, as follows:
- the SP is a service provider that provides the telecommunication service for the end user by using the resource allocation system.
- a resource allocation system needs to provide services for different terminal user groups corresponding to multiple SPs at the same time, the mode is multi-tenancy.
- a telecommunications carrier that builds a multi-tenancy system is called a provider or a host, and an SP that rents the resource allocation system to provide services to an end user group to which the SP belongs is called a tenant.
- a plurality of resource entities in the resource allocation system may be explicitly assigned to any SP.
- the terminal user group of the SP can only Selecting a corresponding resource entity according to the resource type requested by the request or selecting a resource entity from the corresponding resource group for allocation; if the resource entity or the resource group is not explicitly assigned to an SP, the terminal user group of the SP may be allocated according to the request.
- the resource type selects a corresponding resource entity from a resource entity or a resource group corresponding to the resource type in the resource allocation system; by using the resource configuration relationship, not only the resource entity and the SP are allocated, but also the resource and the number are simplified.
- the setting of the segment allocation because different SPs can be configured with the same number segment, as long as the SP to which the terminal user belongs is determined, the resource entity can be allocated according to the number segment under the SP, and the configuration under the port number transfer scenario is solved. .
- the resource allocation system records the SP information to which the terminal user belongs in each end user attribute; when a new user is created, the telecommunication service system follows the preset.
- the rule determines the SP to which the terminal user belongs, and further selects the resource entity corresponding to the terminal user according to the corresponding relationship between the SP and the resource entity; and if the resource usage request of the certain SP is not explicitly assigned to the SP, the resource is still configured according to the global configuration. Entity and The corresponding relationship of the terminal user groups is used to select resource entities matched by the terminal users.
- the resource entity can be allocated according to the tenant in the multi-tenancy scenario.
- the mechanism for allocating data between multiple data nodes is not controlled by the service layer. Data security and privacy protection requirements while avoiding software complexity introduced by applications and business layers using other data isolation technologies.
- the embodiment of the present invention performs resource virtualization processing on the functional software application and/or the hardware application module at the application level, and abstracts the functional software application and/or the hardware application module into different types of resource entities for unified configuration and management, and Converting a call between a software application and/or a hardware application module into a service requesting a resource, thereby reducing the complexity of system configuration and management; and, in addition, the resource type, the terminal user number, and the terminal user that can be allocated according to the request in the embodiment of the present invention
- the corresponding relationship between the group and the resource entity flexibly allocates resources, so as to meet the requirements of different resource granularity and different types of resource allocation; and the resource allocation system provides a unified URL interface for the calling end to obtain access by a terminal user.
- the resource address is then requested by the resource address to provide services for the terminal user, thereby simplifying the process of allocating resource entities.
- the resource entity can achieve reasonable use of resources.
- embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware. Moreover, the present invention is applicable to one or more computer-usable storage media (including but not limited to disks) having computer usable program code embodied therein. A form of computer program product embodied on a memory and optical storage, etc.).
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
- the embodiment of the present invention pre-configures a plurality of resource entities with a resource-oriented architecture, and determines a correspondence between the terminal user group and the resource entity; receiving a resource allocation request sent by the terminal user, where the resource allocation request carries a request Allocated resource type, end user number; Requesting the allocated resource type, the terminal user number, and the correspondence between the terminal user group and the resource entity, and allocating the corresponding resource entity to the terminal user; thus, the resource entity is uniformly configured and managed based on the resource architecture; According to the resource type, the terminal user number, and the corresponding relationship between the terminal user group and the resource entity, the resource allocation is flexibly performed, so that the requirements of different resource granularities and different types of resource allocation can be met.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本发明实施例公开了一种资源分配方法,所述方法包括:预先配置多个资源实体,并确定终端用户群与资源实体的对应关系;接收资源分配请求,所述资源分配请求中携带有请求分配的资源类型及终端用户号码;根据所述请求分配的资源类型、终端用户号码、以及预先确定的所述终端用户群与资源实体的对应关系,为所述终端用户分配对应的资源实体。本发明实施例还同时公开了一种资源分配系统及计算机存储介质。
Description
一种资源分配方法、 系统及计算机存储介质 技术领域
本发明涉及通信以及计算机领域中的系统集成技术, 尤其涉及一种资 源分配方法、 系统及计算机存储介质。 背景技术
通常, 电信业务系统由若干个软 /硬件模块构成, 不同类型的模块完成 该系统所需的某项功能, 例如, 数据库提供系统配置、 用户属性、 消息数 据的持久存储及访问; 文件存储服务器提供用户收发消息的媒体文件持久 化存储及访问; 媒体服务器提供录放音以及按键收号的功能; 互动式语音 应答(Interactive Voice Response, IV )应用服务器提供业务逻辑的解析以 及对用户输入的响应处理; 漏话通知服务器提供漏话事件整合为短信的逻 辑和功能。
发明人在实现本发明的过程中, 发现现有电信业务系统至少存在以下 缺陷:
现有的电信业务系统, 通常釆用小型机或高端服务器作为数据库以及 关键业务软件的硬件平台,而最近几年由于高级通讯计算机架构( Advanced Telecom Computing Architecture, ATCA )硬件平台的优势, ATC A成为运营 商部署电信业务平台的首选硬件平台; 但单个 ATCA硬件的计算密度相对 小型机和高端服务器要低, 故釆用 ATCA硬件平台时, 原有的数据库等关 键软件由安装在一个服务器的模式转变为部署到多个 ATCA刀片的分布部 署模式, 因此, 现有电信业务系统由于多节点部署而导致了配置及管理的 复杂度; 并且, 现有电信业务系统是基于虚拟化的云管理技术对通用的虚 拟资源进行管理, 例如, 对通用的虚拟机 /虚拟磁盘等虚拟资源进行管理,
因此, 现有电信业务系统不能根据请求分配的资源类型为终端用户分配相 应的资源。 发明内容
有鉴于此, 本发明实施例期望提供一种资源分配方法、 系统及计算机 存储介质, 能基于资源架构对资源实体进行统一配置与管理, 并能满足不 同资源粒度及不同类型资源调配的要求。
为达到上述目的, 本发明实施例的技术方案是这样实现的:
本发明实施例提供了一种资源分配方法, 所述方法包括:
预先配置多个资源实体, 并确定终端用户群与所述资源实体的对应关 系;
接收资源分配请求, 所述资源分配请求中携带有请求分配的资源类型 及终端用户号码;
根据所述请求分配的资源类型、 终端用户号码、 以及预先确定的所述 终端用户群与资源实体的对应关系, 为所述终端用户分配对应的资源实体。
优选地, 所述预先配置多个资源实体, 包括:
将实现不同功能的软件应用模块和 /或硬件应用模块分别配置为不同 类型的资源实体。
优选地, 所述确定终端用户群与资源实体的对应关系, 包括: 确定终 端用户群与单个资源实体的对应关系;
相应的, 所述根据所述请求分配的资源类型、 终端用户号码、 以及预 先确定的所述终端用户群与资源实体的对应关系, 为所述终端用户分配对 应的资源实体, 包括:
根据所述终端用户号码确定所述终端用户所属的终端用户群; 根据所述请求分配的资源类型及所述用户终端群与单个资源实体的对 应关系, 为所述终端用户分配对应的资源实体。
优选地, 所述确定终端用户群与资源实体的对应关系, 包括: 对资源实体进行分类, 并将相同类型的多个资源实体配置为一个资源 组, 确定终端用户群与资源组的对应关系;
相应的, 所述根据所述请求分配的资源类型、 终端用户号码、 以及预 先确定的所述终端用户群与资源实体的对应关系, 为所述终端用户分配对 应的资源实体, 包括:
根据所述终端用户号码确定所述终端用户所属的终端用户群; 根据所述请求分配的资源类型及终端用户群与资源组的对应关系, 确 定所述终端用户对应的资源组, 为所述终端用户分配对应的资源组内的资 源实体。
优选地, 所述根据所述终端用户的号码确定所述终端用户所属的终端 用户群, 包括:
预先通过号码头、 号码尾或号码头加号码尾配置方式, 将终端用户号 码配置在所述终端用户所属的终端用户群对应的号码段内;
根据所述终端用户号码以及对应的配置方式, 确定所述终端用户所属 的终端用户群。
优选地, 所述为所述终端用户分配对应的资源实体, 包括:
釆用最大可用优先分配方式、 随机分配方式或按终端用户号码取模方 式为所述终端用户分配对应的资源实体。
优选地, 所述接收终端用户发送的资源分配请求, 包括:
通过统一资源定位服务 ( Uniform Resource Locator , URL )接口, 接收 资源分配请求。
优选地, 所述为所述终端用户分配对应的资源实体之后, 所述方法还 包括:
根据 URL接口返回的资源实体分配信息, 获取分配的资源实体的资源
地址;
通过所述资源地址请求资源为所述终端用户提供相应的服务。
优选地, 所述方法还包括:
自动探测资源实体的状态变化;
根据资源实体的状态, 添加或删除资源实体。
本发明实施例还提供了一种资源分配系统, 所述系统包括: 资源配置 模块、 确定模块、 接收模块和资源分配模块; 其中,
所述资源配置模块, 配置为预先配置多个资源实体;
所述确定模块, 配置为确定终端用户群与所述资源配置模块配置的资 源实体的对应关系;
所述接收模块, 配置为接收资源分配请求, 所述资源分配请求中携带 有请求分配的资源类型及终端用户号码;
所述资源分配模块, 配置为根据所述接收模块接受的所述请求分配的 资源类型、 终端用户号码、 以及所述确定模块确定的所述终端用户群与资 源实体的对应关系, 为所述终端用户分配对应的资源实体。
优选地, 所述资源配置模块, 配置为将实现不同功能的软件应用模块 和 /或硬件应用模块分别作为不同类型的资源实体。
优选地, 所述确定模块, 配置为确定终端用户群与单个资源实体的对 应关系;
相应的, 所述资源分配模块, 配置为根据所述终端用户号码确定所述 终端用户所属的终端用户群; 根据所述请求分配的资源类型及所述用户终 端群与单个资源实体的对应关系, 为所述终端用户分配对应的资源实体。
优选地, 所述资源配置模块, 配置为对资源实体进行分类, 将相同类 型的多个资源实体配置为一个资源组; 确定终端用户群与资源组的对应关
相应的, 所述资源分配模块, 配置为根据所述终端用户号码确定所述 终端用户所属的终端用户群; 根据所述请求分配的资源类型及终端用户群 与资源组的对应关系, 确定所述终端用户对应的资源组, 为所述终端用户 分配对应的资源组内的资源实体。
优选地, 所述资源分配模块, 配置为预先通过号码头、 号码尾或号码 头加号码尾配置方式, 将终端用户号码配置在所述终端用户所属的终端用 户群对应的号码段内; 根据所述终端用户号码以及对应的配置方式, 确定 所述终端用户所属的终端用户群。
优选地, 所述资源分配模块, 配置为釆用最大可用优先分配方式、 随 机分配方式或按终端用户号码取模方式为所述终端用户分配对应的资源实 体。
优选地, 所述接收模块, 配置为通过 URL接口, 接收资源分配请求。 优选地, 所述系统还包括:
服务提供模块, 配置为根据 URL接口返回的资源实体分配信息, 获取 分配的资源实体的资源地址; 通过所述资源地址请求资源为所述终端用户 提供相应的服务。
优选地, 所述系统还包括:
资源守护模块, 配置为自动探测资源实体的状态变化; 并根据资源实 体的状态, 添加或删除资源实体。
本发明实施例还提供了一种计算机存储介质, 所述计算机存储介质中 存储有计算机可执行指令, 所述计算机可执行指令用于执行本发明实施例 所述的资源分配方法。
本发明实施例所提供的资源分配方法、 系统及计算机存储介质, 釆用 面向资源的架构预先配置多个资源实体, 并确定终端用户群与资源实体的 对应关系; 接收终端用户发送的资源分配请求, 所述资源分配请求中携带
有请求分配的资源类型、 终端用户号码; 根据所述请求分配的资源类型、 终端用户号码、 以及终端用户群与资源实体的对应关系, 为所述终端用户 分配对应的资源实体; 如此, 本发明实施例实现了基于资源架构对资源实 体进行统一配置与管理; 并能够根据请求分配的资源类型、 终端用户号码、 以及终端用户群与资源实体的对应关系灵活地进行资源分配, 从而能够满 足不同资源粒度及不同类型资源调配的要求。 附图说明
图 1为本发明实施例资源分配方法实现流程示意图;
图 2为本发明实施例资源分配系统的组成结构示意图;
图 3为本发明实施例电信业务系统的组成结构示意图。 具体实施方式
本发明实施例中, 预先配置多个资源实体, 并确定终端用户群与资源 实体的对应关系; 接收终端用户发送的资源分配请求, 所述资源分配请求 中携带有请求分配的资源类型、 终端用户号码; 根据所述请求分配的资源 类型、 终端用户号码、 以及终端用户群与资源实体的对应关系, 为所述终 端用户分配对应的资源实体。
下面结合附图和具体实施方式对本发明所述方法和系统作进一步说 明。
图 1为本发明资源分配方法流程示意图, 如图 1所示, 所述方法包括: 步骤 S100: 预先配置多个资源实体, 并确定终端用户群与资源实体的 对应关系。
这里, 所述预先配置多个资源实体, 包括: 将实现不同功能的软件应 用模块和 /或硬件应用模块分别配置为不同类型的资源实体。
这里, 本发明实施例所述的资源分配方法应用于资源分配系统中, 所
述资源分配系统由若干类软件应用 /硬件应用模块构成, 不同类型的软件应 用 /硬件应用模块完成各自特定的某些功能或服务, 若某个软件应用 /硬件应 用模块能够为应用或业务提供某些功能或服务, 则将该软件应用 /硬件应用 模块抽象为一个资源实体, 因此, 所述资源分配系统中可由多个资源实体 构成。 这样, 能够基于资源架构对资源实体进行统一配置与管理。
这里, 所述确定的终端用户群与资源实体的对应关系在资源分配系统 中被预先设置, 也就是说, 所述终端用户群中的终端用户需提供服务时只 能选择与所属终端用户群对应的资源实体。
这里, 在确定终端用户群与资源实体的对应关系时, 可以釆取两种方 式: 方式一、 确定终端用户群与单个资源实体的对应关系; 方式二、 对资 源实体进行分类, 并将相同类型的多个资源实体配置为一个资源组, 确定 终端用户群与资源组的对应关系; 无论釆用上述哪种方式, 其中, 所述确 定终端用户群与资源实体的对应关系, 包括:
确定终端用户群与单个资源实体的对应关系。
具体的, 由于资源可分为存储类资源和计算类资源两种类型, 因此, 对资源实体进行分类时, 可将资源实体按照资源类型分为两类: 第一类资 源实体及第二类资源实体; 其中, 所述第一类资源实体为存储类资源实体, 第二类资源实体为计算类资源实体; 其中, 所述存储类资源实体提供持久 性存储的服务, 例如, 数据库、 文件存储服务器等, 由于所述存储类实体 具有存储特性, 因此所述存储类资源实体是有状态的资源实体; 所述电信 业务系统中其他不能够提供持久性数据或文件存储的资源实体属于计算类 资源, 例如, 媒体服务器、 IVR应用服务器、 漏话通知服务器等, 虽然计 算类资源实体不能够持久性存储用户的数据或文件, 但可能会记录临时的 会话数据或通过一定的复制同步技术在本地緩存某些非实时变化的配置及 数据, 用以提高所述电信业务的性能。
另外, 所述电信业务系统中某些软件 /硬件模块不直接为应用或业务提 供服务或功能则不属于资源实体范畴, 例如, 网管服务器, 开销户接口。
这里, 虽然不同类型的资源实体在结构和功能方面存在差异, 但为实 现统一的配置与分配管理, 会为资源实体配置若干通用属性, 包括: 资源 名、 资源唯一编号用户身份证明( User Identification, UID ), 资源类型、 资 源地址、 资源状态、 主备用标志、 专属标示等; 其中, 资源地址为一个资 源实体向其他业务 /应用模块(例如, 实现某类外部协议的接口模块)或资 源实体提供其功能或服务的内部寻址接口, 不同类型的资源实体根据其资 源特性而具有不同类型的资源地址, 例如, 数据库的地址为其数据库服务 的互联网协议地址(Internet Protocol Address, IP )地址以及端口号, IVR 应用服务器为其内部消息接口 IP 地址, 媒体服务器为接收会话初始协议 ( Session Initiation Protocol, SIP ) 消息的 IP地址。
依据本发明实施例的另一优选实施例, 本发明实施例能够自动感知资 源实体的状态变化, 并能够根据资源实体的状态动态地添加或删除资源实 体, 具体实现方式如下:
自动探测资源实体状态的变化, 所述变化包括新的资源实体启动运行 和已有的资源实体停止运行, 例如, 在话务高峰时段, 云平台按照预设的 资源池调度规则为某个应用实例化若干个新的虚拟机资源作为新的媒体服 务器;
当探测到新的资源实体启动运行时, 自动为新的资源实体添加对应的 资源实体记录, 并配置所述资源实体与终端用户群的对应关系; 在配置为 资源组时, 按照预设的规则将新的资源实体加入预设的资源组; 反之, 当 探测到资源实体退出时, 自动将已退出的资源实体记录删除, 同时删除所 述资源实体与终端用户群的对应关系; 在配置为资源组时, 从所述资源实 体所在的资源组中删除所述资源实体。 这样, 能够扩展系统的总体性能,
具有平滑的水平扩展能力, 并能够相应地减少由于扩容导致的配置及管理 的工作量。
步骤 S101 : 接收资源分配请求, 所述资源分配请求中携带有请求分配 的资源类型及终端用户号码。
这里, 所述资源分配请求是由资源分配系统中服务于所述终端用户的 软件应用 /硬件应用模块发送的。
这里, 所述资源分配请求包括请求分配的资源类型、 终端用户号码等 信息。
步骤 S102: 根据所述请求分配的资源类型、 终端用户号码、 以及预先 确定的所述终端用户群与资源实体的对应关系, 为所述终端用户分配对应 的资源实体。
这里, 在以方式一确定终端用户群与单个资源实体的对应关系时, 首 先根据所述终端用户号码确定所述终端用户所属的终端用户群; 然后根据 所述请求分配的资源类型及用户终端群与单个资源实体的对应关系, 为所 述终端用户分配对应的资源实体。 其中, 方式一中可以为每个终端用户群 配置对应的多个资源实体。
这里, 在以方式二确定终端用户群与资源组的对应关系时, 首先根据 所述终端用户号码确定所述终端用户所属的终端用户群; 根据所述请求分 配的资源类型及终端用户群与资源组的对应关系, 确定所述终端用户对应 的资源组; 为所述终端用户分配对应的资源组内的资源实体。 其中, 方式 二中可以为每个终端用户群配置对应的多个资源组。
这里, 在为所述终端用户分配对应的资源实体时, 可以釆用最大可用 优先分配方式、 随机分配方式或按终端用户号码取模方式等为所述终端用 户分配对应的资源实体; 具体的分配方式可根据请求分配的资源类型及资 源使用情况进行设定, 并不限于上述给出的三种分配方式; 本发明实施例
对上述分配方式不作具体限定。
需要说明的是, 对于存储类资源实体, 由于存储类资源实体要持久存 储用户相关数据或文件, 因此不论釆用何种方式分配存储类资源实体, 一 个终端用户所使用的存储类资源必须固定, 故当一个终端用户被创建时, 按照所配置的分配方式以及当前资源使用情况综合选择所述终端用户所使 用的存储类资源实体, 系统将存储类资源实体的地址存储在所述终端用户 所分配的数据库中, 后续所述终端用户相关的应用或业务均不再重新分配 存储类资源实体。
具体的, 在为所述终端用户分配存储类资源实体时, 可以釆用最大可 用优先分配方式为所述终端用户分配对应的存储类资源实体, 例如, 根据 资源使用情况对各个资源实体的已用数据量进行统计, 为所述终端用户分 配存储类资源实体时, 优先选择已用数据量最小的资源实体; 在为所述终 端用户分配计算类资源实体时, 可以釆用随机分配方式或按用户号码取模 方式等为所述终端用户分配对应的资源实体, 若按用户号码取模方式为所 述终端用户分配对应的资源实体。
上述方案中, 所述根据所述终端用户的号码确定所述终端用户所属的 终端用户群, 包括:
预先通过号码头、 号码尾或号码头加号码尾配置方式, 将终端用户号 码配置在所述终端用户所属的终端用户群对应的号码段内;
然后, 根据所述终端用户号码以及对应的配置方式, 确定所述终端用 户所属的终端用户群。
下面对如何根据所述终端用户号码确定所述终端用户所属的终端用户 群的具体实施方式进行详细说明:
以号码头方式进行配置时, 例如, 将号码头为 185 的终端用户归为第 一终端用户群, 将号码头为 186 的终端用户归为第二终端用户群, 将号码
头为 187 的终端用户归为第三终端用户群, 根据终端用户号码的号码头即 可确定所述终端用户所属的终端用户群; 以号码尾方式进行配置时, 例如, 将号码尾最后两位从 00-30的终端用户归为第一终端用户群,将号码尾最后 两位从 31-60的终端用户归为第二终端用户群, 将号码尾最后两位从 61-99 的终端用户归为第三终端用户群, 根据终端用户号码的尾部最后两位即可 确定所述终端用户所属的终端用户群; 以号码头加号码尾方式进行配置时, 例如,将号码头为 185及号码尾最后一位从 1-5的归为第一终端用户群,将 号码头为 185及号码尾最后一位从 6-9的归为第二终端用户群,根据终端用 户号码的号码头及尾部最后一位即可确定所述终端用户所属的终端用户 群。
依据本发明实施例的另一优选实施例, 所述为所述终端用户分配对应 的资源实体, 包括:
釆用最大可用优先分配方式、 随机分配方式或按终端用户号码取模方 式为所述终端用户分配对应的资源实体。
下面以具体实施例对上述为所述终端用户分配对应的资源实体的过程 进行详细说明:
若预先配置两个终端用户群(ID1-ID2 以及五个资源实体(ID1-ID5 ), 以方式一进行配置时, ^^设配置的终端用户群与单个资源实体的对应关系 如表 1所示:
通过上述方式确定所述终端用户所属的终端用户群为终端用户群 1时, 根据表 1中终端用户群 1与单个资源实体的对应关系, 确定可以为所述终 端用户分配资源实体 1、 资源实体 3或资源实体 4;
进一步地, 若所述终端用户请求分配的资源类型为计算类资源, 则确 定可以为终端用户分配资源实体 3或资源实体 4, 然后通过随机分配方式, 为所述终端用户分配资源实体 3或资源实体 4。
以方式二进行配置时, 对资源实体进行分类, 并将相同类型的多个资 源实体配置为一个资源组, 4艮设配置的终端用户群与资源组的对应关系如 表 2所示:
表 2
通过上述方式确定所述终端用户所属的终端用户群为终端用户群 1时, 根据表 2中终端用户群 1与资源组的对应关系, 确定可以为所述终端用户 分配资源组 1或资源组 2中的资源实体;
进一步地, 若所述终端用户请求分配的资源类型为存储类资源, 则确 定可以为终端用户分配资源组 1中的资源实体, 通过最大可用优先分配方
式为所述终端用户分配资源组 1中的资源实体 1或资源实体 3,此时由于资 源实体 3的已用数据量高于资源实体 1的已用数据量, 因此为所述终端用 户选择资源组 1中的资源实体 1。
优选的, 由于为所述终端用户分配对应的资源实体时, 需要根据请求 分配的资源类型、 终端用户号码、 以及终端用户群与资源实体的对应关系, 并结合相应的分配方式为所述终端用户分配对应的资源实体; 上述资源分 配算法非常复杂, 因此为简化实现资源实体的分配过程, 本发明实施例中 将上述资源分配算法封装为 URL接口, 并提供不同形式的 URL接口供调 用端调用, 所述调用端可以是某个外部的业务 /应用模块, 例如, 调用端 IMAP4协议接口调用 URL接口获取登陆用户所分配的数据库资源地址;也 可以是某个内部的资源实体或内部业务 /应用模块, 例如, 调用端 IVR应用 服务器调用 URL接口获取呼叫的主叫用户所分配的媒体服务器资源地址。
其中, 所述 URL接口包括 SQL存储过程接口和消息接口, 所述 SQL 存储过程接口通常供内部资源实体或内部业务 /应用模块调用, 所述消息接 口通常供外部业务 /应用模块调用。
在步骤 S101 中, 调用端可以通过 URL接口接收资源分配请求, 相应 的, 所述 URL接口的输入参数即为从资源分配请求中获取的请求分配的资 源类型、 终端用户号码等参数。
在步骤 S102之后, 调用端根据 URL接口的输出参数, 即: 根据 URL 接口返回的资源实体分配信息, 获取分配的资源实体的资源地址; 通过所 述资源地址请求资源为终端用户提供相应的服务。
具体的, 所述资源实体分配信息包括: 是否有可用资源实体的标识, 分配的资源实体的 UID等信息,调用端根据 URL接口返回的是否有可用资 源实体的标识确定是否有可用的资源实体, 确定有可用的资源实体时, 根 据分配的资源实体的 UID获取对应的资源地址; 然后通过所述资源地址请
求资源为终端用户提供相应的服务。
本发明实施例在应用层面针对功能性软件应用和 /或硬件应用模块做资 源虚拟化处理, 将功能性软件应用和 /或硬件应用模块分别抽象为不同类型 的资源实体进行统一配置与管理, 并将软件应用和 /或硬件应用模块间的调 用转换为请求资源的服务, 从而降低了系统配置与管理的复杂度; 并且, 本发明能够根据请求分配的资源类型、 终端用户号码、 以及终端用户群与 资源实体的对应关系灵活地进行资源分配, 从而能够满足不同资源粒度及 不同类型资源调配的要求。
本发明实施例还提供了一种计算机存储介质, 所述计算机存储介质中 存储有计算机可执行指令, 所述计算机可执行指令用于执行本发明实施例 所述的资源分配方法。
为实现上述方法, 本发明实施例提供了一种资源分配系统, 由于所述 系统解决问题的原理与方法相似, 因此, 资源分配系统的实施过程及实施 原理均可以参见前述方法的实施过程及实施原理描述, 重复之处不再赘 述。
图 2为本发明实施例资源分配系统的组成结构示意图; 如图 2所示, 本发明实施例提供的资源分配系统, 包括: 资源配置模块 200、 确定模块 201、 接收模块 202、 资源分配模块 203 ; 其中,
所述资源配置模块 200, 配置为预先配置多个资源实体;
所述确定模块 201,配置为确定终端用户群与所述资源配置模块 200配 置的资源实体的对应关系;
所述接收模块 202, 配置为接收资源分配请求, 所述资源分配请求中携 带有请求分配的资源类型及终端用户号码;
所述资源分配模块 203,配置为根据所述接收模块 202接受的所述请求 分配的资源类型、 终端用户号码、 以及所述确定模块 201 确定的所述终端
用户群与资源实体的对应关系, 为所述终端用户分配对应的资源实体。 以上功能单元或模块的划分方式仅为本发明实施例给出的一种优选实 现方式, 功能单元或模块的划分方式不构成对本发明的限制。
具体实施中, 所述资源配置模块 200, 配置为将实现不同功能的软件应 用模块和 I或硬件应用模块分别作为不同类型的资源实体。
具体实施中, 所述确定模块 201, 配置为确定终端用户群与单个资源实 体的对应关系;
相应的, 所述资源分配模块 203, 配置为才艮据所述终端用户号码确定所 述终端用户所属的终端用户群; 根据所述请求分配的资源类型及所述用户 终端群与单个资源实体的对应关系, 为所述终端用户分配对应的资源实体。
具体实施中, 所述确定模块 201, 配置为对资源实体进行分类, 将相同 类型的多个资源实体配置为一个资源组; 确定终端用户群与资源组的对应 关系;
相应的, 所述资源分配模块 203, 配置为才艮据所述终端用户号码确定所 述终端用户所属的终端用户群; 根据所述请求分配的资源类型及终端用户 群与资源组的对应关系, 确定所述终端用户对应的资源组, 为所述终端用 户分配对应的资源组内的资源实体。
具体实施中, 所述资源分配模块 203, 配置为预先通过号码头、 号码尾 或号码头加号码尾配置方式, 将终端用户号码配置在所述终端用户所属的 终端用户群对应的号码段内; 根据所述终端用户号码以及对应的配置方式, 确定所述终端用户所属的终端用户群。
具体实施中, 所述资源分配模块 203, 配置为釆用最大可用优先分配方 式、 随机分配方式或按终端用户号码取模方式为所述终端用户分配对应的 资源实体。
具体实施中, 所述接收模块 202, 配置为通过 URL接口, 接收资源分
配请求。
具体实施中, 所述系统还包括:
服务提供模块 204, 配置为根据调用接口返回的资源实体分配信息, 获 取分配的资源实体的资源地址; 通过所述资源地址请求资源为所述终端用 户提供相应的服务。
具体实施中, 所述系统还包括:
资源守护模块 205, 配置为自动探测资源实体的状态变化; 并根据资源 实体的状态, 添加或删除资源实体。
其中, 所述资源分配系统中的资源配置模块 200、 确定模块 201、 资源 分配模块 203、服务提供模块 204和资源守护模块 205在实际应用中, 均可 由所述资源分配系统中的中央处理器 ( CPU, Central Processing Unit )、 或 数字信号处理器(DSP, Digital Signal Processor ),或可编程门阵列( FPGA, Field-Programmable Gate Array ) 实现; 所述接收模块 202在实际应用中, 可由所述资源分配系统中的接收器或接收天线实现。
本发明实施例中, 由于以虚拟化和云化逐渐成为高端电信运营商新建 电信业务系统的首选方案。 这种趋势, 一方面要求资源分配系统提供商的 产品尽可能純软件化以能部署到运行在通用硬件之上的虚拟机中, 此外需 而整个系统的业务规模也可相应扩展或收缩, 因此, 本发明实施例中的资 源分配系统具有自动探测内部资源实体的状态变化, 更新资源实体及配置 相关信息的能力。
本发明实施例中, 由于 URL接口对应用层模块具有屏蔽效果, 因此, 应用层并不会感知到底层资源实体的状态变化, 仍按照已有方式调用 URL 接口请求所需的某类资源地址, URL接口会自动根据当前配置的资源实体 及相关配置信息选择终端用户可用的资源实体返回, 从而使得应用层可自
动调用新增的资源实体以扩展整个系统的处理能力, 或不调用已退出的资 源实体以避免业务中断, 进而使整个资源分配系统的业务规模相应地扩展 或收缩。
上述功能模块可以是软件功能模块, 也可以是硬件设备。 该资源分配 系统可以是分布式系统或集中式系统, 若为分布式系统, 则上述功能模块 可分别由硬件设备实现, 各硬件设备之间通过网络交互; 若是集中式系 统, 则上述各功能模块可由软件实现, 并可集成在一个硬件设备中。
为实现上述方法, 本发明实施例还提供了一种电信业务系统, 由于该 系统解决问题的原理与方法相似, 因此, 电信业务系统的实施过程及实施 原理均可以参见前述方法的实施过程及实施原理描述, 重复之处不再赘 述。
图 3为本发明实施例电信业务系统的组成结构示意图; 如图 3所示, 本发明实施例提供的电信业务系统, 包括两个图 2所述的资源分配系统, 可称为第一资源分配系统 300及第二资源分配系统 301,所述第一资源分配 系统 300与所述第二资源分配系统 301功能相同且互为主备用系统。
这里, 由于高可用性一直是电信业务系统的重要能力要求, 高可用性 包括单系统高可用性和地理容灾两个层次, 其复杂度不尽相同, 伴随多租 和云平台的部署场景, 需电信业务系统提供商考虑如何确保系统的高可用 性, 基于此, 本发明实施例釆用基于资源的架构实现电信业务系统, 并可 分别在所述第一资源分配系统 300与所述第二电信业务系统 301 中配置主 用资源实体和备用资源实体, 然后, 根据主备用关系建立从主用资源实体 到备用资源实体之间数据的复制关系; 所述第一资源分配系统 300与所述 第二资源分配系统 301 可以部署在不同的机房或不同的城市, 这样, 能够 为电信运营商分担业务;
并且, 所述第一资源分配系统 300与所述第二资源分配系统 301互为
主备容灾系统, 当其中一个资源分配系统由于故障而切换到备用资源分配 系统后, 由于终端用户的数据已从主用资源分配系统复制到备用资源分配 系统, 而且备用资源分配系统配置了切换到所述备用资源分配系统的终端 用户群所使用的备用资源实体, 因此, 所述备用资源分配系统可完全自动 地根据已配置的备用资源实体切换到该备用资源分配系统的终端用户所需 使用的备用资源地址, 从而利用所述备用资源实体为切换到备用资源分配 系统的终端用户继续提供业务, 以确保地理容灾场景下业务的连续性。
相应的, 在所述电信业务系统中, 终端用户向所述电信业务系统中的 一个资源分配系统发送的资源分配请求中还携带有请求分配的主用 /备用资 源实体的标识, 接收到终端用户发送的资源分配请求时, 首先根据请求分 配的主用 /备用资源实体的标识确定请求的是主用资源实体还是备用资源实 体, 根据判断结果执行后续相应的操作, 为所述终端用户分配对应的主用 资源实体或备用资源实体。
所述电信业务系统可扩展至包括 N个资源分布系统, N为正整数; 所 述电信业务系统中的 N个资源分布系统可以部署在不同的机房或不同的城 市, 并配置相应的主备用关系, 例如, 所述电信业务系统由一个中心站点 和多个远端站点构成, 中心站点配置主用资源实体, 多个远端站点配置备 用资源实体; 这样, 所述电信业务系统能够为电信运营商分担业务, 并具 有更高层次的地理容灾能力。
实际应用中, 除了计费系统和 CRM系统外, 移动虚拟运营商(Mobile Virtual Network Operator, MVNO )通常不建设自有的电信增值业务平台, 而利用其租用移动网络运营商 (MNO ) 的电信业务平台为其用户提供电信 增值业务, 这种运营模式即多租; 这要求移动网络运营商的电信业务平台 一方面除了为自己的用户提供业务外, 还要为一个或多个 MVNO的终端用 户提供业务。 出于管理、 安全和隐私等方面考虑, MNO和 MVNO运营商
希望共享平台能在一定程度上相互隔离, 需电信业务系统提供商能支持在 一个电信业务系统提供多个虚拟的电信业务系统, 实现不同租户之间的用 户数据及业务数据管理的隔离,同时该系统仍需给宿主 MNO运营商提供统 一的管理视图而不是若干个完全分裂的子系统。
基于此, 本发明可以将资源实体指派给业务提供商 ( Service Provider, SP ), 同时在终端用户群与 SP之间建立关联, 具体说明如下:
所述 SP就是一个利用所述资源分配系统为终端用户提供电信业务的 服务提供商; 当一个资源分配系统需要同时为多个 SP对应的不同终端用户 群提供业务时, 这种模式即为多租。 建设多租系统的电信运营商称为提供 商或宿主, 而租用所述资源分配系统为 SP 所属的终端用户群提供业务的 SP称为租户。 在面向资源的资源分配系统中, 可明确将所述资源分配系统 中的若干资源实体指派给任一 SP, 一旦为某个 SP指派资源实体或资源组, 那么所述 SP的终端用户群只能根据请求分配的资源类型选择对应的资源实 体或从对应的资源组中选择资源实体进行分配; 如果没有为某个 SP明确指 派资源实体或资源组,则所述 SP的终端用户群可根据请求分配的资源类型 从所述资源分配系统中对应资源类型的资源实体或资源组中选择对应的资 源实体; 通过这种资源配置关系, 不仅实现了资源实体与 SP的分配关系, 也简化了资源与号码段分配的设置, 因为不同 SP可以配置相同的号码段, 只要确定了一个终端用户所属的 SP, 那么在该 SP下可按照号码段分配资 源实体即可, 解决了携号转网场景下的配置。
这里, 为确定 SP与终端用户群的对应关系, 所述资源分配系统在每个 终端用户属性中记录该终端用户所属的 SP信息; 当一个新用户被创建时, 所述电信业务系统按照预设规则确定该终端用户所属 SP, 进一步根据所述 SP与资源实体的对应关系选择该终端用户对应的资源实体;而对于所属 SP 没有明确分配某类资源的资源使用请求, 则仍按照全局配置的资源实体与
终端用户群的对应关系来选择终端用户所匹配的资源实体。
上述实施例中, 在多租场景下可实现资源实体按租户的指定分配, 从 不是共享一个数据库集群, 数据库集群在多个数据节点之间分配数据的机 制不是业务层可控的, 从而满足对数据安全性和隐私的保护要求, 同时避 免了应用和业务层釆用其他数据隔离技术所引入的软件复杂度。
本发明实施例在应用层面针对功能性软件应用和 /或硬件应用模块做资 源虚拟化处理, 将功能性软件应用和 /或硬件应用模块分别抽象为不同类型 的资源实体进行统一配置与管理, 并将软件应用和 /或硬件应用模块间的调 用转换为请求资源的服务, 从而降低系统配置与管理的复杂度; 并且, 本 发明实施例能够根据请求分配的资源类型、 终端用户号码、 以及终端用户 群与资源实体的对应关系灵活地进行资源分配, 从而能够满足不同资源粒 度及不同类型资源调配的要求; 并且, 所述资源分配系统提供统一的 URL 接口以供调用端获取某个终端用户访问的资源地址, 然后, 通过所述资源 地址请求资源为所述终端用户提供服务, 从而简化了资源实体的分配过程。 此外, 通过在电信业务系统中配置第一资源分配系统与第二资源分配系统 之间的主备用关系, 可实现系统级地理容灾的平滑切换, 确保业务的连续 性, 并且, 通过配置地理分布的资源实体可实现对资源的合理使用。 术人员根据本发明的技术方案得出其它的实施方式, 同样属于本发明的技 术创新范围。
本领域内的技术人员应明白, 本发明的实施例可提供为方法、 系统、 或计算机程序产品。 因此, 本发明可釆用硬件实施例、 软件实施例、 或结 合软件和硬件方面的实施例的形式。 而且, 本发明可釆用在一个或多个其 中包含有计算机可用程序代码的计算机可用存储介质 (包括但不限于磁盘
存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、 设备(系统)、 和计算机程序 产品的流程图和 /或方框图来描述的。 应理解可由计算机程序指令实现流程 图和 /或方框图中的每一流程和 /或方框、以及流程图和 /或方框图中的流程和 /或方框的结合。 可提供这些计算机程序指令到通用计算机、 专用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器, 使得 在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功 能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理 设备以特定方式工作的计算机可读存储器中, 使得存储在该计算机可读存 储器中的指令产生包括指令装置的制造品, 该指令装置实现在流程图一个 流程或多个流程和 /或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备 上, 使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机 实现的处理, 从而在计算机或其他可编程设备上执行的指令提供用于实现 在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功 能的步骤。
以上所述仅是本发明实施例的实施方式, 应当指出, 对于本技术领域 的普通技术人员来说, 在不脱离本发明实施例原理的前提下, 还可以作出 若干改进和润饰, 这些改进和润饰也应视为本发明实施例的保护范围。 工业实用性 本发明实施例釆用面向资源的架构预先配置多个资源实体, 并确定终 端用户群与资源实体的对应关系; 接收终端用户发送的资源分配请求, 所 述资源分配请求中携带有请求分配的资源类型、 终端用户号码; 根据所述
请求分配的资源类型、 终端用户号码、 以及终端用户群与资源实体的对应 关系, 为所述终端用户分配对应的资源实体; 如此, 实现了基于资源架构 对资源实体进行统一配置与管理; 并能够根据请求分配的资源类型、 终端 用户号码、 以及终端用户群与资源实体的对应关系灵活地进行资源分配, 从而能够满足不同资源粒度及不同类型资源调配的要求。
Claims
1、 一种资源分配方法, 所述方法包括:
预先配置多个资源实体, 并确定终端用户群与所述资源实体的对应关 系;
接收资源分配请求, 所述资源分配请求中携带有请求分配的资源类型 及终端用户号码;
根据所述请求分配的资源类型、 终端用户号码、 以及预先确定的所述 终端用户群与资源实体的对应关系, 为所述终端用户分配对应的资源实体。
2、 根据权利要求 1所述的方法, 其中, 所述预先配置多个资源实体, 包括:
将实现不同功能的软件应用模块和 /或硬件应用模块分别配置为不同 类型的资源实体。
3、 根据权利要求 1所述的方法, 其中, 所述确定终端用户群与资源实 体的对应关系, 包括:
确定终端用户群与单个资源实体的对应关系;
相应的, 所述根据所述请求分配的资源类型、 终端用户号码、 以及预 先确定的所述终端用户群与资源实体的对应关系, 为所述终端用户分配对 应的资源实体, 包括:
根据所述终端用户号码确定所述终端用户所属的终端用户群; 根据所述请求分配的资源类型及所述用户终端群与单个资源实体的对 应关系, 为所述终端用户分配对应的资源实体。
4、 根据权利要求 1所述的方法, 其中, 所述确定终端用户群与资源实 体的对应关系, 包括:
对资源实体进行分类, 并将相同类型的多个资源实体配置为一个资源 组, 确定终端用户群与资源组的对应关系;
相应的, 所述根据所述请求分配的资源类型、 终端用户号码、 以及预 先确定的所述终端用户群与资源实体的对应关系, 为所述终端用户分配对 应的资源实体, 包括:
根据所述终端用户号码确定所述终端用户所属的终端用户群; 根据所述请求分配的资源类型及终端用户群与资源组的对应关系, 确 定所述终端用户对应的资源组, 为所述终端用户分配对应的资源组内的资 源实体。
5、 根据权利要求 3或 4所述的方法, 其中, 所述根据所述终端用户的 号码确定所述终端用户所属的终端用户群, 包括:
预先通过号码头、 号码尾或号码头加号码尾配置方式, 将终端用户号 码配置在所述终端用户所属的终端用户群对应的号码段内;
根据所述终端用户号码以及对应的配置方式, 确定所述终端用户所属 的终端用户群。
6、 根据权利要求 1所述的方法, 其中, 所述为所述终端用户分配对应 的资源实体, 包括:
釆用最大可用优先分配方式、 随机分配方式或按终端用户号码取模方 式为所述终端用户分配对应的资源实体。
7、根据权利要求 1所述的方法, 其中, 所述接收资源分配请求, 包括: 通过统一资源定位服务 URL接口, 接收资源分配请求。
8、 根据权利要求 6所述的方法, 其中, 所述为所述终端用户分配对应 的资源实体之后, 所述方法还包括:
根据 URL接口返回的资源实体分配信息, 获取分配的资源实体的资源 地址;
通过所述资源地址请求资源为所述终端用户提供相应的服务。
9、 根据权利要求 1所述的方法, 其中, 所述方法还包括:
自动探测资源实体的状态变化;
根据资源实体的状态, 添加或删除资源实体。
10、 一种资源分配系统, 所述系统包括: 资源配置模块、 确定模块、 接收模块和资源分配模块; 其中,
所述资源配置模块, 配置为预先配置多个资源实体;
所述确定模块, 配置为确定终端用户群与所述资源配置模块配置的资 源实体的对应关系;
所述接收模块, 配置为接收资源分配请求, 所述资源分配请求中携带 有请求分配的资源类型及终端用户号码;
所述资源分配模块, 配置为根据所述接收模块接受的所述请求分配的 资源类型、 终端用户号码、 以及所述确定模块确定的所述终端用户群与资 源实体的对应关系, 为所述终端用户分配对应的资源实体。
11、 根据权利要求 10所述的系统, 其中, 所述资源配置模块, 配置为 将实现不同功能的软件应用模块和 /或硬件应用模块分别作为不同类型的 资源实体。
12、 根据权利要求 10所述的系统, 其中, 所述确定模块, 配置为确定 终端用户群与单个资源实体的对应关系;
相应的, 所述资源分配模块, 配置为根据所述终端用户号码确定所述 终端用户所属的终端用户群; 根据所述请求分配的资源类型及所述用户终 端群与单个资源实体的对应关系, 为所述终端用户分配对应的资源实体。
13、 根据权利要求 10所述的系统, 其中, 所述资源配置模块, 配置为 对资源实体进行分类, 将相同类型的多个资源实体配置为一个资源组; 确 定终端用户群与资源组的对应关系;
相应的, 所述资源分配模块, 配置为根据所述终端用户号码确定所述 终端用户所属的终端用户群; 根据所述请求分配的资源类型及终端用户群
与资源组的对应关系, 确定所述终端用户对应的资源组, 为所述终端用户 分配对应的资源组内的资源实体。
14、 根据权利要求 12或 13所述的系统, 其中, 所述资源分配模块, 配置为预先通过号码头、 号码尾或号码头加号码尾配置方式, 将终端用户 号码配置在所述终端用户所属的终端用户群对应的号码段内; 根据所述终 端用户号码以及对应的配置方式, 确定所述终端用户所属的终端用户群。
15、 根据权利要求 10所述的系统, 其中, 所述资源分配模块, 配置为 釆用最大可用优先分配方式、 随机分配方式或按终端用户号码取模方式为 所述终端用户分配对应的资源实体。
16、 根据权利要求 10所述的系统, 其中, 所述接收模块, 配置为通过 URL接口, 接收资源分配请求。
17、 根据权利要求 16所述的系统, 其中, 所述系统还包括: 服务提供模块, 配置为根据 URL接口返回的资源实体分配信息, 获取 分配的资源实体的资源地址; 通过所述资源地址请求资源为所述终端用户 提供相应的服务。
18、 根据权利要求 10所述的系统, 其中, 所述系统还包括: 资源守护模块, 配置为自动探测资源实体的状态变化; 并根据资源实 体的状态, 添加或删除资源实体。
19、 一种计算机存储介质, 所述计算机存储介质中存储有计算机可执 行指令, 所述计算机可执行指令用于执行权利要求 1或 9所述的资源分配 方法。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201410307459.6A CN105307130A (zh) | 2014-06-30 | 2014-06-30 | 一种资源分配方法及系统 |
CN201410307459.6 | 2014-06-30 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016000303A1 true WO2016000303A1 (zh) | 2016-01-07 |
Family
ID=55018355
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/085146 WO2016000303A1 (zh) | 2014-06-30 | 2014-08-26 | 一种资源分配方法、系统及计算机存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN105307130A (zh) |
WO (1) | WO2016000303A1 (zh) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106130765B (zh) * | 2016-06-23 | 2019-07-09 | 新华三技术有限公司 | 虚拟桌面分配方法及装置 |
CN106209423B (zh) * | 2016-06-23 | 2019-09-06 | 新华三技术有限公司 | 虚拟桌面分配方法及装置 |
CN110167012A (zh) * | 2018-02-12 | 2019-08-23 | 电信科学技术研究院有限公司 | 一种通信资源管理方法及装置 |
CN108965167A (zh) * | 2018-07-19 | 2018-12-07 | 郑州云海信息技术有限公司 | 一种云资源的分配方法及装置 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1585548A (zh) * | 2004-05-25 | 2005-02-23 | 中兴通讯股份有限公司 | 一种分布式访问位置寄存器vlr的实现方法 |
CN101064559A (zh) * | 2006-04-30 | 2007-10-31 | 华为技术有限公司 | 资源分配方法和系统 |
CN102958166A (zh) * | 2011-08-29 | 2013-03-06 | 华为技术有限公司 | 一种资源分配方法及资源管理平台 |
CN103299312A (zh) * | 2011-02-08 | 2013-09-11 | 株式会社日立制作所 | 数据存储系统及其控制方法 |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5031195B2 (ja) * | 2005-03-17 | 2012-09-19 | 株式会社日立製作所 | ストレージ管理ソフトウェア及びグルーピング方法 |
CN100377603C (zh) * | 2005-04-30 | 2008-03-26 | 华为技术有限公司 | 一种蜂窝系统中按键即说业务的通信资源分配方法、系统及装置 |
CN101094494A (zh) * | 2006-06-19 | 2007-12-26 | 上海贝尔阿尔卡特股份有限公司 | 无线网络中用于对组用户进行无线接入控制的方法及设备 |
CN101631116B (zh) * | 2009-08-10 | 2012-10-17 | 中国科学院地理科学与资源研究所 | 一种分布式双重授权及访问控制方法和系统 |
US8805365B2 (en) * | 2010-01-15 | 2014-08-12 | Apple Inc. | Registration with a mobile telecommunications service provider |
WO2012056490A1 (en) * | 2010-10-25 | 2012-05-03 | Hitachi, Ltd. | Storage apparatus and management method thereof |
-
2014
- 2014-06-30 CN CN201410307459.6A patent/CN105307130A/zh active Pending
- 2014-08-26 WO PCT/CN2014/085146 patent/WO2016000303A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1585548A (zh) * | 2004-05-25 | 2005-02-23 | 中兴通讯股份有限公司 | 一种分布式访问位置寄存器vlr的实现方法 |
CN101064559A (zh) * | 2006-04-30 | 2007-10-31 | 华为技术有限公司 | 资源分配方法和系统 |
CN103299312A (zh) * | 2011-02-08 | 2013-09-11 | 株式会社日立制作所 | 数据存储系统及其控制方法 |
CN102958166A (zh) * | 2011-08-29 | 2013-03-06 | 华为技术有限公司 | 一种资源分配方法及资源管理平台 |
Also Published As
Publication number | Publication date |
---|---|
CN105307130A (zh) | 2016-02-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20220107848A1 (en) | Edge service providing method and apparatus, and device | |
CN107181808B (zh) | 一种私有云系统及运行方法 | |
US20240176672A1 (en) | Systems and methods providing serverless dns integration | |
US10158579B2 (en) | Resource silos at network-accessible services | |
WO2015172362A1 (zh) | 一种网络功能虚拟化网络系统、数据处理方法及装置 | |
US8972519B2 (en) | Optimization of multimedia service over an IMS network | |
CN112099938A (zh) | 使用多维元数据标签集确定分布式计算环境中的资源分配 | |
RU2683630C2 (ru) | Способ обновления дескриптора сетевой службы nsd и устройство | |
CN106817432B (zh) | 云计算环境下虚拟资源弹性伸展的方法,系统和设备 | |
CN109995641B (zh) | 一种信息处理方法、计算节点和存储介质 | |
CN103607430A (zh) | 一种网络处理的方法和系统及网络控制中心 | |
CN106302074B (zh) | 一种虚拟化网络功能vnf的迁移方法及装置 | |
CN108347343B (zh) | 一种策略管理方法、装置和系统 | |
CN111857873A (zh) | 一种实现云原生容器网络的方法 | |
EP3125468B1 (en) | Cloud application processing method and application deployment method and relevant apparatus and system | |
WO2021109750A1 (zh) | 节点管理方法、装置、设备、存储介质和系统 | |
WO2016095524A1 (zh) | 资源分配方法及装置 | |
CN110727738B (zh) | 基于数据分片的全局路由系统、电子设备及存储介质 | |
CN106911741B (zh) | 一种虚拟化网管文件下载负载均衡的方法及网管服务器 | |
WO2018196843A1 (zh) | 资源请求方法及装置 | |
CN115150410B (zh) | 多集群访问方法和系统 | |
US20160183229A1 (en) | Ip phone network system, server apparatus, ip exchange and resource capacity expansion method | |
WO2016000303A1 (zh) | 一种资源分配方法、系统及计算机存储介质 | |
WO2022007908A1 (zh) | 网元设备间业务协同的方法和网元设备 | |
CN108738027B (zh) | 一种网络处理方法、资源管理系统及网络设备 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14896921 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 14896921 Country of ref document: EP Kind code of ref document: A1 |