10.46243/jst.2022.v7.i01.pp82-91 registered
Energy-Aware VMs Consolidation Computing Frameworks’ of Data Center in Cloud Computing Environment
Resolves to https://www.jst.org.in/index.php/pub/article/view/284
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2022.v7.i01.pp82-91
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 3d01b3aa7070c6a6…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
Also as schema.org JSON-LD · Turtle · RDF/XML · DataCite XML · Crossref UNIXREF · Crossref UNIXSD — the formats of the DOI content-negotiation service, from this record (which carries what).
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
Energy-Aware VMs Consolidation Computing Frameworks’ of Data Center in Cloud Computing Environment (PrincipalTitle · en)
Published 2023-07-26
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 7 · issue 1 · pages 82–91
Agents
- Dr. Rajesh P. Patel Dr. Rajesh P. Patel (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2022.v7.i01.pp82-91
Abstract · en
Cloud computing is a service model that can conveniently access a shared pool of configurable computing resources that can be quickly configured and released on demand. In cloud data centers, the scale and complexity of various computing resources such as servers, network equipment, and cooling systems are constantly evolving, which consumes a lot of power and increases the energy consumption of the data center. Because cloud data center resources are not optimized for maximum utilization, they consume more power. Therefore, it is necessary to integrate virtual machines (VMs) on data center servers to help optimize the use of resources in the cloud, thereby reducing energy consumption. By considering the optimal power consumption of various data center resources, many researchers have proposed various methods and algorithms to reduce the power consumption of servers and network equipment. In this paper, we introduced two energy-saving computing frameworks (1) data center energy-saving server power model, (2) energy-saving VM migration based on Multi-objective to help optimize data center power consumption.
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jst.2022.v7.i01.pp82-91 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Energy-Aware VMs Consolidation Computing Frameworks’ of Data Center in Cloud Computing Environment (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Dr. Rajesh P. Patel Dr. Rajesh P. Patel publisher: Longman Publishers published: 2023-07-26 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 7 · no. 1 · pp. 82–91 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2024-02-16 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
Recommended for a journal article and not in this record: the reference list.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
Cited by — in this registry
No record held in this registry cites this DOI.
Counts only records held in this registry; a citation from a work held elsewhere is not seen here. The list as JSON
Relations
The record states no relation, and no record held here states one with this DOI.
Funding
The record names no funder.
Each funder's page lists every work held here that names it. ROR IDs open at ror.org; Funder Registry IDs resolve at doi.org.
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 52 fields set · sha256 38b0addb575a… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
Changes made at Crossref through DOI Doctor
Every deposit Smart Scholars' DOI Doctor made for this DOI, oldest first, with Crossref's own answer. Each fingerprint is the SHA-256 of its entry and of the fingerprint before it, so a change to any earlier entry changes every fingerprint after it.
| When | What changed | Crossref | Fingerprint |
|---|---|---|---|
| 28 Sep 2026, 01:40 | Address updated from https://www.jst.org.in/index.php/pub/article/view/336 to https://www.jst.org.in/index.php/pub/article/view/284 | ● accepted by Crossref | 7683ca1b9057… |
| 28 Sep 2026, 04:05 | Read back: the DOI resolves to the new address | ● confirmed | 459b7e619d52… |
| 07 Oct 2026, 07:37 | Metadata completed abstract (163 words) · licence | ● accepted by Crossref | 9717d87d65d4… |
| 07 Oct 2026, 08:47 | Read back: Crossref's record shows it | ● confirmed | 6d8be6d54862… |
4 entries · the last fingerprint 6d8be6d548627b85a12ba79a5bb01b3bf005cdaa0c9fcca0e3b6e705f172d530 · the history as JSON, each entry with the fingerprint before it, to check them yourself.



