★5G 제안요청서 II.기술사항.ko.en PDF

Ⅱ.
Premise Ⅱ- One
5G system main equipment supplier request for proposal
(Release 1)
Ⅱ. Premise
SK Telecom
Ⅱ. Premise Ⅱ- 2
Contents
One Common .................................................. .................................................. ........................................ 6
1.1 Standards ................................................ .................................................. .................................................. 6
1.2 Network Architecture .................................................. .................................................. ......................... 6
1.2.1 5G system configurations .................................................. .................................................. ....................... 6
1.2.2. NSA (Non-standalone) Architecture .................................................. .............................................. 6
1.2.3. SA (Standalone) Architecture ............................................. .................................................. ............. 7
1.2.4 Network Architecture related to our additional requirements ........................................... .................................. 8
1.3 Standards and Open Interface .................................................. .................................................. ....................... 8
1.3.1 Compliance .................................................. .................................................. .......................................... 8
1.3.2 Open Interface .................................................. .................................................. ................................ 9
1.4 MVI (Multi Vendor Interoperability) support .................................................. ........................................... 9
1.4.1 MVI supports a range .................................................. .................................................. ................................. 9
1.4.2 MVI support measures .................................................. .................................................. ............................... 10
1.5 technical support .................................................. .................................................. ............................................... 11
1.5.1 System Integration and Optimization Support .................................................. ............................................... 11
1.5.2 S-Index .................................................. .................................................. ........................................... 11
1.6 service .................................................. .................................................. .................................................. . 12
1.6.1 5G services .................................................. .................................................. ....................................... 12
1.6.2 Existing services .................................................. .................................................. .................................... 13
1.7 Network Performance .................................................. .................................................. ...................... 13
1.8 Security Support ................................................ .................................................. ................................................ 14
1.8.1 Security Guide .................................................. .................................................. .................................... 14
1.8.2 Security requirements ............................................... .................................................. .................................... 15
1.8.3 Security Regulations .................................................. .................................................. ........................................ 17
1.9 System Evolution .................................................. .................................................. .......................................... 17
1.9.1 Evolution Support Systems .................................................. .................................................. ........................... 17
1.10 BMT / DVT Availabilty .................................................. .................................................. ...................... 18
1.11 Open Source Support .................................................. .................................................. .............................. 18
2 5G Radio Access Network .................................................. .................................................. ...... 19
2.1 RAN shape and structure .................................................. .................................................. ............................... 19
2.1.1 RAN Architecture .................................................. .................................................. ......................... 19
2.1.2 gNB H / W shape .................................................. .................................................. .............................. 21
2.1.3 Fronthaul .................................................. .................................................. ....................................... 30
2.1.4 Backhaul ................................................. .................................................. .......................................... 34
2.1.5 Optical module .................................................. .................................................. ............................................. 35
2.2 General Specifications .................................................. .................................................. ............................................... 36
2.2. Mechanical specifications .................................................. .................................................. .................................... 36
2.2. Electrical Specifications .................................................. .................................................. .................................... 38
SK Telecom
Ⅱ. Premise Ⅱ- 3
2.2.3 Environmental Specifications .................................................. .................................................. .................................... 39
2.3 RAN Performance .................................................. .................................................. ............................................. 41
2.3.1. Capacity .................................................. .................................................. ......................................... 41
2.3.2. Latency .................................................. .................................................. ........................................... 42
2.3.3 Coverage .................................................. .................................................. ........................................ 43
2.3.4 Mobility .................................................. .................................................. .......................................... 45
2.3.5 QoS .................................................. .................................................. ................................................. 45
2.3.6 Energy efficiency .................................................. .................................................. ................................ 45
2.3.7 MTBF, MTTR, MTTF .................................................. .................................................. ..................... 46
2.3.8 Etc .................................................. .................................................. ................................................. 47
2.4 RAN functions .................................................. .................................................. ............................................. 47
2.4.1 Synchronization feature .................................................. .................................................. .................................... 47
2.4.2 Call processing .................................................. .................................................. .................................... 48
2.4.3. Resource management ............................................... .................................................. .................................... 50
2.4.4 Add-ons .................................................. .................................................. ......................................... 51
2.4.5 RF transceiver function ............................................... .................................................. .................................. 53
2.4.6 O & M functions .................................................. .................................................. ...................................... 54
2.4.7 Additional interlocking device ............................................... .................................................. .................................... 61
2.4.8 Multi-RAT support .................................................. .................................................. ............................. 63
2.4.9 Intelligent Management .................................................. .................................................. ............. 63
2.4.10 Other features .................................................. .................................................. ........................................ 66
2.5 Interface Specification .................................................. .................................................. ..................................... 66
2.5.1 gNB connection between the AMF standards .................................................. .................................................. ............. 67
2.5.2 Connection between standards and UPF gNB .................................................. .................................................. .............. 67
2.5.3 Connection between the standard and gNB gNB .................................................. .................................................. .............. 68
2.5.4 gNB-CU and the inter-connection standard gNB-DU .................................................. .................................................. 69
2.5.5 Access standards between eNB and gNB .................................................. .................................................. .............. 69
2.6 Radio Protocol .................................................. .................................................. ................................... 70
2.6.1 Physical Layer Protocol .................................................. .................................................. ............... 71
2.6.2 Layer 2 Protocol .................................................. .................................................. ........................... 72
2.6.3 Layer 3 Protocol .................................................. .................................................. ........................... 75
2.7 RAN EMS .................................................. .................................................. ............................................. 77
2.7.1 General Specifications .................................................. .................................................. ........................................ 77
2.7.2 RAN EMS General Features .................................................. .................................................. ...................... 78
2.7.3 OSS interworking function .................................................. .................................................. ................................ 89
2.8 RAN Virtualization Support .................................................. .................................................. .............................. 102
2.8.1 VNF your needs .................................................. .................................................. ............................... 102
2.8.2 Details RFV (Radio Function Virtualizaiton) requirements .................................................. .......................... 103
2.9 RAN competitiveness .................................................. .................................................. ....................................... 103
SK Telecom
Ⅱ. Premise Ⅱ- 4
3 5G Core Network .................................................. .................................................. ................... 104
3.1 Common ................................................ .................................................. .............................................. 104
3.1.1. Network Architecture and Configuration .................................................. .................................................. ................ 104
3.1.2 Capacity, performance calculated based on .................................................. .................................................. ................... 105
3.1.3. System reliability ................................................ .................................................. ................................. 107
3.1.4 Reliability of service ................................................ .................................................. ................................. 107
3.1.5 System scalability ............................................... .................................................. .................................. 107
3.1.6 Systems and service reliability .................................................. .................................................. ............. 108
3.2 5G-enabled EPC .................................................. .................................................. ............................... 109
3.2.1 Common Features .................................................. .................................................. ...................................... 110
3.2.2 Management .................................................. .................................................. ...................................... 115
3.2.3. 5G-enabled MME .................................................. .................................................. ....................... 119
3.2.4 5G-enabled SGW .................................................. .................................................. ........................ 123
3.2.5 5G-enabled PGW .................................................. .................................................. ........................ 125
3.2.6 Interface specification and existing EPC works .................................................. ................................................. 128
3.2.7 Migration Support .................................................. .................................................. ............................ 129
3.3 5G Nextgen Core .................................................. .................................................. ............................. 129
3.3.1. Common Features .................................................. .................................................. ...................................... 130
3.3.2. Management .................................................. .................................................. ...................................... 132
3.3.3 Access & Mobility Management .................................................. ............................................... 132
3.3.4. Session Management .................................................. .................................................. ................ 135
3.3.5 User Plane .................................................. .................................................. ................................... 136
3.3.6 Policy Management .................................................. .................................................. ................... 137
3.3.7 Subscriber Management ................................................ .................................................. ............. 138
3.3.8 NF / Service Discovery .................................................. .................................................. ................ 139
3.3.9 Network Slice Selection .................................................. .................................................. ............ 139
3.3.10 Service Exposure .................................................. .................................................. ........................ 139
3.3.11 Storage Function .................................................. .................................................. ........................ 140
3.3.12 SMS Function .................................................. .................................................. .............................. 140
3.3.13 Interface standards and interworking .................................................. .................................................. ................ 140
3.4 Core EMS .................................................. .................................................. .......................................... 144
3.4.1. General Specifications .................................................. .................................................. ...................................... 144
3.4.2 Common Core EMS functions .................................................. .................................................. ................... 144
3.4.3. OSS interworking function .................................................. .................................................. .............................. 150
3.5 Details VNF demand for 5G Core Virtualization .................................................. ........................................... 153
3.5.1. General requirements .................................................. .................................................. ............................. 153
3.5.2 VNF Interface Structure .................................................. .................................................. .................... 154
3.5.3. VNF Traffic Load-Balancing Structure .................................................. .............................................. 154
3.5.4 VNF Traffic Management .................................................. .................................................. ......... 154
3.6 5G Core Competitiveness .................................................. .................................................. ................................. 155
SK Telecom
Ⅱ. Premise Ⅱ- 5
4 Virtualization Management and Orchestration .................................................. .............................. 156
4.1 summary .................................................. .................................................. .................................................. .. 156
4.2 Details SKT NFV MANO interlocking requirements .................................................. .................................................. ..... 156
4.2.1 SKT NFV MANO Architecture .................................................. .................................................. .. 156
4.2.2. Details Generic VNFM linkage requirements .................................................. .................................................. ... 157
4.2.3 Details Common VIM requires Interlocking .................................................. .................................................. .... 160
4.2.4 Details Local NFVO and E2E NO interlock requirements .................................................. ...................................... 160
4.2.5 Details DC SDN interlock requirements .................................................. .................................................. ............... 161
4.2.6 Details TIO works requirements .................................................. .................................................. ....................... 161
4.3 5G MANO Requirements .................................................. .................................................. ......................... 162
4.3.1. ETSI NFV MANO Basic Requirements ............................................ .................................................. ...... 162
4.3.2 Details 5G Network Slicing requirements .................................................. .................................................. ... 163
4.3.3 Details NFV open platform requirements .................................................. .................................................. ..... 164
5 NFV Infrastructure .................................................. .................................................. ................. 165
5.1 General specifications ................................................ .................................................. .............................................. 165
5.1.1 Mechanical specifications .................................................. .................................................. .................................. 165
5.1.2. Electrical Specifications .................................................. .................................................. .................................. 166
5.1.3 Environmental Specifications .................................................. .................................................. .................................. 167
5.2 Your virtualization needs .................................................. .................................................. ................................ 168
5.2.1 Details ETSI NFV and NFV open platform requirements .................................................. ................................ 168
5.2.2. Virtualization Acceleration Technology .................................................. ................................................ 169
5.2.3 NFVI-PoP (Point-of-Presence) .................................................. .................................................. .. 170
5.2.4 NFVI-Fabric ............................................... .................................................. ..................................... 171
5.2.5 Tap support functions .................................................. .................................................. .............................. 172
SK Telecom
Ⅱ. Premise Ⅱ- 6
One Common
1.1 Specification
Our 5G system shall comply with international standards and recommendations, such as 3GPP, ETSI, ITU, IETF, and also comply with the relevant national
legislation (Telecommunications Act, the Radio Law, the stations technical standards, etc.).
1.2 Network Architecture
1.2.1 5G system configurations
5G system is a system that provides 5G 5G Service association with NR, to have two configurations.
- Configured to pass through the LTE Control Plane Signaling interworking for the NR 5G Service and Support to LTE and Dual
Connectivity Type: NSA (Non-standalone)
- SA (Standalone): configured to enable the NR solely for 5G Service and also transmitted to the Control Plane Signaling NR
1.2.2 NSA (Non-standalone) Architecture
The figure below shows the configuration of the NSA Non-romaing Reference Architecture, this article refers to the Core that supports 5G Service
to configure NSA LA 5G-enabled EPC. Components of NSA Architecture is as follows.
HSS
S6a
5G-enabled
PCRF
MME S11
S1-MME
S1-MME Gx
S5 SGi
5G-enabled 5G-enabled
UE eNB PDN
SGW PGW
Uu
S1-U
X2 Gy / Gz
Charging
gNB
System
Figure 1.2.2-1 NSA Non-roaming Reference Architecture
One gNB: 5G NR including call processing equipment to support the next generation of technologies and services, resource management, a baseband signal processing,
RF transmission and reception of the transmission signal, the signal strength control, and a device that performs a function such as a quality measure.
SK Telecom
Ⅱ. Premise Ⅱ- 7
2 eNB: LTE / LTE-A / LTE-A Pro technology and equipment to the call processing support services, resource management, a baseband signal processing,
3 5G-enabled SGW: Depending on the settings in the Control Session and User Plane NF handling the Payload Traffic
Using a 5G-enabled and the GTP Tunneling PGW forwards the PDU.
4 5G-enabled PGW: a User Plane and Control NF allocated to the IP terminal, and linked to the PDN Packet
For the service and transmits the PDU to the S-GW and the external network.
5 5G-enabled MME: Session management, subscriber management Idle as NF to manage the mobility of the subscriber information and the terminal,
Responsible for the Paging, such as subscriber authentication.
6 PCRF: PCRF provides the ability to offer Dynamic QoS and Charging Rule in accordance with the Service Data Flow.
7 HSS: the function of the location information for the Database Roles and terminals that store subscriber information registration / management
to provide.
8 Charging system: a system for handling billing, OCS and the offline charging for real-time charging process
And an OFCS to provide statistics.
9 PDN: a Packet Data Network for IP-based Serivce provided.
1.2.3. SA (Standalone) Architecture
The figure below shows a configuration of a SA Non-roaming Reference Architecture, the article supporting the Core Service 5G 5G Nextgen the
SA configuration is referred to as Core (5GNC). Components of SA Architecture is as follows.
NEF UDM NRF AUSF NSSF
Nnef Nudm Nnrf Nausf Nnssf
Namf Nsmf Npcf Nsmsf
TDB
Charging TDB
AMF SMF PCF SMSF
N1
System
N2 N4
N3 N6
UE gNB UPF DN
Uu
Figure 1.2.3-1 SA Non-roaming Reference Architecture
One gNB: 5G NR including call processing equipment to support the next generation of technologies and services, resource management, a baseband signal processing,
2 AMF: a Control Plane NF to support authentication, connection management, mobility management for terminals, Session-related
And it serves to transfer the signaling to the SMF.
SK Telecom
Ⅱ. Premise Ⅱ- 8
3 SMF: Control Plane to perform Session management, IP address management, UPF management and QoS control for the terminal
Is the NF.
4 UPF: Anchor Point, and perform the role of the mobile terminal, Gatewate role between the terminal and the DN, Packet
Processing / transmission, a User Plane NF to perform a Policy Enforcement role.
5 PCF: Integration Policy governs the overall operation of the 5G Network and the Policy on the other Control Plane NF
It serves to transfer.
6 NEF: Perform the Service Capability Exposure functions between network operators and 3rd Party.
7 NRF: provides the functionality for Service Discovery for other NF to support the request of the NF.
8 UDM: Front-end provides the capability for interworking with other features and NF Database to store subscriber information.
9 AUSF: performs the authentication server role features for subscribers.
10 SMSF: in conjunction with the AMF provides the SMS over NAS functions.
11 It serves to provide configuration information for Information and Network Slice Slice to help you choose: NSSF.
12 Charging system: a system for handling billing, OCS and the offline charging for real-time charging process
And an OFCS to provide statistics.
13 DN: the Data Network for IP and Non-IP-based Serivce provided.
1.2.4 Network Architecture matters related to our additional requirements
1.2.4.1 ATSCALE, COSMOS Compliance
The company is a public ATSCALE, COSMOS paper bar to reflect the design philosophy and High Level Requirements for 5G system to
system. Our 5G Systme shall comply with the ATSCALE, COSMOS paper.
- 5G ATSCALE, COSMOS Paper: https://developers.sktelecom.com/resource/document/#
1.2.4.2 Network Slicing, MEC support
It shall support the Network Slicing, (Mobile Edge Computing) MEC to facilitate the provision of a variety of 5G-based services.
1.3 Standards and Open Interface
1.3.1 Compliance
1 Our 5G system to apply to 3GPP Release 15 standard by default. Proponents relevant when creating proposals
List and shall specify the Version.
SK Telecom
Ⅱ. Premise Ⅱ- 9
a) gNB - UE Interface Specification (Uu Interface)
b) gNB-CU - gNB-DU Interface Specification (F1 Interface)
c) gNB-DU-h - gNB-DU-l Interface Specification (Fx Interface)
d) gNB-CU-CP - gNB-CU-UP Interface Specification (E1 Interface)
e) gNB - gNB Interface Specification (Xn Interface)
f) gNB - eNB Interface Specification (X2 / Xn Interface)
g) gNB - AMF Interface Specification (Interface N2)
h) gNB - UPF Interface Specification (N3 Interface)
i) eNB and 5G-enabled EPC with Interface Specification (see 3.2)
j) gNB and 5G-enabled EPC with Interface Specification (see 3.2)
k) Interface specifications between 5G-enabled EPC NF (see 3.2)
l) Interface between standard 5G Nexten Core NF (see Section 3.3)
m) 5G Nextgen Core and Legacy EPC with Interface Specification
1.3.2 Open Interface
Proponents for the 1.3.1 and our request Interface, shall be subject to the relevant requirements Open Interface.
1 MVI and international standards, and our company is given, including a detailed implementation plan for the implementation of its Protocol
It shall disclose the specifications in the target company.
2. The proponent shall be accepted by the Company if the Protocol requires modification, if necessary by the Company is presented
It shall conform to the specifications Interface
1.4 (Multi Vendor Interoperability) MVI Support
Our 5G system should support the MVI for interworking between different vendors.
1.4.1 MVI supports a range
MVI main scope of support that we require are as follows:
SK Telecom
Ⅱ. Premise Ⅱ- 10
1.4.1.1 3GPP standards-based Inferface
MVI Support Interface is as follows, and other required support for the MVI 2.1.1 RAN Archiecture / 3.2 5G Enabled-EPC Architecture / 3.3 5G
Netgen Core Architecutre the Interface / Reference Point defined / described in this document, the Company is required do.
- 5G Radio Access Network - 5G Core Network
- 5G DU - 5G CU
- 5G gNB DU-h - 5G gNB DU-l
- 5G gNB - LTE eNodeB
- 5G Core / CP - 5G Core / UP
- 5G NE (Network Entity) / NF (Network Function) between
1.4.1.2 Other Interface
5G system should support MVI about Interface / Reference Point in accordance with the 3GPP standard, in addition, our standards and ETSI, IETF and other
international standards. because of this
1 in addition to the call processing must ensure operability and reliability of such statistical billing.
Two other suppliers of Orchestrator, VNF Manager, VIM (Virtualized Infrastructure Manager), such as NFV Manager
Interoperability must be ensured between the Entity.
1.4.2 MVI support measures
MVI will be made based on the international standards and our standards. Proponents occur if the equipment modification for the MVI, shall be accepted by, construed, equipment
modification method and scope of the standards and specifications shall take precedence in our opinion.
1.4.2.1 Development plans for the MVI Support
1 Proposed by the time the main features MVI development plan (Roadmap) (hereinafter the reference point), the system-specific section (hereinafter
It is presented divided into Interface), and the reference point should be marked with: However, when it is verified in the End to End System Level
reference point, rather than setting the completion of the development in individual Node basis.
2 Additional presented by MVI Feature that presents services and features proponents Development Plan (Feature is common, Access,
The separated RAN-EMS, Core, CN-EMS, etc.) should be provided, including the following.
a) The proponents of the system and S / W Version
b) MVI function development lead time (D + MM) according to the above item
c) applied standard
SK Telecom
1.4.2.2 Verification Plan for MVI Support
1 Proposed by dividing the amount of time available and the MVI Test Duration (min - max) and equipment of each Feature
It shall be presented.
2. The proponent shall present the following proposal MVI performed by such equipment and Feature.
a) Prerequisites
b) MVI Test Procedures
c) We, proponents and opponents of the act developer
1.5 Technical Support
1.5.1 System Integration and Optimization Support
1 Proposed system Integration and with H / W, and based on S / W (Hypervisor, MANO, etc) that we presented
It should support the optimization.
2 proposer H / W, based on S / W (Hypervisor, MANO like) / Change in the upgrade system in which we proposed
It should support Integration and optimization.
Three measures in case of failure, presented each element constituting the 5G system according to process (H / W, based
S / W) actively cooperate with the vendors to resolve the problem within 24 hours of disaster recovery and should be supported.
1.5.2 S-Index
1 5G system must comply with our safety indicators (S-Index) information.
2 S-Index is an essential item required for the introduction and operation of new systems in the company, the integrity of the system
A stability index that comprehensively evaluated.
Three proponents to reflect the S-Index 5G information during system design and development should be dressed in our company, our equipment
Until acceptance testing of the operational departments, it should be evaluated for compliance with the S-Index items from our relevant departments.
4 proposer needs to be further improvement and Penalty system granted under the S-Index Level Assessment received from the Company
Can.
The main contents of the 5 S-Index are as follows:
a) S / W Stability
• Multi Thread-based Multi Process implementation, Asynchronous Log Write technique used, e-poll method used,
• Uplink / Downlink Queue / Thread Pool disconnect, overload control how and when, Lock contention minimize such
SK Telecom
• Algorithm adequacy, Thread management algorithms, Disk I / O-related Non-Blocking I / O use, Multi-Thread Safe, etc.
• Memory leak prevention variables, Validation defense, Buffer / Queue Overflow Control, Block Exception Handling Units,
etc.
b) RM solution
• Burst Traffic flows overload control, NAS works when you can not take advantage of the caching service provides a continuous, interlocking system retries
Abnormal or even bypass function, Timer Management of Client / Server works etc.
c) Performance
• Normal processing up to the performance of the system and provides an overload control for more traffic
d) operational support
• Operating systems management / monitoring built environment, GUI / CLI-based commands provide stable, Operational Event Logging, threshold setting
and visible / audible alarm, such as the implementation
• Process resource use monitoring and alarm subscriber / destination system unit control / adjustment Internal Framework State Management and Statistics
provides
• S / W type of backup and recovery, and the remote access control system interlock, the system redundancy, etc.
e) technical documentation
• Project deliverables, operator's manual, S / W Architecture specifications, Database Creation and submission specifications, etc.
1.6 Service
1.6.1 5G services
5G system must be capable of supporting a wide range of 5G-based services such as eMBB, URLLC and shall meet the following
service requirements. More information is referring to 3GPP TS 22.261.
1.6.1.1 Enhanced Mobile Broadband Services
Scenario Experienced data Experienced data

UE speed Coverage
rate (DL) rate (UL)
Urban
Pedestrians and users in vehicles
50 Mbps 25 Mbps Full network
macro (up to 120 km / h)
Rural
Pedestrians and users in vehicles
50 Mbps 25 Mbps Full network
macro (up to 120 km / h)
Indoor 1 Gbps 500 Mbps Pedestrians Office and
SK Telecom
hotspot residential
Broadban d
access
25 Mbps 50 Mbps Pedestrians Confined area
in a
crowd
Dense
Pedestrians and users in
300 Mbps 50 Mbps Downtown
urban vehicles (up to 60 km / h)
1.6.1.2 Ultra Reliable and Low Latency Services
User
Scenario End-to-end Service availability Payload size (Small:
Jitter experienced
latency & Reliablity <256 bytes)
data rate
Discrete
10 ms 100 μs 99,99% 10 Mbps Small to big
automation
Process
1 Mbps up to
automation - remote 50 ms 20 ms 99,9999% Small to big
100 Mbps
control
Process
automation - 50 ms 20 ms 99,9% 1 Mbps Small

monitoring
Intelligent transport
systems -
10 ms 20 ms 99,9999% 10 Mbps Small to big
infrastructure
backhaul
1.6.2 Existing Service
5G system, should be able to support voice and video services, messaging services, roaming, Safety characters disaster (PWS), location-based services (LCS), eMBMS
based on existing networks, such as LTE services and related value-added services.
The proponent shall give such a detailed implementation plan and schedule for the existing service support.
1.7 Network Performance
1 proposer to the target to be presented and the associated detail based on network performance required for each section.
a) proposer be provided with equipment required for the proposed network performance objective verification and shall present a validated method.
SK Telecom
b) each entry in the network performance objective is to be measured in the End-to-End (User Perspective).
c) it does not satisfy the requirements of the 3GPP technical specifications that were not specified below shall explain the details and reasons in
detail.
division quality(%) Remarks
Connection rate (communication rate)
Data call
video call
SMS / MMS voice
calls (VoIP)
Handover success rates
Intra-5GC (Inter / Intra Cell) Inter / Intra Cell presented each
Between the Inter-5GC Inter-

Data
third party 5GC Carrier (Inter / Intra
call
Cell) Inter / Intra Cell presented each
Inter RAT
Between the Inter-5GC Inter-
Video call third party 5GC Carrier (Inter / Intra
Inter RAT
Voice calls Between the Inter-5GC Inter-
(VoIP) third party 5GC Carrier (Inter / Intra
1.8 Security Assistance
5G system should be to support the security requirements. And, for matters not mentioned in the proposed requisition shall comply with the relevant laws and
regulations at home and abroad and our security standards.
1.8.1 Security Guide
1 shall comply with the relevant laws and regulations
Act on the a) Information Network Promotion and Safety
b) Privacy Act
SK Telecom
2, and it must comply with the security of our security guidelines to be developed and applied prior to commercialization.
Our security guidelines are organized as follows:
a) Operating System Security
b) DBMS security
c) Web Server Security
d) WAS security
e) Web Application (Web pages) Security
f) Network Security
g) the mobile terminal security
h) Internet of Things (IoT) Security
3 points that are not mentioned in the proposed requisition shall also comply with the 3GPP, IETF, ETSI, ITU Security Recommendation,
When the party should support the request.
4 domestic software development guides, Secure Coding Guide (Acts Regards, KISA) and the Global OWASP Top 10 Project
It should be developed to meet the requirements and comply with our S / W Requirement Security. And, it should continue to support them when the
respective guide documents / requirements document further improvement.
a) Software Development Guide (Acts Regards / KISA)
https://www.moi.go.kr/frt/bbs/type001/commonSelectBoardArticle.do?bbsId=BBSMSTR_000000000015&nttId=57473
https://www.kisa.or.kr/public/laws/laws3_View.jsp?mode=view&p_No=259&b_No=259&d_No=56&ST=T&SV =
b) Secure coding guide (line regards / KISA)
http://www.moi.go.kr/frt/bbs/type001/commonSelectBoardArticle.do?bbsId=BBSMSTR_000000000012&nttId=42152
https://www.kisa.or.kr/public/laws/laws3_View.jsp?mode=view&p_No=259&b_No=259&d_No=55&ST=T&SV=
c) OWASP Top 10 (Open Web Application Security Project)
https://www.owasp.org
https://github.com/OWASP/Top10/raw/master/2017/OWASP%20Top%2010%20-%202017%20RC1-English.pdf
d) Our S / W Requirement Security (separate document)
Details 1.8.2 Security Requirements
1. Each system is configured to hacking attacks to be protected from external attacks and abnormal (toxic) traffic
Should be developed not vulnerable, it should be presented to provide possible detection, blocking, and specialized features proponents.
SK Telecom
a) Redirection URL blocking, blocking incoming packets from the Internet without the terminal requests
b) TCP SYN Flooding blocked, an abnormal packet from the terminal (Fragment, etc.) upon receiving the packet block
c) to verify the correct assigned by the initially received IP packet from the terminal IP operation checking
d) Protocol tamper detection and prevention (for example: in GTP GTP, etc.)
e) IoT terminal group is possible by a group communications block with a particular group and blocking and allowing communication only
f) less than the internal network scan request block and a predetermined number using the ICMP receiving only
g) increased traffic due to terminal malfunctions such as abnormal traffic congestion defense etc.
Through the second terminal and another system when interlocked, proper authentication to be interlocked between the authorized system.
a) such as an authentication token validity control (24 hours) function (note that the session authentication per session)
The third terminal and the other system when interlocked, the main information (IMSI, MDN, additional subscriber information, location information, etc.) and for the traffic,
It shall be encrypted.
4 should be developed so as not susceptible to enforce such security for a specific program or script.
5 SQL to LDAP, SOAP, HTTPS, Oauth, protocols and message store used by the DB system, etc.
It should provide a defense for injection, XSS, Format String injection attacks and should be developed to avoid such
vulnerabilities Buffer / Heap overflow / underflow.
Tool used to automate such scanning or 6 for Burst Traffic caused by DDoS (including DoS) attacks
Control functions to be provided, should be presented to provide specific functionality available from proponents.
a) PPS controlled by a specific IP / PORT / TCP Flag
b) specific Pattern (Payload within a specific character string) detected and controlled, such as PPS
7, the operation message, the user terminal or the visible anomalies conduct data transfer on the given information, such as deviated
It shall be provided by the detection / informational / off function.
8 message authentication, user information storage, performance management, all activities, including all user access and work locations
For log generation / storage and thus to verify the validity, integrity and the like, should be provided, such as specific locations occurs when the alarm function.
9 for each configuration management system shall be provided with connectivity via user authentication, when required, detailed configuration
It should be provided access controls, rights management-specific factors.
a) Single Sign-On capabilities and Two factor authentication must be supported
b) the default account password force changes, the password and a predetermined length or more systems connected account
c) for a password to be provided with a periodic function to change the password setting to be changed and also
d) it must be separated management screens based on user access rights, the major search through the elevation
SK Telecom
10 Number of terminals adversely affect the network when you are hacking attempts or malware spreading harmful traffic (IMSI,
Extracts containing IMEI) and be able to block the attack.
a) identify in real time the level of the abnormal traffic patterns and corresponding isolation
b) If the block has a specific pattern, receiving more than the threshold at the terminal
c) charging or non-real time class with respect to the terminal leads to an abnormal traffic accounting, etc. can be
11 NAT (Network Address Translation) to be designed and implemented to operate in a network configuration.
1.8.3 Security provisions
1 5G system must be software source code vulnerability assessment and action in the previous step, commercialization, and related
It shall submit the data.
The two presented above apply security details must be maintained even after the PKG application and system re Instantiation.
Three of the latest security issues for the 5G system requirements to proceed with regular information sharing and Research, the system
If the vulnerabilities that can affect, and shall proceed to quick action. Shall continue managing / 5G support to prevent the interruption
of service due to security issues.
1.9 System Evolution
The proponent shall be presented in detail along with a system based on evolution-related measures.
1.9.1 support system evolution
1 Our 5G system, but apply the 3GPP Release 15 standard by default, since the future Release 16 ~
It should provide standards-based features.
2 5G system be capable of being evolved through the S / W Upgrade during evolved 3GPP Release 16 and later, and performance
And decreases, and H / W change should not occur.
3 Release 15 and Release 16 during subsequent evolution of each Protocol and Interface Enhancement possibilities and S / W
It should provide a basis to change the room.
Relea se 16 an d beyond
eMBB / URLLC
division
NoMA Unlicensed Access V2X enhancement
Backhaul mMTC
Whether Evolution
Development Schedule
SK Telecom
Changes
Limitations
In addition to a) indicated in the table above Feature, if there is additionally possible evolution features, can be implemented by extending the above table.
b) If this occurs during the evolution restrictions it should provide ways to compensate.
c) RAN, separate Core equipment to mark and, in the case of the RAN equipment, shall be provided, including a constant for a support
band.
4 NSA↔SA switch 5G of the system should be provided in S / W Upgrade based.
5 5G system must be able to accommodate integrate existing LTE services / Traffic.
6 Add our ATSCALE Architecture architecture / technology by 3GPP Release Protocol sophistication and new features
It should be possible.
1.10 BMT / DVT Availabilty
1 test schedule where possible, Scope, upon our progress and BMT specifically separately classified as Lab and Field
a) BMT place if domestic areas, testing equipment available, the environment, Scope and Schedule
b) BMT if the place is a foreign country and city, testing equipment available, the environment, Scope and Schedule
Our two test and where possible during the progress DVT, Scope, Schedule and specifically divided into separate Lab and Field
a) if domestic areas, testing equipment available, the environment, Scope and Schedule
b) if the foreign country and city, testing equipment available, the environment, Scope and Schedule
1.11 Open Source Support
One proponent in the use of virtualization-related S / W and OS, DB and server-related S / W and Openstack CentOS, Maria
DB should be able to take advantage of such Open Source S / W.
a) If you use a specific S / W Open Sourece shall present the change availability and schedule.
SK Telecom
2 5G Radio Access Network
2.1 RAN shape and structure
2.1.1 RAN Architecture
Geometry under consideration by our 5G RAN Architecture (NG-RAN) were as follows:
Figure 2.1.1-1 5G RAN Architecture
2.1.1.1 RAN Function Split
1 F1 Interface between gNB-CU and DU-gNB is subject to the 3GPP specification (TS 38.470 ~ 38.475) and open
It shall provide the Interface.
2 gNB-DU separately Hardware and Software without further separation in gNB-DU-h (high) and gNB-DU-l (low) is
3 gNB-DU-h and Fx Interface between gNB-DU-l is Option 6 (MAC-PHY Split), Option 7 (Intra-PHY Split)
And to consider such, proponents must comply with the Option to specify our future and should provide open Interface.
4:00 own standard requirements for the implementation of our Fx Interface should reflect this.
SK Telecom
Figure 2.1.1.1-1 RAN Function Split
5 Fx Interface and is at gNB processing time and the need to satisfy the minimum HARQ perspective 20km transmission distance,
It must present a Simulation or measurement results. (Of UE processing time is processing time gNB
1.5 times the home. Slot length Number of HARQ Process and Presentation)
6, including the F1 / Fx Interface should provide a eMBB 4ms, URLLC 0.5ms Air latency, each section
It should provide a latency. (GNB-CU, F1 Interface, gNB-DU-h, Fx Interface, gNB-DU-l)
2.1.1.2 CU-CP - CU-UP separation
1 gNB-CU should support the CU-CP and CU-UP-separated structure as shown below.
Figure 2.1.1.2-1 CP - UP separation and Interface
The separation capacity of 2 CU-CP and CU-UP should be possible.
E1 Interface between 3 and CP-CU-CU UP shall provide an open Interface.
4 gNB-CU-CP and gNB-CU-UP should be capable of being flexibly arranged such affairs exchange, concentration affairs.
5 NR / LTE Tight shall not affect the Interworking.
SK Telecom
2.1.2 gNB H / W shape
1 gNB shall support the band.
a) 3.5 ㎓ (3.4 ㎓ - 3.7 ㎓)
b) 28 ㎓ (26.5 ㎓ - 29.5 ㎓)
2 gNB should support the following for each frequency band.
division 3.5 ㎓ 28 ㎓
IBW / OBW 100 ㎒ / 300 ㎒ 1㎓/3㎓
Channel 1 (3.4 ㎓ - 3.5 ㎓) Channel 1 (26.5 ㎓ - 27.5 ㎓) Channel
Support Channel Channel 2 (3.5 ㎓ - 3.6 ㎓) 2 (27.5 ㎓ - 28.5 ㎓) Channel 3 (28.5
Channel 3 (3.6 ㎓ - 3.7 ㎓) ㎓ - 29.5 ㎓)
Duplex Dynamic TDD Dynamic TDD
3 Out of Band Emission and regarding Spurious shall comply with the 3GPP TS 38.104 and the local technical standard.
4 3.5GHz / 28GHz respectively to the gNB-DU (gNB-DU-h + gNB-DU-l) one-piece removable and equipment must be provided as shown.
Figure 2.1.2-1 RAN E2E Network
5 and gNB-CU and DU-gNB-h must provide a one-piece virtual base station equipment, a separate H / W Accelerator
If necessary, it shall present a detailed specification and design.
The 6 3.5 ㎓ / 28 ㎓ Inter-band CA and 28 ㎓ Intra-band CA must support.
SK Telecom
7 gNB-CU base station equipment and gNB-CU + gNB-DU-h integrated base station equipment as shown in the figure below, SDRAN
It shall comply with the structure.
Figure 2.1.2-2 SDRAN structure
COTS Server that supports virtualization and 8 must be at least two species, support the COTS Server H / W Pool which
2.1.2.1 gNB-CU
1 gNB-CU shall satisfy the following requirements should be specifically provided for presenting items requested.
division gNB-CU
2U week) gNB-DU-h per (removable) More than 50
gNB-DU per 2U (one-piece) 1000 or later

Week) Height standard equipment (1U: 44.45mm)
a) it shall give the maximum support per 2U Cell.
b) support BW, support Layer, supported when the number of changes per 2U Support Cell Function Split Option depending on fluctuations should be provided with
detailed conditions can support Cell.
2 If there is a separate H / W Accelerator shall give a detailed standards and specifications.
3 should be provided to the equipment details and features described shape also.
a) shall give a detailed H / W and the structural units also mounted Block Diagram.
SK Telecom
d) Detail H / W Configuration Unit Name, the main function, should be provided whether or not the main control module description, redundancy.
4 presents the devices in Size Height (mm) x Width (mm) x Depth (mm) and the weight (kg) and the volume (Liter)
5 supply equipment should be provided on the power system (the standard voltage, the operating voltage range).
6 shall be given to equipment consuming energy.
a) it should be provided to the average power consumption of the equipment according to one of the preceding claims in 2.3.6.
and b) in accordance with paragraph 2 to 4 of the 2.3.6 it is provided a low-power design and operation solution of the machine.
c) it shall be presented Cooling way. (For example: Natural cooling or Fan cooling)
d) it should be provided to the operating temperature and humidity. (Example: 0˚C - 50˚C, 10-90%)
2.1.2.2 Separate gNB-DU
1 If gNB-DU is detachable gNB-DU-h shall comply with the following requirements.
a) Cell number per 2U is to be not less than 36Cell, it should be provided to support the maximum number Cell.
b) support BW, support Layer, supported when the number of changes per 2U Support Cell Function Split Option depending on fluctuations should be provided with
detailed conditions can support Cell.
2 If there is a separate H / W Accelerator shall give a detailed standards and specifications.
3 and gNB-DU if one detachable gNB-DU-l shall satisfy the following requirements, with respect to the proposed request items
To be presented in detail.
division 3.5 ㎓ gNB-DU-l 28 ㎓ gNB-DU-l
weight Less than 20kg Less than 20kg
volume Less than 16L It presented the request
wind pressure 60m / s or more 60m / s or more
Assisted Cell One or more Cell One or more Cell
DL 256QAM 256QAM
Modulation
UL 64QAM 64QAM
Tx / Rx shape 64T64R 256T256R
EIRP More than 70dBm More than 68dBm
MIMO Layer More than 16 8 or more
Beam Scan Range:
3dB Beamwidth: 120 ° (horizontal), 60

Beamfor Horizontal / Vertical Angular Range
65 degrees degrees (perpendicular)
ming (Total Beamwidth)
(horizontal), 12 degrees (perpendicular)
(Beam Scan ID
selectable)
SK Telecom
Beamforming implementation Digital Hybrid
a) for the H / W-shaped support 128 Tx / Rx 24 and Layer shape when 3.5GHz should be provided separately.
4 should be provided for each unit road and functional description details specific shape.
a) Baseband, shall include a description of the like RF Transceiver, Antenna, Array Beamforming.
b) it is provided Test Port (transmission and reception) for measuring the RF and shall present a measuring room.
c) should be provided to be shaped (Cell / Sector) detail H / W and the structural units also mounted by each Block Diagram.
5 presents the device-specific Size, shown above in Height (mm) x Width (mm) x Depth (mm) and weight (kg) and
It shall give the volume (Liter).
6 should be provided to a device-specific power supply method (standard voltage, the operating voltage range), shown above.
7 shall present the amount of power consumed by each device.
d) it should be provided to the operating temperature and humidity. (Example: -20˚C - 50˚C, 10-90%)
2.1.2.3 Integrated gNB-DU
1 If gNB-DU integral and gNB-DU shall meet the following requirements must be satisfied, on the request presented items
About to be presented in detail.
division 3.5 ㎓ gNB-DU 28 ㎓ gNB-DU
weight Less than 20kg Less than 20kg
volume Less than 16L It presented the request
wind pressure 60m / s or more 60m / s or more
Assisted Cell One or more Cell One or more Cell
DL 256QAM 256QAM
Modulation
UL 64QAM 64QAM
Tx / Rx shape 64T64R 256T256R
EIRP More than 70dBm More than 68dBm
MIMO Layer More than 16 8 or more
Horizontal / Vertical 3dB Beamwidth: Beam Scan Range:

Beamfor
Angular Range 65 degrees 120 ° (horizontal), 60
ming
(Total (horizontal), 12 degrees (perpendicular) degrees (perpendicular)
SK Telecom
Beamwidth) (Beam Scan ID selectable)
Beamforming nine
Digital Hybrid
Current approach
a) for the H / W-shaped support 128 Tx / Rx 24 and Layer shape when 3.5GHz should be provided separately.
2 should be present also and functional description of each specific equipment detailed shape.
b) it is provided Test Port (transmission and reception) for measuring the RF and shall present a measuring room.
3 presents the equipment by Size, shown above in Height (mm) x Width (mm) x Depth (mm) and weight (kg) and
4 to be presented to a machine-specific power supply method (standard voltage, the operating voltage range), shown above.
5 should be provided for each device-specific power consumption.
d) it should be provided to the operating temperature and humidity. (Example: -20˚C - 50˚C, 10-90%)
2.1.2.4 Other forms
2.1.2.4.1 Building a Small Cell Solution
1 5G Small Cell in-building solutions targeted for in-building coverage and apply my small basically 1-Cell
It is configured as a unit, to be considered gNB DU-piece shape.
2 5G-building Small Cell solution shall satisfy the following requirements, requesting details about the proposed topics
division Small Cell (the building)
3.5GHz: 30mx30m more than

Coverage
28GHz: 20mx20m or more
SK Telecom
Assisted Cell Cell 1
3.5GHz: at least 4-Layer

MIMO
28GHz: 2-Layer over
3.5GHz: 24dBm or higher / Layer 28GHz:

EIRP
27dBm or higher / Layer
DL 256QAM
Modulation
UL 64QAM
~ Configured RF antenna Integrated
weight 1.5kg or less
volume 2.0L or less
power AC 220V
Cooling Natural Cooling
Etc Indoor Compact shape
Operating temperature 0 ~ 50 ℃
Humidity 20-80%
3 to be present also and functional description of each specific equipment detailed shape.
a) Baseband, shall present the H / W structure and function of such RF Transceiver, Antenna, Array Beamforming.
b) it should be provided to provide Test Port (transmit and receive) for the RF measurement, or the measurement methods.
c) shall give a detailed H / W Configuration Unit configuration, and system-wide Block Diagram.
d) shall give a detailed H / W Configuration Unit Name, the main function, the main control module described.
4 should be provided to equipment by Size, shown above in Height (mm) x Width (mm) x Depth (mm).
Shall be presented to five devices consume power.
2.1.2.4.2 In-building / metro Distributed Solutions
1 5G of the building / metro Distributed solutions in the building and metro area service providers within the various spaces
Purpose and in consideration of the number of installation of the equipment must be designed to gNB DU-DU-l h & gNB distributed architecture.
2 Number of buildings / Metro solutions are to be built-in support for MIMO,
a) In-building solutions 3.5GHz or more 4-Layer, Layer-2 the case of 28GHz or more
b) subway solution 3.5GHz 4-Layer above, in the case of a 28GHz-Layer 2 over support, but receiving the distributed MIMO Layer which can ensure the same
capacity compared to the same area of ground Macro
SK Telecom
3 or the MIMO 5G Layer of the base station for the unique capacitance provided by multiple service areas within a building / underground space
It should consider a system architecture that can be applied to distribution.
4 Cascade configuration be available for the equipment installed in a number distribution structure applied during in-building / metro area and
The highest priority service of the equipment, the equipment Dedicated Layer, coverage extension purposes are to be considered all the way to
configure the Copy Layer.
2.1.2.4.2-1 3.5GHz and 28GHz distributed architecture distributed architecture
5, consider the Dynamic TDD service and Macro network synchronization is required and gNB-DU-h ~ gNB- To this
DU-l the Delay Time Advanced Features for compensation arising between lines should be implemented and should the operator for a variety of site
conditions can be configured to set the Time Advanced settings randomly.
6-building / number applied to a subway gNB-DU-to-l synchronization is also required and for this purpose between each equipment Sync Timing
That should be applied.
7 states in the building / site and remotely to multiple subway gNB-DU-l ease of applying monitoring and supervisory control
It shall provide the control functions possible.
8 3.5GHz configure gNB-DU-h ~ gNB-DU-l interval in consideration of the ease of building a distributed architecture to UTP Cable and is to be considered the manner
in which power is supplied to the PoE system without applying a separate AC power source.
9 28GHz For a distributed architecture to gNB-DU-h ~ gNB-DU-l interval in consideration of the capacity to Analog Fronthaul
Transfer and taking into account the damping characteristics to be considered by way of interlocking IFoF (IF over Fiber) method.
10 to be tunnel-like equipment is installed in a subway tunnel is shaped by Slim considering that within a limited mounting space tunnel
And be H / W structure capable of transmitting and receiving signals via an antenna attached integrally to the equipment side.
11-building / metro solutions shall meet the following requirements.
division 3.5GHz 28GHz
Distributed: 30m within the Distributed: 30m within the

Coverage
tunnel: about 200m tunnel: about 200m
Assisted Cell Multi-Cell Multi-Cell
MIMO Layer At least 4-Layer 2-Layer over
EIRP (scatter) More than 24dBm / Layer More than 27dBm / Layer
SK Telecom
EIRP (tunnel) More than 55dBm / Layer More than 52dBm / Layer
Transmission UTP + PoE or other IF over Fiber
DL 256QAM
Modulation
UL 64QAM
~ Configured RF antenna Integrated
Distributed: 1kg or less

weight
tunnel: 15kg or less
Distributed: 2.0L or less

volume
tunnel-type: 20L below
DC (POE distributed) AD / DC (tunnel

power AC / DC (tunnel, Rectifier Type)
type, a rectifier integrated)
Cooling Natural Cooling
Operating temperature Scatter (indoor) 0 ~ 50 ℃, tunnel-type (outdoor) -30 ~ 50 ℃
Humidity Scatter (indoor) 20 to 80%, the tunnel type (outdoor) 5 to 90%
12 should be provided for each unit road and functional description details specific shape.
b) it should be provided to provide Test Port (transmit and receive) for the RF measurement, or the measurement methods.
13 should be provided to equipment by Size, shown above in Height (mm) x Width (mm) x Depth (mm).
14 must present the amount of power consumed by each device.
15 UTP scheme shall not use the Delay and degradation issues.
2.1.2.4.3 Coverage Extension Interface Solutions
1 Coverage Extension Interface solutions shall meet the following requirements.
division 3.5 ㎓ 28 ㎓
Assisted Cell 1 Cell Based 1 Cell Based
Analog IF center frequency 150MHz 3.5GHz
Port can The same number of DU Tx / Rx The same number of DU Layer
DL Level - 10dBm (Max) - 5dBm (Max)
UL Level 0dBm (Max) 0dBm (Max)
Modulation DL 256QAM 256QAM
SK Telecom
UL 64QAM 64QAM
Connector Type SMB Female SMB Female
LVTTL (0V ~ 3.3V), provides LVTTL (0V ~ 3.3V), provides

TDD Sync (DL / UL)
one or more ports one or more ports
5dBm, provide more 5dBm, provide more

10MHz Reference
than one port than one port
power DC + 24 / -48V (Free Voltage) DC + 24 / -48V (Free Voltage)
2 20Km over Time Advanced offers the ability to support the Optic Line and the implementation measures for it
3 Time should be provided to more than 1us Delay Step for Advanced Features, Time Advanced Function when applying
It should be no performance degradation.
The signal received through the UL Path Path gNB UL received at 4 Coverage Extension Interface Solution
It is separated to be free from cross-Noise Effects.
6 that no performance degradation for Coverage Extension Interface solution sufficient UL signal on UL Path
It should ensure a Dynamic Range.
7 PAPR of the DL signal and can be less than 10dB (0.01% based on CCDF) (0% by Cell Loading, 20%, 50%, 80%,
It should be provided for 100%) measurements or estimates.
8 should be provided to the equipment details and features described shape also.
a) IF Interface Configuration / Block diagram / Power Budget and DL / UL Path for the DL / UL Port Path of the matching should be provided at the
best repeater Level.
b) it must provide the Test Port (transmission and reception) for RF measurements.
9 presents the device shown above by Size Height (mm) x Width (mm) x Depth (mm) and weight (Kg) and
Shall be presented 10 devices consume power.
c) it should be provided to the operating temperature and humidity. (Example: -20˚C - 50˚C, 10-90%)
SK Telecom
2.1.3 Fronthaul
2.1.3.1 Transmission Standard
1 Fronthaul refers to gNB-CU or less F1 Fx Interface.
2 F1 if no restrictions on long-distance transport in our Ethernet-based and Open Interface based
City Solution and works shall be free from restrictions.
3 Fx Interface transmission distance considering the gNB-DU-h, Processing Time and HARQ of gNB-DU-l Minimum
It is able to support and 20km and gNB-CU and F1 Interface transport distance between the one-piece gNB-DU also be able to support at least
20Km or more.
4 should be provided to support a maximum possible transmission distance of the F1 and Fx Interface Interface.
5 gNB-CU and DU-gNB transmission capacity between the variable is changed in consideration of the maximum data throughput of UE
Should be possible, it should be specifically presented in the transmission capacity.
The 6-gNB CU and DU-gNB (including removable and integrated) section should be free from limitations in the transmission distance. This
Transfer of support measures for the consideration of the development schedule shall give the Roadmap developed by the transmission capacity.
7 gNB-CU and DU-gNB (including removable and integrated) in the network architecture that supports the redundant path and a beam of the sections
When the line protection switching operation for disconnection to the beam (<50ms) flood (Call drop) will be free.
Protocol required for 8 gNB-CU and DU-gNB (removable and integrated included) sections Fronthaul network interface
Standard (Frame Information, indexation, etc.) should be provided in detail in the Company, the Company shall not have its own wired network and Solution works in
question.
9 gNB-CU and DU-gNB (removable and includes integrated) section Fronthaul physical layer required for the network interface
Specification (Synchronization, Jitter, Bit Error Ratio, Packet Error Ratio, etc.) should be provided in detail in the report.
10 gNB-CU and DU-gNB (including removable and integrated) equipment and our WDM (Wavelength Division
For Multiplexing) -PON (Passive Optical Network) technology in conjunction Fronthaul transmission equipment must support the content of 2.1.3.5.
11 Our Fronthaul the optical module developed for the transmission equipment and the interworking is gNB-CU and DU-gNB (removable and integrated
The implementation and linked to the equipment included) should be available.
If during interworking between 12 gNB-DU-h and gNB-DU-l Protocol two days CPRI way, our operational management aspects seonbeon Chapter Management
Specific information (Serial Number, such as an overhead position and Message Format) for the automation to be provided for the information for identifying the
connection information.
SK Telecom
2.1.3.2 Topology
1 gNB-CU and DU-gNB (one-piece) Area network structure is directly coupled to the beam, as shown below PtP, Star, Tree,
Chain (Cascade), be able to support the Ring and even in our WDM-PON technology Fronthaul transmission equipment and the interworking should be
able to support the same topology, without any restrictions.
- PtP] gNB-CU gNB-DU
gNB-DU
[Star] gNB-CU
gNB-DU
gNB-DU
[Tree] gNB-CU gNB-DU
gNB-DU
[Chain] gNB-CU gNB-DU gNB-DU gNB-DU
[Ring] gNB-CU gNB-DU gNB-DU gNB-DU
2.1.3.2-1 gNB-CU and DU-gNB (one-piece) structure section
2 For gNB-DU-h and gNB-DU-l (DU removable) separate equipment interval network structure is a beam, as shown below
Is directly coupled PtP, Star, Tree, Chain (Cascade), be able to support the Ring and even in our WDM-PON technology Fronthaul transmission equipment and
the interworking should be able to support the same topology, without any restrictions.
- PtP] gNB-CU gNB-DU-h gNB-DU-l
gNB-DU-l
[Star] gNB-CU gNB-DU-h
gNB-DU-l
gNB-DU-l
[Tree] gNB-CU gNB-DU-h gNB-DU-l
gNB-DU-l
[Chain] gNB-CU gNB-DU-h gNB-DU-l gNB-DU-l
[Ring] gNB-CU gNB-DU-h gNB-DU-l gNB-DU-l
2.1.3.2-2 gNB-CU and gNB-DU-h / gNB-DU-l (DU-removable) Area Structure
SK Telecom
3 Star, Tree, Chain (Cascade) and Ring network architecture can support the case of Node-enabled devices and network operation during
It shall give considerations.
2.1.3.3 Link Set-up and Negotiation
From 1 Fronthaul Link interval setting can be selectively performed in a fixed (Fixed) and the automatic type (Negotiation)
We have to WDM-PON technology Fronthaul even in conjunction with the transfer equipment in the same manner without any restrictions optionally fixed (Fixed) and
the automatic type (Negotiation) Link setting is should be possible.
2 Link Setup time is sufficient time to consider the linkage with our WDM-PON technology Fronthaul transmission equipment
Period should be as short as possible, while providing (Time period) and if necessary, (<20 seconds), you should be able to change the time period.
3 mesh structure in all cases (e.g., Ring, Star, Tree, Chain (Cascade), Ring, our WDM-PON technology
Fronthaul transmission equipment to be specifically presented for the Link Set methods and details of the interlocking set time) considering the fixed (Fixed) and
the automatic type (Negotiation).
2.1.3.4 Delay measurement and compensation
1 Fronthaul should support the Delay Time Adjustment feature for the measurement and compensation of the interval.
2 Delay Measurement of Fronthaul interval must be possible to support the transmission distance to be presented in Section 2.1.3.1, and support up to
It should be provided as possible Delay measurement, Delay compensation value, and the transmission distance.
a) support up Delay measurements, a compensation value and the distance (to the first gNB-DU or gNB-DU-l)
b) gNB-DU or gNB-DU-l is when connected to Casecade gNB-CU / gNB-DU-h ~ end gNB-DU / gNB-DU-l for up Delay Delay measurements, a
compensation value and the distance (up Cascade The configuration)
3 Delay Measurement considering the network structure in all cases the transmission distance (the minimum, 10km, 20km, max) required by
It shall give a measure of time.
4 to momentary transmission distance changes, such as line protection switching operation for disconnection to the beams in the region Fronthaul
Be for Flood (Call drop) Delay the measured value is automatically compensated for and so that even when linked with the Company WDM-PON technology
Fronthaul transfer equipment should be the same, the Delay measurement value is automatically compensated for without any restrictions.
5 Delay value service affected by the re-measurement (Call drop) so that the Delay measurement must be performed in real-time
And it must be able to automatically apply the Delay value variation thereof. In addition, it should be provided to compensate the maximum possible
Delay value.
6 Delay measurement method performed by the Fronthaul interval, the Delay Compensation method and a method of re-measurement and the reference details
About to be specifically presented.
a) Delay Measurement
b) Delay Compensation method
SK Telecom
c) Delay change detection method, and then re-measured and the change Delay Compensation method
d) Basis for Delay Delay reference value and a reference value, etc.
2.1.3.5 Transmission equipment interworking
1 in 2.1.3.1 Even our WDM-PON technology Fronthaul transmission equipment and interlock as shown below
This support must be sent away to be presented and shall state the value of Latency transfer of equipment required to
support them.
[Fronthaul transmission equipment of WDM-PON technology;
T-SFP gNB-DU
gNB-CU COT
RN
gNB-DU-h T-SFP gNB-DU-l
※ COT: Central Office Terminal, RN: Remote Node, T-SFP: Tunable SFP
2.1.3.5-1 Fronthaul network structure
2, the transmission capacity to be presented in 2.1.3.1 through our WDM-PON technology Fronthaul transmission equipment and the interworking
And supports should be, gNB-CU and DU-gNB (including removable and integrated) should be provided for the maximum transmission capacity interlocking Considering
Roadmap development of equipment.
3 The SFP (Small Form-factor Pluggable) developed in our WDM-PON technology Fronthaul transmission equipment
Your light modules that meet the MSA (Multi-source Agreement) gNB-CU and gNB-DU (including discrete and integrated) should be possible to mount the
equipment and must be able to support the works in the equipment, detailed optical modules related requirements follow the content of the 2.1.5.
4 WDM-PON technology Fronthaul line protection switching operation for disconnection to the rays of the interlocking of the transport equipment
When (<50ms) flood (Call drop) will be free, and line protection switching operation when to be presented specifically with respect to the detailed
condition, and a specification generated flood (Call drop).
Using Protocol Specification (Frame information, the interlock system, and so on) information provided by the 5 2.1.3.1 while in our WDM-PON technology Fronthaul
transmission equipment line information (gNB-CU and DU-gNB (including removable and integrated) by the machine It never should help you to extract product
information Serial and IP information, etc.) that do not overlap with other devices on the same network.
Physical Layer Specification (Synchronization, Jitter, Bit Error Ratio, Packet Error Ratio, etc.) The information provided in 6 2.1.3.1 must help
our WDM-PON technology Fronthaul transmission equipment can be integrated.
SK Telecom
2.1.4 Backhaul
2.1.4.1 Interlocking Interface Specification
1 is gNB Backhaul wired network or gNB-CU-CU equipment and backbone connecting the devices and equipment between 5G Core
It refers to a wired network connecting the network.
2 gNB-CU Backhaul Equipment Interface is connected and has built-in support for Ethernet.
gNB-CU connection bandwidth equipment and 3 Backhaul shall provide the total capacity Cell accommodated, the required
Backhaul capacity and shall give the Port number / specification. However, UTP Interface Type is impossible.
4 gNB-CU is in case you have Backhaul traffic growth supports link aggregation capabilities.
5 gNB-CU are (such as 1G, 5G, 10G) Multi rate support is considered Backhaul traffic should be possible.
2.1.4.2 Protocol Support
gNB CU-1 is connected to the Backhaul must support 802.1Q VLAN, 802.1ad Q-in-Q, DHCP, LACP, ECMP
do. Future must be capable of low-latency Network-based time-sensitive demands upon interlocking.
2 Network Slicing, SDN, NFV based Backhaul must be capable of interlocking with the next-generation technology.
2.1.4.3 Service redundancy scheme
1 gNB-CU is multi-homing upon Backhaul and interlocked to ensure a stable service, multiple IP
It should support the service redundancy schemes such as address.
2 gNB-CU equipment when interlocked in a manner that duplicates the uplink connecting and Backhaul, the backhaul equipment
It must be able to support the supporting redundant switching function (LACP etc.).
3 gNB-Backhaul CU according to the Active / Standby and Packet amount to redundancy during NG_U Lo ad
It should support the Share Rate and functions.
4 Backhaul should be presented in a specific way for the indexation of each port at the time of redundancy. duplication
It should support the Active / Active (Load sharing) for Active / Standby Configuration and User Data Path for between physical ports 5G Core
and Signaling Path in the configuration
5, the terminal must provide a per-session Load Balancing feature.
6 to be without switching to another Call Drop Down Interface when some of the redundant backhaul Interface (Transfer
Time less than 300 ms)
7 gNB-CU internal IP is used not to boyeoseo externally such Backhaul Port, the IP by an operator command
You can easily change must h. In addition, there shall be no IP changes when the system is restarted.
8 gNB shall not in any case during the Out Of Service Backhaul redundant operation.
SK Telecom
9 gNB is to provide the duplication of the EMS and the O & M Path.
10 gNB automatically if the Check the Link Status in Core and EMS equipment and the End To End Service and the cash
Blocking and should have no degradation of service.
2.1.4.4 Backhaul quality measurement
1 gNB TWAMP-CU is to measure the Backhaul and interlocking when, packet loss is installed in the center, delay, jitter, etc.
Y.1731 or a hardware timestamp information based on a quality measure Packet received from the quality measuring unit must write down supports the ability
to report the measurement device. (Example: TWAMP, Y.1731)
2 Hardware-based time stamp function may increase the gNB-CU CPU load affect the time stamp information accuracy
It should not, and must maintain a constant quality of measurement accuracy.
3 TWAMP or must present a hardware-based time stamp accuracy features that support Y.1731. (Yes:
± 50usec, etc.)
4 Full manner when operating in TWAMP Reflector (TWAMP Sender and spec. Negotiation through TCP port 862)
And it should support the Light mode (set manually, without Negotiation Procedure).
5 If you have a more level TWAMP quality measurable Solution can be presented.
6 using TWAMP Y.1731 or no effect on the gNB quality, and should be provided free of charge.
2.1.5 Optical Modules
First optical module refers to an optical Interface module to be supplied to all the devices and the server. It also integrated the universal structure
Using the optical module linked to standards, and the equipment and supplies servers must comply with such principles.
2 referred to as a general-purpose standard integrated Locking structure and optical properties in order to minimize the heterogeneous interworking issues /
The specifications for power / temperature shall propose appropriate standards-based optical modules
3 Multi-rate support must be possible for the investment costs and inventory control, and, using the Bi- 1Core optical cable
To provide a directional Type.
4 also, it must support 3rd party integrated optical module according to the specifications of the general-purpose structure.
5. The optical module of the optical output intensity, light intensity, type, temperature, Laser Bias current, supply voltage, and the wavelength information
It shall provide (Digital Diagnostics Monitoring) DDM information and Inventory Information (manufacturer, date of manufacture, S /
N, etc.), Vendor Specific Code should Unlocking.
6 gNB-CU and DU-gNB (including removable and integral), the optical module used in gNB-DU-DU-l-h and gNB interval is present
It is capable of supporting a maximum transmission distance to be presented to the specification and the maximum supportable transmission distance and optical
modules related detailed specification - to be present (optical standard light output intensity, the reception sensitivity and so on, electrical specifications).
SK Telecom
The optical module used in the section provided for a 7 Server, Storage and other services, it is in this specification
It is capable of supporting a maximum transmission distance to be presented, and the maximum supportable transmission distance and optical modules related
detailed specification - to be present (optical standard light output intensity, the reception sensitivity and so on, electrical specifications).
8 gNB-CU and DU-gNB (including removable and integral), gNB-DU-h and gNB-DU-l optical module used in the interval
It must satisfy the SFP, SFP +, and SFP28 MSA standard according to the transmission rate, even if a longer length of the optical module (<20mm) must not have any
restrictions on the equipment mounting and construction.
9 Server, optical modules used in the section provided for the Storage Company and other services, depending on the transmission rate
It must meet the XFP, SFP, SFP + and SFP28 MSA standards, even if the longer the length of the optical module (<20mm) shall not have any restrictions on building and
equipment mounting.
It should be enough to satisfy the temperature characteristic of the power consumption and the outdoor installation of an optical module 10 according to the transmission rate
And, current constraints for the operating SFP individual ports and all of the ports should be free.
a) Power consumption supports more than 2.5W: SFP, SFP +
b) SFP28: 3.0W power consumption over support
c) Temperature characteristics: -20 ℃ (surface temperature) ~ + 85 ℃ (surface temperature) by satisfying the low-temperature storage test, and support
2.2 General Specifications
2.2.1 mechanical specifications
2.2.1.1 gNB-CU
1 gNB-CU is to be designed in consideration of the capacity expansion and Upgrade Module as units, each Module
To be designed by a Push-Pull method of de / mounting the hoisting structure.
2 gNB-CU is considered an indoor installation, and may further take into account the Fan mounted for self-cooling when applied
To be capable of being monitored and controlled from a remote state. In addition, the Fan Fitting solutions for enhanced durability and tamper prevention should
be applied.
3 gNB-CU 19 "must be a H / W shape that can be mounted on Rack and to enable the seismic construction of the rack
It should be designed.
It is designed to avoid hot issues caused by heating equipment such as a local smooth Air Flow configuration for the device 4
And it shall present a thermal analysis data.
2.2.1.2 gNB-DU
For gNB-DU considering RAN Split Function Option to be considered gNB-DU-h / gNB-DU-l-removable structure and gNB DU-integrated
structure.
SK Telecom
2.2.1.2.1 gNB-DU-removable (gNB-DU-h)
1 gNB-DU-h are to be designed in consideration of the capacity expansion and Upgrade Module as units, each Module-specific
The ride / mounting of the Push-Pull method to be designed with ease of construction.
2 gNB-CU is considered an indoor installation, and may further take into account the Fan mounted for self-cooling when applied
To be capable of being monitored and controlled from a remote state. In addition, the Fan Fitting solutions for enhanced durability and tamper prevention should
be applied.
3 gNB-CU 19 "must be a H / W shape that can be mounted on Rack and to enable the seismic construction of the rack
It is designed to avoid hot issues caused by heating equipment such as a local smooth Air Flow configuration for the device 4
And it shall present a thermal analysis data.
2.2.1.2.2 gNB-DU-DU-one and gNB removable (gNB-DU-l)
GNB-1-one and the DU-DU-removable gNB (gNB-DU-l) equipment is integrated antenna structure and installation Tower Top
Shall be considered to satisfy the following requirements.
weight volume wind pressure
20kg or less (TBC) Below 16 Liter (TBC) 60m / sec
2 Tower Top load distribution structure on-site installation, considering the stability (Pole, Frame, etc.) and the like Solution
3 cooling system must be designed so as not to affect the quality of service, taking into account the external environment and long-term operation
And, but a separate Fan natural cooling without a base, to be so constructed that can be mounted outside the Fan as required. In
addition, it is possible to offer an additional cooling.
4 so that a curved surface is piled up for a long time during cooling operation when the natural leaves and other debris from the heat generating performance fall-type
It should take into account the mechanical shapes such as a structure.
If the RPM 5 Fan mounted on the temperature conditions must be able to be automatically adjusted to reduce power consumption, and
It should be in the Remote Monitoring and Control (On / Off and Reset) enabled.
6 Fan installed when considering the convenience of on-site maintenance and structure to be easily removable, long-term management during
It shall be so designed that the fastening failure issues due to vibration does not occur.
7 Fan noise during operation should satisfy the week 65 dBA, night 60dBA or less at 1.5m spacing condition in the equipment.
(Noise, vibration control laws claim 21, section 2)
8. Equipment be constructed in that water does not penetrate, and to prevent moisture condensation, caused by the inside / outside temperature difference enclosure
Which can be less structure.
9 and the housing and be a ground terminal for attachment inside the system, connected to the secondary ground line equipment due to lightning
It must be able to prevent damage.
SK Telecom
The 10 Pole, measures that can be easily deployed in various deployments such as External Wall, Frame, Ceiling
It shall give
11 Tower top considering how external exposure during the installation should be considered eco-friendly exterior design.
12 enclosures and fittings are corrosion and rust should not happen and does not crack the material by the external environment
It shall be used.
Plating or painting of the housing 13 must be able to be protected from external dust, moisture, salt, gas, etc., operators
It shall be possible for the seal when required equipment stomach.
It is provided outside Sample Port (wired, wireless) to measure the RF characteristics in preparation for inspection stations 14
do. Wireless method gNB-DU (integrated or removable) the devices are installed on a building wall or tower inspection stations during instrument linkage
(needed later development function) to be capable of being measured.
a) Sampling position is to be sent DL last stage, UL LNA stage.
15 Equipment must be such as to protect equipment from lightning Arrestor mounted on its own.
a) it shall provide clear specifications and standards for the equipment mounted Arrestor.
2.2.2 Electrical Specifications
1, input power must be supplied to the AC220V (single phase) or DC + 24 / -48V (Free Voltage), to the electrical specifications
It shall be satisfied.
division Standard voltage Operating voltage range Remarks
+ 24V or 48V + 30V ~ -59V

DC power supply (Free Voltage) - The equipment group: DU (indoor type)
Single phase 220V Single phase 220V • 15%

AC power supply - The equipment group: CU, DU
(60Hz) (60Hz • 5%)
Even if the applied power to the second terminal inverted and the system must not be damaged.
3 should be the external direct current power source is connected to the structure of polarity shown a clear terminal installation.
4 rectifier is installed in the indoor / outdoor and apply the following requirements, can meet temperature and humidity requirements, and environmental change
So it should be designed.
gNB-DU-one,
Separate rectifier Integrated Rectifier
gNB-DU-l
In a) a rectifier integrated equipment should be provided an auxiliary power supply (Battery) support measures.
5, the battery must be designed to be installed within or outside the rectifier, a temperature change and environmental change
It should be considered.
When replacing an auxiliary power source (battery) 6 main power supply there shall be no interruption of service gNB.
SK Telecom
7 auxiliary power source (battery) when the main power is restored to the normal state of operation used without manual interruption of operations or operational
It should be possible and should be charging the auxiliary power progress.
8, the battery must be applied to both the lead acid battery, a lithium polymer battery, a lithium ion.
On the remote to 9 remote battery charging and discharging test should provide a voltage / current setting and Alarm Threshold Function
And it shall be managed by DB for remote charging and discharging test results.
10 should be provided the power consumption according to the load of each device (Load 25%, 50%, 75%, 100%)
2.2.3 Environmental Specifications
First operation on / humidity conditions the RF transmission / reception characteristic in the standard test under the environment (the transmission output, ACLR, EVM, and so on) that you are happy
It is based.
division Outdoor type Indoor type
Highest Temperature / Humidity 50 • C / 90% RH 50 • C / 80% RH
(Retention time) (8 hours) (8 hours)
Minimum Temperature / Humidity 30 • C / 5% RH 0 • C / 20% RH
a) cyclically count: 2 times
b) the equipment is tested in the Active state
2 for a long time high temperature / high humidity environment, under operating conditions in a test based on whether our RF transmission / reception characteristic Compliant
do.
division Outdoor type Indoor type
Highest Temperature / Humidity 50 • C / 90% RH 50 • C / 80% RH
b) the equipment is tested in the Active state
3 the high temperature / humidity storage condition is our RF transmission / reception characteristic in the test under the environment-compliant and normal call processing operation
And whether based.
division Outdoor type
Highest Temperature / Humidity 50 • C / 90% RH
(Retention time) (12 hours)
b) Equipment 23 • C / changed to 50% RH (30 • After C / min) powered
SK Telecom
4 Cold Start conditions are less than one hour in a test environment under our RF Tx / Rx characteristics meet specifications and normal call processing
And based on the operation status.
Minimum Temperature / Humidity 30 • C / 5% RH
(Retention time) (12 hours)
b) After maintaining the lowest power equipment Is Temperature / Humidity 12 hours
5, the vibration condition is free from mechanical variations in the testing environment, and under the RF transmit / receive test changes the measurement value of Data
Allowed to be within range.
division frequency acceleration Sweep Rate shaft
General Equipment
5 ~ 100Hz,
Operating condition 0.1g 0.1 oct / min 3-axis (X, Y, Z)
Sine wave
(Operating conditions)
Tunnel equipment
5 ~ 150Hz,
Operating condition 2.0g 0.1 oct / min 3-axis (X, Y, Z)
Sine wave
(Operating conditions)
9 ~ 200Hz,
1.1g 0.1 oct / min 3-axis (X, Y, Z)
Packaging Sine wave
(Operating conditions) 200 ~ 500Hz,

1.53g 0.25 oct / min 3-axis (X, Y, Z)
Sine wave
a) Reference standard: GR-63-Core
6 salt spray conditions are free from corrosion or discoloration / deformation of the specimen upon visual observation (enlarged 10 times) in a test environment under
do.
Brine pH value 6.5 to 7.2
density 5%
Temperature / Humidity 35 • C / 85% RH
Spray time 168 hours
Retention time 24 hours (after the spraying, the test flight retention)
Time Sum 192 hours
a) Reference standard: IEC 60068-2-52: 1996
7 rainproof condition shall be free from traces of water in the inner housing in the testing environment below.
SK Telecom
Supply / spraying 10 mm / min
Water pressure 1.5 kgf / cm 2
Spray direction 45 jet downward angle from the horizontal
Street 1.3 m
Spray time 24 hours
8 noise conditions should be less than 60dBA in the testing environment below.
division Indoor type / outdoor type
Measuring distance 1.5 m
Measuring height 1m
a) Reference standard: GR-487-Core
9 seismic criteria are "broadcast technology standards for stability and reliability of the communication equipment," and "telecommunication equipment vibration test method" the
It is satisfied, and shall provide the products received the certificate. Richter (Richter) meets the criteria shall be 7.5 to 8.0.
10 Other environmental specifications (vibration, EMI, EMS, etc.) must also meet the test conditions and detailed specifications presented on our
do.
11 Power consumption Idle / 25% / 50% / 75% / 100% Traffic measured and submit the certification report
do.
2.3 RAN Performance
2.3.1 Capacity
NR 1 Band Range (frequency: 3.5GHz, 28GHz TDD band) per single cell in accordance with the TDD Configuration
It shall provide the Peak throughput over.
a) it should be provided to the supportable Configuration and thus Peak throughput according to the table shown in MIMO Order
and TDD Configuration outer Proposed is added.
b) The proposed performance calculation basis and shall describe the performance and provide environmental conditions.
c) the reference 100MHz 3.5GHz, 28GHz 1GHz Channel Bandwidth
# Of TDD C onfiguration ( DL: UL)

Layers DL / UL
1:01 3:01 9:01 1:03 1:09
DL 4.2 6.3 7.6 2.1 0.8

16
UL 3.1 1.5 0.6 4.7 5.7
DL 6.3 9.5 11.4 3.1 1.2

24
UL 4.7 2.3 0.9 7.1 8.5
SK Telecom
# Of TDD C onfiguration ( DL: UL)

Layers DL / UL
1:01 3:01 9:01 1:03 1:09
DL 21.1 31.7 38.0 10.5 3.3

8
UL 15.8 7.6 3.1 23.7 22.8
2, more than 25% of the Peak throughput shall provide the Average throughput in the multi cell environment.
a) it shall be set forth in the Table, and Order MIMO TDD Configuration other proponents to provide additional possible Configuration
and this Average throughput according to the support.
5% or more of the 3 Peak throughput shall provide a 5% percentage user throughput. .
a) it should be provided within a given MIMO Order and TDD Configuration outer proposer possible additional support to the Configuration and
accordingly 5% percentage user throughput in the multi cell environment table.
※ The performance requirements that may change upon completion of 3GPP NR Release 15 specifications
4 to be provided describing the maximum possible RRC, ERAB, Paging, VoLTE reference capacitance and dongjeopja be based and calculated.
2.3.2. Latency
2.3.2.1 C-plane latency
1 Idle to Active transition time (except paging delay and NAS signaling delay) should be less than 10ms.
2 Data Call Setup Time is RRC Connection Request ~ RRC Connection Reconfiguration Complete
It should be less than 10ms.
2.3.2.2 U-plane latency
1 One way to comply with the criteria Delay URLLC DL / UL 0.5ms, eMBB DL / UL 4ms.
Latency 2 E2E, respectively 30, 1000, 1500byte Ping transfer of RTD is to comply with the 10ms.
3 TDD be presented based calculation The Latency and details according to the Configuration and FDD performance Gap
The shall specify.
SK Telecom
2.3.2.3 The handover latency
1 Intra / Inter gNB Handover Latency shall be less than 10ms, it should reflect support during standard for future 0ms
do.
2 Inter RAT handover (5G ↔ LTE, 5G ↔ WCDMA) Latency should be less than or equal to 20ms.
※ handover Latency is the terminal of the handover Triggering Message by the practice handover after the time and necessary for the handover call
processing procedure for receiving a normal response from the Target Cell is completed from the time when transmitting the defined time for the Traffic
is successful, do.
2.3.3 Coverage
2.3.3.1 Link budget
1 & 3.5GHz band from 28GHz Morphology by (Dense Urban / Urban / Suburban / Rural) 2x2 / 4X4 / 8X8, etc. Order-specific support MIMO / Support
Channel Bandwidth-specific / specific QoS Cell radius and Link budget should be provided per TDD Configuration. (submit a separate Excel file)
2 3.5GHz & 28GHz presented Cell radius for each of the LOS / NLOS satisfying to satisfy QoS under DL / UL standards in-band TDD
Configuration and the following specific and should be presented to the relevant Link budget (Related Link budget submitted separate Excel
file )
division 3.5GHz band 28GHz 5G band
Bandwidth 100MHz 1000MHz
TX EIRP RX NF
(noise figure)
MIMO layer TDD
configuration 1:01 3:01 9:01 Others 1:01 3:01 9:01 Others
DL / UL Peak throughput
Coverage # 1
(Radius [m] @ 2Mbps [DL], 2Mbps [UL]) Coverage # 2
(radius [m] @ 15Mbps [DL], 2Mbps [UL])
Coverage # 3 (radius [m] @ 15Mbps [DL], 15Mbps
[UL]) Coverage # 4
(Radius [m] @ 50Mbps [DL], 15Mbps [UL]) Coverage
#5
#6
#7
SK Telecom
(Radius [m] @ 100Mbps [DL], 100Mbps [UL])
Coverage # 9
# 10
Coverage # 11
Coverage # 12
2.3.3.2 Maximum Cell Radius (In Traffic)
After a call setup to go to the Cell outside should be provided to Cell radius until the Call Drop.
TDD configuration 1:01 3:01 9:01 Others
DL / UL Cell radius (m)
a) a CP Size, gNB Tx Power etc. The measurement should be provided in detail.
2.3.3.3 Maximum Cell Radius (Idle)

100Mbps [DL], 15Mbps [UL]) Coverage # 8
TDD configuration 1:01 3:01 9:01 Others
DL / UL Cell radius (m)
a) a CP Size, gNB Tx Power etc. The measurement should be provided in detail.
2.3.3.4 Maritime ensure coverage plan
1 when the maximum Idle, In Traffic radius in question is within the 100km, 100km or more coverage can be secured
It should be provided about the ways.
2.3.3.5 Aerial ensure coverage plan
1 when the maximum Idle, In Traffic radius in question and the height of 200m within the ground compared, the 200m or more coverage
It should be provided about the measures that can be secured.
2.3.3.6 Cell Planning Plan
Shall present a Channel Modeling and Ray Tracing such 5G Cell Planning Solutions is one proponent has.
2 28GHz Standalone, 3.5GHz Standalone, 3.5GHz + 28GHz, 28GHz to 3.5GHz + + include LTE frequency 5G
Current Status and Development of Cell Planning solutions should be provided to future events. (Radius [m] @
SK Telecom
2.3.4 Mobility
1 Call Success Ratio 99% based on the maximum moving speed of more than 500km per hour, the UE may have
It is provided and should be given the maximum support possible travel speed.
2, high-speed movement, including Copy Mode must present a performance degradation if such Throughput, Delay, quality VoLTE
do.
3 should be provided a high-speed moving service measures to improve the quality.
4 presents the case with specialized functions for high-speed environmental services.
2.3.5 QoS
2.3.5.1 Reliability
99.999% required by 1 ITU URLLC Reliability should be supported.
2:00 Reliability Support should be provided Lab / Field Test methods.
3 Reliability should provide support during detailed and Call Flow Algorithm for them.
2.3.5.2 RAN Slicing
One should support the RAN Slicing features for the support E2E NETWORK Slicing.
2 SDAP Layer based on whether or not to include detailed implementation should be provided Algorithm and performance.
2.3.6 Energy efficiency
1 proposer 2.1.2 Tx output to all devices proposed in the Traffic Load and wherein such operating environment area, the average power consumption
It presents information according to the following criteria.
a) shall be described by dividing it in accordance with the Traffic Load detail in Idle, 10%, 20%, 25%, 30%, 40%, 50%, 60%, 70%, 75%, 80%, 90%, 100%.
However, the "Idle" means the normal operational status or User Traffic silriji the minimum power consumption environment is.
b) equipment, including RF portions are divided into a maximum, and Tx Power 10W unit can set the minimum distance, but presents a specific amount of power Tx
Power. However, the equipment is set greater than the maximum difference - the minimum Power can 1,000W is 100W interval, 300W - 1,000W is 50W interval,
less than 10W of the equipment can be divided into three stages, including the maximum, minimum and median Power.
c) Proposed measures of the proposed power consumption environment (on / humidity, Cell number, Tx / Rx specific path, MIMO Layer such as H / W structure, Reference
Signal settings, etc.), a reproducible method for measuring (with Traffic Load give way) the definition and present a power consumption increase / decrease pattern of
that appears when the measurement environment, such as MIMO Layer change.
SK Telecom
- Table Example city]
RF Load Tx
Idle 10% 20% 25% 30% 40% 50% 60% 70% 75% 80% 90% 100%
Power
Min
10W
20W
30W
Max
[Consumed power measurement environment;
- Temperature / Humidity:
- Wed Cell:
- Tx / Rx path can
- MIMO Layer:
[Consumed power measurement method;
[Consumed power increase / decrease type according to the measured environmental changes;
- Wed Cell:
- Tx / Rx can path:
- MIMO Layer:
2 proposer 2.1.2 claim the equipment design used in order to achieve low-power / high-efficiency for each proposed equipment, devices utilizing
It should be provided advantages and expected savings hence such.
3 proposer 2.1.2 Each proposed power saving or low power operation that we can take advantage of each device shown in
Expected to be presented to a solution containing the savings. The proposed solution should be minimal impact on the quality and the operator
must be able to easily apply / monitoring / analysis.
(Eg saving plans operating in real-time operation by operation / pre-planning or operator of Traffic Load)
4. Each equipment is operating plan that can minimize the standby power without quality effects such as service interruption is required.
Proponents suggest specific ways, such as reduction of block / control the PSU power supply in the standby state and implements to an operator, the
remote control.
2.3.7 MTBF, MTTR, MTTF
1 Proposed by the gNB-CU, a long time average innocent (MTBF) of each Board / Module of gNB-DU reliability and availability are
61,320 hours (seven years) to be less than, the average system-wide failure time to repair (MTTR) should not be more than 2 hours.
Two proponents as an indicator to measure the reliability of the Machine / System by the Board / Module of gNB-CU, gNB-DU
Should be provided for use MTTF and MTBF, MTTR is.
3 Proposed is a (Highly Accelearated Life Test) HALT the calculated last before delivery MTBF method and result
SK Telecom
4 proposer Borad / Module-specific delivery up to the possible failure ratio MEFR (Maximum Expected Fault Rate)
Since broken down by year, it should be provided for more than 10 years.
a) MEFR is a ratio of volume a failure has occurred in the same year, compared to the material by the total amount delivered at the same time. However, it is the
summation of the number of times when a malfunction has occurred twice or more in the same year.
b) "volume a failure occurs" in the above a) refers to the repair request amount toward the provider regardless of the repair results. However, the repair request that
the material is actually not the fault provider of vocation, and if it is approved by the Company shall be excluded from the "volume failure occurred."
c) The supplier facilities or check S / W to pre-check the validity of the requested service can be provided to us. The proponent shall present a breakdown
of the equipment or the S / W that can be provided to us for this purpose.
* MTTR: MeanTime To Repair
* MTTF: MeanTime To Failure
* MTBF: MeanTime Between Failure
2.3.8 Other
The Key Capabilities and KPI achieved if, Test method, details Call Flow Algorithm and presented on the Performance other ITU-R, 3GPP
should be provided in detail.
2.4 RAN functions
2.4.1 Synchronization feature
1 synchronization is a function for accurate Network Time Sync full of such gNB.
2 gNB shall support the syncing method for synchronization technology for improved accuracy, etc. Clock
Etc. advancement must be acceptable structure.
a) GPS
b) IEEE1588v2 (G.8275.2 / G.8275.1)
3 the second paragraph synchronized manner by size, configuration methods, Clock Accuracy, support and distance restrictions should be provided.
a) each be provided for a GPS, IEEE1588v2 PTP (each containing Profile history support and constraint).
b) for the system-specific synchronization scheme configured to be presented gNB-CU and DU-gNB (for each of the one-piece), gNB-DU-h and
gNB-DU-l (removable).
c) it should be provided by the interlock system synchronization scheme (BC, TC ( P2PTC / E2ETC), OC)
4 gNB shall support gNB between synchronization by utilizing the synchronization method 2 above.
SK Telecom
Between 5 and 5G gNB Core time synchronization ( Time) The support should be.
6 gNB is hadeorago of synchronization failure Frequency 48 hours or more, Time & Phase 24 hours or more
Shall maintain Holdover, it should be no performance of the system during the Holdover Time, status, and deterioration of the quality of service.
7 via our wired Network (IP backhaul / backbone / Fronthaul include groups that are operating system), a synchronized manner
It should be supported.
a) gNB must satisfy all of the Feature Supports ITU-T G.8275.1 Multicast, G.8275.2 Unicast Nego and presented in the standard.
b) gNB are to be capable of receiving at least three or more Clock Reference for a signal to IEEE 1588v2 and should be automatic transfer in case of more than
quality of a signal that is used as the primary clock source. It should also be possible to Clock Reference in the following combinations.
• GPS (Master) + IEEE1588v2 (Slave)
• IEEE1588v2 (Master) + IEEE1588v2 (Slave)
• IEEE1588v2 (Master) + GPS (Slave)
c) The synchronization method used for each base station should be no performance degradation and functional limitations due to Clock Source.
d) it should provide automatic transfer of a Reference clock (IEEE1588v2 etc.) when another GPS failure, should or vice versa
• Rebooting the system or the Power Off / On poetry should be kept intact Clock Sync.
e) The IEEE1588v2.1 such advanced technology for Time Accuracy improvements should be possible.
8 by the operator to be possible to change the synchronizing method.
9 future due to our requirements 他 It should support a synchronized manner.
10 Manufacturers must present the specific synchronization performance, improved reliability measures.
2.4.2 call processing
2.4.2.1 Basic Features
1 shall provide system Information Broadcast feature.
2 shall provide the Access Control function.
3 shall provide the RRC Connection feature.
4 shall provide the Bearer capability.
SK Telecom
And providing a 5 Paging Control function, the operator can set the monitoring period for the UE Paging
Should.
2.4.2.2 Mobility / handover
It shall provide 1 Cell Selection / Reselection function.
It shall provide 2 Intra / Inter CU and Intra / Inter DU handover.
3 Inter-RAT handover, and it shall provide Reselection function.
2.4.2.3 Power Control
1 Cell should be set by the TX Power and shall present a detailed algorithm.
2 provides an Uplink Power Control, and must be able to establish the relevant Parameter, a detailed algorithm
3 and QCI be provided by the DL, UL Target BLER, Targer BLER should provide the ability to change.
2.4.2.4 Call Admission Control
1, taking into account the available Radio Resource, QoS requirement, priority level, RRC Call, Paging, etc. can gNB
Be in accordance with the operator setting value to restrict the outgoing call, handover call, Paging inlet and be able to set the relevant
parameters.
2.4.2.5 Overload Control
1 gNB is the traffic loaded cell for the maintenance of cell load balance handover or cell reselection
Through such parameter changes to be capable of being shifted to underutilized cell.
3 gNB in accordance with the Load Alarm performs such as Minor, Major, Critical, Alarm Load rating levels
The operator must be able to set up.
And the 4 Minor, Major, Critical Alarm such as the second highest rating, Transition to primary grade child should be possible,
Details algorithm should be presented.
Be operated in conjunction with Core end overload control according to gNB 5 Load and detail algorithms are to be presented.
6 gNB is a dynamic (Dynamic) resource allocation algorithm for load balancing if having a Channel Card structure
It shall be implemented and shall give it.
2.4.2.6 Scheduling
1 information such as the CQI, Rank Indication, PMI (Precoding Matrix Indication) sent by the UE, UE-specific QoS
It must present the requirements, detailed scheduling Considering the status of Buffer, Interference state.
SK Telecom
2 considering Interference Coordination shall control and the like, using restriction on the Resource Block.
3 gNB Scheduler MAX is possible by the operator setting the variable C / I, Proportional Fairness, RR (Round
This should support algorithms such as Robin) algorithm to enable operation and the details are to be presented.
Table MCS (AMC) allocation for CQI is a parameter to 4 Offset is possible according to the user environment,
It should be provided.
The five specific restriction subscriber transmission rate per Cell (Rate Control) should be available. For example, a particular Cell FTP
Data to prevent convergence of User (User Heavy) to be capable of controlling the transmission rate of the FTP User of the Cell below a certain
speed.
2.4.3 Resource Management
2.4.3.1 Radio Resource Management
1 Radio Resource Management (RRM) related functions comply with TS38.133, TS 38.300, TS38.331 specification
do.
2 Radio Bearer Control (RBC): When you set up a Radio Bearer overall radio resource situation, the current QoS requirements,
It should consider a QoS for the new service.
3 Subscriber Profile ID for RAT / Frequency Priority: gNB the Idle mode by the Subscriber Profile ID
And the Inter RAT handover control in the cell selection / reselection priority can be defined and connected mode in.
Four other shall provide additional functionality to provide QoS policies that we require.
2.4.3.2 Virtualization, resource management
1 gNB-CU and is open to offers Scale In / Out capabilities for virtualized resources, set by the operator
2 gNB-CU monitors the physical / logical connection gNB-DU, should support the Auto-Scaling.
3 gNB-CU shall provide the Scale Up / Down functionality for virtualized resources, set by the operator
4 gNB-CU shall provide the Migration feature (Auto / Manual) for the resource virtualized by the operator
Set this to be possible.
5 gNB-CU will not affect the quality of service when Scaling and Migration performed.
SK Telecom
2.4.4 Add-ons
2.4.4.1 LCS
1 gNB is associated, such as 3GPP TS 36.455 to provide the Location Service as defined in 3GPP TS 22.071 specification
It shall comply with the standards.
a) gNB shall provide the E-CID, the OTDOA based Location Service.
b) gNB shall support functions for GPS Location Service.
• Support UE-Assisted GPS Method functions
• Support UE-Based GPS Method functions
2 gNB should be able to accommodate our LCS solution is determined.
3. Future changes in the Company during the LCS service must accept it.
2.4.4.2 PWS
1 PWS (ETWS, CMAS) function is to be supported and shall present a configuration plan including details Node.
2 gNB should be able to accommodate disaster-related character PWS solutions we set.
3 Our future when changes in PWS services must accommodate this.
2.4.4.3 Voice services and quality improvements
From 1 5G network shall support the voice service functionality, this time to support Interoperability with our IMS network
do.
2, should support the following metrics to monitor the quality of the voice service, the next operation
It shall implement any additional required statistics.
a) voice services, Packet Delay / Jitter / Loss Statistics
b) Bearer BLER statistics by QCI
c) Call Statistics Unit Packet Interval and Threshold exceeds a certain Packet Interval occurs Statistics
3 must support the following features to improve voice quality of service, it must provide for additional quality improvements
do.
a) Supported Codec Rate change function according to the wireless environment.
b) CMR-based support AMR Rate Changes feature (TR36.750)
SK Telecom
4, voice services are to be supported the RLC AM, UM Mode, AM ~ to-Cell Mode UM during handover
There should be no loss of quality.
2.4.4.4 Energy Saving Features
One must present a power-saving feature for gNB equipment.
a) Output adjustment according to the Traffic, which minimizes the change MIMO operation, OFDM Symbol Unit On / Off, etc. Power consumption
It must support this feature.
b) In addition to the methods according to the Traffic must provide a method capable of Energy Saving.
2.4.4.5 Remote Electrical Tilting / Swing Features
1 gNB-DU, and DU-gNB-l is an antenna beam in a desired direction without further H / W on the remote Tilting / Swing
It should support the Electrical Tilting / Swing ability to, and controllable proponent shall present the Tilting / Swing maximum angle
and Control Step Range.
2.4.4.6 5G Core works
1 gNB when the MME or NGCore AMF abnormal to normal or other MME NGCore AMF
The transfer should be possible and should present a concrete plan for them.
2 MME or NGCore limit the arc in gNB during AMF overload the MME or the load NGCore AMF
Reduce, shall control the call according to the after loading, it details algorithms to be present.
3 Multi PLMN MME or MOCN should support the ability to support NG Core AMF works.
4 In-bound Roaming must support the function for DECOR MME Re-routing for the terminal.
5 shall support the Extended QoS class identifier (QCI).
The 6 gNB the S1 SETUP functions, depending on the Time to wait (S1 SETUP Failure) values passed from the MME
And to operate (MME S1SETUP control) it must be provided similar functionality in NG Core.
The 7 gNB in a handover situation has changed MME / SGW shall ensure that the service connectivity. gNB is
If an abnormal SGW should be the possible transfer to other normal SGW via the MME. In NG Core it should provide
a similar function.
8 gNB must respond to the message of GTPU ECHO SGW. Similar functionality should be available in the NG Core
do.
9, detailed requirements for the Core Network works must comply with the Core Network linked items.
Encrypted IMSI provided 10 MME and Call Setup when Initical Context Setup Request during which we presented
Decoding by the method must be utilized or the like Call Log, Call Log Fail, call trace. In NG Core it must provide the IMSI.
SK Telecom
2.4.5 RF transmission and reception functions
2.4.5.1 RF characteristics
1 RF-related characteristics of gNB systems must satisfy the transmission characteristics defined in 3GPP TS 38.104, the test
Based follows the 3GPP TS 38.141.
2 If the maximum Carrier operation and maximum output when other operators using adjacent bands Guard Band or without the need and rationale
100MHz BW when used in a) 3.5GHz band
b) when used in the 1000MHz BW 28GHz band
3 gNB and the transmission power setting and fluctuation correction on the system by Cell (Sector) of the operation needs to be supported, in which case
There shall be no interruption of service.
4 DU and equipment by specialized technology for small / light-weight to be applied, it must be presented with evidence
And (e: Cooling system technology, compact filter technology, PA efficiency improving technique, and so on)
Peak Power Reduction (Crest Factor Reduction) for transmitting the output efficiency and the improvement of the base station 5
When applying the algorithm, the deterioration of the RF signal quality is to be minimized, and that no Data resulting performance degradation.
6 to Peak Power Reduction for the base station signal and the output signal Coverage Extension Interface
Presented algorithm is applied and shall submit the detailed data for the BW-specific PAPR characteristics according to the Traffic Loading.
※ PAPR measurement criteria CCDF 0.01%
PAPR
100MHz 100MHz 200MHz 400MHz 800MHz 1000MHz
0%
50%
Cell Loading
70%
100%
7 Passive Passive IM of the RF device is not to be less than the reference minimum 3rd order 150dBc.
2.4.5.2 Power amplification
1, the maximum output can be automatically limited to the critical output power than to older high power amplifier to protect parts of
That should be implemented to the maximum output limit.
SK Telecom
2 and in accordance with the amplification technology must support the following features for self-diagnosis and fault alarm, Alarm
Based on the level required to provide a processing method such as the Alarm / Automatic Shutdown / Auto-Recovery and be interlocked with
EMS.
a) Output Power / Temperature Monitoring
b) Over Power Warning Alarm
c) Over Power Shutdown Alarm
d) High Temperature Alarm
e) Device Fail Alarm
f) Output VSWR Alarm
g) DC Input Fail Alarm
3 Efficiency Power Amp and shall present a calculated basis (Block Diagram Amp, etc.).
4 be provided with linearisation method of the power amplifier and power efficiency to improve system efficiency and miniaturization
To maximize the room should be provided in detail.
5 specialized power-saving Solution when there shall be given them.
2.4.5.3 Front-End Features
1 the received signal and low noise amplifier LNA must provide fault monitoring.
Sufficient Isolation between the two transmission paths should not interfere with the receive path characteristics in the transmission output
And it shall present a Isolation secured Implementation and boards.
3 shall provide the Test Port for transmitting and receiving signals and check the antenna VSWR measurement.
4 gNB Type should be provided by the transmission filter Rejection specification and insertion loss.
5 shall be presented to our existing base stations and feeder sharing scheme, the receiver due to PIM and Harmonic generation
It must present a plan to eliminate the effects.
a) 3.5GHz / 28GHz band 5G service on the receiving end measures affect eliminated due to 800MHz CDMA / LTE, 1.8GHz LTE 2.1GHz WCDMA / LTE,
2.6GHz LTE feeders can be shared with the room and PIM Harmonic generation
2.4.6 O & M functions
2.4.6.1 General Information
1 gNB EMS will be possible to work with our NMS (Tango-A) and a specific scheme for this Interface
SK Telecom
2.4.6.2 The Reset function
1 gNB shall provide the capability to download.
a) from at system initialization EMS S / W and parameter download functions
b) If you are having problems downloading the S / W and parameters apply to occur functionality to support Fall Back and report it to the EMS
c) due to the system failure function requiring automatically downloaded if necessary S / W and the parameter down-loading
d) redundancy (Standby-loading capabilities of the Active-Standby structure) H / W Configuration Unit
e) when a redundant unsupported (Active Only structure) Main Memory with a replacement at the time of service Processor after completing a new S / W Down
operator to the new S / W function serviceable with minimal down time of the transfer to the
f) present during system initialization downtime and provide ways to minimize them
2 gNB shall provide the capability to restart.
Restart due to a) Power On / Off
Restart function according to b) H / W Reset (with power Reset)
c) H / W Configuration Unit de / restart function according to the assembled
d) the system / H / W constituent unit / remote processor restart function according to the command to restart the EMS
When all H / W of the structural unit replacement gNB 3 and the operator must be capable of operating without any setup operation.
4 should provide the S / W Package related N + 2 → N Rollback.
2.4.6.3 Configuration management
1 gNB may transmit collected information to the shape by the EMS request to the H / W units and the processor unit
It shall provide the capability.
a) H / W Configuration Unit Mounting and shape information
b) H / W Version
c) S / W Version
2 H / W shape and operational parameters of gNB is changed and the change history when a change occurs in the resources gNB
It shall be reported to the EMS.
3. Change the parameters of the required operation should be changed and controlled without service interruption.
a) Cell Block / Deblock, the output changes, and
SK Telecom
4 LMT, Telnet (or SSH) Change H / W shape / operational parameters through the remote access, the status query, the test, S / W downloading
The real-time reporting capabilities, such as EMS and should be supported.
On DU-5 gNB using a rectifier monitoring port at a separate rectifier and interlocked be possible DU monitoring and control,
Open Interface Specifications should be interlocked.
6 shall be no loss of quality due to the parameter change process.
2.4.6.4 Fault management
1 gNB are to be reported to the EMS and detects in real time the event of the H / W failure, S / W failure.
2 gNB shall provide the ability to report the failure to place.
a) H / W failures: failure to provide the smallest interchangeable H / W unit generating information function
b) S / W Breakdown: providing the smallest S / W S / W fault occurs in Block Unit Information function
c) failure PM: No Call (Sleeping Cell), such as quality-related failure information providing function
3 gNB is malfunctioning, causes, and failure rating (Critical, Major, Minor, Warning, Indeterminate, Cleared),
It shall report the fault occurrence time, fault recovery time.
4 gNB must be able to Block the ability to minimize the impact of failure fault occurs it by EMS
It must be reported.
5 Higher Layer Split should be the quality and fault management of the interlocking section and the Lower Layer Split interlocking sections.
6 gNB-CU is to be provided with a protective function including sequentially Cell Lock, Shut Down according to the temperature, etc. Fan fault.
2.4.6.5 Performance management
1 is gNB regular time intervals by the Traffic metrics / performance-related Data (1 minute, 5 minutes, 15 minutes, 1 hour)
By the collection / reporting and operator of the requirements should be provided the ability to collect / report Data for a period of time.
Immediately collect the Alarm, or if the Traffic Statistics Data Threshold least one second operator to set encounter
It must be reported.
3 gNB shall provide the ability to collect and report the following minimum Trafic / Performance Data.
a) Traffic service by performance-related Data
• Data call tinted / outgoing Related Data
• Data handover
• Paging Related Data (including Paging Discard)
• Location Registration Data Related
SK Telecom
• Data No. Throughput (DL / UL-specific, per Cell Per User) Related Data
• QCI Stars Related Data
b) RF Quality Related Data
c) processor utilization and Overload Related Data
d) N2, N3, usage and transport-related Data Interface Error to Xn
Throughput (M-Byte, including Peak Throughput) to e) by Ethernet Traffic Port
f) RRE (RRC Re-Establishment) Related Data
g) GTP Loss, Out of Sequence Related Data
h) the RF Scheduler sanity operator shall provide a Debugging Tool or a way to determine the UE unit.
i) disaster-related characters Data
j) VoLTE should provide statistics to distinguish between (DL, UL Packet Delay, Loss%, delay interval ratio%) and Silence & Voice interval.
• Delay interval, terminal, Air, MAC, RLC, PDCP, DU Backhaul
4 to be provided with a Unique one second Trace Trace Log and focus on a specific request terminal.
a) call attempt, access success rate, Call Drop rate, transmission through rate, transmission rate, MAC, RLC, PHR, HARQ, R-BLER, CQI, RI, SINR, MCS, such as RF and
Scheduling information, Candidate UE per TTI, and so on)
5 gNB should support additional information, features and statistics for Backhaul, Fronthaul quality control.
a) SFP / SFP + / SFP28 such as temperature / voltage / optical power and wavelength of the reception level Optic Transceiver Module Shift
b) Link Speed / Link Bit Error statistics / malfunction occurred during Event Trace
Provided gNB 6 proposer shall give all possible metrics.
2.4.6.6 State management
1 gNB shall report the usage (Usage) and Overload states of the processor / H / W in the structural unit EMS.
2 gNB status (Processor, Device, H / W Configuration Unit Service Status (Normal / Fail), power), Cell Loading specific state,
When the Main Process supports redundant representation Active state the H / W structural unit shall provide reporting.
3 auxiliary power when using the auxiliary power to be provided to the remaining status reporting.
4 Ethernet Port, should provide Optic signal monitoring and fault reporting.
SK Telecom
Cell-specific DL / UL monitoring the RF signal (RF Spectrum) of 5 gNB and should provide a way to store.
a) DL / UL RF waveform and Snapshot, DL power, be capable of providing a UL RSSI periodically, and Alarm Threshold monitoring interval is
to be operator settable.
6 is gNB at regular time intervals by measuring the actual power consumption, instantaneous Peak value into a permanent red (1 minute, 5 minutes)
Collection / reporting should be.
7 should be grateful if the outdoor type equipment environmental (temperature, battery, Door Open, etc.).
2.4.6.7 Test and diagnostic functions
1 gNB provides test and diagnostic functions and be able to Report.
a) self-diagnostic function
b) the main inter-process IPC diagnostic functions
c) testing and diagnostic capabilities using LMT
Provided d) test and diagnostic functions through Remote Access accommodate from EMS
e) gNB power measurements Output Power, EIRP) by (transmit Total Power, Cell (Sector)
f) Active antennas over whether diagnostic and reporting capabilities (RF Chain, Beamforming, Auto Calibration, etc.)
g) test functions such as Loopback, Ping, Traceroute for Ethernet Port
h) Packet Capture capabilities through Port Mirroring for the Ethernet Port and Internal Switch interval
Providing i) Latency-related internal gNB Protocol Latency measurements per section
2, the operator via the EMS on demand gNB remote access and up to 20 for a particular UE IMSI / TMSI
And it is based on Protocol-specific Trace for Trace (RRC, GTP, PDCP, RLC, MAC) and Scheduling information must be available, Trace results
are to be saved as Text type.
3 gNB configuration commands for the information, Parameter change is in addition to EMS UI, Telnet (or SSH) RAN-based EMS and
GNB to connect to must be capable of MMI Command carried out and the results confirmed.
4 gNB-DU (Type), an antenna-integrated devices such as gNB-DU-l does rise in the tower and the main steel pipe simplified pylon
It shall provide remote access plans that can be checked / controlled status.
2.4.6.8 Inventory management
1 gNB shall provide to asset management.
a) reporting persons manufacturer Serial Number, and agreed to our topic, QR codes (barcodes) function
b) log-in feature for a consultation with our items (production date, installation date, service date / history, etc.)
SK Telecom
c) Backhaul, Fronthaul Port of SFP information (Company and agreed items)
d) Information rectifiers (Also, agreed with)
2 should be provided for items for device configuration information management.
a) shall provide catalog information we have defined for the total and H / W configuration unit equipment.
b) even if the equipment and components to be added in the future should provide catalog information, we have defined.
c) Description will be required to provide for the information provided by the system, such as EMS.
d) If upon the structure (schema) changes in the information provided by the EMS system, such as changes occur Package shall consult with SMC
beforehand.
e) When Changing Package information provided by the EMS system, such information must provide the relevant information before applying Package.
3 EMS etc systems typically must provide the following information:
a) the new facility during mounting and removal information in the device Activation / Deactivation via EMS should be provided immediately (within 1 second).
• Identifiers for all components that make up the equipment (Serial Number)
• Component comprises a physical unit that contains the equipment, H / W Configuration Unit, SFP, etc.
b) shall provide immediately (within 1 second) the alarm for equipment mounting information is changed, the alarm should include information to.
• Information changes mounting Type: H / W configuration unit mounting / hernia, SFP Team / hernia, mounting / Hernia of other components
• Equipment identifier, date and time change Event occurs, changes occur Event Slot / Port information, change Event occurrence H / W
Configuration Unit / SFP / identifier of the other component
c) it shall provide immediately (within 1 second) the alarm for the logical connection information changes.
• gNB-CU and DU-gNB (including removable and integrated) with each Port Cell connection relationship
• Change Event occurrence date, occurrence change Event Slot / Port information, change Event occurred gNB-CU and gNBDU (including removable and
integral) / identifier of the Cell
d) must be able to identify the equipment and components, physical implementation occurred Port Information / Change connection information provided by the alarm.
e) Mount / Connection information shall be provided separately for each Package version when available files.
f) shall include a version information Package Mount / Connection Information Changing the alarm message.
SK Telecom
2.4.6.9 Auto Connection / Configuration
1 gNB-CU according to the initial installation, large objects or operator-defined presets when re-setting the system Plug &
The setting is completed automatically within 20 minutes to the Play mode.
a) pre-set to the operator defines the IP Address Assignment Rules, shape information, PKG, Default Parameter, etc. and should be able to
develop the Plan prior to equipment unit or the entire Network.
b) to implement the EMS, such as input convenience features such that the input and Plan making process for the preset simplified for the operator defined. Minimize
this manual when equipment unit and within 5 minutes, it should be possible to set up more than 30 minutes for the entire Network.
c) The Plug & Play includes all the equipment powered equipment after setting the IP Address, operating PKG / Parameter apply, such as the End to End Process
Equipment required for the opening of. This process is conducted in a fully automated without any intervention of the operator should be completed within 20 minutes
to complete the equipment immediately should be a good transition to the services available. Shall be presented to Plug & Play step-by-step progress takes time.
d) Overall progress and results of the Plug & Play is a system to automatically verify its own operator in real time
It must be able to check the status. Error occurred during the retry performed the first automatic response to such Process must show the cause
analysis and action plan Advice If you need a manual action of the operator to operator.
e) One-Click-based or reset to the wonbok be possible if progress is not possible due to the Plug & Play procedure opened with Fail.
f) If the Plug & Play Opening a complete equipment to synchronize EMS and auto must complete the registration of the equipment, EMS is the equipment state /
alarms / time statistics, such as the automatic diagnostic / Report to the operator to determine the full final results should.
g) must also be carried, each feature gNB-CU and DU-gNB a state in gNB-CU alone are not interlocked.
2 gNB-DU according to the initial installation, large objects or operator-defined presets when re-setting the system Plug &
It shall be completed within 10 minutes This automatically sets the Play method.
Preset to the operator defined for a) gNB-DU should be established with the setting of the upper-gNB CU.
b) operator-defined presets include the IP Address Assignment Rules, shape information, PKG, Default Parameter, etc., and should be able to
develop the Plan prior to the unit or the entire Network equipment units.
c) implements the EMS, such as input convenience features such that the input and Plan making process for the preset simplified for the operator defined. Minimize
this manual when equipment unit and within 5 minutes, it should be possible to set up more than 30 minutes for the entire Network.
d) Plug & Play is that the supply voltage of the equipment after the equipment IP Address setup, and operation, including all PKG / Parameter End Application, including
the necessary equipment at the time of opening to End Process, the procedure is complete without operator intervention
SK Telecom
Proceeds to the automation must be completed within 10 minutes to complete the equipment immediately should be a good transition to the services available. In
addition, it should be presented step-by-step progression Plug & Play Time.
e) overall progress and results of the Plug & Play is automatically verified by the system itself must be able to check the operator real-time status. Error
occurred during the retry performed the first automatic response to such Process must show the cause analysis and action plan Advice If you need a
manual action of the operator to operator.
f) Plug & Play If progress is not possible in the process of opening to Fail occurs shall be possible wonbok or initialization of the One-Click
basis.
g) If the Plug & Play is complete, the equipment is in synchronization with EMS and automatically, and to complete the ad EMS is equipment status / alarm / real-time
statistics (including RF signal by Status / per antenna Cell) including an automatic diagnostic / Report by the operator that should be able to determine the overall final
result.
h) gNB-DU of the Cell-specific / per antenna RF signals (RF Spectrum) states should be possible provided the DL / UL RF waveform Snapshot, DL output,
UL RSSI so that the operator no measuring equipment at the time of deployment / operation can be found in the EMS and , Alarm Threshold and
monitoring period shall be the operator can be set.
3 gNB-CU and gNB-DU is logically remotely without physical relocation of all being accommodated each Cell
Should be mutually change the mapping of the Cell. If the feature to be added if the additional equipment, modules and components, such as for the implementation
should be provided to help with the configuration components
2.4.6.10 Other Functions
1 gNB communicates with rectifiers Rectifier Firmware Download, Version, manufacturer name, etc. that we present
It shall control the rectifier information.
2.4.7 Additional interlocking device
2.4.7.1 General Information
1 gNB are additional devices operating in the company (an optical repeater, RF surveillance, environmental monitoring device, the additional device communication HUB,
It must provide the distributor with a Node Interface, etc.).
2 gNB should provide an Ethernet communication function to the additional communication devices.
a) gNB is required to provide a separate Ethernet port for communicating with our environment monitoring server (RMS) for adding the device state information,
gNB status information, a base station environment information and the like, shall implement the interworking function.
Communication Method Transmission speed Port can Connector Type
Upward, downward 10 / 100Mbps CU: 1 dogs

Ethernet RJ45
(Auto Nego support) DU: 1 dogs
3 is gNB PAT (Port Address Translation, Port Forwarding) for communication classification of various additional devices
It shall provide the feature.
4 and Translation processing for the up to 255 per gNB Port should be.
SK Telecom
In 5 additional device gNB-CU and DU-gNB (including removable and integrated) by way of the upper communication port with gNB
Must provide a path to meet the Ethernet Communication Protocol Stack can be transmitted as additional device-specific O & M Server.
6, if the outdoor type gNB separate DC power source for the additional device can provide (+ 27V or -48V, Free Voltage)
Exist and details are to be discussed with the company added.
7-one gNB-DU and a removable gNB-DU-h, gNB-DU-l is to be possible to communicate with the rectifier. (For details,
Additional company and should be discussed.)
2.4.7.2 Outdoor type gNB environmental monitoring equipment matching
Outdoor type gNB that one proponent offered to provide environmental monitoring information to our dedicated Server Environment Monitoring System
Should.
Two way communication follows a communication method that we proposed (further provide a separate Protocol)
3 outdoor type gNB should be able to control with respect to entry via a dedicated environmental monitoring system Server.
a) Remote charge-discharge test function
• Outdoor type gNB from the remote monitoring device through a dedicated Server environment, and be capable of battery charging and
discharging test, discharge test should be designed to last more than 10 minutes
b) automatically stops the rectifier
• The ability to cut off the power at the discretion of fire or flooding occurs eNB Default is 'Disable'.
c) Environmental Threshold setting
• It must be able to change Alarm Threshold values that are the basis for generating a value other than 'Default' values. In addition, it should be able to change
the temperature upper / lower limit, rectifier / battery voltage upper / lower limit, such as Cold Start Start temperature.
d) it should be provided remotely Firmware Download feature for all the additional equipment (rectifiers, etc.), including the outdoor type gNB
4 Alarm and status reports
a) Basic Alarm history and environmental conditions that are reported to the collection and dedicated Server is the same as the table below, the Company shall be
required for Alarm History can be added.
b) shall be reported to the Alarm occurs in real time.
division Alarm Name Remarks
One HMS Cable Open
2 HMS DC Power When using (Heat Management System) HMS
3 HMS Heater Fail
SK Telecom
4 FAN Fail When using FAN
5 Door Open Door gujo
6 Flood Alarm Rack type base station
7 Temperature Alarm Measure, a high temperature / low temperature alarm

Flooding expected in the installation area concerned
8 Battery Alarm Voltage values, and the / low voltage alarm
9 Battery Test Remote charge-discharge test results store / manage
10 Rectifier Alarm (voltage, current) DC voltage / current measurement value and the low-voltage alarm
11 AC Input Alarm (voltage, current) AC voltage / current measurements
2.4.8 Multi-RAT support
1 H / W of gNB-CU and DU-gNB (including removable and one-piece) are to be available to change the RAT other than the 5G
do.
2 gNB the H / W 他 If you change the RAT, it shall present a changeable history and Restrictions, including details
3 gNB the H / W 他 When changing to the RAT, be possible to simultaneously receive and 5G, each RAT-specific by the operator
Cell number of adjustments should be possible.
4 gNB the H / W and 5G 他 Additional ways to accommodate at the same time as the RAT and its constraints, S / W, H / W in accordance with
It shall present a configuration and changes and so on.
2.4.9 Intelligent Management
One must be developed to meet the requirements related to the SON standards and our operational requirements defined in 3GPP.
2 and 'Auto-Configuration', should support the 'Auto-Optimization', 'Auto-Healing', the next Function Add
S / W restrictions should be free.
3 changes by the Intelligent Management History has to be a separate control, by an operator
Fallback should be easily available.
4 and should not occur due to the operation of the Intelligent Management Network service quality degradation,
Intelligent Management disability should not affect the Network Management and Quality of Service.
5 Intelligent Management function shall be the Sub-NE and function by ON / OFF by the operator.
6 Intelligent Management should be based GUI for managing the operational convenience.
2.4.9.1 Structure and function
1 Intelligent Management, but it can be implemented in a separate EMS or equal to H / W, the main functions of the EMS
Giving the effect is not.
2 structure of the H / W constituting the Intelligent Management system also, the other ( 他) Associated with the equipment also, the function of each H / W
And roles should be given to specifications.
SK Telecom
3 configuration of the S / W constituting the Intelligent Management System, Fig., Each S / W association between each S / W Block
It shall give the function and role of the Block.
4 Intelligent Management System shall be capable of performing the following functions.
a) information input function by the operator
b) gathering network information via EMS works with features
c) performing the algorithm according to the input / collecting the government and the operator-defined criteria function
Based on the d) performing the algorithm results in a changed network information and enforcement
The interworking function between nodes to accommodate e) Distributed, Centralized or Hybrid Architecture
f) interworking with our Planning, Optimization System
g) the other ( 他) Interworking with the manufacturer of Intelligent Management System
2.4.9.2 Operation algorithm
1 Intelligent Management is performing a Self Configuration / Self Optimization / Self Recovery function
An optimal algorithm should be designed.
2 details the algorithm for providing the respective functions and related information (Flow Chart, S / W Block association as well, the data flow diagram
Etc.) should be provided.
3 For we require multiple algorithms and each algorithm, the function must be additionally applied, which
The operator must be able to selectively apply.
2.4.9.3 Auto Configuration
1 Intelligent Management is defined in the 3GPP Release 15 and higher SON-based Self-Configuration
It should support all of the features.
2 Intelligent Management are predefined by the original operator of the building and when the system is reset gNB-CU
This can be set to be automatically set based on the information.
3 Intelligent Management is pre-defined by the operator during the initial deployment, and system reset gNB-DU
Based on the configuration information it should be able to automatically set by Plug & Play.
4 Intelligent Management shall support the Auto Configuration feature.
a) Dynamic Configuration of N2 / N3 interface
b) Dynamic Configuration of Xn interface
c) Dynamic Configuration of F1 interface
d) Automatic Neighbor Relation (ANR) function
SK Telecom
e) Automatic allocation PCI
5 Intelligent Management shall support the additional features Auto Configuration according to our needs.
2.4.9.4 Auto Optimization
1 Intelligent Management is defined in 3GPP Release 15 and higher SON-based Self-Optimization
It should support all of the features.
2 Auto Optimization feature is the Intelligent Management Operator Controlled (Open Loop) Operation
And it must be implemented by dividing the Autonomous (Closed Loop) Operation, and the interconversion be easy.
Close Loop
Input data Performance Performance

monitor Evaluation improved? Y
Parameter SON algorithm

Fall back execution
Optimized New
Parameter param
Deloyment ready
Manual
Intervention Open Loop
Figure 2.4.9.4-1: Closed / Open Loop Optimization Flow
3 Intelligent Management shall support the Auto Optimization feature.
a) Intra FA, Inter FA, Inter RAT gNB-DU / gNB-CU Load balancing between
b) RACH Optimization
c) Beam Optimization
d) Tx Power Optimization
e) Mobility Robustness Optimization
4 Intelligent Management must be able to quantify the current performance level of the system and, Optimization Features
Before / after recording the performance level achieved by the operator must be able to verify the improved performance also.
5 Intelligent Management shall support the additional features Auto Optimization according to our needs.
SK Telecom
2.4.9.5 Auto Recovery
1 Intelligent Management is a SON-based Self-Healing features defined in the 3GPP Release 15 and higher
Should all support.
2 Auto Recovery feature is the Intelligent Management Operator Controlled (Open Loop) Operation and
It is implemented by dividing the Autonomous (Closed Loop) and Operation and the interconversion be easy.
3 Intelligent Management shall support the Auto Healing features.
By a) Overload (Overload) Recovery of Cell / gNB-DU / gNB-CU disorders
b) recovery of a system failure due to S / W error
c) the system is reset by the above H / W
d) High Availability (HA in a virtual environment)
Failure prediction and notification via e) monitoring system
4 Intelligent Management shall support the additional features Auto Healing according to our needs.
5 Intelligent Management is based on the quality of service being provided during the Auto Healing Features
It should not impact.
2.4.9.6 Manufacturer-specific functions
One must present a specialized manufacturer of Intelligent Management features in addition to the proposed function.
2.4.10 Other Functions
No one shall support the MDT (Minimization Of Drive Test), Core, TCE Server by EMS Only
It shall operate.
2 PIM occurrence should support auto-Rx Path On / Off function.
3 TCP / IP Header TCP / IP Packet Header should support the RoHC Profile 6 functions for compression.
4. Considering the UL quality should support the handover.
a) DL quality (for example: RSRP, RSRQ), as well as supports the Inter / Intra handover considering Quality Fig UL
Should be able to set a handover triggering threshold for UL SINR): b) UL quality indicators (eg.
2.5 Interface Specification
All standard connection between Node shall comply with the Protocol and the attached specifications defined in 3GPP Release 15 and higher, 3GPP other
other ( 他) For standard it should reflect the most recent specifications:
SK Telecom
TDB
Charging TDB
AMF SMF PCF SMSF
N1
System
N2 N4
N3 N6
UE gNB UPF DN
Uu
Figure 2.5-1: 5G System Architecture
2.5.1 gNB inter-connected with the AMF standards
1 structure of the liver and gNB AMF N2 Interface is as shown in the figure below, the 3GPP TS38.410, TS38.411, TS38.412
NG-AP
SCTP
IP
Data link layer
Physical layer
Figure 2.5.1-1: N2 Interface
Up specifications for the two physical layer IEEE 802.3 / IEEE 802.12 and related to the Fast / Gigabit Ethernet connection
Third connection specification for the data link layer is to comply with the protocol specification defined in this specification 2.6.
4 Connection specifications for the IP layer must satisfy all of the IETF RFC2460 and IETF RFC791 for IPv6 and IPv4
do.
2.5.2 The connection between the UPF standard gNB
1 gNB structure of the liver and UPF N3 Interface is as shown in the figure below, the 3GPP TS38.410, TS38.411, TS38.414
SK Telecom
plane PDUs
GTP-U
UDP
IP
Data link layer User
Physical layer
Figure 2.5.2-1: N3 Interface
Third connection specification for the data link layer is to comply with the protocol specification defined in this document 2.6.
do.
Connection specifications for 5 UDP shall meet the IETF RFC768.
6 access rules for the GTP-U is to comply with the 3GPP TS29.281.
2.5.3 access standards and cross-gNB gNB
1 Structure of the liver and gNB gNB Xn Interface is as shown in the figure below, 3GPP TS38.420, TS38.421, TS38.422,
It shall meet the TS38.424.
plane PDUs
Xn-AP
GTP-U
SCTP UDP
IP IP
Data link layer Data link layer User
Physical layer Physical layer
Figure 2.5.3-1: Xn Interface C-Plane Figure 2.5.3-2: Xn Interface U-Plane
SK Telecom
Third connection specification for the data link layer is to comply with the protocol specification defined in this specification 3.6.
do.
Connection specifications for 5 UDP shall meet the IETF RFC768.
6 access rules for the GTP-U is to comply with the 3GPP TS29.281.
2.5.4 gNB-CU and the inter-connection standard gNB-DU
1 gNB-CU and DU-gNB between the structure of the Interface F1 is as shown below, to comply with the 3GPP TS38.470
do.
SDAP
PDCP
RLC
MAC
PHY-h RRC /
PHY-l
Figure 2.5.4-1: F1 Interface
2.5.5 Standard connection between eNB and gNB
1 gNB and eNB time NR-E-UTRA Dual Connectivity operation was as shown below Control Plane Interworking Architecture
It should support all of the Operation specified in 3GPP TS 37.340.
SK Telecom
S1
MeNB
RRC
X2-C
SgNB
Uu
NR RRC
UE
Uu
RRC
(MeNB
state)
Figure 2.5.5-1: gNB-eNB Interface C-Plane
2 NR-E-UTRA Dual Connectivity Operating User Plane Interworking Architecture between gNB and eNB is the same as the figure below,
All interlocked Option (Bearer MCG, SCG Bearer, Split Bearer MCG, SCG Split Bearer, etc.) to be specified in 3GPP TS 37.340 must
support.
MCG SCG
MCG SCG
Split Split
Bearer Bearer
Bearer Bearer
X2
MN PDCP MN PDCP SN PDCP SN PDCP
MN RLC MN RLC MN RLC SN RLC SN RLC SN RLC
MN MAC SN MAC
MN SN
Figure 2.5.5-2: gNB-eNB Interface U-Plane
X2 Interface for interworking with the eNB 3 is a restriction on the NR-E-UTRA Dual Connectivity operate with a third-party eNB
So it should satisfy the TS 36.423.
2.6 Radio Protocol
gNB follows the Radio Protocol for the Core 5G and UE and the access defined in the 3GPP TS38.300, the structure shown below.
UE gNB
SDAP SDAP
PDCP PDCP
RLC RLC
MAC MAC
PHY PHY
SK Telecom
Figure 2.6-1: User Plane Protocol Stack
UE gNB AMF
NAS NAS
RRC RRC
PDCP PDCP
RLC RLC
MAC MAC
PHY PHY
Figure 2.6-2: Control Plane Protocol Stack
2.6.1 Physical Layer Protocol
1 gNB, as all the Physical Layer Protocol The 3GPP TS38.2xx defined in the following Table below
Spec no. Title
TS38.201 Physical layer; General description
TS38.211 Physical channels and modulation
TS38.212 Multiplexing and channel coding
TS38.213 Physical layer procedures
TS38.214 Physical layer procedures for data
TS38.215 Physical layer measurements
2 100MHz Component Carrier Channel Bandwidth 95% or less based Effective Channel
Must provide Bandwidth (<95MHz) and detailed numerology parameter subcarrier spacing, etc. for this purpose shall meet the
TS38.211.
3 1ms Subframe in URLLC 0.5ms user plane latency slot unit for satisfaction, mini-slot units
It should support channels / signals / procedures.
4 to support QPSK, 16QAM, 64QAM, 256QAM or higher and must meet the TS38.213.
To 5 it shall support the Physical channel detailed procedures related functions.
a) Random access
b) Scheduling
c) Power control
d) HARQ
SK Telecom
6 3.5GHz band in the TDD DL Layer 16, must support UL MIMO or more operable than 16 Layer.
7 28GHz band TDD MIMO should support Layer 8 DL, UL Layer 8 or more operable in.
8 LTE Physical layer provides the functionality for Co-existence, Carrier Aggregation / Dual Connectivity Support
Should be.
9 supported Physical / Transport Channel structure and mapping should support cross TS38.212 based.
2.6.2 Layer 2 Protocol
1 gNB will be supported, as to all Physical Layer Protocol defined in the 3GPP TS38.3xx to Table
do.
Spec no. Title
TS38.300 Overall description; Stage-2
TS38.304 User Equipment (UE) procedures in idle mode
TS38.306 User Equipment (UE) radio access capabilities
TS38.321 Medium Access Control (MAC) protocol specification
TS38.322 Radio Link Control (RLC) protocol specification
TS38.323 Packet Data Convergence Protocol (PDCP) specification
2, should support Sublayer below for 3GPP NR Layer 2 structure support.
a) MAC Sublayer
b) RLC Sublayer
c) PDCP Sublayer
d) SDAP Sublayer
SK Telecom
QoS Flows
QoS flow QoS flow

SDAP
handling handling
Radio Bearers
ROHC ROHC ROHC ROHC
PDCP
Security Security Security Security
RLC Channels
Segm. Segm. Segm. Segm.

RLC ... ...
ARQ ARQ ARQ ARQ
Logical Channels
Scheduling / Priority Handling
MAC Multiplexing UE One Multiplexing UE n
HARQ HARQ
Transport Channels
Figure 2.6.2-1: Downlink Layer 2 Structure
QoS Flows
QoS flow
SDAP
handling
Radio Bearers
ROHC ROHC
PDCP
Security Security
Channels
Segm. Segm.
...
ARQ ARQ
RLC
Logical Channels RLC
Scheduling
MAC Multiplexing
HARQ
Transport Channels
Figure 2.6.2-2: Uplink Layer 2 Structure
Of 3 MAC layer it must support the following features.
SK Telecom
a) Mapping between logical channels and transport channels
b) Multiplexing / demultiplexing of MAC SDUs belonging to one or different logical channels into / from transport blocks
(TB) delivered to / from the physical layer on transport channels
c) Scheduling information reporting
d) Error correction through HARQ
e) Priority handling between UEs by means of dynamic scheduling
f) Priority handling between logical channels of one UE
g) Padding
4 to support the following functionality of the RLC layer, and should support both AM, UM, TM mode.
a) Transfer of upper layer PDUs, according to transmission modes AM, UM and TM
b) Sequence numbering independent of the one in PDCP
c) Error Correction through ARQ (only for AM data transfer)
d) Segmentation and resegmentation
e) Reassembly of SDU
f) RLC SDU discard (only for UM and AM data transfer)
g) RLC re-establishment
Of 5 PDCP layer User Plane shall support the following features.
a) Sequence Numbering
b) Header compression and decompression: ROHC only
c) Transfer of user data
d) Reordering and duplicate detection (if delivery in order to PDCP layers above is required)
e) PDCP PDU routing (in case of split bearers)
f) Retransmission of PDCP SDUs
g) Ciphering and deciphering
h) PDCP SDU discard
i) PDCP re-establishment and data recovery for RLC AM
j) Duplication of PDCP PDU in case of multi-connectivity and CA
SK Telecom
Of 6 PDCP layer Control Plane should support the following functionality.
a) Ciphering, deciphering and Integrity Protection
b) Transfer of control plane data
c) Duplication of PDCP PDU in case of multi-connectivity and CA.
7 control plane of the SDAP layer should support the following functionality.
a) Mapping between a QoS flow and a data radio bearer
b) Marking QoS flow ID in both DL and UL packets
2.6.3 Layer 3 Protocol
1 gNB should support the 3GPP TS38.331 RRC Protocol.
2 RRC to support and must support the RRC Details Function.
a) Broadcast of the system Information related to AS and NAS
b) Paging initiated by 5GC or NG-RAN
c) Establishment, maintenance and release of an RRC connection between the UE and NG-RAN including
d) Addition, modification and release of carrier aggregation
e) Addition, modification and release of Dual Connectivity in NR or between E-UTRA and NR.
f) Security functions including key management
g) Establishment, configuration, maintenance and release of Signalling Radio Bearers (SRBs) and Data Radio Bearers
(DRBs)
h) Mobility functions including
i) handover and context transfer
j) UE cell selection and reselection and control of cell selection and reselection
k) Inter-RAT mobility
l) QoS management functions
m) UE measurement reporting and control of the reporting
n) Detection of and recovery from radio link failure
o) NAS message transfer to / from NAS from / to UE.
SK Telecom
3 RRC UE states and must provide a detailed state transition functions.
a) RRC_IDLE
• Cell re-selection mobility
• Paging is initiated by CN
• Paging area is managed by CN
b) RRC_INACTIVE
• Cell re-selection mobility
• CN - NR RAN connection (both C / U-planes) has been established for UE
• The UE AS context is stored in at least one gNB and the UE
• Paging is initiated by NR RAN
• RAN-based notification area is managed by NR RAN
• NR RAN knows the RAN-based notification area which the UE belongs to
c) RRC_CONNECTED
• The UE has an NR RRC connection
• The UE has an AS context in NR
• NR RAN knows the cell which the UE belongs to
• Transfer of unicast data to / from the UE
• Network controlled mobility, ie handover within NR and to / from E-UTRAN
SK Telecom
NR
RRC_CONNECTED
RRC_INACTIVE
establishment / release NR
Connection
NR
RRC_IDLE
Figure 2.6.3-1: UE state and state transition in NR
2.7 RAN EMS
2.7.1 General Specifications
1 RAN-EMS should be developed to satisfy the requirements our operational requirements.
07/01/22 details are not described in the section follows the existing LTE EMS company level.
2.7.1.1 Management skills
1 shall present a manageable number gNB from EMS, the Upgrade to our capacity for future demand
It should be possible. Further, by default, receiving capacity per EMS is not to be less than 10,000Cell.
Two simultaneous connections shall present a number of available Client, to perform the basic functions of the plurality of simultaneous Client connections
There should be no performance degradation.
3 is a commercial relational DBMS should be supported for all the Data Storage and analysis.
2.7.1.2 System Specifications
1 CPU is to be provide a high-speed processing for processing basic functions and Client requests in real time.
2 weeks is sufficient storage capacity with EMS and other basic functions Application can work smoothly
SK Telecom
3 the disk storage medium is sufficient capacity in the EMS and other basic functions Application to seamlessly operate
a) statistics, alarms, and configuration information (PLD, XML, etc.) Backup should provide capacity that can be stored for a period of consultation with us.
4, the disk storage medium is a protective function to prevent Data loss and system down time by providing a function Mirroring
5 shall support an external storage device for archiving, and recovery of the main Data.
6 Seamless for a service to be supported for redundancy and the corresponding structure.
7 be provided for such as CPU, main memory, disk storage medium, an external storage device Minimum Specification
do.
2.7.2 RAN EMS General Features
The O & M Transport Layer Implementation specific feature set between the EMS 1 and NE (Network Element)
2 shall support the S / W and H / W shape information downloading functions requested by the NE.
3 operating parameters according to the request of the NE (Cell Setup, Common Channel, System Information Related Data, etc.)
It should support the downloading function.
4 it should support the S / W / parameter downloading functions according to the operator's requirements (MMC).
Redundancy for the purpose of 5 Seamless Service (Active-Standby structure) Standby loading on the support structural unit
It shall support the functions to be downloaded to the NE in the Background Without Impact on operations in service.
6 to be supported by S / W compression, compression parameters for rapid downloading support.
7 must be supported by each NE Firmware downloading functions.
When a problem occurs during eight downloading it should support Fallback feature wonbok to the previous Version.
9 NE Stars should support the downloading of history management.
It must support remote Reset function by 10 MMC.
11 Rectifiers shall support Firemware enforcement.
SK Telecom
The H / W-shaped information / operating parameters of the NE 1 in real time, stored in a relational DBMS commercial / administrative and thus for
Update changed to be in the case of commercial relational DBMS.
2 outputs and change of shape information to be gNodeB support (increase / gamseol) function.
3 gNodeB, it shall support the administrative functions that need to be managed in a Cell ID, etc. 5G.
4 Cell shape information output, and changes to be supported (increase / gamseol) function.
5 trunk should support output and add / delete function of the link shape information.
6 to be supported and the output changing function of the wireless channel information.
a) shall give a minimum of Step output changes (for example, can be changed by 0.5dB step)
b) There must be no delay when the output changes.
7 Sector / Cell Block Unit shall support functions.
8 shall be presented to the supported operating parameters, it should provide the setup and management of the parameters
do.
a) shall help support Hangul for a parameter.
Mounted on 9 NE must support the version check for all S / W.
10 to a maximum of three levels should support the "H / W implemented by NE also GUI" provided functions.
a) Level 1: Network Element Level
b) Level 2: Rack / Shelf levels
c) Level 3: Unit / Board-level (H / W unit), Level Virtualization Function
To meet the 11 configuration information in a standard form established by SKT should support the ability to Export.
It marks the 12 gNB people in Hangul and should support the ability to input.
NE 13 gNB each of the latitude, longitude, altitude automatically collect / manage and Data Antenna Beam Pattern Data
It must support the function.
a) by the operator latitude, longitude, altitude, Main Beam Azimuth (Swing angle) / Elevation (Tilting angle), and the history information input,
must support the management, including periodic reporting.
b) gNB-DU (including removable and-one), such as equipment containing Antenna automatically collecting / managing the latitude, longitude, altitude,
Main Beam Azimuth (azimuth) / Elevation (Tilting angle) Data and the EMS real-time the information must be a configuration management should be
included in the PLD.
SK Telecom
14 Main Beam Antenna Azimuth (Swing angle) of gNB-DU (including removable and integrated) by an operator of a request /
Elevation and (Tilting angle) must support the ability to change the S / W based on no Site visits via Remote Electrical Tilting /
Swing, it should be supported without additional H / W.
a) shall present a changeable and changing Range Minimum Step.
b) shall support the ability to automatically collect / manage Main Beam Azimuth (Swing angle) / Elevation Antenna Beam Pattern Data reflects
(Tilting angle) after the change by the operator requirements.
c) changes in the minimum possible without degradation Range Main Beam Azimuth (Swing angle) is ± 15 °, Elevation (Tilting angle)
should be less than ± 10 °, it should be given maximum support each change.
The Audit function for like 15 Parameter to be supported.
This chapter hour hours 16 EMS gNB accommodate changes should be minimal.
17 EMS is a proven PLD Tool that can be extracted by comparing the difference by date for the entire PLD gNB
2.7.2.3 Fault management
1 H / W fault if, S / W fault occurs must support the ability to detect in real time.
a) H / W failure: presenting detectable minimum time
b) S / W Breakdown: detect possible given the minimum time
c) virtualization fault Function: detect possible given the minimum time
2 to units shall support the ability to report the failure to the operator places.
a) H / W fault: replace present the smallest possible structural units
b) S / W Fail: report presents the smallest possible S / W Block Unit
c) Function Virtualization failure: report presenting the smallest possible unit Function
A step 6, based on the 3 ITU-T X.733 (Critical, Major, Minor, Warning, Indeterminate, Cleared) breakdown rates
The operator must provide and support the ability to specify the breakdown graded according to Alarm Code.
4 Depending on the cause of failure generates an Alarm Message and shall support the ability to generate a visible / audible alarm.
5 Pop Up Window such as the ability to turn off the audible alarm if the operator received the ACK through the (visible alarm
It should support the holding).
6 If the fault recovery generates an Alarm Message release and release and the ability to disable the visible / audible alarm
7 it should support the ability to display a fault occurrence time and fault recovery time.
SK Telecom
8 Alarm Code shall be supported by the Alarm Filtering feature.
The 9 Alarm History Data shall support the ability to save the commercial relational DBMS, the storage period
It should support the ability to support the implementation of the Fault Localization in 10 NE.
11 calculating the total managed NE and NE per individual statistics period based operator is specified, this table and
It shall support the features that can be displayed in graphic form, to be presented the details specified period of time.
a) Alarm Code stars failure NE / Block by such
b) fault occurrence time, recovery time, time to failure (fault recovery time - time generated)
12 If any trouble occurs, it should support the ability to provide help for the Hangul fault causes and corrective actions.
EMS 13 provides each of gNB NE (gNB-DU (including removable and integrated gNB-CU,), etc.) to remove the fault alarm code,
Unique Stars should have broken the alarm code.
EMS 14 is each NE of gNodeB (including gNB-CU, gNB-DU (separate and integral), and so on) interlocking equipment (5G Core, LTE Core,
An LTE eNB, etc.) failure when the alarm and interlock Fault message destination node information representation (IP Address, Node Name, etc.) should be
included.
Alarm functions and shall provide the following: 15.
It provides a) accounting period User Defined Alarm Function
b) PIM (Passive Inter-Modulation), Harmonic generation provided Alarm
c) gNB-CU and DU-gNB (removable and includes integrally) linked interval, quality and fault management for gNB-DU-DU-l-h and gNB interlocking section
It shall provide the rectifier 16 and the interlocking Alarm.
2.7.2.4 Performance management
1 EMS shall support the control and accounting functions for its own load.
Second management target periodically automatically collect performance-related Data of all the NE within the commercial relational
It should support the ability to save / manage the DBMS.
a) The operator has access to the DBMS statistics Data from the EMS should provide SQL Query Tool or the way, and be saved.
3 functions in constant time performance statistics for each item can be automatically collecting Data (5 minutes, 15 minutes, 1 hour) and gap
It should support the ability to gather the Data for a period of time by the operator's requirements. Performance statistics shall be possible
to make intuitive form such as XML, TEXT.
SK Telecom
4 to have the ability to collect and report performance and Data, Data collection is divided into gNB, Cell Unit
You should be able to.
a) Traffic service by performance-related Data
• Data call tinted / outgoing Related Data
• Data handover
• Paging Related Data (including Paging Discard)
• The Call Statistics Discard according to CAC
• Location Registration Data Related
• Data No. Throughput (DL / UL-specific, per Cell Per User) Related Data
• To be provided with Unique focus on a specific Trace request terminal (call attempt, access success rate, CD rates, transfer completion rates,
transfer rates, MAC, RLC, PHR, HARQ, R-BLER, CQI, RI, SINR, MCS, etc. RF and Scheduling information, Candidate UE per TTI, and so on)
b) Protocol Data related performance
• Support should be provided as possible Protocol Data related to performance, such as RRC, PDCP, RLC, MAC, N2 Interface, N3
Interface, Xn Interface.
c) Other Performance Data
• Data processing unit of the DSP (or ASIC) related performance Data (example: CPU load ratio, etc.)
• Processor CPU load and Overload Related Data
• RF Quality Related Data
• N2, N3 sent to the interface usage and error-related Data
• Throughput on Ethernet Traffic by Port (including M-Byte, Peak Throughput)
• RRE (RRC Re-Establishment) Related Data
• GTP Loss, Out of Sequence Related Data
• It shall provide the Debugging Tool or the way the RF Schedular sanity operator can determine the UE unit.
• Disaster-related statistics letters
• Others should be provided in a timely manner, the necessary statistics by company policy.
d) you should be able to perform a test gNB call origination / incoming tests using the specified resources by the operator's requirements.
SK Telecom
• Perform the test call results shall include all Protocol Message (including details), as a result of the Call Trace.
• Should be reported through the Call Trace Diagram A illustrates the Trace report and the results of Text-based, performance test results
call shall include Throughput information.
To 5 it shall support the ability to handle Statistics Data.
a) Performance Data (Data from / to communicate for a termination call rate / percent complete / Call Drop Rate / Throughout (service-specific) performance for
Data) based major PI (Performance Indicator) for periodically calculating, graph and table, the operator ability to report in the form
b) the feature that the operator can input an item and a calculation formula for calculating PI
c) function that generates Alarm If the operator is greater than or below a set Threshold for any of the PI value
d) the ability to display the Busy Hour, for at least 31 days, and PI-based performance Data in graph and table form
e) the ability to display the performance Data and PI classified time of at least seven days in a graph and table form
f) the ability to show the 5-minute and 15 minutes and PI Performance Data for at least 6 hours in a graph and table form
6 shall be given the support available Call Fail Reason (see examples below implements request)
a) Cause offered for all calls with Call Fail
• Cause includes providing for the call and the user reached the limit number of shut down by the user of the origination
b) Call Fail Reason implementation causes occurs, shall provide the actions taken by the EMS as Hangul, the operator needs to be edited.
c) all failed calls (traffic lights, INCOMPLETE, CD No.) must be broken down into statistical call type.
d) any failure Call (non communication, INCOMPLETE, CD No.) must be real-time analysis and output to a call type.
e) fails to be output with the gNodeB resource allocation for the call history (including the structural unit ID # / # Modem Information)
g) In addition to failed calls should be output to allow real-time statistics broken down and analyzed the call is poor Throughput occurred does
not meet the standards we set.
h) shall provide a mean value for all other Peak Performance Data.
• Example: N2, 5 minutes during service Buffer usage, Congestion / Flow Control occurrence history statistics on the N3 Interface, 15 minutes, within one mean
value provided outside the period of the statistical time providing also Peak Value
SK Telecom
i) Call Release Reason (CRR), CSL (Call Summary Log) service and CRR & statistics provided, etc. Mapping Table, CRR & N2 Cause
Mapping Table
7 Fail Call Log is to be provided in one-minute increments.
8 (Minimization of Drive Test) MDT provides related features.
a) Cell-specific and provides the On / Off function and Schedulging function.
b) The MDT Log in EMS should be saved in XML Format, which is presented to us, or a specific folder.
c) The EMS should be no restrictions on the use MDT.
2.7.2.6 Security and Account Management
1 shall provide support user ratings and rating adjustments.
2 shall support the command and provided grade rating adjustments.
3 shall support the currently connected Client Information Display.
4 limited number of connections Client, shall support the connection force release function.
5 it must support the same user ID login control and alarm functions.
6, should support the operator ID add / delete function.
7 shall support operator specific ID password change function.
8, an operator must support the Profile Information Output and change function (including the operator rating) function.
9 should follow the guide complements required by our security department.
1 to check the connection and operational status of the managed NE "network configuration diagram in the form of GUI" to be supported.
Second operational state of the processor / building blocks of gNB (Equipment, Block, Activity, and so on) and the failure state "NE-specific H / W
Mounting is also reflected in the GUI "should be supported by features that the operator can immediately identify the status of each NE part.
A processor / building blocks of gNB usage by a third operator demand (Usage) and to output the state Overload
The ability to be supported.
4 shall support the status output function gNB.
a) Main Service Processor and the status of all the structural units (Normal / Fail / Block)
b) If the Main Processor supports dual display Active state of the structural unit
c) Logical Resource Display Function
SK Telecom
d) Service status (Normal / Fail / Block) of the common channel-based Cell
e) RF Path by each VSWR
Ongoing of 5 Cell Unit should support the real-time output function of the service is by call.
6 RAN EMS is integrated with the state of the NE ~ RAN EMS, NE ~ NE between Interface (N2, N3, and so on) all Interface
It supports the GUI and should be able to manage and control.
7 Cell shall be provided by the RF monitoring function, periodic monitoring is the operator must be set.
a) function of outputting the TX, RX RF state to Snapshot Cell type-specific
b) the operator-specific settings Threshold Cell function for generating Alarm
8 gNB-CU, gNB-DU, gNB-DU-h, gNB-DU-l to verify in real time the respective power consumption and consumption current
Shall provide the function, the operator shall facilitate the implementation, statistical convenience features that allow you to monitor / analyze real-time and
period.
2.7.2.7 Log function
One must support the ability to save the results and all Command, operator ID, runtime information about it.
2.7.2.8 Operator Interface Function
It should support 1 Interface functions.
Command execution function according to a) the menu selection system
b) Multi Window support
2 shall support the CLI feature.
a) shall show the supported CLI (Command Line Interface).
b) Command Command input and the execution result output when the operator ID, runtime information display function
c) CLI command execution and the result confirmed that should be available.
d) performing CLI commands via Telnet (or SSH) connected to the EMS, and the results confirmed this to be possible.
3 shall support a wide range of Report File Format.
a) shall give assistance available Report File Format (excel, xml, etc.)
4 and comply with our standards for MMI command of the GUI and the CLI, menu-driven format, support for those cases
It shall be presented to availability and support plan.
a) 3.4.2.7 4 wherein the operator of the matching function, subject to the 5.
SK Telecom
2.7.2.9 Operator support
1 All features and operational support should be provided to operators as a GUI-based, this should not affect the ongoing services
do.
It should support the two shape information, operational parameters Audit function.
a) in the case of Data Data stored on the NE and EMS do not match, report the results to the operator and should provide a set of
features to complement it modify /.
b) the operator must be performed in real time or period defined in advance.
3 to be adjacent supports Cell Information Audit function.
Case a) that are not adjacent to match Adjacent (Neighbor) Cell List information between the Cell, the report results to the operator and should
provide a set of functions for automatic correction / compensate.
b) Neighbor Cell List information should be possible to remove them in bulk in a short time.
c) it should be between gNodeB Neighbor Cell List information received in different EMS match in both directions.
4 shall support the Remote Access feature.
a) connected to the main processor of the NE through a Telnet or the like, should be able to perform a function, such as remote Debugging.
5 Batch Job function should support the function.
a) it shall be collectively performed at the time specified by the operator MMI Command Script created.
b) MMI Command Script will be able to include a plurality of Command for multiple NE and, Batch Job execution time should be
minimized.
6, it should support the ability to change the automatic acceptance.
a) gNodeB should be automatically set to the configuration and operating parameters, Neighbor List information of the target gNodeB When doing a
receiving change.
7 it should support the UI and Telnet (or SSH) based Call Trace feature.
a) Call Trace capable UE shall specifically suggested as the number and Trace method (least 100UE)
b) UE shall be registered to the IMSI or TMSI. (IMSI is to be provided to accommodate the method proposed by us.)
c) Call Trace register, delete, change, confirm information are to be available via a connection UI and Telnet (or SSH), it shall be stored in the
Trace Results Text form the EMS specific folder.
d) Details of heading Logging Trace targets should include all of the Protocol Message.
SK Telecom
e) Trace results should be reported through the Call Trace Trace Diagram a schematic view showing a report with the results of Text-based.
f) Trace results shall include the RRC, PDCP, RLC, MAC Protocol and at least one second Throughput, RF (RSRP, SINR, CQI, RI, etc.),
AMC, Power Control, Scheduling information.
If g) which is stored in the form of Binary To provide a real-time conversion Tool as Text.
8 normal / abnormal shutdown call must support the storage / analysis.
a) storing details of all call terminates abnormally, and must be able to analyze it, and the analysis information, to be able to
see the end caused by abnormal statistics to eNB and Cell unit in table and graph form.
9 it should support the handover analysis.
a) analyze the frequency of the handover between the handover Cell Source and Target Cell-based handover statistics should be able
to see the priority of Adjacent (Neighbor) Cell form of a table and graph form.
b) it should be one, if the call is associated with the handover of two or more times, each handover analysis.
10 it should support the system configuration and unit testing / diagnostics.
a) the operator is carried out if it requires a complete system or its own system, the constituent unit test / diagnose the operator-specified and analyze
results to include a H / W and S / W, functional testing / diagnosis and be reported.
It shall support the test feature 11 transmissions.
a) be provided with the ability to test and diagnose for the transmission by operators of the requirements, the test results should be
reported.
Between 12 gNB Node (gNB-C ~ gNB-DU (including removable and integral), gNB-DU-h ~ gNB-DU-l) the Interface function test
a) shall be given the ability to test and diagnose for inter-Node Interface Link by the operator's requirements, the test
results should be reported.
b) shall be able to check the quality of the inter-Interface Link Node.
13 Other Functions
a) When applying Package must present a plan to minimize the time and it Out of Service
b) it shall be available between versions Package gNB accommodate change.
c) when operational tasks such as change and configuration change receiving presents Out of Service and time should be given to ways to
minimize it.
d) EMS should be able to add the gNB Port Status communication device and configuration management.
SK Telecom
2.7.2.10 Inventory management
1 NE should be supported by the Serial Number auto management and reporting capabilities for all components, to assets
It shall include the entry.
a) Serial Number, Manufacturer Name reporting on the items of the Company and hyab
b) Backhaul, Fronthaul between the SFP, such as Node Information (Company and agreed items)
The quantity management and reporting capabilities for all components 2 stars NE should be supported.
3 history for all of the components of the NE management and reporting capabilities (manufacturing date, installation date, service date / history, etc.)
a) shall report to include information under the mounting information of the new facility and dismantling hours, the device Activation / Deactivation via
EMS.
• Identifiers of all the components constituting the equipment (Serial Number)
• Components are collectively referred to a physical H / W containing equipment, H / W Configuration Unit, SFP, etc.
b) it shall provide an alarm that includes the following information about the device mounting information changes.
• Mounting equipment Change Type: H / W configuration unit mounting / hernia, SFP Team / hernia, or other mounting / hernia components
• Equipment identifier, date and time change Event occurs, changes occur Event Slot / Port information, change Event occurrence H / W
Configuration Unit / SFP / identifier of the other component
c) it must provide an alarm containing the following information about the connection information to change a physical Port level.
• gNB-C, gNB-DU (including removable and integral), gNB-DU-h, gNB-DU-l Each Port and Cell connection relationship
• Change Event generation date and time, changes occurred Event occurs Slot / Port information, change Event gNB-C, gNBDU (including removable
and integral), the identifier of the gNBDU-h, gNBDU-l, Cell
d) it should provide an alarm that includes the following information about logical connection information changes.
• gNB-C, gNB-DU (including removable and integral), gNB-DU-h, gNB-DU-l and Cell connection relationship
• Change Event generation date and time, changes occurred Event occurs Slot / Port information, change Event gNB-C, gNBDU (including removable
and integral), the identifier of the gNBDU-h, gNBDU-l, Cell
e) be able to identify the equipment and components, physical implementation occurred Port Information / Change connection information provided by the alarm.
f) you should be able to check the mounted equipment information and connection information aperiodically through if it can not mount / Connection information
change alarm service, MMI command.
SK Telecom
2.7.2.11 NBI (North Bound Interface) support
One must be able to be connected through the NMS Tool and NBI as required by the company.
2.7.3 OSS interworking function
2.7.3.1 OSS interlocking Overview
Our OSS (TANGO, hereinafter OSS) is a next-generation management platform for efficient and systematic support to the Network Management business.
OSS is Access-Transport-Core Eng.- building area - accommodates business operations integrate key features of the existing Tool to gradually concerning the pursuit of
intelligence / automation of operation through the Network Big data analysis, and analysis of various environmental and community to provide support so that you can
perform on a single platform for End-to-End services to data-based.
Figure 2.7.3.1-1 OSS Platform
Our OSS is organized into six parts as follows:
- TANGO-EC Eng. & Con. : Transmission network engineering - building support services
- TANGO-O Operation Mgmt. : Access- -Core transmission network operation collection - Monitoring / Analysis - Task Management
- TANGO-I Inventory Mgmt. : Network Resource (National History - Equipment - Port-line) shape / configuration management
- TANGO-A Advanced Analytics: Access / Core Networks advanced real-time Big Data analytics platform
- TANGO-D Datawarehouse: DW-Mart-BI service delivery platform
- TANGO-PF PlatForm: open-source development TANGO - Exams - Environmental Management and Common Services
SK Telecom
Figure 2.7.3.1-2 OSS architecture
2.7.3.2 It provides features FM / PM / CM Information
2.7.3.2.1 General Information
1 EMS (Element Mgmt. System) network management information stored or generated in the EMS (fault, performance, structure, shape,
For Call Fail information and the like) is transmitted to the EMS mutually engaged position and the OSS (Operations Support System), and must provide the Notification
information to the transmission is complete.
Data passed to 2 OSS is to be stored for more than seven days within EMS.
3 EMS shall manage the environmental information required by OSS and linked to the Configuration File form of OSS
At the request of the operation should be reflected in real-time changes and OSS works.
4 After the auto repair and need to restore the connection when connected to the connection with the OSS disconnected unsent data
For loss-free transfer and complete transfer shall ensure that the information provided Notification.
5 EMS and cooperative manner between the OSS account is used by default SSH (SFTP) and connect to the EMS and OSS
Passwords and access SSH Key provides information such as server IP OSS is connected before starting the works. It should also be provided to the
IP, account, OSS OSS is a password prior to connecting to the EMS.
Depending on the network conditions between national history and OSS that 6 EMS Installation If you are unable to use SSH, Telnet, and
You should be able to use the FTP.
The data provided by the EMS 7 a description of the data to be used in our OSS, data structures,
Data generated should be provided, including Rule, Parsing room.
2.7.3.2.2 FM (Fault Management)
1 EMS generates two types of files (RAW Data files, file NOTI) the OSS and mutually engaged position,
Maintained and shall provide the failure information according to the order of occurrence in real time.
SK Telecom
After the session disconnection between 2 OSS unsent data will not be lost upon recovery in accordance with the separate data recovery process definition
It shall ensure the transfer, even if this should not affect the real-time network management and OSS information sent to the management of the EMS.
If you disconnect a session time between 3 OSS is at least a certain period of time (Default = 1 hour), after the connection is restored within one hour earlier
Fault messages generated so that OSS can take to Get from EMS as EMS Bulk EMS is my path is managed by Configuration
files should create a file in the path.
2.7.3.2.3 (Performance Management) PM
1 EMS is time to OSS and the mutual commitments location-specific equipment, transmission of statistical metrics for each file, and each file transfer
The resulting information should be provided through the NOTI file.
2:00 SFTP (or FTP) as a cause of failure statistics file transfer fails, and record the results failed to NOTI files,
Through such retransmission shall ensure that transmission without loss.
Statistics 3 files should support the operator in CSV or XML format is easy to read.
4 If a header that provides the metrics specific field information in the first line of the accounting file if the CSV file, XML file
It should provide a DTD file with statistics.
After 5 OSS and disconnected sessions unsent data will not be lost upon recovery in accordance with the separate data recovery process definition
It shall ensure the transfer, even if this should not affect the normal network management and OSS information sent to the management of the EMS.
2.7.3.2.4 (Configuration Management) CM
1 EMS is a configuration file to the OSS unit in relation with a mutual commitment to align with the position prior appointment
Transport and shall provide information through the transmission result NOTI file.
2:00 SFTP (or FTP) failure caused by transfer failure, such as configuration information and writes the result in the failure NOTI file,
Through such retransmission shall ensure that transmission without loss.
3. If the configuration information collected from network equipment or EMS causes of failure such as EMS, calendar period (Default =
I shall try to re-collected by 10 minutes) at regular times (Default = 3 times), and shall record the results of OSS within NOTI file for the
results of attempts to re-collect.
Based on the time and number of retries for four recollections of attempts by management to operate within the EMS Configuration File
This change is based on requests by the OSS should be immediately reflected in the operation.
5, configuration information, and the operator must support the CSV or XML format is easy to read, in the case of CSV files File
If the first line is a header that provides the parameter name information, XML files, must be provided with a DTD file.
If you have already sent to the session disconnection occurred between 6 OSS recovery after the session immediately transmit unsent data, without loss
It shall ensure the transmission of data.
SK Telecom
2.7.3.3 Inventory provides information function
2.7.3.3.1 Provide information
For all equipment and components proposed to construct a 1 5G network must provide the following information, change information
And, if necessary, an additional impact of OSS should also be given the changes planned in advance for understanding.
a) catalog information for all equipment and components for delivery from the proposer shall be provided in accordance with the form defined by the Company
Hardware models.
b) if the equipment and components to be added later deliveries occur catalog information for all equipment and components must be provided in accordance with
the form defined by the Company Hardware models.
c) If possible mount additional components Models of the equipment has changed the catalog information must be provided in accordance with the form, we have
defined.
d) If the Package version upgrade information, etc. Inventory, Descriptor information, connection information change to the structure (schema) occurs due to the
proposed changes should be planned in advance, it should be changed in consultation with us.
e) Inventory information, and Descriptor information defined by the field of the connection information, the type of the value, which should be provided with a range of
values.
2.7.3.3.2 General Information
1 EMS is reporting / response for all Hardware, Components and Software to change the configuration of your equipment
a) All Inventory information should be immediately available from EMS or equipment depending on the quality of OSS. However, Inventory information of the virtual
machine is in a question and answer of the OSS EMS / equipment can be via MANO in consultation when necessary.
b) EMS should be able to provide a full list of equipment that they manage.
c) entry corresponding to the change of the Inventory Information details, even if the quality of OSS should be provided as soon as OSS. However, in the case
of a virtual machine EMS or change of equipment can be provided via the MANO reported to OSS.
According to d) Package version, for example, when the Inventory information structure (schema) of different, must be provided separately for each version.
2.7.3.3.3 Inventory provides information on non-virtualized devices
1 non-virtualized devices will collectively refer to a device on the equipment, and a general-purpose server using only Hardware.
2 Hardware components of the non-virtualized equipment should be immediately available in EMS according to the quality of OSS,
It includes the following topics: Components are mounted on the card slot is referred to throughout: Module (SFP example) to be mounted on (for example, a blade
server, a channel card, a power supply card) and port. Mapping of Slot / Port Names and physical shape of the device
SK Telecom
It shall be provided for each model. (Eg name from the left side of the slot located on the rear panel of the equipment two third port from the left of the name
of the second slot, the card front panel RJ45 port)
a) Name of device, serial number, make and model equipment that is uniquely managed in the EMS ID
b) the name of the mounted components within the device (or ID), serial number, make and model
c) The equipment and components are compliant with the slots and ports
d) The maximum network throughput (Mbps) ports of the equipment and components which
e) the equipment is the total number of slots and ports total with, components having the total number of ports
f) is uniquely managed in the equipment, a name of an individual slot and port to identify the equipment location (or ID)
g) position within the component mounting devices (slot and port name)
h) CPU architecture type, CPU model number CPU Core, CPU Clock Rate (MHz)
i) memory, the memory model, memory Clock Rate
j) the disk type, the disk size (MB)
k) Firmware Version
3 Hardware virtualization is not a component of the equipment shall be immediately available on the EMS according to the quality of OSS,
It includes the following topics: Components are mounted on the card slot is referred to throughout: Module (SFP example) to be mounted on (for example, a blade
server, a channel card, a power supply card) and port. Operational status information should be provided is divided by the value of the setting, fault information and
quality of equipment and components. (For example, is mounted, but if it is in use by setting and so on)
a) changing operational status of equipment and components
b) Equipment and components, with individual slots and operational status of the port (Up, Down) to change and change has occurred slot / port name, the
date and time change occurs
c) components within the equipment status changes (new mount, then mounting hernia, hernia) and implementation / Slot Name hernia happened, mounting /
hernia happened component name, the date and time change occurs
d) changing the port-specific cabling state (cabling, separate) and connect / disconnect the port takes place name, connect / disconnect the components takes place
name, a date and time change occurs,
4 Software components of the non-virtualized equipment should be immediately available in EMS according to the quality of OSS,
It includes the following topics: Package Software is commercially available and Software: includes both (such as OS, DBMS, Web, WAS).
a) All equipment installed on the Software List
b) the type of individual Software (eg: OS, DBMS, Web, WAS), name, version, manufacturer, warranty expiration
SK Telecom
5 non-virtualized Software Components change of equipment shall be immediately available at the point of the change EMS,
It includes the following topics: Package Software is commercially available and Software: includes both (such as OS, DBMS, Web, WAS).
a) changing the Software on the list of installed equipment (new installation, removal), and date and time change
b) changes in the Software installed on the device (eg version upgrades), and temporary changes
2.7.3.3.4 Inventory provides information on the virtual machines
1 Physical Hardware components of the virtual machine immediately from the equipment or EMS, depending on the quality of OSS
It should be provided. Hardware items are provided and include all of the components of the item 2.7.3.3.3 are not virtual machines, further includes
the following topics:
a) the name and ID of the system for managing physical Hardware (VIM)
Whether or b) use CPU Pinning
c) DPDK and whether to enable or disable
d) whether the memory NUMA support, and whether
e) whether the disc supports RDMA and whether
2 Hardware virtualization physical component changes to the equipment should be immediately available in EMS equipment or to change time
do. Hardware items are provided and include all of the components of the change item 2.7.3.3.3 non-virtualized devices, further includes the following
topics:
Changing a) the name and ID of the system for managing physical Hardware (VIM)
Whether or b) use CPU Pinning
c) whether use DPDK
Whether d) use NUMA memory
e) whether use RDMA disk
3 the physical Hardware Software components of the virtual machine is in the equipment and the EMS according to the quality of the OSS
It should be provided immediately. Offerings include all of the Software Components Item 2.7.3.3.3 of non-virtualized devices.
4. Physical Hardware award Software components of the virtual machine changes immediately from the equipment and EMS to change the time
It should be provided. Offerings include all of the Software Components Change item 2.7.3.3.3 of the non-virtualized devices.
5 Virtualization virtual resources component of the equipment shall be immediately available through the MANO depending on the quality of OSS,
It includes the following topics: And the name and ID of the virtual resources in the OSS and physical Hardware MANO
SK Telecom
To be the only possible identification. It should be possible virtual resource name given by the OSS and MANO for this purpose.
a) virtualization type (Baremetal, Hypervisor, Container)
b) Virtualization Software type (eg: KVM, Docker), version, manufacturer,
c) Virtual Resource Type (Compute, Storage, Network), a virtual resource name and ID
d) the virtual resource is a physical Hardware name and ID of the assigned
e) the mapping of physical ports and virtual ports Hardware resources
f) the list of ports of the virtual resources, the name of the individual ports and ID
g) whether the CPU architecture-type, CPU model name, CPU Core number, CPU Clock Rate (MHz), CPU Oversubscription ratio (vCore /
pCore), DPDK whether, CPU Pinning
h) memory, the memory model, memory Clock Rate, memory Oversubscription ratio (vMem / pMem), NUMA Support Status
i) disk type, disk size in megabytes (MB)
j) the name and ID of the system for managing virtual resources (VIM)
Six virtualization virtual resource components change of equipment shall be immediately available through the MANO to change the time,
It includes the following topics:
a) changing operation states of the virtual resource (e.g., create, change, and termination) and changes the resource ID
b) Virtualization Software changes (eg version upgrades)
c) Virtual Hardware resources and physical mapping changes, the changed resource and physical Hardware name and ID of the
d) changes in the list of ports, virtual resources, has changed the name of the port and ID
e) remap the port and the physical port on the virtual Hardware resources, the modified virtual / physical port name, and ID of
f) CPU, memory, disk information changes in virtual resource
g) the name and ID of the system for managing virtual resources (VIM) Change
7 virtual resources on the Software Components of the virtual machine immediately via MANO depending on the quality of OSS
It must be provided, including the following topics: Software is VNF / VNFC Package and Commercial Software: includes both (such as OS,
DBMS, Web, WAS). Name and ID of VNF and VNFC instance will be the value that can uniquely identify from the OSS and MANO. It must
Available Software Instance name given by the OSS and MANO for this purpose.
a) the name of the virtual resource lists and individual resources used by the virtual machine and ID
b) All Software list to configure the virtual machine
SK Telecom
c) Type of Sale Software (eg: VNF, VNFC, OS, DBMS, Web, WAS), name, version, manufacturer, warranty expiration
d) Name of VNF / VNFC instance, ID, version, manufacturer, Descriptor ID, Flavor ID, INS Level
e) capacity, and capacity criteria (such as the VNF / VNFC instance: the number of subscribers receiving 5M, Throughput 10 Gbps)
f) VNF / VNFC instance type of the CP within the list, an individual CP (Internal, External, Service Access), name, ID, IP address, Subnet information, allocated
bandwidth value (Mbps)
g) map of VNF / VNFC instance within the CP and the virtual resources the virtual port
h) the name and ID of the system for managing VNF / VNFC instance (VNFM)
8 virtual resources on the Software Components of change virtual machine immediately via the change point MANO
It must be provided, including the following topics: Software is VNF / VNFC Package and Commercial Software: includes both (such as OS,
DBMS, Web, WAS).
a) Name of the resource changes and changes in virtual resource list used by a virtual machine and ID
b) changes in the list of Software for configuring a virtual machine and to change information of each instance Software
c) Change Lifecycle condition of VNF / VNFC instance (e.g., create, change, and termination), and an instance ID has changed
d) Change Descriptor ID of VNF / VNFC instance and change ID Flavor
e) changing the capacity and capacity criteria of VNF / VNFC instance
f) VNF / VNFC instances in the CP list changes (e.g., create, delete), the individual information is changed and modified CP CP ID
g) VNF / VNFC instance within the CP and the virtual resource remap the virtual port, port ID and virtual modified CP
h) VNF / VNFC name and ID of the system for managing instance (VNFM) Change
2.7.3.3.5 Descriptor provides information function
1 MANO is a report / responses to all components and changes in non-materialized virtual machine details
It should be provided. Reporting and response must be provided in accordance with ETSI NFV IFA011, IFA014 standards, and includes the following topics:
a) Descriptor name, ID, version
b) by Flavour Descriptor name, ID, capacity and capacity criteria
c) Software image size, the disk format for the OS, Software image installation used, the minimum size of the disk for installation, at least a
memory size for installation, virtualization for installation
SK Telecom
2.7.3.4 It provides connection information Function
EMS 1 is connected to all sections of the information for all devices, including the devices that make up the 5G 5G RAN RAN
It shall provide for the reporting / response. All the equipment ID and the port ID used in the connection information is provided
2.7.3.3 ID must be provided through the Inventory section provides information function.
a) The items that make up the 5G RAN comprises all of the equipment according to the shape presented in the proposer 2.1.
b) the connection information constituting the 5G RAN connection section comprises all the proposer presented in 2.5.
c) OSS can query the connection between both connections of the internal gear and equipment.
d) all the connection information should be immediately available from EMS or equipment depending on the quality of OSS. However, the connection information of
the virtual machine has the quality of OSS and EMS responds to via MANO in consultation when necessary.
e) any changes to the connection information details, even if the quality of OSS should be provided as soon as OSS. However, if the virtual machine has
changed the EMS report it can be provided via the MANO with OSS.
f) connection information, by default, to be provided with {A-side equipment ID, A-side port ID, Z side equipment ID, the port ID} Z form.
g) If the connection information structure (schema) due to a different Package version, should be provided separately for each version.
Figure 2.7.3.4-1: Connection Information configurations
2.7.3.4.1 It provides the physical connection between the devices information
1 between the physical equipment connection information must be provided immediately by the EMS according to the query, and any change in the OSS,
It includes the following topics: A physical connection of the information-side / Z side port will be available physical port identification on the equipment Hardware. If 5G
RAN device and the other provided a difficult connection information for the equipment to-access period,
It shall provide 5G RAN-side information equipment, such as line information provided in transmission equipment of interworking 2.1.3.1.
a) a list of the RAN device 5G and the reference port Cell
b) connection for all connections between sections 5G RAN equipment information
c) connection for all connections between sections 5G RAN equipment with other equipment information
d) if 5G RAN device and the other provided a difficult connection information of the equipment between the access period, 5G RAN equipment-side connection
information (device ID, serial number, port ID, IP address)
SK Telecom
e) acceptance of the changed information 5G RAN equipment
f) the protocol of the individual connection information (for example: Ethernet, CPRI), the main / spare whether
※ The equipment and the list of ports of the Cell reference is a list of the devices and ports to service a particular Cell
(Example: ECI 26031 times the port 2 and port 3 of DU # 21 of CU # 01 is used to service the Cell)
※ 5G RAN equipment with other equipment connected to the LTE RAN equipment, repeaters, transmission equipment, IP equipment, Core Equipment
Collectively all
2.7.3.4.2 Equipment provided within the physical connection information
1. Equipment within the physical connection information must be provided immediately via EMS depending on the query and change the generation of OSS,
It includes the following topics: A physical connection of the information-side / Z side port will be available physical port identification on the equipment Hardware.
a) the connection between the same Blade Enclosure my server information
2.7.3.4.3 Provide logical connection information
One logical connection of the device information must be provided immediately via EMS depending on the query and change the generation of OSS,
It includes the following topics: A side / Z-side port of the connection information shall be identifiable on the virtual port CP or VNF / VNFC on the
virtual resources.
a) mapping between the Virtual Link ID, CP ID, Virtual Link and CP
b) whether the application of the protocol, high speed technology individual connections, high speed technology type (example: DPDK, PCI-Passthrough, SRIOV)
technology provides high-speed and resource ID
※ Virtual Link information includes all the equipment connections within and connection information between devices
※ Virtual Link ID and Network Service ID must be a value that uniquely identifies at MANO and OSS should
2.7.3.4.4 Services Connection Information
One service connection information must be provided immediately via EMS depending on the query and change the generation of OSS, under
It includes an item. All services connected to the information should be provided by a combination of physical / logical connection information, equipment information and
equipment. Inventory information, Descriptor information, connection information, refer to the equipment 2.7.3.3, 2.7.3.4.
a) it is not substantiated information and services connected to the instantiation of the service connection information
b) NS instance name and ID, NS Descriptor ID, NS Flavour
c) Network Slice information (for example: Slice configuration, SLA basis)
d) Service Function Chain Information
e) VNF Forwarding Graph Information
SK Telecom
f) the individual service connection status Lifecycle
2.7.3.5 SON control
1. One or network configuration and network management via a plurality of Network Management System
It should be possible to query and control parameter.
2. All queries and control commands should support both CLI, Script behavior.
3 so that a large number of queries and control commands can be processed in a number of gNodeB should provide a high-speed processing capabilities.
If you have not given your 4 2.7.3.5 In accordance with our existing OSS level.
a) viewed in the operating parameter through the CLI / control command is a single or a plurality of parameter should be viewed / controlled
via a single command.
b) a query / control command execution result, and by the Remote CLI to be report to the Network Management System.
c) after performing query / control commands via the Remote CLI result report should include the operator ID, the run time, and end time.
Query / control command written in d) Remote CLI and Script shall be batch at a given time.
e) Views of the operational parameter via the Script / Command control is not a limited number of commands must be done through one of the script.
f) viewed through the Script / control the contents of the entire success, and last-minute changes to the Script parameter when performing a Network
Management System report should be done, and this time, should be included in the elapsed time for script execution time.
g) To provide a high-speed processing capabilities to minimize the number of query / control command execution time by the Script.
It must provide h) Network Management System-specific query / command, control and traceability functions
i) remotely through one or a plurality of Network Management system shall be the H / W control.
j) and the information on the number of stages, and the success and the final change parameter for a plurality of control commands to be report to the
Network Management System, to be provided immediately in real-time report that this command is run.
k) if it is determined as an error with respect to the control command via the Remote CLI and Script as soon as errors are detected in real time with respect to the
error information to be report to the Network Management System.
l) should be a report on the cause of failure upon failure to perform the Remote CLI and Script command.
m) should minimize the effects on parameter changes during service by a control command.
n) shall be no effect on the command when performing services for RF output control.
SK Telecom
2.7.3.6 Call Log feature provides real-time
1. The base station must generate to Network Analytics, Call Log between the base station and all the terminals in real time.
a) Call Log should contain at such terminal ID and the Node ID, and network time, should include information for identifying the connection release process with
the call number.
b) Call Log shall include information for identifying the distance and the uplink / downlink radio quality information of the BS and the MS.
c) Call Log shall contain specific QCI Traffic transmission information of the base station and the terminal.
d) Call Log shall include a handover (HO) and the HO-related information History information for performance analysis Mobility of UE.
e) Call Log is to include information that distinguishes an abnormal number and Jeong Sangho, and shall include the information to know the cause of abnormality when
the arc.
f) Call Log shall contain information identifying the Signalling Latency process, such as the UE RRC, RRE, a handover. (For example, the time
taken to complete RRE occurs, the time, and the actual time the Traffic does not transmit required for HO)
g) Call Log shall contain the information to know the state of each UE is assigned Traffic. (Example: Modulation, MCS, etc.)
2. The base station for Network Analytics, shall create a Real-time Performance Monitoring (RPM) Log indicating the real-time status
of the base station.
a) RPM Log shall contain information to know the congestion of such attempts can Rach, can attempt RRC, ERAB attempts, can dongjeopja, HO
can occur, the resource allocation.
b) RPM Log should include the major KPI information to know the Call Fail occurs.
c) RPM Log shall contain information to know the up / downlink radio channel condition. (Example: Uplink RSSi, Noise Uplink, Downlink
Measurement Report, etc.)
d) RPM Log shall contain information unknown Traffic assignments. (Example: Modulation, MCS, etc.)
e) RPM Log shall contain information to know the status information of the base station. (Example: CPU usage, etc.)
2.7.3.7 OSS interlocking interface features
1 EMS shall provide the information required by 2.7.2.2 ~ 2.7.2.7 with our OSS, for it
It shall provide an interface in the manner specified by the Company.
2.7.3.7.1 FM / PM / CM / IM / connection information interworking
1 FM / PM / CM / IM data provided by OSS to the path and file generation rules to be supported as follows:
do.
SK Telecom
a) Naming Rule of the path and the file shall be provided in the manner specified by the Company.
b) Path and Naming Rule of files for transfer to the Bulk shall be provided in the manner provided by the company.
c) Naming Rule deliver complete path and file for recording Notification information should be provided in the manner specified by the
Company.
2 Notification format of FM / PM / CM / IM should be supported by the following format.
a) deliver complete NOTI data structure shall include a Timestamp, Type, Status, ID, Path, PKG version information, such as details
will be provided in the manner specified by the Company.
b) If the unsent data is transmitted to the Bulk even after the completion of transmission to be recorded in the transfer result NOTI file.
3 FM / PM / CM / IM provides detailed procedures for interworking of data to OSS should be supported in the following manner.
a) normal linkage procedure should be provided in the manner specified by the Company.
b) after the connection recovery procedure works shall be provided in the manner specified by the Company.
4 IM information, Descriptor information, provide connection information must be immediately available, depending on the quality of OSS, ETSI NFV
IFA012, IFA013, shall be provided in accordance with the SOL005 standards.
a) OSS may request to provide information on all the equipment that EMS is managed.
b) OSS may request to provide information about some of the equipment / components and connections that EMS is managed. ID of a query when OSS
manage specific items: must be used (for example, equipment ID, component ID, port ID).
c) providing information to be provided in response to a query from the OSS (CLI message and RESTful).
5 Report on Inventory information, Descriptor information, connection information change must be provided immediately when changes occur,
ETSI NFV IFA012, IFA013, shall be provided in accordance with the SOL005 standards.
a) EMS must provide information about the specific equipment / components and connect these changes occurred. ID managed by the OSS to refer to a range
change has occurred, you should use (for example, equipment ID, component ID, port ID).
b) provide the information shall be provided in Push mode (File Append and RESTful messages), without question the OSS.
2.7.3.7.2 SON works
1 Network Element to control the EMS or other type of gNodeB is periodically collected by NMS
Configuration information, you should Report a fault information and performance information.
a) one or through a plurality of Network Management System for the entire S / W and H / W configuration information must be provided
in the form of File.
and b) with respect to one or the S / W and H / W information configuration part via a plurality of Network Management system must be
provided in the File type or message type.
SK Telecom
c) one or over the entire operating parameter through a plurality of Network Management system shall be available in the file
form.
d) one or for the operating parameter part via a plurality of Network Management system shall be provided in the form of file or
message type.
e) S / W and a Network Management System interworking of H / W configuration information are to be given more than x times a day.
When changing f) H / W configuration information to be report to the Network Management System in real time.
With respect to g) fault information for all S / W, H / W which report to the EMS to be report to the Network Management
System.
h) for all Alarm generated by the EMS and the report should be available to Network Management System, when operator
wants must provide the ability to report only on a particular alarm.
If for i) Network Management System all types of malfunction alarm and the report to have been a release material should report the
release message. However, Alarm code and release code must be the pair indexing.
j) Network Element stars should provide interlocking traceability features.
Performance statistics to the statistics collected in the collection interval k) EMS must report to the Network Management System.
l) If a company needs to be developed for interlocking with each Network Element must support a minimum of time.
All information provided by m) Network Management System shall be presented to File Format.
Effect on the service due to n) linked with the Network Management system shall be free.
o) to the top of the OSS during interlock failed and Network Management System must report the cause of the failure for them.
2.7.3.7.3 Real-Time Call Log interworking
1 real-time and real time RPM Log Call Log The data to be collected in real time from our collection server,
The base station shall transmit the data collected by our servers.
2.8 RAN Virtualization Support
2.8.1 VNF your needs
Details VNF requirements for RAN Virtualization shall comply with 3.5.
SK Telecom
Details 2.8.2 RFV (Radio Function Virtualizaiton) requirements
1 for virtualization of Radio Resource NFV addition to the existing virtualization infrastructure to the evolution of the RFV following structure:
Figure 2.8.2-1 RFV structure
2.9 RAN competitiveness
One proponent shall present the advantage compared to other manufacturers products.
a) virtualisation and S / W introduced
b) Wireless Coverage, Beamtracking high speed, such as Throughput
c) Saving TCO (CapEx / OpEx)
d) Fronthaul capacity etc.
Network Configuration Method for e) Low Latency
f) Edge Cloud, Open API, etc.
Proposed in the second product of the Multi-Cell Environment Dynamic TDD operation status and DL: UL Configuration different
Cell mix during operation shall provide interference control solution to avoid interference effects.
Whether a) Dynamic TDD Support
b) support during detailed operational scenarios
c) Operating and performance indicators DL: UL Configuration Different Cell mix when interference control operation-specific solutions
SK Telecom
3 5G Core Network
5G Core Network works in conjunction with the 5G NR must be able to provide services 5G. 5G system as mentioned above may have two
configurations, in the present document to distinguish 5G Core Network, as shown below.
- 5G-enabled EPC: 5G Core supports the NSA (Non-standalone)
- 5GNC (5G Nextgen Core): 5G Core that supports SA (Standalone)
3.1 Common
When 5G Core Network Design shall comply with the requirements below.
1 must be a structure capable of high-capacity / high-speed Data transmission.
2 Unit extension and through a VM (Virtual Machine) configuration change should be the expansion of the capacity of hoisting structure.
3 must have a flexible system
a) structure that can easily accommodate changes in standards and reflects S / W of
b) facilitates the structure and interlocked in a network configuration, and other equipment
c) a quick and easy structure interference in H / W, S / W, VM-specific isolated
d) the possible structure Seamless S / W Upgrade without service interruption
4 should provide reliable and robust support maintenance functions, such as high level of operational capability and operator ease-of-use
do.
Must present an acceptable plan for 5 5G technology evolving standards and technology evolution is a proponent Upgrade to form
It is provided and shall minimize the H / W changes to the proposed 5G Core Network System.
6 other providers inter-system is to be applied to open Architecture / Protocol to enable the inter-working.
For example, the other Access Network equipment and between Core Network equipment of providers should not be a structure capable of interworking and matching.
Proposer proposer satisfy the following for H / W and S / W for supplying and comply with the specifications, if we Install the S / W of the proposer for H
/ W for supplying there to the company supplying H / W Spec It should support them when needed S / W features to support.
3.1.1 Network structure and configuration
NF constituting a 1 5G Core Network should be capable of being separated or combined, depending on the configuration 5G Use Case.
2 configuration, and interlocking of the 5G NF Core Network must be constantly changed through the operator setting.
SK Telecom
3 5G Core Network is supported by capacity H / W Configuration (H / W and the Vendor Model which, Rack, Shelf shape,
Board mounting, etc.) and the Session Bearer Capacity, Data Throughput, must be presented in accordance with the receiving subscriber capacity, and should be able
to be presented in accordance with the performance of CPS and TPS reference.
Depending on the 4 H / W Configuration presented in the Company, to provide capacity and performance 5G Core Network
It must be presented.
3.1.2 capacity, performance calculated based on
1 as it presents a performance / capacity specifications H / W specifications based on, or based on a more efficient general purpose H / W Spec
It shall be presented. (Example: 1U H / W server E5-2680v4 and 256GB RAM, GPU, FPGA accelerator)
2 consider the All-Virtualization structure to the S / W and H / W evolution in Scale-Up / Scale-Out structure, in the form of VNF
3 according to 5G Core Network of VNF purpose it must be able to physically separate multipurpose H / W.
4 hanmyeo be able to logically separate the VNF, while at the same time be able to take advantage of the most efficient H / W resources.
(Eg: Control / Management / User Plane separate structure)
5 should be able to take advantage of the efficient H / W resources adapted to the VNF the H / W shown in 1U units flexible
do. (Example: Control all the 1U / Management / User Plane functions with VNF and by separation)
6 consideration of the H / W component to be effective such as Active-Active, Active-Standby, N + 1 and N + M reliable
Consideration should be given to VNF structural redundancy.
7 and providing a system and Call Simulator for capacity and performance test, Call Simulator is further
It must be able to perform the following functions:
a) Traffic Profile and management for various Workload (for example: HTTP / s Web, Video Streaming, IMS, etc.)
b) whether or not generation and processing a variety of more 5-tuple Traffic Flow Check
c) 3GPP Control Plane / Management / User Plane generation and processing the Traffic Check
d) Benchmarking results detailed performance report
8 as it presents a performance / capacity and specifications based on the following Call Model, factors that affect the performance / capacity is
It must be clearly presented, taking into account the newly defined 3GPP Signaling procedures.
9. Proposed design requirements and in accordance with the method considering the UP / CP-separated structure needs through the tables to modify the following
Must satisfy the Summary, it needs to be modified in consideration of the 3GPP type Signaling / steps, if necessary.
3GPP Transaction per

3GPP Signaling
Signaling ITEM Subscriber Remarks
Count
type (BHCA)
INIT 10.5 0.04

ATCH
COMB 12 1.03
SK Telecom
UE 3 0.07
DTCH
NW 3 1.27
Preser
eNB INIT S1 REL 2.5 170.04
vation
UE 2.5 42.41
SR
NW 2.5 26.99
IDLE_MO 2.5 0.21
IDLE_MT 3.5 0.42

CSSR
ACTIVE_MO 2.5 0.23
ACTIVE_MT 3.5 0.13
COMB 7.5 8.73
TAU WITH_IMSI 9.5 2.13
PERIOD 3.5 0.66
X2 2 14.63
HO S1_INTRA_SRC 7 0.13
S1_INTRA_TAR 7 0.13
S1AP_PAG PAGING 0.19 77.94
• 1000000 Subscriber =
100,000 TPS
• BHCA = 347.18 TPH (First
• 2000000 Subscriber =
Requirements Summary subscriber)
200,000 TPS
• 0.1 TPS
• 10 Million Subscriber =
1,000,000 TPS
Remarks:
- BHCA: Busy Hour Call Attempt (call attempts being applied during the busy hour)
- Transaction: 1 Send + 1 Receive sum basis
- TPH: Transaction per Hour
- TPS: Transaction per Second
10, the PCC, such as billing and DPI-compatible add-on and a change in the capacity for each case of On / Off
And to present a practical and GW 11 packet Size Traffic Profile, the change of capacity according to the Profile
12 3GPP separated by CUPS virtual structure S / PGW UP capacity and UL (from AN) of - DL (to AN) traffic Gb / s
Ratio point of view, must meet the performance processing capability as shown in the following table. That is, except for the capacity of the internal East-West Traffic
and LB structure of the S / PGW UP and shall present a substantial User Plane processing capacity.
UL - DL Performance Capacity Performance Capacity Performance Capacity

Notes / Configuration
Ratio 100 Gb / s 500 Gb / s 10 Tb / s
Profile 1 50 Within 140U (4

Within 1U Within 7U Based on the upper surface 42U
- 50 Rack)
SK Telecom

- 80 Rack)

- 90 Rack)
13. The proposed system for processing Packet success rate shall ensure high reliability for Packet processing
14. The proposed system and satisfy the following Packet Processing Delay speed reference of that, the value of the Delay
It must be provided.
a) Signaling Processing Delay: 1ms
b) Traffic Processing Delay: 0.2ms
3.1.3 System Reliability
1 5G Core Network systems ensure the reliability and stability, as recommended in the relevant international recommendations (ITU-T)
do.
2 5G Core suppliers are active in the Trouble Shooting procedures in accordance with the failure, including H / W Fault
Shall participate, it must provide strong support necessary for effective Trouble Shooting. Scope of support to be provided
only shall comply with the criteria that we specified.
3.1.4 Reliability of service
1 Control Plane Signaling Quality in the Inter-RAT, interlocking between the Intra-RAT will ensure the success rate of more than 99.5%
do.
3.1.5 System scalability
1 when performing the authentication / gamseol operations and system upgrades will be constructed with no interruption in service, and Packet Loss.
2 shall be possible theories increase / decrease of the VM unit, H / W and S / W of 5G Core NE / NF is to increase VM unit / task gamseol
When you perform it shall be constructed without service interruption and Packet Loss.
3 5G H / W and S / W is the structure of the Core Network without add-stop service and expanded upon Packet loss should be
And it should be easy to process the structure, such as maintenance, testing, and verification failure
4 5G Core Network of Pakage replacement, Maintenance and Upgrade / Downgrade during the outage and Packet
It shall be constructed without a loss.
SK Telecom
3.1.6 System and service reliability
1 5G Core Network systems should provide features such as RM (Disaster Recovery) DR liver (Data Center) Inter DC
And in detail it is provided, including an IP network scheme capable of providing the service by Seamless (voice, data) for this purpose.
a) Location Free, Easy, Seamless should provide a service switching function. That is, the inter-service systems and national history should be possible
without the transfer process affecting subscriber services such as deleting and Reattach.
2 CP / UP must support the Pool structure, its functions should be provided even when a heterogeneous mix of operations.
The maximum capacity of the traffic over the three manufacturers have proposed even when the inlet is to ensure the stability of the system.
4 VM unit redundant architecture M: Live Migration Functionality must be provided between the N redundancy and Intra / Inter DC,
It shall show the test results can provide proponents.
5 3rd Party from the adverse effects caused by abnormal / malicious operation of the service must be able to protect the terminal and the system
And it shall provide the following functions for this purpose.
a) PPS control-specific IP / PORT / TCP Flag
b) specific Pattern (a specific character string in the Payload) detection and control PPS
6 shall be provided to protect the system from IP Scanning flowing from the Internet network.
7 Core ago capacities and characteristics of the equipment (use specific, resource-specific) can be automatically Balancing Traffic to reflect the
Function shall provide that, should the proposed measures.
3.1.6.1 More details RM functionality requirements
1 proposer H / W and S / W, such as a redundant system, and each module RM for providing continuity of service in the event of a fault
Solution offers, and shall show the test results.
a) H / W and S / W redundancy scheme, provided that the failure and automatic recovery algorithm
b) includes a maximum recovery time redundant and message loss minimization algorithm
2 Proposed operates to effectively control the incoming traffic capacity in excess and Burst traffic situation, and
The algorithm should be provided in detail.
a) Burst signaling and self-protection and other protection systems in preparation for traffic and traffic such as aggressiveness
3. The proponent shall provide a reliable service in an overload situation, to alleviate the overload situation
The ability to be presented in detail.
a) support standards-based link overload control function (for example: 3GPP TS29.272, RFC 7683 Diameter Overload Indication Conveyance
etc.)
b) operation of the load control algorithms and solutions,
SK Telecom
4. The proponent shall support the session inquiry and deletion of various conditions.
a) interworking node-specific, allocated resources, time, etc.
b) a long period of time, such as the use / non-use / Heavy User / Call Fail Reason subscriber extracts
5 linked node failure while maintaining existing services to support the non-reciprocal handling and traffic bypass feature.
a) HSS, EIR, PCRF, the existing call when the OCS, CG, etc. signaling node failure non-cross-treatment
b) DNS, PCSCF isochronous traffic system disorders Noti. And RM functions such as traffic detour
6 Restoration of functionality (with P-CSCF) set forth in the 3GPP standard should support.
7 charges related to an abnormal situation the alarm and RM functions
8 controls the terminal to be able to minimize the system impact of retries for a specific terminal. Certification to this
Failure such as a terminal during an initial access Fail Fail Cause-specific retry also be able to change the period
3.2 5G-enabled EPC
5G-enabled EPC must be able to use the NR Dual Connectivity forms to comply with the 3GPP Release 15 using the LTE
Control Plane. Non-Roaming Reference Architecture, including the 5G-enabled EPC is as follows:
HSS
S6a
5G-enabled
PCRF
MME S11
S1-MME
S1-MME Gx
S5 SGi
5G-enabled 5G-enabled
UE eNB PDN
SGW PGW
Uu
S1-U
X2 Gy / Gz
Charging
gNB
System
Figure 3.2-1 NSA Non-roaming Reference Architecture
Detailed Description of the Entity and Interface (or Reference Point) that is included in the figure of the article 1.2.2 and 3GPP TS
It is referring to 23.401. In order to support the interworking with 5G NR particular MME, SGW, PGW, so the center to be added to
function for NR supports, this article only if that supports interworking with each NR 5Genabled MME, SGW 5Genabled, referred to as
5G-enabled PGW.
Although the figure shows only the structure in which the 5G-5G-enabled enabled SGW and PGW separated for convenience, 5G-enabled EPC
suggesting shall be able to support a variety of configurations including:
SK Telecom
- The separated structure 5G-5G-enabled SGW and PGW enabled
- 5G-enabled SGW and PGW 5G-enabed an integrated structure
- The 5G-enabled GW User Plane and Control Plane is a separate structure,
3.2.1 Common Features
One The proposed system should support the following interworking 5G NR Option.
a) Option 3a
b) Option 3x
5G-enabled EPC 5G-enabled EPC
PDCP PDCP PDCP PDCP
RLC RLC RLC RLC
MAC MAC MAC MAC

Control
LTE eNB 5G gNB LTE eNB 5G gNB

Data
[Option 3a - Core N / W Split] [Option 3x - 5G RAN Split]
Figure 3.2.1-1 NR linkage Option 3a and 3x
2 The proposed system should provide the ability to add, disable, manage to 5G NR Secondary RAT that.
3 5G-enabled EPC system, a variety of IP address assignment system including IPv4 only, IPv4 / 6 mixed, IPv6 only
Flexible be able to assist you.
4 MTU Size shall be adjusted in accordance with the operator setting.
5 companies if there is a specific function must be presented.
3.2.1.1 Handover Support
One The system must support the following proposals and handover features that should provide a detailed scenario.
a) X2-based handover with SGW Relocation
b) X2-based handover without SGW Relocation
c) S1-based handover with SGW Relocation
d) S1-based handover without SGW Relocation
SK Telecom
2, the proposed system of Secondary RAT handover occurs for the terminal in use to 5G NR
It should support the ability to handle Connectivity.
3.2.1.2 IMS-based voice / video Service features
One The proposed system of MME, SGW shall provide the capability for voice / video call Service.
a) Default and provides Conversational Voice / Video Service function using the Dedicated Bearer
b) Proposed Service-specific capabilities for improved quality voice / video calls
2 should provide a separate accounting functionality stars Service based on IMS standards.
3 should be available IMS-based Emergency Call Service provides.
a) providing a Trace function with the IMSI, MSISDN, IMEI, etc. for emergency call
b) generating an emergency call generation / termination event with location information, store and retrieve
c) Emergency Call Service provides in all cases, including authentication failures subscribers, subscriber fee limits
3.2.1.3 Setup and Support D-value
1 The proposed system in order to prevent the loss of a Packet Downlink Path setting before you arrive
It is able to compute the appropriate D-value and should be able to Buffering the incoming Packet according to this value.
3.2.1.4 Restoration feature
1 The proposed system should provide failover capabilities defined in the 3GPP standard.
3.2.1.5 Dedicated Core and Network Sharing Function
1 The proposed system must be able to accommodate a variety of scenarios for Dedicated Core, the following functions:
a) DCN DCN separation and subscription-based information by selecting function of the terminal-specific Service
b) the terminal DCN selection and validation functions using the DCN-ID provided with the connection
2, the proposed system must be able to accommodate a variety of scenarios for Network Sharing, the following functions:
a) MOCN / GWCN
3.2.1.6 DRA support functions
One proposed system the DRA (Diameter Routing Agent) function to select the appropriate Diameter Server to
To be provided to the system's on-board, or a separate system.
SK Telecom
2, the system should be able to select Service Type Diameter Server through DRA to suggest.
3.2.1.7 Message Routing Support
1 The proposed system shall provide the following Routing feature.
a) RIPv1, RIPv2, OSPFv2, BGPv4, Static Routing function (IS-IS is recommended)
b) Virtual Redundant Router Protocol (VRRP) features
c) CIDR (Classless Inter-Domain Routing) features
3.2.1.8 MPLS features
1 The proposed system is efficient Routing and Traffic Engineering in IP Backbone network and external Internet to
For it shall support the MPLS (Multi-Protocol Label Switching) functions.
3.2.1.9 Daylight Saving Time
1 The proposed system shall be capable of DST Mode On / Off to set the operator or automatically, which, DST mode
Change in time should be guaranteed the reliability of the billing process.
3.2.1.10 Lawful Interception
1 The proposed system should support legal interception capability.
3.2.1.11 Overload Control
1 system should have step-by-step overload control algorithms that offer and call control scenarios such as overload
A detailed scenario should be presented.
In the second overload controls 3-5 overload step-by-step control is performed for the next function to be possible.
a) Service type control
b) Priority control per subscriber
c) a multi-RAT, etc. Signaling Path by interlocking Case Control
d) Protocol specific control
e) Control Processor by
f) IP bandwidth control by
3.2.1.12 Charging Function
1 The proposed system should provide separate accounting functions for the Data Transfer to 5G and LTE.
SK Telecom
2 5G-enabled GW is more than 9,000,000 billing Data Protocol by such GTPP, Radius, Diameter
It must be able to Buffering.
3 proposed system shall provide differential billing function.
4 The proposed system must be able to store at least 30 days generating a CDR in internal or external to Disk,
To provide a separator stars lookup functions such as subscriber ID and the APN for the saved Data.
It shall save a log of the five transmission charges.
6:00 Failed to create the billing should print its history.
7 charging transmission and storage during non-circumvention must be stored in the EMS Server, etc.
8. The proponent shall provide accounting segmentation capabilities that meet the requirements presented by the company.
9 shall satisfy the following conditions CDR performance and reliability.
a) generate billing CDR failure: EPS Bearer must be activated within the CDR generation failure rate for the call is successful 1CDR 1000 million per
CDR.
b) CDR transmission failure rate: CDR transmission failure rate of the 5G-GW eanbled normal charging system for a CDR generated by the should
be less than one per 10 million CDR.
c) CDR transfer processing performance (to the billing system): more than 100 million per hour
d) Opening Time, Closing Time Error: Less than 0.1 seconds
e) Partial CDR generation time error due to the Time Limit: within 0.5 seconds
f) Data Volume error: 10 7 Within
3.2.1.13 Trace Function
1 The proposed system shall provide the following functions Trace, performance / capacity testing results according to Trace, which
It should be presented.
a) Automatic shutdown when Trace Trace decreases system performance in excess
b) at least 0.1% of the processable number of subscribers simultaneously Trace
c) Trace of the subscriber identification number
d) Trace and Interface Protocol Trace On / Off function according to an Interface
According to e) Control / User Plane Trace
f) HSS, 5G-enabled EPC Entity O & M Trace by
g) Trace Trace status information inquiry and status control of the Superuser
SK Telecom
h) 5G-enabled EPC system-wide and individual Trace Function
i) Traffic Trace and Packet Capture / analysis functions
2 Trace output must provide the following information:
a) Trace start and end times
b) Message pass / fail results and reasons for failure
c) UE IP address
d) 5G-enabled MME, SGW, PGW IP address of
e) APN
f) billing information
g) Throughput information
h) Uplink / Downlink Packet Volume Information
i) Session Duration Information
j) the mandatory information as defined in the Parameter Other specifications
For the Parameter included in the 3 Trace it must be provided by the help function.
4 shall be provided to any subscriber-Trace function through a separate window.
3.2.1.14 Other call processing
1 must be able to control a specific Interface / interlocking NE per second message is sent and the incoming quantity set by the system
2 stars by the eNB Group, IP Address should provide overload control.
3 The proposed system is a free development with respect to the requirements present a company specialized call processing required to implement our sangyongmang
Should be supported, based on the time period of the current level of implementation will be submitted to the RFP Response time.
4 5G-enabled GW has to provide the following functions for the external Interface interlock.
a) interlocking external router according to LACP / LAG and load balancing
b) Static L3 external router interlock and load-balancing function of the routing
c) Dynamic L3 routing (external router interlock and load-balancing function of the OSPF, etc.)
d) Other proponents specialized functionality Routing
In all five tunnel sections to support the Inner / Outer IP Fragmentation and, 1500 Byte section below and beyond
Fragmentation should be set up ways for each.
SK Telecom
3.2.1.15 Test Support and Debugging Function
One must be able to vary the allocation of dedicated resources and policies, including a specific session to Test Support.
a) a specific VM, APN, IP Pool, Rule-base, PCO, etc.
When two failures occur for a variety of Fault message identifying the cause and can cause rapid sufficient Log
It should and must be able to present a variety of ways Debugging.
3 Call Setup during Initial Context Setup Request encrypted in a way that we present based in Message
Including the IMSI information should be sent to the eNB.
4 ways to verify the self-test Simulator call service and billing through abnormalities in commercial equipment
It is provided to
3.2.1.16 virtualization support
The proposed system is one that other suppliers of Orchestrator, VNF Manager, VIM (Virtualized Infrastructure
It shall provide the Manager) such as NFV Management Entity with Interoperability.
3.2.1.17 H / W gain independence
1 H / W, taking into account the evolution of S / W will be free to obtain H / W Independence H / W for the object when S / W development and change
do.
3.2.2 Management
3.2.2.1 O & M requirements Common requirements
1 The proposed system must be able to manage the status of the components in real time, about the status change
Information to the operator shall provide a visible, audible
2. The proposed system should be able to be controlled by the status of the components of the instruction.
For 3 H / W and S / W Event occurs, the operator must provide the Alarm a visible / audible.
4 to check the status of the components of the system status, and proposals for interworking system to an operator command
Should.
5 Physical NIC VNIC and used in the proposed system must provide Port Mirroring feature.
Control per subscriber for all the Protocol to the proposed system through instruction 6 Use Plane, User
It shall be available for the Trace Plane.
7, and the Signaling Bearer for all subscribers via a system internal or external to suggest Interface
To allow real-time Logging should be able to provide Disk and System Logging and Analysis Solution.
SK Telecom
8. The proposed system should provide Self Diagnosis function and through this system, VM status and H / W to
The diagnosis of the Unit Operator for the state to be possible.
9 proposed system should provide overload control commands by the operator
The control system configuration, including 10 proposed expansion / gamseol / enable / disable / subscriber moves / transfer / restart of the element
The CLI (Command Line Interface) and GUI (Graphic User Interface) must be done through.
11 Service that you are able to determine the number of each type of call Session in real time, next time, the largest lake,
It must be able to provide an alarm in accordance with the operator setting the minimum conditions of the lake.
a) minimum standards lake below one per operator set
b) Based on more than one operator to set the maximum hourly Lake
12, the proposed system in real time, 5 minutes for the call processing statistics, 10, 30, 60, and providing a 24-hour cycle,
It shall satisfy the following conditions:
a) the statistics provided should be broken down into specific Protocol, backed by system, by Service Type, etc. and be able to verify the
Service Quality through it.
b) metrics should be available in the Threshold setting by the operator and must be available for out-of-this Notification
Threshold.
13 proposed system must be able to determine the next state of call processing resources, the call processing resources by the operator
Management standards must be set and must provide the basis upon departure warning.
a) IP Pool, Bandwidth, Memory, CPU, Session Count, TPS, CPS duty
b) The other main call-processing-related resource utilization
14 must provide a Web-based On-line operating manual and Hard copy Soft copy and manuals.
15 proponents should be able to offer if you have specific functions.
16 and the new statistics and add / edit the alarm should be easy, should be provided for the room.
One should be able to check the progress of the initialization.
2:00 perform initialization tasks should support the following functions:
a) it should be the Session processing and billing generation proceeds as normal for conventional call processing.
b) shall provide information that can be analyzed during initialization failure cause of the failure, it must be wonbok is possible to its original state.
c) In the case of subscriber information DB initialization should enable the On / Off of the information maintained.
SK Telecom
3.2.2.3 Dump Function
Total File or File to select a specific system must be capable of storing a Disk from a storage medium.
2:00 Dump run should be as File system structure does not affect the existing DB.
3 File Dump The total duration should not exceed 10 minutes
3.2.2.4 Loading feature
1 As the system loading request, to be performed by the sequential automatic Loading function of the system.
It should provide Class Loading (Restart class) VM-specific / call processing Block Star according to the second operator.
a) memory initialization
b) initializing program loading level Data (Data Program Loading)
c) Reset of the Guest OS level
3 VM-specific / call processing by Block Loading Loading when the operator to check the status (On-line, On-Demand) to
It must and should be checked is currently Loading progress.
4 process is a redundancy and that each VM-specific / call processing by Block in a state in which multiplexing information Loading
It must be checked.
5 VM / per call processing upon confirmation by Information Loading Block, DISK in the File Size Loading File with the processor
Size should be the same output, and should be provided with information about Version people, Loading dates, such as the Loading Block by Size.
6 shall be possible to load and call processing in less than three minutes for the complete system initialization.
3.2.2.5 Log functions
1 suggests that system is to be provided as a system event log function follows: Message
a) loading the program type File storage function (daily, automatically Renaming) by File size
b) generating and Message ID Message Type classification by output function
c) the system ID and date (year, month, day, hour, minute, second, day) display
3.2.2.6 S / W Upgrade Features
It must be given time to complete the transfer of the 1 S / W Upgrade, and proponents for maintaining continuity Service
It must be able to present a specific function.
2 S / W (Partial S / W and Total S / W) Upgrade / Downgrade, Maintenance Service and Packet interrupted at work
It shall be constructed without a loss.
SK Telecom
3 S / W Update wonbok after application, even if it should not affect the existing Service.
4 S / W (Partial S / W and Total S / W) Update System Service interruption to the existing Service continued support at work
So two hours should be provided to secure Service Continuity features.
It must be able to present the 5 S / W Upgrade reference time.
6 issues on the S / W will be able to update to fit the Solution proposed time of the request according to the priority
do.
importance History Solution proposed deadline
1 (a call processing defect) Issue occurs when the customer complaint handling defects Immediately
2 (poor performance) When KPI indicators and bodily deterioration Within 2 days
3 (Alarm) When Fail occurrence of call processing components, etc. Within 1 week
3.2.2.7 System Information Backup
1 periodically and the system backup and restore functions of the Network-specific configuration information at the request of the operator
It shall be provided and shall comply with the following conditions:
a) Program loading type File storage function (daily, File Renaming automatically by size)
b) Select the entire File or File-specific should be able to backup and recovery.
c) While performing a backup task it should not affect the existing call processing and DB.
d) Working hours should not exceed 20 minutes.
e) The system should load rises due to backup operations to exceed 10% and shall not affect the existing Service
3.2.2.8 Remote control function
One It must provide the following remote management capabilities of the user.
a) you should be able to block the outside Telnet connection to the case of critical operation system when connected to a dedicated terminal or Superuser.
b) be able to control to make the currently connected user when connected to a dedicated terminal or Superuser.
c) when connected to a dedicated terminal or Superuser must be able to block new users access, you should be able to output the
appropriate Message for the block new users.
3.2.2.9 Reliability and ease of operations
A first interlock and configuration information input / delete operations, and the like to be easy to ensure the reliability, see the results and work
It must be able to check the history of a certain period of storage /.
SK Telecom
2 must be applied immediately, without any interruption during service work, proponents jobs generated service interruption
For it should be clearly presented, including the impact.
3.2.3. 5G-enabled MME
In this section refers to 5G-enabled MME to MME.
3.2.3.1 function
1 MME should be able to accommodate all relevant UE Capability specified in the 3GPP standard processes.
2 MME will be able to handle and accommodate all NR (New Radio) support-related functions specified in the 3GPP standards
do.
3. Proponents should be given if there is a specific function.
3.2.3.1.1 Tracking Area Management
1 MME is the TAI List Configuration and Management that can be separated and manage 5G and 5G support area unsupported region
Two proponents should be able to propose an efficient TAI List Configuration and Management.
3 MME for the following items shall be given the maximum acceptable levels.
a) the maximum number of supported eNB
b) The maximum supported number of TAI List
c) The maximum supported number of TA
3.2.3.1.2 UE access control
1 MME shall manage the connection state of the UE, the relevant Timer should the operator can set.
a) Mobile Reachable Timer, Implicit Detach Timer, etc.
2 MME should be able to distinguish between 5G NR Whether a terminal for the connection request.
3 MME 5G is considering whether to join on whether the terminal supports 5G and 5G Service for terminal
It should be able to decide whether or not to allow the Service.
4 MME may provide a bypass (Re-route) function of the terminal to the other MME to process the access request requested
Should.
3.2.3.1.3 Paging management
Sequential Paging Timer setting by the operator 1 is to be possible.
SK Telecom
2 Proposed shall be able to present an efficient sequential Paging scheme.
3.2.3.1.4 MME Pool Management
1 MME should be able to set the MME Pool information.
2 Serving MME MME in the same Pool failure must be able to handle this scenario and details
3 must support the MME among Load Balancing within the same MME Pool, it shall give a detailed scenario.
3.2.3.1.5 QoS management
MME 1 is required through Subscribed Data in the APN-AMBR is received from the HSS to perform the following functions:
do.
a) passing APN-AMBR to the 5G-enabled SGW
b) Subscribed UE-AMBR, eNB transmission for UE-AMBR values calculated and Access Network Control via the APN-AMBR values
2 MME should be able to support the new QoS parameters to support the 5G Service.
a) extended AMBR
b) new QCI and the associated QoS parameters
3 MME should support a mechanism to map the existing 5G QoS parameters QoS parameters.
3.2.3.1.6 Charging
MME 1 is required to support the control of the separation charges for the Data transmitted to 5G and LTE.
2 MME is required to support the function of receiving and 5G separated from charging information transmitted to the eNB 5G-enabled SGW
do.
3.2.3.1.7 S5 / S8 Protocol setting
1 MME should be able to manage the possible support of the Protocol SGW, PGW.
3.2.3.1.8 SGW Selection
One MME should be able to perform the SGW Selection by considering the following:
a) Capability of the terminal NR
b) the terminal is selected DCN ID
c) registering information on the use of terminal NR
SK Telecom
d) NR whether support of SGW
2 MME are all the Dynamic Selection SGW via the SGW Static Selection and DNS over a predetermined value,
It must be able to perform.
3 MME can manage them separately if you have the SGW / PGW integrated mixed equipment in the Network
Should.
3.2.3.1.9 PGW Selection
1 MME must be able to perform the PGW Selection to consider the following, the Priority must be set
do.
a) Capability of the terminal NR
b) the terminal is selected DCN ID
c) registering information on the use of terminal NR
d) NR supports the PGW whether
Selected according to e) Pre-Configuration APN table
Selected according to f) Pre-Configuration Type PDN
g) Pre-Configuration other Subscribed selected according to subscriber information
Selection by h) APN OI-Replacement
Selected according to i) Default APN
Dynamic Selection through j) PGW Identity (FQDN, Logical Name)
3.2.3.1.10 Overload Control and Load Balancing
1 MME is an appropriate overload control settings for the eNB should be possible, depending on the system overload situation and
It shall give a detailed Scheme.
2 MME new or in overload situations should be able to present the existing Session control scenarios.
3.2.3.1.11 Authentication and Security
1 shall support the NAS Signaling Integrity between MME- terminal and shall present a detailed scenario.
It should support the 2 MME-eNB between Security and shall present a detailed scenario.
3 certification process must be On / Off depending on the setting of the operator.
4 to be presented to the performance capabilities and the capacity to be reduced when degradation of the authentication and security features.
SK Telecom
3.2.3.1.12 SCTP Server / Client
1 MME is the SCTP (Stream Control Transmission Protocol) Server or Client functions in accordance with the following conditions
It shall be carried out.
a) When eNB works: SCTP Server
b) SCTP Client: HSS, during EIR works
2 to manage the SCTP Association If you have a problem, it should be released.
3 it must support the SCTP Multi-homing function.
3.2.3.1.13 SMS support
One MME should provide the functionality of the SMS Service SMS over SGd way.
3.2.3.2 Capacity and performance
1 MME should meet the following criteria capacity by at least one meal-like items.
a) present a minimum geometry for the MME 1 expression, and receiving on this basis the maximum subscriber / Concurrent Session can / can simultaneously present
a Bearer / TPS
b) Concurrent Session is three times co-Bearer of subscribers can cater up to accommodate more than four times
c) at least one shape expression accommodate more than one eNB and over 10,000 40,000 CU
d) over the next number of interlocking manages Node
• EIR: 20 or more
• HSS: More than 100
• S / PGW: more than 100
e) at least one expression and shape to be able to respectively manage at least more than 10,000 TA List and the TA, the maximum acceptable TA List, a TA may
present and effective control measures
f) MME performance and capacity-related information when the addition of an additional base Call Model, H / W specification, provided it
2 MME shall present the information request to the maximum shape under the reference 1, and so on.
a) the subscriber must be able to accommodate at least 3 million, accommodate presenting the maximum subscriber capacity and shape
b) Session / Bearer can must be able to accommodate at least 309 million / 12 million or more, respectively, present the maximum acceptable Session / Bearer
be
c) can be up to 11 bearer assigned per subscriber
SK Telecom
d) call processing capabilities should be able to accommodate at least 250,000 or more, and TPS, can accommodate up to present the TPS
3 Architecture & Scalability-related must show the following request.
a) Proponents suggest physical universal H / W and the VM number for Case bottom, respectively, present the overall system construction geometry detail
Case # 1 Case # 2 Case # 3 Case # 4

division
Subscribers 10 just 100 just 250 just 500 just
b) 19-inch standard Rack (42U) standard provides suggested a possible maximum capacity and the present system configuration, the shape for it in detail
c) be a Scale In / Out minimum increment / gamseol unit is less than 1 million subscribers, and presents a minimum increment / unit gamseol
Applying d) without any H / W for performance by the object / dose related S / W Development and Change
e) shape proposer is presented and Traffic is to be treated is evenly Balancing between VM / server, provided for a scheme that can be
uniformly distributed to the inlet Traffic
3.2.4 5G-enabled SGW
This section is referred to 5G-SGW enabled by SGW.
3.2.4.1 function
1 SGW must be able to handle and accommodate all NR (New Radio) support-related functions specified in the 3GPP standard.
2 proponent should be given if there is a specific function.
3.2.4.1.1 Packet Buffering
1 SGW is the destination terminal is able to Buffering the called Packet Data when the called party can not for reasons such as Idle State
Should.
2. The proponent shall give the Buffer Size in the SGW.
3.2.4.1.2 QoS
1 SGW judges whether GBR supportable to the Bearer request Bearer set, changed, the failure handling
It must be able to provide.
2 SGW will be able to support the new QoS parameters to support the 5G Service.
a) Extended AMBR
b) New QCI and associated QoS parameters
SK Telecom
3 shall support the Transport Level Packet Marking feature.
4 shall be processed in accordance with the Packet QCI priority.
3.2.4.1.3 Charging
1 SGW should support the separation charging functions for the Data transmitted to 5G and LTE.
2 SGW must support the function of receiving and 5G separated from charging information transmitted to the MME 5G-enabled PGW
do.
3 SGW shall provide the charging function through linkage with the OFCS for such roaming billing settlement.
3.2.4.1.4 UP / CP Separation
1 SGW should be able to operate in UP / CP separated structure.
2 UP / CP of discrete SGW should be capable of being integrated with the UP / CP of discrete PGW.
3, if the SGW UP / CP separation of, Interface between the UP / CP shall comply with the 3GPP standard.
4, even if the SGW UP / CP is disconnected from other equipment: should be able to be associated with (e.g., eNB, gNB, MME, SGW, PGW)
do.
5 If the SGW UP / CP the separation, you must specify the UP / CP allocation of the functions of the proponents SGW.
One SGW should meet the following criteria capacity with minimum feature reference 1, and so on.
a) Present the minimum geometry for the SGW 1 expression, and can accommodate up to subscriber / Concurrent Session possible on this basis / co-present
can Bearer / TPS / Throughput
b) Concurrent Session 3 times the maximum subscribers, the number of concurrent Bearer accommodates up to four times more subscribers.
c) Receiving at least one shape expression over 40,000 eNB and over 1,000 CU
d) Processing over 10,000 a Routing Entry
2 SGW shape up and down based on one meal should provide the requested information.
a) Session / Bearer can must be able to accommodate at least 300 million / 900 million or more each, the maximum acceptable given Session / Bearer can
b) Data processing power (Throughput) should process at least more than 100Gbps, it presents a maximum processing capacity
c) Call processing performance and be able to accommodate a minimum of 250,000 TPS least, acceptable given the maximum TPS
3 It must present a request under Architecture & Scalability-related.
SK Telecom
a) Proponents suggest physical universal H / W volume for the lower Case (CP / UP, respectively), and present the overall system construction geometry detail
division Case # 1 Case # 2 Case # 3 Case # 4
Control Plane
10 just 100 just 300 just 500 just
(Session)
User Plane
10G 60G 100G 200G
(Throughput)
b) 19-inch standard Rack (42U), providing the reference state the capacitor (CP, UP respectively) as possible, and for this system
It presents a construction geometry detail
c) Scale In / Out minimum increment / gamseol unit must be less than 1 million subscribers and 1Gbps and presenting minimum increment / unit gamseol
d) H / W body usually applied without due performance / capacity-related S / W development and change
e) Proposed by the present shape it is processed, and Traffic is to be evenly Balancing between VM / server, provided for a scheme that can be
3.2.5 5G-enabled PGW
This section is referred to as a 5G-enabled PGW PGW.
3.2.5.1 function
1 PGW will be able to handle and accommodate all NR (New Radio) support-related functions specified in the 3GPP standards
do.
2 proponent If you have specific features should be presented
3.2.5.1.1 QoS and PCEF
1 PGW judges whether GBR supportable to the Bearer request Bearer set, changed, the failure handling
It must be able to provide.
2 shall support the Transport Level Packet Marking feature.
3, depending on the QCI priority should handle the Packet.
4 It shall provide the Bearer Binding feature.
a) the same IP address, if the multi-EPS Bearer is created with the same APN provides the ability to select one of the EPS Bearer by
the Packet Filter
5 GBR Traffic Policing and perform functions through APN-AMBR
SK Telecom
6 PGW is required to support the new QoS parameters to support the 5G Service.
a) extended AMBR
b) new QCI and the associated QoS parameters
7 Bearer Binding Verification should be carried out on the Up / downlink.
8 PGW and PCRF shall provide interworking via Gx / Sd Interface, Predefined Rule Set Features
Dynamic PCC rule and should be able to apply through the PCRF.
9 PGW will be able to apply the DPI Function and, DPI Function shall provide the following features:
do.
a) Application / subscriber / IP, Port and URL-specific Traffic Management (Traffic Shaping / Packet
Discard / Redirection)
b) Tethering detection and blocking
c) Malware such as the Signature Packet within the worm, DDoS attack is received from a subscriber or an external network
Detection and blocking
10 It should provide for the possible detection and blocking Signature at DPI.
11 Proponents about the Signature Update planning and application of the L7 Application Pattern add and change measures
It shall be presented to the bailout ever.
12 Must be able to present the value DPI Function Application performance decreases when the PGW.
13 Proposed is a detectably with respect to the encryption of traffic, and whether the detection level, that potentially increase the detection sujunreul
It shall be presented in detail.
14 IP, Port, URL for Traffic Management should be available at least 3 million applies.
3.2.5.1.2 Charging
1 PGW shall support the separation charges for the Data transmitted to 5G and LTE.
2 PGW is a separate charging information for each RAT from 5G-SGW enabled to support the separation charging 5G
It should support the ability to receive.
3 PGW is the Credit Function and Function Online Charing through OCS linked to real-time data charging
4 PGW shall provide the Flow Based Charging function according to the PCC Rule.
5 PGW is the charging data to comply with the billing generated and interlocked specification to use our accounting structure of
Generated and be able to transfer the charging data generated and interlocked OFCS.
SK Telecom
3.2.5.1.3 Operator Determined Barring related
1 PGW should provide a 3GPP standard-based ODB function.
3.2.5.1.4 Star Service Routing
1 is a PGW Packet as a separate physical Port according to the Service and the user via the identifier, such as APN
It must be able to Routing.
3.2.5.1.5 APN and IP Pool-related functions
1 PGW will be able to assign a Virtual APN, and be provided with a separate function for each Virtual Routing APN
do.
2 according to the APN shall be able to assign an IP on a separate IP Pool.
3 should be delimited in accordance with the accounting APN.
3.2.5.1.6 UP / CP Separation
PGW 1 shall be capable of operating in UP / CP separated structure.
2 UP / CP of discrete PGW should be capable of being integrated with the UP / CP of discrete SGW.
3 when the PGW UP / CP separation of, Interface between the UP / CP shall comply with the 3GPP standard.
4, even if the PGW UP / CP is disconnected from other equipment: should be able to be associated with (e.g., SGW, PCRF, billing systems, etc.).
5 If the PGW UP / CP the separation, you must specify the UP / CP allocation of the functions of the proponents PGW.
One To GW per minimum feature formula must meet the following criteria capacity.
a) present a minimum geometry for the GW 1 expression, and can accommodate up to subscriber / Concurrent Session possible on this basis / co-present can
Bearer / TPS / Throughput
b) Concurrent Session is three times, concurrent Bearer up to the subscriber receiving at least 4 times the maximum subscriber
c) receiving at least one shape expression over 40,000 eNB and over 1,000 CU
d) processing at least 10,000 the Routing Entry
e) PGW must be able to accommodate more than 2,000 APN, APN state the receiving capacity
2 GW below 1 Maximum shape criteria must present a request.
a) Session / Bearer can must be able to accommodate at least 300 million / 900 million or more each, the maximum acceptable given Session / Bearer
can
SK Telecom
b) Data processing power (Throughput) should process at least more than 100Gbps, it should be provided to the maximum processing capacity. In addition, PCC,
billing and DPI function On / Off presents an amount of change in capacity (Throughput) for each
c) call processing capabilities should be able to accommodate at least 250,000 or more, and TPS, can accommodate up to present the TPS
3 Architecture & Scalability-related must show the following request.
a) Proponents suggest physical universal H / W volume for the lower Case (CP / UP, respectively), and present the overall system construction geometry detail
division Case # 1 Case # 2 Case # 3 Case # 4 Remarks
Control Plane
(Session) 10 just 100 just 300 just 500 just

PCC, Billing, DPI On / Off
User Plane Presenting both the shaped
(Throughput) 10G 60G 100G 200G
b) 19-inch standard Rack (42U) standard provides the maximum capacity (CP, UP respectively) the present, and presents a system configuration shaped for this detail
c) Scale In / Out minimum increment / gamseol unit must be less than 1 million subscribers and 1Gbps and presenting minimum increment / unit gamseol
d) H / W body usually applied without due performance / capacity-related S / W development and change
e) shape proposer is presented and Traffic is to be treated is evenly Balancing between VM / server, provided for a scheme that can be
3.2.6 Interface specification and existing EPC works
3.2.6.1 Common
1 The proposed system shall comply with the 3GPP Release 15 specifications.
Two proposed systems and components must be able to be based on the standards in conjunction with other manufacturers systems,
If necessary, it must comply with the standard linkage that we provide.
3 The proposed system with our Core equipment, including HSS, HLR, PCRF, OFCS, OCS, IMS (CSCFs), which
It should support Interoperability.
4 The proposed system should be capable of efficient structural integration with our existing systems.
a) Registration processing of the interlock destination, and Paging System
b) handover (Voice, Data, etc.) of the target system and the interworking
c) providing the continuity of the services provided by interworking machine (additional services, billing, etc.)
SK Telecom
5 the proposed system in addition to the call processing for a subscriber linked to the reliability of the operating functions such as statistics, billing for
It must be ensured.
3.2.7 Migration Support
1. Upgrade the system should be available to 5GNC upon our request to offer.
3.3 5G Nextgen Core
5G Nextgen Core (5GNC) shall be capable of operating in Standalone Mode in conjunction with AN 5G and compliant with 3GPP Release 15.
Non-Roaming Reference Architecture for 5GNC are as follows:
TDB
Charging TDB
AMF SMF PCF SMSF
N1
System
N2 N4
N3 N6
UE gNB UPF DN
Uu
Figure 3.3-1 SA Non-roaming Reference Architecture
Detailed Description of the Entity and Interface (or Reference Point) that is included in the illustration. See also the section 1.6, and 3GPP TS 23.501 of
the present document. In 5GNC Interface are to be implemented as Service-based Interface newly defined in Release 15.
a) Namf: Service-based Interface that provides the AMF
b) Nsmf: Service-based Interface that provides SMF
c) Nnef: Service-based Interface that provides NEF
d) Npcf: Service-based Interface that provides PCF
e) Nudm: Service-based Interface that provides UDM
f) Nnrf: Service-based Interface that provides NEF
g) Nausf: Service-based Interface that provides AUSF
h) Nnssf: Service-based Interface that provides NSSF
i) Naf: Service-based Interface, which provides that the AF is available
j) Nsmsf: Service-based Interface that provides SMSF
SK Telecom
In addition, to 5G Nextgen in the system that supports the Standalone Reference Point it should be implemented in a Point-to-point manner.
a) N1: between the UE and the AMF Reference Point
b) N2: 5G AN between the AMF Reference Point
c) N3: 5G AN between the UPF Reference Point
d) N4: the Reference Point between SMF and UPF
e) N6: between UPF and DN Reference Point
3.3.1 Common Features
1 5GNC system in conjunction with the 5G AN should be able to operate in stand alone mode (Standalone Mode).
2 The proposed system will support a variety of IP address allocation method such as Flexible each PDU Session IPv4, IPv6, which
It should be.
3 MTU Size shall be adjusted in accordance with the operator setting.
4 5GNC system must support the Intra-5G Multiple Connectivity feature.
3.3.1.1 LTE Interworking
1 5GNC system must support the LTE Interworking scheme.
a) Single-based Registration interworking
b) Registration Dual-based interlocking of
2 proposed system should support QoS Mapping and Security Context Mapping occurs during Inter-RAT Mobility
do.
3 5GNC system, the system must support the Inter-RAT Multiple Connectivity feature.
3.3.1.2 Handover Support
One The system should provide a hand-over function between 5G base station as follows: The proposed.
a) Xn-based handover with and without UPF Relocation
b) Hand does not use over Xn with and without UPF Relocation
3.3.1.3 International roaming support
1 The proposed system must be able to accommodate international roaming scenarios, Home Routed and Local
It must be able to support the Breakout.
SK Telecom
3.3.1.4 SBI (Service-based Interface) support
1 proposed system is basically compliant Service-based Architecture defined in 3GPP Release 15, which
2 Control Plane functions of the proposed system will be implemented to meet the Service-based Interface Specification
do.
3 Service-based Interface of the proposed system must support Multi-vendor Interoperability.
3.3.1.5 Daylight Saving Time
1 The proposed system shall be capable of DST Mode On / Off to set the operator or automatically to Mode
Change in time should be guaranteed the reliability of the billing process.
3.3.1.6 Lawful Interception
1 The proposed system should support the lawful intercept capabilities.
3.3.1.7 Overload control
1 The proposed system should have step-by-step control algorithm must present a call overload control scenarios
do.
3.3.1.8 Authentication and Security
1 5GNC system should provide the following features for the terminal 5G.
a) User Authentication
b) Security Context creation and management
c) encryption support for user-Traffic
d) support for encryption and integrity Signaling
3.3.1.9 IP Pool Management
One should support the effective ways of managing IP Pool (application / delete / search).
a) integrate the internal management of the IP Pool of 5GNC (assign / delete / search) presented a plan to
3.3.1.10 Charging Function
1 The proposed system shall provide differential billing function.
SK Telecom
2, the proposed system must be able to store at least 30 days generating a CDR in internal or external to Disk,
To provide a separator stars lookup functions such as subscriber ID and the APN for the saved Data.
3 shall save the log for billing transport.
4:00 Failed to create the billing should print its history.
5 charging transmission and storage during non-circumvention must be stored in the EMS Server, etc.
6. The proponent shall provide accounting segmentation capabilities that meet the requirements presented by the company.
7 shall comply with the CDR performance and reliability criteria that we proposed.
3.3.1.11 IMS-based voice / video Service features
1, the system must support the Audio / Video Service for IMS-based offer.
2 should provide a separate accounting functionality stars Service based on IMS standards.
3 General and Limited Service subscriber terminal status to all IMS-based Emergency Call Service provides must be in.
3.3.1.12 Trace Function
1, the system must provide a level of functionality equivalent to the Trace our existing commercial equipment that offers (5G-enabled
EPC Trace Function Note)
If you have a vendor-specific features considering the 2 5G should be presented.
3.3.2 Management
1, the system must provide the same level of management with our existing commercial equipment that offers (5G-enabled
EPC management Note)
If you have a vendor-specific features considering the 2 5G should be presented.
3.3.3 Access & Mobility Management
3.3.3.1 function
AMF must be able to handle to accommodate all relevant UE Capability specified in the 3GPP standard.
3.3.3.1.1 Registration Area Management
1 AMF must be able to manage a configuration of varying sizes TA Considering the terminal operation mode.
2 AMF must be able to configure the optimal Registration Area for each terminal, Registration Area is
It is expressed in the TAI List.
SK Telecom
3 The proposed system should support an efficient TAI List Configuration and Management.
4 The AMF is required to present an acceptable maximum value for the following items.
a) the maximum number of supported gNB
b) The maximum possible number of TA support
c) Maximum number of supported TAI List
3.3.3.1.2 UE access control
1 AMF shall manage the connection state of the UE, and then the Timer should the operator can set.
a) Mobile Reachable Timer
b) Implicit Detach Timer
2 AMF is case of a supported RAT UE, and shall be able to determine the appropriate RAT access for the terminal.
a) 5G Only
b) 5G and 4G
3 AMF is to provide a bypass (Re-route) function of the terminal to the other AMF is processing a connection request requested
Should.
4 AMF must be able to provide the ability to be processed by the EPC Fallback for connection management of the terminal.
AMF 5 shall be able to consider performing the connection control and the Network Capability Slice information of the terminal.
6 AMF must be able to support various operation modes in accordance with the Capability and the subscription information of the terminal.
a) UE battery consumption, the operation mode for the system resource saving 5G
b) Mode of operation for ultra-low latency / high reliability Service offers
3.3.3.1.3 Paging management
1 AMF system must be able to support the Paging Service, and Session-specific settings to suggest.
The Paging Timer sequentially set by the second operator to be possible.
3 5GNC system should support efficient sequential Paging room.
3.3.3.1.4 AMF Set Management
1 The proposed system should be managed in accordance with the AMF Set Network Slice.
AMF Set by the two operators shall be freely create / change must be reflected in the configuration information 5G AN
do.
SK Telecom
3 in the Registration process AMF Selection is taking into account the Network Load Slice information and the network state of the terminal
It should proceed.
4 AMF Removal / Failure / overload occurs should be able to do the AMF Reselection effectively.
5 in conjunction with the AMF and AMF Set Selection should be able to effectively manage the temporary identifier of the UE.
3.3.3.1.5 SMF Service works
1 AMF should support the exchange Signaling to SMF performs the functions of a terminal for the Session Management
do.
2 SMF works for Communication Service and Support is made using the SBI.
3.3.3.1.6 SMF Selection
One must support both the Selection and Selection by Local Settings leverage Discovery Service.
2:00 SMF Selection should consider the following information:
a) Whether roaming
b) DNN
c) Information Network Slice (Slice and associated Service Properties)
d) Subscriber Information
e) Local Policy
f) Load status
3.3.3.1.7 Overload Control and Load Balancing
1 according to system overload situation to be possible to overload the appropriate control settings for gNB.
2 new or AMF in overload conditions should support the existing access control.
3.3.3.1.8 SMS over NAS support
1 AMF it must support the SMS over NAS functionality, linked with the SMSF must be implemented by SBI.
2 AMF, considering the support SMS Capability of the terminal must determine whether SMS Service support.
3.3.3.1.9 LTE Interworking Support
1 AMF it must support the Single Registration Mode and Dual Registration Mode.
2 AMF should be considered to determine the behavior of the terminal to Mode Capability, network configuration of the terminal.
SK Telecom
3 AMF is the linkage between the MME via the N26 Interface during Single Mode Registration applied to terminal
4 N26 Interface must support Multi-vendor Interoperability.
3.3.4. Session Management
3.3.4.1 function
1 SMF shall provide a PDU Session creation and management of the terminal.
SMF 2 shall provide the IP address allocation and management of the terminal.
3 interlock between the SMF and the other NF has to be implemented via the SBI.
4 SMF will be able to support the Home Routed and Local Breakout roaming.
5 SMF should support optional User Plane Activation feature.
3.3.4.1.1 QoS and Policy Support
SMF 1 shall be capable of controlling the QoS according to the subscription information received from the UDM, DNN, Slice Type.
SMF 2 shall be capable of controlling the QoS according to a Policy received from the PCF.
3 SMF should provide Flow-based QoS control mechanisms.
4 SMF must support mechanisms to control the Reflective QoS through the User Plane.
5 SMF must be able to support 5QI and QoS parameters defined in the 3GPP standard.
3.3.4.1.2 UPF Selection
1 SMF is to consider the following points should be selected for optimum UPF PDU Session.
a) Terminal position
b) A network configuration (Centralized / Localized)
c) DNN
d) Information Network Slice (Slice and associated Service Properties)
e) Service Continuity Mode
f) Subscriber Information
g) Load status of the UPF
SK Telecom
3.3.4.1.3 Accounting management
1 SMF should provide interworking with the billing system for billing functions.
a) IP terminal by accounting
b) Subscriber-specific billing process
c) Service-specific billing process
d) Star Network Slice accounting
3.3.4.1.4 DNN
1 SMF must provide separate IP Pool UPF and management by DNN.
3.3.4.1.5 Service Continuity
1 SMF should support a wide range of Service Continuity Mode.
2 SMF must be selected by applying the appropriate Mode PDU Session of the terminal according to your requirement Service.
3.3.5 User Plane
3.3.5.1 function
1 UPF should support Transport Level Packet Marking.
2 UPF must support Packet Buffering and Notification.
3 UPF will be able to support the Lawful Interception.
4 proponents should be able to offer if you have specific functions.
3.3.5.1.1 QoS / Policy Enforcement
Policy 1 UPF is applied, such as QoS, charging and Packet Inspection accordance with the received at PCF Policy
Enforcement should be able to perform a function.
2 UPF will be able to support the 5QI and QoS parameters defined in the 3GPP standard.
3 UPF shall support the Flow-based QoS mechanism.
3.3.5.1.2 Traffic Routing
1 UPF will be able to pass through the Tunnel to gNB suitable for Downlink Traffic.
2 UPF will be able to deliver up to DN suitable for Uplink Traffic.
SK Telecom
3 UPF shall support the Flow Mapping for Uplink Traffic.
3.3.5.1.3 Billing Support
1 UPF must support the Traffic Reporting on usage, you must specify whether to provide the following functions related to billing
do.
a) IP / Port per Flow-based accounting
b) Subscriber-specific billing process
c) URL-based accounting
3.3.5.1.4 Other features
Proposed 1 may present the following specific features: Packet processing implemented to merge the UPF, the configuration of
Benefits will be required to present operating scenario and the performance indicators.
a) NAT (from the IP / Destination IP / Port M: N ratio to include the ability to Readdress)
b) Traffic Steering function
c) Firewall
d) DPI
e) DNS
f) Other proponents specific features
3.3.6 Policy Management
3.3.6.1 function
1 PCF should support the following functionality in conjunction with the NF in 5GNC system.
a) Application / Service Flow Detection Control
b) QoS Control
c) Charging Control
d) Policy Negotiation between AF and 5G Core
e) QoS Notification Control
f) UE Policy Control
2 PCF shall be able to deliver the Rule to Control Plane NF in 5GNC.
SK Telecom
3 PCF and the interlocking of the Control Plane NF is to be implemented by SBI.
4 PCF should be linked to the Front End of the UDR.
5 PCF must be able to support roaming.
6, should support the efficient function of the QoS policy management and system parameters (application / delete / search).
a) Integrating QoS policy and system parameters of the entire interlocking SMF management (application / delete / search) to
Provide capacity
b) SMF interlocked across the entire subscriber unit / App Unit / Service (HDV, SMS, MMS etc.) basis / DNN
Service unit Traffic control and management functions (Traffic monitoring, Bandwidth adjustment, PPS adjustment, Session be adjusted, TPS adjustment, etc.)
3.3.7 Subscriber Management
3.3.7.1 function
1 UDM is separated into two detail functions, and then the separated detail function is to be capable of inter-working.
a) UDR (User Data Repository)
b) UDM-FE (UDM Front End)
2 UDM must be able to support roaming, roaming UDM is present in the HPLMN.
3 UDM should provide the linkage function between EPC, proponents should provide the details for this.
3.3.7.1.1 UDR function
1 UDR should support the Save functionality for the following information.
a) User subscription information
b) Policy-related information
2 UDR is to be capable of interlocking with the UDM-FE, FE according to the PCF and UDC structure.
3.3.7.1.2 UDM-FE Function
1 UDM-FE shall provide the following features:
a) Subscriber Information Processing
b) Authentication Information Processing
c) Processing subscriber identifier
SK Telecom
d) Register / mobility management
e) Support SMS Service
3.3.8 NF / Service Discovery
3.3.8.1 function
1 NRF should provide NF / Service Discovery feature.
2 NRF should provide the Authorization function for NF / Service Discovery requests.
3 NRF is to support the NF Service configuration and each NF in 5GNC systems and Network Slice
It must be able to store the information.
4 interlocked with the Control Plane and the NF in the NRF 5GNC system shall be implemented as SBI.
5 NRF is a whole PLMN, depending on the system configuration and setting of the operator, a particular one Slice Network, or
It must be able to provide the Discovery feature of the NF / Service belonging to Network Slice Set.
3.3.9 Network Slice Selection
3.3.9.1 function
1 NSSF shall provide the Network Slice Instance selection function for the UE.
2 UE should be able to decide whether to allow for the requested Network Slice.
You should be able to choose the right AMF or AMF Candidate Set for 3 UE.
4 interlocked with the Control Plane and the NF in the NSSF 5GNC system shall be implemented as SBI.
3.3.10 Service Exposure
3.3.10.1 Function
1 NEF is 5GNC systems and external systems: the Service / Capability Exposure function between AF (eg 3rd Party)
2 NEF must be able to perform the authentication and access control for the external AF Service / Exposure Capability Request
do.
3 NEF must support information to convert between 5GNC system and the external system.
4 interworking between NEF and 5GNC system shall be implemented as SBI.
5 NEF will be able to pass a standardized information from the other NF in 5GNC system to an external system.
SK Telecom
6. The proponent should provide a detailed specification of the Service / Capability NEF offers available.
3.3.11 Storage Function
3.3.11.1 SDSF
1 SDSF should provide standardized information storage capabilities for the NEF Service Exposure Service.
2 SDSF interworking between the different NF are to be implemented in the SBI.
3.3.11.2 UDSF
1 UDSF should provide data storage function of the internal 5GNC system.
2 UDSF interworking between the different NF are to be implemented in the SBI.
3.3.12 SMS Function
3.3.12.1 Function
1 SMSF should provide the SMS over NAS functions.
2 SMSF should provide Lawful Interception functionality.
3 SMSF should provide the accounting function for SMS services.
4 linkage of the SMSF and AMF / UDM should be implemented as SBI.
5 SMSF should provide interworking with our SMS system.
3.3.13 Interface specifications and works
3.3.13.1 Common
1 5GNC system must comply with the 3GPP Release 15 specifications.
Control Plane NF of 2 5GNC should be linked through the SBI.
3 5GNC is linked to 5G AN and N2 / N3 Reference Point, the N2 / N3 Reference Point are MVI
3.3.13.2 IMS interworking
1 5GNC system in conjunction with our IMS network must be able to provide IMS-based voice / video services.
2 NF of 5GNC that work with IMS shall provide the following P-CSCF management.
SK Telecom
a) The P-CSCF Node that work must be input / delete / change.
b) Real-time monitoring P-CSCF interlocked state, and should be capable of generating an abnormal occurrence Notification.
3 NF of 5GNC that works with the IMS P-CSCF shall provide the following group management functions.
a) A plurality of the P-CSCF group containing the P-CSCF Node shall be able to generate at least 64.
b) Node number of P-CSCF, which may include the P-CSCF group is not to be less than 32 Min.
4 NF in 5GNC that work with IMS is required to provide the next P-CSCF allocation.
a) DNN should be able to assign a P-CSCF group at least three or more of each.
b) Must be able to manage a group within the P-CSCF and the load capacity by, and available when the subscriber is assigned a specific P-CSCF
It should be reflected in the capacity.
c) The inactive P-CSCF shall not allocated even if the non-zero available capacity.
It may be able to provide QoS management functions for the IMS to provide audio / video services.
6 P-CSCF to be used if failure to provide Re-address function for the P-CSCF IP address.
7 P-CSCF if a failure occurs on the IMS PDU Session to be used in the Restoration of the CSCF
It must be able to perform Reactivation.
8 different PDU Session ongoing even if you disable active IMS voice / video call should be protected.
9 system, the processing of the outgoing and incoming of the IMS voice / video calls in Traffic overload situation is a priority
Adjustments must be able to handle.
With respect to the operator 10 is set, the terminal provides a Trace function with the SIP / RTP packet dump functions for SIP messages.
3.3.13.3 charging system interworking
1 5GNC system should support integration with Online / Offline Charging capabilities and our billing system.
2 5GNC Online billing system when applied should support the following functionality:
a) 5GNC is in line with a period set in the Session Setup information when the OCS and OCS PDU Session Set
Data Reporting capabilities provide usage information
b) 5GNC unit is set in reporting data amount: The amount of the Uplink / downlink (for example, by Rating Group)
It should be more information.
c) 5GNC shall perform the Policy creation / management and control for the appropriate QoS to support real-time billing
do.
3 Offline billing
SK Telecom
a) NF Offline billing data to generate billing are created in compliance with the Company's accounting standards and interworking
Generating data and be able to transfer the charging data generated and interlocked OFCS.
b) 5GNC system in case of failure (5GNC OFCS disorder or disability) occurs, to pass billing data to the OFCS
Should be provided for (billing data stored a predetermined time, the retransmission function after a failure recovery, etc.): in network configuration (for
redundancy) and RM functions.
3.3.13.4 opening interlocking system
1 UDM shall meet the following requirements in order to support the process of opening the 5G wireless subscribers.
a) The opening of the terminal try 5G: when the location registration in accordance with the UDM (for NAM setting) occurs, the opening system (e.g.
Request message delivery by opening OTA)
2 AUSF shall meet the requirements below to support the authentication of 5G Wireless subscribers.
a) Create new subscribers during, Network authentication of subscribers to 5G UCMS (USIM Card Management System) Key
Lookup request
b) Key viewed from Key UCMS stores in AUSF to 5G for subscriber authentication, management, and through the Key
Support 5G terminal authentication features
3.3.13.5 roaming infrastructure works
1 5GNC system is roaming and interworking infrastructure for the support of 5G Inbound / Outbound roaming and call processing
It must support this feature.
a) AMF / UDM should support the position registration and exchange of information on the roaming terminal.
b) AMF / AUSF must support the authentication procedure and exchange of information on the roaming terminal.
c) SMF / UDM should support the PDU Session creation / management procedures and information exchange.
d) SMF must be able to store subscriber information obtained from the UDM for Inbound roaming terminal.
e) The PCF must support the ability to save the business between the Policy Exchange Policy and received in roaming situations
do.
f) AMF will be able to apply to Local Policy for Inbound roaming terminal.
g) AMF / UDM should be able to support SMS over NAS functionality for roaming terminals.
h) Inbound SMF-UDM interworking between a break in the roaming situation, such as a linkage disconnection between PCF IB in the roaming situation
Presenting disorder happens, scenarios and response measures, and should be supported.
i) When the equipment works with overseas operators, our roaming interworking equipment (eg: Gateway Location Register) and standard
Interface to be able to be linked.
SK Telecom
3.3.13.6 SMS interworking
1 5GNC system in order to provide for our SMS infrastructure: must support the linkage between (eg SMSC), linked
It must present a detailed plan.
2 5GNC system must support the registration process for the SMS.
a) UDM is when a subscriber's SMS Service Capability management requests must pass it to the SMSF.
b) AMF shall deliver the SMS received from the UE to our SMS infrastructure through a SMSF.
3 5GNC system must support the call handling process for SMS.
a) SMSF receives the subscriber information from the UDM, be in association with the SMS infrastructure handles the SMS
Should.
b) Payload SMS is to be sent is encrypted based on the secret key between the terminal and the AMF.
3.3.13.7 PWS (Disaster letter Service) works
1 5GNC Our system is Cell Broadcasting Service to provide the infrastructure for disaster letters Service (for example:
CBSC) and said support interworking, and be able to send emergency text through 5G AN.
3.3.13.8 DPI Function works
1 5GNC subscriber identifying information and subscriber / per service for subscribers Traffic / service Traffic Management
The management policy (Rule Name and AVP, etc.) should be able to provide the DPI Function.
a) 5G when the terminal connection is valid when the subscriber generated by Network Session Slice information, subscriber and DNN
Provide policy information
b) Subscriber Identification, for the identification in the subscriber IP Data Traffic (terminal identifier, terminal IP address, a connection 5GNC
The system identifier, base station identifier) provided
c) Default Policy provides information based on the subscriber products provided by the subscriber opening system
d) Real-time policy update function according to the subscriber data usage and additional services Change
e) 5GNC system identifier, service information, whether the mobile communication network connection using NR.
2 5GNC should support the 3GPP standard-based DPI Function works.
3 UPF is when a failure occurs in a separate DPI, should be able to support the Bypass of the Internet access period.
4 DPI Function can be operated Inline / Offline (packet mirroring) for Data Traffic Inspection.
5 If a separate DPI is being linked to the UPF, UPF will be able to support interworking specification that we require.
SK Telecom
3.3.14 xDR generation
1 5GNC shall be able to generate the billing xDR for reprocessing and VoC response. There is information to xDR
It shall include
a) Traffic information, including information 5 Tuple
b) Terminal identifier and terminal and user information,
3.4 Core EMS
EMS should be developed to meet the operational needs and requirements, we do not provide any other details depends on our level of existing EPC EMS
3.4.1 General Specifications
1 EMS must be able to integrate at least 100 NE (VNF) at the same time, management of at least 5 Network Entity
Set: (eg, MME, SGW, PGW) should be integrated management.
2 system at maximum load conditions should provide an operator matching function.
3 System Standard Time: allows you to set the (UTC Universal Coordinated Time) NTP (Network Time
It shall provide the Protocol) client functionality.
3.4.2 Core EMS General Features
1 is EMS resources required for initialization and operation of all the managed target NE (the H / W is assigned to VNF, etc.), and S / W
Through the shape information and the MMI should be sure to use a commercial relational DBMS as the repository of possible changes or operating parameter
information query.
2 H / W information of 5G Core must provide the operator confirmed features include the following details
a) The serial number (Serial Number), Firmware Version Number and date of application, etc.
3 EMS is S / W equal "NE by the original by using the shape information stored in a commercial relational DBMS of the inner
Mounting also should provide a GUI "to the operator.
4 eNB / Mark gNB the name in Hangul, and shall provide the ability to input.
5 EMS should be available through all the works Data and operational parameters change of the managed target NE, the NE
This configuration change occurs, the information must be reflected in real-time changes in the relational DBMS inside.
SK Telecom
1 EMS is in place to determine the operational status of key resources and S / W of all the NE target blood management in real time
Configuration management features offered in "S / W implemented by NE also GUI" should reflect on.
2 NE operational state of the display can recognize the abnormal operating state of each part using appropriate color immediately
So.
3 when the state transition of critical system resources occurs when the normal call processing did not occur, it
Output Alarm or Fault Message or State Change Message File and displayed by a specific Window (or List View) in the GUI for the fault
monitoring referred back to the same information so that operators are able to recognize them.
4 status is displayed on the "NE S / W implemented by a GUI" shall reflect the actual situation as the NE, State
The maximum allowable time discrepancy is 2 seconds.
May be able to perform all H / W and optionally the diagnostic manual operators to target the S / W Unit features and diagnosis
The results should be reflected in real time GUI.
3.4.2.3 Fault monitoring
1 Fault, depending on the severity of which interfere with the service Critical, Major, Minor and Fault (Warning and
Informational also managed separately in the same class).
2 When Fault is minor, such as the degree of S / W disorder or call processing fails there is no problem in the actual service
Occurs.
3 EMS collects the failure of all the resources and NE Main S / W of the managed target in real time over
Configuration management features offered in "S / W implemented by NE also GUI" should be reflected in a consistent form.
4, when the failure of critical system resources occurs, outputs it to the Alarm Message File, and the same content
It appears in the form of a table for the fault monitoring GUI Window (Alarm List View) allows the operator to recognize it.
5 fault conditions shown in the "Alarm List View" are to be matched exactly to the actual state of the NE, State
The maximum allowable time discrepancy is 2 seconds.
If a large amount of 6 Fault occurred in a short time, it must support Escalation feature to handle this as Alarm.
Threshold values of settings for Fault Alarm Escalation by the operator must be changed to an arbitrary value through the GUI.
7 the operator to hear it to a predefined media Audio File If a predefined occurrence of critical failures
It should recognize the operator. In addition, unlike the assignment and release of these audible alarms per Alarm it should be set and changed by the
operator through the GUI.
If the 8 pre-defined critical failure occurred operator it to the operator to open the Pop Up Window
It must be confirmed (Acknowledge). In addition, unlike the assignment and release of such a visible alarm by Alarm it should be set and
changed by the operator through the GUI.
SK Telecom
9 for each NE to be a failure history between the current fault status and week storage in table form in the internal DBMS
And the operator must be within 3 seconds after the required two faults identified by the GUI.
If the fault repaired 10 generates an Alarm Message release and release and the ability to disable the visible / audible alarm
It is provided, and release Message shall indicate the time of the Message failure.
3.4.2.4 Performance monitoring
EMS 1 is a measurement system that collects performance (Performance Measurement) information of all the managed target NE
The cycle time by automatically collecting and storing in a separate XML File Format loaded in the commercial relational DBMS must be kept inside
the information.
2 by the main EMS is system performance using the measurement information stored in the commercial relational DBMS of the inner
Calculate the (Performance Indicator) PI and shall provide the operator with a GUI, you should be able to present a machine-specific PI.
3 so that the operator can himself set the Threshold value in advance with respect to the desired value by PI NE.
4 is EMS when a PI value that is out of the limits of the Threshold, to convert it to a QoS Alarm event a fault management
By passing a Module to perform and to perform fault management capabilities.
5 Performance Monitoring GUI is to be displayed as a trend graph of a history of at least at least 6 hours PI for each NE on the screen
It should be.
6, each of the NE are based on the actual time you need to create the PM Data and NTP and between them in order to NE
It should be provided, such as time synchronization mechanism.
If there is not transmitted to the EMS 7 PM Data Store and more than 1 time to be transferred when EMS interlocking material
Should.
8 EMS must provide a GUI that can query the value of PI for each of the last 24 hours of the NE via the GUI
do.
9 CN-EMS is a major PM (Performance Measurement) information with any PI by all the managed target NE
It summarizes the information in one hour and must be stored for more than one week to File form. The File form to (eXtensible Markup Language)
XML format and details, we will decide in consultation with the proponent to target the proposed form of the first proponents.
10 PM (including Traffic statistics) and is as a rule for calculating, based on the sum, according to the statistical target entry
The mean value, to be provided with the basic statistics, such as standard deviation, minimum and maximum values.
11 Breakdown Statistics for more than a week to File types are summarized in a time reference for each type of fault and fault areas
It shall be saved. File type is (eXtensible Markup Language) XML.
12. Periodic (Periodic) statistical processing is subject to the requirements of our regular time intervals for each statistical item (1 minute,
5, 15, to be automatically performed for 1 hour, 24 hours).
SK Telecom
13, the operator can be performed manually (On-Demand) to collect specific statistical information on demand, the execution time
Adjustments should be possible and should be confirmed on the GUI On-Demand full collection cycle status and collect statistics and make changes.
14 collection cycle, and whether its collection of one set On-Demand Statistics EMS is even after a reboot
It should be maintained.
15 must be notified about it in case of statistical error, and have the ability to log on to the state
do.
3.4.2.5 Security and Account Management
1 EMS and should provide user authentication for internal DBMS.
2 EMS shall provide at least three steps your rating.
3 registered user of EMS information management manager property registration / view / edit / delete and you should be able to
It must be able to specify permissions for each.
4 should be able to restrict the EMS functions and access privileges for each user of the managed NE.
5 should provide the ability to identify the user currently logged on.
6 shall be provided for control and alarm functions for this if you are logged in as the same user ID.
7 should provide other security features such as password functionality Aging.
3.4.2.6 S / W management
Blood management is the subject of all the NE system via 1 EMS S / W packages and interruption of the run-time Data File Service
It must be able to be downloaded without.
2, the downloading of S / W in the NE to a new is a separate command transition to the Active state at least during the process
The event should be automatically returned to the original state to the previous S / W package.
3 should provide a GUI that can be performed to determine the current S / W version for each NE.
3.4.2.7 Operator Interface Function
The EMS is legitimate from a remote operator located at a remote location via the management of IP-based networks as one network management center
It should be able to run.
2 Client Window screen the managed NE Management Console Direct connection of the subject on the possible or EMS
Or it must provide the same functions.
3 operator using the buttons and menus on a common management tasks can be run without a GUI, a separate type
Should.
SK Telecom
4 menu-driven GUI, as well as the (Command Line Interface) existing CLI format of MMI (Man Machine
Interface) and is also required to provide instruction, CLI must meet sustainability criteria required by the company. (Not supported in support Availability
and Plan presented)
a) It must support the standard command system.
b) Instruction shall provide separate at least create, delete, modify, query, Trace purpose, the Company is required
It can be broken down by add.
c) Command configuration is composed of the following three hierarchies (for example: ○○○ - □□□ - △△△;) should be provided.
• Instruction nine minutes (○○○): creation (CREATE), delete (DELETE), change (CHANGE), Views (RETRIEVE), Trace
• Target Target (△△△): System, DB, CPU, Process, User, statistical areas,
• Target applications (□□□): Information, Configuration, Interface, etc.
• Each of the separator-use "."
• If you need to display a parameter of the instruction after the instruction "," attached to must be added to the parameters, each classification
parameter is "," uses the
• Express one command creates a finished paste; at the end of the command ""
d) The operator must be able to do the same even on all kinds of Shell all MMI command of the CLI format
do.
5 POD of Alarm, Fault message must meet our criteria, as presented below, Alarm, Fault message other
Area should be added in the future to meet the criteria provided by the manufacturer.
a) all the NE shall be based on the severity that interfere with the service of Critical, Major, Minor, Alarm Warning of ratings.
b) Alarm messages must provide detailed information on the breakdown as follows:
• Events (occurring or recovery) time
• Separator for the event (occurrence or recovery)
• Details about fault Description
• Location provides the most detailed information that may have caused the failure
• Providing the most detailed information about the cause of the failure occurred
• Using the same Alarm Code (Number) for the Alarm having the same Description
c) Alarm shall provide at least the following types
• Communication Alarm: periodically (including identification information such as IP, the signal point) connection associated with the interlocking Node
SK Telecom
• Environmental Alarm: Node environmental temperature, power, etc.
• Equipment Alarm: Disk, Network, CPU, Board, Card, etc. Hardware and Related Resource
• Processing Alarm: Software-related, etc. Process, Function, DB
• Such as performance-related Performance Indicator Threshold, Overload: Quality of Service Alarm
• Time Domain Violation: Clock, Time Sync, GPS-related
d) Fault must be provided in the case, such as the degree of slight S / W disorder or call processing fails there is no problem in actual service.
• Call processing-related failure message must be provided immediately generated for the total failure number.
e) Fault message shall provide the details below.
• Event time, Call Information for information, a subscriber check for the classification, service classification information, call processing operation information,
failure cause information, the Information Resource, handover failures Target information used for the call processing
6 must have a hierarchical Hangul HELP function for the operator, and malfunctioning of the fault causes and corrective actions
It must be able to support the HELP function.
7 5G Core each Entity at the same time to make a Trace should be able to see the results and subscriber identification number, chronological or
Call processing must be provided in order to sort by Flow. (GUI recommended)
8 MATRIX or all of the GUI table form can be arranged to filter, in accordance with the information in the screen the properties of Data
It shall provide the capability.
9 EMS client programs are set by the operator environment (for example, GUI screens specific criteria and sorting conditions)
And it shall provide storage.
Most orders are made using a 10 GUI operator is done is done within 3 seconds to see the results
Should.
11 must be set to the following Data Management as, and should be provided for the additional operational Data.
a) APN view, change delete function
b) IP Routing information Query, change, and delete functions
c) The subscriber information inquiry, change, delete function
d) Primary / Secondary billing system information
e) Generating billing and accounting type, a buffer, a storage-related information
f) Session prolonged delete timer (Dedicated Bearer Life Timer)
g) NTP Server search, change, and delete functions
SK Telecom
12 Session Management shall provide the following features:
a) System-wide, and the EPS bearer viewed and deleted allocated per APN
3.4.2.8 Log Management
1 EMS is a separate log of the ASCII format by each NE for all to Data collected from the lower NE
It must maintain at least a month.
a) All the collected PM from the NE (Performance Measurement) Data
b) A variety of statistics calculated from the PM Data Data
c) The NE equipment H / W and S / W status change history
d) NE of Alarm and Fault Message5
e) All unsuccessful call history
f) Stars operator ID login and logout history (including terminal and IP address information)
g) The operator ID by performing CLI Commands history (including the original Command History)
2 EMS is a form of Logs to File for more than a week metabolic history of all commands and their respective operators in ASCII format
3 EMS is the log to a File type of the ASCII format for its S / W recording schedule associated with the operation period of the system
3.4.3 OSS interworking function
3.4.3.1 OSS interlocking Overview
It shall comply with 2.7.3.1.
3.4.3.2 It provides features FM / PM / CM Information
3.4.3.3 Inventory provides information function
3.4.3.4 It provides connection information Function
EMS shall provide the report / reply to all sections of the connection information for all equipment, including the 5G Core equipment that make up the 5G
Core.
SK Telecom
Equipment constituting the 5G Core 1 includes all of the equipment according to the shape presented in Proposed Core 3 5G.
2 and connection information constituting the 5G Core includes all connection section is provided in the Proposed 3.2 and 3.3.
3 OSS can query the connection between both connections of the internal gear and equipment.
4, all connection information will be immediately available from EMS or equipment depending on the quality of OSS. However, the virtual machine
The connection information there is the question of OSS and EMS responds to via MANO in consultation when necessary.
Any changes to the five connection information details, even if the quality of OSS should be provided as soon as OSS. However, virtualization
If the equipment has changed the EMS report can be provided via the MANO with OSS.
6 connection information, by default, be provided in the side devices {A ID, A-side port ID, Z side equipment ID, the port ID} Z form
do.
7. All equipment ID and port ID used in the connection information is provided through the Inventory section 2.7.3.3 provides information function
It should be given ID.
3.4.3.4.1 Provide connection information between devices
Figure 3.4.3.4.1-1: Connection Information configurations
Connections between devices Information shall be provided immediately via EMS depending on the quality of OSS, including the following topics: A side / Z-side port of the
connection information shall be possible nine minutes on the equipment ports.
1 5G Core equipment and port list
2 5G Core cross-connect equipment information on all the access period
3 5G Core and other equipment connected to all cross-sections connected equipment information
5G Core 4 link information between devices and switches
5 5G Core equipment and the other when the connection information provided in the connection section between the equipment difficult, 5G Core equipment-side connection information
(Equipment ID, serial number, port ID, IP address)
6, protocol for an individual connection information: Status (such as Ethernet, MPLS), the main / spare
Other devices with a connection to 5G Core equipment is known as both the LTE RAN equipment, 5G RAN equipment, transmission equipment, IP equipment, the existing Core
equipment.
If 5G Core equipment and the other equipment between the service connection information for the Interface section is difficult, it should provide 5G Core-side information
equipment.
If 5G when the Core virtualization, and provide a virtual appliance, and port information.
SK Telecom
3.4.3.4.2 Equipment provided within the physical connection information
It shall comply with 2.7.3.4.2.
3.4.3.4.3 Provide logical connection information
3.4.3.4.4 Services Connection Information
3.4.3.5 Call Log feature provides real-time
1 Network Element have to generate a Call Log between all the terminals in real time.
a) Call Log should contain at such terminal ID and the Node ID and the network time, to learn which Call Flow
It shall contain the information.
b) Call Log is such packet RTT (Round Trip Time) representing each QCI Traffic transmission and reception by each haptic terminal
It shall contain the information.
c) Call Log shall contain up / down Traffic transmission information.
d) Call Log should include information to distinguish the abnormal arc and Jeong Sangho and, if abnormal heading know the cause
It should be included in the information.
e) Call Log shall contain information that can identify the process Signalling Latency.
3.4.3.6 OSS interlocking interface features
EMS shall provide the information required by 3.4.3.2 ~ 3.4.3.5 with our OSS, it shall provide an interface for this purpose in a manner specified by the
Company.
3.4.3.6.1 FM / PM / CM / IM / connection information interworking
3.4.3.6.2 Real-Time Call Log interworking
Real Time Call Log is to be sent to our servers collect the real-time so that they can be collected from our collection server.
SK Telecom
3.5 Details VNF demand for 5G Core Virtualization
3.5.1. General requirements
1, general-purpose and it should be able to be flexibly changed according to the specific H / W resources.
Support H / W accelerator available from 2 NFVI should be implemented to be used efficiently. (Example: FPGA,
GPU, NPU devices)
Offloading implement functions need to efficiently handle the 3GPP UPF through the acceleration of the 3 resources NFVI
do. (Such as: N-tuple flow based VXLAN, GTP, Checksum, and accounting functions)
4 NFVI-PoP I / NFVI-PoP between Migration city, should be implemented to prevent the disorder service and quality.
5 flexibility to use the NFVI resources and, at the same time should be implemented to prevent service failures and quality deterioration.
6 Control / Management / User Plane classification for processed per Packet Flow of VNF and that
Presenting all the Min / Max / Avg and Jitter (Nanosecond unit), and to be implemented on the basis of each of the real-time processing architecture.
Although the resources of 7 NFVI changes must be implemented so that the service failures and quality deterioration.
8 should be implemented to take advantage of the best-purpose NFVI configured, general and specific H / W resources effectively.
(Eg: Control / Management / User-Plane separate structure)
8 must be able to provide a structure in combination with the structure of the QoS NFVI to support various QoS 3GPP.
10 VNF is and must be implemented as Stateless structure, should take advantage of the NFVI ability to support them.
11 NFVI in failure for my resources shall be no service interruption and loss of quality.
Search for the accelerator 12 through the linkage with NFVI and VIM (e.g., capacity, Capability, QoS, etc.), selection, and
It should be the LCM (Life Cycle Management).
To flexible use of the resources of NFVI 13, it should be implemented in the Extension Agent and heterogeneous VIM.
14 proposer must present a structure and a traffic path for the VNF consisting VNFC detail, for each VNFC
Interface should support the (virtual IP / Port) architecture.
15 proponents VNF / VNFC is to support a variety of Control / Management / User Plane traffic processing
Internal / External Interface must support the (virtual IP / Port), should be able to get control of the various Open Iterface. (Eg:
Openflow standard 1.5+)
16 proposer VNF / internal traffic path VNFC structure for performance, redundancy, and reliability: (for example, session-based LB)
It should be light weight.
SK Telecom
17 proposer VNF / VNFC is based on the Flow-based defined in 3GPP for performance, redundancy, and reliability
And to utilize the Virtual Switch / Router function of NFVI, to reflect the characteristics of NFVI should optimize the traffic route structure.
18 proposer fast E2E services: implementation should the capacity of VNF / VNFC a minimum amount in order (for example, Ins, Term)
And, at the same time, the migration should be implemented to prevent service failures and quality deterioration.
3.5.2 VNF Interface Structure
1 VNF has multiple physical Interface in order to support the flexible Scale-In / Out no expression unit Pharmaceuticals
It should be utilized. In addition, the Interface VNFC for external link to be configured separately, corresponding VNFC shall be a
Stateless structure.
Interface 2 is VNFC of Scale / In / Out is be possible structure, a plurality of Physical Interface and a plurality
In the Interface VNFC structure it must be capable of handling a normal call.
3 Interface when VNFC consist of a redundant structure (ACT / STBY) All non-Active structure ACT / TSBY
Virtual IP must support structure between.
Interface 4 each are to have different values as will be appreciated from the IP Network, service of VNF
IP should be able to use a separate IP IP or non-IP Interface VNFC physical Interface.
5 OVS etc. Network and VNF process for the external-internal-processing VNF when utilize a Virtual Switch
Network should be clearly separated into logical for, and should be a separate reference to the Interface Unit.
3.5.3 VNF Traffic Load-Balancing Structure
One. 3.5.2 Interface according to clause VNF structure, VNF is that the clarity Interface VNFC and call processing VNFC to be configured.
2. Interface VNFC is for the call to process VNFC must be able to perform a Traffic Load-Balancing, manage and call processing information
only allocated a Session for an incoming call does not involve offering the role of Load-Balancing Function and Interface focused do.
3. Interface VNFC should be possible if the VNF Destination IP services IP Routing and call handling.
4. Interface Host VNFC is due to a physical disorder such as a call to a different Network path even when the inlet and the treatment should be possible,
the call processing VNFC must support the normal call processing, even if the inlet to another path.
3.5.4 VNF Traffic Management
One. VNF should be available by the Traffic Management and Subscriber Service Flow.
SK Telecom
2. Services for Network Flow Control units VNF can distinguish Traffic Flow per unit to its management
The information that must be provided, including the Network Traffic.
3.6 5G Core Competitiveness
1 Proposed Describe the advantages of the product compared to other manufacturers.
a) TCO Saving (CapEx / OpEx)
b) Processing Capacity (Throughput, etc.)
c) Services / system reliability / stability / scalability
d) Operational efficiency (automation)
e) Support for Telco Cloud Evolution
f) MVI Support
g) PKG development / support (travel time, the applicable number, etc.)
2 Please indicate the quantitative effect when CP / UP Severability.
3:00 UP forward-deployed provided by the MEC Please indicate the available services and platforms.
SK Telecom
4 Virtualization Management and Orchestration
4.1 Overview
ETSI NFV is to start a standardization group Release-1 (February 2013), Release-2 (January 2015), Release-3 (September 2016, February) activities
configured for the established network virtualization industry standard multi underway to develop industry standards to provide interoperability of vendor
environment.
We ETSI NFV holds virtualization Management and Orchestration (hereinafter MANO) solutions that comply with the standard, and is considered a
top priority of our evolution and Interlocking MANO in the commercialization of 5G.
However, 5G RAN Virtualization and End-to-End Network Slicing support and the evolution, standardization and related functions, the development of virtualization technology
in terms 3GPP specifications is underway, and specifies the general requirements of NFV MANO due to these changes, MANO solutions that support the needs and
differentiating features may also be considered further.
The present section first and Technology (Chapter 4.2), the requirements that the proponents of VNF must support in order to work with our NFV MANO,
proponents shall answer a counter Applied together with the description. Overall (Section 4.3), followed by technical requirements of 5G MANO Technology and
answers about the interlocking needs, proponents can only answer with differentiated features and whether a proponent of information technology needs.
4.2 Details SKT NFV MANO interlocking requirements
4.2.1 SKT NFV MANO Architecture
1 Our NFV MANO structure has been defined to comply and extend NFV ETSI standards, Generic VNFM (hereinafter
'G-VNFM'), Common VIM (hereinafter 'C-VIM'), Local NFV Orchestrator (hereinafter 'Local NFVO'), E2E Network Orchestrator (hereinafter
'E2ENO'), SDN Orchestrator (hereinafter 'SDNO'), Transport Intelligent It consists Orchestrator (hereinafter 'TIO').
SK Telecom
Service Orchestration
Service Adaptation Service Service Exposure

(PCRF / U.Key I / F, Design Portal) Life-Cycle Mgmt. (Open API)
End-to-end Network Orchestration
Catalog (Local NS, End-to-end NS

OSS / BSS Interconnection
PNF / VNF, TIO) Life-Cycle Mgmt.
Local NFVO
Local NFV Orchestrator Local TIO (T-SDN)
NFV Orchestrator
Local NS Local NS Local NS SDN
Life-Cycle Mgmt. Assurance Dashboard Orchestrator
Generic VNFM Common VIM

EMS IP / MPLS (L3)
(PNF, (L1-2) PTN (L2)
VNF) Virtualized Functions Physical / Virtual Infra. (L1) POTN
ROADM OTN
Edge
Core Functions Edge DC Central DC (L0)
Functions
Figure 4.2.1-1 SKT NFV Architecture
2 is a Local NFVO, G-VNFM, C-VIM built into each unit of national history and unified management of virtual resources and services,
E2E NO manages integrated virtual resources and services of the Multi-DC environment as the interlock Local NFVO, T-SDN.
4.2.2 Generic VNFM requirements linked requirements
4.2.2.1 Indexation
VNF of the first proposer must support the G-VNFM interworking specifications SKT is provided, linked to the scheme G-VNFM
You can choose by way of VNF Agent or the REST API Interface mode, which is automatically installed on the VM.
EMS 2 proponent must support the G-VNFM linkage specification that SKT is present, indexation is REST API
Interface is the way.
4.2.2.2 VNF Lifecycle Management
VNF and EMS of one proposer should provide the following functions to perform on the VNF Lifecycle Event handling such requests
do.
Event The VNF / EMS Action
Instantiate VNF Application Package Installation, Configuration and Service completed operations
Scale-out VM creation and reflects additional services
Scale-in Remove from the VM service to be deleted Quarantine and VNF Instance Configuration shape
SK Telecom
Terminate VNF Instance End, and Delete
Evacuate VM installed on other Host, VNF App. Pkg. Installation, prior to service state repair and service operations
Reinstantiate VM regeneration, VNF App. Pkg installed, the previous state of repair services, and service operations
Forced Scale-in The abnormal condition VM service isolation and removal from VNF Instance Config VNF
Apply forwarded information to the VNF Instance Configuration
2 EMS will be able to receive a Notification for a new generation and Lifecycle Change of VNF Instance
do. And, to be able to register and renew your subscription to the G-VNFM for this purpose.
3 is a list of the EMS to manage VNF Instance and detailed information on the individual VNF Instance to G-VNFM
It must be able to look up.
4.2.2.3 VNF Configuration Management
1 VNF is defined in the Item VNFD for Configuration can not be confirmed in writing VNFD time, and create
See Item stars Value in each event, the G-VNFM pass the time and shall perform the configuration of the VNF
Instance.
2 EMS is the Edit Configuration of the VNF Instance in operation with respect to the defined Item VNFD
In order to be able to pass the request to the G-VNFM.
3 VNF Instance in operation is a change in the G-VNFM request with respect to the defined Item Value of VNFD
Received, it must be able to process.
4.2.2.4 VNF Information Management
The EMS 1 is for the Notification When the HA state of the VNFC Instance constituting the modified VNF
It must be delivered to the G-VNFM.
2 EMS shall provide a Subscription Notification function for transmission on the change VNFC HA state.
Subscription shall be possible to process update request before the new registration and expiration, Notification is to be delivered to a
Consumer registered Callback from URI Subscription.
3 VNF should support the REST API specification to view the real-time status information about VNFC.
4 VNF system Resource Usage information for Guest OS (real time for the CPU, Memory, Disk, Network
It should support the REST API specification to view the usage information).
4.2.2.5 VNF Fault Management
EMS should support the Action for the Event below.
Event EMS in Action
VNF Instance failure, failure information (failure Identifier, occur time, type, grade, cause, location and destination, the outside
Passing the Notification to the G-VNFM for details)
Off VNF Instance failure Notification to the pass the G-VNFM release information on disability
SK Telecom
always Subscription Notification feature provides for the transfer of the failure and release of VNF
Instance
- Subscription supports new registration and expiration update request before processing
- Notification is delivered to the Consumer Callback URI registered in the Subscription
always Received support for the failure of NFVI and release the relevant Notification concerning VNF Instance
always Support REST API standard that can query all the fault information that is currently occurring in the VNF
Instance
4.2.2.6 VNF Performance Management
EMS 1 is configured by the Run-time value for the VNF Indicator items described in the G-VNFD VNFM
Should notify and should give basically supports one minute to Notify. And it shall provide the capability for the
Subscription Notification.
2 EMS shall provide a Subscription Notification function for transmission on the VNF indicator.
Subscription shall be possible to process update request before the new registration and expiration, Notification is to be delivered to a
Consumer registered Callback from URI Subscription.
Value of VNF Indicator EMS to 3 is passed is Scale (auto / manual) and TCA (cross threshold alarm)
It should be used to determine the basis for the Policy.
4 EMS should support the REST API specifications that can be viewed real-time information on the Value VNF Indicator.
4.2.2.7 VNF Package Management
1 VNF is to provide the package of the VNF VNFD, Guest OS Image, VNF Application file.
2, the configuration information of VNFD VNFC, network configuration of VNF, external link information, information Deployment flavor, VNF
indicator information, such as Item Information, Auto-scale / TCA Policy Information must be technology for the Configuration.
3 Guest OS Image will be a format which can be registered in a Openstack Image and, OS manufacturer
Use the official image for the VM provided by, or with the Cloud-init, etc. should be made to enable as an image for the Cloud.
4 VNF application file are in separate separately from the Guest OS Image, using a Guest OS Image
It recommends a structure that can be installed on the VNF application After you create a VM.
5 VNF package Update the VNF / VNFC is generating a VNF / VNFC Instance or create existing
It shall comprise the files and information that can be (Version Upgrade).
6 VNF is an updated way not affect the initial installation and service of VNF VNF package of services
SK Telecom
4.2.3 Details Common VIM works requirements
4.2.3.1 Indexation
VNF of the first proposer must support the C-VIM interworking specifications SKT is provided, interlocked manner is by C-VIM
You can choose one way or Zabbix Agent REST API Interface mode, which is automatically installed on the VM.
4.2.3.2 Virtual Resource Monitoring
1 VNF must provide this information in accordance with the case of failure of the virtual resources linked to the C-VIM specifications:
2 VNF shall provide in accordance with the periodic performance of the virtual resource to the C-VIM interworking specifications of.
4.2.4 Details Local NFVO and E2E NO linkage requirements
4.2.4.1 Indexation
1 Local NFVO is disposed DC or DC Cluster distributed unit, through the G-and C-VNFM VIM interworking unit DC
NFV MANO perform the function. The proponent must provide 5G VNF so that Lifecycle Management and Assurance of VNF / NS of
Local NFVO center can be performed.
2 NFV for the automation of the MANO-based Lifecycle Management services outside our perspective, our proposer
The Local NFVO, E2E NO and the host system must provide the NBI (North Bound Interface) to the On-Demand setting of 5G
VNF.
4.2.4.2 VNF / NS Lifecycle Management
1 Proposed shall show the VNF / NS Descriptor of TOSCA base for 5G VNF design.
2 Proponents and schedule for, so VNF Descriptor-based design of our proposed VNF Descriptor Specification
It should provide the interlocking scheme.
3 proposer Local / Group Affinity Rule and Anti-Affinity VNFD for the NFV Infra resources automatically assigned
It must show the Rule.
4 proposer for NFV Infra resources allocated automatically, VNF is going to take advantage of OpenStack Extra Spec Category,
Presented Prefix, Option, Value, and should provide a VNF Descriptor reflect this.
a) Category types: CPU limits, Watchdog behavior, CPU topology, Large page allocation, PCI pass through, Bandwidth Limit
etc.
5. The proponent must then VNF Onboarding, must present a Pre-Instantiation information needed to set up a Run-Time
Six proponents and schedule for the city, Pre Instantiation The proposed design based our Pre-Instantiation Specification
It should provide the interlocking scheme.
SK Telecom
7 proponent for the end-to-end service automation associated with it when Lifecycle Management of specific VNF, services
It must present a protocol / standard of the Day-N Configuration Plan of VNF being driven and NBI.
4.2.4.3 VNF / NS Assurance
1 Proposed describes a VNF Fault information to be delivered to VNFM, and from this point of view in the Local NFVO in NS
Collected should provide the necessary information to identify the VNF Fault.
2 MANO proponents that upon receiving information from the VNF Fault Local NFVO, required for VNF Auto Recovery
It must present an action.
3. Proponents describe the VNF Performance information is delivered to VNFM, and from the standpoint Local Network Service
It should provide the information necessary to identify the VNF Fault collected from NFVO.
4 proposer upon receiving information from the VNF Performance Local NFVO, Seamless required for service
It should provide the MANO operation.
4.2.5 Details DC SDN linkage requirements
4.2.5.1 DC SDN control range
DC SDN is Telco DC of the physical / virtual Network and configuration / control, specifically Telco DC and within Leaf / physical Network of Underlay Networking
consisting of the Spine, configuring a logical connection between the DC within a VM (eg: Service Chaining) the for and configuration / control of the virtual
Network Overlay Networking.
Management functions of the DC SDN is composed of my SDN Application MANO is, the SDN Controller controls the Telco DC of the physical / virtual device and a
Network Resource based on the configuration policies SDN Application. Further, there is provided an integrated information (NS / VNF and physical resource / Network
liver) through interworking between the NBI E2ENO.
Details for the SDN-based NETWORK control and the structure of the Interface VNF be configured for SDN-based controlled environment, whereby to request is
described in Chapter 3.5.2 - 3.5.4.
4.2.6 Details TIO works requirements
SKT Network Transport means, such as wired Network Fronthaul, Backhaul, IP Backbone & Optical Transport Network. SKT
Transport Network is composed Network equipment of Multi-layer, Multi-vendor, Multi-domain.
1 Transport Infra. Orchestrator (hereinafter TIO) is integrated, and control these Transport Network, further
Including Edge / Core DC within the L2 / L3 switch aggregation Multi-DC Network Control and Transport-5G RAN-to-Core performs Dynamic
Network Connection Control.
2. To this end, 5G RAN / Core Infra. Network Element or may be interlock between SDN Controller / EMS and TIO
And a, End-to-End Network Transport Network Slicing Slicing each 5G Network Slice to be implemented through the TIO.
SK Telecom
a) 5G RAN / Core Infra. When the My Network Element directly with TIO Open Interface (NETCONF,
It should provide RESTCONF, gRPC etc.).
b) 5G RAN / Core Infra. EMS / Controller and the TIO when directly linked Open API (RESTCONF, REST API *
To provide a w / Notification, gRPC etc.).
c) Configuration and Operation provides information and receive Status information or change information in real time
It shall provide for the Notification feature. (For example, if the REST API requires present, there is no separate room Notification)
d) In addition to the Proprietary Open API it should support the standardized Open API, including IEEE / IETF / 3GPP.
Three interlocking features below are required for this purpose.
a) SKT Transport Network within a Network Element 5G RAN / Core Infra connected to (switches, transmission equipment).
My Network Element (server equipment) Physical Port Information, Physical / Logical Link connection information and Routing / Forwarding
information or change information
b) Routing / Forwarding Information and Control
c) Tunneling information and control
d) Interface information and control
e) ACL information and control
f) Flow (including L2 / L3 Service) information and control
g) Flow over Tunnel mapping information and control
4.3 5G MANO Requirements
4.3.1. Details ETSI NFV MANO basic requirements
1 must meet the requirements ETSI NFV Release 1
a) MANO the proposer Europe Telecommunications Standards Institute (hereinafter ETSI) NFV Industry
Specified in ETSI GS NFV 002 V1.1.1 (2013-10) of the Specification Groups (hereinafter ISG) to be based on the Reference
Architectural Framework.
b) The proponents of the ETSI MANO NFV Reference Architecture in MANO Domain and another Domain (example: VNF,
To support Interface with NFVI, etc.) and should support the MVI for the Interface.
c) The proponents of the MANO ETSI GS NFV 001 V1.1.1 The Proof-of-Concept (hereinafter referred to ETSI (2013-10)
NFV PoC) should be able to support all of them.
d) MANO proponents are to satisfy the requirements referred to in ETSI GS NFV 004 V1.1.1 (2013-10).
SK Telecom
2 ETSI NFV Release 2 should meet the requirements.
Release No. Related Documents Specification
Virtualization acceleration technology and related standards VNF Interface: NFV-IFA 002 v2.1.1 MANO-related
specifications:
ETSI GS NFV-IFA004, ETSI GS NFV-IFA005, ETSI GS NFV-IFA006, ETSI GS NFVIFA007, ETSI GS
NFV-IFA008, ETSI GS NFV-IFA010, ETSI GS NFV-IFA011, ETSI GS NFV-IFA013, ETSI GS NFV- IFA014, IFA-022,
IFA-028, ETSI GS NFV-REL009, ETSI GS NFV-TST009
TOSCA Protocol and Data Model Specification includes:
ETSI DGS NFV-SOL001, ETSI DGS NFV-SOL002, ETSI DGS NFV-SOL003, ETSI DGS NFV-SOL004, ETSI DGS
NFV-SOL005 MANO performance measurement specifications: ETSI DGS NFV-IFA027 MANO Test Specifications and
Features: ETSI GS NFV-TST007
4.3.2 Details 5G Network Slicing requirements
1, which is defined in the 3GPP SA2 / SA5 End-to-End 5G Network Slice and thus for efficient Lifecycle
Management must support structure.
a) 5G Network of Slice Data Model, Lifecycle Management structure and manner of operation (for example: Onboarding, Installation,
The Termination, Scale, Update, Upgrade, Self-healing, etc.) should be supported.
b) 5G Network Slicing and NFVI, VNF, VIM, VNFM specific to NetworkSlice-as-a-Service provided,
Orchestrator to support the structure and functions (policy, billing, authentication, security, etc.) and must provide an implementation plan for this.
c) It should support the setting for the network operators within the 5G Network Slice Selection, and specific implementation plan
It must give way.
2 Network Slice of units and PI KPI lists, and real-time Live / Historical, Analytical statistics support, and performance (up to
The number of concurrent sessions, should support the co-Throughput, etc.) Monitoring and Alarm.
a) Configuration of Network Slice, resource usage, and Lifecycle Management related to visualization
It should provide specific and intuitive operation User Interface (CLI and GUI).
3 Disability association between Network Slice should support (isolation, Trace) and security.
Between 4 and operators need to support interworking between MANO for Multi-domain Network Slice works, concrete
It should provide the interlocking plan and implementation.
It must provide an efficient and differentiated capabilities for Service of Tuesday 5 Network Slice, specific for them
It must present a plan and implementation.
SK Telecom
Details 4.3.3 NFV open platform requirements
One Proposed by the VIM it should provide a H / W supplier, irrespective of the Model H / W interlock / administrative functions.
a) Must support the management of the included universal H / W, Open / Disaggregated H / W such as OCP, shall not redistribute the package according
to the H / W changes.
2 VIM is a proponent of the integrated Multi-VIM environment, configuration, and support should be available.
3 There should be no change in functionality and Upgrade during operation and service interruptions, and for presenting a detailed plan Upgrade
shall.
4 VIM, shall provide real time status monitoring and recovery functions for the management resources of the VIM.
a) There should be no system changes and additional packages distributed according to the system and monitored Metric change.
b) VIM proponents should be designed to be linked with external monitoring solutions.
c) Required to support real-time monitoring of virtualization S / W and H / W accelerator.
d) It should support the real-time Fault Detection and Automatic Recovery.
5 S / W (DPDK, SRIOV, etc.) (such as FPGA, GPU) H / W based virtualization should support the management of the acceleration.
6 Should support the linkage and management of real-time for 5G RAN Virtualization Hypervisor.
7 In the case of OpenStack, based on the Pika or later and should be provided for compatibility with earlier versions.
8 And contribute to the OpenStack Global Upstream be available, it should be provided if the contributions history.
9 The contribution to the Open Platform for NFV (OPNFV) must be available and must be presented if the contribution histories.
10 We shall provide the specifications and external link Interface for VNFM and NFVO association, our works standards
It shall be accepted.
11 It must support IPv4 / IPv6, should support the security function for intrusion and attack.
12 Proponents must present a specific plan of only proponent for improving the future of VIM features, performance and reliability.
SK Telecom
5 NFV Infrastructure
5.1 General Specifications
5.1.1 mechanical specifications
One The proponent must comply with the technical standards of telecommunications equipment and matters not specified in the technical standards
Based on the Telcordia NEBS (Network Equipment Building Standard) Level 3 criteria mechanically, to comply with the environmental conditions.
2 Infrastructure components are installed, capacity and functionality changes to the structure of the Module screen Disaggregation should facilitate the
And it shall be so constructed that the H / W structure changes upon impact on the S / W can be minimized.
3 H / W component of Infrastructure by the operating personnel easy access troubleshooting must be enabled and easy to maintain
do.
4 The following conditions with respect to the vibration can not be avoided during transport and relocation of the Unit or part of the equipment and the impact
a) It should not affect such operations and perform functions.
b) It should not adversely affect such significant change or damage to the exterior parts, painting of the Unit of the respective configuration.
5 Installation and off of equipment within the Board Unit, shall satisfy the following conditions related to insulation.
a) It is capable of being installed and dismantled parts such as screws for securing the Board within 5 seconds, and the wear caused by the installation and dismantling
equipment such as driver should not happen.
b) Isolated Module Board within the power supply unit has to be protected from wear by friction.
6 Virtualized infrastructure and to satisfy the electrical and mechanical properties required for air communication equipment, the required environment
And in the operating condition to be the rated value is determined so that even a high degree of reliability can be maintained for long periods of time.
7 Virtualization infrastructure in accordance with certain rules must be over 10 years of continuous mass production and, Module / per Unit
Easy to learn and have a label or marker. It should also be a display form of a Unit LED implemented in consideration of the operational
efficiency.
8 And within an acceptable error range can be replaced by other components, affect the function and performance of the system replacement
It should not, and must be notified in advance.
9 Depending on the degradation of the components should provide an alternative if a degradation of the system.
10 It shall satisfy the following conditions: FAN for preventing overheating of a virtualized infrastructure, and cabling
It must be a structure which can easily be laid in the shortest distance.
SK Telecom
a) FAN must have been effectively installed and attached.
b) Internal temperature of the product according to the FAN is to maintain the proper temperature capable of normal operation, to be able to present the reference
temperature.
c) According to alarm FAN failure to operators should be provided in real time.
d) Even when the FAN fault should be for normal operation of a certain period of time, you should be able to present a guaranteed time.
11 All cables without mechanical damage even in the worst conditions or any cause during operation
It shall be affected by induced noise from the outside.
5.1.2 Electrical Specifications
One AC power system overvoltage / overcurrent protection, the requirements of the AC ground as the AC voltage and AC power plants
To comply with the standards for equipment or the like device.
2 DC power supply system should be Modular forms to facilitate the increase of the size of the virtual infrastructure,
Normally, and supplies power to a rectifier, a need is powered by a battery when the commercial power source the power failure and be able to recharge the battery
when the commercial power source is recovered.
3 The power supply should provide redundant power to operate Load Sharing, each power is to be supplied to all the Load
It should be.
4 The power supply unit and ensure the reliability of the system, including overvoltage / overcurrent protection, in case of failure
Rapidly detected and to be designed in a structure that can be replaced.
5 To be presented to the leakage current and resistance of the grounding system.
6 Next to the to satisfy the allowable value based on the power and voltage.
division Standard voltage Voltage range Remarks
DC power supply - 48V - 43.5 ~ -54V - 48V ± 10%
220V (± 10% decrease) 60Hz

AC power supply 220V (60Hz)
(± 5% decrease)
7 It shall comply with the following instantaneous voltage and over-voltage tolerance.
8 Instantaneous voltage tolerance: -43.5V, less than 1 second
9 Transient Voltage tolerance: -60V, less than 0.2 seconds
10 Can accommodate up to DC Ripple shall meet the following criteria:
Noise Rating RMS PP Remarks
2mV or less Less than 100mV Less than 200mV
11 The evaluation noise contained in the direct-current power supply, peak value, effective value is to comply with the following criteria.
SK Telecom
Noise Rating Peak Rms Remarks
Less than 200mV Less than 100mV

2mVrms less
(10Hz ~ 14MHz) (10Hz ~ 10MHz)
5.1.3 Environmental Specifications
One In the following temperature and humidity conditions it should be able to stabilize operations.
2 Temperature and humidity measuring location: 1.2m height from the bottom surface, more than 0.4m from a position away from the device
It shall be measured.
3 Standard temperature and humidity threshold
Standard temperature Standard relative humidity
25 ℃ 50%
4 Nominal tolerance, short-term tolerance
division Temperature Range The relative humidity range
Nominal tolerance 16 ~ 28 ℃ 30-70%
Short-term tolerance 2 ~ 50 ℃ 20-80%
5 It shall meet the following criteria: low temperature / high temperature operation test of the short-term tolerance.
6 Test for a long time at a high temperature in the system is in Active state should be able to normal operation for more than 24 hours.
7 Low temperature, and interfere with the stable operation of the system should not even at a high temperature condition, there are no changes in system properties
do.
8 The mechanism of deformation and damage due to the following vibration and free conditions, to comply with the standard characteristics.
division Vibration values Vibration frequency range Sweep Rate standard
Operating condition (operating condition) 0.1 G 5 ~ 100 Hz 0.1 oct / min GR-63-Core
1.1 G 9 ~ 200 Hz 0.1 oct / min GR-63-Core

Transport conditions (in package)
1.53 G 200 ~ 500 Hz 0.25 oct / min GR-63-Core
9 Virtualized infrastructure RRL Communications Commission Notice "technology for the stability and reliability of telecommunications equipment
Standards "to meet the requirements and be certified, Modified Mercalli Intensity Scale earthquake of magnitude 5-8 Conditions shall be free of mechanical
deformation and damage.
10 Virtualized infrastructure EMC registration rules, including the unnecessary radiation noise limits and voltage limits
It shall be met and shall submit to the EMC (Electro Magnetic Compatibility) test reports from the certification authority.
EMC shall include EMI (Electro Magnetic Interference) and EMS (Electro Magnetic Susceptibility).
11 Magnetic field strength permitted
SK Telecom
division Field strength The magnetic field strength
Allow strength 127dB ~ • V / m 127dB ~ • A / m
12 Unnecessary radiation limit
Limit
Frequency (MHz) Measuring the distance (m)
• V/m 127dB ~ • V
30-88 30 30 29.5
88-216 30 50 34.0
210-1000 30 70 36.9
13 Noise voltage limit
Limit
Frequency (MHz)
•V dB ~ • V
0.45 ~ 1.6 1000 60
1.6 to 30 3000 69.5
14 So as to minimize the effect on the electrostatic discharge and be provided with ESD-Wrist Strap or Wire-Wrap
do.
15 In relation to transport packaging it shall comply with the following conditions:
a) it must be rigid to avoid being influenced by the transport of equipment, storage and transport Temperature, humidity, static electricity shock, such as
unexpected progress and invasive and safe environment without packaging.
b) the material of the room packing material is a poly ethylene film (having a thickness of 0.05mm or greater), an aluminum kraft paper, or an equivalent should be at least
the material, and the buffer should be at least the foamed styrofoam, sponge, cotton wood or equivalent material.
c) electrostatic, friction or induction furnace proof packaging material is to be equal to or more vinyl or electrostatic shielding material.
16 So to choose a method that do not affect the packaging systems Conveyor systems can be delivered to the installation site system
It shall be and shall accept them if there are any of our needs.
5.2 virtualization requirements
5.2.1 Details ETSI NFV and NFV open platform requirements
1 must meet the requirements ETSI NFV Release 1/2/3
Release No. Related Documents Specification
One NFVI is an Architectural Reference described in ETSI GS NFV 002 V1.1.1 (2013-10)
SK Telecom
It shall be based on the Framework
Interface must support with: (VNF, MANO such example) is NFVI ETSI NFV Reference Architecture in
the other Domain Domain NFVI
NFVI shall be able to support all of the Proof-of-Concept (hereinafter ETSI NFV PoC) mentioned ETSI GS
NFV 001 V1.1.1 (2013-10).
NFVI is to comply with the requirements mentioned in the ETSI GS NFV 004 V1.1.1 (2013-10).
Virtualization acceleration and VNF Interface relevant part: NFV-IFA 002 v2.1.1 vSwitch Benchmarking
specification shall show the results of the Use Case in (ETSI GS NFV-IFA 003 v2.1.1).
It should be able to provide Metric described in NFVI performance measurement standard (ETSI GS NFV-TST 008
v2.1.1).
NFVI specifications and features support:
ETSI GS NFV-EVE008, ETSI GS NFV-IFA018, ETSI GS NFV-IFA019, ETSI GS NFVIFA029, ETSI GS
3 NFV-REL009, ETSI GS NFV-TST009
NFV ETSI Release 3 NFVI Interface: to implement the architecture and protocol, the message format, and an API for (for
example, such as Vn-Nf, Nf-Vi, NI-Ha)
2 must meet the Open Platform for NFV (OPNFV) requirements
a) it must support the verification according to the ETSI OPNFV based NFV TST standard. It must present the level of automation for the Test Environment
Configuration and Verification
b) VIM and NFVI layers are to be implemented in consideration of interoperability of the Multi-Vendor, it should provide Interoperability and
Validation Test, etc. Continuous Integration system for Multi-vendor / Version (NFVI).
c) VIM and the Lifecycle Management for the Component should provide options that can be performed independently, it should enable automatic
recovery in the event of a problem with the Component.
d) setting a possible shape of the Deployment VIM as a profile, and to be based on this as can be installed in the all the
Component is automatically VIM.
e) VIM and the configuration of HA should be possible, and the extension of service continuity HA cluster should be possible to meet the capacity and
stability.
5.2.2 Virtualization Acceleration Technology
One 5G is a general-purpose accelerator to be used for resource efficiency and performance increase of VNF / VNFC.
2 In 1U and 2U servers universal presenting H / W accelerator, and provide and support.
3 Must be present in consideration of the kind and the shape of the accelerator, NFV ETSI standard based Lifecycle Management,
Use should be implemented as possible (Open Library and API, etc.) and control support form.
SK Telecom
4 Type / structure of the H / W accelerator: the function Offload technology through (for example, a general-purpose GPU, such as FPGA and Embedded)
5 And NFVI must support the use of resources over the set on / off and utilization of the H / W accelerator, at the same time
Service failure and should be implemented to prevent the loss of quality.
6 Should continue to support the change / addition of the H / W accelerator, when service failure and there is no loss of quality
It should support the structure.
5.2.3 NFVI-PoP (Point-of-Presence)
1 NFVI-PoP within, NFVI-PoP between Compute, Storage, a structure capable of cost-effective extension of the Network
It should have. (Eg: OCP, including RSD Support )
2, cost-effective upgrade of Host and Host OS, it should be possible to extend security and management.
Resources through such Pinning / EPA / Scheduler for a resource in the Host to configure the 3 PoP efficiently
It must be able to operate.
4 VNF / VNFC that can communicate, control and control of the Control / Data / Management Plane traffic of
It should support the virtual switch.
5, the virtual switch is a virtual resource to the physical resource in consideration of the physical - be implemented in a map the logical I / F structure
do.
6, the virtual switch to reflect the Host OS, Kernel structure so that service failures and degradation of VNF / VNFC
It should be implemented to have evolved independently.
7 and a virtual switch to support and present the protocol defined by various IETF and 3GPP, 5G VNF / VNF C
It should be implemented to function Extension to increase their performance.
8 virtual switch Underlay flood of VNF / VNFC through support to:: (VxLAN example) (for example, L2) and Overlay
And it should be implemented to prevent the loss of quality.
9, the virtual switch is active manner (for example, supported by the vProbe VNF: NETWORK Slicing SLA, 5G service, QCI and
It must be able to measure the QoS Parameter).
10, a virtual switch Passive methods supported by the vProbe VNF: support (such as Full, Sampling, Flow separately)
Should.
11, the virtual switch should be supported to receive control from vProbe VNF, various I / F (for example, physical,
It should be implemented to support the probing for the virtual port).
12, the virtual switch is a particular collection of Parameter vProbe VNF, statistical processing, Filtering, Correlation, Enrichment, etc.
To allow the creation and deletion functions should be given the NBI (REST API) specification.
13, a virtual switch during Probing, sophisticated TimeStamping (in ns) to minimize each packet by the error range
Give way and should be supported.
SK Telecom
14, a virtual switch to use a general-purpose accelerator including S / W and H / W to optimize the performance
It should be implemented.
15 services for disability and quality assurance, etc. Considering the distributed HA Storage must be able to support the use special equipment
do.
Shall be available 16 vPOD / vDC configuration, it should provide a description of the PIM / BMaaS to manage them
do
17 The END TO END Network Slicing implementation point of view is different, and per-service QoS Priority and Isolation in
Support should be provided to ensure the Host / Virtualization. (Example: Hypervisor level of the Resource Allocation / Pinning /
Prioritization, Scheduling, Real Time Hypervisor etc.)
5.2.4 NFVI-Fabric
One NFVI-Fabric Networking Protocol should support a standard, such as Ethernet, IP, such as 3GPP / IEEE / IETF.
2 Network Element constituting NFVI-Fabric is a structure which is controlled by the SDN Controller (s)
3 Leaf-Spine must support the structure, ECMP (Equal Cost Multi-Path) between Rack and operators of Policy-based
It must be able to support Traffic Engineering capabilities.
4 END TO END Network Slicing Priority is different and each service QoS and Isolation from the implementation point of view
That should be guaranteed should be able to support my NFVI-Fabric and NFVI-Fabric Cross Networking.
5 Network interworking guide including a redundant configuration (including Forntend / Backend) are presented redundancy
a) Looping Free physical structures, L2 / L3 configuration and support LAG, ECMP Load Balancing measures, internal / external IP uses standard,
• When DU or CU in conjunction Backhaul perspective dual scheme: L3 (including Data / Signal Path)
• Call Flow Load-Balacing structure for Data: Call base or Traffic base
b) IP network according to the virtual evolution (SDN Controller, Spine-Leaf structure, etc.) can be presented when configuring specific external Network Configuration
• Segment Routing introduction request: Segement MPLS Routing US VRF capacity limit when progress (LFIB etc.)
• Whether to provide the backbone / backhaul 1588v2 for future network integration and 5G Service, End to End Clock offers
SK Telecom
5.2.5 Tap support functions
One NFVI optical Port will be provided for outputting to send in real time all at the external Packet
do.
c) To be indicated in the type and quantity of the output light Port Available Virtual Function Block.
d) To be output to the optical Port Packet transmission rate to be indicated by each Virtual Functional Block.
2 Optical Port are sufficient to monitor the input and output of the Virtual Functional Block in the system at the same time 5G
Must be provided by the quantity and speed, it should have a stable output.
a) At the same time it shall specify the combination and quantity of available monitoring Virtual Functional Block.
Optical Port should be able to arbitrarily set or change the connection of input and output terminals of all of the Virtual Functional Block 5G.
SK Telecom
EOD
SK Telecom

★5G 제안요청서 II.기술사항.ko.en PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

★5G 제안요청서 II.기술사항.ko.en PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Ⅱ.

5G system main equipment supplier request for proposal

One Common .................................................. .................................................. ........................................ 6

1.1 Standards ................................................ .................................................. .................................................. 6

1.2 Network Architecture .................................................. .................................................. ......................... 6

1.2.1 5G system configurations .................................................. .................................................. ....................... 6

1.2.2. NSA (Non-standalone) Architecture .................................................. .............................................. 6

1.2.3. SA (Standalone) Architecture ............................................. .................................................. ............. 7

1.2.4 Network Architecture related to our additional requirements ........................................... .................................. 8

1.3 Standards and Open Interface .................................................. .................................................. ....................... 8

1.3.1 Compliance .................................................. .................................................. .......................................... 8

1.3.2 Open Interface .................................................. .................................................. ................................ 9

1.4 MVI (Multi Vendor Interoperability) support .................................................. ........................................... 9

1.4.1 MVI supports a range .................................................. .................................................. ................................. 9

1.4.2 MVI support measures .................................................. .................................................. ............................... 10

1.5 technical support .................................................. .................................................. ............................................... 11

1.5.1 System Integration and Optimization Support .................................................. ............................................... 11

1.5.2 S-Index .................................................. .................................................. ........................................... 11

1.6 service .................................................. .................................................. .................................................. . 12

1.6.1 5G services .................................................. .................................................. ....................................... 12

1.6.2 Existing services .................................................. .................................................. .................................... 13

1.7 Network Performance .................................................. .................................................. ...................... 13

1.8 Security Support ................................................ .................................................. ................................................ 14

1.8.1 Security Guide .................................................. .................................................. .................................... 14

1.8.2 Security requirements ............................................... .................................................. .................................... 15

1.8.3 Security Regulations .................................................. .................................................. ........................................ 17

1.9 System Evolution .................................................. .................................................. .......................................... 17

1.9.1 Evolution Support Systems .................................................. .................................................. ........................... 17

1.10 BMT / DVT Availabilty .................................................. .................................................. ...................... 18

1.11 Open Source Support .................................................. .................................................. .............................. 18

2 5G Radio Access Network .................................................. .................................................. ...... 19

2.1 RAN shape and structure .................................................. .................................................. ............................... 19

2.1.1 RAN Architecture .................................................. .................................................. ......................... 19

2.1.2 gNB H / W shape .................................................. .................................................. .............................. 21

2.1.3 Fronthaul .................................................. .................................................. ....................................... 30

2.1.4 Backhaul ................................................. .................................................. .......................................... 34

2.1.5 Optical module .................................................. .................................................. ............................................. 35

2.2 General Specifications .................................................. .................................................. ............................................... 36

2.2. Mechanical specifications .................................................. .................................................. .................................... 36

2.2. Electrical Specifications .................................................. .................................................. .................................... 38

2.2.3 Environmental Specifications .................................................. .................................................. .................................... 39

2.3 RAN Performance .................................................. .................................................. ............................................. 41

2.3.1. Capacity .................................................. .................................................. ......................................... 41

2.3.2. Latency .................................................. .................................................. ........................................... 42

2.3.3 Coverage .................................................. .................................................. ........................................ 43

2.3.4 Mobility .................................................. .................................................. .......................................... 45

2.3.5 QoS .................................................. .................................................. ................................................. 45

2.3.6 Energy efficiency .................................................. .................................................. ................................ 45

2.3.7 MTBF, MTTR, MTTF .................................................. .................................................. ..................... 46

2.3.8 Etc .................................................. .................................................. ................................................. 47

2.4 RAN functions .................................................. .................................................. ............................................. 47

2.4.1 Synchronization feature .................................................. .................................................. .................................... 47

2.4.2 Call processing .................................................. .................................................. .................................... 48

2.4.3. Resource management ............................................... .................................................. .................................... 50

2.4.4 Add-ons .................................................. .................................................. ......................................... 51

2.4.5 RF transceiver function ............................................... .................................................. .................................. 53

2.4.6 O & M functions .................................................. .................................................. ...................................... 54

2.4.7 Additional interlocking device ............................................... .................................................. .................................... 61

2.4.8 Multi-RAT support .................................................. .................................................. ............................. 63

2.4.9 Intelligent Management .................................................. .................................................. ............. 63

2.4.10 Other features .................................................. .................................................. ........................................ 66

2.5 Interface Specification .................................................. .................................................. ..................................... 66

2.5.4 gNB-CU and the inter-connection standard gNB-DU .................................................. .................................................. 69