5G Mobile Core - Revision history

Unknown user at 06:55, 26 October 2022

2022-10-26T06:55:52Z

← Older revision		Revision as of 06:55, 26 October 2022
Line 26:		Line 26:

	Pada kesempatan ini, kita menganggap implementasi, takeaway utama adalah bahwa kita dapat mengonsep Mobile Core sebagai graph of services. Kita kadang-kadang akan mendengar ini disebut Service Graph atau Service Chain, yang terakhir lebih lazim dalam dokumen berorientasi NFV. Istilah lain, Service Mesh, memiliki arti yang agak spesifik dalam terminologi asli cloud — kami akan menghindari kelebihan istilah itu di sini. 3GPP diam pada terminologi spesifik karena dianggap sebagai pilihan implementasi daripada bagian dari spesifikasi.		Pada kesempatan ini, kita menganggap implementasi, takeaway utama adalah bahwa kita dapat mengonsep Mobile Core sebagai graph of services. Kita kadang-kadang akan mendengar ini disebut Service Graph atau Service Chain, yang terakhir lebih lazim dalam dokumen berorientasi NFV. Istilah lain, Service Mesh, memiliki arti yang agak spesifik dalam terminologi asli cloud — kami akan menghindari kelebihan istilah itu di sini. 3GPP diam pada terminologi spesifik karena dianggap sebagai pilihan implementasi daripada bagian dari spesifikasi.



			==Pranala Menarik==

			* [[5G]]

Unknown user at 06:55, 26 October 2022

2022-10-26T06:55:30Z

← Older revision		Revision as of 06:55, 26 October 2022
Line 19:		Line 19:
	Kelompok ketiga mencakup satu komponen yang berjalan di User Plane (UP):		Kelompok ketiga mencakup satu komponen yang berjalan di User Plane (UP):

	UPF (User Plane Function): Forward lalu lintas antara RAN dan Internet, sesuai dengan kombinasi S/PGW di EPC. Selain forward paket, ia bertanggung jawab atas penegakan kebijakan, lawful intercept, pelaporan penggunaan lalu lintas, dan QoS policing.		* UPF (User Plane Function): Forward lalu lintas antara RAN dan Internet, sesuai dengan kombinasi S/PGW di EPC. Selain forward paket, ia bertanggung jawab atas penegakan kebijakan, lawful intercept, pelaporan penggunaan lalu lintas, dan QoS policing.

	Dari jumlah tersebut, kelompok pertama dan ketiga paling baik dilihat sebagai refactoring langsung dari EPC 4G, sedangkan kelompok kedua—meskipun pengenalan terminologi baru secara sembarang—adalah cara 3GPP untuk menunjuk ke solusi cloud native sebagai kondisi akhir yang diinginkan untuk Mobile Core. Dari catatan khusus, memperkenalkan layanan penyimpanan yang berbeda berarti bahwa semua layanan lain dapat menjadi stateless, dan karenanya, lebih mudah diskalakan. Perhatikan juga bahwa Gambar 15 mengadopsi ide yang umum dalam microservice-based system, yaitu, untuk menunjukkan message bus yang menghubungkan semua komponen daripada menyertakan set lengkap koneksi pairwise. Ini juga menyarankan strategi implementasi yang dipahami dengan baik.		Dari jumlah tersebut, kelompok pertama dan ketiga paling baik dilihat sebagai refactoring langsung dari EPC 4G, sedangkan kelompok kedua—meskipun pengenalan terminologi baru secara sembarang—adalah cara 3GPP untuk menunjuk ke solusi cloud native sebagai kondisi akhir yang diinginkan untuk Mobile Core. Dari catatan khusus, memperkenalkan layanan penyimpanan yang berbeda berarti bahwa semua layanan lain dapat menjadi stateless, dan karenanya, lebih mudah diskalakan. Perhatikan juga bahwa Gambar 15 mengadopsi ide yang umum dalam microservice-based system, yaitu, untuk menunjukkan message bus yang menghubungkan semua komponen daripada menyertakan set lengkap koneksi pairwise. Ini juga menyarankan strategi implementasi yang dipahami dengan baik.

Unknown user at 06:55, 26 October 2022

2022-10-26T06:55:12Z

← Older revision		Revision as of 06:55, 26 October 2022
Line 23:		Line 23:
	Dari jumlah tersebut, kelompok pertama dan ketiga paling baik dilihat sebagai refactoring langsung dari EPC 4G, sedangkan kelompok kedua—meskipun pengenalan terminologi baru secara sembarang—adalah cara 3GPP untuk menunjuk ke solusi cloud native sebagai kondisi akhir yang diinginkan untuk Mobile Core. Dari catatan khusus, memperkenalkan layanan penyimpanan yang berbeda berarti bahwa semua layanan lain dapat menjadi stateless, dan karenanya, lebih mudah diskalakan. Perhatikan juga bahwa Gambar 15 mengadopsi ide yang umum dalam microservice-based system, yaitu, untuk menunjukkan message bus yang menghubungkan semua komponen daripada menyertakan set lengkap koneksi pairwise. Ini juga menyarankan strategi implementasi yang dipahami dengan baik.		Dari jumlah tersebut, kelompok pertama dan ketiga paling baik dilihat sebagai refactoring langsung dari EPC 4G, sedangkan kelompok kedua—meskipun pengenalan terminologi baru secara sembarang—adalah cara 3GPP untuk menunjuk ke solusi cloud native sebagai kondisi akhir yang diinginkan untuk Mobile Core. Dari catatan khusus, memperkenalkan layanan penyimpanan yang berbeda berarti bahwa semua layanan lain dapat menjadi stateless, dan karenanya, lebih mudah diskalakan. Perhatikan juga bahwa Gambar 15 mengadopsi ide yang umum dalam microservice-based system, yaitu, untuk menunjukkan message bus yang menghubungkan semua komponen daripada menyertakan set lengkap koneksi pairwise. Ini juga menyarankan strategi implementasi yang dipahami dengan baik.

			[[File:Slide33.png\|center\|300px\|thumb\|Figure 15. 5G Mobile Core (NG-Core)]]

	~~_images/~~Slide33.png
	Figure 15. 5G Mobile Core (NG-Core).

	Pada kesempatan ini, kita menganggap implementasi, takeaway utama adalah bahwa kita dapat mengonsep Mobile Core sebagai graph of services. Kita kadang-kadang akan mendengar ini disebut Service Graph atau Service Chain, yang terakhir lebih lazim dalam dokumen berorientasi NFV. Istilah lain, Service Mesh, memiliki arti yang agak spesifik dalam terminologi asli cloud — kami akan menghindari kelebihan istilah itu di sini. 3GPP diam pada terminologi spesifik karena dianggap sebagai pilihan implementasi daripada bagian dari spesifikasi.		Pada kesempatan ini, kita menganggap implementasi, takeaway utama adalah bahwa kita dapat mengonsep Mobile Core sebagai graph of services. Kita kadang-kadang akan mendengar ini disebut Service Graph atau Service Chain, yang terakhir lebih lazim dalam dokumen berorientasi NFV. Istilah lain, Service Mesh, memiliki arti yang agak spesifik dalam terminologi asli cloud — kami akan menghindari kelebihan istilah itu di sini. 3GPP diam pada terminologi spesifik karena dianggap sebagai pilihan implementasi daripada bagian dari spesifikasi.

Unknown user at 06:54, 26 October 2022

2022-10-26T06:54:07Z

← Older revision		Revision as of 06:54, 26 October 2022
Line 1:		Line 1:
	~~The~~ 5G Mobile Core, ~~which~~ 3GPP ~~calls the~~ NG-Core, ~~adopts a~~ microservice-like architecture, ~~where we say “microservice~~-~~like” because while the~~ 3GPP ~~specification spells out this level of disaggregation~~, ~~it is really just prescribing a~~ set ~~of functional blocks and not an implementation~~. A set ~~of functional blocks is very different from the collection of engineering decisions that go into designing a~~ microservice-based system. ~~That said~~, ~~viewing the collection of components shown in Figure~~ 15 ~~as a~~ set of microservices ~~is a good working~~ model.		5G Mobile Core, yang disebut 3GPP sebagai NG-Core, mengadopsi microservice-like architecture, di mana kita mengatakan "microservice-like" karena meskipun spesifikasi 3GPP menguraikan tingkat disagregasi ini, itu benar-benar hanya menetapkan satu set blok fungsional dan bukan implementasi. Satu set blok fungsional sangat berbeda dari kumpulan keputusan teknik yang digunakan untuk merancang microservice-based system. Meskipun demikian, melihat kumpulan komponen yang ditunjukkan pada Gambar 15 sebagai satu set microservices adalah model kerja yang baik.

	~~The following organizes the~~ set ~~of functional blocks into three groups~~. ~~The first group runs in the~~ Control Plane (CP) ~~and has a~~ counterpart ~~in the~~ EPC.		Berikut ini mengatur set blok fungsional menjadi tiga kelompok. Grup pertama berjalan di Control Plane (CP) dan memiliki counterpart di EPC.

	* AMF (Core Access and Mobility Management Function): ~~Responsible for connection and reachability management~~, ~~mobility management~~, ~~access authentication and authorization~~, ~~and location services~~. ~~Manages the mobility-related aspects of the EPC’s~~ MME.		* AMF (Core Access and Mobility Management Function): Bertanggung jawab atas manajemen koneksi dan jangkauan, manajemen mobilitas, otentikasi dan otorisasi akses, dan layanan lokasi. Mengelola aspek terkait mobilitas dari MME EPC.
	* SMF (Session Management Function): ~~Manages each~~ UE ~~session~~, ~~including~~ IP ~~address allocation~~, ~~selection of associated~~ UP ~~function~~, ~~control aspects of~~ QoS, ~~and control aspects of~~ UP ~~routing~~. ~~Roughly corresponds to part of the EPC’s~~ MME ~~and the control-related aspects of the EPC’s~~ PGW.		* SMF (Session Management Function): Mengelola setiap sesi UE, termasuk alokasi alamat IP, pemilihan fungsi UP terkait, aspek kontrol QoS, dan aspek kontrol perutean UP. Kira-kira sesuai dengan bagian dari MME EPC dan aspek terkait kontrol dari PGW EPC.
	* PCF (Policy Control Function): ~~Manages the policy rules that other~~ CP ~~functions then enforce~~. ~~Roughly corresponds to the EPC’s~~ PCRF.		* PCF (Policy Control Function): Mengelola aturan kebijakan yang kemudian diterapkan oleh fungsi CP lainnya. Kira-kira sesuai dengan PCRF EPC.
	* UDM (Unified Data Management): ~~Manages user identity~~, ~~including the generation of authentication credentials~~. ~~Includes part of the functionality in the EPC’s~~ HSS.		* UDM (Unified Data Management): Mengelola identitas pengguna, termasuk pembuatan kredensial otentikasi. Termasuk bagian dari fungsionalitas dalam HSS EPC.
	* AUSF (Authentication Server Function): ~~Essentially an authentication~~ server. ~~Includes part of the functionality in the EPC’s~~ HSS.		* AUSF (Authentication Server Function): Pada dasarnya server otentikasi. Termasuk bagian dari fungsionalitas dalam HSS EPC.

	~~The second group also runs in the~~ Control Plane (CP) ~~but does not have a direct~~ counterpart ~~in the~~ EPC:		Grup kedua juga berjalan di Control Plane (CP) tetapi tidak memiliki counterpart langsung di EPC:

	* SDSF (Structured Data Storage Network Function): A “helper” service ~~used to store~~ structured data. ~~Could be implemented by an~~ “SQL Database” ~~in a~~ microservices-based system.		* SDSF (Structured Data Storage Network Function): “helper” service digunakan untuk menyimpan structured data. Dapat di implementasikan dengan “SQL Database” di sebuah microservices-based system.
	* UDSF (Unstructured Data Storage Network Function): A “helper” service ~~used to store~~ unstructured data. ~~Could be implemented by a~~ “Key/Value Store” ~~in a~~ microservices-based system.		* UDSF (Unstructured Data Storage Network Function): “helper” service digunakan untuk menyimpan unstructured data. Dapat di implementasikan dengan “Key/Value Store” di sebuah microservices-based system.
	* NEF (Network Exposure Function): ~~A means to expose select capabilities to third-party services~~, ~~including translation between~~ internal ~~and external representations for~~ data. ~~Could be implemented by an~~ “API Server” ~~in a~~ microservices-based system.		* NEF (Network Exposure Function): Sarana untuk mengekspos kemampuan tertentu ke layanan pihak ketiga, termasuk terjemahan antara representasi internal dan eksternal untuk data. Dapat di implementasikan dengan “API Server” di sebuah microservices-based system.
	* NRF (NF Repository Function): ~~A means to discover available services~~. ~~Could be implemented by a~~ “Discovery Service” ~~in a~~ microservices-based system.		* NRF (NF Repository Function): Sarana untuk menemukan layanan yang tersedia. Dapat di implementasikan dengan “Discovery Service” di sebuah microservices-based system.
			* NSSF (Network Slicing Selector Function): Cara untuk memilih Network Slice untuk melayani UE yang diberikan. Irisan jaringan pada dasarnya adalah cara untuk mempartisi sumber daya jaringan untuk membedakan layanan yang diberikan kepada pengguna yang berbeda. Ini adalah fitur utama 5G.

	~~NSSF~~ (~~Network Slicing Selector Function~~): A means to select a Network Slice to serve a given UE. Network slices are essentially a way to partition network resources in order to differentiate service given to different users. It is a key feature of 5G that we discuss in depth in a later chapter.		Kelompok ketiga mencakup satu komponen yang berjalan di User Plane (UP):

	~~The third group includes the one component that runs in the~~ User Plane ~~(UP~~):		UPF (User Plane Function): Forward lalu lintas antara RAN dan Internet, sesuai dengan kombinasi S/PGW di EPC. Selain forward paket, ia bertanggung jawab atas penegakan kebijakan, lawful intercept, pelaporan penggunaan lalu lintas, dan QoS policing.

			Dari jumlah tersebut, kelompok pertama dan ketiga paling baik dilihat sebagai refactoring langsung dari EPC 4G, sedangkan kelompok kedua—meskipun pengenalan terminologi baru secara sembarang—adalah cara 3GPP untuk menunjuk ke solusi cloud native sebagai kondisi akhir yang diinginkan untuk Mobile Core. Dari catatan khusus, memperkenalkan layanan penyimpanan yang berbeda berarti bahwa semua layanan lain dapat menjadi stateless, dan karenanya, lebih mudah diskalakan. Perhatikan juga bahwa Gambar 15 mengadopsi ide yang umum dalam microservice-based system, yaitu, untuk menunjukkan message bus yang menghubungkan semua komponen daripada menyertakan set lengkap koneksi pairwise. Ini juga menyarankan strategi implementasi yang dipahami dengan baik.

	UPF (User Plane Function): Forwards traffic between RAN and the Internet, corresponding to the S/PGW combination in EPC. In addition to packet forwarding, it is responsible for policy enforcement, lawful intercept, traffic usage reporting, and QoS policing.

	Of these, the first and third groups are best viewed as a straightforward refactoring of 4G’s EPC, while the second group—despite the gratuitous introduction of new terminology—is 3GPP’s way of pointing to a cloud native solution as the desired end-state for the Mobile Core. Of particular note, introducing distinct storage services means that all the other services can be stateless, and hence, more readily scalable. Also note that Figure 15 adopts an idea that’s common in microservice-based systems, namely, to show a message bus interconnecting all the components rather than including a full set of pairwise connections. This also suggests a well-understood implementation strategy.

	_images/Slide33.png		_images/Slide33.png
	Figure 15. 5G Mobile Core (NG-Core).		Figure 15. 5G Mobile Core (NG-Core).

	~~Stepping back from these details~~, ~~and with the caveat that we are presuming an implementation~~, ~~the main~~ takeaway ~~is that we can conceptualize the~~ Mobile Core ~~as a~~ graph of services. ~~You will sometimes hear this called a~~ Service Graph or Service Chain, ~~the latter being more prevalent in~~ NFV~~-oriented documents~~. ~~Another term~~, Service Mesh, ~~has taken on a rather specific meaning in~~ cloud ~~native terminology—we’ll avoid overloading that term here~~. 3GPP ~~is silent on the specific terminology since it is considered an implementation choice rather than part of the specification. We describe our implementation choices in later chapters~~.		Pada kesempatan ini, kita menganggap implementasi, takeaway utama adalah bahwa kita dapat mengonsep Mobile Core sebagai graph of services. Kita kadang-kadang akan mendengar ini disebut Service Graph atau Service Chain, yang terakhir lebih lazim dalam dokumen berorientasi NFV. Istilah lain, Service Mesh, memiliki arti yang agak spesifik dalam terminologi asli cloud — kami akan menghindari kelebihan istilah itu di sini. 3GPP diam pada terminologi spesifik karena dianggap sebagai pilihan implementasi daripada bagian dari spesifikasi.

Unknown user at 06:06, 26 October 2022

2022-10-26T06:06:29Z

← Older revision		Revision as of 06:06, 26 October 2022
Line 3:		Line 3:
	The following organizes the set of functional blocks into three groups. The first group runs in the Control Plane (CP) and has a counterpart in the EPC.		The following organizes the set of functional blocks into three groups. The first group runs in the Control Plane (CP) and has a counterpart in the EPC.

	AMF (Core Access and Mobility Management Function): Responsible for connection and reachability management, mobility management, access authentication and authorization, and location services. Manages the mobility-related aspects of the EPC’s MME.		* AMF (Core Access and Mobility Management Function): Responsible for connection and reachability management, mobility management, access authentication and authorization, and location services. Manages the mobility-related aspects of the EPC’s MME.
			* SMF (Session Management Function): Manages each UE session, including IP address allocation, selection of associated UP function, control aspects of QoS, and control aspects of UP routing. Roughly corresponds to part of the EPC’s MME and the control-related aspects of the EPC’s PGW.
	SMF (Session Management Function): Manages each UE session, including IP address allocation, selection of associated UP function, control aspects of QoS, and control aspects of UP routing. Roughly corresponds to part of the EPC’s MME and the control-related aspects of the EPC’s PGW.		* PCF (Policy Control Function): Manages the policy rules that other CP functions then enforce. Roughly corresponds to the EPC’s PCRF.
			* UDM (Unified Data Management): Manages user identity, including the generation of authentication credentials. Includes part of the functionality in the EPC’s HSS.
	PCF (Policy Control Function): Manages the policy rules that other CP functions then enforce. Roughly corresponds to the EPC’s PCRF.		* AUSF (Authentication Server Function): Essentially an authentication server. Includes part of the functionality in the EPC’s HSS.

	UDM (Unified Data Management): Manages user identity, including the generation of authentication credentials. Includes part of the functionality in the EPC’s HSS.

	AUSF (Authentication Server Function): Essentially an authentication server. Includes part of the functionality in the EPC’s HSS.

	The second group also runs in the Control Plane (CP) but does not have a direct counterpart in the EPC:		The second group also runs in the Control Plane (CP) but does not have a direct counterpart in the EPC:

	SDSF (Structured Data Storage Network Function): A “helper” service used to store structured data. Could be implemented by an “SQL Database” in a microservices-based system.		* SDSF (Structured Data Storage Network Function): A “helper” service used to store structured data. Could be implemented by an “SQL Database” in a microservices-based system.
			* UDSF (Unstructured Data Storage Network Function): A “helper” service used to store unstructured data. Could be implemented by a “Key/Value Store” in a microservices-based system.
	UDSF (Unstructured Data Storage Network Function): A “helper” service used to store unstructured data. Could be implemented by a “Key/Value Store” in a microservices-based system.		* NEF (Network Exposure Function): A means to expose select capabilities to third-party services, including translation between internal and external representations for data. Could be implemented by an “API Server” in a microservices-based system.
			* NRF (NF Repository Function): A means to discover available services. Could be implemented by a “Discovery Service” in a microservices-based system.
	NEF (Network Exposure Function): A means to expose select capabilities to third-party services, including translation between internal and external representations for data. Could be implemented by an “API Server” in a microservices-based system.

	NRF (NF Repository Function): A means to discover available services. Could be implemented by a “Discovery Service” in a microservices-based system.

	NSSF (Network Slicing Selector Function): A means to select a Network Slice to serve a given UE. Network slices are essentially a way to partition network resources in order to differentiate service given to different users. It is a key feature of 5G that we discuss in depth in a later chapter.		NSSF (Network Slicing Selector Function): A means to select a Network Slice to serve a given UE. Network slices are essentially a way to partition network resources in order to differentiate service given to different users. It is a key feature of 5G that we discuss in depth in a later chapter.

Unknown user: Created page with "The 5G Mobile Core, which 3GPP calls the NG-Core, adopts a microservice-like architecture, where we say “microservice-like” because while the 3GPP specification spells out..."

2022-10-26T03:24:56Z

Created page with "The 5G Mobile Core, which 3GPP calls the NG-Core, adopts a microservice-like architecture, where we say “microservice-like” because while the 3GPP specification spells out..."

New page

The 5G Mobile Core, which 3GPP calls the NG-Core, adopts a microservice-like architecture, where we say “microservice-like” because while the 3GPP specification spells out this level of disaggregation, it is really just prescribing a set of functional blocks and not an implementation. A set of functional blocks is very different from the collection of engineering decisions that go into designing a microservice-based system. That said, viewing the collection of components shown in Figure 15 as a set of microservices is a good working model.

The following organizes the set of functional blocks into three groups. The first group runs in the Control Plane (CP) and has a counterpart in the EPC.

AMF (Core Access and Mobility Management Function): Responsible for connection and reachability management, mobility management, access authentication and authorization, and location services. Manages the mobility-related aspects of the EPC’s MME.

SMF (Session Management Function): Manages each UE session, including IP address allocation, selection of associated UP function, control aspects of QoS, and control aspects of UP routing. Roughly corresponds to part of the EPC’s MME and the control-related aspects of the EPC’s PGW.

PCF (Policy Control Function): Manages the policy rules that other CP functions then enforce. Roughly corresponds to the EPC’s PCRF.

UDM (Unified Data Management): Manages user identity, including the generation of authentication credentials. Includes part of the functionality in the EPC’s HSS.

AUSF (Authentication Server Function): Essentially an authentication server. Includes part of the functionality in the EPC’s HSS.

The second group also runs in the Control Plane (CP) but does not have a direct counterpart in the EPC:

SDSF (Structured Data Storage Network Function): A “helper” service used to store structured data. Could be implemented by an “SQL Database” in a microservices-based system.

UDSF (Unstructured Data Storage Network Function): A “helper” service used to store unstructured data. Could be implemented by a “Key/Value Store” in a microservices-based system.

NEF (Network Exposure Function): A means to expose select capabilities to third-party services, including translation between internal and external representations for data. Could be implemented by an “API Server” in a microservices-based system.

NRF (NF Repository Function): A means to discover available services. Could be implemented by a “Discovery Service” in a microservices-based system.

NSSF (Network Slicing Selector Function): A means to select a Network Slice to serve a given UE. Network slices are essentially a way to partition network resources in order to differentiate service given to different users. It is a key feature of 5G that we discuss in depth in a later chapter.

The third group includes the one component that runs in the User Plane (UP):

UPF (User Plane Function): Forwards traffic between RAN and the Internet, corresponding to the S/PGW combination in EPC. In addition to packet forwarding, it is responsible for policy enforcement, lawful intercept, traffic usage reporting, and QoS policing.

Of these, the first and third groups are best viewed as a straightforward refactoring of 4G’s EPC, while the second group—despite the gratuitous introduction of new terminology—is 3GPP’s way of pointing to a cloud native solution as the desired end-state for the Mobile Core. Of particular note, introducing distinct storage services means that all the other services can be stateless, and hence, more readily scalable. Also note that Figure 15 adopts an idea that’s common in microservice-based systems, namely, to show a message bus interconnecting all the components rather than including a full set of pairwise connections. This also suggests a well-understood implementation strategy.

_images/Slide33.png
Figure 15. 5G Mobile Core (NG-Core).

Stepping back from these details, and with the caveat that we are presuming an implementation, the main takeaway is that we can conceptualize the Mobile Core as a graph of services. You will sometimes hear this called a Service Graph or Service Chain, the latter being more prevalent in NFV-oriented documents. Another term, Service Mesh, has taken on a rather specific meaning in cloud native terminology—we’ll avoid overloading that term here. 3GPP is silent on the specific terminology since it is considered an implementation choice rather than part of the specification. We describe our implementation choices in later chapters.