http://www.itu.int/pub/publications.aspx?lang=en&parent=T-TUT-IMT-2017-1
권호기사보기
| 기사명 | 저자명 | 페이지 | 원문 | 기사목차 |
|---|
국회도서관 홈으로
정보검색
소장정보 검색
결과 내 검색
동의어 포함
저자 검색
- 검색종류
| 대표형(전거형, Authority) | 생물정보 | 이형(異形, Variant) | 소속 | 직위 | 직업 | 활동분야 | 주기 | 서지 | |
|---|---|---|---|---|---|---|---|---|---|
| 연구/단체명을 입력해주세요. | |||||||||
관련 키워드 검색
- 대표어
- 외국어
|
|
|
|
|
|
주제별 검색
* 주제를 선택하시면 검색 상세로 이동합니다.
목차보기
Title page
Contents
Foreword 3
1. Core network aspects 9
1.1. Future networks 10
Future networks: Objectives and design goals 10
Summary 11
1. Scope 13
2. References 13
3. Definitions 13
3.1. Terms defined elsewhere 13
3.2. Terms defined in this Recommendation 13
4. Abbreviations and acronyms 14
5. Conventions 14
6. Introduction 14
7. Objectives 15
7.1. Service awareness 15
7.2. Data awareness 15
7.3. Environmental awareness 15
7.4. Social and economic awareness 16
8. Design goals 16
8.1. Service diversity 16
8.2. Functional flexibility 17
8.3. Virtualization of resources 17
8.4. Data access 17
8.5. Energy consumption 18
8.6. Service universalization 19
8.7. Economic incentives 19
8.8. Network management 19
8.9. Mobility 20
8.10. Optimization 20
8.11. Identification 21
8.12. Reliability and security 21
9. Target date and migration 21
Appendix I. Technologies for achieving the design goals 23
I.1. Network virtualization (virtualization of resources) 23
I.2. Data/content-oriented networking (data access) 23
I.3. Energy-saving of networks (energy consumption) 24
I.4. In-system network management (network management) 24
I.5. Network optimization (optimization) 25
I.6. Distributed mobile networking (mobility) 26
Bibliography 28
Framework of data aware networking for future networks 30
Summary 31
1. Scope 33
2. References 33
3. Definitions 33
3.1. Terms defined elsewhere 33
3.2. Terms defined in this Recommendation 33
4. Abbreviation and acronyms 34
5. Conventions 34
6. Introduction 34
7. Overview of data aware networking 35
8. Problem spaces 36
8.1. Scalable and cost-efficient content distribution 36
8.2. Mobility 36
8.3. Disruption tolerance 36
9. Design goals 37
9.1. Naming 37
9.2. Routing 37
9.3. Caching 37
9.4. Security 37
9.5. Mobility 38
9.6. Application programming interface 38
9.7. Transport 38
10. Environmental considerations 38
11. Security considerations 39
Appendix I. ICN: naming, routing and caching 40
I.1. Naming 40
I.2. Routing 40
I.3. Caching 41
Bibliography 42
Data Aware Networking (Information Centric Networking) - Requirements and Capabilities 43
Summary 44
1. Scope 46
2. References 46
3. Definitions 46
3.1. Terms defined elsewhe 46
3.2. Terms defined in this Recommendation 47
4. Abbreviations and acronyms 47
5. Conventions 47
6. Justification 47
7. Requirements for DAN 47
7.1. Forwarding 47
7.2. Routing 48
7.3. Mobility 48
7.4. Security 48
7.5. Management 49
7.6. Miscellaneous 49
7.7. Use case specific 49
8. Capabilities of DAN 50
8.1. Configuration of DAN components 50
8.2. Capabilities 51
9. Security considerations 53
10. Environmental considerations 53
Bibliography 54
Data aware networking - Scenarios and use cases 55
Summary 56
1. Scope 58
2. References 58
3. Definitions 58
3.1. Terms defined elsewhere 58
3.2. Terms defined in this Supplement 58
4. Abbreviations and acronyms 59
5. Conventions 59
6. Overview 59
7. Service scenarios 60
7.1. Content dissemination 60
7.2. Sensor networking 62
7.3. Vehicular networking 64
7.4. Automated driving 66
7.5. Networking in a disaster area 68
7.6. Advanced metering infrastructure in a smart grid 70
7.7. Proactive video caching 72
7.8. In-network data processing 73
7.9. Multihoming with DAN 76
7.10. Traffic engineering of DAN 78
8. Migration 80
9. Environmental considerations 80
10. Security considerations 80
Appendix I. Efficient and resilient data dissemination in a disaster area 81
Appendix II. Design of advanced metering infrastructure in smart grid with DAN 82
Appendix III. Proactive video caching with DAN 83
Bibliography 84
1.2. Virtualization 85
Framework of network virtualization for future networks 85
Summary 86
Introduction 88
1. Scope 89
2. References 89
3. Definitions 89
3.1. Term defined elsewhere 89
3.2. Terms defined in this Recommendation 89
4. Abbreviations and acronyms 90
5. Conventions 90
6. Overview 90
7. Problem spaces 92
7.1. Coexistence of multiple networks 92
7.2. Simplified access to resources 93
7.3. Flexibility in provisioning 93
7.4. Evolvability 93
8. Design goals 94
8.1. Isolation 94
8.2. Network abstraction 94
8.3. Topology awareness and quick reconfigurability 95
8.4. Performance 95
8.5. Programmability 95
8.6. Management 95
8.7. Mobility 96
8.8. Wireless 96
9. Applicability 97
10. Environmental considerations 97
11. Security considerations 97
Appendix I. Detailed description of LINP 98
Appendix II. Use cases of network virtualization 99
II.1. Case 1: Network virtualization for network service providers 99
II.2. Case 2: Experiments on the feasibility of new network architectures [b-GENI GDD0608] 100
II.3. Case 3: mobility in virtualized network 100
II.4. Case 4: Wireless access network virtualization 102
Bibliography 105
Requirements of network virtualization for future networks 106
Summary 107
1. Scope 109
2. References 109
3. Definitions 109
3.1. Terms defined elsewhere 109
3.2. Terms defined in this Recommendation 109
4. Abbreviations and acronyms 109
5. Conventions 110
6. Overview of network virtualization 110
7. Requirements 110
7.1. Physical resource management 110
7.2. Virtual resource management 110
7.3. LINP management 111
7.4. Service management 111
7.5. Authentication, authorization and accounting 112
7.6. LINP federation 112
7.7. Service mobility 112
8. Environmental considerations 113
9. Security considerations 113
Appendix I. Resource hierarchical model 114
Functional architecture of network virtualization for future networks 115
Summary 116
1. Scope 119
2. References 119
3. Definitions 119
3.1. Terms defined elsewhere 119
3.2. Terms defined in this Recommendation 119
4. Abbreviations and acronyms 119
5. Conventions 120
6. Overview of functional architecture 120
6.1. User roles 121
6.2. LINP federation without LINP exchangers 123
7. Resources and LINPs 124
7.1. Physical resources 124
7.2. Virtual resources 125
7.3. LINPs 125
7.4. Allocation and binding 125
8. Physical node architecture 126
9. Physical resource management functions 127
9.1. Physical resource configuration functions 127
9.2. Physical resource monitoring and fault management function 128
9.3. Physical resource discovery function 128
10. Virtual resource management functions 128
10.1. Virtual resource configuration functions 128
10.2. Virtual resource monitoring and fault management function 128
10.3. Virtual resource discovery function 128
11. LINP management functions 129
11.1. Resource coordination function 129
11.2. LINP configuration functions 129
11.3. LINP monitoring and fault detection function 129
11.4. Authorization functions 129
12. LINP operator functions 130
13. Service deployment functions 130
14. Service developer functions 131
15. Gateway functions 131
16. User terminal functions 132
17. Federation functions 133
18. Reference points 133
18.1. User-to-network interface (UNI) 133
18.2. Network-to-network interface (NNI) 134
18.3. Virtual resource management interface (VMI) 134
18.4. LINP management interface (LMI) 134
18.5. Service management interface (SMI) 134
18.6. Programmer-to-redirector interface (PRI) 134
19. Security considerations 134
Appendix I. Implementation example of network virtualization 135
Bibliography 137
Framework of software-defined networking 138
Summary 139
1. Scope 141
2. References 141
3. Definitions 141
3.1. Terms defined elsewhere 141
3.2. Terms defined in this Recommendation 141
4. Abbreviations and acronyms 141
5. Conventions 142
6. Introduction 142
7. Overview 142
8. Objectives 143
9. High-level capabilities 144
10. Requirements 144
11. High-level architecture 145
11.1. Application layer 145
11.2. SDN control layer 145
11.3. Resource layer 146
11.4. Multi-layer management functions 146
11.5. Interfaces 147
12. Environmental considerations 147
13. Security considerations 147
Appendix I. Areas for further considerations in SDN standardization 148
I.1. Interworking 148
I.2. Verification of SDN applications 148
I.3. Adaptation to large-scale networks 149
I.4. Design of resource abstraction 149
I.5. Virtualization of network elements 149
I.6. Multiple-level of programmability 150
I.7. Programmatic extension in resource layer 150
I.8. Management 150
Bibliography 151
Functional requirements of software-defined networking 152
Summary 153
1. Scope 155
2. References 155
3. Definitions 155
3.1. Terms defined elsewhere 155
3.2. Terms defined in this Recommendation 155
4. Abbreviations and acronyms 155
5. Conventions 156
6. Overview 156
7. Functional requirements 156
7.1. General requirements 156
7.2. SDN application layer 157
7.3. SDN control layer 157
7.4. SDN resource layer 157
7.5. Multilayer management functions 158
8. Environmental considerations 158
9. Security considerations 158
Functional architecture of software-defined networking 159
Summary 160
1. Scope 162
2. References 162
3. Definitions 162
3.1. Terms defined elsewhere 162
3.2. Terms defined in this Recommendation 163
4. Abbreviations and acronyms 163
5. Conventions 164
6. Introduction 164
7. Functional architecture 165
7.1. SDN application layer 166
7.2. SDN control layer 167
7.3. SDN resource layer 169
7.4. Multi-layer management functions 171
8. SDN functional profiles 173
9. Environmental considerations 173
10. Security considerations 173
Annex A. Multi-layer management functional components details 175
A.1. Application layer management functional component 175
A.2. Control layer management functional component 177
A.3. Resource layer management functional component 179
A.4. Multi-layer management orchestration functional component 181
A.5. External relationship management functional component 182
Appendix I. Orchestration in SDN 184
Bibliography 185
Requirements and capability framework for NICE implementation making use of software-defined networking technologies 186
Summary 187
1. Scope 189
2. References 189
3. Definitions 189
3.1. Terms defined elsewhere 189
3.2. Terms defined in this Recommendation 190
4. Abbreviations and acronyms 190
5. Conventions 191
6. Requirements of software-defined NICE 191
6.1. Introduction to S-NICE 191
6.2. Requirements of service control 191
6.3. Requirements of open environment 192
6.4. Requirements of content and context analysis 192
6.5. Requirements of policy control 192
6.6. Requirements of traffic scheduling 193
6.7. Requirements of access and core transport 193
6.8. Requirements for support of virtualized network and virtualized network functions 193
7. The capability framework for software-defined NICE 194
7.1. Overview of the capability framework 194
7.2. The S-NICE orchestration capabilities at the service layer 194
7.3. The S-NICE controller capabilities at the transport layer 195
7.4. The S-NICE infrastructure capabilities at the transport layer 196
8. Security considerations 196
Appendix I. Differences between NICE capabilities and S-NICE capabilities 198
Bibliography 201
Functional architecture for NICE implementation making use of software defined networking technologies 202
Summary 203
1. Scope 205
2. References 205
3. Definitions 205
3.1. Terms defined elsewhere 205
3.2. Terms defined in this Recommendation 206
4. Abbreviations and acronyms 206
5. Conventions 206
6. Overview for S-NICE 206
7. Functional architecture for S-NICE 207
7.1. Overall functional architecture of S-NICE 207
7.2. Detailed functional architectures of S-NICE orchestration functions 209
7.3. Detailed functional architectures of S-NICE controller functions 212
7.4. Detailed functional architectures of S-NICE infrastructure functions 214
8. Reference points of S-NICE 215
8.1. Internal reference points of S-NICE orchestration functions 215
8.2. Internal reference points of S-NICE controller functions 216
8.3. Internal reference points of S-NICE infrastructure functions 217
8.5. External reference points of S-NICE 218
8.4. Internal reference points among functions of S-NICE 218
9. Security considerations 219
Appendix I. This appendix does not form an integral part of this Recommendation 220
I.1. Implementation flows of on-demand provision 220
I.2. Implementation flows of resource guarantee based on network awareness 221
I.3. Implementation flows of traffic scheduling based on network awareness 222
Bibliography 223
Requirements of soft network architecture for mobile 224
Summary 225
1. Scope 227
2. References 227
3. Definitions 227
3.1. Terms defined elsewhere 227
3.2. Terms defined in this Recommendation 227
4. Abbreviations and acronyms 227
5. Conventions 228
6. Soft network architecture for mobile and its design principle 228
7. Requirements of SAME 229
Appendix I. Scenarios of SAME 231
I.1. Flexible traffic steering 231
I.2. Virtualization of network functions 232
I.3. SAME network slice for MVNO scenario 233
I.4. Separation of control function and forwarding function 234
Appendix II. Problem statement of current mobile packet core network 237
II.1. Problem in traffic steering 237
II.2. Problem caused by proprietary hardware 237
II.3. Problem statement of the mobile packet core gateway 237
Appendix III. Mapping between scenarios, problems, design principles and requirements 239
Bibliography 240
1.3. Multi-connection 241
Functional architecture of multi-connection 241
Summary 242
1. Scope 244
2. References 244
3. Definitions 244
3.1. Terms defined elsewhere 244
3.2. Terms defined in this Recommendation 244
4. Abbreviations and acronyms 245
5. Conventions 246
6. Overview of the multi-connection architecture 246
6.1. General architecture 246
6.2. High level function descriptions 248
6.3. Functional entities 251
6.4. Reference points 253
7. Multi-connection architecture in relation to the NGN architecture 254
8. Security considerations 255
Appendix I. The evolvement of multi-connection architecture 256
Appendix II. Mapping of baseline to 3GPP EPC/IMS 257
Appendix III. Mapping of baseline to next generation hotspot (NGH)/IMS 258
Appendix IV. Information procedures of multi-connection 259
IV.1. Initiating/adding a new connection 259
IV.2. Removing a connection 260
IV.3. IP flow mobility 261
IV.4. Service composition during call establishment 263
IV.5. Service decomposition during call establishment 264
IV.6. Service decomposition with QoS policy control 265
IV.7. Subscriber attaches to the access network 266
IV.8. Policy control procedure 266
Bibliography 268
Intelligent access selection in multi-connection 269
Summary 270
1. Scope 272
2. References 272
3. Definitions 272
3.1. Terms defined elsewhere 272
3.2. Terms defined in this Recommendation 273
4. Abbreviations and acronyms 273
5. Conventions 273
6. Scenarios and requirements 274
6.1. Scenarios 274
6.2. Requirements 275
7. Solutions 276
7.1. Overview 276
7.2. Access discovery solution 276
7.3. Access selection solution 277
Bibliography 279
A multi-path transmission control in multi-connection 280
Summary 281
1. Scope 283
2. References 283
3. Definitions 283
3.1. Terms defined elsewhere 283
3.2. Terms defined in this Recommendation 283
4. Abbreviations and acronyms 284
5. Conventions 285
6. Scenarios and requirements 285
6.1. Scenarios 285
6.2. Requirements 285
7. A multi-path transmission mechanism 287
7.1. Overview 287
7.2. Initialization of the mechanism 288
7.3. Description of the mechanism 289
8. Capability requirements 292
8.1. MPT-enhanced MUE requirements in the sending side 292
8.2. MPT-enhanced MUE requirements in the receiving side 292
8.3. MPT-enhanced MPC-FE requirements 293
8.4. MPT-enhanced SCF requirements 293
9. Information flow 293
9.1. Path selection mechanism 293
9.2. Traffic adjustment mechanism 296
10. Security considerations 299
10.1. Security requirement 299
10.2. Attack defence 300
Bibliography 302
Flow-based service continuity in multi-connection 303
Summary 304
1. Scope 306
2. References 306
3. Definitions 306
3.1. Terms defined elsewhere 306
3.2. Terms defined in this Recommendation 307
4. Abbreviations and acronyms 307
5. Conventions 307
6. Scenarios and requirements 308
6.1. Scenarios 308
6.2. Requirements 308
7. Flow-based service continuity mechanisms 309
7.1. Overview 309
7.2. Description of the mechanisms 310
7.3. Capability requirements 311
7.4. Procedures 312
Bibliography 315
Multi-connection requirements 316
Summary 317
1. Scope 319
2. References 319
3. Definitions 320
3.1. Terms defined elsewhere 320
3.2. Terms defined in this Recommendation 320
4. Abbreviations and acronyms 320
5. Conventions 321
6. Multi-connection requirements 322
6.1. Connection management 323
6.2. Multi-connection registration 323
6.3. Multi-connection coordination 323
6.4. Service transfer 324
6.5. Service decomposition and composition 324
6.6. Multi-connection related policies 324
6.7. QoS requirements in multi-connection 325
6.8. QoS mapping among different access networks 325
6.9. Access network selection 325
6.10. Access network monitoring 326
6.11. Identifying and binding of IP flows 326
6.12. Charging and accounting in multi-connection 326
6.13. UE function in multi-connection 327
6.14. IPv4/6 consideration 327
6.15. Energy efficiency and energy/power management in multi-connection 327
6.16. Backward compatibility 327
6.17. Security requirement 327
7. Security considerations 328
Appendix I. QoS mapping among different access networks 329
Appendix II. Generic scenarios of multi-connection 330
Appendix III. Policy required for different scenarios 332
Bibliography 333
Identification and configuration of resources for multi-connection 334
Summary 335
1. Scope 337
2. References 337
3. Definitions 337
3.1. Terms defined elsewhere 337
3.2. Terms defined in this Recommendation 338
4. Abbreviations and acronyms 338
5. Conventions 339
6. Identification of resources and attributes for multi-connection 339
6.1. Identification of resources 339
6.2. Resource identifiers 342
7. Configuration of resource identifiers 342
7.1. Relations between resource identifiers within each layer 343
7.2. Relationship between resource identifiers and multi-connection functional entities 344
8. Resource identifiers in multi-connection network 346
8.1. Introduction of resource IDs according to multi-connection scenarios 346
8.2. Introduction of resource IDs according to multi-connection use cases 346
9. Security considerations 347
Bibliography 348
Capabilities of multi-connection to support streaming services 349
Summary 350
1. Scope 352
2. References 352
3. Definitions 352
3.1. Terms defined elsewhere 352
3.2. Terms defined in this Recommendation 353
4. Abbreviations and acronyms 353
5. Conventions 355
6. Service definition and general requirements 355
6.1. Service definition 355
6.2. General requirements 355
6.2.1. Multimedia content requirement 355
6.2.2. Interaction requirement 356
6.3. QoS/QoE requirements 356
6.4. Use case of MC-Streaming 357
7. Network and MUE requirements 357
7.1. Network transport capability requirements 357
7.2. MUE requirements 358
8. Architecture 358
8.1. General architecture 358
8.2. High level description of functions 359
8.3. Functional entities 359
8.4. Reference points 361
9. Information flows 362
9.1. Authorization and streaming establishment 362
9.2. Streaming decomposition 364
9.3. Streaming composition 365
9.4. Streaming transfer 367
10. Security considerations 369
10.1. Subscriber security 369
10.2. Service security 370
10.3. Network security 371
10.4. Terminal device security 373
11. Charging 373
11.1. Charging mechanisms 374
11.2. Charging policies 374
Appendix I. Scenarios of streaming services over multi-connection 376
I.1. Video services 376
I.2. Video conference services 376
I.3. Real-time monitor services 377
Bibliography 378
Capabilities of multi-connection to support enhanced multimedia telephony services 379
Summary 380
1. Scope 383
2. References 383
3. Definitions 383
3.1. Terms defined elsewhere 383
3.2. Terms defined in this Recommendation 384
4. Abbreviations and acronyms 384
5. Conventions 385
6. Description of service features 386
6.1. Service definition 386
6.2. Enriched call 386
6.3. Enhanced file transfer 386
6.4. Enhanced content sharing 386
6.5. Enhanced messaging 387
7. Architecture of eMMTel over multi-connection 387
7.1. High level functions description 388
7.2. Functional entities defined in the eMMTel service function 388
8. Specific capabilities of multi-connection to support eMMTel 389
8.1. Requirement for MAS-F 389
8.2. Requirement for SCF 389
8.3. Requirement for MCF 389
8.4. Requirement for MMF 390
8.5. Requirement for transport function (TF) 391
8.6. Requirement for MUE 391
9. Information flow 391
9.1. Enriched call 391
9.2. Enhanced content sharing 395
9.3. Enhanced file transfer 397
9.4. Enhanced messaging 399
10. Charging consideration 399
11. Security and privacy considerations 400
11.1. Access security for the user-to-network interface (UNI) 400
11.2. Security for the service 400
11.3. Communication security 401
11.4. Data confidentiality 401
11.5. Data integrity 401
Appendix I. Scenarios for enhanced multimedia telephony services 402
I.1. Reliability and service continuity 402
I.2. Bandwidth aggregation 402
I.3. Multiple UE receiving multimedia 403
I.4. UE initiated network selection 404
I.5. Network initiated network selection 404
I.6. Service transfer 404
Bibliography 406
1.4. Fixed-Mobile Convergence and Mobility Management 407
Fixed-mobile convergence general requirements 407
Summary 408
1. Scope and purpose 411
2. References 411
3. Definitions 412
3.1. Terms defined elsewhere 412
3.2. Terms defined in this Recommendation 412
4. Abbreviations and acronyms 412
5. Conventions 414
5.1. Usage of the term "IMS" 414
6. Objectives of FMC 414
6.1. General objectives of FMC 414
6.2. Objectives from different perspectives 414
7. Fundamental characteristics of FMC 415
8. FMC service requirements 416
8.1. Access service support 416
8.2. Enhanced VPN 416
8.3. Unified messaging 416
9. FMC capability requirements 416
9.1. Access independence 417
9.2. Uniform authentication and uniform authorization mechanism 417
9.3. Charging and management 417
9.4. Service access environment 417
9.5. Quality of service 417
9.6. Interworking 417
9.7. Reliability requirements 417
9.8. Security requirements 417
9.9. Public services issues 418
9.10. Network selection 418
9.11. Location identification 418
9.12. Personalized configuration 418
9.13. Personal data network storage 418
9.14. Accounting support capabilities 419
9.15. Message processing 419
9.16. Presence information 419
9.17. Mechanism for applications to access user data 419
9.18. User identifier management 419
10. Network environment 420
10.1. General network environments 420
10.2. FMC network scenarios 420
Appendix I. FMC approach and scenarios 422
I.1. Convergence in the control layer 422
I.2. Convergence in application layer 423
I.3. Convergence in the management layer 423
Bibliography 425
FMC service using legacy PSTN or ISDN as the fixed access network for mobile network users 426
Summary 427
1. Scope 429
2. References 429
3. Definitions 430
3.1. Terms defined elsewhere 430
3.2. Terms defined in this Recommendation 430
4. Abbreviations and acronyms 430
5. Conventions 432
6. Service features 432
6.1. Service numbering 432
6.2. Service subscription 432
6.3. Registration and authentication for legacy fixed network access 432
6.4. Call handling 433
6.5. Extent of mobility provided by PAM service 434
7. Architecture 434
7.1. Architecture alternatives 434
7.2. Functional entities 436
7.3. Information flows overview 439
7.4. Allocation of functional entities to physical nodes 441
8. Capability requirements 444
8.1. User authentication through PSTN/ISDN access 444
8.2. User identification and routing 445
8.3. User profile treatment 446
8.4. Emergency call handling 446
8.5. Video call handling 446
9. Implementation of PAM service using IN approach 447
9.1. Network configuration 447
9.2. Signalling requirements 449
9.3. Call flows 449
Bibliography 455
Mobility management and control framework and architecture within the NGN transport stratum 456
Summary 457
1. Scope 459
2. References 459
3. Definitions 460
3.1. Terms defined elsewhere 460
3.2. Terms defined in this Recommendation 460
4. Abbreviations and acronyms 461
4.1. Functions 461
4.2. Functional entities 461
4.3. Functional blocks 462
4.4. Other 462
5. Conventions 462
6. Architecture model and concepts 462
6.1. General concepts 462
6.2. IP mobility management selection principles 463
6.3. High level functions 464
6.4. Functional entities 465
6.5. Reference points 469
7. Procedures 480
7.1. Overview of mobility procedures 480
7.2. Network attachment, IP configuration, and mobility location management 481
7.3. Handover 485
8. Security considerations 491
8.1. Security threats 491
8.2. Security requirements 492
Appendix I. Architecture reference model 493
I.1. Non-roaming architecture and scenarios 493
I.2. Roaming architecture and scenarios 494
Appendix II. Mapping between functions defined in this Recommendation and IETF entities 498
II.1. The IETF mobility architectures 498
Appendix III. Mapping between this Recommendation and 3GPP functions 501
III.1. Introduction 501
III.2. References 501
III.3. Architectural scenarios 501
III.4. Mapping from 3GPP entities to ITU-T Y.2018 entities 504
Bibliography 506
Mobility management framework for applications with multiple devices 507
Summary 508
1. Scope 510
2. References 510
3. Definitions 510
3.1. Terms defined elsewhere 510
3.2. Terms defined in this Recommendation 510
4. Abbreviations and acronyms 511
5. Overview of Mobility Management (MM) for applications with multiple devices 512
6. Requirements of MM for applications with multiple devices 515
6.1. Cooperation between MM functions and capabilities to handle multiple devices 515
6.2. Support of network-based control scheme 515
6.3. Alignment with [ITU-T Y.2018] and [ITU-T Q.1707] 515
6.4. Identification of user and multiple devices 515
6.5. Support of the device switchover 515
6.6. Support for authentication and authorization of user and devices 515
7. Functional architecture for applications with multiple devices 515
7.1. Transport stratum 516
7.2. Service stratum 517
8. MM procedure for applications with multiple devices 517
8.1. Procedure for registration 518
8.2. Procedure for applications with one-to-multiple devices 518
8.3. Procedure for applications with multiple devices-to-one 519
8.4. Procedure for applications with multiple devices-to-multiple devices 521
9. Security considerations 521
Appendix I. Use case of application based on MIP 522
I.1. Use case overview 522
I.2. Deployment scenario of application with multiple devices using MIP 522
Bibliography 525
Applications 526
Overview of the Internet of things 526
Summary 527
1. Scope 529
2. References 529
3. Definitions 529
3.1. Terms defined elsewhere 529
3.2. Terms defined in this Recommendation 529
4. Abbreviations and acronyms 529
5. Conventions 530
6. Introduction of the IoT 530
6.1. Concept of the IoT 530
6.2. Technical overview of the IoT 531
7. Fundamental characteristics and high-level requirements of the IoT 533
7.1. Fundamental characteristics 533
7.2. High-level requirements 533
8. IoT reference model 534
8.1. Application layer 535
8.2. Service support and application support layer 535
8.3. Network layer 535
8.4. Device layer 535
8.5. Management capabilities 536
8.6. Security capabilities 536
Appendix I. IoT ecosystem and business models 537
I.1. Business roles 537
I.2. Business models 538
Bibliography 540
Overview of Smart Farming based on networks 541
Summary 542
Introduction 544
1. Scope 545
2. References 545
3. Definitions 545
3.1. Terms defined elsewhere 545
3.2. Terms defined in this Recommendation 546
4. Abbreviations and acronyms 546
5. Conventions 546
6. Introduction of Smart Farming based on networks 546
6.1. Concept 546
6.2. General overview 547
7. Reference model of Smart Farming based on networks 548
7.1. Reference architecture 548
7.2. Service roles 549
8. Service capabilities required to support Smart Farming 549
9. Network capabilities 550
10. Security considerations 550
Appendix I. The cyclic procedures of a convergence service for agriculture 551
Appendix II. Environments and deployments of a convergence service for agriculture 552
Appendix III. Service capabilities 554
III.1. Service capabilities for the pre-production stage 554
III.2. Service capabilities for the production stage 554
III.3. Service capabilities for the post-production stage 555
Bibliography 559
2. Transport aspects 560
2.1. Radio over Fiber (RoF) 561
Radio-over-fibre (RoF) technologies and their applications 561
Summary 562
1. Scope 564
2. References 564
3. Definitions 564
3.1. Terms defined elsewhere 564
3.2. Terms defined in this Supplement 564
4. Abbreviations and acronyms 565
5. General concept 567
6. System architectures 569
6.1. Analogue RoF system 569
6.2. Digital RoF system 572
6.3. Relay transmission (repeater) 574
7. Fundamental technologies 577
7.1. Electrical-to-optical conversion 577
7.2. Optical-to-electrical conversion 578
7.3. High-spectral-efficient transmission 580
7.4. Digital-signal-processing-assisted (DSP-assisted) analogue RoF techniques 585
8. Network models 588
8.1. Reference points 590
8.2. Service 591
8.3. Optical distribution network 591
8.4. Possible RoF over ODN configurations and characteristics 592
8.5. Possible RoF over ODN survivability and characteristics 593
9. System design for supporting a radio access system over an optical access network 594
9.1. Measurement test model for mobile front-hauling over an optical distribution network 594
9.2. Example of system performance evaluation 595
Bibliography 611
2.2. Common Public Radio Interface (CPRI) 612
OTN transport of CPRI signals 612
Summary 613
1. Scope 615
2. References 615
3. Definitions 615
4. Abbreviations and acronyms 615
5. Conventions 616
6. Introduction 616
7. Mappings based on normative methods 616
7.1. Single CPRI signal mapping into ODUk (k = 0, 1, flex(CBR)) 617
7.2. Multiple CPRI client signal mapping using GFP-T 622
8. Multiple CPRI option 3, 4 or 5 signal mapping into ODU2r 623
8.1. OPU2r overhead description 623
8.2. OPU2r payload mappings 625
8.3. PCS receiver 627
8.4. OTU2r structure 627
8.5. Bit rates and tolerances 627
2.3. G.Fast - Fast access to subscriber terminals 628
Fast access to subscriber terminals (G.fast) - Power spectral density specification 628
Summary 629
1. Scope 631
2. References 631
3. Definitions 631
4. Abbreviations and acronyms 632
5. Conventions 632
6. Transmit PSD mask 632
6.1. Overview 632
6.2. Limit PSD mask (LPM) 633
6.3. Subcarrier masking 633
6.4. Power spectral density shaping 633
6.5. Notching of specific frequency bands 634
6.6. Low frequency edge stop-band masking 635
7. Specification of spectral content 636
7.1. Profile control parameters 636
7.2. PSD mask specifications 637
7.3. Termination impedance 640
7.4. Maximum aggregate transmit power 640
8. Transmit PSD verification 640
Annex A to Annex W 642
Annex X. Adaptation to the coax medium 643
X.1. Profile control parameters 643
X.2. Termination impedance 643
X.3. Maximum aggregate transmit power 643
Appendix I. International amateur radio bands 644
Appendix II. Broadcast radio bands 645
Appendix III. Definition of transmitter PSD (TXPSD) for non-continuous transmissions 646
Fast access to subscriber terminals (G.fast) - Physical layer specification 647
Summary 648
1. Scope 653
2. References 655
3. Definitions 655
3.1. Terms defined elsewhere 655
3.2. Terms defined in this Recommendation 655
4. Abbreviations and acronyms 659
5. Reference models and system requirements 663
5.1. System reference models 663
5.2. Application reference models 667
5.3. FTU protocol reference model 672
5.4. FTU functional model 674
5.5. INP system requirements 676
6. Profiles 676
6.1. Definition 676
6.2. Profile compliance 678
7. Transmission medium interface characteristics 679
7.1. Duplexing method 679
7.2. Frequency band 679
7.3. Power spectral density 679
7.4. Out-of-band PSD limit 692
7.5. Termination impedance 692
7.6. Maximum aggregate transmit power 692
8. Transport protocol specific transmission convergence (TPS-TC) function 692
8.1. Functional reference model 692
8.2. Generic DTU format 700
8.3. Packet-based TPS-TC (PTM-TC) 702
8.4. Network timing reference (NTR) 705
8.5. Time-of-day (ToD) 707
9. Physical media specific transmission convergence (PMS-TC) sub-layer 711
9.1. Functional reference model 711
9.2. DTU scrambler 714
9.3. DTU encoder 714
9.4. Interleaver 715
9.5. Data frame multiplexer 715
9.6. RMC 718
9.7. Acknowledgement 729
9.8. Retransmission function 731
10. Physical media dependent (PMD) function 739
10.1. PMD functional reference model 739
10.2. Symbol encoder 743
10.3. Precoder (downstream vectoring) 763
10.4. Modulation 777
10.5. TDD frame structure 780
10.6. Superframe structure 783
10.7. Normal and discontinuous operation intervals 784
10.8. Alignment of transmissions in vectored group 787
11. Operation and maintenance (OAM) 787
11.1. OAM functional model 787
11.2. Management functions and procedures over eoc 791
11.3. OAM primitives 832
11.4. OAM parameters 835
12. Link activation methods and procedures 860
12.1. Overview 860
12.2. Special operations channel (SOC) 877
12.3. Initialization procedure 881
12.4. Loop diagnostics mode 946
13. Online reconfiguration (OLR) 946
13.1. Overview 946
13.2. Eoc-based procedures 947
13.3. RMC-based procedures 962
13.4. Low power link states 966
14. Electrical requirements 983
14.1. Balance 983
14.2. Differential port impedance 984
Annex A to Annex R 985
Annex S. NT software upgrade 986
S.1. Scope 986
S.2. References 986
S.3. Reference mod 986
S.4. Software image management process 987
S.5. Message set 991
S.6. Software upgrade (informative) 1000
Annex T. Dynamic time assignment (DTA) - higher-layer control aspects 1006
T.1. Scope 1006
T.2. DTA control parameters 1006
T.3. Coordination between the link state request and the DTA request 1008
Annex U to Annex W 1009
Annex X. Operation without multi-line coordination intended for a crosstalk-free environment 1010
X.1. Scope 1010
X.2. Definitions 1010
X.3. Abbreviations and acronyms 1010
X.4. Reference model(s) 1010
X.5. Profiles 1011
X.6. Dynamic time assignment (DTA) 1013
X.7. Initialization messages 1019
X.8. Discontinuous operation 1023
X.9. On-line reconfiguration 1023
X.10. Initialization 1023
X.11. Low power states 1023
X.12. Adaptation to the coaxial cable medium 1024
Annex Y. Upstream dynamic resource reports 1029
Annex Z. Cross-layer traffic monitoring functions and link state control 1031
Z.0. Introduction 1031
Z.1. Definition of Terms 1031
Z.2. Abbreviations and acronyms 1031
Z.3. Reference models 1031
Z.4. Generic traffic monitoring functions 1033
Z.5. Generic information flows 1034
Z.6. Link state specific functions 1037
Z.7. Link state management and reporting parameters 1041
Appendix I. Wiring topologies and reference loops 1043
I.1. Wiring topologies 1043
I.2. Reference loops 1043
Appendix II. Example OLR use cases 1051
II.1. Transmitter initiated gain adjustment (TIGA) 1051
Appendix III. Motivation of MTBE accelerated test 1053
Appendix IV 1054
Appendix V. Retransmission buffer size and the achievable bit-rate 1055
V.1. Case 1: NSYMret+NSYMack+1≤Mus 1055
V.2. Case 2: NSYMret+NSYMack+1≥Mus 1056
V.3. Case 3: Lower bound for the achievable net data rate 1056
V.4. Memory size example 1057
Appendix VI. Example applications of discontinuous operation 1058
VI.1. Discontinuous operation with vectoring disabled 1058
VI.2. Examples of discontinuous operation with vectoring enabled 1059
Appendices VII to YX 1064
Appendix YY. Calculation of loop attenuation (LATN) 1065
Bibliography 1066
2.4. OTN 1067
Interfaces for the optical transport network 1067
Summary 1068
1. Scope 1073
2. References 1073
3. Definitions 1075
3.1. Terms defined elsewhere 1075
3.2. Terms defined in this Recommendation 1075
4. Abbreviations and acronyms 1076
5. Conventions 1081
6. Optical transport network interface structure 1082
6.1. Basic signal structure 1082
6.2. Information structure for OTN interfaces 1084
7. Multiplexing/mapping principles and bit rates 1087
7.1. Mapping 1089
7.2. Wavelength division multiplex 1089
7.3. Bit rates and capacity 1089
7.4. ODUk time-division multiplex 1093
8. OTN Interfaces 1099
8.1. Single-OTU (SOTU) interface 1099
8.2. Multi-OTU (MOTU) interface 1099
8.3. Single-OTU with management (SOTUm) interface 1099
8.4. Multi-OTU with management (MOTUm) interface 1100
9. Media Element 1100
10. OCh and OTSiA 1100
10.1. OCh 1100
10.2. Optical tributary signal assembly (OTSiA) 1100
11. Optical transport unit (OTU) 1100
11.1. OTUk frame structure 1101
11.2. Scrambling 1102
11.3. OTUCn frame structure 1102
12. Optical data unit (ODU) 1103
12.1. ODU frame stru 1103
12.2. ODU bit rates and bit-rate tolerances 1104
13. Optical payload unit (OPU) 1107
14. Overhead information carried over the OSC and OCC 1108
15. Overhead description 1108
15.1. Types of overhead 1112
15.2. Trail trace identifier and access point identifier definition 1113
15.3. OTS-O description 1115
15.4. OMS-O description 1116
15.5. OCh-O and OTSiG-O description 1116
15.6. OTU/ODU frame alignment OH description 1118
15.7. OTU OH description 1119
15.8. ODU OH description 1125
15.9. OPU OH description 1138
16. Maintenance signals 1141
16.1. OTS maintenance signals 1142
16.2. OMS maintenance signals 1142
16.3. OCh and OTiSA maintenance signals 1142
16.4. OTU maintenance signals 1143
16.5. ODU maintenance signals 1143
16.6. Client maintenance signal 1145
17. Mapping of client signals 1145
17.1. OPU client signal fail (CSF) 1146
17.2. Mapping of CBR2G5, CBR10G, CBR10G3 and CBR40G signals into OPUk 1146
17.3. Blank clause 1150
17.4. Mapping of GFP frames into OPUk (k=0, 1, 2, 3, 4, flex) 1150
17.5. Mapping of test signal into OPU 1151
17.6. Mapping of a non-specific client bit stream into OPUk 1153
17.7. Mapping of other constant bit-rate signals with justification into OPUk 1153
17.8. Mapping a 1000BASE-X and FC-1200 signal via timing transparent transcoding into OPUk 1162
17.9. Mapping a supra-2.488 Gbit/s CBR signal into OPUflex using BMP 1165
17.10. Mapping of packet client signals into OPUk 1167
17.11. Mapping of FlexE client signals into OPUflex using IMP 1168
17.12. Mapping of FlexE aware signals into OPUflex 1169
17.13. Mapping a 64b/66b PCS coded signal into OPUflex using BMP and 2-bit alignment of 66b code words 1173
18. Blank clause 1174
19. Mapping ODUj signals into the ODTU signal and the ODTU into the OPUk tributary slots 1174
19.1. OPUk tributary slot definition 1175
19.2. ODTU definition 1181
19.3. Multiplexing ODTU signals into the OPUk 1183
19.4. OPUk multiplex overhead and ODTU justification overhead 1190
19.5. Mapping ODUj into ODTUjk 1201
19.6. Mapping of ODUj into ODTUk.ts 1208
20. Mapping ODUk signals into the ODTUCn signal and the ODTUCn into the OPUCn tributary slots 1211
20.1. OPUCn tributary slot definition 1211
20.2. ODTUCn definition 1216
20.3. Multiplexing ODTUCn signals into the OPUCn 1217
20.4. OPUCn multiplex overhead and ODTU justification overhead 1218
20.5. Mapping ODUk into ODTUCn.ts 1222
Annex A. Forward error correction using 16-byte interleaved RS(255, 239) codecs 1225
Annex B. Adapting 64B/66B encoded clients via transcoding into 513B code blocks 1227
B.1. Transmission order 1227
B.2. Client frame recovery 1227
B.3. Transcoding from 66B blocks to 513B blocks 1227
B.4. Link fault signalling 1230
Annex C. Adaptation of OTU3 and OTU4 over multichannel parallel interfaces 1231
Annex D. Generic mapping procedure principles 1234
D.1. Basic principle 1234
D.2. Applying GMP in OTN 1237
D.3. Cm(t) encoding and decoding 1241
D.4. ΣCnD(t) encoding and decoding 1246
Annex E. Adaptation of parallel 64B/66B encoded clients 1248
E.1. Introduction 1248
E.2. Clients signal format 1248
E.3. Client frame recovery 1248
E.4. Additions to Annex B transcoding for parallel 64B/66B clients 1251
Annex F. Improved robustness for mapping of 40GBASE-R into OPU3 using 1027B code blocks 1254
F.1. Introduction 1254
F.2. 513B code block framing and flag bit protection 1254
F.3. 66B block sequence check 1255
Annex G. Mapping ODU0 into a low latency OTU0. (OTU0LL) 1259
G.1. Introduction 1259
G.2. Optical transport unit 0 low latency (OTU0LL) 1259
Annex H. OTUCn sub rates (OTUCn-M) 1262
H.1. Introduction 1262
H.2. OTUCn-M frame format 1262
Appendix I. Range of stuff ratios for asynchronous mappings of CBR2G5, CBR10G, and CBR40G clients with ±20 ppm bit-rate tolerance into OPUk, and for asynchronous multiplexing of ODUj into ODUk (k 〉 j) 1263
Appendix II. Examples of functionally standardized OTU frame structures 1269
Appendix III. Example of ODUk multiplexing 1272
Appendix IV. Blank appendix 1274
Appendix V. ODUk multiplex structure identifier (MSI) examples 1275
Appendix VI. Parallel logic implementation of the CRC-9, CRC-8, CRC-5 and CRC-6 1277
Appendix VII. OTL4.10 structure 1280
Appendix VIII. CPRI into ODU mapping 1281
Appendix IX. Overview of CBR clients into OPU mapping types 1282
Appendix X. Overview of ODUj into OPUk mapping types 1284
Appendix XI. Derivation of recommended ODUflex(GFP) bit-rates and examples of ODUflex(GFP) clock generation 1286
XI.1. Introduction 1286
XI.2. Tributary slot sizes 1286
XI.3. Example methods for ODUflex(GFP) clock generation 1288
Appendix XII. Terminology changes between ITU-T G.709 Edition 4 and Edition 5 1290
Appendix XIII. OTUCn sub rates (OTUCn-M) Applications 1292
XIII.1. Introduction 1292
XIII.2. OTUCn-M frame format and rates 1292
XIII.3. OTUCn-M fault condition 1293
Bibliography 1294
Flexible OTN short-reach interface 1295
Summary 1296
1. Scope 1298
2. References 1298
3. Definitions 1298
3.1. Terms defined elsewhere 1298
3.2. Terms defined in this Recommendation 1299
4. Abbreviations and acronyms 1299
5. Conventions 1300
6. Introduction and applications 1301
6.1. FlexO considerations 1301
6.2. Sample applications 1301
7. Structure and processes 1302
7.1. Basic signal structure 1302
7.2. Process flow 1303
8. FlexO frame 1303
8.1. Frame structure 1303
8.2. Multi-frame structure 1304
8.3. Bit rates 1305
8.4. FEC 1305
9. Alignment markers and overhead 1306
9.1. Lane alignment markers (AM) 1306
9.2. Overhead description 1307
10. OTUCn mapping 1313
10.1. Dividing and combining OTUCn 1313
10.2. FlexO frame payload 1313
10.3. Mapping of OTUC into FlexO frame 1313
10.4. FlexO group alignment and deskewing 1314
10.5. Scrambling 1314
11. FOIC interface 1315
11.1. FOIC1.4 interface 1315
Bibliography 1317
3. Signalling aspects 1318
3.1. Control plane of distributed service networking (DSN) 1319
Signalling architecture for the control plane of distributed service networking 1319
Summary 1320
1. Scope 1322
2. References 1322
3. Definitions 1322
3.1. Terms defined elsewhere 1322
3.2. Terms defined in this Recommendation 1322
4. Abbreviations and acronyms 1323
5. Conventions 1323
6. Control architecture and functions 1323
6.1. Functions 1324
6.2. Reference points 1325
7. Physical entities and interfaces in DSN architecture 1326
7.1. PEs and interfaces for content services over DSN 1327
7.2. PEs and interfaces when deploying MMTel service over DSN 1328
8. Protocols used for interfaces 1329
8.1. Protocols used for interfaces when deploying content services over DSN 1329
8.2. Protocols used for interfaces when deploying MMTel service over DSN 1329
9. Security considerations 1330
3.2. Control plane of SDN 1331
Framework of signalling for software-defined networking 1331
Summary 1332
1. Scope 1334
2. References 1334
3. Definitions 1334
3.1. Terms defined elsewhere 1334
3.2. Terms defined in this Supplement 1334
4. Abbreviations and acronyms 1335
5. Conventions 1335
6. Signalling requirements and scenarios 1336
6.1. SDN-enabled network 1336
6.2. SDN-enabled overlay network 1336
6.3. SDN controller related requirements and scenarios 1336
6.4. Software-defined mobile network 1339
7. Signalling model 1339
8. Description of interfaces in the signalling model 1340
8.1. Sa 1340
8.2. Sn 1340
8.3. Sew 1341
8.4. Ss 1341
8.5. Sma 1341
8.6. Smo 1342
8.7. Smc 1342
8.8. Smn 1342
9. Signalling protocol procedures 1342
9.1. Procedure for VM live migration 1342
Appendix I. Scenarios and corresponding requirements of Ss for seamless handover 1344
I.1. IEEE 802.21 media independent service (MIS) 1344
I.2. Signalling protocol procedures 1345
Appendix II. Development methodology of this Supplement 1346
Bibliography 1347
3.3. Resource control protocols for SDN 1348
Signalling requirements for flexible network service combination on broadband network gateway 1348
Summary 1349
Introduction 1351
1. Scope 1352
2. References 1352
3. Definitions 1352
3.1. Terms defined elsewhere 1352
3.2. Terms defined in this Recommendation 1352
4. Abbreviations and acronyms 1352
5. Conventions 1353
6. Architecture for the BNG with flexible network service combination 1353
7. Signalling requirements of the BNG 1354
7.1. Service route path, service combination and orchestration 1354
7.2. Service configuration on the BNG 1360
7.3. BNG resources, event and status notification to the service platform 1361
Annex A. Scenarios related to flexible network service combination on BNG 1364
A.1. Scenarios of the service route path 1364
A.2. Requirements of the network service combination 1366
Annex B. Scenarios and requirements of network service configuration on BNG 1368
B.1. Scenarios and requirements of the network service configuration on BNG 1368
Annex C. Scenarios and requirements of BNG event and status notification to the service platform 1370
C.1. Scenarios and requirements of BNG event and status notification to the service platform 1370
Annex D. Signalling requirements of service/user awareness and control 1371
D.1. Introduction 1371
D.2. Descriptions 1371
Signalling requirements for software-defined broadband access network 1376
Summary 1377
1. Scope 1379
2. References 1379
3. Definitions 1379
3.1. Terms defined elsewhere 1379
3.2. Terms defined in this Recommendation 1379
4. Abbreviations and acronyms 1379
5. Conventions 1380
6. Introduction of SBAN 1381
7. Procedures 1382
7.1. SBAN node initialization 1382
7.2. Registration 1383
7.3. Status query 1383
7.4. Service creation 1383
8. The signalling requirements of SBAN 1384
8.1. Overview of signalling requirements 1384
8.2. Signalling requirements for southbound interface 1384
8.3. Signalling requirements for northbound interface 1391
9. Security considerations 1395
Appendix I. An example of SBAN 1396
Bibliography 1398
Scenarios and signalling requirements of unified intelligent programmable interface for IPv6 1399
Summary 1400
1. Scope 1402
2. References 1402
3. Definitions 1402
3.1. Terms defined elsewhere 1402
3.2. Terms defined in this Recommendation 1402
4. Abbreviations and acronyms 1402
5. Conventions 1402
6. The deployment scenario and use cases 1403
6.1. Evolve from one IPv6 transition scenario to another 1403
6.2. Multiple transition mechanisms co-exist 1403
7. The signalling architecture 1405
8. Signalling requirements 1405
8.1. Component functions 1405
8.2. Interface requirements 1405
9. The signalling protocol procedures 1407
9.1. Information model 1408
9.2. Operations 1408
Appendix I. Protocol profiles for this Recommendation 1409
Bibliography 1410
Signalling requirements for Broadband Network Gateway (BNG) pool 1411
Summary 1412
1. Scope 1414
2. References 1414
3. Definitions 1414
3.1. Terms defined elsewhere 1414
3.2. Terms defined in this Recommendation 1414
4. Abbreviations and acronyms 1414
5. Conventions 1415
6. Introduction of BNG Pool 1415
7. Architecture of the BNG pool 1416
8. Signalling requirements for the BNG pool 1416
8.1. Signalling for membership management and configuration of the BNG pool 1416
8.2. Signalling for the notification of BNG status/information 1419
8.3. Signalling for fault monitoring and notification 1419
8.4. Signalling for synchronization of user session information among BNGs 1419
8.5. Signalling for user traffic scheduling among BNGs 1420
Annex A. The scenarios related to BNG pool 1422
Appendix A. The networking methods of BNG pool 1424
3.4. Service plane 1426
The framework and overview of cloud computing interoperability testing 1426
Summary 1427
1. Scope 1429
2. References 1429
3. Definitions 1429
3.1. Terms defined elsewhere 1429
3.2. Terms defined in this Recommendation 1429
4. Abbreviations and acronyms 1430
5. Overview of cloud computing interoperability testing 1430
5.1. Common aspects to be considered in cloud computing interoperability testing 1432
5.2. Infrastructure capabilities type interoperability testing 1433
5.3. Platform capabilities type interoperability testing 1433
5.4. Application capabilities type interoperability testing 1434
6. Cloud computing interoperability testing between CSC and CSP 1434
7. Cloud computing interoperability testing between CSP and CSP 1436
8. Cloud computing interoperability testing between CSP and its management system 1438
Appendix I. Cloud interoperability testing scenarios 1440
Bibliography 1440
Future networks: Objectives and design goals 16
Figure 1 - Four objectives and twelve design goals of future networks 16
Framework of data aware networking for future networks 36
Figure 1 - Use cases of data aware networking 36
Data Aware Networking (Information Centric Networking) - Requirements and Capabilities 51
Figure 1 - Overall network structure of DAN 51
Figure 2 - Functional view of DAN capabilities 51
Data aware networking - Scenarios and use cases 60
Figure 7-1 - Content dissemination using DAN 60
Figure 7-2 - Use case of content dissemination with DAN 61
Figure 7-3 - depicts a scenario for sensor networking using DAN 62
Figure 7-4 - Use case of sensor networking with DAN 63
Figure 7-5 - Vehicular networking using DAN 64
Figure 7-6 - Use case of vehicular networking with DAN 65
Figure 7-7 - Automated driving with DAN 66
Figure 7-8 - Use case of automated driving with DAN 67
Figure 7-9 - Networking in a disaster area with DAN 68
Figure 7-10 - Use case of networking in a disaster area with DAN 69
Figure 7-11 - Advanced metering infrastructure in a smart grid 70
Figure 7-12 - Use case of advanced metering infrastructure in a smart grid with DAN 71
Figure 7-13 - Proactive video caching 72
Figure 7-14 - Use case of proactive video caching with DAN 73
Figure 7-15 - In-network data processing with DAN 74
Figure 7-16 - Use case of in-network data processing with DAN 75
Figure 7-17 - Multihoming with DAN 76
Figure 7-18 - Use case of multihoming with DAN 77
Figure 7-19 - Traffic engineering of DAN data flows 78
Figure 7-20 - Use case of traffic engineering DAN 79
Framework of network virtualization for future networks 91
Figure 1 - Conceptual architecture of network virtualization 91
Figure 2 - Concept of LINP provided by network virtualization 92
Functional architecture of network virtualization for future networks 120
Figure 1 - User roles, resources, functions, and reference points in the functional architecture of network virtualization 120
Figure 2 - An example of LINP federation with a LINP exchanger's federation functions 123
Figure 3 - An example of LINP federation without LINP exchangers 124
Figure 4 - Categories of physical resources 125
Figure 5 - An example of an LINP 125
Figure 6 - Allocation 126
Figure 7 - Binding 126
Figure 8 - Physical node architecture 127
Figure 9 - Functional architecture with service deployment functions supported by a service developer 130
Figure 10 - Gateway functions in relation to LINP management functions 131
Figure 11 - User terminal functions in relation to gateway functions 132
Functional architecture of software-defined networking 164
Figure 6-1 - SDN layering framework 164
Figure 7-1 - SDN functional architecture 165
Figure 7-2 - SDN-AL functional components 166
Figure 7-3 - SDN-CL functional components 167
Figure 7-4 - SDN-RL functional components 170
Figure 7-5 - MMF internal structure and reference points 171
Framework of software-defined networking 143
Figure 7-1 - Concept of SDN 143
Figure 11-1 - High-level architecture of SDN 145
Requirements and capability framework for NICE implementation making use of software-defined networking technologies 194
Figure 1 - Capability framework overview of S-NICE 194
Functional architecture for NICE implementation making use of software defined networking technologies 207
Figure 7-1 - Relationship between architectures of NICE and S-NICE 207
Figure 7-2 - Overall functional architecture of S-NICE 208
Figure 7-3 - Detailed functional architectures of S-NICE orchestration functions 209
Figure 7-4 - Detailed functional architectures of S-NICE controller functions 212
Figure 7-5 - Detailed functional architecture of S-NICE infrastructure functions 214
Figure 8-1 - Internal reference points of S-NICE orchestration functions 215
Figure 8-2 - Internal reference points of S-NICE controller functions 216
Figure 8-3 - Internal reference points of S-NICE infrastructure functions 217
Figure 8-4 - Internal reference points of S-NICE 218
Figure 8-5 - External reference points of S-NICE 218
Functional architecture of multi-connection 247
Figure 6-1 - Overview of multi-connection architecture 247
Figure 6-2 - Functional entities supporting multi-connection architecture 247
Figure 6-3 - Multi-connection control function 249
Figure 6-4 - Distinction between SUE and MUE 250
Figure 6-5 - Characteristic of MUE 250
Figure 6-6 - Functional entities in multi-connection architecture 251
Figure 7-1 - Relationship between multi-connection architecture and NGN architecture 254
Intelligent access selection in multi-connection 276
Figure 7-1 - Homogeneous accesses discovery 276
Figure 7-2 - Heterogeneous accesses discovery 276
Figure 7-3 - Terminal-based access discovery 277
Figure 7-4 - Network policy provision flow 278
A multi-path transmission control in multi-connection 288
Figure 7-1 - Functional entities associated with multi-path transmission 288
Figure 9-1 - Path selection procedure initiated by MPT-enhanced MUE 294
Figure 9-2 - Path selection procedure in network-based scenario 295
Figure 9-3 - Traffic adjustment procedure initiated by MPT-enhanced MUE 297
Figure 9-4 - Traffic adjustment procedure initiated by the network 298
Flow-based service continuity in multi-connection 310
Figure 7-1 - Multi-connection flow-based service continuity related functional entities 310
Figure 7-2 - MUE initiated FSC 313
Figure 7-3 - Network initiated FSC 314
Multi-connection requirements 322
Figure 6-1 - Generic multi-connection scenarios 322
Identification and configuration of resources for multi-connection 340
Figure 6-1 - Association of the multi-connection architecture functional entities relative to the general TCP/IP stack 340
Figure 7-1 - Conceptual configuration of multi-connection IDs in the MUE 343
Figure 7-2 - Configuration of interface IDs and access network IDs 343
Figure 7-3 - Configuration of IP flow IDs and interface IDs 344
Figure 7-4 - Configuration of service IDs and session IDs 344
Figure 7-5 - Relationship between resource IDs and multi-connection FEs 345
Capabilities of multi-connection to support streaming services 359
Figure 8-1 - MC-Streaming architecture 359
Figure 8-2 - Functional entities in MC-Streaming architecture 360
Figure 9-1 - Authorization and streaming establishment 363
Figure 9-2 - Streaming decomposition 364
Figure 9-3 - Streaming composition 366
Figure 9-4 - MUE initiated streaming transfer 367
Figure 9-5 - Network initiated streaming transfer 368
Capabilities of multi-connection to support enhanced multimedia telephony services 388
Figure 7-1 - Architecture of eMMTel over multi-connection 388
Figure 9-1 - Enriched call composition 392
Figure 9-2 - Enriched call decomposition 394
Figure 9-3 - Content sharing during a voice call 395
Figure 9-4 - Content sharing flow transfer without a voice call 396
Figure 9-5 - Enhanced file transfer related to the call 397
Figure 9-6 - Enhanced file transfer unrelated to the call 398
Figure 9-7 - Call-related enhanced messaging 399
FMC service using legacy PSTN or ISDN as the fixed access network for mobile network users 435
Figure 1 - The functional model of the PAM service using a discrete PAM service number 435
Figure 2 - The functional model of the PAM service using a MSISDN as the PAM service number 435
Figure 3 - Scenario for assigning FEs to different physical nodes when using a discrete PAM service number 442
Figure 4 - Scenario for assigning functional entities to the same physical node when using a discrete PAM service number 443
Figure 5 - Scenario for assigning FEs to different physical nodes when using MSISDN as the PAM service number 443
Figure 6 - Scenario for assigning FEs to the same physical node when using MSISDN as the PAM service number 444
Figure 7a - The network configuration of the PAM service using MSISDN as the PAM service number for a GSM/UTRAN mobile network 447
Figure 7b - The network configuration of the PAM service using MSISDN as the PAM service number for an ANSI-41/cdma2000 mobile network 447
Figure 8 - User registration call flow 450
Figure 9 - User deregistration call flow 452
Figure 10 - Originating call flow 453
Figure 11 - Terminating call flow 454
Mobility management and control framework and architecture within the NGN transport stratum 463
Figure 1 - Position of mobility management and control in the NGN transport stratum architecture 463
Figure 2 - Relations of HDC-FE sub-functions 467
Figure 3 - Reference points and information flows involved in mobility management and control 469
Figure 4 - Overview of the handover process 480
Figure 5 - Information flows for attachment in the case of host-based 482
Figure 6 - Information flows for attachment, case of network-based mobility 484
Figure 7 - Illustration of network discovery and decision procedure - Network-triggered handover 487
Figure 8 - Information flow for pre-authentication 488
Figure 9 - Procedure for establishing a new layer 3 path 489
Figure 10 - Routing optimization assuming network-based mobility at each end 491
Mobility management framework for applications with multiple devices 512
Figure 5-1 - Mobility management for application using multiple devices 512
Figure 5-2 - Scenario model of application with one-to-multiple devices (Case I) 514
Figure 5-3 - Scenario model of application with multiple device-to-one (Case II) 514
Figure 7-1 - High level architecture for application with multiple devices based on [b-ITU-T Y.2012] 516
Figure 8-1 - Procedure for registration of user and devices 518
Figure 8-2 - Procedure for application with one-to-multiple devices 519
Figure 8-3 - Procedure for application with multiple devices-to-one 520
Overview of the Internet of things 531
Figure 1 - The new dimension introduced in the Internet of things [b-ITU Report] 531
Figure 2 - Technical overview of the IoT 531
Figure 3 - Types of devices and their relationship with physical things 532
Figure 4 - IoT reference model 535
Overview of Smart Farming based on networks 547
Figure 1 - Conceptual diagram of Smart Farming based on networks 547
Figure 2 - Reference model of Smart Farming based on networks 548
Radio-over-fibre (RoF) technologies and their applications 568
Figure 5-1 - Basic concept of a RoF system 568
Figure 6-1 - Configuration examples for transmitting subcarrier signal(s): a) RF-band; b) only IF-band signal; and c) IF-band signal and reference frequency 569
Figure 6-2 - Configuration examples for transmitting equivalent low-pass signal(s): a) only I/Q baseband signals; and b) I/Q baseband signals and reference frequency 571
Figure 6-3 - Configuration examples for transmitting digital signal(s): RF-band pulse 572
Figure 6-4 - Configuration examples for transmitting digitized signal(s): a) digitized RF-band signal(s); b) digitized IF-band signal(s); and c) digitized I/Q baseband signal(s) 573
Figure 6-5 - Configuration examples for analogue relay transmission: a) RF-band signal(s); b) IF-band signal(s); and c) I/Q baseband signals 575
Figure 6-6 - Configuration examples for digital relay transmission: a) digitized RF-band signal(s); b) digitized IF-band signal(s); and c) digitized I/Q baseband signals 575
Figure 7-1 - Schematic block diagram of direct modulation: a) for subcarrier signal(s) transmission; and b) for equivalent low-pass (baseband) signal(s) or digital signal(s) transmission 577
Figure 7-2 - Schematic block diagram of external modulation: a) for subcarrier signal(s) transmission; and b) for equivalent low-pass (baseband) signal(s) or digital signal(s) transmission 578
Figure 7-3 - Schematic block diagram of optical incoherent detection: a) for subcarrier signal(s) transmission; and b) for digital signal(s) transmission 579
Figure 7-4 - Schematic block diagram of optical coherent detection: a) for subcarrier signal(s) transmission; and b) for equivalent low-pass (equivalent baseband) signal(s) transmission 580
Figure 7-5 - Schematic block diagram of SCM transmission 581
Figure 7-6 - Schematic diagram of an aggregated analogue RoF based MFH system. C-RAN: centralized radio access network; BBU: baseband unit; DSP: digital signal processing... 582
Figure 7-7 - Illustration of the channel aggregation principle 582
Figure 7-8 - Schematic block diagram of WDM transmission: a) for subcarrier signal(s) transmission; and b) for equivalent low-pass (equivalent baseband) signal(s) or digital signal(s) transmission 583
Figure 7-9 - Schematic block diagram of multi-level modulation performed in the electrical domain: a) with direct modulation; and b) with external modulation 584
Figure 7-10 - Schematic block diagram of multi-level modulation performed in the optical domain 585
Figure 7-11 - Typical configurations: a) of an analogue RoF system; and b) of a D-RoF system 586
Figure 7-12 - Example configurations of DSP-assisted analogue RoF systems: a) with DSP at the edge of the link for post-compensation; b) with DSP at the edge of the link for... 588
Figure 8-1 - Reference configuration for a RoF over ODN 590
Figure 8-2 - Possible RoF over ODN configurations for a RoF based PON. WM: wavelength multiplexer/demultiplexer 593
Figure 9-1 - General test model for RoF transmission over ODN: a) block diagram of measurement set-up; b) general configuration of E/O converter for direct modulation; and c) general... 594
Figure 9-2 - Typical experimental set-up (upper) and optical power level diagram (lower) 595
Figure 9-3 - Measured symbol constellations and electrical spectra 596
Figure 9-4 - Measured EVMs vs. optical path loss 596
Figure 9-5 - Typical experimental set-up 597
Figure 9-6 - Measured EVMs vs. optical path loss 598
Figure 9-7 - Measured EVMs vs. input RF power 598
Figure 9-8 - Typical experimental set-up (upper) and optical power level diagram (lower) 599
Figure 9-9 - Measured RF spectra before E/O conversion (upper) and after O/E conversion (lower) 600
Figure 9-10 - Measured EVM as a function of an additional optical link loss after 20. km-long SMF transmission 600
Figure 9-11 - Aggregated analogue RoF system with the 36. LTE channels, aggregated in a single optical wavelength 601
Figure 9-12 - Typical experimental set-up and measurement results. IM/DD: intensity modulation with direct detection 601
Figure 9-13 - Measured EVMs of all the 36 LTE channels after transmission through the aggregated analogue RoF-based MFH system 602
Figure 9-14 - Linear gains, power averages, and power-efficiency gains (benefits) of various OFDM formats. DCO: down-converter-offset OFDM; AC: asymmetrically clipped OFDM... 603
Figure 9-15 - a) Simulated optical spectrum of 24, 20 MHz LTE signals (and their images due to Hermitian symmetry) that are aggregated using the odd-channel-only mapping under... 604
Figure 9-16 - Typical experimental set-up for evaluating the performance of the proposed soft-clipping technique 604
Figure 9-17 - a) Experimentally measured spectrum of the aggregated signals after 20 km SSMF transmission with a received power of -22 dBm and b) Measured EVM vs. received... 605
Figure 9-18 - a) Experimentally measured spectrum of the aggregated signals after 20 km SSMF transmission with a received power of -22 dBm; and b) Measured EVM vs. receiver power... 606
Figure 9-19 - Experimentally measured spectrum of 48, 20 MHz LTE signals (and their images due to Hermitian symmetry) that are aggregated using seamless channel mapping and... 607
Figure 9-20 - The EVMs of all the 48 LTE signals measured under three conditions: a) optical back-to-back (L = 0 km) at PRX = -6 dBm; b) after 5 km SSMF transmission (L = 5 km)... 607
Figure 9-21 - a) The mean EVM of the aggregated LTE signals as a function of optical path loss and received optical power for L = 0 km and L = 5 km; and b) a typical recovered 64-QAM... 608
Figure 9-22 - Typical experimental set-up 609
Figure 9-23 - Measured EVM as a function of optical path loss to evaluate the available dynamic range of optical path loss 610
Figure 9-24 - Measured EVM as a function of input RF power to evaluate the minimum input RF power 610
OTN transport of CPRI signals 624
Figure 8-1 - OPU2r overhead 624
Figure 8-2 - OPU2r multiframe identifier (OMFI) overhead 625
Figure 8-3 - Mapping of six [CPRI] option 3 signals into the OPU2r payload 626
Figure 8-4 - Mapping of three [CPRI] option 4 (after padding) or 5 signals into the OPU2r payload 626
Fast access to subscriber terminals (G.fast) - Power spectral density specification 636
Figure 6-1 - Low-frequency edge stop-band mask 636
Figure 7-1 - In-band limit PSD mask for 106 MHz profile 637
Figure 7-2 - In-band limit PSD mask for 212 MHz profile 638
Figure 7-3 - Low-frequency edge out-of-band LPM 639
Figure 7-4 - High-frequency edge out-of-band LPM 639
Fast access to subscriber terminals (G.fast) - Physical layer specification 664
Figure 5-1 - Reference model of FTTdp deployment (shown for line 1 of N lines connected to a DPU) 664
Figure 5-2 - Reference model of the DPU (shown for line 1 of N lines connected to the DPU) 665
Figure 5-3 - Reference model of NT-n 667
Figure 5-4 - Application reference model for FTTdp with POTS 668
Figure 5-5 - Application reference model for FTTdp with reverse powering and POTS 669
Figure 5-6 - Application reference model for FTTdp with reverse powering and derived POTS 670
Figure 5-7 - Application reference model for FTTdp with reverse powering and derived POTS not sharing the in-premises wiring with ITU-T G.9701 671
Figure 5-8 - Electrical reference model for FTTdp with reverse powering and (derived) POTS 672
Figure 5-9 - FTU protocol reference model 673
Figure 5-10 - Data plane protocol reference model 674
Figure 5-11 - FTU functional model 675
Figure 7-1 - Relation between ITU-T G.9700 PSD masking functions, DPU-MIB configuration parameters, ITU-T G.9701 transceiver control parameters and final transmit PSD mask (at U-interface) 680
Figure 7-2 - Illustration of a MIBPSDMASK when no LESM is specified 682
Figure 7-3 - Illustration of the one-slope steep upward shape 683
Figure 8-1 - Functional reference model of the TPS-TC (FTU-O) 692
Figure 8-2 - Functional reference model of the TPS-TC (FTU-R) 693
Figure 8-3 - Data flow primitives 696
Figure 8-4 - Generic DTU format 700
Figure 8-5 - Bit mapping generic DTU header bytes 700
Figure 8-6 - PTM-TC DTU payload format 702
Figure 8-7 - Format of the DTU frame header 703
Figure 8-8 - Example of mapping of packets for transmission in DTUs 705
Figure 8-9 - NTR phase offset estimation 706
Figure 8-10 - NTR offset recording and communication timeline 706
Figure 8-11 - End-to-end system reference model for time-of-day transport 707
Figure 8-12 - Definition of reference sample in a symbol i (see clause 10.4.4 for details) 708
Figure 8-13 - Reference samples of events t1, t2, t3, t4 and a timeline of eoc command transmission 709
Figure 8-14 - ToD phase difference (△Φ) computation 710
Figure 9-1 - Functional reference model of PMS-TC 712
Figure 9-2 - Illustration of the block interleaver (D = Q and N = NFEC) 715
Figure 9-3 - Multiplexing of RMC frame and DTUs into data frames 716
Figure 9-4 - Example of downstream data frame generation and time alignment of DTUs and RMC frames with symbols 717
Figure 9-5 - RMC frame format 718
Figure 9-6 - RMC scrambler 718
Figure 9-7 - RMC message format 719
Figure 9-8 - Example acknowledging downstream DTUs, U-R reference point 730
Figure 9-9 - Example acknowledging upstream DTUs, U-O reference point 730
Figure 9-9.1 - Illustration of definition of Qtx 732
Figure 9-10 - Definition of Tack and Tret 732
Figure 10-1 - PMD functional reference model 740
Figure 10-2 - Functional model of the data symbol encoder 743
Figure 10-3 - Order of bit extraction from data frame 744
Figure 10-4 - Example of tone ordering and pairing including one-bit subcarriers 747
Figure 10-5 - Bit conversion by trellis encoder 750
Figure 10-6 - Conversion of u to v and w 751
Figure 10-7 - Convolutional encoder: Finite state machine representation 751
Figure 10-8 - Mapping of 2-dimensional cosets 752
Figure 10-9 - Trellis diagram 753
Figure 10-10 - Constellation labels for b = 2 and b = 4 755
Figure 10-11 - Constellation labels for b = 1 755
Figure 10-12 - Combination of a pair of 1-bit constellations to build a 2-bit constellation 756
Figure 10-13 - Constellation labels for b = 3 756
Figure 10-14 - Constellation labels for b = 5 757
Figure 10-15 - Bit generator 763
Figure 10-16 - Vectored group functional model of PMD sub-layer using N×N precoder for downstream vectoring 764
Figure 10-17 - Definition of the normalized error sample E 765
Figure 10-18 - Functional reference model of FTU-R for the definition of DFT output samples over the sync symbol 766
Figure 10-19 - Example of two registers, each representing a VF sample component 770
Figure 10-20 - Example of reported bits for a block of VF samples for different padding types without rounding 770
Figure 10-21 - Example of reported bits for a block of VF samples for different padding types with round 771
Figure 10-22 - VFRB format (in case only vectored bands 1 and 3 are requested by the VCE) 773
Figure 10-23 - VBB format depending on F_block 773
Figure 10-24 - Format of a VF block 775
Figure 10-25 - Cyclic extension, windowing and overlap of symbols 779
Figure 10-26 - TDD frame structure 781
Figure 10-27 - Example of sync symbol and RMC symbol positions 782
Figure 10-28 - Superframe structure 783
Figure 10-29 - General illustration of discontinuous operation in the DOI for downstream logical frames 786
Figure 10-30 - General illustration of discontinuous operation in the DOI of upstream logical frames 787
Figure 11-1 - OAM protocol reference model of ITU-T G.9701 link 788
Figure 11-2 - eoc packet format containing m eoc messages with length P1, P2, ... Pm bytes 792
Figure 11-3 - Control field format 792
Figure 11-4 - eoc message format 793
Figure 11-5 - Timing diagram of the upstream probe sequence update command and response 824
Figure 11-6 - Timing diagram of the downstream probe sequence update command and response 825
Figure 11-7 - Voltage across the load without access cabling 845
Figure 11-8 - Voltage across the load with access cabling inserted 845
Figure 11-9 - Voltage across the load without access cabling 854
Figure 11-10 - Voltage across the load with access cabling inserted 855
Figure 11-11 - Voltage across the load without access cabling 856
Figure 11-12 - Voltage across the load with access cabling inserted 856
Figure 12-1 - Link states and link-state transition diagram 861
Figure 12-2 - Example of L0. link state operation in the downstream direction 862
Figure 12-3 - Example of L0. link state operation with limited transmission time in the downstream direction 863
Figure 12-4 - State diagram for the FTU-O 870
Figure 12-5 - State diagram for the FTU-R 871
Figure 12-6 - Structure of SOC message transmitted using HDLC-like frame 877
Figure 12-7 - Timeline of the initialization procedure 882
Figure 12-8 - The details of early stages of the channel discovery phase 894
Figure 12-9 - The details of the later stages of the channel discovery phase 895
Figure 12-10 - SOC message exchange during the channel discovery phase 900
Figure 12-10.1 - Reference timing diagram of a superframe for construction and placement of an O-P-SYNCHRO signal 915
Figure 12-11 - Vectoring feedback timing diagram 922
Figure 12-12 - Timing diagram of the channel analysis and exchange phase 925
Figure 12-13 - SOC messages exchanged during the channel analysis and exchange phase 926
Figure 12-14 - Illustration of CIpolicy = 0 946
Figure 13-1 - SRA downshift procedure 950
Figure 13-2 - SRA upshift procedure 951
Figure 13-3 - Timing diagram of SRA transition 952
Figure 13-4 - Example of mapping of retransmitted DTU and DTU 1 of old DTU size into a larger new DTU size 953
Figure 13-5 - Example of mapping of retransmitted and new DTU during the transition time of delay_max 953
Figure 13-6 - TIGA procedure with non-segmented messages 959
Figure 13-7 - Flowchart of TIGA procedure 960
Figure 13-8 - Example L2.1 transmission format for N=2, MSF = 8 967
Interfaces for the optical transport network 1082
Figure 5-1 - OTU, ODU and OPU overhead 1082
Figure 6-1 - Digital structure of the OTN interfaces 1083
Figure 6-2 - Optical structure of the OTN interfaces 1084
Figure 6-3 - MOTUm interface principal information containment relationships 1085
Figure 6-4 - B100G MOTUm interface principal information containment relationships 1085
Figure 6-5 - SOTU interface principal information containment relationships 1085
Figure 6-6 - MOTU interface principal information containment relationships 1086
Figure 6-7 - Multi-lane SOTU interface principal information containment relationships 1086
Figure 6-8 - SOTUm interface principal information containment relationships 1087
Figure 7-1 - OTN multiplexing and mapping structures 1088
Figure 7-2 - ODU1 into ODU2 multiplexing method via ODTUG2 (PT=20) 1094
Figure 7-3 - ODU1 and ODU2 into ODU3 multiplexing method via ODTUG3 (PT=20) 1095
Figure 7-4 - ODU0 into ODU1 multiplexing method via ODTUG1 (PT=20) 1095
Figure 7-5 - ODU0, ODU1 and ODUflex into ODU2 multiplexing method via ODTUG2 (PT=21) 1096
Figure 7-6 - ODU0, ODU1, ODU2, ODU2e and ODUflex into ODU3 multiplexing method via ODTUG3 (PT=21) 1097
Figure 7-7 - ODU0, ODU1, ODU2, ODU2e, ODU3 and ODUflex into ODU4 multiplexing method via ODTUG4 (PT=21) 1098
Figure 7-8 - ODU0, ODU1, ODU2, ODU2e, ODU3, ODU4 and ODUflex into ODUCn multiplexing method via ODTUGCn (PT=22) 1098
Figure 10-1 - OCh information structure 1100
Figure 10-2 - OTSiA information structure 1100
Figure 11-1 - OTUk frame structure 1101
Figure 11-2 - Transmission order of the OTUk frame bits 1101
Figure 11-3 - Frame synchronous scrambler 1102
Figure 11-4 - OTUCn frame structure 1103
Figure 12-1 - ODU frame structure 1103
Figure 12-2 - ODUflex clock generation for CBR signals 1105
Figure 12-3 - ODUflex clock generation for GFP-F mapped packet client signals 1106
Figure 12-4 - ODUflex clock generation for IMP mapped packet client signals 1107
Figure 13-1 - OPU frame structure 1107
Figure 15-1 - OTS-O, OMS-O, OCh-O and OTSiG-O information carried within the OSC 1108
Figure 15-2 - OCh-O information carried within the OCC 1109
Figure 15-3 - OTUk frame structure, frame alignment and OTUk overhead 1109
Figure 15-4 - OTUCn frame structure, frame alignment and OTUCn overhead 1110
Figure 15-5 - ODUk frame structure, ODUk and OPUk overhead 1111
Figure 15-6 - ODUCn frame structure, ODUCn and OPUCn overhead 1112
Figure 15-7 - TTI structure 1114
Figure 15-8 - Access point identifier structure 1115
Figure 15-9 - OTU/ODU frame alignment overhead 1118
Figure 15-10 - Frame alignment signal overhead structure 1118
Figure 15-11 - Multiframe alignment signal overhead 1119
Figure 15-12 - OTU overhead 1119
Figure 15-13 - OTU section monitoring overhead 1120
Figure 15-14 - OTU SM BIP-8 computation 1121
Figure 15-15 - OTUCn GCC0 transmission order 1123
Figure 15-16 - Timing diagram example for OTUk 1125
Figure 15-17 - ODU overhead 1126
Figure 15-18 - ODU path monitoring overhead 1126
Figure 15-19 - ODU tandem connection monitoring #i overhead 1126
Figure 15-20 - ODU PM BIP-8 computation 1128
Figure 15-21 - Example of nested and cascaded ODU monitored connections 1132
Figure 15-22 - Example of overlapping ODU monitored connections 1132
Figure 15-23 - ODU TCM BIP-8 computation 1133
Figure 15-24 - Example of TCM overhead field assignment 1135
Figure 15-25 - OTUCn GCC1, GCC2 and GCC1+2 transmission order 1137
Figure 15-26 - OPU overhead 1139
Figure 16-1 - OTUk-AIS 1143
Figure 16-2 - OTUCn-AIS 1143
Figure 16-3 - ODU-AIS 1144
Figure 16-4 - ODUk-OCI 1144
Figure 16-5 - ODU-LCK 1145
Figure 16-6 - Generic-AIS generating circuit 1145
Figure 17-1 - OPUk frame structure for the mapping of a CBR2G5, CBR10G or CBR40G signal 1147
Figure 17-2 - Mapping of a CBR2G5 signal into OPU1 1149
Figure 17-3 - Mapping of a CBR10G signal into OPU2 1149
Figure 17-4 - Mapping of a CBR40G signal into OPU3 1149
Figure 17-5 - Mapping of a CBR10G3 signal into OPU2e 1150
Figure 17-6 - OPUk frame structure and mapping of GFP frames into OPUk 1150
Figure 17-7 - OPU2 frame structure and mapping of GFP frames into an extended OPU2 payload area 1151
Figure 17-8 - OPU frame structure and mapping of a NULL client into OPU 1152
Figure 17-9 - OPU frame structure and mapping of 2 147 483 647-bit pseudo-random test sequence into OPU 1152
Figure 17-10 - OPUk frame structure for the mapping of a synchronous constant bit stream 1153
Figure 17-11 - OPU0 frame structure for the mapping of a sub-1.238 Gbit/s client signal 1155
Figure 17-12 - OPU1 frame structure for the mapping of a supra-1.238 to sub-2.488 Gbit/s client signal 1157
Figure 17-13 - OPU2 frame structure for the mapping of a CBR client signal 1159
Figure 17-14 - OPU3 frame structure for the mapping of a CBR client signal 1160
Figure 17-15 - OPU4 frame structure for the mapping of a CBR client signal 1161
Figure 17-16 - Mapping of transcoded FC-1200 into OPU2e 1163
Figure 17-17 - GFP frame format for FC-1200 1164
Figure 17-18 - OPUflex frame structure for the mapping of a supra-2.488 Gbit/s client signal 1166
Figure 17-19 - OPUflex frame structure for the mapping of a FlexE client signal 1169
Figure 17-20 - Full/partial rate FlexE signal interleaving 1170
Figure 17-21 - Sigma-delta accumulator for deterministic justification generation 1171
Figure 17-22 - Mapping of the combined FlexE stream into ODUflex via deterministic stuffing and using GMP encoding 1172
Figure 17-23 - OPUflex frame structure for the mapping of a 64b/66b PCS client signal with 2-bit alignment 1173
Figure 19-1 - OPU2 tributary slot allocation 1176
Figure 19-2 - OPU3 tributary slot allocation 1177
Figure 19-3 - OPU1 tributary slot allocation 1179
Figure 19-4A - OPU4 1.25G tributary slot allocation 1180
Figure 19-4B - OPU4 tributary slots in 160 row x 7620 column format 1180
Figure 19-5 - ODTUjk frame formats 1182
Figure 19-6 - ODTUk.ts frame formats 1183
Figure 19-7 - Mapping of ODTU12. into one OPU2 2.5G tributary slot (left) and two OPU2 1.25G tributary slots (right) 1184
Figure 19-8 - Mapping of ODTU13. into one OPU3 2.5G tributary slot (left) and two OPU3 1.25G tributary slots (right) 1185
Figure 19-9 - Mapping of ODTU23 into 4 OPU3 2.5G tributary slots (#A, #B, #C, #D with A〈B〈C〈D) (top) and 8 OPU3 1.25G tributary slots (#A, #B, #C, #D, #E, #F, #G, #H with A〈B〈C〈D〈E〈F〈G〈H) (bottom) 1186
Figure 19-10 - Mapping of ODTU01 (excluding JOH) into OPU1 1.25G tributary slot 1187
Figure 19-11 - Mapping of ODTU2.ts into 'ts' OPU2 1.25G tributary slots 1188
Figure 19-12 - Mapping of ODTU3.ts into 'ts' OPU3 1.25G tributary slots 1189
Figure 19-13 - Mapping of ODTU4.ts into 'ts' OPU4 1.25G tributary slots 1190
Figure 19-14A - OPUk (k=1, 2, 3) multiplex overhead associated with an ODTUjk only (payload type = 20) 1192
Figure 19-14B - OPUk (k=2, 3) multiplex overhead associated with an ODTUjk only (payload type = 21) 1193
Figure 19-14C - OPUk (k=2, 3, 4) multiplex overhead associated with an ODTUk.ts (payload type = 21) 1194
Figure 19-15 - OPU2-MSI coding - Payload type 20 1195
Figure 19-16A - OPU3-MSI coding - Payload type 20 1195
Figure 19-16B - OPU3 MSI coding - Payload type 20 1196
Figure 19-17 - OPU1 MSI coding - Payload type 20 1196
Figure 19-18A - OPU4 1.25G TS MSI coding - Payload type 21 1197
Figure 19-18B - OPU4 MSI coding - Payload type 21 1197
Figure 19-19A - OPU2 MSI coding - Payload type 21 1198
Figure 19-19B - OPU2 MSI coding - Payload type 21 1198
Figure 19-20A - OPU3 MSI coding - Payload type 21 1199
Figure 19-20B - OPU3 MSI coding - Payload type 21 1199
Figure 19-21 - OPU4 multiframe identifier (OMFI) overhead 1200
Figure 19-22 - Extended ODUj frame structure (FA OH included, OTUj OH area contains fixed stuff) 1201
Figure 19-23A - ODTU12 frame format and mapping of ODU1 (mapping in 2.5G TS1) 1202
Figure 19-23B - ODTU12 frame format and mapping of ODU1 (mapping in 1.25G TS1 and TS4) 1203
Figure 19-24A - ODTU13 frame format and mapping of ODU1 (mapping in 2.5G TS3) 1204
Figure 19-24B - ODTU13 frame format and mapping of ODU1 (mapping in 1.25G TS2 and TS25) 1205
Figure 19-25A - ODTU23 frame format and mapping of ODU2 (mapping in 2.5G TS 1, 5, 9, 10) 1206
Figure 19-25B - ODTU23 frame format and mapping of ODU2 (mapping in 1.25G TS 1, 2, 5, 9, 10, 25, 26, 32) 1207
Figure 19-26 - Mapping of ODU0. in OPU1 TS1 1208
Figure 19-27 - ODTU2.M GMP byte numbering 1210
Figure 19-28 - ODTU3.M GMP byte numbering 1210
Figure 19-29 - ODTU4.M GMP byte numbering 1211
Figure 20-1 - OPUC tributary slot allocation in 80 row x 3810 column format 1213
Figure 20-2 - OPUC tributary slot allocation in 8 row x 38100 column format 1214
Figure 20-3 - OPUCn tributary slot allocation with n OPUC 16-byte interleaved 1215
Figure 20-4 - ODTUCn.ts frame formats 1217
Figure 20-5 - OPUCn TS order 1217
Figure 20-6 - Mapping of ODTUCn.ts into 'ts' OPUCn 5G tributary slots 1218
Figure 20-7 - OPUCn multiplex overhead (payload type = 22) 1219
Figure 20-8 - OPUCn 5G TS MSI coding - Payload type 22 1220
Figure 20-9 - OPUCn MSI coding - Payload type 22 1220
Figure 20-10- OPUCn multiframe identifier (OMFI) overhead 1221
Figure 20-11 - ODTUCn.M GMP 16-byte block numbering 1224
Flexible OTN short-reach interface 1301
Figure 6-1 - Example FlexO handoff router-transport 1301
Figure 6-2 - Example FlexO inter-domain handoff 1302
Figure 7-1 - FlexO group principal information containment relationship 1303
Figure 8-1 - FlexO frame structure 1304
Figure 8-2 - FlexO multi-frame structure 1305
Figure 9-1 - Overhead overview 1306
Figure 9-2 - FlexO lane alignment marker format 1306
Figure 9-3 - 100G FlexO alignment marker area with four interleaved lane alignment markers and padding 1307
Figure 9-4 - FlexO OH structure 1308
Figure 9-5 - Multi-frame alignment signal overhead 1309
Figure 9-6 - FlexO PHY MAP field 1310
Figure 9-7 - FlexO OH STAT field 1310
Figure 9-8 - FCC transmission order 1311
Figure 9-9 - OSMC transmission order 1311
Figure 9-10 - Timing diagram example for OSMC 1312
Figure 10-1 - OTUCn divided onto n OTUC 1313
Figure 10-2A - OTUC mapped into 100G FlexO frame payload 1314
Figure 10-3 - FlexO scrambler 1315
Figure 10-4 - FlexO scrambler after AM and FEC insertion 1315
Signalling architecture for the control plane of distributed service networking 1324
Figure 6-1 - DSN functional architecture 1324
Figure 7-1 - PEs and interfaces of DSN architecture for content services 1327
Figure 7-2 - PEs and interfaces of DSN architecture for MMTel service 1328
Framework of signalling for software-defined networking 1337
Figure 6-1 - Hybrid network model 1337
Figure 6-2 - Middleboxes in the fixed and mobile networks 1338
Figure 6-3 - White-boxes in the fixed and mobile networks 1338
Figure 7-1 - The signalling model of SDN framework 1340
Figure 9-1 - VM live migration procedures 1342
Signalling requirements for flexible network service combination on broadband network gateway 1354
Figure 1 - Architecture for BNG with flexible network service combination 1354
Figure 2 - Service management message types 1355
Figure 3 - Message composition 1355
Figure 4 - Service configuration message types on BNG 1360
Figure 5 - Messages types for the BNG resource, events and status notifications 1362
Signalling requirements for software-defined broadband access network 1381
Figure 6-1 - Ring structure of BAN 1381
Figure 6-2 - SBAN model 1382
Figure 7-1 - SBAN node initialization 1383
Figure 8-1 - Message composition 1384
Scenarios and signalling requirements of unified intelligent programmable interface for IPv6 1404
Figure 6-1 - Scenario and use case of this Recommendation 1404
Figure 7-1 - Signalling interface 1405
Figure 9-1 - Signalling procedures of this Recommendation 1407
The framework and overview of cloud computing 1416
Figure 7-1 - The Architecture of the BNG Pool 1416
Figure 8-1 - The membership management and configuration procedure 1417
Figure 8-2 - The address pool management procedure 1418
Figure 8-3 - The load balancing procedure 1420
Figure 8-4 - The fault protection procedure 1421
The framework and overview of cloud computing interoperability testing 1431
Figure 1 - Target areas of cloud computing interoperability testing 1431
Figure 2 - Functional components of the CCRA 1432
Figure 3 - Relationships among functional components and functions for the "use cloud service" activity between CSC and CSP 1436
Data aware networking - Scenarios and use cases 81
Figure I.1 - Packet loss versus number of connections that simultaneously connect to an original content holder 81
Figure II.1 - Protocol stack of advanced metering infrastructure with DAN in [b-Yu, 2014] 82
Figure II.2 - Bandwidth consumptions in DAN-AMI and IP-AMI (see [b-Yu, 2014] for details) 82
Figure III.1 - Experimental setup for proactive caching mechanism with DAN 83
Figure III.2 - Variations of throughputs as a mobile user on a train moves from station A to C 83
Framework of network virtualization for future networks 101
Figure II.1 - Use cases of user and application mobility 101
Figure II.2 - Use cases of system image and resource mobility 101
Figure II.3 - Use cases of partitioning and aggregation of wireless access network virtualization 103
Figure II.4 - Composite use case of wireless access network virtualization 104
Requirements of network virtualization for future networks 114
Figure I.1 - Resource hierarchical model 114
Functional architecture of network virtualization for future networks 135
Figure I.1 - VNode system components and interfaces 135
Figure I.2 - An example of virtual network and its implementation using VNode system 136
Functional architecture for NICE implementation making use of software defined networking technologies 220
Figure I.1 - Implementation flows of on-demand provision 220
Figure I.2 - Implementation flows of resource guarantee based on network awareness 221
Figure I.3 - Implementation flows of traffic scheduling based on network awareness 222
Requirements of soft network architecture for mobile 231
Figure I.1 - Flexible traffic steering scenario 231
Figure I.2 - Fast deployment 232
Figure I.3 - Scaling out/in 233
Figure I.4 - SAME network slice for MVNO scenario 234
Figure I.5 - Centralized control function and forwarding function 235
Figure I.6 - Traffic localization and latency reduction 235
Figure I.7 - Traffic scheduling optimization 236
Figure III.1 - Mapping between scenarios, problems, design principles and requirements 239
Functional architecture of multi-connection 257
Figure II.1 - Mapping of baseline to 3GPP EPC/IMS 257
Figure III.1 - Mapping of baseline to NGH/IMS 258
Figure IV.1 - Adding a new connection 259
Figure IV.2 - Deleting or updating a connection 260
Figure IV.3 - MUE initialled IP flow mobility 261
Figure IV.4 - Network initialled IP flow mobility 262
Figure IV.5 - Service composition during call establishment 263
Figure IV.6 - Service decomposition during call establishment 264
Figure IV.7 - Service decomposition 265
Figure IV.8 - Subscriber attaches to the access network 266
Figure IV.9 - Policy control procedure 266
Multi-connection requirements 330
Figure II.1 - Generic multi-connection scenarios 330
Capabilities of multi-connection to support streaming services 376
Figure I.1 - VoD service continuity 376
Figure I.2 - Video conference service 377
Figure I.3 - Real-time monitor service 377
Capabilities of multi-connection to support enhanced multimedia telephony services 402
Figure I.1 - Scenario of reliability and service continuity 402
Figure I.2 - Scenario of bandwidth aggregation 403
Figure I.3 - Scenario of multiple UE receiving multimedia 403
Figure I.4 - Scenario of UE initiated network selection 404
Figure I.5 - Scenario of network initiated network selection 404
Figure I.6 - Scenario of service transfer 405
Fixed-mobile convergence general requirements 422
Figure I.1 - Scenario: Convergence in service control functions 422
Figure I.2 - Scenario: Convergences in application/service support functions 423
Figure I.3 - Scenario: Convergence in applications 423
Figure I.4 - Scenario: Convergence in charging and billing functions 424
Mobility management and control framework and architecture within the NGN transport stratum 493
Figure I.1 - Non-roaming architecture for network-based mobility using m1 493
Figure I.2 - Non-roaming architecture for host-based mobility using m3 494
Figure I.3 - Non-roaming architecture for host-based mobility using m1 and m2 494
Figure I.4 - Roaming architecture for network-based mobility using m1 495
Figure I.5 - Roaming architecture for network-based mobility using m1 and m4 495
Figure I.6 - Roaming architecture for host-based mobility using m3 496
Figure I.7 - Roaming architecture for host-based mobility using m1 and m2 496
Figure I.8 - Roaming architecture for host-based mobility using m3 and m4 497
Figure I.9 - Roaming architecture for host-based mobility using m1, m2 and m4 497
Figure II.1 - MIPv4 architecture according to the IETF 498
Figure II.2 - Signalling flows for PMIPv6 initial attachment 499
Figure II.3 - PMIPv6 signalling flows for handover 500
Figure III.1 - Non-roaming architecture for 3GPP accesses within EPS using PMIP-based S5 501
Figure III.2 - Roaming architecture for 3GPP accesses within EPS using PMIP-based S8 502
Figure III.3 - Roaming architecture for EPS using S5, S2c - Local breakout 503
Mobility management framework for applications with multiple devices 522
Figure I.1 - Example of application with one-to-multiple devices 522
Figure I.2 - Deployment of applications using MIPv4 (in case of one-to-multiple devices) 523
Figure I.3 - Mobility management procedure based on MIP 524
Overview of the Internet of things 537
Figure I.1 - IoT ecosystem 537
Figure I.2 - Model 1 538
Figure I.3 - Model 2 538
Figure I.4 - Model 3 539
Figure I.5 - Model 4 539
Figure I.6 - Model 5 539
Overview of Smart Farming based on networks 551
Figure I.1 - The cyclic procedures of a convergence service for agriculture 551
Figure II.1 - Environments and deployments of a convergence service for outdoor farming 552
Figure II.2 - Environments and deployments of a convergence service for greenhouse/plant factory farming 553
Figure III.1 - Product flow between producers and consumers 556
Figure III.2 - Product distribution flow at the post-production stage 556
Figure III.3 - Conceptual product flow control for post-production stage 557
Fast access to subscriber terminals (G.fast) - Physical layer specification 1043
Figure I.1 - Modified star wiring topology 1043
Figure I.2 - Distributed wiring topology 1043
Figure I.3 - Overview of the final drop 1043
Figure I.4 - Primary final drop loop (D5) 1044
Figure I.5 - Illustration of final drop loops 1044
Figure I.6 - Overview of the in-premises wiring 1045
Figure I.7 - Illustration of in-premises loops 1046
Figure I.8 - Illustration of the reference combinations 1047
Figure V.1 - Balanced asymmetric ratio 1056
Figure V.2 - Case 2 1056
Figure VI.1 - Discontinuous operation without vectoring (autonomous discontinuous operation) 1058
Figure VI.2 - Example 1: Reduction of vector matrix size in the DOI 1060
Figure VI.3 - Example 2: Avoiding common symbol periods in DOI to turn off crosstalk cancellation processing 1061
Figure VI.4 - Example 3: Two distributed vector groups in DOI 1062
Figure VI.5 - Example 4: Use of idle symbols in case TBUDGET 〈 TTR 1063
Interfaces for the optical transport network 1269
Figure II.1 - OTUk (with RS(255, 239) FEC) 1269
Figure II.2 - OTUk with alternative OTUkV FEC (OTUk-v) 1269
Figure II.3 - OTUk with a smaller OTUkV FEC and the remainder of an FEC area filled with fixed stuff 1270
Figure II.4 - OTUk with a larger OTUkV FEC 1270
Figure II.5 - OTUk without an OTUkV FEC area 1270
Figure II.6 - OTUkV with a different frame structure 1270
Figure II.7 - OTUkV with a different frame structure and without FEC area 1270
Figure II.8 - Asynchronous (or bit-synchronous) mapping of ODUk into OTUkV 1271
Figure III.1 - Example of multiplexing 4 ODU1 signals into an ODU2 1272
Figure III.2 - Example of multiplexing 2 ODU0 signals into an ODU1 1273
Figure V.1 - OPU3-MSI coding for the case of 16 ODU1s into OPU3 1275
Figure V.2 - OPU3-MSI coding for the case of 4 ODU2s into OPU3 TS# (1, 5, 9, 13), (2, 6, 10, 14), (3, 7, 11, 15) and (4, 8, 12, 16) 1275
Figure V.3 - OPU3-MSI coding for the case of 4 ODU2s into OPU3 TS# (1, 5, 9, 10), (2, 3, 11, 12), (4, 14, 15, 16) and (6, 7, 8, 13) 1276
Figure V.4 - OPU3-MSI coding for the case of 5 ODU1s and 2 ODU2s into OPU3. TS# (2), (6), (11), (12), (14), (1, 5, 9, 13) and (4, 8, 10, 16) and OPU3 TS# 3, 7, 15 unallocated (default to ODU1) 1276
Figure XI.1 - Graphical representation of frequency ranges in Table XI.1 1288
Figure XIII.1 - OTUCn sub rate application scenario A 1292
Figure XIII.2 - OTUCn sub rate application scenario B 1292
Figure XIII.3 - OTUCn sub rate mismatch fault condition 1293
Framework of signalling for software-defined networking 1345
Figure I.1 - Seamless handover in SDMNs procedures 1345
Signalling requirements for software-defined broadband access network 1397
Figure I.1 - SBAN node in software-defined IP RAN 1397
The framework and overview of cloud computing 1424
Figure Ap.1 - The networking methods for members of the BNG pool 1424
Annex Tables
Fast access to subscriber terminals (G.fast) - Power spectral density specification 643
Table X.1 - Profile control parameters for operation over coaxial cables 643
Fast access to subscriber terminals (G.fast) - Physical layer specification 990
Table S.1 - NT software management message types 990
Table S.2 - NT software image attributes 991
Table S.3 - NT software image attributes 991
Table S.4 - Get software image message 991
Table S.5 - Get software image response message 992
Table S.6 - Start software download message 993
Table S.7 - Start software download response message 993
Table S.8 - Download section message 994
Table S.9 - Download section response message 995
Table S.10 - End software download message 996
Table S.11 - End software download response message 997
Table S.12 - Activate image message 998
Table S.13 - Activate image response message 999
Table S.14 - Commit image message 999
Table S.15 - Commit image response message 1000
Table X.1 - Annex X profiles for operation over coaxial cables 1012
Table X.2 - DTA-related DRA primitives of the data flow at the γO reference point 1013
Table X.3 - Mds values to support as a function of MF 1013
Table X.4 - RMC commands 1019
Table X.4.1 - DTA update command (sent by the FTU-O only) 1019
Table X.5 - FTU-O CL message NPar(2) bit definitions for Annex X operation 1020
Table X.6 - FTU-O CL message SPar(2) bit definitions 1020
Table X.7 - FTU-O CL message Npar(3) bit definitions 1020
Table X.8 - FTU-O MS message NPar(2) bit definitions 1020
Table X.9 - FTU-O MS message SPar(2) bit definitions 1020
Table X.10 - FTU-O MS message NPar(3) bit definitions 1021
Table X.11 - FTU-R CLR message NPar(2) bit definitions 1021
Table X.12 - FTU-R CLR message SPar(2) bit definitions 1021
Table X.13 - FTU-R CLR message NPar(3) bit definitions 1021
Table X.14 - FTU-R MS message NPar(2) bit definitions 1022
Table X.15 - FTU-R MS message SPar(2) bit definitions 1022
Table X.16 - FTU-R MS message NPar(3) bit definitions 1022
Table X.17 - Annex X parameter field 1022
Table X.18 - Annex X parameter field 1023
Table X.19 - Insertion loss characteristic of coaxial cable types [b-Freeman] 1025
Table X.20 - Exponential approximation of coaxial cable insertion loss coefficients 1027
Table X.21 - Typical coaxial cable characteristic [b-Large] 1028
Table Y.1 - Encoding of queue fill in blocks 1029
Table Y.2 - DRRdata field sent by FTU 1030
Table Z.1 - Information flows at the θO reference point 1035
Table Z.2 - Traffic monitoring parameters at the θO reference point 1035
Table Z.3 - Information flows at the θR reference point 1036
Table Z.4 - Traffic monitoring parameters at the θR reference point 1036
Table Z.5 - Link state primitives at the λO reference point 1036
Table Z.6 - Traffic monitoring primitives at the λR reference point 1036
Table Z.7 - Link state primitives at the λR reference point 1037
Table Z.8 - Link state primitives at the γR reference point 1037
Table Z.9 - Short names for valid link state transitions 1039
Table Z.10 - Valid traffic driven link state transitions 1039
Table Z.11 - Trigger criteria for the valid traffic driven link state transitions 1040
Table Z.12 - Valid battery operation status driven link state transitions 1041
Table Z.13 - Trigger criteria for the valid battery operation status driven link state transitions 1041
Table Z.14 - DPU-MIB configuration parameters related to link state 1042
Interfaces for the optical transport network 1231
Table C.1 - Lane rotation assignments for OTU3 1231
Table C.2 - Lane rotation assignments for OTU4 1232
Table D.1 - OPUk, ODTUk.ts and ODTUCn.ts GMP parameter values 1240
Table D.2 - 14-bit Cm(t) increment and decrement indicator patterns 1241
Table D.3 - 10-bit Cm(t) increment and decrement indicator patterns 1242
Table E.1 - PCS lane alignment marker format for 40GBASE-R 1250
Table E.2 - PCS lane alignment marker format for 100GBASE-R 1250
Annex Figures
Functional architecture of software-defined networking 175
Figure A.1 - Functional elements of the ALM functional component 175
Figure A.2 - Functional elements of the CLM functional component 177
Figure A.3 - Functional elements of the RLM functional component 179
Figure A.4 - Functional elements of the MMO functional component 181
Figure A.5 - Functional elements of the ERM functional component 182
Fast access to subscriber terminals (G.fast) - Physical layer specification 986
Figure S.1 - Software image management reference model 986
Figure S.2. - Message type field subdivision 989
Figure S.3. - Software image state diagram 1001
Figure S.4 - Relationship between image, windows and sections 1002
Figure S.5 - Software download 1003
Figure S.6 - Busy response handling 1004
Figure S.7 - Software activate and commit 1005
Figure X.1 - Reference model of a DPU intended for operation in a crosstalk-free environment 1011
Figure X.2 - TDD frame structure before and after a DTA update 1014
Figure X.3 - Examples to illustrate the impact of a DTA update on the ACK window size 1015
Figure X.4 - Application reference model for coaxial cable medium 1024
Figure X.5 - Coaxial cable configurations for two North American use cases: (a) G.fast with Satellite TV, (b) G.fast only 1024
Figure X.6 - Exponential approximation of insertion loss vs. frequency for RG-6 coaxial cable 1026
Figure X.7 - Exponential approximation of insertion loss vs. frequency for RG-59 coaxial cable 1026
Figure X.8 - Exponential approximation of insertion loss vs. frequency for RG-11 coaxial cable 1027
Figure X.9 - Typical coaxial cable construction [b-Large] 1027
Figure Z.1 - FTU-O reference model with traffic monitoring and cross-layer link state control 1032
Figure Z.2 - FTU-R reference model with traffic monitoring and cross-layer link state control 1032
Figure Z.3 - TMF-O and DRA functional models 1033
Figure Z.4 - TMF-R functional model 1034
Figure Z.5 - DRRUSF functional model 1034
Figure Z.6 - LRCC-O functional model 1038
Interfaces for the optical transport network 1225
Figure A.1 - FEC sub-rows 1225
Figure A.2 - FEC code word 1226
Figure B.1 - Stream of 64B/66B code blocks for transcoding 1227
Figure B.2 - 66B Block coding 1228
Figure B.3 - 513B block code format 1228
Figure B.4 - 513B block's control block header 1229
Figure B.5 - 513B code block components 1230
Figure C.1 - OTU3 and OTU4 frames divided on 16-byte boundary 1231
Figure C.2 - Distribution of bytes from OTU3 to parallel lanes 1233
Figure C.3 - Distribution of bytes from OTU4 to parallel lanes 1233
Figure D.1 - Generic functionality of a mapper/de-mapper circuit 1235
Figure D.2 - Processing flow 1236
Figure D.3 - Sigma-delta based mapping 1236
Figure D.4 - Sigma-delta accumulator 1237
Figure D.5 - Processing flow for GMP in OTN 1239
Figure D.6 - JC1, JC2 and JC3 generation 1243
Figure D.7 - GMP sink count synchronization process representation using the two least significant bits of the count as inputs 1244
Figure D.8 - GMP sink count synchronization process diagram 1245
Figure D.9 - "S"-state interpretation for Figures D.7 and D.8 1245
Figure E.1 - De-skewed/serialized stream of 66B blocks 1249
Figure E.2 - Transcoded lane marker format 1251
Figure F.1 - Flag parity bit on two 513B blocks (1027B code) 1254
Figure F.2 - Receive state machine for the 512B/513B code blocks including lane alignment markers 1257
Figure F.3 - Trans-decode state machine for the 64B/66B code blocks including the lane alignment markers 1258
Figure F.4 - Receive state machine for the lane alignment markers 1258
Figure G.1 - OTU0LL frame structure, overhead and ODU0 mapping 1260
Figure G.2 - Transmission order of the OTU0LL frame bits 1260
Figure G.3 - Frame synchronous scrambler 1261
Signalling requirements for flexible network service combination on broadband network gateway 1364
Figure A.1 - Example of packet processing by network services 1364
Figure A.2 - Scenario of Chrysanthemum service route path 1364
Figure A.3 - Scenario of Lily service route path 1365
Figure A.4 - Scenario of Hybrid service route path 1365
Figure A.5 - Service atoms in the service platform 1366
Figure D.1 - Service/user control procedure 1372
The framework and overview of cloud computing 1422
Figure A.1 - The scenario of BNG pool 1422
MARC 보기
오류 데이터 정정요청
*표시는 필수 입력사항입니다.
알림톡 발송
| *전화번호 | ※ '-' 없이 휴대폰번호를 입력하세요 |
|---|
연속간행물 권호 선택
우편복사 안내
- ◾ 도서관을 방문하지 못할 경우 인터넷, 팩스 등으로 자료 복사를 신청하고, 복사물을 우편·팩스 등으로 제공받는 서비스
- ◾ 대상자료: 일반도서, 연속간행물 및 학위논문
- ※ 고서, 고잡지, 훼손될 우려가 있는 자료, 마이크로폼 자료 및 신문 등 제외
- ◾ 신청 책수: 1인 5책 이하(1일 기준)
- ◾ 신청 절차: 자료 검색 → 우편복사 목록담기 → 복사 범위 입력 → 우편복사 주문서 입력 → 접수 및 확인
- ※ 저작권법에 의거하여 부분 복사(전체 페이지 수의 1/3 범위 이내)만 가능
- ◾ 복사 범위 입력 예시: (연속 페이지) 1-30, (부분 페이지) 25, 30-40
| 번호 | 발행일자 | 권호명 | 제본정보 | 자료실 | 원문 | 신청 페이지 |
|---|
도서위치안내(서울관)
도서위치안내: / 서가번호:
0
확인
우편복사 목록담기를 완료하였습니다.
내서재에 담기
새로운 서재
*표시는 필수 입력사항입니다.
저장
저장 되었습니다.