Delayed Contributions  |
|
Number
|
Title
|
Source
|
AI/Question
|
Date
|
|
[ 634 ]
|
Proposed changes to draft TRQ.NCAP1
|
NTT COMWARE CORP.
|
QN1/11, Q1/11
|
2004-02-18 |
|
[ 633 ]
|
Analysis of the differences between the xDSL and IMS session control protocol
|
France Telecom
|
QN3/11, Q11/11, Q6/11
|
2004-02-18 |
|
[ 632 ]
|
Draft TRQ.NCAPX
|
France Telecom
|
QN2/11, Q6/11
|
2004-02-18 |
|
[ 631 ]
|
Building the NGN standards from the 3GPP IMS Specifications
|
France Telecom
|
QN2/11, QN1/11, Q6/11, Q1/11
|
2004-02-18 |
|
[ 630 ]
|
Proposals for Updating Questions for submission to WTSA-2004
|
France Telecom
|
QALL/11
|
2004-02-18 |
|
[ 629 ]
|
Proposal for the handling of New Questions N1 to N3/11
|
France Telecom
|
QALL/11
|
2004-02-18 |
|
[ 628 ]
|
ISDN Simulation in an NGN: the example of the CCBS supplementary service
|
Siemens AG
|
QN1/11, Q6/11
|
2004-02-18 |
|
[ 627 ]
|
Generic NGN functional architecture with session and call control infrastructure
|
Siemens AG
|
QN1/11
|
2004-02-18 |
|
[ 626 ]
|
Examples of IMS relocation in an NGN session and call control functional architecture
|
Siemens AG
|
QN3/11, QN1/11
|
2004-02-18 |
|
[ 625 ]
|
NGN Requirements
|
Siemens AG
|
QN1/11
|
2004-02-18 |
|
[ 624 ]
|
Proposed draft of the Guideline document for API specification
|
NTT Corporation
|
Q4/11
|
2004-02-18 |
|
[ 623 ]
|
Comments on "TRQ.NCAPX" new requirements
|
Deutsche Telekom
|
QN2/11, Q9/11, Q6/11
|
2004-02-18 |
|
[ 622 ]
|
Comments on "TRQ.NCAPX" Chapters 10-14
|
Deutsche Telekom
|
QN2/11, Q9/11, Q6/11
|
2004-02-18 |
|
[ 621 ]
|
Comments on "TRQ.NCAPX" Chapters 6 - 9
|
Deutsche Telekom
|
QN2/11, Q9/11, Q6/11
|
2004-02-18 |
|
[ 620 ]
|
Comments on "TRQ.NCAPX" Chapters 1 - 5
|
Deutsche Telekom
|
QN2/11, Q9/11, Q6/11
|
2004-02-18 |
|
[ 619 ]
|
TRQ.BICC/ISUP-SIP-2 Requirements for Closed User Group (CUG)
|
Deutsche Telekom
|
Q9/11, Q6/11
|
2004-02-18 |
|
[ 618 ]
|
TRQ.BICC/ISUPSIP-2 Requirements for Call Forwarding Supplementary Services
|
Deutsche Telekom
|
Q9/11, Q6/11
|
2004-02-18 |
|
[ 617 ]
|
TRQ.BICC/ISUPSIP Set2 Requirements for Sub-addressing (SUB)
|
Deutsche Telekom
|
Q9/11, Q6/11
|
2004-02-18 |
|
[ 616 ]
|
TRQ.BICC/ISUPSIP Set2 Requirements for MCID
|
Deutsche Telekom
|
Q9/11, Q6/11
|
2004-02-18 |
|
[ 615 ]
|
Proposed revised text to draft Signalling Requirements to support IP Telephony
|
NEC Corporation, NTT
|
Q7/11
|
2004-02-17 |
|
[ 614 ]
|
Additional CS3 Requirements for the support of Profiles and Individual Auditing in CBC
|
L.M. Ericsson
|
Q9/11
|
2004-02-18 |
|
[ 613 ]
|
Proposed Requirement Signalling Flows for the PTime Selection mechanism
|
L.M. Ericsson
|
Q9/11
|
2004-02-18 |
|
[ 612 ]
|
Proposed Requirement Signalling Flows for support of Compressed voice CODECS for 3.1. kHz calls
|
L.M. Ericsson
|
Q9/11
|
2004-02-18 |
|
[ 611 ]
|
Proposed Requirement Signalling Flows for support of Comfort Noise parameters in BICC CS3.
|
L.M. Ericsson
|
Q9/11
|
2004-02-18 |
|
[ 610 ]
|
Call Flows for IEPS Bearer Level - Priority Indicator Functionality
|
L.M. Ericsson
|
Q9/11
|
2004-02-18 |
|
[ 609 ]
|
Call Flows for IEPS Bearer Level - Queuing Functionality
|
L.M. Ericsson
|
Q9/11
|
2004-02-18 |
|
[ 608 ]
|
Proposal on how to handle TRQ.RSVP
|
Nortel Networks (Canada)
|
Q8/11
|
2004-02-16 |
|
[ 607 ]
|
Discussion in regards to COM 17 - LS 18 - E on security requirements
|
Nortel Networks (Canada)
|
QALL/11
|
2004-02-16 |
|
[ 606 ]
|
Need for a practical example requiring the use of the proposed new mechanism to carry narrowband service signalling information within IP-based signalling systems
|
Nortel Networks (Canada)
|
Q16/11, Q6/11
|
2004-02-16 |
|
[ 605 ]
|
Proposal to modify the Content Disposition header field in Q.GTD.1
|
Nortel Networks (Canada)
|
Q16/11, Q6/11
|
2004-02-16 |
|
[ 604 ]
|
Enhancement proposed to make GTD globally acceptable
|
Nortel Networks (Canada)
|
Q16/11, Q6/11
|
2004-02-16 |
|
[ 603 ]
|
Proposals to enhance Q.GTD to allow for extensibility and logical growth
|
Nortel Networks (Canada)
|
Q16/11, Q6/11
|
2004-02-16 |
|
[ 602 ]
|
Implication of removing Requirement 3 from TRQ.NSIP as per Delayed D.580
|
Nortel Networks (Canada)
|
Q6/11
|
2004-02-16 |
|
[ 601 ]
|
Semantics of GTD content
|
Nortel Networks (Canada)
|
Q16/11, Q6/11
|
2004-02-16 |
|
[ 600 ]
|
Reference scenarios for the use of GTD
|
Nortel Networks (Canada)
|
Q16/11, Q6/11
|
2004-02-16 |
|
[ 599 ]
|
Concerns about "compact mode" in draft Q.GTD1
|
Nortel Networks (Canada)
|
Q16/11, Q6/11
|
2004-02-16 |
|
[ 598 ]
|
Definition of "Mapped Parameter" in draft Recommendation Q.GTD.2
|
Nortel Networks (Canada)
|
Q16/11, Q6/11
|
2004-02-16 |
|
[ 597 ]
|
Structure of TRQ.BICC CS3 Requirements.
|
L.M. Ericsson
|
Q9/11
|
2004-02-17 |
|
[ 596 ]
|
Requirement for IP V4 - IP V6 negotiation with BICC.
|
L.M. Ericsson
|
Q9/11
|
2004-02-17 |
|
[ 595 ]
|
Comments on the Draft Signalling Requirements to support IP telephony
|
Finnish Communications Regulatory Authority
|
Q7/11
|
2004-02-16 |
|
[ 594 ]
|
Merger of existing protocol Questions
|
Australia
|
QALL/11
|
2004-02-13 |
|
[ 593 ]
|
Merger of existing Signalling Requirement Questions
|
Australia
|
QALL/11
|
2004-02-13 |
|
[ 592 ]
|
Questions for the next Study Period
|
Australia
|
QALL/11
|
2004-02-13 |
|
[ 591 ]
|
Use of Info method in SIP-I (Q.1912.5)
|
LM Ericsson
|
Q11/11
|
2004-02-12 |
|
[ 590 ]
|
Priority Bearer Connection Setup in DSS2
|
United States of America
|
Q12/11, Q11/11
|
2004-02-11 |
|
[ 589 ]
|
Priority Bearer Connection Setup in AAL2
|
United States of America
|
Q15/11
|
2004-02-11 |
|
[ 588 ]
|
Responses to the Proposals Regarding CgPC for Mobile Originated Calls
|
United States of America
|
Q12/11, Q11/11, Q9/11
|
2004-02-11 |
|
[ 587 ]
|
BICC Enhancements for IEPS
|
United States of America
|
Q12/11, Q11/11
|
2004-02-11 |
|
[ 586 ]
|
ISUP Enhancements for IEPS
|
United States of America
|
Q12/11, Q11/11
|
2004-02-11 |
|
[ 585 ]
|
New IEPS Call Information parameter for ISUP and BICC
|
United States of America
|
Q12/11, Q11/11
|
2004-02-11 |
Results:59 total items.
Result page:
1 -
2
- Next
|
Multiple Document Download: Formats and Languages to be included (when available):
