WO2014029308A1 - 资源分配方法和装置 - Google Patents
资源分配方法和装置 Download PDFInfo
- Publication number
- WO2014029308A1 WO2014029308A1 PCT/CN2013/081743 CN2013081743W WO2014029308A1 WO 2014029308 A1 WO2014029308 A1 WO 2014029308A1 CN 2013081743 W CN2013081743 W CN 2013081743W WO 2014029308 A1 WO2014029308 A1 WO 2014029308A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- attribute
- node
- nodes
- load
- current
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/52—Allocation or scheduling criteria for wireless resources based on load
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
- H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
- H04W16/10—Dynamic resource partitioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/08—Testing, supervising or monitoring using real traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/08—Load balancing or load distribution
- H04W28/09—Management thereof
- H04W28/0958—Management thereof based on metrics or performance parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/12—Access point controller devices
Definitions
- the present invention relates to the field of communications, and in particular to a resource allocation method and apparatus.
- the radio network controller Radio Network Controller, RNC for short
- RNC Radio Network Controller
- Control Plane (referred to as CP), mainly used to process transmission signaling and wireless air interface control plane protocols;
- CP and UP can be divided into two categories, one is public CP, public UP, mainly used to deal with the protocols of their respective public parts, such as: protocols for cells, public channels, etc.; the other is dedicated CP, dedicated
- the UP function is mainly used to process the related functions of the user equipment (User Equipment, UE for short).
- the backup mode of the public CP and the public UP is 1+1 backup.
- the dedicated CP and the dedicated UP are through the resource pool, that is, there are dedicated CP resource pools and dedicated UP resource pools.
- the traditional dedicated CP resource pool and the dedicated UP resource pool have a static configuration ratio when the actual network is operated, and the number and proportion of the CP resource pool and the UP resource pool are solidified.
- the control of the RNC thus exacerbates the load on the control plane signaling processing. From the analysis of business models, smartphone users often send and receive emails, and instant messaging (IM) messaging calls. The interval between sending and receiving may have a time interval of a few seconds.
- the present invention provides a resource allocation method and apparatus to solve at least the technical problem of resource waste caused by static configuration of resources in a resource pool in the prior art.
- a resource allocation method including: monitoring a plurality of nodes of a shared resource pool, where the plurality of nodes include a node having a property of CP and a node having an attribute of UP; adjusting according to a monitoring result An attribute of one or more of the plurality of nodes.
- adjusting the attributes of some or all of the plurality of nodes according to the monitoring result includes: when detecting that the total load of the node whose current attribute is CP is greater than a first predetermined threshold, and the node whose current attribute is UP When the total load is less than the second predetermined threshold, adjusting one or more attributes of the node whose current attribute is UP to CP; and/or when detecting that the total load of the node whose current attribute is UP is greater than a third predetermined threshold, And when the total load of the node whose current attribute is CP is less than the second predetermined threshold, the attribute of one or more nodes whose current attribute is CP is adjusted to UP.
- the ratio between the number of users currently accessing the above system and the maximum number of users each node capable of supporting CP is used as the current total load of the node whose attribute is CP; and/or according to the current CPU
- the load and media plane traffic determine the current total load of the node whose attribute is UP.
- the node whose attributes are adjusted is one or more nodes that have the least current load.
- the method before adjusting the attributes of one or more of the plurality of nodes, the method further includes: determining, after adjusting the attributes of the one or more nodes, the remaining one or more adjusted Whether the nodes with the same attribute of the node can bear the traffic load corresponding to the attribute.
- adjusting an attribute of one or more of the plurality of nodes includes: sending an attribute adjustment instruction to each node to be adjusted, wherein the attribute adjustment instruction is used to indicate that the node changes its current attribute; If the adjustment completion indication message returned by the node is not received within the predetermined time, the attribute of the node is restored to the attribute before the adjustment.
- the monitoring of the plurality of nodes of the shared resource pool includes: each node in the shared resource pool periodically reports its current load and its own processing capability; or the resource configuration management module periodically detects the shared resource pool. The current load of each node and its own processing power.
- the CP is a dedicated CP
- the UP is a dedicated UP.
- a resource allocation apparatus including: a monitoring unit, configured to monitor a plurality of nodes of a shared resource pool, wherein the plurality of nodes include a node having a property of CP and a node having an attribute of UP
- the adjustment unit is set to adjust the attributes of one or more of the plurality of nodes according to the monitoring result.
- the adjusting unit includes: a first adjusting module, configured to: when detecting that a total load of a node whose current attribute is CP is greater than a first predetermined threshold, and a total load of a node whose current attribute is UP is smaller than a second predetermined At the threshold, adjusting one or more attributes of the node whose current attribute is UP to CP; and/or a second adjustment module, configured to when detecting that the total load of the node whose current attribute is UP is greater than a third predetermined threshold, And when the total load of the node whose current attribute is CP is less than the second predetermined threshold, the attribute of one or more nodes whose current attribute is CP is adjusted to UP.
- a first adjusting module configured to: when detecting that a total load of a node whose current attribute is CP is greater than a first predetermined threshold, and a total load of a node whose current attribute is UP is smaller than a second predetermined At the threshold, adjusting one
- the adjusting unit further includes: a sending module, configured to send an attribute adjustment instruction to each node to be adjusted, where the attribute adjusting instruction is used to instruct the node to change its current attribute; and the recovery module is set to be scheduled If the adjustment completion indication message returned by the node is not received within the time, the attribute of the node is restored to the attribute before the adjustment.
- a sending module configured to send an attribute adjustment instruction to each node to be adjusted, where the attribute adjusting instruction is used to instruct the node to change its current attribute
- the recovery module is set to be scheduled If the adjustment completion indication message returned by the node is not received within the time, the attribute of the node is restored to the attribute before the adjustment.
- the CP node and the UP node are allocated by sharing the resource pool, thereby
- Dynamic switching can be implemented between the CP node and the UP. As long as the resources in the resource pool are monitored in real time and the node attributes are switched according to the monitoring result, the purpose of effectively utilizing the resources can be achieved.
- the technical problem of resource waste caused by static configuration of resources in the resource pool in the prior art is solved in the above manner, and the technical effect of effectively utilizing resources and improving service processing capability is achieved.
- FIG. 1 is a preferred flow chart of a resource allocation method according to an embodiment of the present invention
- FIG. 2 is another preferred flow chart of a resource allocation method according to an embodiment of the present invention
- FIG. 4 is a block diagram of another preferred structure of a resource allocating device according to an embodiment of the present invention
- FIG. 5 is still another preferred embodiment of a resource allocating device according to an embodiment of the present invention.
- Structure diagram is still another preferred flowchart of a resource allocation method according to an embodiment of the present invention.
- FIG. 7 is a further preferred flowchart of a resource allocation method according to an embodiment of the present invention;
- FIG. 8 is a sharing according to an embodiment of the present invention.
- FIG. 9 is a schematic diagram of a preliminary allocation of a shared resource pool according to an embodiment of the present invention;
- FIG. 10 is a flowchart of a CP to UP attribute switching process according to an embodiment of the present invention; Flowchart of the UP to CP attribute switching process of the embodiment.
- the embodiment of the present invention provides a preferred resource allocation method. As shown in FIG. 1 , the method includes the following steps: Step S102: Monitor multiple nodes of a shared resource pool, where multiple nodes include nodes with attributes of CP and The node whose attribute is UP; Step S104: Adjust the attributes of one or more of the plurality of nodes according to the monitoring result.
- the CP node and the UP node are allocated by sharing the resource pool, so that dynamic switching can be implemented between the CP node and the UP, as long as the resources in the resource pool are monitored in real time and monitored according to the As a result, the switching of node attributes can achieve the purpose of effectively utilizing resources.
- the technical problem of resource waste caused by static configuration of resources in the resource pool in the prior art is solved in the above manner, and the technical effect of effectively utilizing resources and improving service processing capability is achieved.
- the property is adjusted to UP.
- the load is equalized, and gp is mainly adjusted by the processing load of the node of each attribute.
- part of the plurality of nodes is adjusted according to the monitoring result or
- the properties of all nodes include: 1) when it is detected that the total load of the node whose current attribute is CP is greater than the first predetermined threshold, and the total load of the node whose current attribute is UP is less than the second predetermined threshold, one or more current attributes are UP
- the properties of the node are adjusted to CP; and/or
- the node's properties are adjusted to UP.
- the load balancing of nodes in the resource pool can be effectively realized by adjusting the load according to the above.
- the load can be determined by different basis. For example, for the node with CP attribute, the number of users of the current access system can be between the number of users that can be supported by each node whose attribute is CP.
- the ratio is taken as the current total load of the node whose attribute is CP; for the node of the UP attribute, the current total load of the node whose attribute is UP can be determined according to the current CPU load and the media plane traffic.
- a preferred processing method is to select the node with the lowest current load for adjustment. For example, when the load of the CP is too large and some partial UP nodes need to be converted into CP nodes, one or more nodes with the least load in the UP node can be selected for conversion. That is, the node whose attribute is adjusted is one or more nodes with the lowest current load.
- adjusting the attributes of one or more of the plurality of nodes includes the following steps: Step S202: Send an attribute adjustment instruction to each node to be adjusted, where the attribute adjustment instruction Used to instruct the node to change its current attributes; Step S204: If the adjustment completion indication message returned by the node is not received within a predetermined time, the attribute of the node is restored to the attribute before the adjustment.
- the multiple nodes that monitor the shared resource pool may be in the form of active reporting by the node, or may be actively checked by the resource configuration management module. Preferably, one or more of the following methods may be used to monitor multiple nodes of the shared resource pool.
- Each node in the shared resource pool periodically reports its current load and its own processing capability
- the resource configuration management module periodically detects the current load of each node in the shared resource pool and its own processing capability.
- the CP is a dedicated CP and the UP is a dedicated UP.
- a resource allocation device is also provided, which is used to implement the foregoing embodiments and preferred embodiments, and has not been described again.
- the term "unit” or “module” may implement a combination of software and/or hardware of a predetermined function.
- the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and conceivable.
- FIG. 3 is a block diagram showing a preferred structure of a resource allocating apparatus according to an embodiment of the present invention.
- the monitoring unit 302 includes an adjusting unit 302 and an adjusting unit 304.
- the structure will be described below.
- the monitoring unit 302 is configured to monitor a plurality of nodes of the shared resource pool, where the plurality of nodes include a node with the attribute CP and a node with the attribute UP;
- the adjusting unit 304 is coupled with the monitoring unit 302, and is set to adjust according to the monitoring result.
- the adjusting unit includes: a first adjusting module 402 coupled to the monitoring unit 302, configured to when detecting that the total load of the node whose current attribute is CP is greater than a first predetermined threshold And when the total load of the node whose current attribute is UP is less than the second predetermined threshold, the attributes of the one or more nodes whose current attribute is UP are adjusted to CP; and/or the second adjustment module 404 is coupled to the monitoring unit 302. And setting, when the total load of the node whose current attribute is UP is greater than the third predetermined threshold, and the total load of the node whose current attribute is CP is less than the second predetermined threshold, one or more current attributes are CP The properties of the node are adjusted to UP.
- the adjusting unit may further include: a sending module 502, configured to send an attribute adjustment instruction to each node to be adjusted, where the attribute adjustment instruction is used to indicate that the node is modified
- the current module is changed to the current attribute
- the recovery module 504 is coupled to the sending module 502, and is configured to restore the attribute of the node to the attribute before the adjustment if the adjustment completion indication message returned by the node is not received within a predetermined time.
- the resource utilization rate and the overall processing capability of the system are improved, and the number of redundant boards is reduced.
- the control plane and the user plane processing board share the resource pool of the present application are proposed. Specifically, the original independent dedicated CP resource pool and the dedicated UP resource pool are merged to form a large resource pool.
- Each node in the resource pool is identical, and each node can be used as a dedicated CP or as a dedicated UP depending on the load of the current system.
- a node in the resource pool that is used as a CP function can be dynamically switched, used as an UP function, or when the entire CP is used.
- the load is high, and when the UP load can withstand, the attributes of a node used as the UP function in the resource pool can be switched and used as the CP function. Specifically, as shown in FIG.
- the resource allocation method includes the following steps: Step S602: Calculate the number of nodes of the dedicated CP and the number of nodes of the dedicated UP according to the system capacity, and configure the nodes into shared resource pool nodes (preferably , you do not need to set the external properties of each node). Step S604: The system periodically performs load monitoring on each node in the resource pool. For CP and UP, the load may be determined according to different conditions. For example, for a node with a CP attribute, the load may be, but is not limited to, the current number of users.
- Step S606 When the system is powered on, the configuration of the resource pool is read, and each node is assigned an initial attribute, that is, the initial setting node is used as the CP attribute or the UP attribute;
- Step S608 During the system running, the resource Any node in the pool needs to report the current load and total processing capacity of the node periodically.
- Step S610 The system periodically performs load evaluation.
- the system may A predetermined algorithm is used to select a node for dynamic switching of node attributes.
- N nodes in a resource pool are taken as an example for description.
- the resource allocation method includes the following steps: Step S702: Configure a board in the shared resource pool and related resource attribution in the background, so that the resource configuration management module in the foreground knows the resource pool in which the capacity is configured. Step S704: As shown in FIG.
- a resource configuration management module is deployed on the master control board for globally evaluating the load in the resource pool and making corresponding decisions.
- one resource may be deployed in each resource pool node.
- the configuration management agent is configured to calculate the load of the local node, and then reported to the resource configuration management module, and the resource configuration management brings a decision command for receiving the resource configuration management module.
- Step S706 The entire system is powered on, and the resource configuration management module obtains resource pool information. As shown in FIG. 9, according to the traditional configuration, an initial attribute is set to any node in the resource pool, that is, whether the node is a CP attribute or UP attribute.
- Step S708 Each node in the resource pool reports the processing capability and the current load of the local node to the resource configuration management module of the master control board through the resource configuration agent timing (for example, every 2 s).
- Step S710 The resource configuration management module of the master control module periodically performs load evaluation, which mainly includes:
- Embodiment 1 the resource pool board is converted from the control plane CP to the user plane UP. As shown in FIG. 1
- Step S1002 The resource configuration management module is configured according to the following steps: After the load is evaluated, the following decisions are made according to different scenarios: Scenario A: If the current total CP load is a light load state compared to the total processing capacity (preferably, the threshold can be determined by configuration), the CP node with the least load in the resource pool is powered off; Scene B: If current The total CP load is a non-light load state compared to the total processing capacity, but the processing capacity remains, and the status quo is maintained; Scenario C: If the current total UP load is a high load state compared to the total processing capacity, the processing capability is no longer Support, you need to switch some CP nodes in the system to the UP attribute, then do the following:
- S1 Determine whether there is an UP node that has been powered off in the resource pool, and if so, directly restore the powered UP node to power on;
- Step S1004 If the total processing capacity of the remaining CP after the calculation of the CP node is insufficient to support the current CP load, the status is maintained.
- Step S1004 After the resource configuration management module decides that the CP attribute needs to be switched to UP, the resource configuration proxy sends a property switching command to the resource configuration proxy of the CP node that needs to be switched;
- Step S1006 After receiving the attribute switching command, the resource configuration proxy gives the CP The service sends a pre-notification message, informing the node that the attribute is switched to UP immediately, and setting a waiting timer, the timer is used to determine whether the handover can be successfully completed within a predetermined time; after receiving the CP service, the CP service determines the current Whether the service volume and the traffic pattern on the CP node are allowed to be switched. If the traffic is allowed, the related service migration is started. If the service after the service is completed, the resource configuration proxy returns the attribute switching response message.
- Step S1008 The resource configuration agent determines The
- the resource configuration agent performs the switching of the running software to run the UP software; and then notifies the resource configuration management module to update the information and the related node status; 2) If the service in the response message indicates that the current CP node cannot perform the attribute switching due to some conditions, the resource configuration agent terminates the final switching action, and then notifies the resource configuration management module to perform state rollback, and the CP node attribute is still a CP.
- the resource pool board is converted from the user plane UP to the control plane CP. As shown in FIG.
- the UP-to-CP attribute switching process includes the following steps: Step S1102: The resource configuration management module is configured according to the following steps: After the load is evaluated, the following decisions are made according to different scenarios - Scenario A: If the current total UP load is a light load state compared to the total processing capacity (preferably, the threshold can be determined by configuration), then the resource pool will be The lowest UP node is powered off; Scenario B: If the current total UP load is a non-light load state compared to the total processing capacity but the processing capacity remains, keep the status quo; Scenario C: If the current total CP load phase If the total processing capacity is a high-load state and the processing capability is unsupported, you need to switch some of the UP nodes in the system to the CP attributes. Then, do the following: S1: Determine whether there are CP nodes that have been powered off in the resource pool. If yes, restore the powered-up CP node to power-on.
- Scenario A If the current total UP load is
- Step S4 If the total processing capacity of the remaining UP after removing the computing power of the UP node is insufficient to support the current UP load, the current status is maintained.
- Step S1104 After the resource configuration management module decides that the UP attribute needs to be switched to the CP, the attribute configuration command is sent to the resource configuration agent of the UP node that needs to be switched.
- Step S1106 After receiving the attribute switching command, the resource configuration agent gives the UP The service sends a pre-notification message, informing the node that the attribute is switched to the CP, and setting a wait timer.
- Step S1108 The resource configuration agent determines the response message, which mainly includes: 1) if the service clears that the UP node can perform attribute switching in the response message, the resource configuration agent runs the software. Switching, running the CP software; then notifying the resource configuration management module to update the information and related node status;
- a software is also provided for performing the technical solutions described in the above embodiments and preferred embodiments.
- a storage medium is provided, the software being stored, including but not limited to: an optical disk, a floppy disk, a hard disk, a rewritable memory, and the like.
- the present invention achieves the following technical effects: the CP node and the UP node are allocated by sharing the resource pool, so that dynamic switching can be implemented between the CP node and the UP, as long as the resource pool is
- the real-time monitoring of the resources in the real-time and the switching of the node attributes according to the monitoring results can achieve the purpose of effectively utilizing resources.
- the technical problem of waste of resources in the resource pool in the prior art is solved in the above manner, and the technical effect of effectively utilizing resources and improving the processing capability of the service is achieved.
- modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
- the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
- the invention is not limited to any specific combination of hardware and software.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
本发明公开了一种资源分配方法和装置,其中,该方法包括:监控共享资源池的多个节点,其中,多个节点包括属性为CP的节点和属性为UP的节点;根据监控结果,调整多个节点中的一个或多个节点的属性。本发明解决了现有技术中资源池的资源静态配置而造成资源浪费的技术问题,达到了有效利用资源和提高业务处理能力的技术效果。
Description
资源分配方法和装置
技术领域 本发明涉及通信领域, 具体而言, 涉及一种资源分配方法和装置。 背景技术 在移动通信***中, 无线网络控制器 (Radio Network Controller, 简称为 RNC) 根据处理协议和功能的不同可以将业务处理单板分为两类:
1 ) 控制面处理板 (Control Plane, 简称为 CP), 主要用于处理传输信令和无线空 口控制平面协议;
2) 用户面处理板 (User Plane, 简称为 UP), 主要用于处理无线用户平面协议。 其中, CP和 UP又各自可以分为两类, 一类是公共 CP、 公共 UP, 主要用于处理 各自公共部分的协议, 例如: 小区、 公共信道等的协议; 另外一类是专用 CP、 专用 UP, 主要用于处理具体的专用用户设备 (User Equipment, 简称为 UE) 相关的功能。 公共 CP和公共 UP的备份方式是 1+1备份, 专用 CP和专用 UP则是通过资源池的方 式, 即有专用 CP资源池和专用 UP资源池。 传统的专用 CP资源池和专用 UP资源池,在实际网络运营的时候, 都有一套静态 的配置比例, 固化了 CP资源池和 UP资源池的数目和比例。随着智能终端价格下降和 Android***、智能手机的推广, 网络中智能终端的数目越来越多, 然而, 智能终端往 往由于节电的需要, 会自行发起状态的变更, 其行为不受限于 RNC的控制, 从而加剧 了控制面信令处理的负荷。 从业务模式上分析, 智能手机用户会经常收发邮件, 进行 即时消息 (Instant Messaging, 简称为 IM) 消息通话等。 收发的时间间隔可能有几秒 的时间间隔。 间隔期间智能手机为了省电一般会主动释放信令连接, 进入空闲 (idle) 模式。 这样会造成很多的连接 /释放, 占用网络资源, 造成网络拥塞, 对控制器造成控 制面 CP和用户面 UP的负荷增加。 鉴于传统的资源池中节点的分配采用固化的方式造成资源无法合理利用, 造成资 源的浪费, 也渐渐难以满足现有的无线网络中复杂多变的业务分布和信令风暴。 针对上述的问题, 目前尚未提出有效的解决方案。
发明内容 本发明提供了一种资源分配方法和装置, 以至少解决现有技术中资源池的资源静 态配置而造成资源浪费的技术问题。 根据本发明的一个方面, 提供了一种资源分配方法, 包括: 监控共享资源池的多 个节点, 其中, 上述多个节点包括属性为 CP的节点和属性为 UP的节点; 根据监控结 果, 调整上述多个节点中的一个或多个节点的属性。 优选地, 根据监控结果, 调整上述多个节点中的部分或全部节点的属性包括: 当 检测到当前属性为 CP的节点的总的负荷大于第一预定阈值时,且当前属性为 UP的节 点的总的负荷小于第二预定阈值时, 将一个或多个当前属性为 UP的节点的属性调整 为 CP;和 /或当检测到当前属性为 UP的节点的总的负荷大于第三预定阈值时,且当前 属性为 CP的节点的总的负荷小于第二预定阈值时,将一个或多个当前属性为 CP的节 点的属性调整为 UP。 优选地, 将当前接入上述***的用户数与每个属性为 CP 的节点所能支持的最大 用户数之间的比值作为属性为 CP的节点当前的总的负荷;和 /或根据当前 CPU的负荷 以及媒体面流量确定属性为 UP的节点当前的总的负荷。 优选地, 属性被调整的节点是当前负荷最小的一个或多个节点。 优选地,在调整上述多个节点中的一个或多个节点的属性之前, 上述方法还包括: 判断在将上述一个或多个节点的属性进行调整后, 剩余的与该被调整的一个或多个节 点的属性相同的节点是否可以承载该属性所对应的业务负荷。 优选地, 调整上述多个节点中的一个或多个节点的属性包括: 向每个待调整的节 点发送属性调整指令,其中, 上述属性调整指令用于指示该节点改变自身当前的属性; 如果在预定时间内未收到该节点返回的调整完成指示消息, 则将该节点的属性恢复为 进行调整前的属性。 优选地, 监控共享资源池的多个节点包括: 上述共享资源池中的每个节点周期性 地上报自身当前的负荷和自身的处理能力; 或者资源配置管理模块周期性地检测上述 共享资源池中每个节点的当前的负荷和自身的处理能力。 优选地, 上述 CP为专用 CP, 上述 UP为专用 UP。
根据本发明的另一方面, 提供了一种资源分配装置, 包括: 监控单元, 设置为监 控共享资源池的多个节点, 其中, 上述多个节点包括属性为 CP 的节点和属性为 UP 的节点; 调整单元, 设置为根据监控结果, 调整上述多个节点中的一个或多个节点的 属性。 优选地, 上述调整单元包括: 第一调整模块, 设置为当检测到当前属性为 CP 的 节点的总的负荷大于第一预定阈值时, 且当前属性为 UP的节点的总的负荷小于第二 预定阈值时,将一个或多个当前属性为 UP的节点的属性调整为 CP;和 /或第二调整模 块, 设置为当检测到当前属性为 UP的节点的总的负荷大于第三预定阈值时, 且当前 属性为 CP的节点的总的负荷小于第二预定阈值时,将一个或多个当前属性为 CP的节 点的属性调整为 UP。 优选地, 上述调整单元还包括: 发送模块, 设置为向每个待调整的节点发送属性 调整指令, 其中, 上述属性调整指令用于指示该节点改变自身当前的属性; 恢复模块, 设置为在预定时间内未收到该节点返回的调整完成指示消息的情况下, 将该节点的属 性恢复为进行调整前的属性。 在本发明实施例中,通过共享资源池的方式来分配 CP节点和 UP节点, 从而使得
CP节点和 UP之间可以实现动态的切换, 只要对资源池中的资源进行实时的监控并根 据监控的结果实现节点属性的切换便可以达到有效利用资源的目的。 通过上述方式解 决了现有技术中资源池的资源静态配置而造成资源浪费的技术问题, 达到了有效利用 资源和提高业务处理能力的技术效果。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部分, 本发 明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的不当限定。 在附图 中- 图 1是根据本发明实施例的资源分配方法的一种优选流程图; 图 2是根据本发明实施例的资源分配方法的另一种优选流程图; 图 3是根据本发明实施例的资源分配装置的一种优选结构框图; 图 4是根据本发明实施例的资源分配装置的另一种优选结构框图; 图 5是根据本发明实施例的资源分配装置的又一种优选结构框图;
图 6是根据本发明实施例的资源分配方法的又一种优选流程图; 图 7是根据本发明实施例的资源分配方法的又一种优选流程图; 图 8是根据本发明实施例的共享资源池***的优选结构示意图; 图 9是根据本发明实施例的共享资源池初始分配的优选示意图; 图 10是根据本发明实施例的 CP转 UP属性切换处理流程图; 图 11是根据本发明实施例的 UP转 CP属性切换处理流程图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在不冲突的 情况下, 本申请中的实施例及实施例中的特征可以相互组合。 本发明实施例提供了一种优选的资源分配方法, 如图 1所示, 该方法包括以下步 骤: 步骤 S102: 监控共享资源池的多个节点, 其中, 多个节点包括属性为 CP的节点 和属性为 UP的节点; 步骤 S104: 根据监控结果, 调整多个节点中的一个或多个节点的属性。 在上述优选实施方式中,通过共享资源池的方式来分配 CP节点和 UP节点, 从而 使得 CP节点和 UP之间可以实现动态的切换,只要对资源池中的资源进行实时的监控 并根据监控的结果实现节点属性的切换便可以达到有效利用资源的目的。 通过上述方 式解决了现有技术中资源池的资源静态配置而造成资源浪费的技术问题, 达到了有效 利用资源和提高业务处理能力的技术效果。 对于上述根据监控结果, 调整多个节点中的部分或全部节点的属性主要有两种情 况, 一种就是将属性为 CP的节点的属性调整为 UP, 另一种就是将属性为 UP的节点 的属性调整为 UP。对于上述的这种调整主要是为了实现负荷的均衡, gp, 主要通过每 种属性的节点的处理负荷进行相应的调整, 在一个优选实施方式中, 根据监控结果, 调整多个节点中的部分或全部节点的属性包括:
1 ) 当检测到当前属性为 CP的节点的总的负荷大于第一预定阈值时, 且当前属性 为 UP的节点的总的负荷小于第二预定阈值时,将一个或多个当前属性为 UP的节点的 属性调整为 CP; 和 /或
2) 当检测到当前属性为 UP的节点的总的负荷大于第三预定阈值时, 且当前属性 为 CP的节点的总的负荷小于第二预定阈值时,将一个或多个当前属性为 CP的节点的 属性调整为 UP。 通过上述按照各自的负荷进行调整的方式可以有效实现资源池中节点的负荷均 衡。 对于 CP和 UP而言, 负荷的确定可以采用不同的依据, 例如, 对于 CP属性的节 点, 可以将当前接入***的用户数与每个属性为 CP 的节点所能支持的最大用户数之 间的比值作为属性为 CP的节点当前的总的负荷; 对于 UP属性的节点,可以根据当前 CPU的负荷以及媒体面流量确定属性为 UP的节点当前的总的负荷。 为了保证对节点的变动最小, 在确定需要对节点的属性进行调整的时候, 一种优 选的处理方式是选择当前负荷最小的节点进行调整。 例如, 当 CP 的负荷过大需要将 部分的 UP节点转换为 CP节点时,可以选择 UP节点中负荷最小的一个或多个节点进 行转换。 即, 属性被调整的节点是当前负荷最小的一个或多个节点。 考虑到将一种属性的节点调整为另外一种属性之后, 被调整的节点所对应的节点 的数量可能难以承载当前该节点的业务, 这样的调整显然是不合理的, 为了避免这种 情况的出现, 可以在进行调整之前进行如下判断: 判断在将一个或多个节点的属性进 行调整后, 剩余的与该被调整的一个或多个节点的属性相同的节点是否可以承载该属 性所对应的业务负荷。 在实际应用时, 可能会出现调整异常的状况, 因此可以在调整的过程增加一个回 退操作, 例如, 需要将一个 CP节点调整为 UP节点, 然而在调整的过程中, 该节点未 调整成功, 这样可能会出现异常, 因此, 可以设定一个定时器, 如果在预定时间内未 收到该节点返回的调整成功的消息, 则还将该节点的属性设置为 CP。在一个优选实施 方式中, 如图 2所示, 调整多个节点中的一个或多个节点的属性包括以下步骤: 步骤 S202: 向每个待调整的节点发送属性调整指令, 其中, 属性调整指令用于指 示该节点改变自身当前的属性;
步骤 S204: 如果在预定时间内未收到该节点返回的调整完成指示消息, 则将该节 点的属性恢复为进行调整前的属性。 监控共享资源池的多个节点可以采用节点主动上报的方式, 也可以采取资源配置 管理模块主动检查的方式, 优选地, 可以但不限于采用以下方式之一监控共享资源池 的多个节点-
1 )共享资源池中的每个节点周期性地上报自身当前的负荷和自身的处理能力; 或 者
2)资源配置管理模块周期性地检测共享资源池中每个节点的当前的负荷和自身的 处理能力。 在上述各个优选实施方式中, CP是专用 CP, UP是专用 UP。 在本实施例中还提供了一种资源分配装置, 该装置用于实现上述实施例及优选实 施方式, 已经进行过说明的不再赘述。 如以下所使用的, 术语"单元"或者"模块"可以 实现预定功能的软件和 /或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来 实现, 但是硬件, 或者软件和硬件的组合的实现也是可能并被构想的。 图 3是根据本 发明实施例的资源分配装置的一种优选结构框图, 如图 3所示, 包括: 监控单元 302 和调整单元 304, 下面对该结构进行说明。 监控单元 302, 设置为监控共享资源池的多个节点, 其中, 多个节点包括属性为 CP的节点和属性为 UP的节点; 调整单元 304, 与监控单元 302耦合, 设置为根据监控结果, 调整多个节点中的 一个或多个节点的属性。 在一个优选实施方式中, 如图 4所示, 调整单元包括: 第一调整模块 402, 与监 控单元 302耦合, 设置为当检测到当前属性为 CP的节点的总的负荷大于第一预定阈 值时, 且当前属性为 UP的节点的总的负荷小于第二预定阈值时, 将一个或多个当前 属性为 UP的节点的属性调整为 CP; 和 /或第二调整模块 404, 与监控单元 302耦合, 设置为当检测到当前属性为 UP的节点的总的负荷大于第三预定阈值时, 且当前属性 为 CP的节点的总的负荷小于第二预定阈值时,将一个或多个当前属性为 CP的节点的 属性调整为 UP。 在一个优选实施方式中, 如图 5所示, 调整单元还可以包括: 发送模块 502, 设 置为向每个待调整的节点发送属性调整指令, 其中, 属性调整指令用于指示该节点改
变自身当前的属性; 恢复模块 504, 与发送模块 502耦合, 设置为在预定时间内未收 到该节点返回的调整完成指示消息的情况下, 将该节点的属性恢复为进行调整前的属 性。 本发明提供了一种优选的实施例来进一步对本发明进行解释,但是值得注意的是, 该优选实施例只是为了更好的描述本发明, 并不构成对本发明不当的限定。 为了解决传统的固化配置无法适应现有的无线网络业务的多变性的要求的问题, 以提高资源的利用率和***的整体处理能力, 降低冗余单板数量,在 CP和 UP都采用 同种物理单板的前提下提出了本申请的控制面、 用户面处理板共享资源池的方式, 具 体的就是指将原先独立的专用 CP资源池和专用 UP资源池进行融合形成一个大的资源 池。 其中, 资源池中的每个节点都完全相同, 同时依据当前***的负荷, 每个节点可 以用作专用 CP, 也可以用作专用 UP。 例如, 随着***的正常运行, 当整个 UP的负荷很高, 而 CP负荷可以承受时, 可 以将资源池中某个用作 CP功能的节点进行动态切换, 用作 UP功能, 或者当整个 CP 的负荷很高,而 UP的负荷可以承受时,可以将资源池中某个用作 UP功能的节点的属 性进行切换, 用作 CP功能。 具体的, 如图 6所示, 该资源分配方法包括以下步骤: 步骤 S602:根据***容量计算所需的专用 CP的节点数目和专用 UP的节点数目, 将这些节点配置成共享资源池节点 (优选的, 不需要设置每个节点的对外属性)。 步骤 S604: ***定时对资源池中的每个节点进行负荷监控; 对于 CP和 UP来说, 可以依据不同的条件来确定负荷, 例如, 对于 CP属性的节点, 负荷可以但不局限于 当前用户数与单节点支持的最大用户数之间的比例的归一化负荷; 对于 UP属性节点, 负荷可以是将 CPU负荷、 媒体面流量等加权后得到的归一化负荷。 步骤 S606: 在***上电控制时, 读取资源池的配置, 同时给每个节点分配一个初 始属性, 即, 初始设置节点用作 CP属性还是 UP属性; 步骤 S608: 在***运行过程中, 资源池中的任意一个节点都需要定时上报本节点 的当前负荷和总的处理能力。 步骤 S610: ***周期性地进行负荷评估, 当发现 CP资源和 UP资源的负荷出现 不匹配时, 即, 当前***网络运行情况导致某一方资源不够, 而另一方则仍然有很大 剩余时, 可以采用预定的算法选择某个节点进行节点属性的动态切换。
下面将结合两个具体的实施例进行说明, 在本优选实施方式中以资源池有 N个节 点为例进行说明。 如图 7所示, 该资源分配方法包括以下步骤: 步骤 S702: 后台配置共享资源池中的单板和相关的资源归属, 使得前台的资源配 置管理模块知道配置了多大容量的资源池。 步骤 S704: 如图 8所示, 在总控单板部署一个资源配置管理模块, 用于全局评估 资源池中的负荷并做相应的判决; 优选地, 可以在每个资源池节点中部署一个资源配 置管理代理, 用于计算本节点的负荷, 然后上报给资源配置管理模块, 同时该资源配 置管理带来还用于接收资源配置管理模块的判决命令。 步骤 S706: 整个***上电, 资源配置管理模块获取资源池信息, 如图 9所示, 根 据传统的配置, 先给资源池中的任意一个节点设置初始属性, 即这个节点是作为 CP 属性, 还是 UP属性。 步骤 S708: 资源池中的每个节点通过资源配置代理定时(例如每隔 2s) 向总控单 板的资源配置管理模块上报本节点的处理能力和当前的负荷。 步骤 S710: 总控模块的资源配置管理模块周期性地进行负荷评估, 主要包括:
1 ) 计算资源池中的所有当前为 CP且运行正常的节点的总的 CP处理能力, 以及 当前总的 CP负荷。
2) 计算资源池中的所有当前为 UP且运行正常的节点的总的 UP处理能力, 以及 当前总的 UP负荷。 下面结合两个具体实施方式对上述方法进行描述。 实施方式 1 在本实施方式描述的是将资源池单板从控制面 CP转换为用户面 UP, 如图 10所 示, 该 CP转 UP属性切换处理包括以下步骤: 步骤 S1002: 资源配置管理模块根据负荷进行评估后, 根据不同场景做出如下的 判决:
场景 A: 若当前总的 CP负荷相比总处理能力是一个轻负荷状态 (优选地, 阀值 可以由配置决定), 则将资源池中的负荷最小的 CP节点下电; 场景 B: 若当前总的 CP负荷相比总处理能力是一个非轻负荷状态但处理能力还 有剩余, 则保持现状; 场景 C: 若当前总的 UP负荷相比总处理能力是一个高负荷状态, 处理能力已经 无法支撑, 需要将***中的某些 CP节点切换为 UP属性, 则做如下处理:
S1 : 判断资源池中是否有已经下电的 UP节点, 若有, 则直接将已经下电的 UP 节点恢复为上电;
S2: 若没有已经下电的 UP节点, 则判断资源池中是否有已经下电的 CP节点, 若 有, 则将该已经下电的 CP节点上电, 并且将其属性切换为 UP;
S3: 若资源池中没有已经下电的 CP节点, 则从 CP节点池中选择一块负荷最低的 CP节点, 同时计算将该 CP节点的计算能力去除后剩余的 CP的总的处理能力是否足 够支撑当前的 CP负荷, 如果足够, 则判决将该节点的属性由 CP切换为 UP;
S4: 若该 CP节点的计算能力去除后剩余的 CP的总处理能力不足够支撑当前的 CP负荷, 则保持现状。 步骤 S1004: 在资源配置管理模块判决需要由 CP属性切换为 UP之后, 给需要被 切换的 CP节点的资源配置代理发送属性切换命令; 步骤 S1006: 资源配置代理在收到属性切换命令后,给 CP业务发送一个预通知消 息, 告知该节点马上就要属性切换为 UP 了, 并且设置一个等待定时器, 该定时器用 于判断是否在预定时间内可以成功完成切换; CP业务在收到后, 判断当前 CP节点上 的业务量、 业务形态等是否允许切换, 若允许, 则开始进行相关的业务迁移等; 业务 善后工作处理完毕, 则给资源配置代理回属性切换应答消息; 步骤 S1008: 资源配置代理判断应答消息, 主要包括:
1 )若应答消息中业务明确 CP节点可以进行属性切换, 则资源配置代理进行运行 软件的切换, 将 UP软件运行起来; 然后通知资源配置管理模块对信息和相关节点状 态进行更新;
2)若应答消息中业务明确当前 CP节点由于某些情况不能进行属性切换, 则资源 配置代理终止最终的切换动作, 然后通知资源配置管理模块进行状态回退, 该 CP节 点属性仍然为 CP。 实施方式 2 在本实施方式描述的是将资源池单板从用户面 UP转换为控制面 CP, 如图 11所 示, 该 UP转 CP属性切换处理包括以下步骤: 步骤 S1102: 资源配置管理模块根据负荷进行评估后, 根据不同场景做出如下的 判决- 场景 A: 若当前总的 UP负荷相比总处理能力是一个轻负荷状态 (优选地, 阀值 可以由配置决定), 则将资源池中的负荷最小的 UP节点下电; 场景 B: 若当前总的 UP负荷相比总处理能力是一个非轻负荷状态但处理能力还 有剩余, 则保持现状; 场景 C: 若当前总的 CP负荷相比总处理能力是一个高负荷状态, 处理能力已经 无法支撑, 需要将***中的某些 UP节点切换为 CP属性, 则做如下处理: S1 : 判断资源池中是否有已经下电的 CP 节点, 若有, 则直接将已经下电的 CP 节点恢复为上电;
S2: 若没有已经下电的 CP节点, 则判断资源池中是否有已经下电的 UP节点, 若 有, 则将该已经下电的 UP节点上电, 并且将其属性切换为 CP;
S3: 若资源池中没有已经下电的 UP节点, 则从 UP节点池中选择一块负荷最低 的 UP节点, 同时计算将该 UP节点的计算能力去除后剩余的 UP的总的处理能力是否 足够支撑当前的 UP负荷, 如果足够, 则判决将该节点的属性由 UP切换为 CP;
S4: 若把该 UP节点的计算能力去除后剩余的 UP的总处理能力不足够支撑当前 的 UP负荷, 则保持现状。 步骤 S1104: 在资源配置管理模块判决需要由 UP属性切换为 CP之后, 给需要被 切换的 UP节点的资源配置代理发送属性切换命令; 步骤 S1106: 资源配置代理在收到属性切换命令后,给 UP业务发送一个预通知消 息, 告知该节点马上就要属性切换为 CP 了, 并且设置一个等待定时器, 该定时器用
于判断是否在预定时间内可以成功完成切换; UP业务在收到后, 判断当前 UP节点上 的业务量、 业务形态等是否允许切换, 若允许, 则开始进行相关的业务迁移等; 业务 善后工作处理完毕, 则给资源配置代理回属性切换应答消息; 步骤 S1108: 资源配置代理判断应答消息, 主要包括: 1 )若应答消息中业务明确 UP节点可以进行属性切换, 则资源配置代理进行运行 软件的切换, 将 CP软件运行起来; 然后通知资源配置管理模块对信息和相关节点状 态进行更新;
2)若应答消息中业务明确当前 UP节点由于某些情况不能进行属性切换, 则资源 配置代理终止最终的切换动作, 然后通知资源配置管理模块进行状态回退, 该 UP节 点属性仍然为 UP。 在另外一个实施例中, 还提供了一种软件, 该软件用于执行上述实施例及优选实 施方式中描述的技术方案。 在另外一个实施例中, 还提供了一种存储介质, 该存储介质中存储有上述软件, 该存储介质包括但不限于: 光盘、 软盘、 硬盘、 可擦写存储器等。 从以上的描述中, 可以看出, 本发明实现了如下技术效果: 通过共享资源池的方 式来分配 CP节点和 UP节点, 从而使得 CP节点和 UP之间可以实现动态的切换, 只 要对资源池中的资源进行实时的监控并根据监控的结果实现节点属性的切换便可以达 到有效利用资源的目的。 通过上述方式解决了现有技术中资源池的资源静态配置而造 成资源浪费的技术问题, 达到了有效利用资源和提高业务处理能力的技术效果。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布在多个计算装置所 组成的网络上, 可选地, 它们可以用计算装置可执行的程序代码来实现, 从而, 可以 将它们存储在存储装置中由计算装置来执行, 并且在某些情况下, 可以以不同于此处 的顺序执行所示出或描述的步骤, 或者将它们分别制作成各个集成电路模块, 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样, 本发明不限制于任 何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本领域的技 术人员来说, 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内, 所作的 任何修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。
Claims
权 利 要 求 书 一种资源分配方法, 包括:
监控共享资源池的多个节点, 其中, 所述多个节点包括属性为控制面处理 板 CP的节点和属性为用户面处理板 UP的节点;
根据监控结果, 调整所述多个节点中的一个或多个节点的属性。 根据权利要求 1所述的方法, 其中, 根据监控结果, 调整所述多个节点中的部 分或全部节点的属性包括- 当检测到当前属性为 CP的节点的总的负荷大于第一预定阈值时, 且当前 属性为 UP的节点的总的负荷小于第二预定阈值时, 将一个或多个当前属性为 UP的节点的属性调整为 CP; 和 /或
当检测到当前属性为 UP的节点的总的负荷大于第三预定阈值时, 且当前 属性为 CP的节点的总的负荷小于第二预定阈值时, 将一个或多个当前属性为 CP的节点的属性调整为 UP。
3. 根据权利要求 2所述的方法, 其中, 将当前接入所述***的用户数与每个属性为 CP的节点所能支持的最大用 户数之间的比值作为属性为 CP的节点当前的总的负荷; 和 /或
根据当前 CPU的负荷以及媒体面流量确定属性为 UP的节点当前的总的负 荷。
4. 根据权利要求 1所述的方法, 其中, 属性被调整的节点是当前负荷最小的一个 或多个节点。
5. 根据权利要求 1所述的方法, 其中, 在调整所述多个节点中的一个或多个节点 的属性之前, 所述方法还包括:
判断在将所述一个或多个节点的属性进行调整后, 剩余的与该被调整的一 个或多个节点的属性相同的节点是否可以承载该属性所对应的业务负荷。
6. 根据权利要求 1至 5中任一项所述的方法, 其中, 调整所述多个节点中的一个 或多个节点的属性包括-
向每个待调整的节点发送属性调整指令, 其中, 所述属性调整指令用于指 示该节点改变自身当前的属性;
如果在预定时间内未收到该节点返回的调整完成指示消息, 则将该节点的 属性恢复为进行调整前的属性。
7. 根据权利要求 1至 5中任一项所述的方法, 其中, 监控共享资源池的多个节点 包括:
所述共享资源池中的每个节点周期性地上报自身当前的负荷和自身的处理 能力; 或者
资源配置管理模块周期性地检测所述共享资源池中每个节点的当前的负荷 和自身的处理能力。
8. 根据权利要求 1至 5 中任一项所述的方法, 其中, 所述 CP为专用 CP, 所述 UP为专用 UP。
9. 一种资源分配装置, 包括:
监控单元, 设置为监控共享资源池的多个节点, 其中, 所述多个节点包括 属性为控制面处理板 CP的节点和属性为用户面处理板 UP的节点;
调整单元, 设置为根据监控结果, 调整所述多个节点中的一个或多个节点 的属性。
10. 根据权利要求 9所述的装置, 其中, 所述调整单元包括:
第一调整模块, 设置为当检测到当前属性为 CP的节点的总的负荷大于第 一预定阈值时, 且当前属性为 UP的节点的总的负荷小于第二预定阈值时, 将 一个或多个当前属性为 UP的节点的属性调整为 CP; 和 /或
第二调整模块, 设置为当检测到当前属性为 UP的节点的总的负荷大于第 三预定阈值时, 且当前属性为 CP的节点的总的负荷小于第二预定阈值时, 将 一个或多个当前属性为 CP的节点的属性调整为 UP。
11. 根据权利要求 9或 10所述的装置, 其中, 所述调整单元还包括:
发送模块, 设置为向每个待调整的节点发送属性调整指令, 其中, 所述属 性调整指令用于指示该节点改变自身当前的属性;
恢复模块, 设置为在预定时间内未收到该节点返回的调整完成指示消息的 情况下, 将该节点的属性恢复为进行调整前的属性。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP13831485.1A EP2887720B1 (en) | 2012-08-20 | 2013-08-19 | Resource allocation method and device |
US14/422,442 US9532359B2 (en) | 2012-08-20 | 2013-08-19 | Resource allocation method and device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201210295837.4A CN103634801B (zh) | 2012-08-20 | 2012-08-20 | 资源分配方法和装置 |
CN201210295837.4 | 2012-08-20 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014029308A1 true WO2014029308A1 (zh) | 2014-02-27 |
Family
ID=50149435
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2013/081743 WO2014029308A1 (zh) | 2012-08-20 | 2013-08-19 | 资源分配方法和装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US9532359B2 (zh) |
EP (1) | EP2887720B1 (zh) |
CN (1) | CN103634801B (zh) |
WO (1) | WO2014029308A1 (zh) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106804054A (zh) * | 2015-11-26 | 2017-06-06 | 中兴通讯股份有限公司 | 一种虚拟化基站接入网络共享传输资源的方法及装置 |
US20170161110A1 (en) * | 2015-12-02 | 2017-06-08 | Via Alliance Semiconductor Co., Ltd. | Computing resource controller and control method for multiple engines to share a shared resource |
EP3166349A4 (en) * | 2014-07-03 | 2017-07-05 | ZTE Corporation | Internet access traffic sharing method, device and terminal |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2996382B1 (en) * | 2013-05-31 | 2020-07-08 | Huawei Technologies Co., Ltd. | Physical resource adjustment method, device and controller |
WO2015123836A1 (en) * | 2014-02-20 | 2015-08-27 | Telefonaktiebolaget L M Ericsson (Publ) | Traffic management in the mobile network |
CN105828384B (zh) * | 2015-01-09 | 2019-06-21 | ***通信集团河北有限公司 | 一种lte基站接入核心网的动态负载均衡控制方法及*** |
US10432461B2 (en) | 2015-12-04 | 2019-10-01 | T-Mobile Usa, Inc. | Peer-to-peer distribution of radio protocol data for software defined radio (SDR) updates |
US10257165B2 (en) | 2016-09-30 | 2019-04-09 | T-Mobile Usa, Inc. | Dynamic provisioning of a firewall role to user devices |
US10616776B2 (en) * | 2016-09-30 | 2020-04-07 | T-Mobile Usa, Inc. | Dynamic provisioning of a gateway role to user devices |
US10362482B2 (en) | 2016-12-21 | 2019-07-23 | T-Mobile Usa, Inc. | Network operation and trusted execution environment |
CN109548079A (zh) * | 2017-09-22 | 2019-03-29 | 中兴通讯股份有限公司 | 一种指示通信***的用户平面功能管理资源的方法及装置 |
CN108011754B (zh) * | 2017-11-27 | 2021-11-09 | 新华三技术有限公司 | 转控分离***、备份方法和装置 |
CN114401036A (zh) * | 2022-01-21 | 2022-04-26 | 中国电子科技集团公司第五十四研究所 | 一种基于分布式基带资源池架构的卫星通信控制方法 |
CN117858262B (zh) * | 2024-03-07 | 2024-05-14 | 成都爱瑞无线科技有限公司 | 基站资源调度优化方法、装置、基站、设备、介质及产品 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040009773A1 (en) * | 2002-07-10 | 2004-01-15 | Nec Corporation | Mobile communication system and operation control method thereof |
CN101114927A (zh) * | 2006-07-24 | 2008-01-30 | 华为技术有限公司 | 一种实现负载均衡的***及方法 |
CN101184114A (zh) * | 2007-10-31 | 2008-05-21 | 中兴通讯股份有限公司 | 分组域临时移动用户标志的分配方法 |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7904546B1 (en) * | 2004-09-27 | 2011-03-08 | Alcatel-Lucent Usa Inc. | Managing processes on a network device |
FI20085217A0 (fi) * | 2008-03-07 | 2008-03-07 | Nokia Corp | Tietojenkäsittelyjärjestely |
CN101990215B (zh) * | 2009-08-04 | 2013-10-16 | 大唐移动通信设备有限公司 | 一种资源分配方法及一种rnc |
WO2011044396A2 (en) | 2009-10-07 | 2011-04-14 | Santosh Chandrachood | Method and apparatus for supporting network communications |
WO2012097875A1 (en) | 2011-01-20 | 2012-07-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Gateway allocation in a mobile communication system |
US8516493B2 (en) * | 2011-02-01 | 2013-08-20 | Futurewei Technologies, Inc. | System and method for massively multi-core computing systems |
US8620383B2 (en) * | 2011-10-05 | 2013-12-31 | Alcatel Lucent | Dynamic resource sharing among cellular networks |
-
2012
- 2012-08-20 CN CN201210295837.4A patent/CN103634801B/zh active Active
-
2013
- 2013-08-19 WO PCT/CN2013/081743 patent/WO2014029308A1/zh active Application Filing
- 2013-08-19 EP EP13831485.1A patent/EP2887720B1/en active Active
- 2013-08-19 US US14/422,442 patent/US9532359B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040009773A1 (en) * | 2002-07-10 | 2004-01-15 | Nec Corporation | Mobile communication system and operation control method thereof |
CN101114927A (zh) * | 2006-07-24 | 2008-01-30 | 华为技术有限公司 | 一种实现负载均衡的***及方法 |
CN101184114A (zh) * | 2007-10-31 | 2008-05-21 | 中兴通讯股份有限公司 | 分组域临时移动用户标志的分配方法 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2887720A4 * |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3166349A4 (en) * | 2014-07-03 | 2017-07-05 | ZTE Corporation | Internet access traffic sharing method, device and terminal |
CN106804054A (zh) * | 2015-11-26 | 2017-06-06 | 中兴通讯股份有限公司 | 一种虚拟化基站接入网络共享传输资源的方法及装置 |
US20170161110A1 (en) * | 2015-12-02 | 2017-06-08 | Via Alliance Semiconductor Co., Ltd. | Computing resource controller and control method for multiple engines to share a shared resource |
US10007557B2 (en) * | 2015-12-02 | 2018-06-26 | Via Alliance Semiconductor Co., Ltd. | Computing resource controller and control method for multiple engines to share a shared resource |
Also Published As
Publication number | Publication date |
---|---|
CN103634801A (zh) | 2014-03-12 |
US9532359B2 (en) | 2016-12-27 |
EP2887720B1 (en) | 2019-12-11 |
EP2887720A4 (en) | 2016-01-06 |
CN103634801B (zh) | 2018-02-09 |
US20150223252A1 (en) | 2015-08-06 |
EP2887720A1 (en) | 2015-06-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2014029308A1 (zh) | 资源分配方法和装置 | |
US10659979B2 (en) | Method and device for handling cell outage | |
CN112867050B (zh) | 一种upf网元管理方法及*** | |
CN107690822B (zh) | 网络管理的方法、设备、***及计算机可读存储介质 | |
CN113766558A (zh) | 一种网络模式控制方法及终端、存储介质 | |
CN110535676B (zh) | Smf动态容灾的实现方法、装置、设备及存储介质 | |
JP5656271B2 (ja) | ネットワーク管理システムにおいてエネルギー節約を管理するための方法、デバイス、およびシステム | |
CN110225546B (zh) | 一种双连接中辅节点控制方法及基站 | |
US20200015102A1 (en) | Network slice instance management method, apparatus, and system | |
WO2012083669A1 (zh) | 基于接入网关的主备用设备切换方法和装置 | |
WO2016065552A1 (zh) | 一种心跳周期的设置方法及终端 | |
CN112703774A (zh) | 网络切片管理 | |
WO2018233451A1 (zh) | 通信方法、装置和*** | |
WO2023124308A1 (zh) | 一种xn接***互方法及*** | |
WO2017101446A1 (zh) | 无线制式的处理方法、装置及基站 | |
CN103428682A (zh) | 辅助信息发送方法及用户设备、网络侧配置方法及网络侧 | |
CN113329417A (zh) | 一种网络配置方法及装置 | |
CN102711254A (zh) | 网络侧的资源释放控制方法及rnc | |
WO2017128820A1 (zh) | 一种虚拟化网络功能的管理方法、网络设备及*** | |
WO2011109997A1 (zh) | 基于智能终端的网络优化方法、设备及*** | |
CN112911731B (zh) | 用于uRLLC设备的节电控制方法、装置、设备及介质 | |
WO2017173901A1 (zh) | 虚拟化网络节能方法、装置及计算机存储介质 | |
CN111314272B (zh) | 一种任务处理方法及装置 | |
CN113259975A (zh) | 网络游戏连接方法、电子设备和计算机可读介质 | |
CN110784365A (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: 13831485 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2013831485 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14422442 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |