A game-theoretical approach for spectrum efficiency improvement in Cloud-RAN. Zhou, Z., Peng, J., Zhang, X., Liu, K., & Jiang, F. User association in non-orthogonal multiple access networks. Wang, K., Liu, Y., Ding, Z., & Nallanathan, A. Paper presented at the IEEE/CIC international conference communications China, Qingdao, 22–24 October 2017. Coalition game for user association and bandwidth allocation in ultra-dense mmWave networks. Introduction to the theory of cooperative games. Multiagent systems: Algorithmic, game-theoretic, and logical foundations. V (1953) Theory of games and economic behaviour. IEEE Transactions on Vehicular Technology., 66(2), 1723–1738. A coalition formation game for remote radio head cooperation in cloud radio access network. Paper presented at the European Conference on Networks and Communications (EuCNC), Oulu, 12–15 June 2017. Ensuring Quality of Service in a multi-tenant cloud-enabled RAN environment.
Paper presented at the IEEE global communications conference, Singapore, 4–8 December 2017. Joint user association and power allocation for licensed and unlicensed spectrum in 5G networks.
Instead of looking at all of the project's objectives, the group concentrates on one at a time and decomposes it into lower levels of detail or if using a bottom-up approach goes in the other direction.Ali, M., Qaisar, S., Naeem, M., & Mumtaz, S. Thread - usually done alongside one of the other three processes. Difficult to generate a complete list of tasks.Difficult to retain focus on the "big picture".Harder to get organized into logical steps or phases.The issues of using the bottom up technique are: May lead to a more complete list of tasks.The advantages of using the bottom up technique are: This process continues until all relevant tasks have been grouped into sub-groups that directly tie to a major objective. A brainstorming session where subject matter experts, stakeholders, and team members look at the list of objectives project the project charter and generate as many low-level activities needed to complete objectives, which are then grouped by deliverable. Cost and time estimates are more difficult to create and generally less accurate than under the analogy approachīottom-up - a similar project's WBS doesn't exist.Can be time-consuming, must guard against "analysis paralysis".Make sure to decompose the tasks to appropriate levels.
Need to make sure major objectives are not forgotten.The issues of using the top-down technique are: Can create a greater understanding of the entire project by all participants.Promotes stakeholder participation in the planning phase of the project.Ensures projects are organized logically based on the nature of the project.The advantages of using the top-down technique are: A brainstorming session where subject matter experts, stakeholders, and team members look at the list of objectives project the project charter and create a high-level list of deliverables and then further compose that list into smaller and smaller steps needed to create Top-down - used when a similar project's WBS doesn't exist. Resist the temptation to not critically review previous WBS and its appropriateness for the new project.Make sure the previous WBS was accurate and updated.Make sure the previous WBS is completely understood and similar.The issues of using the analogy technique are: A valuable tool for brainstorming a new project and looking for deliverables.The advantages of using the analogy technique are: There are 4 methods for creating a WBS including: analogy, top down, bottom up, and thread.Īnalogy - created by looking for a similar project done in the past and using its WBS as a starting point.