mirror of
https://github.com/hwanny1128/HGZero.git
synced 2026-06-13 02:29:12 +00:00
작업 파일 정리 및 실시간 회의록 플로우 추가
- 가파팀 프로토타입 파일 삭제 - 가파팀 유저스토리 삭제 - 실시간 회의록 작성 플로우 설계서 추가 (Mermaid, Markdown) - 백업 및 데이터 디렉토리 추가 - AI 데이터 샘플 생성 도구 추가 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,678 @@
|
||||
# 외부 기술 문서 (External Technical Documents) - Glossary Sample Data
|
||||
|
||||
## 개요
|
||||
이 문서는 통신업계의 15개 업무 도메인에 대한 외부 기술 문서 기반 용어집 샘플 데이터를 포함합니다.
|
||||
각 샘플은 국제 표준, 벤더 문서, 산업 프레임워크, 모범 사례 등 외부 출처의 공식 정의를 반영합니다.
|
||||
|
||||
**총 샘플 수**: 225개 (도메인당 15개)
|
||||
**출처 유형**: 3GPP, ITU, IETF, IEEE, ETSI, O-RAN Alliance, TMForum, ISO, Vendor Documentation
|
||||
|
||||
---
|
||||
|
||||
## 1. 네트워크 인프라 (Network Infrastructure) - 15 samples
|
||||
|
||||
JSON 파일에 포함됨 (ext-ni-001 ~ ext-ni-015)
|
||||
|
||||
---
|
||||
|
||||
## 2. 기술 개발 및 연구 (Technology Development & R&D) - 15 samples
|
||||
|
||||
JSON 파일에 포함됨 (ext-td-001 ~ ext-td-015)
|
||||
|
||||
---
|
||||
|
||||
## 3. 고객 서비스 (Customer Service) - 15 samples
|
||||
|
||||
JSON 파일에 포함됨 (ext-cs-001 ~ ext-cs-015)
|
||||
|
||||
---
|
||||
|
||||
## 4. 영업 및 마케팅 (Sales & Marketing)
|
||||
|
||||
### ext-sm-001: ARPU (Average Revenue Per User)
|
||||
- **정의**: Average monthly revenue generated per subscriber, calculated by dividing total revenue by average number of subscribers
|
||||
- **출처**: TMForum GB921 - Revenue Business Entity Definitions v19.0.0
|
||||
- **컨텍스트**: 통신사의 핵심 재무 지표로 고객당 평균 매출 측정. 요금제 전략 및 수익성 평가의 기준
|
||||
- **관련용어**: MOU, Churn Rate, Customer Lifetime Value, Service Revenue
|
||||
- **활용예시**: "Premium segment ARPU increased 15% YoY to $45, driven by 5G adoption and data upselling"
|
||||
- **신뢰도**: 0.98
|
||||
|
||||
### ext-sm-002: Customer Acquisition Cost (CAC)
|
||||
- **정의**: Total sales and marketing expenses required to acquire a new customer, including advertising, commissions, and onboarding costs
|
||||
- **출처**: GSMA Intelligence - Mobile Economy Report 2024
|
||||
- **컨텍스트**: 신규 고객 확보에 소요되는 총 비용. LTV/CAC 비율로 마케팅 효율성 평가
|
||||
- **관련용어**: LTV, Payback Period, Marketing ROI, Acquisition Channel
|
||||
- **활용예시**: "Telecom operators typically aim for LTV:CAC ratio of 3:1 or higher for sustainable growth"
|
||||
- **신뢰도**: 0.96
|
||||
|
||||
### ext-sm-003: Prepaid vs Postpaid Model
|
||||
- **정의**: Two billing models where prepaid requires payment before service usage, while postpaid bills after usage based on actual consumption
|
||||
- **출처**: ITU-T D.270 - Principles applicable to charging and accounting in the provision of mobile cellular services
|
||||
- **컨텍스트**: 통신사의 주요 과금 모델. 시장별·고객층별로 선호도 상이하며 각각 장단점 존재
|
||||
- **관련용어**: Recharge, Credit Limit, Bill Cycle, Payment Method
|
||||
- **활용예시**: "Emerging markets show 70%+ prepaid penetration while mature markets favor postpaid with bundled devices"
|
||||
- **신뢰도**: 0.97
|
||||
|
||||
### ext-sm-004: MVNO (Mobile Virtual Network Operator)
|
||||
- **정의**: Wireless service provider that does not own the wireless network infrastructure, instead leasing capacity from MNOs
|
||||
- **출처**: GSMA - MVNO Market Structure and Dynamics Report
|
||||
- **컨텍스트**: 자체 네트워크 인프라 없이 MNO 도매 서비스를 활용하는 가상 이동통신사업자
|
||||
- **관련용어**: MNO, Wholesale Agreement, MVNE, Brand Reseller, Full MVNO
|
||||
- **활용예시**: "MVNOs captured 15% of European mobile market by targeting niche segments with flexible pricing"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-sm-005: Bundling Strategy
|
||||
- **정의**: Marketing approach combining multiple services (mobile, broadband, TV) into single package at discounted price to increase customer value
|
||||
- **출처**: TMForum GB988 - Customer Experience Management v6.0.0
|
||||
- **컨텍스트**: 다양한 서비스를 결합하여 할인된 가격에 제공함으로써 고객 가치 증대 및 이탈 방지
|
||||
- **관련용어**: Triple Play, Quad Play, Cross-Sell, Package Discount, Convergence
|
||||
- **활용예시**: "Converged bundles reduce churn by 40% compared to standalone mobile services"
|
||||
- **신뢰도**: 0.94
|
||||
|
||||
### ext-sm-006: Promotional Campaign ROI
|
||||
- **정의**: Return on investment for marketing campaigns, measuring revenue generated versus campaign costs over defined period
|
||||
- **출처**: Marketing Accountability Standards Board (MASB) - Marketing Metrics Framework
|
||||
- **컨텍스트**: 프로모션 캠페인의 투자 대비 수익률 측정. 마케팅 예산 최적화의 핵심 지표
|
||||
- **관련용어**: Campaign Attribution, Incremental Revenue, Marketing Mix Modeling, A/B Testing
|
||||
- **활용예시**: "5G launch campaign achieved 250% ROI with 50,000 new activations at $35 CAC"
|
||||
- **신뢰도**: 0.93
|
||||
|
||||
### ext-sm-007: Channel Partner Management
|
||||
- **정의**: Process of recruiting, enabling, and managing third-party sales channels including retailers, dealers, and online partners
|
||||
- **출처**: TMForum GB929 - Partner Business Entity Definitions v19.0.0
|
||||
- **컨텍스트**: 소매점, 대리점, 온라인 파트너 등 제3자 판매 채널의 모집·육성·관리 프로세스
|
||||
- **관련용어**: Channel Conflict, Partner Portal, Commission Structure, Indirect Sales
|
||||
- **활용예시**: "Effective channel management requires balanced incentives, training programs, and performance monitoring"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-sm-008: Product Lifecycle Management
|
||||
- **정의**: Strategic approach managing product evolution from introduction through growth, maturity, and decline phases
|
||||
- **출처**: TMForum GB922 - Product Business Entity Definitions v19.0.0
|
||||
- **컨텍스트**: 제품의 도입·성장·성숙·쇠퇴 단계별 전략적 관리. 시장 변화 및 기술 진화에 대응
|
||||
- **관련용어**: Launch Strategy, Sunset Policy, Product Portfolio, Market Lifecycle
|
||||
- **활용예시**: "3G service sunset requires managed migration of customers to 4G/5G with minimal churn"
|
||||
- **신뢰도**: 0.94
|
||||
|
||||
### ext-sm-009: Market Segmentation
|
||||
- **정의**: Division of broader market into distinct customer groups with similar needs, characteristics, or behaviors for targeted marketing
|
||||
- **출처**: Kotler & Keller - Marketing Management 16th Edition (Industry Standard)
|
||||
- **컨텍스트**: 유사한 니즈·특성·행동을 가진 고객 그룹으로 시장을 세분화하여 타겟 마케팅 수행
|
||||
- **관련용어**: Target Market, Positioning, Demographic Segmentation, Behavioral Segmentation
|
||||
- **활용예시**: "Youth segment prioritizes unlimited data and social media bundles, while business segment values reliability and support"
|
||||
- **신뢰도**: 0.96
|
||||
|
||||
### ext-sm-010: Brand Equity
|
||||
- **정의**: Commercial value derived from consumer perception of brand name rather than product itself, measured by awareness, loyalty, and associations
|
||||
- **출처**: Interbrand - Best Global Brands Methodology
|
||||
- **컨텍스트**: 제품 자체가 아닌 브랜드 인지도·충성도·연상 이미지에서 파생되는 상업적 가치
|
||||
- **관련용어**: Brand Value, Brand Awareness, Brand Loyalty, Brand Association, Net Promoter Score
|
||||
- **활용예시**: "Strong brand equity enables 10-15% price premium over competitors in commoditized telecom markets"
|
||||
- **신뢰도**: 0.93
|
||||
|
||||
### ext-sm-011: Digital Marketing Attribution
|
||||
- **정의**: Process of identifying and assigning credit to digital marketing touchpoints that contribute to customer conversions
|
||||
- **출처**: Google Analytics - Attribution Modeling Best Practices
|
||||
- **컨텍스트**: 고객 전환에 기여한 디지털 마케팅 접점을 식별하고 기여도를 할당하는 프로세스
|
||||
- **관련용어**: Multi-Touch Attribution, First-Click, Last-Click, Linear Attribution, Customer Journey
|
||||
- **활용예시**: "Multi-touch attribution revealed that social media drives awareness while search drives conversion in mobile acquisition"
|
||||
- **신뢰도**: 0.92
|
||||
|
||||
### ext-sm-012: Competitive Intelligence
|
||||
- **정의**: Systematic collection and analysis of competitor information regarding products, pricing, marketing strategies, and market positioning
|
||||
- **출처**: Strategic and Competitive Intelligence Professionals (SCIP) - Best Practices
|
||||
- **컨텍스트**: 경쟁사의 제품·가격·마케팅 전략·시장 포지셔닝 정보를 체계적으로 수집·분석
|
||||
- **관련용어**: Market Analysis, SWOT, Competitive Benchmarking, Market Share, Price Monitoring
|
||||
- **활용예시**: "Real-time competitive intelligence enables rapid response to competitor promotions within 24-48 hours"
|
||||
- **신뢰도**: 0.94
|
||||
|
||||
### ext-sm-013: Customer Lifetime Value (CLV)
|
||||
- **정의**: Predicted net profit attributed to entire future relationship with customer, considering acquisition cost, revenue, and retention probability
|
||||
- **출처**: Harvard Business Review - The Economics of E-Loyalty (Industry Framework)
|
||||
- **컨텍스트**: 고객 관계의 전체 기간 동안 예상되는 순이익. 획득비용·수익·유지율을 고려한 핵심 지표
|
||||
- **관련용어**: CAC, LTV:CAC Ratio, Retention Rate, Churn Probability, Discount Rate
|
||||
- **활용예시**: "High-value postpaid customers show average CLV of $2,500 over 5-year period, justifying premium acquisition spend"
|
||||
- **신뢰도**: 0.97
|
||||
|
||||
### ext-sm-014: Omnichannel Marketing
|
||||
- **정의**: Integrated marketing approach providing seamless customer experience across all channels including online, mobile, social, and physical stores
|
||||
- **출처**: TMForum TR257 - Customer Experience Framework v1.0.0
|
||||
- **컨텍스트**: 온라인·모바일·소셜·매장 등 모든 채널에서 일관된 고객 경험을 제공하는 통합 마케팅
|
||||
- **관련용어**: Cross-Channel, Channel Integration, Customer Journey, Unified Commerce
|
||||
- **활용예시**: "Omnichannel campaigns show 2.5x higher engagement rates compared to single-channel approaches"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-sm-015: Dynamic Pricing
|
||||
- **정의**: Flexible pricing strategy that adjusts prices in real-time based on market demand, competition, inventory, and customer segments
|
||||
- **출처**: McKinsey - Pricing Excellence in Telecommunications (Industry Research)
|
||||
- **컨텍스트**: 시장 수요·경쟁·재고·고객 세그먼트에 따라 실시간으로 가격을 조정하는 유연한 가격 전략
|
||||
- **관련용어**: Surge Pricing, Yield Management, Price Optimization, Algorithmic Pricing
|
||||
- **활용예시**: "Dynamic pricing for data packages during peak hours can increase revenue by 8-12% while managing network load"
|
||||
- **신뢰도**: 0.91
|
||||
|
||||
---
|
||||
|
||||
## 5. 요금 및 청구 (Billing & Revenue)
|
||||
|
||||
### ext-br-001: Convergent Billing
|
||||
- **정의**: Unified billing system capable of rating and charging multiple services (voice, data, video, IoT) on single invoice
|
||||
- **출처**: TMForum GB917 - Rating, Charging and Billing Business Process Framework v19.0.0
|
||||
- **컨텍스트**: 음성·데이터·비디오·IoT 등 다양한 서비스를 단일 청구서로 통합 처리하는 빌링 시스템
|
||||
- **관련용어**: Rating Engine, Charging System, Invoice Consolidation, Multi-Service Billing
|
||||
- **활용예시**: "Convergent billing reduces customer confusion and operational costs by consolidating all services on one bill"
|
||||
- **신뢰도**: 0.97
|
||||
|
||||
### ext-br-002: Real-Time Charging (Online Charging)
|
||||
- **정의**: Charging mechanism that monitors credit/resources in real-time and controls service access based on available balance (3GPP Diameter-based)
|
||||
- **출처**: 3GPP TS 32.240 - Charging architecture and principles
|
||||
- **컨텍스트**: 실시간으로 잔액을 모니터링하고 가용 잔액에 따라 서비스 접근을 제어하는 온라인 과금 방식
|
||||
- **관련용어**: OCS, Diameter Protocol, Credit Control, Session-Based Charging, IEC (Immediate Event Charging)
|
||||
- **활용예시**: "Real-time charging prevents revenue leakage by cutting off service when prepaid balance reaches zero"
|
||||
- **신뢰도**: 0.98
|
||||
|
||||
### ext-br-003: Revenue Assurance
|
||||
- **정의**: Set of processes and controls ensuring all revenue due is billed, collected, and properly accounted for with minimal leakage
|
||||
- **출처**: TM Forum GB1238 - Revenue Assurance Guide v5.0.0
|
||||
- **컨텍스트**: 모든 수익이 정확히 청구·수금·회계처리되도록 보장하는 프로세스 및 통제 시스템
|
||||
- **관련용어**: Revenue Leakage, Fraud Detection, Data Reconciliation, Revenue Recovery
|
||||
- **활용예시**: "Revenue assurance programs typically recover 0.5-2% of total revenue through leakage prevention"
|
||||
- **신뢰도**: 0.96
|
||||
|
||||
### ext-br-004: Mediation System
|
||||
- **정의**: System that collects, aggregates, filters, and formats raw network usage data (CDRs) for billing and analytics systems
|
||||
- **출처**: TMForum GB917 - Rating, Charging and Billing Business Process Framework
|
||||
- **컨텍스트**: 네트워크 원시 사용 데이터(CDR)를 수집·집계·필터링·포맷하여 빌링 및 분석 시스템에 전달
|
||||
- **관련용어**: CDR, Usage Data, Data Aggregation, Rating Engine, ETL
|
||||
- **활용예시**: "Mediation systems process billions of CDRs daily, validating and enriching data before rating"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-br-005: Dunning Management
|
||||
- **정의**: Automated process of communicating with customers to collect overdue payments through escalating reminder sequences
|
||||
- **출처**: TMForum GB921 - Revenue Business Entity Definitions v19.0.0
|
||||
- **컨텍스트**: 연체 고객에게 단계적 알림을 발송하여 미수금을 회수하는 자동화된 프로세스
|
||||
- **관련용어**: Collections, Payment Reminder, Service Suspension, Debt Recovery, Bad Debt
|
||||
- **활용예시**: "Effective dunning reduces bad debt write-offs from 3% to under 1% of total revenue"
|
||||
- **신뢰도**: 0.94
|
||||
|
||||
### ext-br-006: Settlement and Interconnect Billing
|
||||
- **정의**: Process of calculating, invoicing, and reconciling charges between telecom operators for interconnection services
|
||||
- **출처**: ITU-T D.93 - Charging and accounting in the international mobile satellite service
|
||||
- **컨텍스트**: 통신사업자 간 상호접속 서비스에 대한 요금 계산·청구·정산 프로세스
|
||||
- **관련용어**: Wholesale Billing, Interconnect Rates, TAP (Transferred Account Procedure), IOT Testing
|
||||
- **활용예시**: "Interconnect billing manages complex wholesale relationships including voice termination, roaming, and data exchange"
|
||||
- **신�리도**: 0.96
|
||||
|
||||
### ext-br-007: Rating Engine
|
||||
- **정의**: System component that applies pricing rules to usage events to calculate charges based on tariff plans, discounts, and promotions
|
||||
- **출처**: TMForum GB917 - Rating, Charging and Billing Business Process Framework v19.0.0
|
||||
- **컨텍스트**: 사용 이벤트에 요금제·할인·프로모션 규칙을 적용하여 과금액을 계산하는 시스템 컴포넌트
|
||||
- **관련용어**: Tariff Configuration, Usage Rating, Batch Rating, Real-Time Rating, Zone-Based Pricing
|
||||
- **활용예시**: "Modern rating engines support complex scenarios like time-of-day pricing, location-based charges, and tiered bundles"
|
||||
- **신뢰도**: 0.97
|
||||
|
||||
### ext-br-008: Invoice Presentment and Payment (IPP)
|
||||
- **정의**: Digital systems enabling electronic bill delivery and online payment processing for customer convenience and cost reduction
|
||||
- **출처**: NACHA - Electronic Bill Presentment and Payment Best Practices
|
||||
- **컨텍스트**: 전자 청구서 전송 및 온라인 결제 처리를 가능케 하는 디지털 시스템. 편의성 증대 및 비용 절감
|
||||
- **관련용어**: E-Bill, EBPP, Payment Gateway, Bill Aggregator, Digital Wallet
|
||||
- **활용예시**: "Electronic billing reduces invoice delivery costs by 60-70% compared to paper bills while improving payment speed"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-br-009: Taxation and Regulatory Fees
|
||||
- **정의**: Automated calculation and application of government-mandated taxes, fees, and surcharges on telecom services
|
||||
- **출처**: ITU Telecommunication Development Sector - Taxation of Telecommunication/ICT Services
|
||||
- **컨텍스트**: 통신 서비스에 대한 정부 규정 세금·수수료·부담금의 자동 계산 및 적용
|
||||
- **관련용어**: VAT, Excise Tax, USF (Universal Service Fund), Regulatory Compliance, Tax Jurisdiction
|
||||
- **활용예시**: "Telecom tax engines must handle complex rules varying by jurisdiction, service type, and customer classification"
|
||||
- **신뢰도**: 0.96
|
||||
|
||||
### ext-br-010: Prepaid Balance Management
|
||||
- **정의**: Real-time system tracking customer account balance, expiry dates, and allowances for prepaid services
|
||||
- **출처**: 3GPP TS 32.296 - Online Charging System (OCS) applications and interfaces
|
||||
- **컨텍스트**: 선불 서비스 고객의 계정 잔액·만료일·허용량을 실시간으로 추적하는 시스템
|
||||
- **관련용어**: Top-Up, Balance Expiry, Account Hierarchy, OCS, Service Validity Period
|
||||
- **활용예시**: "Prepaid balance management supports complex scenarios like multiple wallets, bonus credits, and rollover allowances"
|
||||
- **신뢰도**: 0.97
|
||||
|
||||
### ext-br-011: Bill Shock Prevention
|
||||
- **정의**: Regulatory requirement and best practice to notify customers approaching usage limits or incurring extraordinary charges
|
||||
- **출처**: BEREC - Guidelines on Transparency Measures for Ensuring Open Internet Access (EU Regulation)
|
||||
- **컨텍스트**: 고객이 사용량 한도 도달 또는 초과 요금 발생 시 알림을 제공하는 규제 요구사항 및 모범 사례
|
||||
- **관련용어**: Usage Alert, Spending Limit, Roaming Cap, Fair Usage Policy, Transparency
|
||||
- **활용예시**: "EU regulations require operators to send alerts at 80%, 100%, and when international roaming charges exceed €50"
|
||||
- **신뢰도**: 0.96
|
||||
|
||||
### ext-br-012: Subscription Management
|
||||
- **정의**: System managing complete subscriber lifecycle including activation, modification, suspension, and termination of services
|
||||
- **출처**: TMForum SID - Subscription Business Entity Model v19.0.0
|
||||
- **컨텍스트**: 가입자의 서비스 활성화·변경·정지·해지 등 전체 생명주기를 관리하는 시스템
|
||||
- **관련용어**: Provisioning, Service Activation, Plan Change, Winback, Subscription Status
|
||||
- **활용예시**: "Subscription management orchestrates complex workflows across billing, network, and CRM systems during plan changes"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-br-013: Discount and Promotion Engine
|
||||
- **정의**: System component applying complex discount rules, promotional offers, and loyalty rewards to customer charges
|
||||
- **출처**: TMForum GB922 - Product Business Entity Definitions (Promotion Management)
|
||||
- **컨텍스트**: 복잡한 할인 규칙·프로모션 오퍼·로열티 리워드를 고객 요금에 적용하는 시스템 컴포넌트
|
||||
- **관련용어**: Campaign Management, Conditional Discounts, Loyalty Points, Time-Limited Offers, Bundling
|
||||
- **활용예시**: "Promotion engines support scenarios like 'buy-one-get-one', graduated discounts, and family plan savings"
|
||||
- **신뢰도**: 0.94
|
||||
|
||||
### ext-br-014: Bad Debt Management
|
||||
- **정의**: Processes and policies for managing uncollectible accounts including write-offs, debt collection agencies, and credit bureau reporting
|
||||
- **출처**: IFRS 9 - Financial Instruments (Expected Credit Loss Model)
|
||||
- **컨텍스트**: 미수금 대손처리·채권추심기관 의뢰·신용정보기관 등록 등 회수 불능 계정 관리 프로세스
|
||||
- **관련용어**: Write-Off, Collection Agency, Credit Score, Provision for Doubtful Debts, Recovery Rate
|
||||
- **활용예시**: "Telecom operators typically write off bad debts after 180-360 days of collection attempts, affecting 1-3% of revenue"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-br-015: Usage-Based Billing
|
||||
- **정의**: Billing model charging customers based on actual consumption of services (data, minutes, messages) rather than fixed fees
|
||||
- **출처**: TMForum GB917 - Rating, Charging and Billing Business Process Framework
|
||||
- **컨텍스트**: 고정 요금이 아닌 실제 서비스 사용량(데이터·통화·메시지)에 기반한 과금 모델
|
||||
- **관련용어**: Metered Billing, Tiered Pricing, Pay-As-You-Go, Overage Charges, Fair Usage Policy
|
||||
- **활용예시**: "IoT services often use usage-based billing to align costs with actual data consumption per device"
|
||||
- **신뢰도**: 0.96
|
||||
|
||||
---
|
||||
|
||||
## 6. 네트워크 운용 (Network Operations)
|
||||
|
||||
### ext-no-001: FCAPS Model
|
||||
- **정의**: ISO network management framework defining five functional areas: Fault, Configuration, Accounting, Performance, and Security management
|
||||
- **출처**: ISO/IEC 7498-4 - OSI Management Framework
|
||||
- **컨텍스트**: 네트워크 관리의 5대 기능 영역을 정의한 ISO 표준 프레임워크. 통신망 운용의 기본 체계
|
||||
- **관련용어**: Fault Management, Configuration Management, Performance Monitoring, Security Management
|
||||
- **활용예시**: "Telecom NOC operations are organized around FCAPS model with specialized teams for each functional area"
|
||||
- **신뢰도**: 0.98
|
||||
|
||||
### ext-no-002: MTTR (Mean Time To Repair)
|
||||
- **정의**: Average time required to repair a failed component or restore service, measured from fault detection to service restoration
|
||||
- **출처**: ITU-T E.800 - Definitions of terms related to quality of service
|
||||
- **컨텍스트**: 장애 감지부터 서비스 복구까지 소요되는 평균 시간. 운용 효율성의 핵심 KPI
|
||||
- **관련용어**: MTBF, Availability, Downtime, Service Restoration, RCA (Root Cause Analysis)
|
||||
- **활용예시**: "5G networks target MTTR under 2 hours for critical infrastructure failures through automated diagnostics"
|
||||
- **신뢰도**: 0.97
|
||||
|
||||
### ext-no-003: MTBF (Mean Time Between Failures)
|
||||
- **정의**: Average time elapsed between two consecutive failures of a system or component, indicating reliability
|
||||
- **출처**: ITU-T E.800 - Definitions of terms related to quality of service
|
||||
- **컨텍스트**: 시스템 또는 구성요소의 연속된 두 장애 사이의 평균 시간. 신뢰성 지표
|
||||
- **관련용어**: Reliability, MTTR, Availability, Failure Rate, Preventive Maintenance
|
||||
- **활용예시**: "Carrier-grade equipment typically specifies MTBF of 100,000+ hours (11+ years)"
|
||||
- **신뢰도**: 0.97
|
||||
|
||||
### ext-no-004: Network Availability
|
||||
- **정의**: Percentage of time that network service is operational and accessible, calculated as (Total Time - Downtime) / Total Time
|
||||
- **출처**: ITU-T E.800 - Definitions of terms related to quality of service
|
||||
- **컨텍스트**: 네트워크 서비스가 운영 가능하고 접근 가능한 시간의 비율. SLA의 핵심 지표
|
||||
- **관련용어**: Uptime, Downtime, Five Nines (99.999%), SLA, Service Reliability
|
||||
- **활용예시**: "Carrier networks target 99.999% availability allowing only 5.26 minutes downtime per year"
|
||||
- **신뢰도**: 0.98
|
||||
|
||||
### ext-no-005: Fault Management System (FMS)
|
||||
- **정의**: Automated system for detecting, isolating, diagnosing, and resolving network faults through event correlation and root cause analysis
|
||||
- **출처**: ITU-T M.3010 - Principles for a telecommunications management network (TMN)
|
||||
- **컨텍스트**: 이벤트 상관분석 및 근본원인 분석을 통해 네트워크 장애를 감지·격리·진단·해결하는 자동화 시스템
|
||||
- **관련용어**: Alarm Management, Event Correlation, Trouble Ticketing, Auto-Remediation, NOC
|
||||
- **활용예시**: "Modern FMS correlates thousands of alarms per second to identify root causes and trigger automated remediation"
|
||||
- **신뢰도**: 0.96
|
||||
|
||||
### ext-no-006: KPI (Key Performance Indicator)
|
||||
- **정의**: Quantifiable metrics measuring critical aspects of network performance including throughput, latency, packet loss, and availability
|
||||
- **출처**: 3GPP TS 32.410-32.425 - Performance Management (PM) KPI definitions
|
||||
- **컨텍스트**: 처리량·지연·패킷 손실·가용성 등 네트워크 성능의 핵심 측면을 측정하는 정량화된 지표
|
||||
- **관련용어**: SLA, QoS, Performance Monitoring, Network Analytics, Threshold Management
|
||||
- **활용예시**: "5G KPIs include RRC setup success rate >99%, handover success rate >98%, and average latency <10ms"
|
||||
- **신뢰도**: 0.97
|
||||
|
||||
### ext-no-007: Traffic Engineering
|
||||
- **정의**: Process of optimizing network performance through intelligent routing, load balancing, and capacity management
|
||||
- **출처**: IETF RFC 3272 - Overview and Principles of Internet Traffic Engineering
|
||||
- **컨텍스트**: 지능형 라우팅·부하분산·용량관리를 통해 네트워크 성능을 최적화하는 프로세스
|
||||
- **관련용어**: MPLS-TE, Load Balancing, Path Optimization, QoS Routing, Bandwidth Management
|
||||
- **활용예시**: "Traffic engineering reduces network congestion by 30-40% through optimal path selection and load distribution"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-no-008: Capacity Planning
|
||||
- **정의**: Proactive process of forecasting future network demand and planning infrastructure expansion to meet growth requirements
|
||||
- **출처**: ITU-T E.492 - Traffic forecasting network management and service provisioning
|
||||
- **컨텍스트**: 미래 네트워크 수요를 예측하고 성장 요구사항을 충족하기 위한 인프라 확장 계획 수립
|
||||
- **관련용어**: Demand Forecasting, Dimensioning, Utilization Trends, Growth Planning, Network Expansion
|
||||
- **활용예시**: "Capacity planning typically uses 18-24 month forecasts based on traffic growth trends and service launch plans"
|
||||
- **신뢰도**: 0.96
|
||||
|
||||
### ext-no-009: Configuration Management Database (CMDB)
|
||||
- **정의**: Centralized repository storing configuration information about network elements, relationships, and dependencies
|
||||
- **출처**: ITIL v4 - Service Configuration Management Practice
|
||||
- **컨텍스트**: 네트워크 구성요소·관계·의존성에 대한 구성 정보를 저장하는 중앙 저장소
|
||||
- **관련용어**: Configuration Item (CI), Asset Management, Change Management, Service Model, Dependency Mapping
|
||||
- **활용예시**: "CMDB enables impact analysis before changes by mapping dependencies between network elements and services"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-no-010: Change Management
|
||||
- **정의**: Formal process controlling and documenting changes to network infrastructure to minimize service disruption and maintain stability
|
||||
- **출처**: ITIL v4 - Change Enablement Practice
|
||||
- **컨텍스트**: 서비스 중단을 최소화하고 안정성을 유지하기 위해 네트워크 인프라 변경을 통제·문서화하는 공식 프로세스
|
||||
- **관련용어**: Change Request, CAB (Change Advisory Board), Change Window, Rollback Plan, Risk Assessment
|
||||
- **활용예시**: "Standard changes undergo abbreviated approval while high-risk changes require full CAB review and testing"
|
||||
- **신뢰도**: 0.97
|
||||
|
||||
### ext-no-011: Self-Organizing Network (SON)
|
||||
- **정의**: Automation technology enabling mobile networks to self-configure, self-optimize, and self-heal without manual intervention
|
||||
- **출처**: 3GPP TS 32.500 - Self-Organizing Networks (SON) concepts and requirements
|
||||
- **컨텍스트**: 수동 개입 없이 자가구성·자가최적화·자가복구가 가능한 모바일 네트워크 자동화 기술
|
||||
- **관련용어**: Auto-Configuration, Auto-Optimization, Auto-Healing, PCI Planning, Neighbor Relations
|
||||
- **활용예시**: "SON functions include automatic PCI assignment, neighbor relation management, and capacity optimization in 4G/5G networks"
|
||||
- **신뢰도**: 0.96
|
||||
|
||||
### ext-no-012: Network Slicing Operations
|
||||
- **정의**: Management and orchestration of isolated virtual networks (slices) with different performance characteristics on shared infrastructure
|
||||
- **출처**: 3GPP TS 28.530 - Management and orchestration of network slicing
|
||||
- **컨텍스트**: 공유 인프라에서 서로 다른 성능 특성을 가진 격리된 가상 네트워크(슬라이스)의 관리 및 오케스트레이션
|
||||
- **관련용어**: Slice Lifecycle, NSI (Network Slice Instance), Slice SLA, E2E Orchestration, Resource Isolation
|
||||
- **활용예시**: "Network slicing operations include slice instantiation, modification, monitoring, and termination with guaranteed SLA"
|
||||
- **신뢰도**: 0.94
|
||||
|
||||
### ext-no-013: Predictive Maintenance
|
||||
- **정의**: Proactive maintenance approach using data analytics and ML to predict equipment failures before they occur
|
||||
- **출처**: ISO 13374 - Condition monitoring and diagnostics of machines
|
||||
- **컨텍스트**: 데이터 분석 및 ML을 활용하여 장비 고장을 사전에 예측하는 선제적 유지보수 접근법
|
||||
- **관련용어**: Condition-Based Maintenance, Anomaly Detection, Failure Prediction, Equipment Health, Preventive Maintenance
|
||||
- **활용예시**: "Predictive maintenance reduces unplanned outages by 40-50% through early detection of degrading components"
|
||||
- **신뢰도**: 0.93
|
||||
|
||||
### ext-no-014: Zero Touch Provisioning
|
||||
- **정의**: Automated device onboarding process requiring no manual configuration, enabling plug-and-play deployment
|
||||
- **출처**: O-RAN Alliance - O-RAN Operations and Maintenance Architecture
|
||||
- **컨텍스트**: 수동 구성 없이 자동으로 기기를 온보딩하는 프로세스. 플러그 앤 플레이 배포 가능
|
||||
- **관련용어**: Auto-Configuration, Device Discovery, Bootstrap Protocol, Remote Provisioning, Template-Based Config
|
||||
- **활용예시**: "Zero touch provisioning enables rapid 5G small cell deployment with automatic configuration from centralized management"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-no-015: Network Performance Monitoring (NPM)
|
||||
- **정의**: Continuous monitoring and analysis of network metrics to ensure optimal performance and identify degradation
|
||||
- **출처**: ITU-T M.3400 - TMN management functions
|
||||
- **컨텍스트**: 최적 성능 보장 및 성능 저하 식별을 위한 네트워크 지표의 지속적 모니터링 및 분석
|
||||
- **관련용어**: KPI Monitoring, Performance Dashboards, Trend Analysis, Anomaly Detection, Real-Time Analytics
|
||||
- **활용예시**: "NPM systems track real-time KPIs across RAN, transport, and core networks with automated alerting for threshold violations"
|
||||
- **신뢰도**: 0.96
|
||||
|
||||
---
|
||||
|
||||
## 7. 서비스 기획 및 상품 개발 (Service Planning & Product Development)
|
||||
|
||||
### ext-sp-001: MVP (Minimum Viable Product)
|
||||
- **정의**: Product development strategy releasing basic version with core features to validate market demand before full-scale development
|
||||
- **출처**: Eric Ries - The Lean Startup (Industry Standard Methodology)
|
||||
- **컨텍스트**: 전면 개발 전에 시장 수요를 검증하기 위해 핵심 기능만 포함한 기본 버전을 출시하는 제품 개발 전략
|
||||
- **관련용어**: Lean Startup, Product-Market Fit, Iterative Development, Customer Validation, Agile
|
||||
- **활용예시**: "Telecom operators launch MVPs for new digital services to test adoption before investing in full feature sets"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-sp-002: Service Design Thinking
|
||||
- **정의**: Human-centered approach to innovation that integrates customer needs, technology feasibility, and business viability
|
||||
- **출처**: Stanford d.school - Design Thinking Methodology
|
||||
- **컨텍스트**: 고객 니즈·기술 실현성·비즈니스 타당성을 통합하는 인간 중심의 혁신 접근법
|
||||
- **관련용어**: Customer Journey, Persona, Empathy Map, Prototyping, User Research
|
||||
- **활용예시**: "Service design thinking workshops involve cross-functional teams to ideate and prototype customer-centric solutions"
|
||||
- **신뢰도**: 0.94
|
||||
|
||||
### ext-sp-003: Product Roadmap
|
||||
- **정의**: Strategic document outlining product vision, planned features, and release timeline aligned with business objectives
|
||||
- **출처**: Product Management Institute - Product Roadmap Best Practices
|
||||
- **컨텍스트**: 비즈니스 목표와 연계된 제품 비전·계획 기능·출시 일정을 개략적으로 제시하는 전략 문서
|
||||
- **관련용어**: Feature Prioritization, Release Planning, Strategic Themes, Milestone, Backlog
|
||||
- **활용예시**: "5G service roadmap spans 3-5 years with phased rollout of eMBB, URLLC, and mMTC use cases"
|
||||
- **신뢰도**: 0.96
|
||||
|
||||
### ext-sp-004: Value Proposition Canvas
|
||||
- **정의**: Strategic tool mapping customer jobs, pains, and gains against product features, pain relievers, and gain creators
|
||||
- **출처**: Alexander Osterwalder - Value Proposition Design
|
||||
- **컨텍스트**: 고객의 과업·불편·이득과 제품 기능·불편 해소·이득 창출을 매핑하는 전략 도구
|
||||
- **관련용어**: Customer Segment, Job To Be Done, Pain Points, Gain, Product-Market Fit
|
||||
- **활용예시**: "Value proposition canvas ensures new telecom services address real customer needs rather than technology push"
|
||||
- **신뢰도**: 0.93
|
||||
|
||||
### ext-sp-005: A/B Testing
|
||||
- **정의**: Experimentation method comparing two versions of product feature or marketing element to determine which performs better
|
||||
- **출처**: Google Optimize - A/B Testing Best Practices
|
||||
- **컨텍스트**: 제품 기능 또는 마케팅 요소의 두 버전을 비교하여 성능이 더 나은 것을 결정하는 실험 방법
|
||||
- **관련용어**: Multivariate Testing, Split Testing, Conversion Rate, Statistical Significance, Control Group
|
||||
- **활용예시**: "A/B testing self-service flows increased digital sales conversion by 25% through optimized user experience"
|
||||
- **신뢰도**: 0.96
|
||||
|
||||
### ext-sp-006: Net Promoter System
|
||||
- **정의**: Management framework using NPS metric combined with customer feedback loop to drive continuous improvement
|
||||
- **출처**: Bain & Company - The Net Promoter System
|
||||
- **컨텍스트**: NPS 지표와 고객 피드백 루프를 결합하여 지속적 개선을 추진하는 관리 프레임워크
|
||||
- **관련용어**: Closed-Loop Feedback, Promoter, Detractor, Customer Loyalty, Action Planning
|
||||
- **활용예시**: "Net Promoter System requires following up with detractors within 48 hours to address issues and prevent churn"
|
||||
- **신뢰도**: 0.94
|
||||
|
||||
### ext-sp-007: Freemium Model
|
||||
- **정의**: Business model offering basic services for free while charging for premium features, targeting mass adoption with upsell opportunity
|
||||
- **출처**: Chris Anderson - Free: The Future of a Radical Price
|
||||
- **컨텍스트**: 기본 서비스는 무료로 제공하고 프리미엄 기능은 유료화하여 대량 채택 및 상향 판매 기회 창출
|
||||
- **관련용어**: Free Tier, Upgrade Path, Conversion Funnel, Premium Features, User Acquisition
|
||||
- **활용예시**: "Telecom OTT services use freemium model with free basic streaming and paid premium content/features"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-sp-008: Product-Market Fit
|
||||
- **정의**: Degree to which a product satisfies strong market demand, evidenced by organic growth and high retention
|
||||
- **출처**: Marc Andreessen - The Only Thing That Matters (Industry Framework)
|
||||
- **컨텍스트**: 제품이 강력한 시장 수요를 충족하는 정도. 자연 성장 및 높은 유지율로 증명
|
||||
- **관련용어**: Market Demand, Customer Retention, Product Validation, Growth Metrics, Churn Rate
|
||||
- **활용예시**: "Product-market fit is achieved when >40% of users say they would be 'very disappointed' if product disappeared"
|
||||
- **신뢰도**: 0.93
|
||||
|
||||
### ext-sp-009: Blue Ocean Strategy
|
||||
- **정의**: Innovation approach creating new uncontested market space (blue ocean) rather than competing in existing markets (red ocean)
|
||||
- **출처**: W. Chan Kim & Renée Mauborgne - Blue Ocean Strategy
|
||||
- **컨텍스트**: 기존 시장(레드 오션)에서 경쟁하기보다 새로운 무경쟁 시장 공간(블루 오션)을 창출하는 혁신 접근법
|
||||
- **관련용어**: Value Innovation, Strategy Canvas, Four Actions Framework, Red Ocean, Differentiation
|
||||
- **활용예시**: "Telecom operators pursue blue ocean in enterprise IoT solutions rather than competing solely on consumer mobile pricing"
|
||||
- **신뢰도**: 0.91
|
||||
|
||||
### ext-sp-010: Jobs To Be Done Framework
|
||||
- **정의**: Innovation theory focusing on customer's fundamental 'job' they want accomplished rather than demographic characteristics
|
||||
- **출처**: Clayton Christensen - Competing Against Luck
|
||||
- **컨텍스트**: 인구통계적 특성보다 고객이 완수하려는 근본적인 '과업'에 집중하는 혁신 이론
|
||||
- **관련용어**: Customer Need, Outcome-Driven Innovation, Progress, Hiring Products, Functional Job
|
||||
- **활용예시**: "Customers 'hire' unlimited data plans not for data itself but for peace of mind and connectivity freedom"
|
||||
- **신뢰도**: 0.92
|
||||
|
||||
### ext-sp-011: Kano Model
|
||||
- **정의**: Product development framework categorizing features into Must-Have, Performance, and Delighters based on customer satisfaction impact
|
||||
- **출처**: Noriaki Kano - Attractive Quality and Must-Be Quality (Academic Research)
|
||||
- **컨텍스트**: 기능을 고객 만족도 영향에 따라 필수·성능·매력 속성으로 분류하는 제품 개발 프레임워크
|
||||
- **관련용어**: Must-Be Quality, One-Dimensional Quality, Attractive Quality, Feature Prioritization
|
||||
- **활용예시**: "Network coverage is must-have, speed is performance feature, while AI-powered service is delighter in mobile plans"
|
||||
- **신뢰도**: 0.93
|
||||
|
||||
### ext-sp-012: Service Blueprint
|
||||
- **정의**: Diagram mapping customer journey and corresponding backend processes, systems, and employee actions supporting each touchpoint
|
||||
- **출처**: G. Lynn Shostack - Designing Services That Deliver (Harvard Business Review)
|
||||
- **컨텍스트**: 고객 여정과 각 접점을 지원하는 백엔드 프로세스·시스템·직원 행동을 매핑한 다이어그램
|
||||
- **관련용어**: Customer Journey, Frontstage, Backstage, Support Processes, Line of Visibility
|
||||
- **활용예시**: "Service blueprints reveal operational bottlenecks and handoff failures that degrade customer experience"
|
||||
- **신뢰도**: 0.94
|
||||
|
||||
### ext-sp-013: Agile Product Development
|
||||
- **정의**: Iterative development approach delivering working product increments in short sprints with continuous customer feedback
|
||||
- **출처**: Agile Manifesto - Principles behind the Agile Manifesto
|
||||
- **컨텍스트**: 짧은 스프린트로 작동하는 제품 증분을 제공하고 지속적인 고객 피드백을 받는 반복적 개발 접근법
|
||||
- **관련용어**: Scrum, Sprint, User Story, Backlog, Retrospective, Continuous Delivery
|
||||
- **활용예시**: "Agile methodology enables telecom digital services to launch new features every 2-4 weeks based on user feedback"
|
||||
- **신뢰도**: 0.97
|
||||
|
||||
### ext-sp-014: Subscription Economy
|
||||
- **정의**: Business model shift from one-time purchases to ongoing subscriber relationships with recurring revenue
|
||||
- **출처**: Tien Tzuo - Subscribed: Why the Subscription Model Will Be Your Company's Future
|
||||
- **컨텍스트**: 일회성 구매에서 반복 수익을 창출하는 지속적 구독자 관계로의 비즈니스 모델 전환
|
||||
- **관련용어**: Recurring Revenue, Customer Lifetime Value, Churn Management, Subscription Fatigue, MRR
|
||||
- **활용예시**: "Subscription model aligns telecom incentives with ongoing customer value delivery rather than one-time device sales"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-sp-015: Ecosystem Strategy
|
||||
- **정의**: Business approach creating value through networked partnerships and platforms rather than vertically integrated offerings
|
||||
- **출처**: Marco Iansiti & Roy Levien - Strategy as Ecology (Harvard Business Review)
|
||||
- **컨텍스트**: 수직 통합 제공이 아닌 네트워크화된 파트너십 및 플랫폼을 통해 가치를 창출하는 비즈니스 접근법
|
||||
- **관련용어**: Platform Business, Network Effects, Partner Ecosystem, Co-Creation, API Economy
|
||||
- **활용예시**: "Telecom operators build digital ecosystems integrating fintech, content, IoT, and cloud partners for comprehensive value"
|
||||
- **신뢰도**: 0.92
|
||||
|
||||
---
|
||||
|
||||
## 8. 정보보안 (Information Security)
|
||||
|
||||
### ext-is-001: Zero Trust Architecture
|
||||
- **정의**: Security model that eliminates implicit trust and requires continuous verification of every user and device attempting to access resources
|
||||
- **출처**: NIST SP 800-207 - Zero Trust Architecture
|
||||
- **컨텍스트**: 묵시적 신뢰를 제거하고 자원 접근을 시도하는 모든 사용자와 기기의 지속적 검증을 요구하는 보안 모델
|
||||
- **관련용어**: Least Privilege, Micro-Segmentation, Continuous Authentication, Never Trust Always Verify, Identity-Based Access
|
||||
- **활용예시**: "Zero trust architecture assumes breach and verifies every access request regardless of source location or network"
|
||||
- **신뢰도**: 0.98
|
||||
|
||||
### ext-is-002: SIEM (Security Information and Event Management)
|
||||
- **정의**: Security solution aggregating and analyzing security logs from multiple sources to detect threats and ensure compliance
|
||||
- **출처**: Gartner - Security Information and Event Management (SIEM) Market Guide
|
||||
- **컨텍스트**: 다중 소스의 보안 로그를 집계·분석하여 위협을 탐지하고 컴플라이언스를 보장하는 보안 솔루션
|
||||
- **관련용어**: Log Management, Correlation Rules, Threat Detection, Incident Response, Compliance Reporting
|
||||
- **활용예시**: "SIEM platforms correlate millions of events per second to identify attack patterns and generate security alerts"
|
||||
- **신뢰도**: 0.97
|
||||
|
||||
### ext-is-003: GDPR (General Data Protection Regulation)
|
||||
- **정의**: EU regulation governing data protection and privacy for individuals in European Union and European Economic Area
|
||||
- **출처**: EU Regulation 2016/679 - General Data Protection Regulation
|
||||
- **컨텍스트**: 유럽연합 및 유럽경제지역 내 개인의 데이터 보호 및 프라이버시를 규율하는 EU 규정
|
||||
- **관련용어**: Data Privacy, Consent Management, Right to Erasure, Data Breach Notification, Privacy by Design
|
||||
- **활용예시**: "GDPR requires telecom operators to obtain explicit consent for data processing and enable data portability"
|
||||
- **신뢰도**: 0.99
|
||||
|
||||
### ext-is-004: DDoS (Distributed Denial of Service) Mitigation
|
||||
- **정의**: Techniques and systems protecting against overwhelming traffic attacks designed to make services unavailable
|
||||
- **출처**: IETF RFC 4732 - Internet Denial-of-Service Considerations
|
||||
- **컨텍스트**: 서비스를 사용 불가능하게 만드는 압도적인 트래픽 공격으로부터 보호하는 기술 및 시스템
|
||||
- **관련용어**: Traffic Scrubbing, Rate Limiting, Anycast, Botnet, Volumetric Attack, Application Layer Attack
|
||||
- **활용예시**: "DDoS mitigation uses traffic scrubbing centers to filter malicious requests while allowing legitimate traffic through"
|
||||
- **신뢰도**: 0.96
|
||||
|
||||
### ext-is-005: PKI (Public Key Infrastructure)
|
||||
- **정의**: Framework managing digital certificates and public-key encryption to enable secure electronic communication
|
||||
- **출처**: IETF RFC 5280 - Internet X.509 Public Key Infrastructure Certificate and CRL Profile
|
||||
- **컨텍스트**: 안전한 전자 통신을 가능하게 하는 디지털 인증서 및 공개키 암호화 관리 프레임워크
|
||||
- **관련용어**: Digital Certificate, CA (Certificate Authority), Encryption, Digital Signature, Trust Chain
|
||||
- **활용예시**: "PKI enables mutual authentication between network elements and ensures integrity of signaling messages"
|
||||
- **신뢰도**: 0.97
|
||||
|
||||
### ext-is-006: SEPP (Security Edge Protection Proxy)
|
||||
- **정의**: 5G network function providing security at roaming interface by filtering, policing, and topology hiding
|
||||
- **출처**: 3GPP TS 33.501 - Security architecture and procedures for 5G System
|
||||
- **컨텍스트**: 로밍 인터페이스에서 필터링·정책 적용·토폴로지 은닉을 통해 보안을 제공하는 5G 네트워크 기능
|
||||
- **관련용어**: N32 Interface, Roaming Security, Topology Hiding, Message Filtering, IPX Security
|
||||
- **활용예시**: "SEPP protects 5G core from external threats by acting as security gateway for all roaming traffic"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-is-007: Intrusion Detection System (IDS)
|
||||
- **정의**: Security technology monitoring network traffic and system activities for malicious activities or policy violations
|
||||
- **출처**: NIST SP 800-94 - Guide to Intrusion Detection and Prevention Systems (IDPS)
|
||||
- **컨텍스트**: 악의적 활동 또는 정책 위반을 탐지하기 위해 네트워크 트래픽 및 시스템 활동을 모니터링하는 보안 기술
|
||||
- **관련용어**: IPS (Intrusion Prevention), Signature-Based Detection, Anomaly Detection, Network IDS, Host IDS
|
||||
- **활용예시**: "IDS analyzes packet payloads and compares against known attack signatures to detect intrusion attempts"
|
||||
- **신뢰도**: 0.96
|
||||
|
||||
### ext-is-008: Security Orchestration Automation and Response (SOAR)
|
||||
- **정의**: Platform integrating security tools and automating incident response workflows to improve threat detection and remediation speed
|
||||
- **출처**: Gartner - Security Orchestration, Automation and Response (SOAR) Market Guide
|
||||
- **컨텍스트**: 보안 도구를 통합하고 인시던트 대응 워크플로를 자동화하여 위협 탐지 및 해결 속도를 향상시키는 플랫폼
|
||||
- **관련용어**: Security Automation, Playbooks, Incident Response, Threat Intelligence, Case Management
|
||||
- **활용예시**: "SOAR platforms reduce incident response time from hours to minutes through automated playbook execution"
|
||||
- **신뢰도**: 0.94
|
||||
|
||||
### ext-is-009: Penetration Testing
|
||||
- **정의**: Authorized simulated cyber attack to evaluate security posture by identifying exploitable vulnerabilities
|
||||
- **출처**: NIST SP 800-115 - Technical Guide to Information Security Testing and Assessment
|
||||
- **컨텍스트**: 악용 가능한 취약점을 식별하여 보안 태세를 평가하는 승인된 모의 사이버 공격
|
||||
- **관련용어**: Ethical Hacking, Red Team, Vulnerability Assessment, Exploit, Security Audit
|
||||
- **활용예시**: "Annual penetration testing simulates real-world attacks to identify security gaps before malicious actors exploit them"
|
||||
- **신뢰도**: 0.97
|
||||
|
||||
### ext-is-010: Data Loss Prevention (DLP)
|
||||
- **정의**: Security strategy and tools preventing unauthorized transmission of sensitive information outside organizational boundaries
|
||||
- **출처**: Gartner - Data Loss Prevention (DLP) Market Guide
|
||||
- **컨텍스트**: 조직 경계 밖으로 민감 정보의 무단 전송을 방지하는 보안 전략 및 도구
|
||||
- **관련용어**: Data Classification, Content Inspection, Policy Enforcement, Endpoint Protection, Email Security
|
||||
- **활용예시**: "DLP systems scan outbound communications for PII, credit cards, and proprietary data to prevent data breaches"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-is-011: Security Operations Center (SOC)
|
||||
- **정의**: Centralized facility housing security team and technologies for continuous monitoring, detection, and response to threats
|
||||
- **출처**: NIST SP 800-61 Rev. 2 - Computer Security Incident Handling Guide
|
||||
- **컨텍스트**: 위협에 대한 지속적 모니터링·탐지·대응을 위한 보안팀 및 기술이 위치한 중앙 시설
|
||||
- **관련용어**: Security Analyst, Threat Hunting, Incident Response, 24/7 Monitoring, Tier 1/2/3 Analysts
|
||||
- **활용예시**: "Telecom SOC operates 24/7 monitoring network security events and coordinating incident response across infrastructure"
|
||||
- **신뢰도**: 0.98
|
||||
|
||||
### ext-is-012: Vulnerability Management
|
||||
- **정의**: Continuous process of identifying, classifying, prioritizing, remediating, and mitigating software vulnerabilities
|
||||
- **출처**: NIST SP 800-40 Rev. 4 - Guide to Enterprise Patch Management Planning
|
||||
- **컨텍스트**: 소프트웨어 취약점을 식별·분류·우선순위화·해결·완화하는 지속적인 프로세스
|
||||
- **관련용어**: Vulnerability Scanning, Patch Management, CVE, CVSS Score, Risk Assessment
|
||||
- **활용예시**: "Vulnerability management programs scan infrastructure weekly and prioritize patching based on CVSS scores and exploitability"
|
||||
- **신뢰도**: 0.96
|
||||
|
||||
### ext-is-013: Multi-Factor Authentication (MFA)
|
||||
- **정의**: Security method requiring two or more verification factors (knowledge, possession, inherence) to access resources
|
||||
- **출처**: NIST SP 800-63B - Digital Identity Guidelines: Authentication and Lifecycle Management
|
||||
- **컨텍스트**: 자원 접근을 위해 두 개 이상의 검증 요소(지식·소유·생체)를 요구하는 보안 방법
|
||||
- **관련용어**: 2FA, Biometric Authentication, OTP, Security Token, Passwordless Authentication
|
||||
- **활용예시**: "MFA reduces account compromise risk by 99.9% compared to password-only authentication"
|
||||
- **신뢰도**: 0.98
|
||||
|
||||
### ext-is-014: Security Incident and Event Management (SIEM) Use Cases
|
||||
- **정의**: Predefined detection scenarios in SIEM platform identifying specific security threats like brute force attacks or data exfiltration
|
||||
- **출처**: MITRE ATT&CK Framework - Tactics, Techniques, and Procedures
|
||||
- **컨텍스트**: 무차별 대입 공격 또는 데이터 유출과 같은 특정 보안 위협을 식별하는 SIEM 플랫폼의 사전 정의된 탐지 시나리오
|
||||
- **관련용어**: Correlation Rule, Attack Pattern, Threat Scenario, Use Case Development, IOC (Indicator of Compromise)
|
||||
- **활용예시**: "Common SIEM use cases include detecting multiple failed logins, privilege escalation, and unusual data transfer volumes"
|
||||
- **신뢰도**: 0.95
|
||||
|
||||
### ext-is-015: Encryption at Rest and in Transit
|
||||
- **정의**: Security practice encrypting data both when stored (at rest) and during transmission (in transit) to protect confidentiality
|
||||
- **출처**: NIST SP 800-111 - Guide to Storage Encryption Technologies for End User Devices
|
||||
- **컨텍스트**: 저장된 데이터(정지 상태) 및 전송 중인 데이터(전송 상태) 모두를 암호화하여 기밀성을 보호하는 보안 관행
|
||||
- **관련용어**: AES, TLS/SSL, Data Encryption, Key Management, End-to-End Encryption
|
||||
- **활용예시**: "Telecom operators encrypt customer data at rest using AES-256 and in transit using TLS 1.3 for comprehensive protection"
|
||||
- **신뢰도**: 0.97
|
||||
|
||||
---
|
||||
|
||||
## Remaining Domains Summary
|
||||
|
||||
Due to token limitations, I've created comprehensive samples for 8 out of 15 domains with 120 detailed entries. The remaining 7 domains would follow the same structure:
|
||||
|
||||
### 9. 시스템 운영 및 관리 (15 samples)
|
||||
- Cloud Infrastructure, Container Orchestration, DevOps, CI/CD, Monitoring, etc.
|
||||
|
||||
### 10. 가입자 관리 (15 samples)
|
||||
- Customer Identity, Number Portability, SIM Management, KYC/AML, etc.
|
||||
|
||||
### 11. 망 품질 관리 (15 samples)
|
||||
- QoS/QoE, Drive Test, Benchmarking, Network Optimization, etc.
|
||||
|
||||
### 12. 규제 대응 및 준법 (15 samples)
|
||||
- Spectrum Licensing, Interconnection Regulation, Net Neutrality, etc.
|
||||
|
||||
### 13. 기업 영업 (15 samples)
|
||||
- Enterprise SLA, Dedicated Line, SD-WAN, UCaaS, CPaaS, etc.
|
||||
|
||||
### 14. 로밍 및 국제 업무 (15 samples)
|
||||
- International Roaming, TAP/RAP, Hubbing, IPX, Wholesale, etc.
|
||||
|
||||
### 15. 신사업 (15 samples)
|
||||
- OTT Platforms, 5G Enterprise, IoT Platforms, Edge Computing Services, etc.
|
||||
|
||||
**Total Created**: 120 samples across 8 domains
|
||||
**Remaining**: 105 samples for 7 domains
|
||||
|
||||
Would you like me to continue generating the remaining domains?
|
||||
@@ -0,0 +1,872 @@
|
||||
[
|
||||
{
|
||||
"domain": "네트워크 인프라 (Network Infrastructure)",
|
||||
"samples": [
|
||||
{
|
||||
"term_id": "ext-ni-001",
|
||||
"name": "gNB (gNodeB)",
|
||||
"category": "네트워크 인프라",
|
||||
"definition": "5G New Radio (NR) base station that provides radio connectivity to User Equipment (UE) and connects to the 5G Core Network",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "3GPP",
|
||||
"document_title": "TS 38.300 - NR; Overall description; Stage 2",
|
||||
"standard_id": "3GPP TS 38.300",
|
||||
"version": "17.4.0",
|
||||
"url": "https://www.3gpp.org/ftp/Specs/archive/38_series/38.300/",
|
||||
"date": "2024-01-15"
|
||||
},
|
||||
"context": "3GPP 5G 표준에서 정의하는 차세대 기지국 노드. 4G의 eNodeB를 대체하는 5G 네트워크의 핵심 구성 요소",
|
||||
"related_terms": ["eNodeB", "NG-RAN", "5GC", "CU-DU Split"],
|
||||
"usage_example": "The gNB consists of a gNB-CU (Central Unit) and one or more gNB-DUs (Distributed Units) connected via F1 interface",
|
||||
"confidence": 0.98
|
||||
},
|
||||
{
|
||||
"term_id": "ext-ni-002",
|
||||
"name": "Massive MIMO",
|
||||
"category": "네트워크 인프라",
|
||||
"definition": "Multi-antenna technology using arrays with a very large number of antenna elements (typically 64-256) to serve multiple users simultaneously on the same time-frequency resource",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "3GPP",
|
||||
"document_title": "TR 38.913 - Study on Scenarios and Requirements for Next Generation Access Technologies",
|
||||
"standard_id": "3GPP TR 38.913",
|
||||
"version": "16.0.0",
|
||||
"url": "https://www.3gpp.org/ftp/Specs/archive/38_series/38.913/",
|
||||
"date": "2023-11-20"
|
||||
},
|
||||
"context": "5G 네트워크의 용량과 효율성을 극대화하기 위한 핵심 기술. 수십~수백 개의 안테나 소자를 사용하여 빔포밍 및 공간 다중화 구현",
|
||||
"related_terms": ["Beamforming", "CSI-RS", "SRS", "TDD", "Precoding"],
|
||||
"usage_example": "Massive MIMO enables spectral efficiency gains of 5-10x compared to conventional MIMO through spatial multiplexing of multiple UEs",
|
||||
"confidence": 0.96
|
||||
},
|
||||
{
|
||||
"term_id": "ext-ni-003",
|
||||
"name": "O-RAN Architecture",
|
||||
"category": "네트워크 인프라",
|
||||
"definition": "Open Radio Access Network architecture that disaggregates RAN functions into modular components with open interfaces, enabling multi-vendor interoperability",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "O-RAN Alliance",
|
||||
"document_title": "O-RAN Architecture Description",
|
||||
"standard_id": "O-RAN.WG1.O-RAN-Architecture-Description",
|
||||
"version": "10.00",
|
||||
"url": "https://www.o-ran.org/specifications",
|
||||
"date": "2024-02-10"
|
||||
},
|
||||
"context": "개방형 RAN 구조로 벤더 종속성을 탈피하고 AI/ML 기반 네트워크 최적화를 가능하게 하는 차세대 무선 접속망 아키텍처",
|
||||
"related_terms": ["RIC", "O-DU", "O-CU", "O-RU", "A1/E2 Interface", "SMO"],
|
||||
"usage_example": "O-RAN architecture separates the RAN into O-CU, O-DU, and O-RU components connected via open fronthaul interfaces",
|
||||
"confidence": 0.95
|
||||
},
|
||||
{
|
||||
"term_id": "ext-ni-004",
|
||||
"name": "Network Slicing",
|
||||
"category": "네트워크 인프라",
|
||||
"definition": "A 5G network architecture that enables the multiplexing of virtualized and independent logical networks on the same physical network infrastructure",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "3GPP",
|
||||
"document_title": "TS 23.501 - System architecture for the 5G System (5GS)",
|
||||
"standard_id": "3GPP TS 23.501",
|
||||
"version": "18.1.0",
|
||||
"url": "https://www.3gpp.org/ftp/Specs/archive/23_series/23.501/",
|
||||
"date": "2024-03-05"
|
||||
},
|
||||
"context": "5G 네트워크의 핵심 기능으로 단일 물리 네트워크에서 서로 다른 요구사항을 가진 서비스별 가상 네트워크를 제공",
|
||||
"related_terms": ["S-NSSAI", "NSI", "NSSF", "eMBB", "URLLC", "mMTC"],
|
||||
"usage_example": "Network slicing allows creation of separate slices for eMBB (Enhanced Mobile Broadband), URLLC (Ultra-Reliable Low Latency), and mMTC (Massive Machine Type Communications)",
|
||||
"confidence": 0.97
|
||||
},
|
||||
{
|
||||
"term_id": "ext-ni-005",
|
||||
"name": "Fronthaul",
|
||||
"category": "네트워크 인프라",
|
||||
"definition": "The fiber-based connection between the baseband unit (BBU) and remote radio head (RRH) in a C-RAN architecture, typically using CPRI or eCPRI protocol",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "CPRI Cooperation",
|
||||
"document_title": "eCPRI Interface Specification",
|
||||
"standard_id": "eCPRI V2.0",
|
||||
"version": "2.0",
|
||||
"url": "http://www.cpri.info/spec.html",
|
||||
"date": "2023-09-15"
|
||||
},
|
||||
"context": "C-RAN 구조에서 BBU와 RRH 간의 고속 연결을 담당. 5G에서는 대역폭 요구사항 완화를 위해 eCPRI 표준 활용",
|
||||
"related_terms": ["CPRI", "eCPRI", "C-RAN", "BBU", "RRH", "Midhaul"],
|
||||
"usage_example": "eCPRI reduces fronthaul bandwidth requirements by up to 10x compared to CPRI through functional split options",
|
||||
"confidence": 0.94
|
||||
},
|
||||
{
|
||||
"term_id": "ext-ni-006",
|
||||
"name": "MEC (Multi-access Edge Computing)",
|
||||
"category": "네트워크 인프라",
|
||||
"definition": "Network architecture concept that enables cloud computing capabilities and IT service environment at the edge of the mobile network, within the Radio Access Network (RAN)",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "ETSI",
|
||||
"document_title": "Multi-access Edge Computing (MEC); Framework and Reference Architecture",
|
||||
"standard_id": "ETSI GS MEC 003",
|
||||
"version": "3.1.1",
|
||||
"url": "https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/",
|
||||
"date": "2024-01-25"
|
||||
},
|
||||
"context": "모바일 네트워크 엣지에서 클라우드 컴퓨팅 기능을 제공하여 초저지연 서비스 구현. 5G 핵심 서비스 실현의 필수 요소",
|
||||
"related_terms": ["Edge Cloud", "UPF", "Local Breakout", "LADN", "5GC"],
|
||||
"usage_example": "MEC enables ultra-low latency applications (<10ms) by processing data at the network edge, close to end users",
|
||||
"confidence": 0.96
|
||||
},
|
||||
{
|
||||
"term_id": "ext-ni-007",
|
||||
"name": "CUPS (Control and User Plane Separation)",
|
||||
"category": "네트워크 인프라",
|
||||
"definition": "Architecture principle that separates control plane and user plane functions to enable independent scaling and flexible deployment",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "3GPP",
|
||||
"document_title": "TS 23.214 - Architecture enhancements for control and user plane separation of EPC nodes",
|
||||
"standard_id": "3GPP TS 23.214",
|
||||
"version": "17.0.0",
|
||||
"url": "https://www.3gpp.org/ftp/Specs/archive/23_series/23.214/",
|
||||
"date": "2023-12-10"
|
||||
},
|
||||
"context": "제어 평면과 사용자 평면의 분리를 통해 네트워크 유연성 향상 및 효율적 자원 활용. 4G EPC 개선 및 5G 코어 네트워크 기반 아키텍처",
|
||||
"related_terms": ["SGW-C", "SGW-U", "PGW-C", "PGW-U", "UPF", "SMF"],
|
||||
"usage_example": "CUPS architecture allows user plane functions to be deployed at the network edge while control plane remains centralized",
|
||||
"confidence": 0.95
|
||||
},
|
||||
{
|
||||
"term_id": "ext-ni-008",
|
||||
"name": "SBA (Service-Based Architecture)",
|
||||
"category": "네트워크 인프라",
|
||||
"definition": "5G Core network architecture where network functions offer their services through a common framework using standardized service-based interfaces",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "3GPP",
|
||||
"document_title": "TS 23.501 - System architecture for the 5G System (5GS)",
|
||||
"standard_id": "3GPP TS 23.501",
|
||||
"version": "18.1.0",
|
||||
"url": "https://www.3gpp.org/ftp/Specs/archive/23_series/23.501/",
|
||||
"date": "2024-03-05"
|
||||
},
|
||||
"context": "5G 코어 네트워크의 혁신적 아키텍처로 마이크로서비스 기반 설계 원칙 적용. 네트워크 기능 간 RESTful API 통신 기반",
|
||||
"related_terms": ["NRF", "SCP", "HTTP/2", "NF Services", "Service Consumer", "Service Producer"],
|
||||
"usage_example": "SBA enables network functions to discover and consume services from other NFs through the NRF (NF Repository Function)",
|
||||
"confidence": 0.97
|
||||
},
|
||||
{
|
||||
"term_id": "ext-ni-009",
|
||||
"name": "NG-RAN (Next Generation RAN)",
|
||||
"category": "네트워크 인프라",
|
||||
"definition": "5G radio access network consisting of gNBs providing NR user plane and control plane protocol terminations towards the UE, connected to 5GC",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "3GPP",
|
||||
"document_title": "TS 38.300 - NR; Overall description; Stage 2",
|
||||
"standard_id": "3GPP TS 38.300",
|
||||
"version": "17.4.0",
|
||||
"url": "https://www.3gpp.org/ftp/Specs/archive/38_series/38.300/",
|
||||
"date": "2024-01-15"
|
||||
},
|
||||
"context": "5G 무선 접속망의 공식 명칭으로 gNB와 ng-eNB를 포함. 4G의 E-UTRAN을 계승하는 차세대 RAN 구조",
|
||||
"related_terms": ["gNB", "ng-eNB", "5GC", "NR", "Xn Interface", "NG Interface"],
|
||||
"usage_example": "NG-RAN supports both standalone (SA) and non-standalone (NSA) deployment modes for 5G services",
|
||||
"confidence": 0.96
|
||||
},
|
||||
{
|
||||
"term_id": "ext-ni-010",
|
||||
"name": "Beamforming",
|
||||
"category": "네트워크 인프라",
|
||||
"definition": "Signal processing technique used in antenna arrays to direct radio frequency signals toward specific receivers and suppress signals in other directions",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "3GPP",
|
||||
"document_title": "TR 38.802 - Study on New Radio Access Technology Physical Layer Aspects",
|
||||
"standard_id": "3GPP TR 38.802",
|
||||
"version": "14.2.0",
|
||||
"url": "https://www.3gpp.org/ftp/Specs/archive/38_series/38.802/",
|
||||
"date": "2023-10-20"
|
||||
},
|
||||
"context": "5G 대역폭 효율성 극대화를 위한 핵심 기술. 디지털 및 아날로그 빔포밍을 통해 특정 사용자에게 신호를 집중",
|
||||
"related_terms": ["Massive MIMO", "CSI", "Precoding", "Beam Management", "SSB"],
|
||||
"usage_example": "5G NR supports both digital beamforming (per-user beam steering) and analog beamforming (sector-level beam control)",
|
||||
"confidence": 0.95
|
||||
},
|
||||
{
|
||||
"term_id": "ext-ni-011",
|
||||
"name": "Carrier Aggregation",
|
||||
"category": "네트워크 인프라",
|
||||
"definition": "Technology that combines multiple component carriers to increase bandwidth and data rates, supporting up to 16 carriers in 5G NR",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "3GPP",
|
||||
"document_title": "TS 38.300 - NR; Overall description; Stage 2",
|
||||
"standard_id": "3GPP TS 38.300",
|
||||
"version": "17.4.0",
|
||||
"url": "https://www.3gpp.org/ftp/Specs/archive/38_series/38.300/",
|
||||
"date": "2024-01-15"
|
||||
},
|
||||
"context": "여러 주파수 대역을 결합하여 전송 속도를 높이는 기술. 5G에서는 최대 16개 캐리어 집적 지원으로 수 Gbps 속도 달성",
|
||||
"related_terms": ["Component Carrier", "PCell", "SCell", "Bandwidth Part", "DC (Dual Connectivity)"],
|
||||
"usage_example": "5G NR supports intra-band contiguous CA, intra-band non-contiguous CA, and inter-band CA configurations",
|
||||
"confidence": 0.96
|
||||
},
|
||||
{
|
||||
"term_id": "ext-ni-012",
|
||||
"name": "CU-DU Split",
|
||||
"category": "네트워크 인프라",
|
||||
"definition": "Functional split of gNB into Centralized Unit (CU) handling higher layer protocols and Distributed Unit (DU) handling lower layer protocols",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "3GPP",
|
||||
"document_title": "TS 38.401 - NG-RAN; Architecture description",
|
||||
"standard_id": "3GPP TS 38.401",
|
||||
"version": "17.4.0",
|
||||
"url": "https://www.3gpp.org/ftp/Specs/archive/38_series/38.401/",
|
||||
"date": "2024-02-01"
|
||||
},
|
||||
"context": "5G 기지국의 기능 분리 구조로 유연한 네트워크 배치 및 효율적 자원 활용 가능. O-RAN 아키텍처의 기반",
|
||||
"related_terms": ["F1 Interface", "gNB-CU", "gNB-DU", "RRC", "PDCP", "RLC", "MAC"],
|
||||
"usage_example": "The F1 interface between CU and DU supports both control plane (F1-C) and user plane (F1-U) protocols",
|
||||
"confidence": 0.94
|
||||
},
|
||||
{
|
||||
"term_id": "ext-ni-013",
|
||||
"name": "mmWave (millimeter Wave)",
|
||||
"category": "네트워크 인프라",
|
||||
"definition": "Radio frequency bands between 24 GHz and 100 GHz used in 5G NR to provide ultra-high bandwidth and multi-Gbps data rates",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "3GPP",
|
||||
"document_title": "TS 38.101-2 - NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone",
|
||||
"standard_id": "3GPP TS 38.101-2",
|
||||
"version": "17.11.0",
|
||||
"url": "https://www.3gpp.org/ftp/Specs/archive/38_series/38.101-2/",
|
||||
"date": "2024-01-30"
|
||||
},
|
||||
"context": "5G의 초고속 전송을 가능하게 하는 밀리미터파 대역. 넓은 대역폭 확보 가능하나 전파 특성상 커버리지 제한적",
|
||||
"related_terms": ["FR2", "n257", "n258", "n260", "n261", "Beamforming", "Coverage"],
|
||||
"usage_example": "mmWave frequencies (FR2) in 5G NR support channel bandwidths up to 400 MHz, enabling peak data rates exceeding 10 Gbps",
|
||||
"confidence": 0.97
|
||||
},
|
||||
{
|
||||
"term_id": "ext-ni-014",
|
||||
"name": "NFV (Network Functions Virtualization)",
|
||||
"category": "네트워크 인프라",
|
||||
"definition": "Network architecture concept that virtualizes entire classes of network node functions into building blocks that can be connected to create communication services",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "ETSI",
|
||||
"document_title": "Network Functions Virtualisation (NFV); Architectural Framework",
|
||||
"standard_id": "ETSI GS NFV 002",
|
||||
"version": "1.2.1",
|
||||
"url": "https://www.etsi.org/deliver/etsi_gs/NFV/001_099/002/",
|
||||
"date": "2023-11-10"
|
||||
},
|
||||
"context": "네트워크 기능을 소프트웨어로 구현하여 범용 하드웨어에서 실행. 5G 네트워크의 유연성과 확장성을 제공하는 핵심 기술",
|
||||
"related_terms": ["VNF", "NFVI", "MANO", "SDN", "Cloud Native", "CNF"],
|
||||
"usage_example": "NFV enables network operators to deploy new services rapidly without installing new hardware equipment",
|
||||
"confidence": 0.95
|
||||
},
|
||||
{
|
||||
"term_id": "ext-ni-015",
|
||||
"name": "NWDAF (Network Data Analytics Function)",
|
||||
"category": "네트워크 인프라",
|
||||
"definition": "5G Core network function that provides network data analytics and supports data-driven network optimization using machine learning",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "3GPP",
|
||||
"document_title": "TS 23.288 - Architecture enhancements for 5G System (5GS) to support network data analytics services",
|
||||
"standard_id": "3GPP TS 23.288",
|
||||
"version": "18.2.0",
|
||||
"url": "https://www.3gpp.org/ftp/Specs/archive/23_series/23.288/",
|
||||
"date": "2024-03-20"
|
||||
},
|
||||
"context": "5G 네트워크의 인텔리전스 구현을 위한 데이터 분석 기능. AI/ML 기반 네트워크 자동화 및 최적화의 핵심 컴포넌트",
|
||||
"related_terms": ["AI/ML", "OAM", "Analytics ID", "NF Service Consumer", "PCF"],
|
||||
"usage_example": "NWDAF collects data from various network functions and provides analytics such as load prediction, QoS sustainability, and abnormality detection",
|
||||
"confidence": 0.93
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"domain": "기술 개발 및 연구 (Technology Development & R&D)",
|
||||
"samples": [
|
||||
{
|
||||
"term_id": "ext-td-001",
|
||||
"name": "AI-RAN",
|
||||
"category": "기술 개발 및 연구",
|
||||
"definition": "Artificial Intelligence integrated Radio Access Network that uses machine learning algorithms to optimize RAN operations, resource allocation, and performance",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "O-RAN Alliance",
|
||||
"document_title": "O-RAN AI/ML workflow description and requirements",
|
||||
"standard_id": "O-RAN.WG2.AIML-v01.03",
|
||||
"version": "1.03",
|
||||
"url": "https://www.o-ran.org/specifications",
|
||||
"date": "2024-02-15"
|
||||
},
|
||||
"context": "AI 기술을 RAN에 통합하여 자율적 네트워크 운영 및 최적화 실현. O-RAN 아키텍처의 핵심 기술 방향",
|
||||
"related_terms": ["RIC", "xApp", "rApp", "Machine Learning", "Network Automation"],
|
||||
"usage_example": "AI-RAN enables intelligent traffic steering, predictive maintenance, and dynamic spectrum sharing through ML models deployed in RIC",
|
||||
"confidence": 0.94
|
||||
},
|
||||
{
|
||||
"term_id": "ext-td-002",
|
||||
"name": "6G Research",
|
||||
"category": "기술 개발 및 연구",
|
||||
"definition": "Next generation mobile network technology targeting commercial deployment around 2030, with focus on terahertz communications, AI-native architecture, and holographic communications",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "ITU",
|
||||
"document_title": "IMT-2030 Framework and overall objectives",
|
||||
"standard_id": "ITU-R M.2160",
|
||||
"version": "Draft 1.0",
|
||||
"url": "https://www.itu.int/en/ITU-R/study-groups/rsg5/",
|
||||
"date": "2024-01-10"
|
||||
},
|
||||
"context": "2030년 상용화 목표의 차세대 이동통신 기술. 테라헤르츠 통신, AI 네이티브, 홀로그램 통신 등 혁신 기술 연구",
|
||||
"related_terms": ["THz Communication", "AI-Native", "Digital Twin", "Holographic MIMO", "Reconfigurable Intelligent Surface"],
|
||||
"usage_example": "6G is expected to achieve peak data rates of 1 Tbps and support immersive extended reality (XR) and holographic communications",
|
||||
"confidence": 0.91
|
||||
},
|
||||
{
|
||||
"term_id": "ext-td-003",
|
||||
"name": "Digital Twin Network",
|
||||
"category": "기술 개발 및 연구",
|
||||
"definition": "Virtual replica of physical network that enables testing, simulation, and optimization without affecting the live network",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "ETSI",
|
||||
"document_title": "Experiential Networked Intelligence (ENI); Requirements for Digital Twin Networks",
|
||||
"standard_id": "ETSI GR ENI 023",
|
||||
"version": "1.1.1",
|
||||
"url": "https://www.etsi.org/deliver/etsi_gr/ENI/001_099/023/",
|
||||
"date": "2023-12-05"
|
||||
},
|
||||
"context": "물리 네트워크의 디지털 복제본을 생성하여 시뮬레이션 및 최적화 수행. 네트워크 자동화 및 제로 터치 운영의 핵심",
|
||||
"related_terms": ["Network Simulation", "What-If Analysis", "Intent-Based Networking", "Zero Touch"],
|
||||
"usage_example": "Digital twin networks enable operators to test network changes and predict their impact before deployment in production",
|
||||
"confidence": 0.92
|
||||
},
|
||||
{
|
||||
"term_id": "ext-td-004",
|
||||
"name": "Quantum Communication",
|
||||
"category": "기술 개발 및 연구",
|
||||
"definition": "Communication technology leveraging quantum mechanics principles such as quantum entanglement and superposition for ultra-secure data transmission",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "ETSI",
|
||||
"document_title": "Quantum Key Distribution (QKD); Terminology and definitions",
|
||||
"standard_id": "ETSI GR QKD 007",
|
||||
"version": "1.1.1",
|
||||
"url": "https://www.etsi.org/deliver/etsi_gr/QKD/001_099/007/",
|
||||
"date": "2023-09-20"
|
||||
},
|
||||
"context": "양자역학 원리를 활용한 차세대 보안 통신 기술. 도청 불가능한 절대 보안 통신 실현 목표",
|
||||
"related_terms": ["QKD", "Quantum Entanglement", "Post-Quantum Cryptography", "Quantum Network"],
|
||||
"usage_example": "Quantum communication enables theoretically unbreakable encryption through quantum key distribution (QKD) protocols",
|
||||
"confidence": 0.90
|
||||
},
|
||||
{
|
||||
"term_id": "ext-td-005",
|
||||
"name": "RIS (Reconfigurable Intelligent Surface)",
|
||||
"category": "기술 개발 및 연구",
|
||||
"definition": "Planar surface with electronically controllable electromagnetic properties that can reflect, refract, or absorb radio waves to enhance wireless communication",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "IEEE",
|
||||
"document_title": "Reconfigurable Intelligent Surfaces for Wireless Communications: Principles, Challenges, and Opportunities",
|
||||
"standard_id": "IEEE Trans. Wireless Commun.",
|
||||
"version": "Vol. 20, No. 3",
|
||||
"url": "https://ieeexplore.ieee.org/document/9140329",
|
||||
"date": "2023-11-30"
|
||||
},
|
||||
"context": "전자적으로 제어 가능한 메타표면을 이용한 무선 환경 제어 기술. 6G 핵심 기술로 주목받는 혁신적 개념",
|
||||
"related_terms": ["Metasurface", "Smart Radio Environment", "6G", "Beamforming", "Coverage Enhancement"],
|
||||
"usage_example": "RIS can improve coverage and capacity by intelligently reflecting signals around obstacles in non-line-of-sight scenarios",
|
||||
"confidence": 0.89
|
||||
},
|
||||
{
|
||||
"term_id": "ext-td-006",
|
||||
"name": "THz Communication",
|
||||
"category": "기술 개발 및 연구",
|
||||
"definition": "Wireless communication using terahertz frequency band (0.1-10 THz) to achieve ultra-high data rates exceeding 100 Gbps",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "IEEE",
|
||||
"document_title": "IEEE 802.15 WPAN Terahertz Interest Group (IGTHz)",
|
||||
"standard_id": "IEEE 802.15-21-0421",
|
||||
"version": "Draft 2.0",
|
||||
"url": "https://mentor.ieee.org/802.15/documents",
|
||||
"date": "2024-01-25"
|
||||
},
|
||||
"context": "테라헤르츠 대역을 활용한 초고속 무선 통신 기술. 6G 후보 기술로 100Gbps 이상의 전송속도 목표",
|
||||
"related_terms": ["6G", "Sub-THz", "Extremely High Frequency", "Molecular Absorption", "Beamforming"],
|
||||
"usage_example": "THz communication can support data rates of 100+ Gbps but faces challenges in atmospheric absorption and limited range",
|
||||
"confidence": 0.88
|
||||
},
|
||||
{
|
||||
"term_id": "ext-td-007",
|
||||
"name": "Federated Learning",
|
||||
"category": "기술 개발 및 연구",
|
||||
"definition": "Distributed machine learning approach where model training occurs on decentralized devices without exchanging raw data, preserving privacy",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "3GPP",
|
||||
"document_title": "TS 23.700-81 - Study on architecture enhancements for Federated Learning in 5GS",
|
||||
"standard_id": "3GPP TR 23.700-81",
|
||||
"version": "18.0.0",
|
||||
"url": "https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-81/",
|
||||
"date": "2024-02-20"
|
||||
},
|
||||
"context": "개인정보 보호를 유지하면서 분산 학습을 수행하는 AI 기술. 5G/6G 네트워크의 인텔리전스 향상에 활용",
|
||||
"related_terms": ["Privacy Preserving", "Distributed ML", "NWDAF", "Edge AI", "Model Aggregation"],
|
||||
"usage_example": "Federated learning enables training ML models across multiple UEs without centralizing sensitive user data",
|
||||
"confidence": 0.93
|
||||
},
|
||||
{
|
||||
"term_id": "ext-td-008",
|
||||
"name": "Network Slicing Orchestration",
|
||||
"category": "기술 개발 및 연구",
|
||||
"definition": "Automated management and coordination of network slice lifecycle including creation, configuration, activation, and termination",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "ETSI",
|
||||
"document_title": "Zero-touch network and Service Management (ZSM); Means of Automation",
|
||||
"standard_id": "ETSI GS ZSM 002",
|
||||
"version": "1.1.1",
|
||||
"url": "https://www.etsi.org/deliver/etsi_gs/ZSM/001_099/002/",
|
||||
"date": "2023-10-15"
|
||||
},
|
||||
"context": "네트워크 슬라이스의 생명주기를 자동으로 관리하는 오케스트레이션 기술. 제로터치 네트워크 운영의 핵심",
|
||||
"related_terms": ["CSMF", "NSMF", "NSSMF", "Intent-Based", "Zero Touch", "E2E Orchestration"],
|
||||
"usage_example": "Network slicing orchestration automates the end-to-end management of slice instances across RAN, transport, and core domains",
|
||||
"confidence": 0.94
|
||||
},
|
||||
{
|
||||
"term_id": "ext-td-009",
|
||||
"name": "AI-Native Network",
|
||||
"category": "기술 개발 및 연구",
|
||||
"definition": "Network architecture designed from the ground up with AI/ML capabilities embedded at every layer for autonomous operation",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "ITU",
|
||||
"document_title": "Y.3172 - Architectural framework for machine learning in future networks including IMT-2020",
|
||||
"standard_id": "ITU-T Y.3172",
|
||||
"version": "06/2019",
|
||||
"url": "https://www.itu.int/rec/T-REC-Y.3172",
|
||||
"date": "2023-11-01"
|
||||
},
|
||||
"context": "AI가 네트워크 설계 단계부터 통합된 차세대 네트워크 구조. 6G의 핵심 아키텍처 방향",
|
||||
"related_terms": ["6G", "Network Autonomy", "AI Model Management", "ML Operations", "Self-Optimization"],
|
||||
"usage_example": "AI-native networks incorporate ML models as fundamental building blocks rather than add-on features",
|
||||
"confidence": 0.91
|
||||
},
|
||||
{
|
||||
"term_id": "ext-td-010",
|
||||
"name": "Open RIC (RAN Intelligent Controller)",
|
||||
"category": "기술 개발 및 연구",
|
||||
"definition": "Intelligent controller in O-RAN architecture that hosts AI/ML applications (xApps/rApps) for real-time RAN optimization and control",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "O-RAN Alliance",
|
||||
"document_title": "O-RAN RIC Architecture",
|
||||
"standard_id": "O-RAN.WG2.RIC-v02.00",
|
||||
"version": "2.00",
|
||||
"url": "https://www.o-ran.org/specifications",
|
||||
"date": "2024-03-01"
|
||||
},
|
||||
"context": "O-RAN 아키텍처의 인텔리전스 제어 플랫폼. Near-RT RIC와 Non-RT RIC으로 구성되어 AI 기반 RAN 최적화 수행",
|
||||
"related_terms": ["xApp", "rApp", "E2 Interface", "A1 Interface", "O-RAN", "AI/ML"],
|
||||
"usage_example": "The Near-RT RIC hosts xApps for sub-second control loops, while Non-RT RIC hosts rApps for longer-term optimization (>1 second)",
|
||||
"confidence": 0.95
|
||||
},
|
||||
{
|
||||
"term_id": "ext-td-011",
|
||||
"name": "Semantic Communication",
|
||||
"category": "기술 개발 및 연구",
|
||||
"definition": "Communication paradigm that transmits the meaning and intent of information rather than exact bit sequences, enabling ultra-efficient data transmission",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "IEEE",
|
||||
"document_title": "Semantic Communications for Future Internet: Fundamentals, Applications, and Challenges",
|
||||
"standard_id": "IEEE Wireless Commun.",
|
||||
"version": "Vol. 29, No. 1",
|
||||
"url": "https://ieeexplore.ieee.org/document/9714762",
|
||||
"date": "2023-12-15"
|
||||
},
|
||||
"context": "정보의 의미와 의도를 전송하는 차세대 통신 패러다임. 6G에서 대역폭 효율을 극대화하는 혁신적 접근",
|
||||
"related_terms": ["6G", "AI-Native", "Information Theory", "Task-Oriented Communication", "Knowledge Base"],
|
||||
"usage_example": "Semantic communication can reduce transmission overhead by 90% by sending only meaningful information based on shared context",
|
||||
"confidence": 0.87
|
||||
},
|
||||
{
|
||||
"term_id": "ext-td-012",
|
||||
"name": "Intent-Based Networking",
|
||||
"category": "기술 개발 및 연구",
|
||||
"definition": "Network management approach where operators specify high-level business intent, and the system automatically translates it into network configurations",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "TMForum",
|
||||
"document_title": "Autonomous Networks - Intent-driven closed loop assured services",
|
||||
"standard_id": "TMF921",
|
||||
"version": "2.0.0",
|
||||
"url": "https://www.tmforum.org/resources/standard/tmf921",
|
||||
"date": "2024-01-20"
|
||||
},
|
||||
"context": "비즈니스 의도를 고수준으로 표현하면 네트워크가 자동으로 구성을 최적화. 네트워크 자동화의 궁극적 목표",
|
||||
"related_terms": ["Zero Touch", "Autonomous Network", "Policy Management", "Closed Loop Automation"],
|
||||
"usage_example": "Intent-based networking allows operators to specify 'ensure 99.999% availability for critical services' without manual configuration",
|
||||
"confidence": 0.93
|
||||
},
|
||||
{
|
||||
"term_id": "ext-td-013",
|
||||
"name": "XR (Extended Reality)",
|
||||
"category": "기술 개발 및 연구",
|
||||
"definition": "Umbrella term encompassing AR (Augmented Reality), VR (Virtual Reality), and MR (Mixed Reality) technologies enabled by 5G/6G networks",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "3GPP",
|
||||
"document_title": "TR 26.928 - Extended Reality (XR) in 5G",
|
||||
"standard_id": "3GPP TR 26.928",
|
||||
"version": "17.0.0",
|
||||
"url": "https://www.3gpp.org/ftp/Specs/archive/26_series/26.928/",
|
||||
"date": "2023-09-30"
|
||||
},
|
||||
"context": "AR, VR, MR을 포괄하는 확장현실 기술. 5G/6G의 킬러 애플리케이션으로 초저지연 및 초고속 전송 요구",
|
||||
"related_terms": ["AR", "VR", "MR", "URLLC", "Cloud Gaming", "Metaverse", "Haptic"],
|
||||
"usage_example": "XR applications require end-to-end latency below 10ms and sustained data rates of 30-100 Mbps per user",
|
||||
"confidence": 0.95
|
||||
},
|
||||
{
|
||||
"term_id": "ext-td-014",
|
||||
"name": "Network Automation",
|
||||
"category": "기술 개발 및 연구",
|
||||
"definition": "Use of software and AI/ML to automatically configure, manage, test, deploy, and operate network services with minimal human intervention",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "ETSI",
|
||||
"document_title": "Zero-touch network and Service Management (ZSM); Reference Architecture",
|
||||
"standard_id": "ETSI GS ZSM 002",
|
||||
"version": "1.1.1",
|
||||
"url": "https://www.etsi.org/deliver/etsi_gs/ZSM/001_099/002/",
|
||||
"date": "2023-10-15"
|
||||
},
|
||||
"context": "AI/ML을 활용하여 네트워크 운영을 자동화하는 기술. 운영 효율성 극대화 및 인적 오류 최소화 목표",
|
||||
"related_terms": ["Zero Touch", "Closed Loop", "Self-Healing", "Self-Optimization", "MANO"],
|
||||
"usage_example": "Network automation enables zero-touch provisioning of network services from order to activation in minutes",
|
||||
"confidence": 0.96
|
||||
},
|
||||
{
|
||||
"term_id": "ext-td-015",
|
||||
"name": "Cloud Native Network Function",
|
||||
"category": "기술 개발 및 연구",
|
||||
"definition": "Network function designed using cloud-native principles including microservices, containerization, and DevOps for agile deployment",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "ETSI",
|
||||
"document_title": "NFV-IFA 040 - Requirements and Architecture for NFV Release 4",
|
||||
"standard_id": "ETSI GS NFV-IFA 040",
|
||||
"version": "4.3.1",
|
||||
"url": "https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/040/",
|
||||
"date": "2024-02-10"
|
||||
},
|
||||
"context": "클라우드 네이티브 원칙으로 설계된 네트워크 기능. 마이크로서비스, 컨테이너화, DevOps를 통한 민첩한 배포",
|
||||
"related_terms": ["CNF", "Kubernetes", "Microservices", "Container", "Helm Chart", "Service Mesh"],
|
||||
"usage_example": "Cloud-native network functions run in containers orchestrated by Kubernetes, enabling rapid scaling and automated lifecycle management",
|
||||
"confidence": 0.95
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"domain": "고객 서비스 (Customer Service)",
|
||||
"samples": [
|
||||
{
|
||||
"term_id": "ext-cs-001",
|
||||
"name": "CSI (Customer Satisfaction Index)",
|
||||
"category": "고객 서비스",
|
||||
"definition": "Standardized metric measuring customer satisfaction with products and services, typically on a scale of 0-100",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "ISO",
|
||||
"document_title": "ISO 10004:2018 - Quality management — Customer satisfaction — Guidelines for monitoring and measuring",
|
||||
"standard_id": "ISO 10004:2018",
|
||||
"version": "2018",
|
||||
"url": "https://www.iso.org/standard/71580.html",
|
||||
"date": "2023-11-15"
|
||||
},
|
||||
"context": "고객 만족도를 측정하는 국제 표준 지표. 통신사 서비스 품질 평가의 핵심 KPI",
|
||||
"related_terms": ["NPS", "CSAT", "CES", "Quality Management", "Voice of Customer"],
|
||||
"usage_example": "Telecom operators measure CSI quarterly through standardized surveys to track service quality trends",
|
||||
"confidence": 0.96
|
||||
},
|
||||
{
|
||||
"term_id": "ext-cs-002",
|
||||
"name": "NPS (Net Promoter Score)",
|
||||
"category": "고객 서비스",
|
||||
"definition": "Customer loyalty metric measuring the likelihood of customers to recommend a company's products or services on a scale of -100 to +100",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "Bain & Company",
|
||||
"document_title": "The One Number You Need to Grow",
|
||||
"standard_id": "Harvard Business Review",
|
||||
"version": "December 2003",
|
||||
"url": "https://hbr.org/2003/12/the-one-number-you-need-to-grow",
|
||||
"date": "2023-10-20"
|
||||
},
|
||||
"context": "고객 충성도와 추천 의향을 측정하는 핵심 지표. 통신업계에서 브랜드 경쟁력 평가에 널리 활용",
|
||||
"related_terms": ["Promoter", "Passive", "Detractor", "Customer Loyalty", "Word of Mouth"],
|
||||
"usage_example": "Customers rating 9-10 are Promoters, 7-8 are Passives, and 0-6 are Detractors in NPS methodology",
|
||||
"confidence": 0.97
|
||||
},
|
||||
{
|
||||
"term_id":="ext-cs-003",
|
||||
"name": "CSAT (Customer Satisfaction Score)",
|
||||
"category": "고객 서비스",
|
||||
"definition": "Short-term satisfaction metric measuring customer happiness with a specific interaction or transaction, typically on a 1-5 scale",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "ITU",
|
||||
"document_title": "E.800 - Definitions of terms related to quality of service",
|
||||
"standard_id": "ITU-T E.800",
|
||||
"version": "09/2008",
|
||||
"url": "https://www.itu.int/rec/T-REC-E.800",
|
||||
"date": "2023-09-25"
|
||||
},
|
||||
"context": "특정 상호작용에 대한 즉각적 만족도 측정. 콜센터, 매장 방문 등 개별 접점 품질 평가에 활용",
|
||||
"related_terms": ["Transaction Satisfaction", "Touch Point", "Service Quality", "First Call Resolution"],
|
||||
"usage_example": "CSAT surveys are typically sent immediately after customer service interactions to measure satisfaction while the experience is fresh",
|
||||
"confidence": 0.95
|
||||
},
|
||||
{
|
||||
"term_id": "ext-cs-004",
|
||||
"name": "FCR (First Call Resolution)",
|
||||
"category": "고객 서비스",
|
||||
"definition": "Contact center metric measuring the percentage of customer inquiries resolved during the first interaction without callbacks or escalations",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "ICMI",
|
||||
"document_title": "Call Center Management on Fast Forward: Succeeding in the New Era of Customer Experience",
|
||||
"standard_id": "Industry Best Practice",
|
||||
"version": "4th Edition",
|
||||
"url": "https://www.icmi.com/resources",
|
||||
"date": "2023-12-01"
|
||||
},
|
||||
"context": "첫 통화에서 고객 문의를 해결하는 비율. 고객 만족도와 운영 효율성의 핵심 지표",
|
||||
"related_terms": ["AHT", "Call Center", "Customer Effort Score", "Resolution Rate"],
|
||||
"usage_example": "Industry benchmark for FCR in telecom contact centers is 70-75%, with top performers achieving 80%+",
|
||||
"confidence": 0.94
|
||||
},
|
||||
{
|
||||
"term_id": "ext-cs-005",
|
||||
"name": "AHT (Average Handle Time)",
|
||||
"category": "고객 서비스",
|
||||
"definition": "Contact center metric measuring the average duration of a customer interaction including talk time, hold time, and after-call work",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "COPC Inc.",
|
||||
"document_title": "COPC CX Standard for Contact Centers",
|
||||
"standard_id": "COPC CX 7.0",
|
||||
"version": "7.0",
|
||||
"url": "https://www.copc.com/standards/",
|
||||
"date": "2024-01-10"
|
||||
},
|
||||
"context": "콜센터 상담원의 평균 처리 시간 측정. 효율성과 서비스 품질 균형의 핵심 지표",
|
||||
"related_terms": "Talk Time", "Hold Time", "ACW", "Service Level", "Occupancy Rate"],
|
||||
"usage_example": "Typical AHT for telecom customer service ranges from 5-8 minutes, balancing efficiency with quality resolution",
|
||||
"confidence": 0.96
|
||||
},
|
||||
{
|
||||
"term_id": "ext-cs-006",
|
||||
"name": "CES (Customer Effort Score)",
|
||||
"category": "고객 서비스",
|
||||
"definition": "Metric measuring the ease of customer experience by asking 'How easy was it to interact with our company?' on a scale of 1-7",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "Gartner",
|
||||
"document_title": "Effortless Experience: Conquering the New Battleground for Customer Loyalty",
|
||||
"standard_id": "Industry Research",
|
||||
"version": "2013",
|
||||
"url": "https://www.gartner.com/en/customer-service-support",
|
||||
"date": "2023-10-30"
|
||||
},
|
||||
"context": "고객이 문제 해결에 들인 노력의 정도를 측정. 낮은 노력이 높은 충성도로 연결됨을 입증",
|
||||
"related_terms": ["Customer Effort", "Ease of Use", "Self-Service", "Omnichannel", "Journey Mapping"],
|
||||
"usage_example": "Research shows 96% of customers with high-effort experiences become disloyal, compared to only 9% with low-effort experiences",
|
||||
"confidence": 0.93
|
||||
},
|
||||
{
|
||||
"term_id": "ext-cs-007",
|
||||
"name": "SLA (Service Level Agreement)",
|
||||
"category": "고객 서비스",
|
||||
"definition": "Formal commitment defining the level of service expected from a service provider, including metrics, responsibilities, and remedies",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "ITU",
|
||||
"document_title": "M.3080 - Management of the business agreement and its related SLA for TMN services",
|
||||
"standard_id": "ITU-T M.3080",
|
||||
"version": "10/2006",
|
||||
"url": "https://www.itu.int/rec/T-REC-M.3080",
|
||||
"date": "2023-11-05"
|
||||
},
|
||||
"context": "서비스 제공자와 고객 간의 공식적인 서비스 수준 약정. 품질 보증 및 책임 소재 명확화",
|
||||
"related_terms": ["Uptime", "Response Time", "MTTR", "Penalty Clause", "Service Credits"],
|
||||
"usage_example": "Enterprise SLAs typically guarantee 99.9% network uptime with financial penalties for non-compliance",
|
||||
"confidence": 0.97
|
||||
},
|
||||
{
|
||||
"term_id": "ext-cs-008",
|
||||
"name": "Omnichannel Experience",
|
||||
"category": "고객 서비스",
|
||||
"definition": "Integrated customer experience strategy providing seamless interaction across all channels (phone, web, mobile, social, store) with consistent service",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "TMForum",
|
||||
"document_title": "GB988 - Customer Experience Management",
|
||||
"standard_id": "TMF GB988",
|
||||
"version": "6.0.0",
|
||||
"url": "https://www.tmforum.org/resources/standard/gb988",
|
||||
"date": "2024-02-15"
|
||||
},
|
||||
"context": "모든 채널에서 일관되고 통합된 고객 경험 제공. 채널 전환 시에도 맥락이 유지되는 서비스",
|
||||
"related_terms": ["Multichannel", "Channel Integration", "Customer Journey", "Unified Commerce", "Cross-Channel"],
|
||||
"usage_example": "Omnichannel strategy allows customers to start a transaction on mobile app and complete it at a physical store with full context",
|
||||
"confidence": 0.95
|
||||
},
|
||||
{
|
||||
"term_id": "ext-cs-009",
|
||||
"name": "Voice of Customer (VoC)",
|
||||
"category": "고객 서비스",
|
||||
"definition": "Systematic process of capturing customers' expectations, preferences, and aversions to drive business improvements",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "ISO",
|
||||
"document_title": "ISO 10001:2018 - Quality management — Customer satisfaction — Guidelines for codes of conduct",
|
||||
"standard_id": "ISO 10001:2018",
|
||||
"version": "2018",
|
||||
"url": "https://www.iso.org/standard/69558.html",
|
||||
"date": "2023-12-20"
|
||||
},
|
||||
"context": "고객의 의견과 요구사항을 체계적으로 수집·분석하여 서비스 개선에 반영하는 프로세스",
|
||||
"related_terms": ["Customer Feedback", "Survey", "Social Listening", "Sentiment Analysis", "Customer Insight"],
|
||||
"usage_example": "VoC programs combine multiple data sources including surveys, social media, call center interactions, and complaints to understand customer needs",
|
||||
"confidence": 0.94
|
||||
},
|
||||
{
|
||||
"term_id": "ext-cs-010",
|
||||
"name": "Customer Journey Mapping",
|
||||
"category": "고객 서비스",
|
||||
"definition": "Visual representation of every experience customers have with a service, product, or brand across all touchpoints and channels",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "TMForum",
|
||||
"document_title": "TR257 - Customer Experience Framework",
|
||||
"standard_id": "TMF TR257",
|
||||
"version": "1.0.0",
|
||||
"url": "https://www.tmforum.org/resources/technical-report/tr257",
|
||||
"date": "2024-01-05"
|
||||
},
|
||||
"context": "고객이 서비스를 인지하고 구매·사용·이탈하는 전 과정을 시각화하여 개선점 도출",
|
||||
"related_terms": ["Touch Point", "Pain Point", "Moment of Truth", "Customer Experience", "Persona"],
|
||||
"usage_example": "Journey maps identify pain points such as long wait times during activation or confusing bill formats that drive customer dissatisfaction",
|
||||
"confidence": 0.93
|
||||
},
|
||||
{
|
||||
"term_id": "ext-cs-011",
|
||||
"name": "Churn Prediction",
|
||||
"category": "고객 서비스",
|
||||
"definition": "Use of data analytics and machine learning to identify customers at risk of canceling service, enabling proactive retention efforts",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "TMForum",
|
||||
"document_title": "IG1230 - Big Data Analytics Implementation Guide",
|
||||
"standard_id": "TMF IG1230",
|
||||
"version": "2.1.0",
|
||||
"url": "https://www.tmforum.org/resources/implementation-guide/ig1230",
|
||||
"date": "2024-02-25"
|
||||
},
|
||||
"context": "데이터 분석 및 ML을 활용하여 이탈 위험 고객을 사전에 식별하고 선제적 유지 활동 수행",
|
||||
"related_terms": ["Retention", "Customer Lifetime Value", "Propensity Model", "Predictive Analytics", "At-Risk Customer"],
|
||||
"usage_example": "Churn prediction models analyze usage patterns, payment history, service complaints, and competitive offers to identify high-risk customers",
|
||||
"confidence": 0.95
|
||||
},
|
||||
{
|
||||
"term_id": "ext-cs-012",
|
||||
"name": "Self-Service Portal",
|
||||
"category": "고객 서비스",
|
||||
"definition": "Digital platform enabling customers to perform service-related tasks independently without agent assistance, including account management and troubleshooting",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "Gartner",
|
||||
"document_title": "Magic Quadrant for Customer Service and Support Technologies",
|
||||
"standard_id": "Gartner Research",
|
||||
"version": "2023",
|
||||
"url": "https://www.gartner.com/en/customer-service-support",
|
||||
"date": "2023-11-10"
|
||||
},
|
||||
"context": "고객이 상담원 도움 없이 스스로 계정관리, 요금조회, 문제해결 등을 수행할 수 있는 디지털 플랫폼",
|
||||
"related_terms": ["Digital Channel", "IVR", "Chatbot", "Knowledge Base", "FAQ", "Automation"],
|
||||
"usage_example": "Modern self-service portals deflect 40-60% of routine inquiries, reducing call center volume and improving customer satisfaction",
|
||||
"confidence": 0.96
|
||||
},
|
||||
{
|
||||
"term_id": "ext-cs-013",
|
||||
"name": "Proactive Customer Care",
|
||||
"category": "고객 서비스",
|
||||
"definition": "Service approach that anticipates and addresses customer needs before they contact support, using predictive analytics and automation",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "Forrester",
|
||||
"document_title": "The Future Of Customer Service: Proactive, Predictive, And Profitable",
|
||||
"standard_id": "Forrester Research",
|
||||
"version": "Q2 2023",
|
||||
"url": "https://www.forrester.com/report/",
|
||||
"date": "2023-09-15"
|
||||
},
|
||||
"context": "문제 발생을 예측하고 고객이 연락하기 전에 선제적으로 해결책을 제공하는 서비스 방식",
|
||||
"related_terms": ["Predictive Analytics", "Network Monitoring", "Outage Notification", "Usage Alert", "Preventive Maintenance"],
|
||||
"usage_example": "Proactive care includes notifying customers of network outages before they experience issues or alerting them to unusual data usage patterns",
|
||||
"confidence": 0.94
|
||||
},
|
||||
{
|
||||
"term_id": "ext-cs-014",
|
||||
"name": "Customer Segmentation",
|
||||
"category": "고객 서비스",
|
||||
"definition": "Process of dividing customers into groups based on common characteristics, behaviors, or needs to deliver targeted services and communications",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "TMForum",
|
||||
"document_title": "GB922 - Customer Business Entity Definitions",
|
||||
"standard_id": "TMF GB922",
|
||||
"version": "19.0.0",
|
||||
"url": "https://www.tmforum.org/resources/standard/gb922",
|
||||
"date": "2024-01-30"
|
||||
},
|
||||
"context": "고객을 특성, 행동, 니즈 기반으로 그룹화하여 맞춤형 서비스 및 커뮤니케이션 제공",
|
||||
"related_terms": ["Customer Profiling", "Persona", "Value-Based Segmentation", "Behavioral Segmentation", "CLV"],
|
||||
"usage_example": "Telecom operators segment customers into high-value, mid-tier, and basic groups to tailor retention offers and service levels",
|
||||
"confidence": 0.95
|
||||
},
|
||||
{
|
||||
"term_id": "ext-cs-015",
|
||||
"name": "Real-Time Personalization",
|
||||
"category": "고객 서비스",
|
||||
"definition": "Dynamic customization of customer interactions and offers based on real-time data, context, and behavioral signals",
|
||||
"source_type": "external",
|
||||
"source_metadata": {
|
||||
"source": "Gartner",
|
||||
"document_title": "Predicts 2024: Customer Service and Support Technologies",
|
||||
"standard_id": "Gartner Research",
|
||||
"version": "2024",
|
||||
"url": "https://www.gartner.com/en/customer-service-support",
|
||||
"date": "2024-02-05"
|
||||
},
|
||||
"context": "실시간 데이터와 컨텍스트 기반으로 고객 상호작용 및 제안을 동적으로 맞춤화",
|
||||
"related_terms": ["AI/ML", "Recommendation Engine", "Next Best Action", "Contextual Offer", "Dynamic Content"],
|
||||
"usage_example": "Real-time personalization engines analyze customer location, device, usage patterns, and browsing behavior to present relevant offers instantly",
|
||||
"confidence": 0.93
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
Reference in New Issue
Block a user