Difference between revisions of "Arsitektur 5G: Pilihan Implementasi"
Onnowpurbo (talk | contribs) (Created page with "With an already deployed 4G RAN/EPC in the field and a new 5G RAN/NG-Core deployment underway, we can’t ignore the issue of transitioning from 4G to 5G (an issue the IP-worl...") |
Onnowpurbo (talk | contribs) |
||
| Line 1: | Line 1: | ||
With an already deployed 4G RAN/EPC in the field and a new 5G RAN/NG-Core deployment underway, we can’t ignore the issue of transitioning from 4G to 5G (an issue the IP-world has been grappling with for 20 years). 3GPP officially spells out multiple deployment options, which can be summarized as follows. | With an already deployed 4G RAN/EPC in the field and a new 5G RAN/NG-Core deployment underway, we can’t ignore the issue of transitioning from 4G to 5G (an issue the IP-world has been grappling with for 20 years). 3GPP officially spells out multiple deployment options, which can be summarized as follows. | ||
| + | |||
| + | Dengan 4G RAN/EPC yang sudah diterapkan di lapangan dan penerapan 5G RAN/NG-Core baru yang sedang berlangsung, kami tidak dapat mengabaikan masalah transisi dari 4G ke 5G (masalah yang dihadapi dunia IP selama 20 tahun). ). 3GPP secara resmi merinci beberapa opsi penerapan, yang dapat diringkas sebagai berikut. | ||
| + | |||
* Standalone 4G / Stand-Alone 5G | * Standalone 4G / Stand-Alone 5G | ||
| Line 6: | Line 9: | ||
The second of the three options, which is generally referred to as “NSA“, involves 5G base stations being deployed alongside the existing 4G base stations in a given geography to provide a data-rate and capacity boost. In NSA, control plane traffic between the user equipment and the 4G Mobile Core utilizes (i.e., is forwarded through) 4G base stations, and the 5G base stations are used only to carry user traffic. Eventually, it is expected that operators complete their migration to 5G by deploying NG Core and connecting their 5G base stations to it for Standalone (SA) operation. NSA and SA operations are illustrated in Figure 18. | The second of the three options, which is generally referred to as “NSA“, involves 5G base stations being deployed alongside the existing 4G base stations in a given geography to provide a data-rate and capacity boost. In NSA, control plane traffic between the user equipment and the 4G Mobile Core utilizes (i.e., is forwarded through) 4G base stations, and the 5G base stations are used only to carry user traffic. Eventually, it is expected that operators complete their migration to 5G by deploying NG Core and connecting their 5G base stations to it for Standalone (SA) operation. NSA and SA operations are illustrated in Figure 18. | ||
| + | |||
| + | |||
| + | Yang kedua dari tiga opsi, yang umumnya disebut sebagai "NSA", melibatkan BTS 5G yang ditempatkan di samping BTS 4G yang ada di geografi tertentu untuk memberikan kecepatan data dan peningkatan kapasitas. Di NSA, kontrol lalu lintas pesawat antara peralatan pengguna dan 4G Mobile Core menggunakan (yaitu, diteruskan melalui) BTS 4G, dan BTS 5G hanya digunakan untuk membawa lalu lintas pengguna. Pada akhirnya, diharapkan operator menyelesaikan migrasi mereka ke 5G dengan menerapkan NG Core dan menghubungkan BTS 5G mereka ke sana untuk operasi Standalone (SA). Operasi NSA dan SA diilustrasikan pada Gambar 18. | ||
_images/Slide38.png | _images/Slide38.png | ||
| Line 11: | Line 17: | ||
One reason we call attention to the phasing issue is that we face a similar challenge in the chapters that follow. The closer the following discussion gets to implementation details, the more specific we have to be about whether we are using 4G components or 5G components. As a general rule, we use 4G components—particularly with respect to the Mobile Core, since that’s what’s available in open source today—and trust the reader can make the appropriate substitution without loss of generality. Like the broader industry, the open source community is in the process of incrementally evolving its 4G code base into its 5G-compliant counterpart. | One reason we call attention to the phasing issue is that we face a similar challenge in the chapters that follow. The closer the following discussion gets to implementation details, the more specific we have to be about whether we are using 4G components or 5G components. As a general rule, we use 4G components—particularly with respect to the Mobile Core, since that’s what’s available in open source today—and trust the reader can make the appropriate substitution without loss of generality. Like the broader industry, the open source community is in the process of incrementally evolving its 4G code base into its 5G-compliant counterpart. | ||
| + | |||
| + | |||
| + | Salah satu alasan kami meminta perhatian pada masalah pentahapan adalah karena kami menghadapi tantangan serupa di bab-bab berikutnya. Semakin dekat pembahasan berikut dengan detail implementasi, semakin spesifik kita harus tentang apakah kita menggunakan komponen 4G atau komponen 5G. Sebagai aturan umum, kami menggunakan komponen 4G—khususnya yang berkaitan dengan Mobile Core, karena itulah yang tersedia di open source saat ini—dan percaya bahwa pembaca dapat melakukan penggantian yang sesuai tanpa kehilangan keumuman. Seperti industri yang lebih luas, komunitas open source sedang dalam proses mengembangkan basis kode 4G secara bertahap menjadi mitra yang sesuai dengan 5G. | ||
| + | |||
| + | |||
| + | ==Pranala Menarik== | ||
| + | |||
| + | * [[5G]] | ||
Revision as of 16:46, 26 October 2022
With an already deployed 4G RAN/EPC in the field and a new 5G RAN/NG-Core deployment underway, we can’t ignore the issue of transitioning from 4G to 5G (an issue the IP-world has been grappling with for 20 years). 3GPP officially spells out multiple deployment options, which can be summarized as follows.
Dengan 4G RAN/EPC yang sudah diterapkan di lapangan dan penerapan 5G RAN/NG-Core baru yang sedang berlangsung, kami tidak dapat mengabaikan masalah transisi dari 4G ke 5G (masalah yang dihadapi dunia IP selama 20 tahun). ). 3GPP secara resmi merinci beberapa opsi penerapan, yang dapat diringkas sebagai berikut.
- Standalone 4G / Stand-Alone 5G
- Non-Standalone (4G+5G RAN) over 4G’s EPC
- Non-Standalone (4G+5G RAN) over 5G’s NG-Core
The second of the three options, which is generally referred to as “NSA“, involves 5G base stations being deployed alongside the existing 4G base stations in a given geography to provide a data-rate and capacity boost. In NSA, control plane traffic between the user equipment and the 4G Mobile Core utilizes (i.e., is forwarded through) 4G base stations, and the 5G base stations are used only to carry user traffic. Eventually, it is expected that operators complete their migration to 5G by deploying NG Core and connecting their 5G base stations to it for Standalone (SA) operation. NSA and SA operations are illustrated in Figure 18.
Yang kedua dari tiga opsi, yang umumnya disebut sebagai "NSA", melibatkan BTS 5G yang ditempatkan di samping BTS 4G yang ada di geografi tertentu untuk memberikan kecepatan data dan peningkatan kapasitas. Di NSA, kontrol lalu lintas pesawat antara peralatan pengguna dan 4G Mobile Core menggunakan (yaitu, diteruskan melalui) BTS 4G, dan BTS 5G hanya digunakan untuk membawa lalu lintas pengguna. Pada akhirnya, diharapkan operator menyelesaikan migrasi mereka ke 5G dengan menerapkan NG Core dan menghubungkan BTS 5G mereka ke sana untuk operasi Standalone (SA). Operasi NSA dan SA diilustrasikan pada Gambar 18.
_images/Slide38.png Figure 18. NSA and SA options for 5G deployment.
One reason we call attention to the phasing issue is that we face a similar challenge in the chapters that follow. The closer the following discussion gets to implementation details, the more specific we have to be about whether we are using 4G components or 5G components. As a general rule, we use 4G components—particularly with respect to the Mobile Core, since that’s what’s available in open source today—and trust the reader can make the appropriate substitution without loss of generality. Like the broader industry, the open source community is in the process of incrementally evolving its 4G code base into its 5G-compliant counterpart.
Salah satu alasan kami meminta perhatian pada masalah pentahapan adalah karena kami menghadapi tantangan serupa di bab-bab berikutnya. Semakin dekat pembahasan berikut dengan detail implementasi, semakin spesifik kita harus tentang apakah kita menggunakan komponen 4G atau komponen 5G. Sebagai aturan umum, kami menggunakan komponen 4G—khususnya yang berkaitan dengan Mobile Core, karena itulah yang tersedia di open source saat ini—dan percaya bahwa pembaca dapat melakukan penggantian yang sesuai tanpa kehilangan keumuman. Seperti industri yang lebih luas, komunitas open source sedang dalam proses mengembangkan basis kode 4G secara bertahap menjadi mitra yang sesuai dengan 5G.